Today we are releasing Consul 0.9 which includes a number of improvements, bug fixes, and features. There are some important backward incompatibilities in this release that are easy to adjust for as you deploy, so please be sure to read the 0.9 upgrade guide for details before you upgrade.
Consul 0.9.0 highlights include:
consul catalogcommand for reading datacenters, nodes, and services from the catalog.
enable_script_checksconfiguration option was added and defaults to
false, which means that operators must now opt-in in order to allow Consul agents to execute scripts. This provides a more secure configuration for Consul, and encourages enabling ACLs at the same time as script checks.
block_endpointsconfiguration option that allows blocking HTTP endpoints by prefix. This allows operators to completely disallow access to specific endpoints on a given agent.
There are lots of additional improvements in the 0.9 release — please review the v0.9.0 changelog for a detailed list of changes. Be sure to read the 0.9 upgrade guide as well. Consul 0.9.0 is also available in Consul Enterprise Pro and Consul Enterprise Premium.
HashiCorp Consul Service (HCS) on Azure can be launched directly from the Azure Portal, but you can also launch HCS using Terraform Cloud.
Get Terraform, Packer, Vault, Consul, and Nomad up and running even faster on macOS with our new official Homebrew Tap.
We are pleased to announce the availability of the HashiCorp Consul Service (HCS) on Azure Production tier. The new offering enables a user to deploy production grade Consul clusters directly from the Microsoft Azure portal.