-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: source_code_hash not getting persisted to tf statefile - causes lambda deployment even if there is no change in etag #29921
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This functionality has been released in v5.32.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Terraform Core Version
1.3.9
AWS Provider Version
4.58.0
Affected Resource(s)
aws_lambda_function
Expected Behavior
Based on source_code_hash, lambda should not be re-deployed / changed if there is no difference in the etag or source_code_hash.
Actual Behavior
The source_code_hash isnt getting stored to the statefile for some reason. Because of this everytime I run a terraform plan or apply, the lambda gets re-deployed even if there is no new zip upload my s3 bucket.
Ran terraform apply 1st time.
Ran terraform apply second time
You can see that the source_code_hash is not getting persisted to the tf statefile.
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
N/A
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: