This repository has been archived by the owner on Sep 9, 2020. It is now read-only.
Add scaling event state management to track event details. #28
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.
Previously the only way to understand what scaling events had been
triggered was to check the Sherpa server logs. This is not ideal
for operators and results in an incomplete picture. This change
adds scaling event state storage, allowing for operators to list
and view scaling events that have been triggered.
The Consul path CLI parameter has been changed to reflect the fact
it now relates to both policies and state. The change doesn't break
existing installs though.
Closes #26