feat(codepipeline): auto rollback for pipeline

[go-to-k]

TODO

• Design
  • I'm wondering if we should provide the properties onFailure and FailureConditions as per CFn or have a boolean type like 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.
  • It is also possible to add a failureConditionsResult as an enum type to stageProps instead of onFailure (FailureConditions) to prevent nesting.
  • We could add the autoRollback property for now and deprecate it if the structure FailureConditions is needed in the future.
• Verify with CFn and add validations if needed
  • if a stage is source stage
  • if a pipeline type is NOT V2
• unit tests
• integ tests
• README
• Change the PR title if needed and this description

Issue # (if applicable)

Closes #30083.

Reason for this change

• Whats New
  • https://aws.amazon.com/about-aws/whats-new/2024/04/aws-codepipeline-stage-level-manual-automated-rollback/
• User guide
  • https://docs.aws.amazon.com/codepipeline/latest/userguide/stage-rollback-auto.html
• CloudFormation
  • 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

WIP

Description of how you validated changes

WIP

Checklist

• My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[aws-cdk-automation]

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

[aws-cdk-automation]

The pull request linter fails with the following errors:

❌ Features must contain a change to a README file.
❌ Features must contain a change to a test file.
❌ Features must contain a change to an integration test file and the resulting snapshot.

PRs must pass status checks before we can provide a meaningful review.

If you would like to request an exemption from the status checks or clarification on feedback, please leave a comment on this PR containing Exemption Request and/or Clarification Request.

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 450a609
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[TheRealAmazonKendra]

I think that we are getting too many features that are only available on pipelines v2 to keep adding properties to the same construct. It's probably time that we make a PipelineV2 instead of just adding more props that only work in specific circumstances.

[go-to-k]

@TheRealAmazonKendra

I see. I think it is good to work on this issue after the V2 construct is completed, so I will close this PR for the time being.

[tvdijk]

Hi, is there an issue I can follow for the V2 construct?