Changelog¶
2.0.1 - 2017-07-20¶
- Disable SNI related SSL warnings from urllib3 when running the CLI tool on Python 2.6. This can still be enabled
with the
--enable-platform-warnings
switch if desired by the caller.
2.0.0 - 2017-06-29¶
- Breaking change - The Warthog library now only supports v3 of the A10 load balancer REST API. If you need to interact with a load balancer that uses v2 of the A10 REST API you are advised to use Warthog 1.1.0.
- Breaking change - Removed the
wait_interval
parameter fromwarthog.client.WarthogClient
. This setting can now be specified directly for calls toenable_node
anddisable_node
methods. - Breaking change - Removed
WarthogAuthCloseError
,WarthogNodeDisableError
,WarthogNodeEnableError
. Places where these exceptions were previously raised will now raisewarthog.exceptions.WarthogApiError
. - Network operations are now retried on transient errors per #17.
1.999.2 - 2017-06-28¶
Note
This version is only meant to be used internally at SmarterTravel as a transition step between two load balancers. As such, it is not available on PyPI.
- Rename
warthog.core3
towarthog.core
- Remove deprecated exceptions in
warthog.exceptions
:WarthogAuthCloseError
,WarthogNodeDisableError
,WarthogNodeEnableError
.
1.999.1 - 2017-04-06¶
Note
This version is only meant to be used internally at SmarterTravel as a transition step between two load balancers. As such, it is not available on PyPI.
- Add support for new Python SSL constant
PROTOCOL_TLS
to allow negotiation of SSL versions between the client and server.
1.999.0 - 2017-04-05¶
Note
This version is only meant to be used internally at SmarterTravel as a transition step between two load balancers. As such, it is not available on PyPI.
1.1.0 - 2016-01-21¶
- Disable
InsecurePlatformWarning
from urllib3 by default for the CLI client since this makes it unusable CentOS / Red Hat 6. This warning can be re-enabled for the CLI client with the--enable-platform-warning
flag. Note that this does not change the behavior of the Warthog library at all, only the CLI client. Fixes #5.
1.0.0 - 2015-12-21¶
- This is the first stable release of Warthog. From this point on, all breaking changes will only
be made in major version releases. This release is functionally the same as the
0.10.0
release.
0.10.0 - 2015-10-05¶
- Add option to
warthog.client.WarthogClient
to allow alternate SSL or TLS versions to be used easily. Fixes #6. - Breaking change - Passing a
None
value towarthog.transport.get_transport_factory()
for thessl_version
parameter will now use the Warthog library default (TLSv1) instead of letting requests/urllib3 pick the default. - Add support for specifying an optional
ssl_version
parameter in INI configuration files. Fixes #4. - Change
verify
to be optional in INI configuration files.
0.9.1 - 2015-08-07¶
- Fix bug where a config file needed to be specified by the CLI client even when not required (such as when displaying help). Fixes #3.
0.9.0 - 2015-06-04¶
- Replace examples documentation with more in depth usage guide (Usage).
- Add documentation for performing a release of the library (Releasing).
- Move enabling/disabling certificate verification to the
warthog.client.WarthogClient
class so that using self-signed certificates is less of a hassle and requires less code.
0.8.3 - 2015-03-18¶
- Dependency on requests updated to version 2.6.0.
- Packaging fixes (use
twine
for uploads to PyPI, stop using the setup.pyregister
command). - Minor documentation updates.
0.8.2 - 2015-02-09¶
- Small documentation fixes.
- Add project logo to documentation.
- Dependency on requests updated to version 2.5.1.
0.8.1 - 2014-12-22¶
- Fixed small documentation issues and changed change log dates.
0.8.0 - 2014-12-22¶
- Breaking change - Changed errors raised by
warthog.config.WarthogConfigLoader
to be subclasses ofwarthog.exceptions.WarthogConfigError
instead of using errors from the standard library (ValueError
,IOError
,RuntimeError
). - Breaking change - Removed the
warthog.client.WarthogClient.disabled_context
context manager method since the level of abstraction didn’t match the rest of the methods in the client. - Breaking change - Removed all command classes in
warthog.core
from the public API (warthog.api
). Users wishing to use them may do so at their own risk. - Change all server-specific exceptions to be based on
warthog.exceptions.WarthogNodeError
. - Improve error handling for CLI client when the configuration file contains an invalid load balancer host (or port, etc.).
- Bundled 3rd-party libs moved to the
warthog.packages
package. - Dependency on requests updated to version 2.5.0.
0.7.0 - 2014-11-24¶
- Breaking change - Changed error hierarchy so that all errors related to interacting
with the load balancer now extend from
warthog.exceptions.WarthogApiError
. The root error classwarthog.exceptions.WarthogError
no longer contains any functionality specific to making API requests to the load balancer.
0.6.0 - 2014-11-20¶
- Breaking change - Removed
warthog.config.WarthogConfigLoader.parse_configuration()
method and split the functionality into two new methods. Additionally, the class is now thread safe. - Renamed “Usage” documentation section to “Examples”.
0.5.0 - 2014-11-03¶
- Breaking change - Changed all command
.send()
methods inwarthog.core
to not take any arguments to given them a consistent interface. - Examples documentation improvements.
- Various code quality improvements.
0.4.2 - 2014-10-29¶
- Documentation improvements (Development).
- Test coverage improvements in
warthog.cli
.
0.4.1 - 2014-10-23¶
- Added CLI tool for using the Warthog Client. See CLI Tool.
- Added
warthog.client.WarthogClient.get_connections()
method for getting the number of active connections to a server. - Added Exceptions in
warthog.exceptions
to the public api inwarthog.api
. - Added config parsing module
warthog.config
and add it to the public api inwarthog.api
.
0.3.1 - 2014-10-17¶
- Changed
setup.py
script to not require setuptools.
0.3.0 - 2014-10-16¶
- Added Install documentation.
- Changed authentication request (
warthog.core.SessionStartCommand
) to usePOST
instead ofGET
though there doesn’t seem to be any actual difference as far as the load balancer API is concerned.
0.2.0 - 2014-10-14¶
0.1.0 - 2014-10-11¶
- Initial release