auth0_client resource: allowed_origins and web_origins fields don't apply removal

[seth-peters-apiture]

Checklist

• I have looked into the README and have not found a suitable solution or answer.
• I have looked into the documentation and have not found a suitable solution or answer.
• I have searched the issues and have not found a suitable solution or answer.
• I have upgraded to the latest version of this provider and the issue still persists.
• I have searched the Auth0 Community forums and have not found a suitable solution or answer.
• I agree to the terms within the Auth0 Code of Conduct.

Description

When updating an auth0_client resource to change cross_origin_auth from true to false, remove allowed_origins, and remove web_origins, only the cross_origin_auth change is successfully applied.

The terraform apply output shows that the change is successful, but on successive plans and in the auth0 console it can be seen that the allowed_origins and web_origins changes are never applied.

Expectation

The expected changes shown in the plan should be applied when running terraform apply.

Reproduction

1. Create an auth0_client resource that has cross_origin_auth set to true and has at least one url in the allowed_origins and web_origins lists with terraform.
2. Update the terraform auth0_client resource code to set cross_origin_auth to false, set allowed_origins to null or remove the field entirely, and set web_origins to null or remove the field entirely.
3. Run terraform apply
4. The changes will say they applied
5. Either run terraform plan again, or check in the auth0 console. The change will not have been applied.

Auth0 Terraform Provider version

1.9.1

Terraform version

1.7.4

[seth-peters-apiture]

I'm also seeing a similar issue with the domain_aliases. Removing the field does not cause terraform to see the change and no change is applied.

[jacobkretz-bf]

I'm also seeing this with the refresh token settings as well.