hashicorp / hashicorp/consul-aws

[req] Purge synced services on exit

Open
#10 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
55
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Currently, consul-aws publishes the consul services and nodes. But does not clean-up after itself on exit. When we stopped the services and removed the container daemon we found all services were still listed.

I found this out when I decided to remove the discovery zone (via Terraform). AWS Cloud Map will not let one delete the zone until all services are deleted, and one cannot remove a service until all instances are deleted. There was much ... clicking that day.

Thank you

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing where consul-aws publishes services and nodes and how process exit is handled. Check the AWS Cloud Map cleanup flow and verify that stopping consul-aws removes its services and instances, leaving the discovery zone deletable.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go
Domain
cloud
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.