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

incorrect documentation of properties ipv4_enabled and private_network of google_sql_database_instance #8818

Closed
mvanholsteijn opened this issue Apr 1, 2021 · 2 comments

Comments

@mvanholsteijn
Copy link
Contributor

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 or link the pull request to this issue.

Terraform Version

0.13.6

Affected Resource(s)

  • google_sql_database_instance

Issue Description

The documentation states that ipv4_enabled and private_network are mutually exclusive but the CloudSQL documentation says:

You can use both public IP and private IP to connect to the same Cloud SQL instance. Neither connection method affects the other.

References

@mvanholsteijn mvanholsteijn changed the title documentation of properties ipv4_enabled and private_network of google_sql_database_instance are incorrect incorrect documentation of properties ipv4_enabled and private_network of google_sql_database_instance Apr 1, 2021
@c2thorn
Copy link
Collaborator

c2thorn commented Apr 5, 2021

closed with #8819

@c2thorn c2thorn closed this as completed Apr 5, 2021
@ghost
Copy link

ghost commented May 6, 2021

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 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators May 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants