Open
Description
Describe the bug
When I run exclusive flag during deploy, the lambda within nested stack failed to do bundling
Expected Behavior
Assets bundling should executed and bundled
Current Behavior
Asset bundling ignored
Reproduction Steps
Demo example created under https://github.com/jk2l/CDK-Debug.git
if you run cdk deploy -e DEBUG-pipeline-DEV/DEV/debug
the lambda lib won't be added into part of the packaging
if you run without -e you should have the lambda dependency from requirements.txt added into lambda folder structure
pre-req for running the demo: you need to put your own account id under cdk.json line 19 (replace the 000000000000)
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
v2.150.0
Framework Version
No response
Node.js Version
v18.15.0
OS
Ubuntu 22.04.1 LTS from Windows WSL
Language
Python
Language Version
Python 3.9
Other information
This may related to the following bug reports:
- (core): Stack assets are no longer bundled if contained in a stage #21162
- (aws-cdk): asset bundling skipped when using --exclusively with custom stack name #19927
- core: incorrect asset bundling skip for assets in stacks inside stages inside stacks #21925
- fix(core): asset bundling skipped when using --exclusively with custom stack name #21248