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

add support for google_compute_forwarding_rule in shared vpc #4771

Closed
pulidon opened this issue Oct 29, 2019 · 2 comments
Closed

add support for google_compute_forwarding_rule in shared vpc #4771

pulidon opened this issue Oct 29, 2019 · 2 comments

Comments

@pulidon
Copy link

pulidon commented Oct 29, 2019

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

New or Affected Resource(s)

  • google_compute_forwarding_rule

Potential Terraform Configuration

Add subnetwork_project field to resource so it can be deployed on a shared vpc host project, but kept as a resource on the service project.

# Propose what you think the configuration to take advantage of this feature should look like.
# We may not use it verbatim, but it's helpful in understanding your intent.

References

  • #0000
@ghost ghost added the enhancement label Oct 29, 2019
@danawillow
Copy link
Contributor

Hi @pulidon, this should work if you pass in a reference to the subnetwork as a URL or relative path that includes the project, rather than as a name.

Since I'm pretty sure this works already, closing, but feel free to open a bug report if it doesn't.

@ghost
Copy link

ghost commented Mar 28, 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 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants