Conversation
Add a non-secret `ebs` block to the authed GET status response so we can
detect a prod deployment accidentally pointed at the staging EBS (the
order-sync misroute). Reports { host, configured, targetsStage,
apiKeyMatchesStage } — targetsStage is true when the deployment default
EBS_BASE_URL equals EBS_BASE_URL_STAGE. Never returns the API key or full URL.
The public version endpoint now reports whether this deployment's EBS and EBS-JSON targets match their injected _STAGE values (targetsStage / apiKeyMatchesStage) so a prod deploy accidentally pointed at staging is visible without auth. Booleans only — no hosts, URLs, or keys. Pairs with the detailed authed check on the ebs-sync status endpoint.
feat(ebs-sync): EBS config health check on status + version endpoints
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.
No description provided.