feat(codepipeline-v2): start codepipeline v2

[jaecktec]

Describe the feature

I'd like to advertise for codepipeline v2 construct.
Since there were some attempts to add v2 features to the current construct, none of them were successful or even rolled back.

The idea is to have an issue we can follow and maybe link some draft PRs so we can discuss the best outcome.

Related issues and comments

• aws_codepipeline: Rollbacks for CodePipelines #30083
• 'We should start a V2 construct' feat(codepipeline): auto rollback for pipeline #30465 (comment)
• feat(codepipeline): GitPushFilter with branches and file paths for trigger #29127
• CodePipeline: Missing stage inputs for onSuccess, onFailure, and beforeEntry #31833
• Code Pipeline: Stage(step) skipping condition support #32045

Feel free to add more features you like to see in the 'new V2' construct

Features

• BeforEntry
• SuccessConditions
• FailiureConditions
• Stage Rollback
• Trigger support

Use Case

Support V2 Pipeline features in a convenient way

Proposed Solution

Create a V2 construct that is heavily inspired by the existing Pipeline construct - but extends the required features.

Maybe:
For cleanup we could roll back #29134 to make clear that the current one is the V1 construct and the new one is V2 so that migration should be a replacement of the Construct not a property.

Other Information

While I would be happy to extend the existing construct I can also see the argument for creating a V2 construct.

Also we probably want to have this as an alpha - I couln't find the docs on how to create an alpha module, so I'd request some help from the maintainers for this :)

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.197.0

[pahud]

I guess this might need a RFC. I'm bringing it up to the team for inputs.