Add Looker product and Instance resource support#8110
Conversation
|
Hello! I am a robot who works on Magic Modules PRs. I've detected that you're a community contributor. @rileykarson, a repository maintainer, has been assigned to assist you and help review your changes. ❓ First time contributing? Click here for more detailsYour assigned reviewer will help review your code by:
You can help make sure that review is quick by running local tests and ensuring they're passing in between each push you make to your PR's branch. Also, try to leave a comment with each push you make, as pushes generally don't generate emails. If your reviewer doesn't get back to you within a week after your most recent change, please feel free to leave a comment on the issue asking them to take a look! In the absence of a dedicated review dashboard most maintainers manage their pending reviews through email, and those will sometimes get lost in their inbox. |
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are. Terraform GA: Diff ( 11 files changed, 2590 insertions(+), 2 deletions(-)) |
Tests analyticsTotal tests: Action takenFound 8 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccLookerInstance_lookerInstanceFullExample|TestAccLookerInstance_lookerInstanceBasicExample|TestAccLoggingBucketConfigProject_cmekSettings|TestAccComputeFirewallPolicyRule_multipleRules|TestAccApigeeKeystoresAliasesKeyCertFile_apigeeKeystoresAliasesKeyCertFileTestExample|TestAccApigeeKeystoresAliasesPkcs12_ApigeeKeystoresAliasesPkcs12Example|TestAccDataSourceAlloydbLocations_basic|TestAccDataSourceGoogleFirebaseAndroidAppConfig |
|
Tests passed during RECORDING mode: Tests failed during RECORDING mode: Please fix these to complete your PR |
|
The failure is not related to this PR. |
rileykarson
left a comment
There was a problem hiding this comment.
The failing test is due to an issue on our end!
The pricing on this product is pretty high, we'll need to work out whether that's an issue for our team or not before merging this. I'm not sure offhand- I'm out tomorrow, but will investigate Monday.
| name: reservedRange | ||
| description: | | ||
| Name of a reserved IP address range within the consumer network, to be used for | ||
| private servicie access connection. User may or may not specify this in a request. |
There was a problem hiding this comment.
| private servicie access connection. User may or may not specify this in a request. | |
| private service access connection. User may or may not specify this in a request. |
This is a typo in the original API docs, fwiw
|
@rileykarson Could you please have another look at this? |
Merge into main
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are. Terraform GA: Diff ( 14 files changed, 2940 insertions(+), 2 deletions(-)) |
Tests analyticsTotal tests: Action takenFound 6 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccVertexAIIndex_updated|TestAccVertexAIIndex_vertexAiIndexStreamingExample|TestAccVertexAIIndex_vertexAiIndexExample|TestAccLookerInstance_lookerInstanceEnterpriseFullExample|TestAccContainerAwsNodePool_BetaBasicHandWritten|TestAccComputeFirewallPolicyRule_multipleRules |
|
Rerun these tests in REPLAYING mode to catch issues
|
|
None of those tests are related. I'll make a final review pass tomorrow, but no action expected from 'em on your end. |
| private_ip_enabled = true | ||
| public_ip_enabled = false | ||
| reserved_range = "${google_compute_global_address.looker_range.name}" | ||
| consumer_network = "projects/${data.google_project.project.number}/global/networks/${google_compute_network.looker_network.name}" |
There was a problem hiding this comment.
Does this accept a project id, or just a number? Per https://google.aip.dev/cloud/2510#google-apis it should accept both (and return the format that was sent), and project ids are generally preferred as we can just reference https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_network#id instead of needing to do string interpolation here.
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are. Terraform GA: Diff ( 14 files changed, 2940 insertions(+), 2 deletions(-)) |
Tests analyticsTotal tests: Action takenFound 10 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected testsTestAccLookerInstance_lookerInstanceEnterpriseFullExample|TestAccContainerAwsNodePool_BetaBasicHandWritten|TestAccComputeFirewallPolicyRule_multipleRules|TestAccClouddeployDeliveryPipeline_VerifyDeliveryPipeline|TestAccClouddeployDeliveryPipeline_DeliveryPipeline|TestAccClouddeployTarget_Target|TestAccClouddeployDeliveryPipeline_CanaryServiceNetworkingDeliveryPipeline|TestAccClouddeployDeliveryPipeline_CanaryrunDeliveryPipeline|TestAccClouddeployDeliveryPipeline_CanaryDeliveryPipeline|TestAccBigtableAppProfile_bigtableAppProfileSingleclusterExample |
|
Rerun these tests in REPLAYING mode to catch issues
|
…#8110) Co-authored-by: Riley Karson <rileykarson@google.com> Co-authored-by: Efe Elaiho <efeelaiho@google.com> Co-authored-by: efeelaiho <efeelaiho15@utexas.edu>
…#8110) Co-authored-by: Riley Karson <rileykarson@google.com> Co-authored-by: Efe Elaiho <efeelaiho@google.com> Co-authored-by: efeelaiho <efeelaiho15@utexas.edu>
…#8110) Co-authored-by: Riley Karson <rileykarson@google.com> Co-authored-by: Efe Elaiho <efeelaiho@google.com> Co-authored-by: efeelaiho <efeelaiho15@utexas.edu>
…#8110) Co-authored-by: Riley Karson <rileykarson@google.com> Co-authored-by: Efe Elaiho <efeelaiho@google.com> Co-authored-by: efeelaiho <efeelaiho15@utexas.edu>
If this PR is for Terraform, I acknowledge that I have:
make testandmake lintin the generated providers to ensure it passes unit and linter tests.Release Note Template for Downstream PRs (will be copied)