-
Notifications
You must be signed in to change notification settings - Fork 9k
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
[Enhancement]: add support for codepipeline type(v1,v2) #34122
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This forces all previous available features like cloudwatch events into v2 with default being v1. This will break new pipeline deployments if you rely on these features until you can select version in your module. Within my infra, I can manually select v2 after deployment and it behaves as intended. |
looking into this |
@DrFaust92 Hi, can I ask the progress of this enhancement? It would be nice of you if we can know the proportion. Many love and thanks. |
I'm trying to implement a fix. Enhanced attribute is Code-modify and AccTest-modify completed. |
Hello, |
This functionality has been released in v5.32.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
https://aws.amazon.com/about-aws/whats-new/2023/10/aws-codepipeline-parameterized-pipelines/
Affected Resource(s) and/or Data Source(s)
Potential Terraform Configuration
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: