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

Introduce application health status #249

Open
axelfontaine opened this issue Mar 4, 2021 · 0 comments
Open

Introduce application health status #249

axelfontaine opened this issue Mar 4, 2021 · 0 comments

Comments

@axelfontaine
Copy link
Member

Currently deployments are transactional, ensuring that once a running version of an app is live it doesn't get replaced by a broken version down the line (based on the results of the healthcheck).

For an initial deployment this breaks down slightly. Every failed attempt at getting that first correct version up and running results in databases and load balancers being provisioned and then torn down again once the healthcheck fails.

This could be improved by marking the application as unhealthy instead, preventing those time-consuming provisioning tasks from being torn down again, making subsequent deployment attempts much faster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant