-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws-lambda-python-alpha: Bundling - AssetHashType.OUTPUT failing cdk destroy #26345
Comments
I didn't get it. According your repro steps, you actually provided the
|
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
Bundling prop was provided. However asset_hash_type=AssetHashType.OUTPUT still fails a Very basic repo to reproduce the issue here: |
Seeing this with node functions on deploy as well btw. lmk if more info is required or you'd prefer it in another issue <3 ty |
Still getting this |
Describe the bug
RuntimeError: Cannot use
output
hash type whenbundling
is not specified.cdk destroy and cdk destroy --no-staging both failing because we have the following bundling options for our lambda:
We create the hash on the Output because our exclusions list is large and some files in the exclusions list are dynamic leading to changes in hash and unnecessary redeployments.
Expected Behavior
cdk destroy and cdk destroy --no-staging should destroy the stack. Creating a hash type of OUTPUT has no relevance here.
Current Behavior
The following stack trace was emitted:
Reproduction Steps
Create a python lambda function with the following options:
deploy and run
cdk destroy --no-staging
Possible Solution
Logic contained within
aws-cdk/packages/aws-cdk-lib/core/lib/asset-staging.ts
Line 501 in f15ed23
Additional Information/Context
No response
CDK CLI Version
2.85.0 (build 4e0d726)
Framework Version
No response
Node.js Version
v18.16.0
OS
MacOs 13.4.1 (c)
Language
Python
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: