Bump github.com/hashicorp/consul/api from 1.12.0 to 1.14.0

[dependabot]

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

Release notes

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

v1.13.1

1.13.1 (August 12, 2022)

BUG FIXES:

• agent: Fixed a compatibility issue when restoring snapshots from pre-1.13.0 versions of Consul [GH-14107] [GH-14149]
• connect: Fixed some spurious issues during peering establishment when a follower is dialed [GH-14119]

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.

... (truncated)

Changelog

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

1.13.1 (August 11, 2022)

BUG FIXES:

• agent: Fixed a compatibility issue when restoring snapshots from pre-1.13.0 versions of Consul [GH-14107] [GH-14149]
• connect: Fixed some spurious issues during peering establishment when a follower is dialed [GH-14119]

1.12.4 (August 11, 2022)

BUG FIXES:

• cli: when acl token read is used with the -self and -expanded flags, return an error instead of panicking [GH-13787]
• connect: Fixed a goroutine/memory leak that would occur when using the ingress gateway. [GH-13847]
• connect: Ingress gateways with a wildcard service entry should no longer pick up non-connect services as upstreams. connect: Terminating gateways with a wildcard service entry should no longer pick up connect services as upstreams. [GH-13958]
• ui: Fixes an issue where client side validation errors were not showing in certain areas [GH-14021]

1.11.8 (August 11, 2022)

BUG FIXES:

• connect: Fixed a goroutine/memory leak that would occur when using the ingress gateway. [GH-13847]
• connect: Ingress gateways with a wildcard service entry should no longer pick up non-connect services as upstreams. connect: Terminating gateways with a wildcard service entry should no longer pick up connect services as upstreams. [GH-13958]

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]

... (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 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)

[codecov-commenter]

Codecov Report

❗ No coverage uploaded for pull request base (main@0db713b). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #35   +/-   ##
=======================================
  Coverage        ?   35.05%           
=======================================
  Files           ?        2           
  Lines           ?      194           
  Branches        ?        0           
=======================================
  Hits            ?       68           
  Misses          ?      119           
  Partials        ?        7           

Flag	Coverage Δ
attache	35.05% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[dependabot]

Superseded by #39.