ATLAS-3508: Add API for getting the active instance as a HTTP status code (503 or 200)#72
Closed
andrewluotechnologies wants to merge 1 commit intoapache:masterfrom
Closed
Conversation
…code (503 or 200)
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Currently, Atlas exposes the active instance using the web API /api/atlas/admin/status. However, this returns the status using a string embedded in the body of the response rather than a HTTP error code. For haproxy, this works but requires a sufficient buffer size for the response. On the other hand, for certain proxies (envoy in particular), this is not supported. This proposes to add a new API to return the status of the instance as an HTTP error code: 200 for active, 503 for passive