fix(docs): keep China layer versions aligned - #8438
Open
dreamorosi wants to merge 1 commit into
Open
Conversation
Stage the installation page in release documentation updates and constrain ARN replacements by partition. This keeps China aligned without advancing GovCloud or implying continued Python 3.9 releases. Fixes GH-8437
boring-cyborg
Bot
added
documentation
powertools-for-aws-oss-automation
Bot
added
the
size/M
|
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.
Issue number: closes #8437
Summary
Changes
User experience
The installation guide now provides valid current ARNs for supported runtimes without implying that Python 3.9 has layers beyond version 27. Future release documentation PRs will keep China ARNs aligned and will only be merged after the partition deployment succeeds.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.