google_container_cluster auto_provisioning_defaults state never converges

[MaT1g3R]

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.

Terraform Version

v0.12.18

Affected Resource(s)

• google_container_cluster

Terraform Configuration Files

resource "google_container_cluster" "default-cluster" {
  provider = google-beta

  name = local.cluster_name

  cluster_autoscaling {
    enabled = true
    resource_limits {
      resource_type = "cpu"
      minimum       = 6
      maximum       = 72
    }
    resource_limits {
      resource_type = "memory"
      minimum       = 24
      maximum       = 128
    }
    auto_provisioning_defaults {
      service_account = google_service_account.k8s_service_account.email
    }
  }
}

Expected Behavior

Terraform state does not track oauth_scopes under auto_provisioning_defaults

Actual Behavior

Terraform state tracks oauth_scopes under auto_provisioning_defaults, which leads to a diff for every apply like so:

~ cluster_autoscaling {
    enabled = true
    ~ auto_provisioning_defaults {
        ~ oauth_scopes    = [
            - "https://www.googleapis.com/auth/logging.write",
            - "https://www.googleapis.com/auth/monitoring",
        ]
        service_account = "xxxx@xxxx.iam.gserviceaccount.com"
    }
    resource_limits {
        maximum       = 72
        minimum       = 6
        resource_type = "cpu"
    }
    resource_limits {
        maximum       = 128
        minimum       = 24
        resource_type = "memory"
    }
}

Steps to Reproduce

1. terraform apply

[edwardmedia]

@MaT1g3R yes, I can repro this issue. It does show below plan after initial apply

Plan: 0 to add, 1 to change, 0 to destroy.

[mtricolici]

This issue is still present in latest terraform version 0.12.20 !

[mtricolici]

/reopen

[danawillow]

Hi @mtricolici, we close issues once the code is checked in, but that doesn't mean it's been released yet. You can see whether or not a given PR has made it into a release by checking the CHANGELOG.

Note also that 0.12.20 is a Terraform CLI version but not a Google Provider version. You can read about provider versions at https://www.terraform.io/docs/configuration/providers.html#provider-versions.

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!