yandex_compute_gpu_cluster_iam_binding (Resource)

Allows creation and management of a single binding within IAM policy for an existing gpu_cluster.

Example usageExample usage

//
// Create a new GPU Cluster and new IAM Binding for it.
//
resource "yandex_compute_gpu_cluster" "gpu1" {
  name              = "gpu-cluster-name"
  interconnect_type = "INFINIBAND"
  zone              = "ru-central1-a"

  labels = {
    environment = "test"
  }
}

resource "yandex_compute_gpu_cluster_iam_binding" "editor" {
  gpu_cluster_id = data.yandex_compute_gpu_cluster.gpu1.id

  role = "editor"

  members = [
    "userAccount:some_user_id",
  ]
}

Arguments & Attributes ReferenceArguments & Attributes Reference

• gpu_cluster_id (Required)(String). The ID of the compute gpu_cluster to attach the policy to.
• id (String). The ID of this resource.
• members (Required)(Set Of String). An array of identities that will be granted the privilege in the role. Each entry can have one of the following values:

• userAccount:{user_id}: A unique user ID that represents a specific Yandex account.
• serviceAccount:{service_account_id}: A unique service account ID.
• federatedUser:{federated_user_id}: A unique federated user ID.
• federatedUser:{federated_user_id}:: A unique SAML federation user account ID.
• group:{group_id}: A unique group ID.
• system:group:federation:{federation_id}:users: All users in federation.
• system:group:organization:{organization_id}:users: All users in organization.
• system:allAuthenticatedUsers: All authenticated users.
• system:allUsers: All users, including unauthenticated ones.

• role (Required)(String). The role that should be assigned. Only one yandex_compute_gpu_cluster_iam_binding can be used per role.
• sleep_after (Number). For test purposes, to compensate IAM operations delay