search

jippi / hashi-ui

A modern user interface for @hashicorp Consul & Nomad
MIT License
1.23k stars 148 forks source link

Bump github.com/hashicorp/consul/api from 1.9.1 to 1.14.0 in /backend #732

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps github.com/hashicorp/consul/api from 1.9.1 to 1.14.0.

Release notes

Sourced from github.com/hashicorp/consul/api's releases.

v1.13.0

1.13.0 (August 9, 2022)

BREAKING CHANGES:

  • config-entry: Exporting a specific service name across all namespace is invalid.
  • connect: Removes support for Envoy 1.19 [GH-13807]
  • telemetry: config flag telemetry { disable_compat_1.9 = (true|false) } has been removed. Before upgrading you should remove this flag from your config if the flag is being used. [GH-13532]

FEATURES:

  • Cluster Peering (Beta) This version adds a new model to federate Consul clusters for both service mesh and traditional service discovery. Cluster peering allows for service interconnectivity with looser coupling than the existing WAN federation. For more information refer to the cluster peering documentation.
  • Transparent proxying through terminating gateways This version adds egress traffic control to destinations outside of Consul's catalog, such as APIs on the public internet. Transparent proxies can dial destinations defined in service-defaults and have the traffic routed through terminating gateways. For more information refer to the terminating gateway documentation.
  • acl: It is now possible to login and logout using the gRPC API [GH-12935]
  • agent: Added information about build date alongside other version information for Consul. Extended /agent/self endpoint and consul version commands to report this. Agent also reports build date in log on startup. [GH-13357]
  • ca: Leaf certificates can now be obtained via the gRPC API: Sign [GH-12787]
  • checks: add UDP health checks.. [GH-12722]
  • cli: A new flag for config delete to delete a config entry in a valid config file, e.g., config delete -filename intention-allow.hcl [GH-13677]
  • connect: Adds a new destination field to the service-default config entry that allows routing egress traffic through a terminating gateway in transparent proxy mode without modifying the catalog. [GH-13613]
  • grpc: New gRPC endpoint to return envoy bootstrap parameters. [GH-12825]
  • grpc: New gRPC endpoint to return envoy bootstrap parameters. [GH-1717]
  • grpc: New gRPC service and endpoint to return the list of supported consul dataplane features [GH-12695]
  • server: broadcast the public grpc port using lan serf and update the consul service in the catalog with the same data [GH-13687]
  • streaming: Added topic that can be used to consume updates about the list of services in a datacenter [GH-13722]
  • streaming: Added topics for ingress-gateway, mesh, service-intentions and service-resolver config entry events. [GH-13658]

IMPROVEMENTS:

  • api: merge-central-config query parameter support added to /catalog/node-services/:node-name API, to view a fully resolved service definition (especially when not written into the catalog that way). [GH-13450]
  • api: merge-central-config query parameter support added to /catalog/node-services/:node-name API, to view a fully resolved service definition (especially when not written into the catalog that way). [GH-2046]
  • api: merge-central-config query parameter support added to some catalog and health endpoints to view a fully resolved service definition (especially when not written into the catalog that way). [GH-13001]
  • api: add the ability to specify a path prefix for when consul is behind a reverse proxy or API gateway [GH-12914]
  • catalog: Add per-node indexes to reduce watchset firing for unrelated nodes and services. [GH-12399]
  • connect: add validation to ensure connect native services have a port or socketpath specified on catalog registration. This was the only missing piece to ensure all mesh services are validated for a port (or socketpath) specification on catalog registration. [GH-12881]
  • ui: Add new CopyableCode component and use it in certain pre-existing areas [GH-13686]
  • acl: Clarify node/service identities must be lowercase [GH-12807]
  • command: Add support for enabling TLS in the Envoy Prometheus endpoint via the consul connect envoy command. Adds the -prometheus-ca-file, -prometheus-ca-path, -prometheus-cert-file and -prometheus-key-file flags. [GH-13481]
  • connect: Add Envoy 1.23.0 to support matrix [GH-13807]
  • connect: Added a max_inbound_connections setting to service-defaults for limiting the number of concurrent inbound connections to each service instance. [GH-13143]
  • grpc: Add a new ServerDiscovery.WatchServers gRPC endpoint for being notified when the set of ready servers has changed. [GH-12819]
  • telemetry: Added consul.raft.thread.main.saturation and consul.raft.thread.fsm.saturation metrics to measure approximate saturation of the Raft goroutines [GH-12865]
  • ui: removed external dependencies for serving UI assets in favor of Go's native embed capabilities [GH-10996]
  • ui: upgrade ember-composable-helpers to v5.x [GH-13394]

