-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Open
Labels
bugThis issue is a bug.This issue is a bug.cliIssues related to the CDK CLIIssues related to the CDK CLIeffort/mediumMedium work item – several days of effortMedium work item – several days of effortp2package/toolsRelated to AWS CDK Tools or CLIRelated to AWS CDK Tools or CLI
Description
Describe the bug
When deploying from the CLI, I'd expect that cdk deploy "beta*" would deploy beta/stackA, beta/stackB, and beta/X/stackC. However, it seems the glob will not pass the / marker. cdk deploy "beta/*" works as expected.
Expected Behavior
I would expect that any stacks matched by the glob would be deployed - this would be the happy path for deploying a whole Stage.
Current Behavior
$ cdk deploy "beta*"
No stacks match the name(s) beta*
Given:
$ cdk list
toplevelA
toplevelB
beta/nested
Reproduction Steps
POC for a related issue: https://github.com/haljarrett/cdk-stage-issue
Execute cdk deploy "beta*" and find that no stacks are matched.
Possible Solution
Suspect that this is a related issue to the one I opened yesterday: #28283, and maybe has to do with how stack names are matched in cdk-toolkit.ts.
Additional Information/Context
No response
CDK CLI Version
2.114.1 (build 02bbb1d)
Framework Version
No response
Node.js Version
v20.6.0
OS
MacOS
Language
TypeScript
Language Version
No response
Other information
No response
Metadata
Metadata
Assignees
Labels
bugThis issue is a bug.This issue is a bug.cliIssues related to the CDK CLIIssues related to the CDK CLIeffort/mediumMedium work item – several days of effortMedium work item – several days of effortp2package/toolsRelated to AWS CDK Tools or CLIRelated to AWS CDK Tools or CLI