[Enhancement]: add support for codepipeline type(v1,v2)

[lmayorga1980]

Description

https://aws.amazon.com/about-aws/whats-new/2023/10/aws-codepipeline-parameterized-pipelines/

Affected Resource(s) and/or Data Source(s)

• aws_codepipeline

Potential Terraform Configuration

No response

References

No response

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[aaron-christian-nttd]

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.

[DrFaust92]

looking into this

[thangdoan89]

@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.

[neruneruo]

I'm trying to implement a fix.

Enhanced attribute is pipeline_type and variable.

Code-modify and AccTest-modify completed.

[romangoldberg]

Hello,
any updates?