1.0.3

changelog

• Updated docs
• disable_redirects removed from service checks

1.0.1

changelog

• 🐞 Fixes the observation connection feature that created multiple tasks to reconnect with the consul leader if the leader ID changed.

1.0.0

changelog

• Updated docs
• Updated CLI
• Internal code refactored

v0.2.5

changelog

• fix connection failure when consul's leader running locally

v0.2.4

Changelog

• Fixed consul connection on cluster mode.
  Now Consul's connection will occur with the leader instance as well the reconnection flow.

v0.2.3

Changelog

• Bug fix on aioclient reconnect method.

v0.2.2

Changelog

• new flow to reconnect on Consul in case of unavailability.

v0.2.1

Changelog

• find_service method now return a dict on format:

{'node': 'a60a5b512b4f', 'address': '127.0.0.1', 'service_id': 'consul', 'service_name': 'consul', 'service_port': 8300}

If more than one instance exists round robin will be set by default, or the method can be changed specifying a different option, for example:

dc.find_service('consul', method='random')

• find_services method returns a list on format:

[{'node': 'a60a5b512b4f-0', 'address': '127.0.0.1', 'service_id': 'consul', 'service_name': 'consul', 'service_port': 8300},{'node': 'a60a5b512b4f-1', 'address': '127.0.0.1', 'service_id': 'consul', 'service_name': 'consul', 'service_port': 8300}]

• the default timeout to reconnect that will be use by method consul_is_healty now it's 30 seconds and his value can be changed though the environment variable DEFAULT_TIMEOUT.

For aioclient only, now it's necessary create a specific task if you wish reconnect on consul in case of unavailability of service. See the examples related on file README.md or examples folder for more details.

v0.1.3

First public release.