docs: lambda layer version may not be 1#2430
Merged
Merged
Conversation
Suggest to always check the ARNs listed in the release notes instead of assuming that the layer version will always be 1.
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
xrmx
commented
Sep 19, 2025
🔍 Preview links for changed docs |
Also fix it for code blocks
xrmx
force-pushed
the
doc-lambda-support
branch
from
a2e5b6d to
5adecd0
Compare
basepi
approved these changes
Sep 19, 2025
xrmx
changed the title
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
3 participants
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 pull request do?
Don't hardcode the apm layer version as 1, in 6.24.0 it's 3. While at it fix vars substitution.
Related issues