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
when using private service access, resource google_sql_database_instance doesn't implicitly depend on private_vpc_connection and hence, requires explicitly defining depends on relationship with private_vpc_connection.
Unfortunately, this is true and pretty much unavoidable since we can't actually reference the networking connection in the SQL instance. As you can see in our example for private ip instances we use a depends_on block.
We certainly can improve the documentation around it but as of now we aren't able to do much else.
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
Apr 18, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
when using private service access, resource google_sql_database_instance doesn't implicitly depend on private_vpc_connection and hence, requires explicitly defining depends on relationship with private_vpc_connection.
The text was updated successfully, but these errors were encountered: