-
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
google_compute_network_peering
project field is required but cannot be set
#496
Comments
Closing in favor of #498 |
Thanks Roch, this is definitely an issue! Reopening, #498 is a PR fixing your issue :) This issue will automatically close once the PR is merged. |
Yes I meant to do that on my own PR sorry :) |
<!-- 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 👉 hashibot-feedback@hashicorp.com. Thanks! |
Since the CI configuration in the test folder is no longer needed, we can safely delete those.
When creating a
google_compute_network_peering
resource with a provider with no default project, the following error is received:This is the expected behaviour. However, when adding the
project
field as requested on the resource, the following error is received:The resource should support the
project
field for Terraform configurations without a default project on the provider.The text was updated successfully, but these errors were encountered: