Skip to content
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

Closed
rochdev opened this issue Sep 29, 2017 · 4 comments · Fixed by #498
Closed

google_compute_network_peering project field is required but cannot be set #496

rochdev opened this issue Sep 29, 2017 · 4 comments · Fixed by #498
Assignees
Labels

Comments

@rochdev
Copy link

rochdev commented Sep 29, 2017

When creating a google_compute_network_peering resource with a provider with no default project, the following error is received:

* google_compute_network_peering.my_peering: "project": required field is not set

This is the expected behaviour. However, when adding the project field as requested on the resource, the following error is received:

* google_compute_network_peering.my_peering: : invalid or unknown key: project

The resource should support the project field for Terraform configurations without a default project on the provider.

@rochdev
Copy link
Author

rochdev commented Sep 29, 2017

Closing in favor of #498

@rochdev rochdev closed this as completed Sep 29, 2017
@rosbo rosbo reopened this Sep 29, 2017
@rosbo
Copy link
Contributor

rosbo commented Sep 29, 2017

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.

@rochdev
Copy link
Author

rochdev commented Sep 29, 2017

Yes I meant to do that on my own PR sorry :)

@rosbo rosbo closed this as completed in #498 Oct 3, 2017
luis-silva pushed a commit to luis-silva/terraform-provider-google that referenced this issue May 21, 2019
<!-- This change is generated by MagicModules. -->
/cc @rileykarson
@ghost
Copy link

ghost commented Mar 30, 2020

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!

@ghost ghost locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants