-
Notifications
You must be signed in to change notification settings - Fork 213
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
During deployments (only), we mark applications as ready depending on the outcome of potentially configured readiness checks. The change goes along with some major refactoring, primarily focused towards retrieving all necessary state from a single Marathon API request thanks to the 'embed=apps.{tasks,deployments,readiness}' query parameter. This is necessary in order to retrieve a single, consistent app/task state not skewed by two API requests send away at slightly different offsets. Additionally, we stop considering tasks as ready which have not yet reached the TASK_RUNNING state since still staging or otherwise non-ready tasks are bound to fail if taken into load-balancing rotation prematurely.
- Loading branch information
1 parent
69ec469
commit 767b0d1
Showing
2 changed files
with
502 additions
and
113 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.