« Changelog History


consul v0.6.1 Release Notes

Release Date: 2016-01-06 // over 8 years ago

  • BACKWARDS INCOMPATIBILITIES:

    • 🔒 The new -monitor-retry option to consul lock defaults to 3. This will cause the lock monitor to retry up to 3 times, waiting 1s between each attempt if it gets a 500 error from the Consul servers. For the vast majority of use cases this is desirable to prevent the lock from being given up during a brief period of Consul unavailability. If you want to get the previous default behavior you will need to set the -monitor-retry=0 option.

    👌 IMPROVEMENTS:

    • Consul is now built with Go 1.5.2
    • ➕ Added source IP address and port information to RPC-related log error messages and HTTP access logs [GH-1513] [GH-1448]
    • 🔧 API clients configured for insecure SSL now use an HTTP transport that's set up the same way as the Go default transport [GH-1526]
    • ➕ Added new per-host telemetry on DNS requests [GH-1537]
    • ➕ Added support for reaping child processes which is useful when running Consul as PID 1 in Docker containers [GH-1539]
    • ➕ Added new -ui command line and ui config option that enables a built-in Consul web UI, making deployment much simpler [GH-1543]
    • ➕ Added new -dev command line option that creates a completely in-memory standalone Consul server for development
    • ➕ Added a Solaris build, now that dependencies have been updated to support it [GH-1568]
    • ➕ Added new -try option to consul lock to allow it to timeout with an error if it doesn't acquire the lock [GH-1567]
    • ➕ Added a new -monitor-retry option to consul lock to help ride out brief periods of Consul unavailabily without causing the lock to be given up [GH-1567]

    🐛 BUG FIXES:

    • 🛠 Fixed broken settings icon in web UI [GH-1469]
    • 🛠 Fixed a web UI bug where the supplied token wasn't being passed into the internal endpoint, breaking some pages when multiple datacenters were present [GH-1071]