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
In some cases you might want to have multiple ::Diplomat::RestClient at
the same time but with different configurations. Using a static config
forbid this kind of uses.
Possible use cases:
- Multiple clients with different Tokens
- Multiple clients pointing to different Consul cluster
This commit should fixWeAreFarmGeek#159
In some cases you might want to have multiple ::Diplomat::RestClient at
the same time but with different configurations. Using a static config
forbid this kind of uses.
Possible use cases:
- Multiple clients with different Tokens
- Multiple clients pointing to different Consul cluster
This commit should fixWeAreFarmGeek#159
Annih
added a commit
to criteo-forks/diplomat
that referenced
this issue
Mar 3, 2018
In some cases you might want to have multiple ::Diplomat::RestClient at
the same time but with different configurations. Using a static config
forbid this kind of uses.
Possible use cases:
- Multiple clients with different Tokens
- Multiple clients pointing to different Consul cluster
This commit should fixWeAreFarmGeek#159
(Not a very good issue description, feel free to rename it)
Let's consider the following scenario:
a second piece of code (different library or maybe chef cookbook) defines another consul token (B).
the first piece of code later calls diplomat assuming the token is A.
In this case, you might encounter an unauthorized error.
The issue is that Diplomat::Configuration is static. In an ideal world we should be able to do:
What do you think?
The text was updated successfully, but these errors were encountered: