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
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 an 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 an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.
Terraform Version
$ terraform version
Terraform v0.11.11
+ provider.google v1.19.1
Error: module.cloudsql.google_sql_database_instance.master: settings.0.ip_configuration.0: invalid or unknown key: private_network
Panic Output
Expected Behavior
According to docs, this is valid syntax. It's expected that the CloudSQL instance comes up with a private IP.
Actual Behavior
Terraform does not validate the code.
Steps to Reproduce
terraform apply
Important Factoids
According to #2127 , it seems the provider won't actually support this until v2.0.0. Since the docs are present, however, one would expect support to be present in a stable version as well.
References
The text was updated successfully, but these errors were encountered:
Sorry for the confusion around versions- we expected at the time that 2.0.0 would be the next release, but ended up making release 1.20.0. If this doesn't work after upgrading, feel free to comment on this issue and we'll reopen it.
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
Feb 25, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
According to docs, this is valid syntax. It's expected that the CloudSQL instance comes up with a private IP.
Actual Behavior
Terraform does not validate the code.
Steps to Reproduce
terraform apply
Important Factoids
According to #2127 , it seems the provider won't actually support this until v2.0.0. Since the docs are present, however, one would expect support to be present in a stable version as well.
References
The text was updated successfully, but these errors were encountered: