-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Updated optional component List to possible values #5136
Conversation
Hello! I am a robot who works on Magic Modules PRs. I have detected that you are a community contributor, so your PR will be assigned to someone with a commit-bit on this repo for initial review. Thanks for your contribution! A human will be with you soon. @c2thorn, please review this PR or find an appropriate assignee. |
@c2thorn TerraformVCRCommunity |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @sehgalnamit, just so we're on the same page, the logic you are updating only affects tests correct?
The schema for the actual resource appears in https://github.com/GoogleCloudPlatform/magic-modules/blob/master/mmv1/third_party/terraform/resources/resource_dataproc_cluster.go.erb#L542
@c2thorn This is my actual issue I was guided to use different codes and also I got another update with below:- Thanks |
@c2thorn Can you please advise on this? Thanks |
@sehgalnamit |
@c2thorn My goal is to get FLINK component added in the provider:- optional_components - |
@sehgalnamit I see, that makes sense. I still do not see We could add that in this PR? |
@c2thorn |
/gcbrun |
This comment has been minimized.
This comment has been minimized.
Hi @sehgalnamit
Even after removing these, the test check to verify optional components list does not do an un-ordered comparison: magic-modules/mmv1/third_party/terraform/tests/resource_dataproc_cluster_test.go.erb Line 904 in 174ad27
If the list is given in any order not specified in magic-modules/mmv1/third_party/terraform/tests/resource_dataproc_cluster_test.go.erb Line 575 in 174ad27
Given these issues, I don't think it is worth actually testing every possible value for optional components. It isn't something we do for other fields, and given the number of possible values it should be fine to just test |
@c2thorn https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/dataproc_cluster terraform { provider "google" { Configuration options} It could be Google API issue with Flink which I can go to Google Product team and ask. If you get similar issue for FLINK as an optional component not working while spinning of dataproc using this provider, I do not think it is worth to update HTML. My original issue |
Hi @sehgalnamit, this makes sense I agree with at least adding Trying it out myself very quickly, I see success. If you are having problems, can you post your config and Debug log? |
@c2thorn So you can just update HTML for the PR.I found further issues with though:-
NOTE: The Flink initialization action has been deprecated. Please use the Flink Component flink-start-yarn-session=true
Meaning I get new IPs even though in my plan, I see no change in the resource. |
Do you mind reverting the change to the test file in this PR, then I'll merge
We are limited by the API in what we can do, and there is not always parity with gcloud. I cannot find anything here: https://cloud.google.com/dataproc/docs/reference/rest/v1/projects.regions.clusters
Is this a current bug in the resource? It may be appropriate to open a new issue with the steps involved so we can solve it. I believe this is falling out of the scope of this PR. |
@c2thorn Also, I have raised a Case with Google for REST API issue Updated my current PR. |
/gcbrun |
I have triggered VCR tests in RECORDING mode for the following tests that failed during VCR: TestAccComputeForwardingRule_internalHttpLbWithMigBackendExample|TestAccComputeForwardingRule_internalTcpUdpLbWithMigBackendExample|TestAccComputeForwardingRule_forwardingRuleExternallbExample|TestAccComputeForwardingRule_forwardingRuleGlobalInternallbExample|TestAccComputeForwardingRule_forwardingRuleL3DefaultExample|TestAccComputeForwardingRule_forwardingRuleInternallbExample|TestAccComputeForwardingRule_forwardingRuleHttpLbExample|TestAccComputePacketMirroring_computePacketMirroringFullExample|TestAccComputeRoute_routeIlbExample|TestAccComputeServiceAttachment_serviceAttachmentBasicExample|TestAccComputeServiceAttachment_serviceAttachmentExplicitProjectsExample You can view the result here: https://ci-oss.hashicorp.engineering/viewQueued.html?itemId=205931 |
Tests failed during RECORDING mode: TestAccComputeServiceAttachment_serviceAttachmentBasicExample Please fix these to complete your PR |
You can merge the HTML. |
If this PR is for Terraform, I acknowledge that I have:
make test
andmake lint
to ensure it passes unit and linter tests.-[X] 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).
-[X] Ran relevant acceptance tests (If the acceptance tests do not yet pass or you are unable to run them, please let your reviewer know).
Release Note Template for Downstream PRs (will be copied)