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 field metastore_config to google_dataproc_cluster #5146

Merged

Conversation

shuyama1
Copy link
Member

This resolves hashicorp/terraform-provider-google#9419

If this PR is for Terraform, I acknowledge that I have:

  • Searched through the issue tracker for an open issue that this either resolves or contributes to, commented on it to claim it, and written "fixes {url}" or "part of {url}" in this PR description. If there were no relevant open issues, I opened one and commented that I would like to work on it (not necessary for very small changes).
  • Generated Terraform, and ran make test and make lint to ensure it passes unit and linter tests.
  • Ensured that all new fields I added that can be set by a user appear in at least one example (for generated resources) or third_party test (for handwritten resources or update tests).
  • Ran relevant acceptance tests (If the acceptance tests do not yet pass or you are unable to run them, please let your reviewer know).
  • Read the Release Notes Guide before writing my release note below.

Release Note Template for Downstream PRs (will be copied)

dataproc: added field `metastore_config` to `google_dataproc_cluster` (beta)

@shuyama1 shuyama1 requested a review from c2thorn August 26, 2021 20:21
@google-cla google-cla bot added the cla: yes label Aug 26, 2021
@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 1 file changed, 21 insertions(+))
Terraform Beta: Diff ( 3 files changed, 158 insertions(+))

@shuyama1
Copy link
Member Author

/gcbrun

@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform GA: Diff ( 1 file changed, 21 insertions(+))
Terraform Beta: Diff ( 4 files changed, 160 insertions(+), 3 deletions(-))

@modular-magician
Copy link
Collaborator

I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccComputeInstanceFromMachineImage_basic|TestAccComputeInstanceFromMachineImage_overrideMetadataDotStartupScript|TestAccDataprocCluster_withMetastoreConfig|TestAccPrivatecaCertificate_privatecaCertificateWithTemplateExample|TestAccPrivatecaCaPool_privatecaCapoolEmptyBaseline You can view the result here: https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=203110

Copy link
Member

@c2thorn c2thorn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great PR, looks very solid!
One thing I noticed was that we are making the field beta-only. From my quick search, I couldn't find anything that indicated this wasn't GA. I found https://cloud.google.com/dataproc-metastore/docs/attach-dataproc which didn't indicate any beta features. Could this work in GA?

@shuyama1
Copy link
Member Author

I found https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/dataproc_metastore_service, and it says the resource google_dataproc_metastore_service is still in beta, and that's why I make the field beta-only. Should I make it in GA instead? Anyways, let me try if this works in GA first.

@shuyama1
Copy link
Member Author

I tried it in GA and it didn't work, as the resource google_dataproc_metastore_service is not supported in GA provider. But since the API did indicate it as a beta feature, should we also bring the resource google_dataproc_metastore_service to GA?

@c2thorn
Copy link
Member

c2thorn commented Aug 27, 2021

@shuyama1 Gotcha, didn't realize the TF resource equivalent was still in beta. I think it is fine to leave as is, and move over when we GA dataproc metastore service. We could GA it now, but I believe that is out of scope for this task. Would you mind filing an issue to GA both google_dataproc_metastore_service and this field?

….go.erb

Co-authored-by: Cameron Thornton <camthornton@google.com>
@shuyama1
Copy link
Member Author

Sure! Will do!

@shuyama1 shuyama1 merged commit 4e514c9 into GoogleCloudPlatform:master Aug 27, 2021
@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician. Your PR generated some diffs in downstreams - here they are.

Diff report:

Terraform Beta: Diff ( 1 file changed, 1 insertion(+), 1 deletion(-))

@modular-magician
Copy link
Collaborator

I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccPrivatecaCaPool_privatecaCapoolEmptyBaseline You can view the result here: https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=203197

@modular-magician
Copy link
Collaborator

Tests failed during RECORDING mode: TestAccPrivatecaCaPool_privatecaCapoolEmptyBaseline Please fix these to complete your PR

khajduczenia pushed a commit to khajduczenia/magic-modules that referenced this pull request Oct 12, 2021
…tform#5146)

* added metastoreConfig to dataproc cluster

* Update mmv1/third_party/terraform/resources/resource_dataproc_cluster.go.erb

Co-authored-by: Cameron Thornton <camthornton@google.com>

Co-authored-by: Cameron Thornton <camthornton@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

google_dataproc_cluster is missing metastoreConfig field
3 participants