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.

Sign up for GitHub

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

Jump to bottom

Support custom service termination order #180

Open
CathalMullan opened this issue Jan 7, 2023 · 0 comments
Open

Support custom service termination order #180

CathalMullan opened this issue Jan 7, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@CathalMullan
Copy link

Similar to how services are started in a specific order (using 'start-after'), would it be possible to shutdown services in a specific order as well? Maybe even just in the reverse order that the services were started?

My use case is that I run a VPN (Tailscale), logs collector (Grafana Agent) and an API in the same container. When a shutdown occurs, ideally the API would shutdown first, then the logs collector, then the VPN. But currently, since the signal is sent to all services at once, the order is fairly random.
@CathalMullan CathalMullan added the enhancement New feature or request label Jan 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@CathalMullan