(pipelines): CDK packages deployment race condition #13221
Description
When using pipelines.CdkPipeline, the default is to install the latest CDK version, which for me was 1.91.0, which happened to have been deployed only minutes before. But installation failed because it then tried to install @aws-cdk/cloud-assembly-schema of the same version, which was not yet available on npm.
Error I got in the selfupdate stage in CodeBuild:
[Container] 2021/02/23 13:23:35 Entering phase INSTALL
[Container] 2021/02/23 13:23:35 Running command npm install -g aws-cdk
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @aws-cdk/[email protected].
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-02-23T13_23_40_901Z-debug.log
[Container] 2021/02/23 13:23:40 Command did not exit successfully npm install -g aws-cdk exit status 1
[Container] 2021/02/23 13:23:40 Phase complete: INSTALL State: FAILED
[Container] 2021/02/23 13:23:40 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: npm install -g aws-cdk. Reason: exit status 1
I think that the actual fix for this is for me to set cdkCliVersion to a version I know is on npm, but this was still surprising behaviour.
Things I can think of that might fix this:
- If cdk version X depends on cloud-assembly-schema version X, should cloud-assembly-schema get released first?
- Alternatively, it might make sense for
CdkPipelineto default to the version of CDK that is in use (so the version used within the pipeline matches the version used to deploy the pipeline).