subnetwork_project for google_dataproc_cluster

[hashibot]

This issue was originally opened by @paul-opsguru as hashicorp/terraform#17052. It was migrated here as a result of the provider split. The original body of the issue is below.

---

Hi TF team,

A feature request for Google DataProc resource -

subnetwork_project (similar to https://www.terraform.io/docs/providers/google/r/compute_instance.html#subnetwork_project) on the https://www.terraform.io/docs/providers/google/r/dataproc_cluster.html#gce_cluster_config level.

Currently, TF assumes the current project namespace without an ability to override. That results in an inability to work with Shared Networks.

Meaning, this configuration of the google_dataproc_cluster resource:

gce_cluster_config {
    subnetwork = "projects/UPSTREAM-PROJECT/regions/us-east1/subnetworks/xpn-us-east1-shared1"
   }

Will result:

* google_dataproc_cluster.research-cluster-test: googleapi: Error 400: The resource 'projects/CURRENT-PROJECT/regions/us-east1/subnetworks/xpn-us-east1-shared1' was not found, badRequest

when running: terraform apply

Regards,
Paul

[rosbo]

Hi @paul-opsguru,

I opened PR #935 to properly support network and subnetwork fields with a self_link using a different project.

Don't forget to add the compute.subnetworks.use IAM permission to your @dataproc-accounts.iam.gserviceaccount.com service account used by the dataproc agent. Let me know if you need additional instructions on how to do this.

[paul-opsguru]

@rosbo , thanks for the prompt response, this is really helpful!

[ghost]

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!