Latest Google beta provider v4.34.0 for gke_container_cluster looking for value of new added attribute node_pool_auto_config

[anudeet-m]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

We are using google beta provider to provision gke cluster

Terraform Version

Terraform v1.1.8 Installed hashicorp/google v4.34.0 Installed hashicorp/google-beta v4.34.0..

Affected Resource(s)

*google_container_cluster

Terraform Configuration Files

We are using the below config to create cluster

provider = google-beta name = abc-kcl description = "test-demo-cluster" project = abc location = "euwes-2" network = "test-network" subnetwork = "test-subnetwork"

module.gke-cluster.module.gke_cluster.google_container_cluster.cluster has changed
  ~ resource "google_container_cluster" "cluster" {
        id                          = "projects/abc/locations/europe-west2/clusters/abc-kcl-euwe2"
      ~ master_version              = "1.21.12-gke.2200" -> "1.21.13-gke.900"
        name                        = "abc-kcl-02"
        # (28 unchanged attributes hidden)

  + node_pool_auto_config {
        }

Debug Output

N/A --->

Panic Output

Expected Behavior

The cluster should have been provisioned

Actual Behavior

It is breaking to create cluster with latest provider looking for the value of node_pool_auto_config

Steps to Reproduce

1. Create a GKE cluster using the latest google beta provider which is v4.34.0
2. Run terraform apply

Important Factoids

References

Not that I could find

[edwardmedia]

@melinath what happened?

[ayush-jain1]

@melinath what happened?

@edwardmedia @melinath can anyone please look into it ?

[melinath]

Wasn't able to get to this. I can't easily tell from the provided debug information what the issue is. Could someone experiencing this please provide a minimal configuration that reproduces the issue? i.e. just using the container_cluster resource, not a module. Thanks!

[philip-harvey]

I think this is a duplicate of https://github.com/hashicorp/terraform-provider-google/issues/12422

[edwardmedia]

@anudeet-m it does appear to be a dup. Closing now. Feel free to reopen if the issue persists.

[github-actions[bot]]

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.