Deploying stack all other stack assets must be present

❓ General Issue

I have multiple stacks in my project and want I deploy only one of them all other stack assets must be present in file tree or else I get ENOENT: no such file or directory, stat....

I did a little digging and figured: a. cdk cli spawns process ts-node /bin/script.ts b. cdk cli does not pass stack name to aws-cdk, therefore I cannot know which should be synthesized c. aws-cdk generates all cloudformation jsons for all stacks it can find and cdk cli picks the ones it needs

I think it would be smart to provide the name of stack and generate only provided one, it would be faster and would not require all assets to be present.

PS. With aws-cli I’m referening to aws-cdk installed globally and with aws-cdk I refer to project dependency.

The Question

1. I wonder what was the reasoning for current approach and should it be changed?
2. Maybe I’m missing something and this can be easily resolved?

Environment

• **CDK CLI Version: 1.27.0 (build a98c0b3)
• **Module Version: “@aws-cdk/core”: “^1.27.0”
• **OS: MacOs Mojave
• **Language: Typescript

Other information

[diesal11]

Any update on this?

[dansalias]

I am encountering the same issue.

Synthesising or attempting to deploy a stack with the --exclusively flag when another stack in the app references a nonexistent path with lambda.Code.fromAsset('/path/that/does-not/exist') fails with the message Cannot find asset at /path/that/does-not/exist.

I’ve put a minimal reproduction together at https://github.com/dansalias/tmp-cdk-6743