You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Like a lot of the older resources in the GCP provider, google_sql_database_instance only stores in state the properties that the user has defined in configs. This makes detecting drift unreliable, and also makes it impossible for us to support importing this resource type. We should update it to persist state from the API regardless of what is in the config.
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Mar 31, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue was originally opened by @paddycarver as hashicorp/terraform#15201. It was migrated here as part of the provider split. The original body of the issue is below.
Like a lot of the older resources in the GCP provider,
google_sql_database_instance
only stores in state the properties that the user has defined in configs. This makes detecting drift unreliable, and also makes it impossible for us to support importing this resource type. We should update it to persist state from the API regardless of what is in the config.The text was updated successfully, but these errors were encountered: