-
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-cdk/lib/index.js: No longer able to update our cdk stacks #26182
Comments
|
I have resolved this issue now. If anyone comes across this in the future this issue is that for some reason within CloudFormation there was a Change Set to be Executed event though the CloudFormation was showing as UPDATE_COMPLETE Seems like there was an update at some point in the last day which was able to execute I would assume |
Describe the bug
Apologies if this is the incorrect place to post this issue but we are no longer able to update our stacks through the cdk. Whenever we run
npx cdk deploy
it results in the following error:Which would make sense if the stack wasn't showing as available in the AWS console, not sure if anyone has come across this issue before and are able to advise on how to resolve
Expected Behavior
In terms of expected behavior when I run the following:
npx cdk deploy
It deploys the cdk without it throwing the following error when the stack is showing available:
An operation on this ChangeSet is currently in progress. Please attempt this operation again later.
Current Behavior
When running
npx cdk deploy
the response message is the following:Reproduction Steps
In terms of reproducing the error I'm not entirely sure what has happened as the issues started happening yesterday.
I know this isn't useful so I apologies in advance but was hoping someone has come across something similar in the past.
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.81
Framework Version
No response
Node.js Version
20.3.1
OS
ubuntu
Language
Typescript
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: