Log message:
sysutils/consul: Update to 1.0.7.

IMPROVEMENTS:

- build: Bumped Go version to 1.10
- agent: Blocking queries on service-specific health and catalog
  endpoints now return a per-service `X-Consul-Index` improving watch
  performance on very busy clusters.
- agent: All endpoints now respond to OPTIONS requests.
- agent: List of supported TLS cipher suites updated to include newer
  options,
- agent: WAN federation can now be disabled by setting the serf WAN
  port to -1.
- agent: Added support for specifying metadata during service
  registration.
- agent: Added a new `discover-max-stale` config option to enable
  stale requests for service discovery endpoints.
- agent: (Consul Enterprise) Added a new option to the snapshot agent
  for configuring the S3 endpoint.
- dns: Introduced a new config param to limit the number of A/AAAA
  records returned.
- dns: Upgrade vendored DNS library to pick up bugfixes and
  improvements.
- server: Updated yamux library to pick up a performance improvement.
- server: Add near=\_ip support for prepared queries
- api: Add support for GZIP compression in HTTP responses.
- api: Add `IgnoreCheckIDs` to Prepared Query definition to allow
  temporarily bypassing faulty health checks

BUG FIXES:

- agent: Fixed an issue where the coordinate update endpoint was not
  correctly parsing the ACL token.
- agent: Fixed an issue where `consul monitor` couldn't be terminated
  until the first log line is delivered
- agent: Added warnings for when a node name isn't a valid DNS name
  and when the node name, a service name or service tags would exceed
  the allowed lengths for DNS names
- agent: Added truncation of TCP DNS responses to prevent errors for
  exceeding message size limits
- agent: Added -config-format flag to validate command to specify the
  syntax that should be used for parsing the config
- agent: HTTP Checks now report the HTTP method used instead of always
  reporting as a GET
- server: Fixed an issue where the leader could miss clean up after a
  leadership transition.

Log message:
Revbump all Go packages after 1.10.1 update.

ok wiz@ for committing during freeze

Log message:
Revbump all Go packages after Go 1.10 update.

Log message:
sysutils/consul: Update to 1.0.6. Simplify Makefile.

## consul 1.0.6
- agent: Fixed a panic when using the Azure provider for retry-join.
- agent: Fixed a panic when querying Consul's DNS interface over TCP.

Log message:
sysutils/consul: Update to 1.0.5.

SECURITY:

- dns: Updated DNS vendor library to pick up bug fix in the DNS server
  where an open idle connection blocks the accept loop.

FEATURES:

- agent: Added support for gRPC health checks that probe the standard
  gRPC health endpoint.

IMPROVEMENTS:

- agent: (Consul Enterprise) The `disable_update_check` option to
  disable Checkpoint now defaults to `true`
- build: Bumped Go version to 1.9.3.

BUG FIXES:

- agent: (Consul Enterprise) Fixed an issue where the snapshot agent's
  HTTP client config was being ignored in favor of the HTTP
  command-line flags.
- agent: Fixed an issue where health checks added to services with
  tags would cause extra periodic writes to the Consul servers, even
  if nothing had changed.
- agent: Fixed several areas where reading from catalog, health, or
  agent HTTP endpoints could make unintended mofidications to Consul's
  state in a way that would cause unnecessary anti-entropy syncs back
  to the Consul servers.
- agent: Fixed an issue where Serf events for failed Consul servers
  weren't being proactively processed by the RPC router.

Log message:
Update sysutils/consul to 1.0.4.

- agent: Fixed several areas where reading from catalog, health, or
  agent HTTP endpoints could make unintended mofidications to Consul's
  state in a way that would cause unnecessary anti-entropy syncs back to
  the Consul servers

Log message:
Update sysutils/consul to 1.0.3.

SECURITY:
- ui: Patched handlebars JS to escape `=` to prevent potential XSS
  issues.

BREAKING CHANGES:
- agent: Updated Consul's HTTP server to ban all URLs containing
  non-printable characters (a bad request status will be returned for
  these cases). This affects some user-facing areas like key/value entry
  key names which are carried in URLs.

FEATURES:
- agent: Added retry-join support for Azure Virtual Machine Scale
  Sets.

IMPROVEMENTS:

- agent: Added agent-side telemetry around Catalog APIs to provide
  insight on Consul's operation from the user's perspecive.
- agent: Added the `NodeID` field back to the /v1/agent/self
  endpoint's `Config` block.
- api: Added missing `CheckID` and `Name` fields to API client's
  `AgentServiceCheck` structure so that IDs and names can be set when
  registering checks with services.

BUG FIXES:
- agent: Fixed an issue where config file symlinks were not being
  interpreted correctly.
- agent: Ignore malformed leftover service/check files and warn about
  them instead of refusing to start.
- agent: Enforce a valid port for the Serf WAN since it can't be
  disabled.
- agent: Stopped looging messages about zero RTTs when updating
  network coordinates since they are not harmful to the algorithm.
  Since we are still trying to find the root cause of these zero
  measurements, we added new metrics counters so these are still
  observable.
- server: Fixed a crash when POST-ing an empty body to the /v1/query
  endpoint.
- server: (Consul Enterprise) Fixed an issue where unhealthy servers
  were not replaced in a redundancy zone by autopilot (servers
  previously needed to be removed in order for a replacement to occur).
- ui: Added a URI escape around key/value keys so that it's not
  possible to create unexpected partial key names when entering
  characters like `?` inside a key.

Log message:
Update sysutils/consul to 1.0.2.

## 1.0.2 (December 15, 2017)

IMPROVEMENTS:

- agent: Updated Serf to activate a new feature that resizes its
  internal message broadcast queue size based on the cluster size.
- agent: Updates posener/complete library to 1.0, which allows
  autocomplete for flags after an equal sign, and simplifies
  autocomplete functions.

BUG FIXES:

- agent: Updated memberlist to pull in a fix for negative RTT
  measurements and their associated log messages about rejected
  coordinates.
- agent: Fixed an issue where node metadata specified via command line
  arguments overrode node metadata specified by configuration files
- agent: Fixed an issue with the /v1/session/create API where it
  wasn't possible to create a session without the `serfHealth` check.
- agent: Fixed an issue with anti-entropy syncing where checks for
  services with tags would cause periodic updates to the catalog, even
  when nothing had changed
- cli: Added missing support for `-base64` option to `consul kv get`
  command.
- server: Fixed an issue with KV store tombstone tracking where bin
  tracking was being confused by monotonic time information carried in
  time stamps, resulting in many unnecessary bins.
- server: (Consul Enterprise) Fixed an issue with Network Segments
  where servers would not properly flood-join each other into all
  segments.
- server: Fixed an issue where it wasn't possible to disable
  Autopilot's dead server cleanup behavior using configuration files.
- server: Removed the 60 second timeout when restoring snapshots,
  which could cause large restores to fail on slower servers.
- server: Fixed a goroutine leak during keyring operations when errors
  are encountered.

## 1.0.1 (November 20, 2017)

FEATURES:

- New Auto Join Cloud Providers: Retry join support was added for
  Aliyun (Alibaba Cloud), Digital Ocean, OpenStack, and Scaleway
- HTTP/2 Support: If TLS is enabled on a Consul agent it will
  automatically negotiate to use HTTP/2 for suitably configured
  clients accessing the client API

IMPROVEMENTS:

- agent: (Consul Enterprise) Added AWS KMS support for S3 snapshots
  using the snapshot agent.
- agent: Watches in the Consul agent can now be configured to invoke
  an HTTP endpoint instead of an executable.
- agent: Added a new `-config-format` command line option which can be
  set to `hcl` or `json` to specify the format of configuration files
- agent: DNS recursors can now be specified as go-sockaddr templates.
- agent: Serf snapshots no longer save network coordinate information.
  This enables recovery from errors upon agent restart.
- agent: Added defensive code to prevent out of range ping times from
  infecting network coordinates
- agent: The agent now warns when there are extra unparsed command
  line arguments and refuses to start.
- agent: Updated go-sockaddr library to get CoreOS route detection
  fixes and the new `mask` functionality.
- agent: Added a new `enable_agent_tls_for_checks` configuration
  option that allows HTTP health checks for services requiring 2-way
  TLS to be checked using the agent's credentials.
- agent: Made logging of health check status more uniform and moved
  log entries with full check output from DEBUG to TRACE level for
  less noise.
- build: Consul is now built with Go 1.9.2.

BUG FIXES:

