●Change8

Migrating to Consul Connect ent-changelog-1.19.0

Version ent-changelog-1.19.0 introduces 1 breaking change. This guide details how to update your code.

Released: 12/2/2025

1
Breaking Changes
2
Migration Steps
5
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

telemetry metrics (state store usage)dns serverapi-gateway listener TLS configurationsnapshot agent configurationconsul snapshot decode CLI

Breaking Changes

●Issue #1

Telemetry state store usage metrics with a double `consul` element in the metric name have been removed. Consumers must use the same metric without the second `consul` (e.g., use `consul.state.config_entries` instead of `consul.consul.state.config_entries`).

Migration Steps

  1. 1
    If you rely on telemetry metrics named with a double `consul` element (e.g., `consul.consul.state.config_entries`), update your monitoring to use the metric name without the second `consul` (e.g., `consul.state.config_entries`).
  2. 2
    For snapshot agent configuration (Enterprise only), migrate top-level snapshot destinations (`local_storage`, etc.) to use the `backup_destinations` config object.

Release Summary

This release introduces a refactored, v1/v2 Catalog compatible DNS server by default and adds support for filesystem-based TLS certificates for API Gateways. It also addresses security vulnerabilities via dependency upgrades and modifies telemetry metric naming conventions.

Need More Details?

View the full release notes and all changes for Consul Connect ent-changelog-1.19.0.

View Full Changelog