![[BACK]](/icons/back.gif){kind=icon}
Up to [cvs.NetBSD.org] / pkgsrc / sysutils / consul
Request diff between arbitrary revisions
Default branch: MAIN
Current tag: pkgsrc-2017Q4
Revision 1.24 / (download) - annotate - [select for diffs], Mon Dec 18 13:54:44 2017 UTC (6 years, 4 months ago) by fhajny
Branch: MAIN
CVS Tags: pkgsrc-2017Q4-base,
pkgsrc-2017Q4
Changes since 1.23: +2 -2
lines
Diff to previous 1.23 (colored)
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.