multiple enabled_clients in a connection causes (un-needed) update about terraform-provider-auth0

[alexkappa]

Hi @domg123 thanks for submitting this bug report.

Could you show the terraform config you used? How can we reproduce the problem?

Cheers!

[domg123]

Hi, sorry for the delay.

So, attached is a file you can use to recreate the issue.

multiple_client_issue.txt

Steps. (assuming valid provider available)

1. rename to a tf file
2. terraform apply
3. terraform plan

At step 3, despite no changes, you will frequently see the output below. If you don't get it the first time, remove the file, apply again to delete, and try again.

====
`An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
~ update in-place

Terraform will perform the following actions:

~ auth0_connection.myconnection
enabled_clients.0: "7I9NL7cPUoIPXUdJp2xUgEeoVivzRD9y" => "PtQinZ36JAoTebouQ5h339hhP0SqLPqg"
enabled_clients.1: "PtQinZ36JAoTebouQ5h339hhP0SqLPqg" => "wEQaqNp1rNRyIq107kY4v8wzu2ZN5Hvi"
enabled_clients.2: "Wn97VIpP5IMpmoeGUyrt9l8hQiU2RMFf" => "7I9NL7cPUoIPXUdJp2xUgEeoVivzRD9y"
enabled_clients.3: "wEQaqNp1rNRyIq107kY4v8wzu2ZN5Hvi" => "Wn97VIpP5IMpmoeGUyrt9l8hQiU2RMFf"
`

[alexkappa]

Hi @domg123, I believe the bug was due to the ListType in Terraform being ordered and the result from Auth0 having a different order.

It could be solved by ordering the list of clients differently, but honestly, I find it a bit weird to resort to such a solution. Can you please test again with the latest release and try to re-order the items in the list?

I will continue to research the topic in hopes to find something better.

[laurentdutheil]

might be fixed with #95

[github-actions]

This issue is stale because it has been open 30 days with no activity.
Stale issues will be closed after 5 days if no action is taken. If you
think this issue should not be closed, remove the stale label.