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
{{ message }}
This repository has been archived by the owner on Jul 27, 2023. It is now read-only.
Sometimes it is necessary to query a Key/Value from another data center. The most visible use-case is a developer working locally on the laptop/desktop, but wanting to act like a QA or PROD server. Rather than running a local Consul instance, changing its datacenter, and redoing all of its joins, it would be much better to just tap into a consistent web API endpoint and use the existing WAN gossip.
The KeyValueClient currently doesn't support this, even though the underlying Consul API does. QueryOptions does not have a datacenter parameter, and CatalogOptions, which has a datacenter, isn't accepted by any of the KeyValueClient methods.
HealthClient, on the other hand, does support this method, through CatalogOptions.
The text was updated successfully, but these errors were encountered:
Sometimes it is necessary to query a Key/Value from another data center. The most visible use-case is a developer working locally on the laptop/desktop, but wanting to act like a QA or PROD server. Rather than running a local Consul instance, changing its datacenter, and redoing all of its joins, it would be much better to just tap into a consistent web API endpoint and use the existing WAN gossip.
The
KeyValueClient
currently doesn't support this, even though the underlying Consul API does.QueryOptions
does not have adatacenter
parameter, andCatalogOptions
, which has adatacenter
, isn't accepted by any of theKeyValueClient
methods.HealthClient
, on the other hand, does support this method, throughCatalogOptions
.The text was updated successfully, but these errors were encountered: