google_container_cluster: add Node auto-provisioning locations

[prauc]

When Node auto-provisioning is enabled, the terraform provider currently cannot be used to define node auto-provisioning locations. This configuration is, as of today, presently limited to the UI, gcloud, or API.

Tests for google_container_cluster were already successfully executed locally

Release Note Template for Downstream PRs (will be copied)

container: added `auto_provisioning_locations` field to `google_container_cluster`

[github-actions]

Hello! I am a robot. Tests will require approval from a repository maintainer to run.

@slevenick, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look.

You can help make sure that review is quick by doing a self-review and by running impacted tests locally.

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 4 files changed, 96 insertions(+))
google-beta provider: Diff ( 4 files changed, 96 insertions(+))

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_container_cluster (373 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_container_cluster" "primary" {
  cluster_autoscaling {
    auto_provisioning_locations = # value needed
  }
}

[modular-magician]

Tests analytics

Total tests: 200
Passed tests: 189
Skipped tests: 10
Affected tests: 1

Click here to see the affected service packages

• container

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests

• TestAccContainerCluster_autoprovisioningLocations

Get to know how VCR tests work

[modular-magician]

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccContainerCluster_autoprovisioningLocations[Debug log]

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$

---

$\textcolor{green}{\textsf{All tests passed!}}$

View the build log or the debug log for each test

[slevenick]

Can you add an update step for this field?

[prauc]

yes, np! done

[prauc]

@slevenick fyi

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

google provider: Diff ( 4 files changed, 114 insertions(+))
google-beta provider: Diff ( 4 files changed, 114 insertions(+))

Missing test report

Your PR includes resource fields which are not covered by any test.

Resource: google_container_cluster (373 total tests)
Please add an acceptance test which includes these fields. The test should include the following:

resource "google_container_cluster" "primary" {
  cluster_autoscaling {
    auto_provisioning_locations = # value needed
  }
}

[modular-magician]

Tests analytics

Total tests: 200
Passed tests: 189
Skipped tests: 10
Affected tests: 1

Click here to see the affected service packages

• container

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests

• TestAccContainerCluster_autoprovisioningLocations

Get to know how VCR tests work

[modular-magician]

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccContainerCluster_autoprovisioningLocations[Debug log]

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$

---

$\textcolor{green}{\textsf{All tests passed!}}$

View the build log or the debug log for each test

[slevenick]

Thanks!