-
Notifications
You must be signed in to change notification settings - Fork 4.1k
feat (pipelines): Follow up on Recent V2 Pipeline Type Implementation #34209
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
Comments
Hey @andreamac003, Thank you for reporting this issue. You're correct that while PR #34005 added support for setting The
Until this is implemented, I did notice the following workaround where i was able to access V2 features:
|
Hi @ykethan , thank you for the quick reply! Yes, so our team has tried that same workaround provided in the cdk community slack channel, but unfortunately our team ran into some errors with that approach, which is what prompted us to raise the original feature request for support on the pipelines.CodePipeline construct. If your team is able to apply these features to this construct directly, we would greatly appreciate it 🙌 |
@andreamac003 interesting, would you be able to share some insights on the issues you experienced. If you do believe they may be bugs do create a issue we would be happy in diving into them. |
Thanks @ykethan , I'll have to go back and see what the specific errors were, but I do know one of the big issues for us with that workaround is that it created a new pipeline rather than updating the existing one in place, so we needed a solution where we could keep the same pipeline |
Hi Community, |
Describe the feature
I would like to follow up on #33995 which was recently implemented as part of PR #34005
The upgrade in place for the v2 pipeline type in cdk.pipelines is working great. However, when I try to implement the features in V2 pipeline, I see that some properties are not found, for example,
executionMode
andtriggers
are not valid property onpipelines.CodePipeline
and so I cannot implement the features available in CodePipeline V2:The features I am trying to test are found below. In addition to
executionMode
andtriggers
, I am not sure what else is needed, but I assume the solution would be to implement the same properties inaws-cdk-lib/aws-codepipeline
to now be in the newly updated construct inaws-cdk-lib/pipelines
Use Case
So that we can take advantage of all the CodePipeline v2 features shown above in the newly updated cdk.pipelines CodePipeline construct
Proposed Solution
I believe the solution would be to implement the same properties in
aws-cdk-lib/aws-codepipeline
to now be in the newly updated construct inaws-cdk-lib/pipelines
Other Information
The documentation I am looking at is below, and so I would like to ensure these features are available for use on the new construct:
Acknowledgements
CDK version used
2.189.0
Environment details (OS name and version, etc.)
MacOS Sequoia 15.4.1
The text was updated successfully, but these errors were encountered: