Auth0 is deprecating the enabled_clients field on a connection object in the context of getting/updating connections, see deprecation note.
We see depnote events in the logstream for a production tenant, not tied to a terraform release.
Since the deprecation of the enabled_clients parameter for the aforementioned endpoints took effect, it appears that the Terraform documentation has been adjusted accordingly by adding the auth0_connection_clients and auth_connection_clientresources in order to manage the clients.
However, I understand you confusion that enabled_clients does not appear as a parameter for the auth0_connection resource, even though it is still available within the Management API one.
I have yet to receive any updates regarding the matter, however, are you able to use enabled_clients when creating a connection or does it throw an error? If you receive an error, you will need to manage the clients using the resources managed above.
If I can help with any other questions, let me know!
The Auth0 Deploy CLI / Auth0 Terraform Provider do not require changes to how connections and respective clients are represented in their data model. You must use the latest available version to guarantee the tool uses the dedicated endpoints.
This for Auth0 Terraform Provider: 1.29.0+.
Given that we are on a newer version, I don’t understand why we see the depnote.