-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Project Name not set on Google Cloud SQL Database #233
Comments
@ubschmidt2 - I believe #167 might be related as well. Google API likes to have the project explicitly set it looks like. #229 is definitely a step in the right direction. Support / Documentation for PostgreSQL is needed. |
@arhea - PostgreSQL is already supported and documented (25c6a00, hashicorp/terraform#12617). Oh, I guess you are referring to charset/collation for PostgreSQL. Looking into it. |
Just like in #167, I can't seem to reproduce this :-/ Can you share your full config instead of just the affected resource? (I really just need the |
I think this was fixed in #469. Let me know if it's still happening and I'll reopen! |
<!-- This change is generated by MagicModules. --> /cc @rileykarson
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! |
Terraform Version
0.10.0-rc1
Affected Resource(s)
Please list the resources as a list, for example:
google_sql_database
Terraform Configuration Files
Debug Output
Steps to Reproduce
terraform apply
Important Factoids
The error returned from the Google API is
sql#operation INTERNAL_ERROR
. After debugging by creating a database through the UI, which worked we determined that the missing field on the request was theproject
field. Without this field explicitly set the API fails. The work around is to set the project manually as such.It is also worth mentioning that the
collation
defaults to a MySQL value which may lead to weird errors with PostgreSQL databases.The text was updated successfully, but these errors were encountered: