Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

provider/google: google_sql_database_instance doesn't set state in read #114

Closed
hashibot opened this issue Jun 13, 2017 · 1 comment · Fixed by #208
Closed

provider/google: google_sql_database_instance doesn't set state in read #114

hashibot opened this issue Jun 13, 2017 · 1 comment · Fixed by #208
Assignees
Labels

Comments

@hashibot
Copy link

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.

@ghost
Copy link

ghost commented Mar 31, 2020

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 ghost locked and limited conversation to collaborators Mar 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
2 participants