feat(codepipeline): auto rollback for pipeline #30085
Draft
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.
WIP: waiting for CFn and the L1 props. see #30083 (comment).
I'm also wondering if we should provide the property as per CFn or have a boolean type like a
autoRollback
. I think customizing it for CDK is a good design, but given the recent CodePipeline trend and its CFn structure, there may be extensions to this in the future. (I've pushed a commit to add a property with the same structure as CFn simply for the record now.)Issue # (if applicable)
Closes #30083.
Reason for this change
https://aws.amazon.com/jp/about-aws/whats-new/2024/04/aws-codepipeline-stage-level-manual-automated-rollback/
https://docs.aws.amazon.com/codepipeline/latest/userguide/stage-rollback-auto.html
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-codepipeline-pipeline-stagedeclaration.html
https://docs.aws.amazon.com/codepipeline/latest/APIReference/API_StageDeclaration.html
Description of changes
Description of how you validated changes
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license