Migrating to Consul Connect ent-changelog-1.17.0
Version ent-changelog-1.17.0 introduces 2 breaking changes. This guide details how to update your code.
Released: 12/2/2025
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
RaftLeaderTransferapiaudit-logginggolang.org/x/netgoogle.golang.org/grpcenvoyCatalog resource controllersMesh resource controllersAuth resource controllersV2 ProtobufsCheckRegisterOptsServiceRegisterOptsTokenServiceResolverConfigEntry.RequestTimeoutBreaking Changes
●Issue #1
api: RaftLeaderTransfer now requires an id string. To maintain old behavior, specify an empty string for the id.
●Issue #2
(Enterprise only) audit-logging: Timestamp based filename is now only allowed on rotation; initially the filename will be just file.json.
Migration Steps
- 1If using `RaftLeaderTransfer`, ensure you provide an `id` string. If you need to maintain the old behavior, pass an empty string for the ID.
- 2Review the limitations of the v2 Catalog API feature preview if considering its use (not supported with client agents, cannot run concurrently with v1, not supported in current UI or HCP Consul for multi-port services).
Release Summary
This release introduces the feature preview of Consul's v2 Catalog and Resource API, alongside significant security updates addressing multiple CVEs. It also adds extensive new features related to ACL templating and API Gateway capabilities.
Need More Details?
View the full release notes and all changes for Consul Connect ent-changelog-1.17.0.
View Full Changelog