blob: d0ee35bdbfef2a7ca58b84ba793ea4fe6ed70a21 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
# Change Log
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](http://keepachangelog.com/)
and this project adheres to [Semantic Versioning](http://semver.org/).
## [2.1.1] - 04/27/2020
* Bug fix DCAEGEN2-2213 ConnectionError exception is lost when CBSUnreachable is raised
## [2.1.0] - 6/24/2019
* Add support for connecting to the CBS if it is running as HTTPS instead of HTTP
## [2.0.0] - 6/19/2019
* The env variable CONFIG_BINDING_SERVICE now has a different meaning per DCAEGEN2-1537. Specifically this variable now holds a resolvable hostname for the CBS, rather than a consul lookup key
* Since the API was broken anyway, the decision not to throw an exception was revisted and overturned. This was causing problems for some users, who were getting `{}` back in their configuration, but without knowing why; either the config wasn't set up, the config was set but as `{}`, or the CBS being unreachable altogether. This client library now throws native python exceptions, rather than logging and returning `{}`. The application client code can handle the exceptions, and retry if they choose.
* Add more tests, move fixtures to conftest
* Move exceptions to own module
## [1.0.4]
* Allow the CBS to be registered in Consul under a different name than "config_binding_service"; instead read from the already-set ENV variable CONFIG_BINDING_SERVICE
## [1.0.3]
* Fix an issue caused by flake8 upgrading
## [1.0.2]
* Refactor some code, PEP8 compliance
* Add flake8 to tox
## [1.0.1]
* [Sadly, Missing]
## [1.0.0]
* Depend on the CBS 2.0.0 API
* Add new endpoint for getting all
## [0.0.5]
* Dont pin requests version
## [0.0.3]
* Changelog started
* Unit test suite created
* Current test coverage = 82%
|
