-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Error enabling bigquery.googleapis.com #4590
Comments
OK so this might be a google side problem, as you can see, bigquery isn't even being returned from the gcloud cli:
|
Hey @Stono! This happened because of some changes upstream that made I'm going to use this issue to track that. In the meantime, if you've defined |
Thanks a lot @rileykarson - I've removed We've had a right nightmare because of this, and accidentally disabled bigquery api on some of our projects as a result when the upstream change was made! Do you have any more details with regards to that change or where Google announced the rename so I can use it in a post mortem? |
thanks @rileykarson, this caused us issues as well - originally, and now again when it was rolled back :). I was wondering if there are any release notes or more details about this change available anywhere? (I was not able to find any mention) |
I'm not aware of any release notes being published- I'll update this issue if I'm made aware of any. I'll also update the TPG/TPGB changelogs to note that users may have encountered a disruption. |
This should be mitigated in release Effectively, Terraform will treat the values as equivalent. It'll retry failed requests using the alternate value in case one of the values no longer works. If there's a real reason for failure and both fail, it'll return the errors. Upon reading either value from the API, Terraform will record what you've defined in your config in state. If you've defined neither, Terraform will write the Additionally, I'm going to disallow the |
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! |
Community Note
Hi,
We are seeing an issue where terraform plans are always trying to enable the biquery api on our project, even though it is already enabled. Even if we push through to an apply, it never completes (with the errors seen below).
Terraform Version
terraform: 0.12.9, provider: 2.16.0
Affected Resource(s)
google_project_services
Terraform Configuration Files
Debug Output
We see:
And then we just see it polling:
We can see the action was performed in the GCP Audit:
And the BigQuery API is enabled
I find interesting in the debug output too its asking for a list of enabled api's and that doesn't seem to include bigquery (probably explains the reason it's showing in the plan):
Panic Output
Expected Behavior
Terraform should manage the apis deterministically
Actual Behavior
We're unable to complete a terraform apply as the api modification times out after 20 minutes with the following error:
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: