-
Notifications
You must be signed in to change notification settings - Fork 9
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
Can't change defaultCloudMapNamespace on the cluster #121
Comments
Can you share a snippet of code where you used the construct? |
I built an app to show the issue. It seems I was mistaken on the source of the issue, it triggers the error when adding cloudMapOptions to an Ec2Service, line 140 at ecstest-stack.ts . Clone the code from: https://github.com/Ismael/cdkecstest , edit bin/ecstest.ts with your vpc and ecs codedeploy role. Deploy once, then uncomment after line 140 and deploy. This should trigger the error. |
Does it only fail if you deploy first without cloudmap and then update stack to add cloudmap? |
Yes. |
Thanks for the sample code. Unfortunately, this is a limitation with configuring ECS Services to use |
Is there any workaround? I don't know enough about the internals, but maybe using cdk to create only the task definition and using EcsDeployment to actually trigger it? |
No, not that I'm aware of. |
I found the upstream issue was recently closed as shipped: aws-cloudformation/cloudformation-coverage-roadmap#1529 |
While changing the ECS defaultCloudMapNamespace, a deployment causes this error:
Is there any way to force the deployment using this construct? Or any other way around?
The text was updated successfully, but these errors were encountered: