Handle Vault standby health responses#1007
Open
henkhofs wants to merge 1 commit into
Open
Conversation
Signed-off-by: henkhofs <henk.hofs@nedap.com>
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.
ReactiveVaultSysTemplate currently propagates VaultClientResponseException for Vault sys/health responses with non-2xx status codes. Vault uses 429 for standby nodes while still returning a health response body, and the blocking VaultSysTemplate already deserializes that body.
This change aligns the reactive implementation with the blocking one by deserializing the sys/health response body from VaultClientResponseException. It also exposes Vault's ha_connection_healthy field through VaultHealth so downstream health contributors can distinguish healthy HA standbys from standbys without an active-node connection.
Tests added/updated:
Verified with: