Skip to content
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.

Fix incorrect response code and msg when scaling breaks thresholds #62

Merged
merged 1 commit into from
Oct 2, 2019

Conversation

jrasell
Copy link
Owner

@jrasell jrasell commented Oct 2, 2019

Previously errors when triggering a scaling action such as the
new count breaking policy thesholds would result in a 304 response
code and an empty message. This changes fixes the behaviour so
that the client will recieve a 409 response code with a useful
message to indicate the reason for not performing the action.

Closes #59

Previously errors when triggering a scaling action such as the
new count breaking policy thesholds would result in a 304 response
code and an empty message. This changes fixes the behaviour so
that the client will recieve a 409 response code with a useful
message to indicate the reason for not performing the action.

Closes #59
@jrasell jrasell added area/scaling Issues related to scaling kind/bug Issues relating to bugs area/api Issues related to the API labels Oct 2, 2019
@jrasell jrasell self-assigned this Oct 2, 2019
@jrasell jrasell merged commit 77647b6 into master Oct 2, 2019
@jrasell jrasell deleted the gh-59 branch October 2, 2019 17:06
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/api Issues related to the API area/scaling Issues related to scaling kind/bug Issues relating to bugs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect response code and error when API scaling breaks limits
1 participant