scottk/vault
1
0
Fork 0
mirror of https://github.com/optim-enterprises-bv/vault.git synced 2025-10-31 10:37:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs/events: update note about client redirect for 1.19 (#29705)

Browse Source 
* docs/events: update note about client redirect for 1.19

* Update website/content/docs/concepts/events.mdx

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>

---------

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
This commit is contained in:
Theron Voran
2025-02-28 13:15:25 -08:00
committed by GitHub
parent 17c0ee93cb
commit 6bf505c1a3
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
website/content/docs/concepts/events.mdx
View File

@@ -139,8 +139,8 @@ Here is an example event notification in JSON format:
<Note title="Note"> <Note title="Note">
For multi-node Vault deployments, Vault only accepts subscriptions on the active node. If a client attempts to subscribe to events on a standby node, For multi-node Vault deployments, Vault only accepts subscriptions on the active node and performance standbys.
Vault will respond with a redirect to the active node. Vault uses the [`api_addr`](/vault/docs/configuration#api_addr) of the active node's configuration to route the redirect. Vault reroutes subscription requests made to [non-performance standby nodes](/vault/docs/enterprise/performance-standby#disabling-performance-standbys) to the active node based on the [`api_addr`](/vault/docs/configuration#api_addr) configuration setting on the active node.
Vault deployments with performance replication must subscribe to events on the Vault deployments with performance replication must subscribe to events on the
primary performance cluster. Vault ignores subscriptions made from secondary primary performance cluster. Vault ignores subscriptions made from secondary