Skip to content
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

no dns cleanup in case of stack destroy #115

Open
ykachube opened this issue Apr 26, 2023 · 2 comments
Open

no dns cleanup in case of stack destroy #115

ykachube opened this issue Apr 26, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@ykachube
Copy link

Ii seems that when this code is in place dns record is created correctly after task becomes RUNNING
but if to delete stack dns record is not cleaned-up

Expected behavior
I assume there should be code to cleanup created records upon stack destruction

@ykachube ykachube added the bug Something isn't working label Apr 26, 2023
@engineal
Copy link
Owner

engineal commented Apr 30, 2023

Thank you for bringing this to my attention @ykachube. If I may ask, are you deploying the ECS cluster, ECS service, and this construct as part of a single stack or across multiple stacks?

@ykachube
Copy link
Author

Hi, to add some details - I need to provide DNS for private IP of task created by stack, so not quite this construct, but same approach. Stack only creates serivces and tasks, cluster created separately and looked up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants