e5faa53ead
etcd changed API version from v3alpha to v3beta, then v3, and because of transition available api versions are different according to the etcd server available. This change implements the mechanism to detect the current api version according to the etcd version obtained via the version API. Discovery is executed at the first request and the result is stored. Closes-Bug: #2043810 Change-Id: I08bc429dd8c59e5d2b6e62f8f48afd78a116fbea
12 lines
591 B
YAML
12 lines
591 B
YAML
---
|
|
features:
|
|
- |
|
|
The ``Etcd3Client`` class now automatically discovers available API version
|
|
and determines the api path. It detects the appropriate api path before
|
|
sending its first request, and the api path is reused for its subsequent
|
|
requests. The client instance needs to be recreated, or the service using
|
|
the instance needs to be restarted, after its backend etcd server is
|
|
upgraded, so that the new api path is detected. The detection is skipped
|
|
if the `api_path` argument is set when creating a class or
|
|
the `ETCD3GW_API_PATH` environment is set.
|