feat(forwarder): add SKIP_REGIONS env var for layer publishing#1139
Merged
Conversation
ndakkoune
approved these changes
May 27, 2026
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
SKIP_REGIONSenv var (comma-separated), so you can skip specific AWS regions during layer publishing (e.g. during a regional outage), and surfaces the existingPROD_GITHUB_RESTART=truerestart flow inrelease.shvia a startup tip and an EXIT-trap hint on failure.Motivation
There is an existing outage in
me-south-1that prevents us from publishing Lambda layers, and as a result the release fails.Testing Guidelines
Additional Notes
Types of changes
Check all that apply