You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A workaround for this is to define multiple watchers, one for each data center. But that is not a great workaround because:
When number of data center changes the config needs to be changed to account for that.
Multiple watchers can trigger the same handler in essentially the same moment for two different DCs causing race conditions.
All of this would be much simpler if -datacenter=all was supported.
Use Case(s)
In our case this doesn't work since we want to be able to detect events across all data centers. This useful for triggering configuration of WireGuard VPN, which exists on all hosts across all data centers, and needs to be updated every time a new host shows up, or leaves the network. With the current setup it would require extra automation to either continuously update the list of watchers, or use the API and dynamically query all data centers.
The text was updated successfully, but these errors were encountered:
Feature Description
Currently the Watch API and command both default to listening for events or service changes in one data center:
https://developer.hashicorp.com/consul/docs/dynamic-app-config/watches#global-parameters
A workaround for this is to define multiple watchers, one for each data center. But that is not a great workaround because:
All of this would be much simpler if
-datacenter=all
was supported.Use Case(s)
In our case this doesn't work since we want to be able to detect events across all data centers. This useful for triggering configuration of WireGuard VPN, which exists on all hosts across all data centers, and needs to be updated every time a new host shows up, or leaves the network. With the current setup it would require extra automation to either continuously update the list of watchers, or use the API and dynamically query all data centers.
The text was updated successfully, but these errors were encountered: