Add support for readiness checks and disabling TCP connections for Cloud Workstation configurations

[daanheikens]

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

The google_workstations_workstation_config resource is currently missing support for the following API fields:

• readinessChecks
• disableTcpConnections

New or Affected Resource(s)

google_workstations_workstation_config

Potential Terraform Configuration

resource "google_workstations_workstation_config" "default" {
  disable_tcp_connections = true 

  readiness_checks {
    path = "/"
    port = 80
  }
  
  readiness_checks {
    path = "/healthz"
    port = 8080
  }
}

References

https://cloud.google.com/workstations/docs/reference/rest/v1beta/projects.locations.workstationClusters.workstationConfigs#resource:-workstationconfig

https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/workstations_workstation_config

b/320650639

[bschaatsbergen]

Hey @daanheikens, thanks for taking the time to raise this issue. I'll happily pick it up 👍🏼.

[bschaatsbergen]

Note, these will be 2 separate PRs.

• 1 to address the disable_tcp_connections field
• Another one to introduce the readiness checks

[github-actions]

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.