docker pull leapsight/bondy:0.8.8
docker pull leapsight/bondy:0.8.7
bondy.conf
options have been added to control when Bondy is allowed to start accepting client connections:startup.wait_for_store_partitions
(default: on) – Defines whether Bondy will wait for the db partitions to be initialised before continuing with initialisation. The HTTP listeners for the Admin API (not the API Gateway) are started at this point, enabling admins and tools to send requests to Bondy e.g. the Kubernetes Liveness probe can perform an HTTP GET on the /ping
resource while Bondy finishes initialising. If the value provided is off
then Bondy will not wait for the database to finish opening the store partitions and will disregard your configuration for the two following options assuming the configuration value was off
for both of them.startup.wait_for_store_hashtrees
(default: on) – Defines whether Bondy will wait for the database Active Anti-entropy hashtrees to be built before continuing with initialisation. If the value provided is off
then Bondy will not wait for the database to finish building the hashtrees and will disregard your configuration for the following option assuming the configuration value was off
for it.startup.wait_for_store_aae_exchange
(default: off) – Defines whether Bondy will wait for the first Active Anti-entropy exchange to be finished before continuing with initialisation. All HTTP and TCP listeners will be started here enabling clients to connect via WAMP or HTTP (API Gateway).private_keys
property to be present in the body.com.leapsight.bondy
Admin Realm is now configurable via the Security JSON specification fileplum_db
versionoptions
and details
and drops any property that is not part of the protocol. _my_property
instead.docker pull leapsight/bondy:0.8.6
bondy_peer_discovery_dns_agent
) which uses DNS srv
to lookup other Bondy nodes. Tested to work with Kubernetes DNS.bondy.conf
file (in addition to the WAMP and HTTP/REST APIs).