Fail fast on google_sql_database_instance when private networking is requested but service network connection isn't enabled

[danawillow]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Currently, if a SQL instance is created with private networking enabled, the instance will be created. If the service network connection doesn't exist, it gets created in a failed state, requiring users to need to recreate the instance to resolve.

Before making the insert request, we can check if the service network connection exists (making sure to ignore 403s since not everyone that runs terraform has all the same permissions), and if it doesn't, fail immediately.

New or Affected Resource(s)

• google_sql_database_instance

References

• Private SQLInstance and private network cannot be created in the same set of configs.  GoogleCloudPlatform/k8s-config-connector#148
• b/166681317

[ghost]

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!