Auth0-deploy-cli uses deprecated `enabled_clients` fields

Product Feedback
,
1

Issue: auth0-deploy-cli uses deprecated enabled_clients field

Description: My organization uses auth0-deploy-cli to deploy Auth0 tenant configuration changes with a CD/CI pipeline. For some time, my organization receives a warning that some of our tenants use the deprecated enabled-clients field: “The enabled_clients field is deprecated and will soon no longer be supported in (GET - /api/v2/connections) and (GET/PATCH - /api/v2/connections/{id}) Management API endpoints.”

After investigating, we found out that the caller that triggers this error is auth0-deploy-cli. This happens both when exporting the configuration and when importing it with the latest version 8.35.0, and it also happens with an older version of auth0-deploy-cli. For now, if we want to avoid the CD/CI pipeline breaking in July, it seems that our only option is to skip the connections in the automated deploy and manage these manually. Do you have plans on changing the handling of enabled_clients in future auth0-deploy-cli releases?

The detailed error message is (relevant properties only):

{
“date”: “2026-05-26T05:47:23.986Z”,
“type”: “depnote”,
“description”: “Legacy Management of Connection’s Enabled Clients: This feature is being deprecated. Please see details.feature of this log for more information.”,
“user_agent”: “Other 0.0.0 / Other 0.0.0”,
“details”: {
“description”: “The enabled_clients field is deprecated when retrieving (GET) or updating (PATCH) connections and will stop being accessible or modifiable. Instead, use the dedicated client management endpoints (GET - /api/v2/connections/{id}/clients) and (PATCH - /api/v2/connections/{id}/clients).”,
“request”: {
“userAgent”: “deploy-cli/8.35.0 (node.js/20.20.0)”,
“path”: “/api/v2/connections/{id}”,
“method”: “get”
},
“response”: {}
},
“auth0_client”: {
“name”: “node-auth0”,
“version”: “5.10.0”,
“env”: {
“node”: “20.20.0”
}
},
}