BUG FIXES:

... (truncated)

Changelog

Sourced from github.com/hashicorp/consul/api's changelog.

1.12.3 (July 13, 2022)

IMPROVEMENTS:

  • Support Vault namespaces in Connect CA by adding RootPKINamespace and IntermediatePKINamespace fields to the config. [GH-12904]
  • connect: Update Envoy support matrix to latest patch releases (1.22.2, 1.21.3, 1.20.4, 1.19.5) [GH-13431]
  • dns: Added support for specifying admin partition in node lookups. [GH-13421]
  • telemetry: Added a consul.server.isLeader metric to track if a server is a leader or not. [GH-13304]

BUG FIXES:

  • agent: Fixed a bug in HTTP handlers where URLs were being decoded twice [GH-13256]
  • deps: Update go-grpc/grpc, resolving connection memory leak [GH-13051]
  • fix a bug that caused an error when creating grpc or http2 ingress gateway listeners with multiple services [GH-13127]
  • ui: Fix incorrect text on certain page empty states [GH-13409]
  • xds: Fix a bug that resulted in Lambda services not using the payload-passthrough option as expected. [GH-13607]
  • xds: Fix a bug where terminating gateway upstream clusters weren't configured properly when the service protocol was http2. [GH-13699]

1.11.7 (July 13, 2022)

IMPROVEMENTS:

  • connect: Update supported Envoy versions to 1.20.4, 1.19.5, 1.18.6, 1.17.4 [GH-13434]

BUG FIXES:

  • agent: Fixed a bug in HTTP handlers where URLs were being decoded twice [GH-13265]
  • fix a bug that caused an error when creating grpc or http2 ingress gateway listeners with multiple services [GH-13127]
  • xds: Fix a bug where terminating gateway upstream clusters weren't configured properly when the service protocol was http2. [GH-13699]

1.10.12 (July 13, 2022)

BUG FIXES:

  • agent: Fixed a bug in HTTP handlers where URLs were being decoded twice [GH-13264]
  • fix a bug that caused an error when creating grpc or http2 ingress gateway listeners with multiple services [GH-13127]

1.13.0-alpha2 (June 21, 2022)

IMPROVEMENTS:

  • api: merge-central-config query parameter support added to /catalog/node-services/:node-name API, to view a fully resolved service definition (especially when not written into the catalog that way). [GH-13450]
  • connect: Update Envoy support matrix to latest patch releases (1.22.2, 1.21.3, 1.20.4, 1.19.5) [GH-13431]

BUG FIXES:

  • ui: Fix incorrect text on certain page empty states [GH-13409]

1.13.0-alpha1 (June 15, 2022)

... (truncated)

Commits
  • 8ea7180 Add changelog entry for new transparent proxying feature
  • 4541171 Denote Cluster Peering as 'Beta' in changelog
  • b4ab942 Consul 1.13.0
  • 293d3c5 Backport of Restructure Api Gateway Documentation into release/1.13.x (#14046)
  • 425dd7e backport of commit e43f1036eba9c8a57bdf94c67df4ce313f3286d0 (#14069)
  • 1b51e58 backport of commit 9c6d3fd332709aed81608b473745c9e0d11d5b86 (#14068)
  • 4f0f43e Backport of add config parameters doc for destination in service-defaults int...
  • ceff925 Backport of Fix wildcard picking up services it shouldn't for ingress/termina...
  • 0c8e849 backport of commit 4c1577845b10326b2787c49bd2f1ba5ab1c60b9b (#14059)
  • fa2135d backport of commit f74e6cb1b51cb11d5ac3b57a54ed3dbb3e18fc71 (#14058)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 2 years ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.