add source code hash to lambda layer #509
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AFT Version
1.13.2
Open issue
#507
Description
I implemented AFT a few months ago when it was not yet compatible with GitLab. Recently, I noticed that starting with version 1.13.2, the module now supports GitLab integration.
While updating the AFT module to use GitLab, I encountered the same issue: when files in the bucket aft-customizations-pipeline-your_account_id were updated, Terraform did not detect the changes to generate a new layer version. This caused a mismatch between the bucket and the code used by the layer.
The solution I implemented was to add the source_code_hash attribute to the aws_lambda_layer_version resource, setting it to use the etag attribute from the aws_s3_bucket_object data source. This ensures that whenever the object in the bucket is updated, Terraform detects the change and automatically publishes a new layer version.
Reference links