-
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
Resources created by CDK missing in console #8346
Comments
Additional observation: If I use |
The resource link for an Activity in CloudFormation console is pointing to "Tasks" which redirects to the service /homepage. The resource id link is: https://eu-central-1.console.aws.amazon.com/states/home?region=eu-central-1#/tasks but it should be https://eu-central-1.console.aws.amazon.com/states/home?region=eu-central-1#/activities Apart from that I could not reproduce the issue in my build, used same version, just running on macOs Catalina. I could see the activity in stepfunctions console and fetch the list via aws cli :/ |
@am29d thanks for logging this issue! I don't believe this is a CDK bug as it appears to be an incorrect link generated in the CloudFormation console. I'll find the stakeholders that can address this issue. For now I'm marking this as guidance instead of a bug. |
aws-cloudformation/cloudformation-coverage-roadmap#139 if this is just an incorrect CloudFormation console link |
Not really actionable for us. Sorry. |
|
Not sure who is responsible for this bug: CloudFormation or CDK, but this is super annoying:
CDK runs into permanent state when any creation of resource with name reported as Successful while there is no any resource is created.
Reproduction Steps
Make sure that CF report that deletion succeeded.
Verify that resource is actually gone.
Check console:
CREATE_COMPLETE
Check that there is everything green in event log - all green and reports as resource creted.
Error Log
No errors. All Green.
Resource is not created.
Environment
Other
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: