We are pleased to announce the release of Consul v0.7.3. This release includes several new features, improvements, and bug fixes.
Consul v0.7.3 includes a number of exciting new features and improvements:
KV Import/Export CLI:
consul kv exportand
consul kv importcan be used to move parts of the KV tree between disconnected consul clusters, using JSON as the intermediate representation.
Node Metadata: Support for assigning user-defined metadata key/value pairs to nodes has been added. This can be viewed when looking up node info, and can be used to filter the results of various catalog and health endpoints.
Node Identifiers: Consul agents can now be configured with a unique identifier, or they will generate one at startup that will persist across agent restarts. This identifier is designed to represent a node across all time, even if the name or address of the node changes. Identifiers are currently only exposed in node-related endpoints, but they will be used in future versions of Consul to help manage Consul servers and the Raft quorum in a more robust manner, as the quorum is currently tracked via addresses, which can change.
Improved Blocking Queries: Consul's blocking query implementation was improved to provide a much more fine-grained mechanism for detecting changes. For example, in previous versions of Consul blocking to wait on a change to a specific service would result in a wake up if any service changed. Now, wake ups are scoped to the specific service being watched, if possible. This support has been added to all endpoints that support blocking queries, nothing new is required to take advantage of this feature.
GCE auto-discovery: New
-retry-join-gceconfiguration options added to allow bootstrapping by automatically discovering Google Cloud instances with a given tag at startup.
Please review the v0.7.3 changelog for a detailed list of changes.