Add update support for google_container_cluster.release_channel

[danawillow]

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 the 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 the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Current field is ForceNew, update support now exists in API: https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1beta1/ClusterUpdate.

New or Affected Resource(s)

• google_container_cluster

References

• b/150897589

[devdinu]

For instance, while updating release_channel, it forces new cluster creation google_container_cluster.gcp_kubernetes , would this solve the issue?

   release_channel {
          ~ channel = "UNSPECIFIED" -> "STABLE" # forces replacement
        }
    }

[danawillow]

Yes, that's what this issue is tracking.

[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!