Skip to content

[FR]: Add support for Workstation Boost Configurations to workstation-cluster module #4075

Description

@davidferguson-telana

The feature request

v5.22.0 of the Google Terraform Provider added support for the boost_configs field to the host.gce_instance argument on the google_workstations_workstation_config resource (diff as didn't make it into release notes).

Please add support for this to the Workstation cluster Module (workstation-cluster) by exposing this field within the workstation_configs variable to enable configuration of one or more boost configurations that workstations created using this workstation configuration are allowed to use.

Proposed solution

Expose a boost_configs field within the existing workstation_configs variable, respecting the structure of the provider module definition here and apply this configuration to the google_workstations_workstation_config.configs resource.

Example:

module "workstation-cluster" {
  source     = "./fabric/modules/workstation-cluster"
  project_id = var.project_id
  id         = "my-workstation-cluster"
  location   = var.region
  network_config = {
    network    = var.vpc.self_link
    subnetwork = var.subnet.self_link
  }
  workstation_configs = {
    my-workstation-config = {
      gce_instance = {
        machine_type                = "e2-standard-4"
        boot_disk_size_gb           = 35
        disable_public_ip_addresses = true
        boost_configs = [
          {
            id           = "boost-1"
            machine_type = "n1-standard-2"
            accelerators {
              type  = "nvidia-tesla-t4"
              count = "1"
            }
          },
          {
            id           = "boost-1"
            machine_type = "e2-standard-2"
          }
        ]
      }
      workstations = {
        my-workstation = {
          labels = {
            team = "my-team"
          }
        }
      }
    }
  }
}

Additional context

See Google documentation for more: Cloud Workstations Docs > Guides > Boost your workstation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions