ci: update region denylist for lambda layers #1171
Merged
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.
Problem
Lambda layers were failing to publish with:
It turns out this error was caused by lambda layers trying to be added to new AWS regions, which are deactivated by default. See a list of new regions here: https://docs.aws.amazon.com/accounts/latest/reference/manage-acct-regions.html
Solution
Updated the deny list of regions to attempt publishing lambda layers to, as new regions have been added since the last RFDK release. Added a log statement so it's clear which region has failed.
Testing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license