-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Faraday 2.0.0 breaks diplomat #223
Comments
@fquesnel Do you think you might provide a patch to support both? |
@fquesnel Issue fixed, released version 2.6.1 that enforce Faraday < 2.x Thanks for reporting the issue |
@pierresouchay thank you for quickly fixing the issue 🙂 |
Since https://github.com/lostisland/faraday/blob/main/CHANGELOG.md#201-2022-01-05 has been released with lostisland/faraday#1366, diplomat can now rely again on Faraday 2.0.1+ |
* 2022-07-28 Dashkevych Oleksii (@Jesterovskiy) Add option to filter services Pass a `:filter` hash as an option to `Diplomat::Service.get` to filter https://www.consul.io/api-docs/catalog#filtering-1. * Relax dependency on Faraday, so 2.x versions can be used again (#223)
In short: faraday 2.0.0 now requires to specify an adapter.
Currently, calling Datacenter::get results in the following error message:
Example stacktrace:
Known mitigation: use faraday <= 1.8.0
The text was updated successfully, but these errors were encountered: