// Hashicorp Blog
We recently released HashiCorp Consul 1.0.7 which includes a number of features and improvements.
Here are some highlights from Consul 1.0.7:
- Service metadata - You can now set key/value data during service registration that will be accessible during the full lifecycle of the service. Service metadata can be used to specify information such as the version of the service, weights or priorities for external load balancing, or other static information that may have previously been stored in the K/V datastore that should be attached to the service directly.
- GZIP compression in HTTP responses - All HTTP API endpoints now support compression when requested by the client. This can improve performance when dealing with large API responses. Depending on your client this may be requested by default (such as a web browser) with the
Accept-Encoding: gzipheader. Additionally, HTTP endpoints now respond to OPTIONS requests.
near=_ipsupport for prepared queries - Prepared queries now support a special
?near=_iplookup to sort results by proximity to an IP similar to how
?near=_agentsorts by proximity to the local agent (using network coordinates). This can be used in conjunction with Consul ESM for looking up results near an external service.
In addition to these new features, there are a handful of smaller bug fixes and improvements. Please review the v1.0.7 changelog for a detailed list of changes. Due to a change made for blocking queries on service-specific health and catalog endpoints, clients relying on undocumented behavior of
X-Consul-Index in blocking queries may be affected. Read the 1.0.7 upgrade guide for more information.
As always, please test in an isolated environment before upgrading. Consul 1.0.7 is also available in Consul Enterprise Pro and Consul Enterprise Premium.
A special thank you to our active community members who have been invaluable in adding new features, reporting bugs, and improving the documentation for Consul.
Read in my feedly