This repository has been archived by the owner on Dec 4, 2024. It is now read-only.
disable configuration cleanup on failed validation (#554) #558
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change set introduces an optional command line flag, which allows to skip the new app by app validation/cleanup in favour of the old behaviour:
A broken setup causes no reload of the haproxy.cfg. The old configuration is still usable. The haproxy.cfg is checked once entirely for configuration problems.
Unfortunately for the setup described in #554 the new app-by-app cleanup meant, that some applications would not be accessible anymore after removing them, depending on the order they are delivered by marathon. This currently prevents us from upgrading marathon-lb.