What is the problem?
When using the SelfMutate step it calls cdk -a ${toPosixPath(embeddedAsmPath(this.pipeline))} deploy ${pipelineStackIdentifier} --require-approval=never --verbose. With the new cdk release this fetches notices. If the SelfMutate runs in a private subnet without internet connection the step takes really long until the request times out. (Build times go up from 2 minutes to 16 minutes).
Reproduction Steps
Create a pipeline which uses the SelfMutate option and runs in a private subnet.
What did you expect to happen?
For the SelfMutate I do not think that it is necessary to fetch the notices.
What actually happened?
The deploy step tries to fetch the notices.
CDK CLI Version
2.17.0
Node.js Version
16.14.0
OS
MacOS Monetery 12.3
Language
Typescript
I think it would suffice to add the --no-notices flag to the cdk deploy command.
What is the problem?
When using the SelfMutate step it calls
cdk -a ${toPosixPath(embeddedAsmPath(this.pipeline))} deploy ${pipelineStackIdentifier} --require-approval=never --verbose. With the new cdk release this fetches notices. If the SelfMutate runs in a private subnet without internet connection the step takes really long until the request times out. (Build times go up from 2 minutes to 16 minutes).Reproduction Steps
Create a pipeline which uses the SelfMutate option and runs in a private subnet.
What did you expect to happen?
For the SelfMutate I do not think that it is necessary to fetch the notices.
What actually happened?
The deploy step tries to fetch the notices.
CDK CLI Version
2.17.0
Node.js Version
16.14.0
OS
MacOS Monetery 12.3
Language
Typescript
I think it would suffice to add the
--no-noticesflag to the cdk deploy command.