-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(codepipeline-v2): start codepipeline v2 #33511
Comments
I guess this might need a RFC. I'm bringing it up to the team for inputs. |
Hi there, Codepipeline dev |
Any ETA on this one ? |
Sorry no clear ETA on this. Already in review process. Will post the update once the review gets approved. But I assume it will be delivered in a few days |
### Issue # (if applicable) #33511 ### Reason for this change Codepipeline launched this feature last years and still missed the update in cdk library. ### Description of changes Support this feature in L2 Construct:https://docs.aws.amazon.com/codepipeline/latest/userguide/concepts-how-it-works-conditions.html ### Describe any new or updated permissions being added No ### Description of how you validated changes Unit test, integ test, and local cdk library deployment(linked to local cdkApp and successfully deploy it) ### Checklist - [Y ] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Hi community, |
The features listed above now are available in aws-codepipeline lib. Please feel free to reach out to us if you have more ideas about V2 construct. |
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
GitPushFilter
with branches and file paths for trigger #29127Feel free to add more features you like to see in the 'new V2' construct
Features
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
CDK version used
2.197.0
The text was updated successfully, but these errors were encountered: