Closed Evesy closed 5 years ago
If you remove it from your config, the error should go away, as will the diff.
@paddycarver what's the upstream bug here? Anything I should file internally?
I don't... know? I think my thought process was that the upstream "fix" would be not having services that you can't actually enable. I think we've already raised that with the team, though?
Ah ok, I definitely remember sending something out about it but I can't find it now. I highly doubt that's going to change though. Still worth it to keep this issue open?
I don't really know what our options are here, or what we could do. Seeing as there's no next steps we can take, as far as I know, I'm going to close this out. If someone thinks we could have better documentation for this, or there's something we could do, I'm happy to reopen or discuss on another issue.
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!
Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
1.16.2
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
From the introduction of #1763 in 1.16.0 I'd expect Terraform to ignore this API since it is automatically enabled alongside other API's (as I understand it)
Actual Behavior
Since upgrading from 1.15.0 to 1.16.2 Terraform is trying to enable the API:
The apply also fails due to insufficient permissions (The user being ran is an Owner of the project, and an Organisation Administrator). The API is already enabled too:
Steps to Reproduce
stackdriverprovisioning.googleapis.com
References
1763