This repository has been archived by the owner on Mar 8, 2022. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 149
Rename scope on Resource Server causes 400 error #197
Comments
Actually it's just a modification of the description. The value remains the same yet the provider wants to delete/create. |
@nitrag which version of the provider were you using? |
@alexkappa |
I could verify the bug and worked on a fix which should be available soon. Keep an eye for 0.9.0 here https://releases.hashicorp.com/terraform-provider-auth0/ |
Closing, but feel free to re-open if the problem persists. Cheers, |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform Version
12.10
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
Scope value/description updated, not set to null + created?
Actual Behavior
400 error
Steps to Reproduce
Important Factoids
Imported resources.
The text was updated successfully, but these errors were encountered: