generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 181
Closed
Labels
automationThis item relates to automationThis item relates to automationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)pending-releaseThis item has been merged and will be released soonThis item has been merged and will be released soon
Description
Summary
Currently, we must run the GitHub action that deploys to China and GovCloud 4 times, once each of gamma and then for prod. This requires manual steps that are error prone. We should update the deployment job to first deploy to gamma and if that succeeds then deploy to prod.
Let's also add another layer of vaildation, let's add a check to make sure that the layer version passed in to the action is exactly one version above the previous one.
Why is this needed?
This will prevent accidentally forgetting the promote to prod step.
Which area does this relate to?
Automation
Solution
Make the GitHub action deploy to gamma and prod sequentially with the prod deployment only happening if gamma is successful.
Acknowledgment
- This request meets Powertools for AWS Lambda (TypeScript) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET
Future readers
Please react with 👍 and your use case to help us understand customer demand.
Metadata
Metadata
Assignees
Labels
automationThis item relates to automationThis item relates to automationinternalPRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)pending-releaseThis item has been merged and will be released soonThis item has been merged and will be released soon
Type
Projects
Status
Coming soon