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 Apr 15, 2024. It is now read-only.
I've probably misread the documentation, but it appears the host= parameter to the consul.Consul() class is very misleading. In my current environment, I have 4 separate Consul clusters I need to add/update KV information in. I attempted to use python-consul to update these, not knowing that the library is effectively an API/abstraction of the local consul agent. When attempting to debug, it was not clear to me that the client was connecting to the local agent instead of the intended hostnames and/or FQDNs.
Documentation should be updated to reflect this more clearly and should indicate that host= is not intended to point to a remote consul server or cluster. Thank you.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
I've probably misread the documentation, but it appears the
host=
parameter to theconsul.Consul()
class is very misleading. In my current environment, I have 4 separate Consul clusters I need to add/update KV information in. I attempted to usepython-consul
to update these, not knowing that the library is effectively an API/abstraction of the localconsul
agent. When attempting to debug, it was not clear to me that the client was connecting to the local agent instead of the intended hostnames and/or FQDNs.Documentation should be updated to reflect this more clearly and should indicate that
host=
is not intended to point to a remoteconsul
server or cluster. Thank you.The text was updated successfully, but these errors were encountered: