search

awslabs / landing-zone-accelerator-on-aws

Deploy a multi-account cloud foundation to support highly-regulated workloads and complex compliance requirements.
https://aws.amazon.com/solutions/implementations/landing-zone-accelerator-on-aws/
Apache License 2.0
566 stars 454 forks source link

feat: Move to CodePipeline V2 #596

Open mbevc1 opened 1 month ago

mbevc1 commented 1 month ago

Is your feature request related to a problem? Please describe. There is new version and features with CodePipeline V2.

Describe the feature you'd like Pipelines should move to V2: https://docs.aws.amazon.com/codepipeline/latest/userguide/pipeline-types.html

Additional context n/a

richardkeit commented 1 month ago

Hi @mbevc1 ,

What features from V2 would the AWS team take advantage of?

mbevc1 commented 1 month ago

Hey @richardkeit .

I think it might make connecting to GH repos easier and hopefully avoid using tokens.

kisst commented 1 month ago

[Notification] AWS CodePipeline is changing the default pipeline type to V2

You are receiving this message because you created one or more pipelines in the past 8 weeks. AWS CodePipeline provides two pipeline types: V1 and V2. These pipeline types differ in the features supported and in their pricing [1]. Currently, pipelines are created as V1 pipelines by default. To create a V2 pipeline, you need to set it as the pipeline type. Beginning December 9, 2024, AWS CodePipeline will create pipelines as a V2 type when the pipeline type is not specified. This change is applicable when creating pipelines using the AWS SDK, CLI, CloudFormation, or CDK. Existing pipelines are not affected by this change. Since the V2 pipeline type is compatible with the V1 pipeline type, there is no immediate action required.

kisst commented 1 month ago

btw to answer the "What features" question , here is one 

Error
Source revisions can only be used with V2 pipelines.