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

subnetwork_project for google_dataproc_cluster #17052

Closed
paul-opsguru opened this issue Jan 8, 2018 · 2 comments
Closed

subnetwork_project for google_dataproc_cluster #17052

paul-opsguru opened this issue Jan 8, 2018 · 2 comments

Comments

@paul-opsguru
Copy link

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

@hashibot
Copy link
Contributor

hashibot commented Jan 8, 2018

This issue has been automatically migrated to hashicorp/terraform-provider-google#931 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.

@hashibot hashibot closed this as completed Jan 8, 2018
@ghost
Copy link

ghost commented Apr 5, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 5, 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

3 participants