chore: prepare lambda layer catalog - #269
Open
ava-silver wants to merge 3 commits into
Open
Conversation
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #269 +/- ##
==========================================
+ Coverage 86.27% 86.83% +0.56%
==========================================
Files 18 19 +1
Lines 1690 1762 +72
Branches 345 352 +7
==========================================
+ Hits 1458 1530 +72
Misses 231 231
Partials 1 1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.

What does this PR do?
Adds a generated Lambda layer catalog and derives the macro's existing runtime, architecture, tracer, and Extension layer lookups from it. Layer versions remain optional and require explicit configuration.
Motivation
Lambda layer metadata needs one generated source of truth before it can consume the shared Serverless catalog. This format-only preparation preserves the macro's current behavior.
Testing Guidelines
Not tested manually.
Additional Notes
This consumer intentionally retains Java 8, Node.js 12/14/16, and Python 2.7/3.6/3.7 even though the central catalog excludes them. Python 2.7/3.6/3.7 also retain their missing ARM layer names and current
layer:undefinedARN behavior. An APM Serverless-approved behavior change must reconcile these runtimes before enabling the CloudFormation runtime campaign.Types of changes
Check all that apply