Describe the feature
the aws_codepipeline package was update to allow pipeline type v2 (super excited, love it, have been waiting a long time for this)
I have services that use both the pipelines and aws_codepipeline package depending on the use case. I have very easily done the upgrade on my more complex pipelines and shortly will be doing some work for environment variables.
so 2 things:
- services that have simpler pipelines using the pipelines module are now getting this warning
[Warning at example] V1 pipeline type is implicitly selected when `pipelineType` is not set. If you want to use V2 type, set `PipelineType.V2`. [ack: @aws-cdk/aws-codepipeline:unspecifiedPipelineType]
- granted this is just a warning, but is a slight pain when dealing with logs and running grep for warnings and errors
- Is there anything in the pipelines team pipeline (if you will) for implementation
- I have a very full schedule right now, running all arch/devops/devex/backend for my company (have worked every weekend for about 4 months now)
- if there is nothing in the backlog, i might be able to put in a story to add the implementation in 2-3 weeks and submit the pr to you
- if something is in the backlog for support in the pipelines package, is there a timeframe?
Hope this doesn't seem pushy, I'm just really excited that the first part came through and even more then wanting to get rid of the warnings. I would like to move a bunch of things to env variables instead of some of the hardcoded arns and ssm work arounds I have going on.
P.S. Got started working on the cognito pre token generation v2 for scopes transition this week and am finishing it up this weekend. like 19 thumbs up on that, makes my multi tenant (users can have multiple tenants also and different scopes per tenant) 1000000x simpler
Use Case
described in feature*
Proposed Solution
described in feature*
if its backlogged to be done shortly, I'm super excited. if not I can toss it in to my work in a few weeks and create a pr
Other Information
No response
Acknowledgements
CDK version used
2.128.0
Environment details (OS name and version, etc.)
n/a
Describe the feature
the aws_codepipeline package was update to allow pipeline type v2 (super excited, love it, have been waiting a long time for this)
I have services that use both the pipelines and aws_codepipeline package depending on the use case. I have very easily done the upgrade on my more complex pipelines and shortly will be doing some work for environment variables.
so 2 things:
[Warning at example] V1 pipeline type is implicitly selected when `pipelineType` is not set. If you want to use V2 type, set `PipelineType.V2`. [ack: @aws-cdk/aws-codepipeline:unspecifiedPipelineType]Hope this doesn't seem pushy, I'm just really excited that the first part came through and even more then wanting to get rid of the warnings. I would like to move a bunch of things to env variables instead of some of the hardcoded arns and ssm work arounds I have going on.
P.S. Got started working on the cognito pre token generation v2 for scopes transition this week and am finishing it up this weekend. like 19 thumbs up on that, makes my multi tenant (users can have multiple tenants also and different scopes per tenant) 1000000x simpler
Use Case
described in feature*
Proposed Solution
described in feature*
if its backlogged to be done shortly, I'm super excited. if not I can toss it in to my work in a few weeks and create a pr
Other Information
No response
Acknowledgements
CDK version used
2.128.0
Environment details (OS name and version, etc.)
n/a