feat: automatic Lambda runtime detection from layer metadata#41
Open
Jno21 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The previous implementation hardcoded runtime selection based on layer version numbers (e.g.,
>= 94→python3.14). This required manual updates whenever Datadog updated the forwarder layer.We could instead read directly from the data source
aws_lambda_layer_versionand getcompatible_runtimes. This makes the code easier to maintain.Implementation
Picks the latest one using
reverse(sort(tolist(...)))[0]. Thesortis necessary because Terraform does not guarantee set ordering, andreverseensures we always pick the highest Python version.