You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/// Change the Identity Aware Proxy (IAP) service configuration for the backend service. You can set IAP to 'enabled' or 'disabled', or modify the OAuth2 client configuration (oauth2-client-id and oauth2-client-secret) used by IAP. If any fields are unspecified, their values will not be modified. For instance, if IAP is enabled, '--iap=disabled' will disable IAP, and a subsequent '--iap=enabled' will then enable it with the same OAuth2 client configuration as the first time it was enabled. See https://cloud.google.com/iap/ for more information about this feature.
160
+
/// Change the Identity Aware Proxy (IAP) service configuration for the backend service. You can set IAP to 'enabled' or 'disabled', or modify the OAuth2 client configuration (oauth2-client-id and oauth2-client-secret) used by IAP. If any fields are unspecified, their values will not be modified. For instance, if IAP is enabled, '--iap=disabled' will disable IAP, and a subsequent '--iap=enabled' will then enable it with the same OAuth2 client configuration as the first time it was enabled. To clear the OAuth2 client ID and secret, set their values to a single space character (e.g., '--iap=enabled,oauth2-client-id=" ",oauth2-client-secret=" "'). Setting them to empty strings will result in an error. Example output of gcloud compute backend-services describe after clearing: iap: enabled: true oauth2ClientId: ' ' See https://cloud.google.com/iap/ for more information about this feature.
/// Enables Confidential VM. See https://cloud.google.com/compute/confidential-vm/docs for more information. Note that Confidential VM can only be enabled when the machine types are N2D (https://cloud.google.com/compute/docs/machine-types#n2d_machine_types) and the image is SEV Compatible.
58
-
/// </summary>
59
-
[CliFlag("--confidential-compute")]
60
-
publicbool?ConfidentialCompute{get;set;}
61
-
62
56
/// <summary>
63
57
/// Specify the name of a Dataproc Metastore service to be used as an external metastore in the format: "projects/{project-id}/locations/{region}/services/{service-name}".
64
58
/// </summary>
@@ -381,10 +375,10 @@ public record GcloudDataprocClustersCreateOptions : GcloudOptions
381
375
publicstring?WorkerLocalSsdInterface{get;set;}
382
376
383
377
/// <summary>
384
-
/// When specified, the VM is scheduled on the host with a specified CPU architecture or a more recent CPU platform that's available in that zone. To list available CPU platforms in a zone, run: $ gcloud compute zones describe ZONE CPU platform selection may not be available in a zone. Zones that support CPU platform selection provide an availableCpuPlatforms field, which contains the list of available CPU platforms in the zone (see Availability of CPU platforms for more information). At most one of these can be specified: --auto-zone-exclude-zones=[ZONE,...] A comma-separated list of compute zones (such as us-central1-a) to exclude when Dataproc Auto Zone placement (https://docs.cloud.google.com/dataproc/docs/concepts/configuring-clusters/auto-zone) picks the zone for the cluster. --zone=ZONE, -z ZONE The compute zone (such as us-central1-a) for the cluster. If empty and --region is set to a value other than global, Dataproc Auto Zone placement (https://docs.cloud.google.com/dataproc/docs/concepts/configuring-clusters/auto-zone) will pick a zone in the region. Overrides the default compute/zone property value for this command invocation. At most one of these can be specified: --delete-expiration-time=DELETE_EXPIRATION_TIME The time when the cluster will be auto-deleted, such as "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for information on time formats. --delete-max-age=DELETE_MAX_AGE The lifespan of the cluster, with auto-deletion upon completion, such as "2h" or "1d". See $ gcloud topic datetimes for information on duration formats. Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the cluster. The 'Compute Engine Service Agent' service account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. The arguments in this group can be used to specify the attributes of this resource.
378
+
/// When specified, the VM is scheduled on the host with a specified CPU architecture or a more recent CPU platform that's available in that zone. To list available CPU platforms in a zone, run: $ gcloud compute zones describe ZONE CPU platform selection may not be available in a zone. Zones that support CPU platform selection provide an availableCpuPlatforms field, which contains the list of available CPU platforms in the zone (see Availability of CPU platforms for more information). At most one of these can be specified: --auto-zone-exclude-zones=[ZONE,...] A comma-separated list of compute zones (such as us-central1-a) to exclude when Dataproc Auto Zone placement (https://docs.cloud.google.com/dataproc/docs/concepts/configuring-clusters/auto-zone) picks the zone for the cluster. --zone=ZONE, -z ZONE The compute zone (such as us-central1-a) for the cluster. If empty and --region is set to a value other than global, Dataproc Auto Zone placement (https://docs.cloud.google.com/dataproc/docs/concepts/configuring-clusters/auto-zone) will pick a zone in the region. Overrides the default compute/zone property value for this command invocation. At most one of these can be specified: --confidential-compute (DEPRECATED) Enables Confidential VM. See https://cloud.google.com/confidential-computing/confidential-vm/docs/ for more information. This flag uses AMD SEV confidential compute technology, which is only supported on N2D, C2D, C3D, and C4D machine types (https://cloud.google.com/compute/docs/machine-types). The --confidential-compute flag is deprecated. Please use --confidential-compute-type=SEV instead. --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE Enables Confidential VM. See https://cloud.google.com/confidential-computing/confidential-vm/docs/ for more information. This flag specifies the type of Confidential Compute technology. See https://cloud.google.com/confidential-computing/confidential-vm/docs/supported-configurations#machine-type-cpu-zone for each machine type supported by Confidential Compute technology. CONFIDENTIAL_COMPUTE_TYPE must be one of: SEV, SEV_SNP, TDX. At most one of these can be specified: --delete-expiration-time=DELETE_EXPIRATION_TIME The time when the cluster will be auto-deleted, such as "2017-08-29T18:52:51.142Z." See $ gcloud topic datetimes for information on time formats. --delete-max-age=DELETE_MAX_AGE The lifespan of the cluster, with auto-deletion upon completion, such as "2h" or "1d". See $ gcloud topic datetimes for information on duration formats. Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the cluster. The 'Compute Engine Service Agent' service account must hold permission 'Cloud KMS CryptoKey Encrypter/Decrypter'. The arguments in this group can be used to specify the attributes of this resource.
/// ID of the key or fully qualified identifier for the key. To set the kms-key attribute: ◆ provide the argument --gce-pd-kms-key on the command line. This flag argument must be specified if any of the other arguments in this group are specified.
/// A SQL-query WHERE clause selecting which data should be included, not including the "WHERE" keyword itself. e.g., t.key1 = 'value1' AND t.key2 = 'value2'. Only supported for SQL sources.
/// Return immediately, without waiting for the operation in progress to complete. Backup vault resource - The Backup Vault that the Backup is stored in This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --backup-vault on the command line with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. To set the location attribute: ◆ provide the argument --backup-vault on the command line with a fully specified name; ◆ provide the argument --location on the command line; ◆ set the property netapp/location.
27
-
/// </summary>
28
-
[CliFlag("--async")]
29
-
publicbool?Async{get;set;}
30
-
31
-
/// <summary>
32
-
/// ID of the backup_vault or fully qualified identifier for the backup_vault. To set the backup_vault attribute: ◆ provide the argument --backup-vault on the command line.
/// List of label KEY=VALUE pairs to add. Keys must start with a lowercase character and contain only hyphens (-), underscores (_), lowercase characters, and numbers. Values must contain only hyphens (-), underscores (_), lowercase characters, and numbers. Snapshot resource - The full name of the Source Snapshot that the Backup is based on', Format: projects/{project_id}/locations/{location}/volumes/{volume_id}/snapshots/{snapshot_id} This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --source-snapshot on the command line with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. To set the location attribute: ◆ provide the argument --source-snapshot on the command line with a fully specified name; ◆ set the property netapp/location. To set the volume attribute: ◆ provide the argument --source-snapshot on the command line with a fully specified name.
/// ID of the snapshot or fully qualified identifier for the snapshot. To set the snapshot attribute: ◆ provide the argument --source-snapshot on the command line. Volume resource - The full name of the Source Volume that the Backup is based on', Format: projects/{projects_id}/locations/{location}/volumes/{volume_id} This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --source-volume on the command line with a fully specified name; ◆ provide the argument --volume on the command line with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. To set the location attribute: ◆ provide the argument --source-volume on the command line with a fully specified name; ◆ provide the argument --volume on the command line with a fully specified name; ◆ provide the argument --location on the command line; ◆ set the property netapp/location.
/// ID of the volume or fully qualified identifier for the volume. To set the volume attribute: ◆ provide the argument --source-volume on the command line; ◆ provide the argument --volume on the command line.
0 commit comments