- agent: Consul 1.0 shipped with an issue where `Args` was erroneously
  named `ScriptArgs` for health check definitions in the
  /v1/agent/check/register and /v1/agent/service/register APIs
- agent: Docker container checks running on Linux could get into a
  flapping state because the Docker agent seems to close the
  connection prematurely even though the body is transferred
- agent: Added new form of `consul.http.*` metrics that were
  accidentally left out of Consul 1.0.
- agent: Fixed an issue with the server manager where periodic server
  client connection rebalancing could select a failed server
- agent: IPv6 addresses without port numbers and without surrounding
  brackets are now properly handled for joins
- agent: Fixed a rare startup panic of the Consul agent related to the
  LAN Serf instance ordering with the router manager.
- agent: Added back an exception for the `snapshot_agent` config key
  so that those configs can again live alongside Consul's configs.
- dns: Fixed an issue where components of a host name near the
  datacenter could be quietly ignored
- server: Fixed an issue where performing rolling updates of Consul
  servers could result in an outage from old servers remaining in the
  cluster
- server: Fixed a deadlock where tombstone garbage collection for the
  KV store could block other KV operations, stalling writes on the
  leader.

Log message:
Update sysutils/consul to 1.0.0

SECURITY:

- Fixed an XSS issue with Consul's built-in web UI where node names
  were not being properly escaped.

BREAKING CHANGES:

- Raft Protocol Now Defaults to 3
- Config Files Require an Extension
- Deprecated Options Have Been Removed
- `statsite_prefix` Renamed to `metrics_prefix`
- `advertise_addrs` Removed
- Escaping Behavior Changed for go-discover Configs
- HTTP Verbs are Enforced in Many HTTP APIs
- Unauthorized KV Requests Return 403
- Config Section of Agent Self Endpoint has Changed
- Deprecated `configtest` Command Removed
- Undocumented Flags in `validate` Command Removed
- Metric Names Updated
- Checks Validated On Agent Startup

FEATURES:

- Support for HCL Config Files
- Support for Binding to Multiple Addresses
- Support for RFC1434 DNS TXT records
- Support for Running Subproccesses Directly Without a Shell
- Sentinel Integration

IMPROVEMENTS:

- agent: Added support to detect public IPv4 and IPv6 addresses on
  AWS.
- agent: Improved /v1/operator/raft/configuration endpoint which
  allows Consul to avoid an extra agent RPC call for the `consul
  operator raft list-peers` command.
- agent: Improved ACL system for the KV store to support list
  permissions. This behavior can be opted in. For more information,
  see the ACL Guide].
- agent: Updates miekg/dns library to later version to pick up bug
  fixes and improvements.
- agent: Added automatic retries to the RPC path, and a brief RPC
  drain time when servers leave. These changes make Consul more robust
  during graceful leaves of Consul servers, such as during upgrades, and
  help shield applications from "no leader" errors. These are configured
  with new `performance` options.
- agent: Added a new `discard_check_output` agent-level configuration
  option that can be used to trade off write load to the Consul
  servers vs. visibility of health check output. This is reloadable so
  it can be toggled without fully restarting the agent.
- api: Updated the API client to ride out network errors when
  monitoring locks and semaphores.
- build: Updated Go toolchain to version 1.9.1.
- cli: `consul lock` and `consul watch` commands will forward `TERM`
  and `KILL` signals to their child subprocess.
- cli: Added support for autocompletion].
- server: Updated BoltDB to final version 1.3.1.
- server: Improved dead member reap algorithm to fix edge cases where
  servers could get left behind.

BUG FIXES:

- agent: Fixed an issue where disabling both the http and https
  interfaces would cause a watch-related error on agent startup, even
  when no watches were defined.
- agent: Added an additional step to kill health check scripts that
  timeout on all platforms except Windows, and added a wait so that
  it's not possible to run multiple instances of the same health check
  script at the same time.
- cli: If the `consul operator raft list-peers` command encounters an
  error it will now exit with a non-zero exit code.
- cli: CLI commands will now show help for all of their arguments.
- server: Fixed an issue where the leader server could get into a
  state where it was no longer performing the periodic leader loop
  duties and unable to serve consistent reads after a barrier timeout
  error.

Full (unabridged) changelog:

  https://github.com/hashicorp/consul/blob/v1.0.0/CHANGELOG.md

Log message:
consul: Fix checksums.