-
Notifications
You must be signed in to change notification settings - Fork 4k
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
(cli): import is not using a custom qualifier #32278
Comments
@moltar Good afternoon. Somehow, I'm unable to reproduce the issue using
CLEANUP: Please let me know if I'm missing anything. Did you also update the version of CDK CLI using command Thanks, |
Hi @ashishdhingra thank you for the repro steps. I think the bootstrap stack name plays a role too. In your repro, you still used the default one (CDKToolkit) which I'm guessing CDK then uses to find/infer some knowledge. I use a different stack name. And what fixed the import for me was to explicitly set the stack name as the CLI option. But IMO that should be unnecessary as there's nothing that CDK should need from that stack. Everything it needs to do the work is based on well known resource names based on the qualifier. |
RESULT:
|
Describe the bug
Similar to #29179,
cdk import
ignores qualifier set in thecdk.json
context and tries to use defaults.Which results in a failure.
Supplying the stack name fixes the problem, but it's not a scalable approach.
Regression Issue
Last Known Working CDK Version
2.171.0
Expected Behavior
cdk import
to respect the qualifier.Current Behavior
Does not respect the qualifier.
Reproduction Steps
Use a custom qualifier.
Try to do an import with a large template.
Get an error:
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.171.0
Framework Version
No response
Node.js Version
22
OS
macOs
Language
TypeScript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: