diff --git a/gcloud/_version b/gcloud/_version index 3bbcfc112..5cd3bbc79 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 541.0.0 -alpha 2025.09.29 -beta 2025.09.29 +Google Cloud SDK 542.0.0 +alpha 2025.10.03 +beta 2025.10.03 bq 2.1.24 bundled-python3-unix 3.12.9 -core 2025.09.29 +core 2025.10.03 gcloud-crc32c 1.0.0 gsutil 5.35 diff --git a/gcloud/alpha/biglake/help b/gcloud/alpha/biglake/help new file mode 100644 index 000000000..d9b35f822 --- /dev/null +++ b/gcloud/alpha/biglake/help @@ -0,0 +1,27 @@ +NAME + gcloud alpha biglake - create and manage Google Cloud BigLake resources + +SYNOPSIS + gcloud alpha biglake GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The gcloud biglake command group lets you create and manage Google + Cloud BigLake resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + iceberg + (ALPHA) Biglake Iceberg REST Catalogs. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/biglake/iceberg/catalogs/delete b/gcloud/alpha/biglake/iceberg/catalogs/delete new file mode 100644 index 000000000..82ee6572f --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/catalogs/delete @@ -0,0 +1,43 @@ +NAME + gcloud alpha biglake iceberg catalogs delete - delete a BigLake Iceberg + REST catalog + +SYNOPSIS + gcloud alpha biglake iceberg catalogs delete CATALOG [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a BigLake Iceberg REST catalog. + +POSITIONAL ARGUMENTS + Catalog resource - The Iceberg Catalog to delete. 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 catalog on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CATALOG + ID of the catalog or fully qualified identifier for the catalog. + + To set the catalog attribute: + ▸ provide the argument catalog on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/biglake/iceberg/catalogs/describe b/gcloud/alpha/biglake/iceberg/catalogs/describe new file mode 100644 index 000000000..c59e948ac --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/catalogs/describe @@ -0,0 +1,44 @@ +NAME + gcloud alpha biglake iceberg catalogs describe - describe a BigLake Iceberg + REST catalog + +SYNOPSIS + gcloud alpha biglake iceberg catalogs describe CATALOG + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a BigLake Iceberg REST catalog. + +POSITIONAL ARGUMENTS + Catalog resource - The Iceberg Catalog to describe. 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 catalog on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CATALOG + ID of the catalog or fully qualified identifier for the catalog. + + To set the catalog attribute: + ▸ provide the argument catalog on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/biglake/iceberg/catalogs/help b/gcloud/alpha/biglake/iceberg/catalogs/help new file mode 100644 index 000000000..7a548e410 --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/catalogs/help @@ -0,0 +1,36 @@ +NAME + gcloud alpha biglake iceberg catalogs - manage BigLake Iceberg REST + catalogs + +SYNOPSIS + gcloud alpha biglake iceberg catalogs COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage BigLake Iceberg REST catalogs. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (ALPHA) Delete a BigLake Iceberg REST catalog. + + describe + (ALPHA) Describe a BigLake Iceberg REST catalog. + + list + (ALPHA) List BigLake Iceberg REST catalogs. + + update + (ALPHA) Update a BigLake Iceberg REST catalog. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/biglake/iceberg/catalogs/list b/gcloud/alpha/biglake/iceberg/catalogs/list new file mode 100644 index 000000000..22c7b7c86 --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/catalogs/list @@ -0,0 +1,58 @@ +NAME + gcloud alpha biglake iceberg catalogs list - list BigLake Iceberg REST + catalogs + +SYNOPSIS + gcloud alpha biglake iceberg catalogs list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List BigLake Iceberg REST catalogs. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/biglake/iceberg/catalogs/update b/gcloud/alpha/biglake/iceberg/catalogs/update new file mode 100644 index 000000000..88470e8b1 --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/catalogs/update @@ -0,0 +1,50 @@ +NAME + gcloud alpha biglake iceberg catalogs update - update a BigLake Iceberg + REST catalog + +SYNOPSIS + gcloud alpha biglake iceberg catalogs update CATALOG + [--credential-mode=TYPE; default="CREDENTIAL_MODE_END_USER"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a BigLake Iceberg REST catalog. + +POSITIONAL ARGUMENTS + Catalog resource - The Iceberg Catalog to update. 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 catalog on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CATALOG + ID of the catalog or fully qualified identifier for the catalog. + + To set the catalog attribute: + ▸ provide the argument catalog on the command line. + +FLAGS + --credential-mode=TYPE; default="CREDENTIAL_MODE_END_USER" + Credential mode to update the catalog with. TYPE must be one of: + CREDENTIAL_MODE_END_USER, CREDENTIAL_MODE_VENDED_CREDENTIALS. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/biglake/iceberg/help b/gcloud/alpha/biglake/iceberg/help new file mode 100644 index 000000000..c21cef895 --- /dev/null +++ b/gcloud/alpha/biglake/iceberg/help @@ -0,0 +1,26 @@ +NAME + gcloud alpha biglake iceberg - biglake Iceberg REST Catalogs + +SYNOPSIS + gcloud alpha biglake iceberg GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Biglake Iceberg REST Catalogs. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + catalogs + (ALPHA) Manage BigLake Iceberg REST catalogs. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/cluster-director/clusters/create b/gcloud/alpha/cluster-director/clusters/create index 2af83aaab..5b0983ac7 100644 --- a/gcloud/alpha/cluster-director/clusters/create +++ b/gcloud/alpha/cluster-director/clusters/create @@ -135,44 +135,65 @@ REQUIRED FLAGS VALUE Sets VALUE value. - newDwsFlexInstances - Sets newDwsFlexInstances value. + config + Sets config value. - machineType - Sets machineType value. + newDwsFlexInstances + Sets newDwsFlexInstances value. - maxDuration - Sets maxDuration value. + machineType + Sets machineType value. - zone - Sets zone value. + maxDuration + Sets maxDuration value. - newOnDemandInstances - Sets newOnDemandInstances value. + zone + Sets zone value. - machineType - Sets machineType value. + newFlexStartInstances + Sets newFlexStartInstances value. - zone - Sets zone value. + machineType + Sets machineType value. - newReservedInstances - Sets newReservedInstances value. + maxDuration + Sets maxDuration value. - machineType - Sets machineType value. + zone + Sets zone value. - reservation - Sets reservation value. + newOnDemandInstances + Sets newOnDemandInstances value. - newSpotInstances - Sets newSpotInstances value. + machineType + Sets machineType value. - machineType - Sets machineType value. + zone + Sets zone value. - zone - Sets zone value. + newReservedInstances + Sets newReservedInstances value. + + machineType + Sets machineType value. + + reservation + Sets reservation value. + + type + Sets type value. + + zone + Sets zone value. + + newSpotInstances + Sets newSpotInstances value. + + machineType + Sets machineType value. + + zone + Sets zone value. description Sets description value. @@ -437,11 +458,11 @@ REQUIRED FLAGS Shorthand Example: - --config=computeResources={string={newDwsFlexInstances={machineType=string,maxDuration=string,zone=string},newOnDemandInstances={machineType=string,zone=string},newReservedInstances={machineType=string,reservation=string},newSpotInstances={machineType=string,zone=string}}},description=string,labels={string=string},name=string,networkResources={string={config={existingNetwork={network=string,subnetwork=string},newNetwork={description=string,network=string}}}},orchestrator={slurm={defaultPartition=string,loginNodes={count=int,disks=[{boot=boolean,sizeGb=int,sourceImage=string,type=string}],enableOsLogin=boolean,enablePublicIps=boolean,labels={string=string},machineType=string,startupScript=string,storageConfigs=[{id=string,localMount=string}],zone=string},nodeSets=[{bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},id=string,labels={string=string},maxDynamicNodeCount=int,resourceRequestId=string,startupScript=string,staticNodeCount=int,storageConfigs=[{id=string,localMount=string}]}],partitions=[{exclusive=boolean,id=string,nodeSetIds=[string]}]}},storageResources={string={config={existingBucket={bucket=string},existingFilestore={filestore=string},existingLustre={lustre=string},newBucket={autoclass={enabled=boolean},bucket=string,hierarchicalNamespace={enabled=boolean},storageClass=string},newFilestore={description=string,fileShares=[{capacityGb=int,fileShare=string}],filestore=string,protocol=string,tier=string},newLustre={capacityGb=int,description=string,filesystem=string,lustre=string}}}} + --config=computeResources={string={config={newDwsFlexInstances={machineType=string,maxDuration=string,zone=string},newFlexStartInstances={machineType=string,maxDuration=string,zone=string},newOnDemandInstances={machineType=string,zone=string},newReservedInstances={machineType=string,reservation=string,type=string,zone=string},newSpotInstances={machineType=string,zone=string}}}},description=string,labels={string=string},name=string,networkResources={string={config={existingNetwork={network=string,subnetwork=string},newNetwork={description=string,network=string}}}},orchestrator={slurm={defaultPartition=string,loginNodes={count=int,disks=[{boot=boolean,sizeGb=int,sourceImage=string,type=string}],enableOsLogin=boolean,enablePublicIps=boolean,labels={string=string},machineType=string,startupScript=string,storageConfigs=[{id=string,localMount=string}],zone=string},nodeSets=[{bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},id=string,labels={string=string},maxDynamicNodeCount=int,resourceRequestId=string,startupScript=string,staticNodeCount=int,storageConfigs=[{id=string,localMount=string}]}],partitions=[{exclusive=boolean,id=string,nodeSetIds=[string]}]}},storageResources={string={config={existingBucket={bucket=string},existingFilestore={filestore=string},existingLustre={lustre=string},newBucket={autoclass={enabled=boolean},bucket=string,hierarchicalNamespace={enabled=boolean},storageClass=string},newFilestore={description=string,fileShares=[{capacityGb=int,fileShare=string}],filestore=string,protocol=string,tier=string},newLustre={capacityGb=int,description=string,filesystem=string,lustre=string}}}} JSON Example: - --config='{"computeResources": {"string": {"newDwsFlexInstances": {"machineType": "string", "maxDuration": "string", "zone": "string"}, "newOnDemandInstances": {"machineType": "string", "zone": "string"}, "newReservedInstances": {"machineType": "string", "reservation": "string"}, "newSpotInstances": {"machineType": "string", "zone": "string"}}}, "description": "string", "labels": {"string": "string"}, "name": "string", "networkResources": {"string": {"config": {"existingNetwork": {"network": "string", "subnetwork": "string"}, "newNetwork": {"description": "string", "network": "string"}}}}, "orchestrator": {"slurm": {"defaultPartition": "string", "loginNodes": {"count": int, "disks": [{"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}], "enableOsLogin": boolean, "enablePublicIps": boolean, "labels": {"string": "string"}, "machineType": "string", "startupScript": "string", "storageConfigs": [{"id": "string", "localMount": "string"}], "zone": "string"}, "nodeSets": [{"bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "id": "string", "labels": {"string": "string"}, "maxDynamicNodeCount": int, "resourceRequestId": "string", "startupScript": "string", "staticNodeCount": int, "storageConfigs": [{"id": "string", "localMount": "string"}]}], "partitions": [{"exclusive": boolean, "id": "string", "nodeSetIds": ["string"]}]}}, "storageResources": {"string": {"config": {"existingBucket": {"bucket": "string"}, "existingFilestore": {"filestore": "string"}, "existingLustre": {"lustre": "string"}, "newBucket": {"autoclass": {"enabled": boolean}, "bucket": "string", "hierarchicalNamespace": {"enabled": boolean}, "storageClass": "string"}, "newFilestore": {"description": "string", "fileShares": [{"capacityGb": int, "fileShare": "string"}], "filestore": "string", "protocol": "string", "tier": "string"}, "newLustre": {"capacityGb": int, "description": "string", "filesystem": "string", "lustre": "string"}}}}}' + --config='{"computeResources": {"string": {"config": {"newDwsFlexInstances": {"machineType": "string", "maxDuration": "string", "zone": "string"}, "newFlexStartInstances": {"machineType": "string", "maxDuration": "string", "zone": "string"}, "newOnDemandInstances": {"machineType": "string", "zone": "string"}, "newReservedInstances": {"machineType": "string", "reservation": "string", "type": "string", "zone": "string"}, "newSpotInstances": {"machineType": "string", "zone": "string"}}}}, "description": "string", "labels": {"string": "string"}, "name": "string", "networkResources": {"string": {"config": {"existingNetwork": {"network": "string", "subnetwork": "string"}, "newNetwork": {"description": "string", "network": "string"}}}}, "orchestrator": {"slurm": {"defaultPartition": "string", "loginNodes": {"count": int, "disks": [{"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}], "enableOsLogin": boolean, "enablePublicIps": boolean, "labels": {"string": "string"}, "machineType": "string", "startupScript": "string", "storageConfigs": [{"id": "string", "localMount": "string"}], "zone": "string"}, "nodeSets": [{"bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "id": "string", "labels": {"string": "string"}, "maxDynamicNodeCount": int, "resourceRequestId": "string", "startupScript": "string", "staticNodeCount": int, "storageConfigs": [{"id": "string", "localMount": "string"}]}], "partitions": [{"exclusive": boolean, "id": "string", "nodeSetIds": ["string"]}]}}, "storageResources": {"string": {"config": {"existingBucket": {"bucket": "string"}, "existingFilestore": {"filestore": "string"}, "existingLustre": {"lustre": "string"}, "newBucket": {"autoclass": {"enabled": boolean}, "bucket": "string", "hierarchicalNamespace": {"enabled": boolean}, "storageClass": "string"}, "newFilestore": {"description": "string", "fileShares": [{"capacityGb": int, "fileShare": "string"}], "filestore": "string", "protocol": "string", "tier": "string"}, "newLustre": {"capacityGb": int, "description": "string", "filesystem": "string", "lustre": "string"}}}}}' File Example: diff --git a/gcloud/alpha/cluster-director/clusters/update b/gcloud/alpha/cluster-director/clusters/update index eda96161d..b5309727f 100644 --- a/gcloud/alpha/cluster-director/clusters/update +++ b/gcloud/alpha/cluster-director/clusters/update @@ -522,44 +522,65 @@ REQUIRED FLAGS VALUE Sets VALUE value. - newDwsFlexInstances - Sets newDwsFlexInstances value. + config + Sets config value. - machineType - Sets machineType value. + newDwsFlexInstances + Sets newDwsFlexInstances value. - maxDuration - Sets maxDuration value. + machineType + Sets machineType value. - zone - Sets zone value. + maxDuration + Sets maxDuration value. - newOnDemandInstances - Sets newOnDemandInstances value. + zone + Sets zone value. - machineType - Sets machineType value. + newFlexStartInstances + Sets newFlexStartInstances value. - zone - Sets zone value. + machineType + Sets machineType value. - newReservedInstances - Sets newReservedInstances value. + maxDuration + Sets maxDuration value. - machineType - Sets machineType value. + zone + Sets zone value. - reservation - Sets reservation value. + newOnDemandInstances + Sets newOnDemandInstances value. - newSpotInstances - Sets newSpotInstances value. + machineType + Sets machineType value. - machineType - Sets machineType value. + zone + Sets zone value. - zone - Sets zone value. + newReservedInstances + Sets newReservedInstances value. + + machineType + Sets machineType value. + + reservation + Sets reservation value. + + type + Sets type value. + + zone + Sets zone value. + + newSpotInstances + Sets newSpotInstances value. + + machineType + Sets machineType value. + + zone + Sets zone value. description Sets description value. @@ -824,11 +845,11 @@ REQUIRED FLAGS Shorthand Example: - --config=computeResources={string={newDwsFlexInstances={machineType=string,maxDuration=string,zone=string},newOnDemandInstances={machineType=string,zone=string},newReservedInstances={machineType=string,reservation=string},newSpotInstances={machineType=string,zone=string}}},description=string,labels={string=string},name=string,networkResources={string={config={existingNetwork={network=string,subnetwork=string},newNetwork={description=string,network=string}}}},orchestrator={slurm={defaultPartition=string,loginNodes={count=int,disks=[{boot=boolean,sizeGb=int,sourceImage=string,type=string}],enableOsLogin=boolean,enablePublicIps=boolean,labels={string=string},machineType=string,startupScript=string,storageConfigs=[{id=string,localMount=string}],zone=string},nodeSets=[{bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},id=string,labels={string=string},maxDynamicNodeCount=int,resourceRequestId=string,startupScript=string,staticNodeCount=int,storageConfigs=[{id=string,localMount=string}]}],partitions=[{exclusive=boolean,id=string,nodeSetIds=[string]}]}},storageResources={string={config={existingBucket={bucket=string},existingFilestore={filestore=string},existingLustre={lustre=string},newBucket={autoclass={enabled=boolean},bucket=string,hierarchicalNamespace={enabled=boolean},storageClass=string},newFilestore={description=string,fileShares=[{capacityGb=int,fileShare=string}],filestore=string,protocol=string,tier=string},newLustre={capacityGb=int,description=string,filesystem=string,lustre=string}}}} + --config=computeResources={string={config={newDwsFlexInstances={machineType=string,maxDuration=string,zone=string},newFlexStartInstances={machineType=string,maxDuration=string,zone=string},newOnDemandInstances={machineType=string,zone=string},newReservedInstances={machineType=string,reservation=string,type=string,zone=string},newSpotInstances={machineType=string,zone=string}}}},description=string,labels={string=string},name=string,networkResources={string={config={existingNetwork={network=string,subnetwork=string},newNetwork={description=string,network=string}}}},orchestrator={slurm={defaultPartition=string,loginNodes={count=int,disks=[{boot=boolean,sizeGb=int,sourceImage=string,type=string}],enableOsLogin=boolean,enablePublicIps=boolean,labels={string=string},machineType=string,startupScript=string,storageConfigs=[{id=string,localMount=string}],zone=string},nodeSets=[{bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},id=string,labels={string=string},maxDynamicNodeCount=int,resourceRequestId=string,startupScript=string,staticNodeCount=int,storageConfigs=[{id=string,localMount=string}]}],partitions=[{exclusive=boolean,id=string,nodeSetIds=[string]}]}},storageResources={string={config={existingBucket={bucket=string},existingFilestore={filestore=string},existingLustre={lustre=string},newBucket={autoclass={enabled=boolean},bucket=string,hierarchicalNamespace={enabled=boolean},storageClass=string},newFilestore={description=string,fileShares=[{capacityGb=int,fileShare=string}],filestore=string,protocol=string,tier=string},newLustre={capacityGb=int,description=string,filesystem=string,lustre=string}}}} JSON Example: - --config='{"computeResources": {"string": {"newDwsFlexInstances": {"machineType": "string", "maxDuration": "string", "zone": "string"}, "newOnDemandInstances": {"machineType": "string", "zone": "string"}, "newReservedInstances": {"machineType": "string", "reservation": "string"}, "newSpotInstances": {"machineType": "string", "zone": "string"}}}, "description": "string", "labels": {"string": "string"}, "name": "string", "networkResources": {"string": {"config": {"existingNetwork": {"network": "string", "subnetwork": "string"}, "newNetwork": {"description": "string", "network": "string"}}}}, "orchestrator": {"slurm": {"defaultPartition": "string", "loginNodes": {"count": int, "disks": [{"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}], "enableOsLogin": boolean, "enablePublicIps": boolean, "labels": {"string": "string"}, "machineType": "string", "startupScript": "string", "storageConfigs": [{"id": "string", "localMount": "string"}], "zone": "string"}, "nodeSets": [{"bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "id": "string", "labels": {"string": "string"}, "maxDynamicNodeCount": int, "resourceRequestId": "string", "startupScript": "string", "staticNodeCount": int, "storageConfigs": [{"id": "string", "localMount": "string"}]}], "partitions": [{"exclusive": boolean, "id": "string", "nodeSetIds": ["string"]}]}}, "storageResources": {"string": {"config": {"existingBucket": {"bucket": "string"}, "existingFilestore": {"filestore": "string"}, "existingLustre": {"lustre": "string"}, "newBucket": {"autoclass": {"enabled": boolean}, "bucket": "string", "hierarchicalNamespace": {"enabled": boolean}, "storageClass": "string"}, "newFilestore": {"description": "string", "fileShares": [{"capacityGb": int, "fileShare": "string"}], "filestore": "string", "protocol": "string", "tier": "string"}, "newLustre": {"capacityGb": int, "description": "string", "filesystem": "string", "lustre": "string"}}}}}' + --config='{"computeResources": {"string": {"config": {"newDwsFlexInstances": {"machineType": "string", "maxDuration": "string", "zone": "string"}, "newFlexStartInstances": {"machineType": "string", "maxDuration": "string", "zone": "string"}, "newOnDemandInstances": {"machineType": "string", "zone": "string"}, "newReservedInstances": {"machineType": "string", "reservation": "string", "type": "string", "zone": "string"}, "newSpotInstances": {"machineType": "string", "zone": "string"}}}}, "description": "string", "labels": {"string": "string"}, "name": "string", "networkResources": {"string": {"config": {"existingNetwork": {"network": "string", "subnetwork": "string"}, "newNetwork": {"description": "string", "network": "string"}}}}, "orchestrator": {"slurm": {"defaultPartition": "string", "loginNodes": {"count": int, "disks": [{"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}], "enableOsLogin": boolean, "enablePublicIps": boolean, "labels": {"string": "string"}, "machineType": "string", "startupScript": "string", "storageConfigs": [{"id": "string", "localMount": "string"}], "zone": "string"}, "nodeSets": [{"bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "id": "string", "labels": {"string": "string"}, "maxDynamicNodeCount": int, "resourceRequestId": "string", "startupScript": "string", "staticNodeCount": int, "storageConfigs": [{"id": "string", "localMount": "string"}]}], "partitions": [{"exclusive": boolean, "id": "string", "nodeSetIds": ["string"]}]}}, "storageResources": {"string": {"config": {"existingBucket": {"bucket": "string"}, "existingFilestore": {"filestore": "string"}, "existingLustre": {"lustre": "string"}, "newBucket": {"autoclass": {"enabled": boolean}, "bucket": "string", "hierarchicalNamespace": {"enabled": boolean}, "storageClass": "string"}, "newFilestore": {"description": "string", "fileShares": [{"capacityGb": int, "fileShare": "string"}], "filestore": "string", "protocol": "string", "tier": "string"}, "newLustre": {"capacityGb": int, "description": "string", "filesystem": "string", "lustre": "string"}}}}}' File Example: diff --git a/gcloud/alpha/compute/health-sources/create b/gcloud/alpha/compute/health-sources/create new file mode 100644 index 000000000..04089847d --- /dev/null +++ b/gcloud/alpha/compute/health-sources/create @@ -0,0 +1,103 @@ +NAME + gcloud alpha compute health-sources create - create a health source + +SYNOPSIS + gcloud alpha compute health-sources create + (HEALTH_SOURCE : --region=REGION) + --health-aggregation-policy=HEALTH_AGGREGATION_POLICY + --sources=[SOURCES,...] [--async] [--description=DESCRIPTION] + [--source-type=SOURCE_TYPE; default="backend-service"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a health source. + +EXAMPLES + The following command creates a new health source: + + $ gcloud alpha compute health-sources create \ + --region= --source-type=BACKEND_SERVICE \ + --sources=my-backend-service \ + --health-aggregation-policy=my-health-aggregation-policy + +POSITIONAL ARGUMENTS + Health source resource - The name of the health source you want to create. + The arguments in this group can be used to specify the attributes of this + 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 health_source on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_SOURCE + ID of the health source or fully qualified identifier for the health + source. + + To set the health_source attribute: + ▸ provide the argument health_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_source on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + --health-aggregation-policy=HEALTH_AGGREGATION_POLICY + URL to the health aggregation policy resource. Must be set. Must be + regional and in the same region as the HealthSource. Can be mutated. + + --sources=[SOURCES,...] + URLs to the source resources. Must be size 1. Must be a BackendService + if the sourceType is BACKEND_SERVICE. The BackendService must have load + balancing scheme INTERNAL or INTERNAL_MANAGED and must be regional and + in the same region as the HealthSource (cross-region deployment for + INTERNAL_MANAGED is not supported). The BackendService may use only + IGs, MIGs, or NEGs of type GCE_VM_IP or GCE_VM_IP_PORT. The + BackendService may not use haPolicy. Can be mutated. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A textual description of the HealthSource. + + --source-type=SOURCE_TYPE; default="backend-service" + Specifies the type of the HealthSource. The only allowed value is + BACKEND_SERVICE. Must be specified when the HealthSource is created, + and cannot be mutated. SOURCE_TYPE must be (only one value is + supported): backend-service. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute health-sources create + diff --git a/gcloud/alpha/compute/health-sources/delete b/gcloud/alpha/compute/health-sources/delete new file mode 100644 index 000000000..be4ae97a3 --- /dev/null +++ b/gcloud/alpha/compute/health-sources/delete @@ -0,0 +1,74 @@ +NAME + gcloud alpha compute health-sources delete - delete a health source + +SYNOPSIS + gcloud alpha compute health-sources delete + (HEALTH_SOURCE : --region=REGION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a health source. + +EXAMPLES + To delete a single health source, run the following command: + + $ gcloud alpha compute health-sources delete \ + --region= + +POSITIONAL ARGUMENTS + Health source resource - Name of the health source you want to delete. The + arguments in this group can be used to specify the attributes of this + 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 health_source on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_SOURCE + ID of the health source or fully qualified identifier for the health + source. + + To set the health_source attribute: + ▸ provide the argument health_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_source on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute health-sources delete + diff --git a/gcloud/alpha/compute/health-sources/describe b/gcloud/alpha/compute/health-sources/describe new file mode 100644 index 000000000..4ea00b2f8 --- /dev/null +++ b/gcloud/alpha/compute/health-sources/describe @@ -0,0 +1,70 @@ +NAME + gcloud alpha compute health-sources describe - describe a health source + +SYNOPSIS + gcloud alpha compute health-sources describe + (HEALTH_SOURCE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a health source. + +EXAMPLES + To retrieve a single health source and print its properties, run the + following command: + + $ gcloud alpha compute health-sources describe \ + --region= + +POSITIONAL ARGUMENTS + Health source resource - Name of the health source you want to inspect. + The arguments in this group can be used to specify the attributes of this + 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 health_source on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_SOURCE + ID of the health source or fully qualified identifier for the health + source. + + To set the health_source attribute: + ▸ provide the argument health_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_source on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute health-sources describe + diff --git a/gcloud/alpha/compute/health-sources/help b/gcloud/alpha/compute/health-sources/help new file mode 100644 index 000000000..db3c95e24 --- /dev/null +++ b/gcloud/alpha/compute/health-sources/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha compute health-sources - manage health sources + +SYNOPSIS + gcloud alpha compute health-sources COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage health sources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a health source. + + delete + (ALPHA) Delete a health source. + + describe + (ALPHA) Describe a health source. + + list + (ALPHA) List health sources. + + update + (ALPHA) Update a health source. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute health-sources + diff --git a/gcloud/alpha/compute/health-sources/list b/gcloud/alpha/compute/health-sources/list new file mode 100644 index 000000000..322185127 --- /dev/null +++ b/gcloud/alpha/compute/health-sources/list @@ -0,0 +1,79 @@ +NAME + gcloud alpha compute health-sources list - list health sources + +SYNOPSIS + gcloud alpha compute health-sources list [NAME ...] + [--regexp=REGEXP, -r REGEXP] [--regions=REGION,[REGION,...]] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List health sources. + +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. + + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. + +FLAGS + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. + + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + + --regions=REGION,[REGION,...] + If provided, only resources from the given regions are queried. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute health-sources list + diff --git a/gcloud/alpha/compute/health-sources/update b/gcloud/alpha/compute/health-sources/update new file mode 100644 index 000000000..835028658 --- /dev/null +++ b/gcloud/alpha/compute/health-sources/update @@ -0,0 +1,99 @@ +NAME + gcloud alpha compute health-sources update - update a health source + +SYNOPSIS + gcloud alpha compute health-sources update + (HEALTH_SOURCE : --region=REGION) + (--description=DESCRIPTION + --health-aggregation-policy=HEALTH_AGGREGATION_POLICY + --sources=[SOURCES,...]) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a health source. + +EXAMPLES + The following command updates a new health source named "my-health-source": + + $ gcloud alpha compute health-sources update \ + --region= --source-type=BACKEND_SERVICE \ + --sources=my-backend-service \ + --health-aggregation-policy=my-health-aggregation-policy + +POSITIONAL ARGUMENTS + Health source resource - The name of the health source you want to create. + The arguments in this group can be used to specify the attributes of this + 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 health_source on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_SOURCE + ID of the health source or fully qualified identifier for the health + source. + + To set the health_source attribute: + ▸ provide the argument health_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_source on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + At least one of these must be specified: + + --description=DESCRIPTION + A textual description of the health source. + + --health-aggregation-policy=HEALTH_AGGREGATION_POLICY + URL to the health aggregation policy resource. Must be set. Must be + regional and in the same region as the HealthSource. Can be mutated. + + --sources=[SOURCES,...] + URLs to the source resources. Must be size 1. Must be a + BackendService if the sourceType is BACKEND_SERVICE. The + BackendService must have load balancing scheme INTERNAL or + INTERNAL_MANAGED and must be regional and in the same region as the + HealthSource (cross-region deployment for INTERNAL_MANAGED is not + supported). The BackendService may use only IGs, MIGs, or NEGs of + type GCE_VM_IP or GCE_VM_IP_PORT. The BackendService may not use + haPolicy. Can be mutated. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/alpha API. The full documentation for this + API can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta compute health-sources update + diff --git a/gcloud/alpha/compute/help b/gcloud/alpha/compute/help index 6d42e16bf..55ab99e7b 100644 --- a/gcloud/alpha/compute/help +++ b/gcloud/alpha/compute/help @@ -74,6 +74,9 @@ GROUPS health-checks (ALPHA) Read and manipulate health checks for load balanced instances. + health-sources + (ALPHA) Manage health sources. + http-health-checks (ALPHA) Read and manipulate HTTP health checks for load balanced instances. diff --git a/gcloud/alpha/compute/migration/disk-migrations/cancel b/gcloud/alpha/compute/migration/disk-migrations/cancel new file mode 100644 index 000000000..97949c6b7 --- /dev/null +++ b/gcloud/alpha/compute/migration/disk-migrations/cancel @@ -0,0 +1,78 @@ +NAME + gcloud alpha compute migration disk-migrations cancel - cancel a disk + migration resource process + +SYNOPSIS + gcloud alpha compute migration disk-migrations cancel + (DISK_MIGRATION : --location=LOCATION --source=SOURCE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute migration disk-migrations cancel cancels an + ongoing disk migration resource process. To use this command, you must + enable VM Migration API in your project. + +EXAMPLES + To cancel an ongoing my-disk-migration resource process in us-central1 in + the AWS source my-aws-source in the default project, run: $ gcloud alpha compute migration disk-migrations cancel \ + my-disk-migration --location=us-central1 --source=my-aws-source + +POSITIONAL ARGUMENTS + Disk migration resource - The disk migration resource you want to cancel + its ongoing process. The arguments in this group can be used to specify + the attributes of this 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 disk_migration on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DISK_MIGRATION + ID of the disk_migration or fully qualified identifier for the + disk_migration. + + To set the disk_migration attribute: + ▸ provide the argument disk_migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --source=SOURCE + The client source environment object. + + To set the source attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --source on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/migration/disk-migrations/create b/gcloud/alpha/compute/migration/disk-migrations/create new file mode 100644 index 000000000..4005616a1 --- /dev/null +++ b/gcloud/alpha/compute/migration/disk-migrations/create @@ -0,0 +1,134 @@ +NAME + gcloud alpha compute migration disk-migrations create - create a disk + migration resource to migrate a disk to Compute Engine + +SYNOPSIS + gcloud alpha compute migration disk-migrations create + (DISK_MIGRATION : --location=LOCATION --source=SOURCE) + --source-volume-id=SOURCE_VOLUME_ID [--disk-id=DISK_ID] + [--disk-type=DISK_TYPE] [--kms-key=KMS_KEY] [--labels=[KEY=VALUE,...]] + [--target-project=TARGET_PROJECT] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute migration disk-migrations create lets you + create disk migration resource. You must create a disk migration resource + before you can migrate your disk from any migration source to a Compute + Engine disk. The disk migration resource tracks the progress of the disk + migration. To use this command, you must enable VM Migration API in your + project. + + Note that this command only creates a disk migration resource. It does not + initiate the disk migration process. After creating the disk migration + resource, you must initiate the migration process using the run command. + +EXAMPLES + To create a disk migration resource to migrate a volume vol-12345 from an + AWS source my-aws-source to my-target-project in us-central1, create the + my-disk-migration disk migration resource in my-project in us-central1, + run: + + $ gcloud alpha compute migration disk-migrations create \ + my-disk-migration --project=my-project --location=us-central1 \ + --source=my-aws-source --source-volume-id=vol-12345 \ + --disk-id=gcp-disk1 \ + --target-project=projects/my-project/locations/global/\ + targetProjects/my-target-project + +POSITIONAL ARGUMENTS + Disk migration resource - The disk migration resource you want to create. + This would be the disk ID if --disk-id is not given. The arguments in this + group can be used to specify the attributes of this 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 disk_migration on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DISK_MIGRATION + ID of the disk_migration or fully qualified identifier for the + disk_migration. + + To set the disk_migration attribute: + ▸ provide the argument disk_migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --source=SOURCE + The client source environment object. + + To set the source attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --source on the command line. + +REQUIRED FLAGS + --source-volume-id=SOURCE_VOLUME_ID + The ID of the source volume that you want to migrate to Compute Engine. + +OPTIONAL FLAGS + --disk-id=DISK_ID + The ID of the disk that will be migrated to Compute Engine. The default + value is the disk migration resource name. + + --disk-type=DISK_TYPE + The Compute Engine disk type to use for the migrated disk. The default + value is COMPUTE_ENGINE_DISK_TYPE_STANDARD. DISK_TYPE must be one of: + + compute-engine-disk-type-balanced + Compute Engine Disk Type Balanced. + compute-engine-disk-type-hyperdisk-balanced + Compute Engine Disk Type hyperdisk-balanced. + compute-engine-disk-type-ssd + Compute Engine Disk Type SSD. + compute-engine-disk-type-standard + Compute Engine Disk Type Standard. + + --kms-key=KMS_KEY + Fully qualified identifier for the Cloud KMS (Key Management Service) + cryptokey that will be used to protect the disk. + + --labels=[KEY=VALUE,...] + A map of labels to associate with the disk. + + --target-project=TARGET_PROJECT + The target project resource path to which the disk will be migrated. + Default is the host project. To get a list of the target projects run + the gcloud alpha migration vms target-projects list command. + + --zone=ZONE + The zone in which to create the disk. The default value is the first + zone of the Google Cloud location parameter given. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/migration/disk-migrations/delete b/gcloud/alpha/compute/migration/disk-migrations/delete new file mode 100644 index 000000000..115e26a9a --- /dev/null +++ b/gcloud/alpha/compute/migration/disk-migrations/delete @@ -0,0 +1,82 @@ +NAME + gcloud alpha compute migration disk-migrations delete - delete a disk + migration resource + +SYNOPSIS + gcloud alpha compute migration disk-migrations delete + (DISK_MIGRATION : --location=LOCATION --source=SOURCE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute migration disk-migrations delete deletes a + disk migration resource. To use this command, you must enable VM Migration + API in your project. + + This command does not delete any disks on Google Compute Engine. + +EXAMPLES + To delete my-disk-migration resource in us-central1 in the AWS source + my-aws-source in the default project, run: + + $ gcloud alpha compute migration disk-migrations delete \ + my-image-import --location=us-central1 --source=my-aws-source + +POSITIONAL ARGUMENTS + Disk migration resource - The disk migration resource you want to delete. + The arguments in this group can be used to specify the attributes of this + 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 disk_migration on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DISK_MIGRATION + ID of the disk_migration or fully qualified identifier for the + disk_migration. + + To set the disk_migration attribute: + ▸ provide the argument disk_migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --source=SOURCE + The client source environment object. + + To set the source attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --source on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/migration/disk-migrations/describe b/gcloud/alpha/compute/migration/disk-migrations/describe new file mode 100644 index 000000000..2fba5e18d --- /dev/null +++ b/gcloud/alpha/compute/migration/disk-migrations/describe @@ -0,0 +1,81 @@ +NAME + gcloud alpha compute migration disk-migrations describe - describe a disk + migration resource + +SYNOPSIS + gcloud alpha compute migration disk-migrations describe + (DISK_MIGRATION : --location=LOCATION --source=SOURCE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute migration disk-migrations describe describes a + disk migration resource. The disk migration resource tracks the disk + migration progress. To use this command, you must enable VM Migration API + in your project. + +EXAMPLES + To describe my-disk-migration resource in us-central1 in the AWS source + my-aws-source in the default project, run: + + $ gcloud alpha compute migration disk-migrations describe \ + my-disk-migration --location=us-central1 --source=my-aws-source + +POSITIONAL ARGUMENTS + Disk migration resource - The disk migration resource you want to + describe. The arguments in this group can be used to specify the + attributes of this 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 disk_migration on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DISK_MIGRATION + ID of the disk_migration or fully qualified identifier for the + disk_migration. + + To set the disk_migration attribute: + ▸ provide the argument disk_migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --source=SOURCE + The client source environment object. + + To set the source attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --source on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/migration/disk-migrations/fetch-inventory b/gcloud/alpha/compute/migration/disk-migrations/fetch-inventory new file mode 100644 index 000000000..e08a5c262 --- /dev/null +++ b/gcloud/alpha/compute/migration/disk-migrations/fetch-inventory @@ -0,0 +1,105 @@ +NAME + gcloud alpha compute migration disk-migrations fetch-inventory - lists + source environment volume inventory + +SYNOPSIS + gcloud alpha compute migration disk-migrations fetch-inventory + (SOURCE : --location=LOCATION) [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute migration disk-migrations fetch-inventory + prints a detailed list of the source environment volume inventory. To use + this command, you must enable VM Migration API in your project. + +EXAMPLES + To list the source environment volume resources in us-central1 in the AWS + source my-aws-source in the default project, run: + + $ gcloud alpha compute migration disk-migrations fetch-inventory \ + my-aws-source --location=us-central1 + +POSITIONAL ARGUMENTS + Source resource - The source environment resource of the disk migration + resources. This is the parent resource of the disk migration resources. + The arguments in this group can be used to specify the attributes of this + 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 on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + SOURCE + ID of the source or fully qualified identifier for the source. + + To set the source attribute: + ▸ provide the argument source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument source on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/migration/disk-migrations/help b/gcloud/alpha/compute/migration/disk-migrations/help new file mode 100644 index 000000000..54d54954a --- /dev/null +++ b/gcloud/alpha/compute/migration/disk-migrations/help @@ -0,0 +1,71 @@ +NAME + gcloud alpha compute migration disk-migrations - migrates disks to Compute + Engine + +SYNOPSIS + gcloud alpha compute migration disk-migrations COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The gcloud alpha migration vms disk-migrations command lets you + create and manage disk migration resource. You must create a disk migration + resource before you can migrate your disk from any migration source to a + Compute Engine disk. The disk migration resource tracks the progress of the + disk migration. To use this command, you must enable VM Migration API in + your project. + + Note that this command only creates a disk migration resource. It does not + initiate the disk migration process. After creating the disk migration + resource, you must initiate the migration process using the run command. + + The disk is migrated to a Google Cloud Project, designated by the Target + Project resource. To get a list of Target Projects, run the gcloud alpha + migration vms target-projects list command. For information on adding + target projects, see + https://cloud.google.com/migrate/virtual-machines/docs/5.0/how-to/target-project. + + A project can support a maximum of 200 Disk/VM Migration active resources + per project; 1000 ready disk migration resources, and 500 finished disk + migration resources. Hence we recommend that you delete a completed disk + migrations to avoid reaching the disk migration resources limit. Deletion + of disk migration resource does not affect the migrated disk. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancel a disk migration resource process. + + create + (ALPHA) Create a disk migration resource to migrate a disk to Compute + Engine. + + delete + (ALPHA) Delete a disk migration resource. + + describe + (ALPHA) Describe a disk migration resource. + + fetch-inventory + (ALPHA) Lists source environment volume inventory. + + list + (ALPHA) List disk migration resources. + + run + (ALPHA) Run a disk migration resource process. + + update + (ALPHA) Update a disk migration resource target details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/migration/disk-migrations/list b/gcloud/alpha/compute/migration/disk-migrations/list new file mode 100644 index 000000000..e7bb2e7d2 --- /dev/null +++ b/gcloud/alpha/compute/migration/disk-migrations/list @@ -0,0 +1,105 @@ +NAME + gcloud alpha compute migration disk-migrations list - list disk migration + resources + +SYNOPSIS + gcloud alpha compute migration disk-migrations list + (--source=SOURCE : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute migration disk-migrations list prints a + detailed list of disk migration resources. To use this command, you must + enable VM Migration API in your project. + +EXAMPLES + To list the disk migration resources in us-central1 in the AWS source + my-aws-source in the default project, run: + + $ gcloud alpha compute migration disk-migrations list \ + --location=us-central1 --source=my-aws-source + +REQUIRED FLAGS + Source resource - The source environment resource of the disk migration + resources. This is the parent resource of the disk migration resources. + The arguments in this group can be used to specify the attributes of this + 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 on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --source=SOURCE + ID of the source or fully qualified identifier for the source. + + To set the source attribute: + ▸ provide the argument --source on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument --source on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/migration/disk-migrations/run b/gcloud/alpha/compute/migration/disk-migrations/run new file mode 100644 index 000000000..cc3d4afed --- /dev/null +++ b/gcloud/alpha/compute/migration/disk-migrations/run @@ -0,0 +1,78 @@ +NAME + gcloud alpha compute migration disk-migrations run - run a disk migration + resource process + +SYNOPSIS + gcloud alpha compute migration disk-migrations run + (DISK_MIGRATION : --location=LOCATION --source=SOURCE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute migration disk-migrations run initiates a disk + migration resource process. To use this command, you must enable VM + Migration API in your project. + +EXAMPLES + To run my-disk-migration resource process in us-central1 in the AWS source + my-aws-source in the default project, run: $ gcloud alpha compute migration disk-migrations run \ + my-disk-migration --location=us-central1 --source=my-aws-source + +POSITIONAL ARGUMENTS + Disk migration resource - The disk migration resource you want to initiate + its process. The arguments in this group can be used to specify the + attributes of this 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 disk_migration on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DISK_MIGRATION + ID of the disk_migration or fully qualified identifier for the + disk_migration. + + To set the disk_migration attribute: + ▸ provide the argument disk_migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --source=SOURCE + The client source environment object. + + To set the source attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --source on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/migration/disk-migrations/update b/gcloud/alpha/compute/migration/disk-migrations/update new file mode 100644 index 000000000..4f2f4f0b1 --- /dev/null +++ b/gcloud/alpha/compute/migration/disk-migrations/update @@ -0,0 +1,117 @@ +NAME + gcloud alpha compute migration disk-migrations update - update a disk + migration resource target details + +SYNOPSIS + gcloud alpha compute migration disk-migrations update + (DISK_MIGRATION : --location=LOCATION --source=SOURCE) + [--disk-id=DISK_ID] [--disk-type=DISK_TYPE] [--kms-key=KMS_KEY] + [--labels=[KEY=VALUE,...]] [--target-project=TARGET_PROJECT] + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute migration disk-migrations update updates a + disk migration resource. To use this command, you must enable VM Migration + API in your project. + +EXAMPLES + To update a disk migration resource my-disk-migration from AWS source + my-aws-source disk type to pd-ssd, run: + + $ gcloud alpha compute migration disk-migrations update \ + my-disk-migration --project=my-project --location=us-central1 \ + --source=my-aws-source --disk-type=COMPUTE_ENGINE_DISK_TYPE_SSD + +POSITIONAL ARGUMENTS + Disk migration resource - The disk migration resource you want to udpate. + The arguments in this group can be used to specify the attributes of this + 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 disk_migration on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DISK_MIGRATION + ID of the disk_migration or fully qualified identifier for the + disk_migration. + + To set the disk_migration attribute: + ▸ provide the argument disk_migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --source=SOURCE + The client source environment object. + + To set the source attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --source on the command line. + +FLAGS + --disk-id=DISK_ID + The ID of the disk that will be migrated to Compute Engine. The default + value is the disk migration resource name. + + --disk-type=DISK_TYPE + The Compute Engine disk type to use for the migrated disk. The default + value is COMPUTE_ENGINE_DISK_TYPE_STANDARD. DISK_TYPE must be one of: + + compute-engine-disk-type-balanced + Compute Engine Disk Type Balanced. + compute-engine-disk-type-hyperdisk-balanced + Compute Engine Disk Type hyperdisk-balanced. + compute-engine-disk-type-ssd + Compute Engine Disk Type SSD. + compute-engine-disk-type-standard + Compute Engine Disk Type Standard. + + --kms-key=KMS_KEY + Fully qualified identifier for the Cloud KMS (Key Management Service) + cryptokey that will be used to protect the disk. + + --labels=[KEY=VALUE,...] + A map of labels to associate with the disk. + + --target-project=TARGET_PROJECT + The target project resource path to which the disk will be migrated. + Default is the host project. To get a list of the target projects run + the gcloud alpha migration vms target-projects list command. + + --zone=ZONE + The zone in which to create the disk. The default value is the first + zone of the Google Cloud location parameter given. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/migration/help b/gcloud/alpha/compute/migration/help index f03651034..371626526 100644 --- a/gcloud/alpha/compute/migration/help +++ b/gcloud/alpha/compute/migration/help @@ -20,6 +20,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + disk-migrations + (ALPHA) Migrates disks to Compute Engine. + image-imports (ALPHA) Imports images to Google Compute Engine from Google Cloud Storage. diff --git a/gcloud/alpha/compute/reservations/sub-blocks/describe b/gcloud/alpha/compute/reservations/sub-blocks/describe index 47eceedcb..9fc79e776 100644 --- a/gcloud/alpha/compute/reservations/sub-blocks/describe +++ b/gcloud/alpha/compute/reservations/sub-blocks/describe @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha compute reservations sub-blocks describe RESERVATION - --block-name=BLOCK_NAME --sub-block-name=SUB_BLOCK_NAME [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] + --block-name=BLOCK_NAME --sub-block-name=SUB_BLOCK_NAME + [--full-view=FULL_VIEW; default="SUB_BLOCK_VIEW_UNSPECIFIED"] + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Describe a Compute Engine reservation sub-block. @@ -30,6 +31,14 @@ REQUIRED FLAGS The name of the reservation sub block. OPTIONAL FLAGS + --full-view=FULL_VIEW; default="SUB_BLOCK_VIEW_UNSPECIFIED" + The view type for the reservation sub-block. FULL_VIEW must be one of: + + SUB_BLOCK_VIEW_BASIC + Basic default view of the reservation sub-block. + SUB_BLOCK_VIEW_FULL + Full detailed view of the reservation sub-block. + --zone=ZONE Zone of the reservation to describe. If not specified and the compute/zone property isn't set, you might be prompted to select a zone diff --git a/gcloud/alpha/compute/routers/create b/gcloud/alpha/compute/routers/create index b43e5ca9f..1dec48d73 100644 --- a/gcloud/alpha/compute/routers/create +++ b/gcloud/alpha/compute/routers/create @@ -101,7 +101,11 @@ OPTIONAL FLAGS CLOUDSDK_COMPUTE_REGION. --resource-manager-tags=[KEY=VALUE,...] - A comma-separated list of Resource Manager tags to apply to the router. + Comma-separated list of Resource Manager tags to attach to the router. + Key-value pairs must be provided in the form + tagKeys/{TagKey_Numeric_ID}=tagValues/{TagValue_Numeric_ID}. See + Listing tag keys + (https://cloud.google.com/resource-manager/docs/tags/tags-creating-and-managing#listing_keys). --set-advertisement-groups=[GROUP,...] The list of pre-defined groups of IP ranges to dynamically advertise on diff --git a/gcloud/alpha/compute/security-policies/update b/gcloud/alpha/compute/security-policies/update index aff58f73d..75520c7f2 100644 --- a/gcloud/alpha/compute/security-policies/update +++ b/gcloud/alpha/compute/security-policies/update @@ -15,11 +15,12 @@ SYNOPSIS [--layer7-ddos-defense-rule-visibility=VISIBILITY_TYPE] [--log-level=LOG_LEVEL] [--network-ddos-adaptive-protection=NETWORK_DDOS_ADAPTIVE_PROTECTION] - [--network-ddos-impacted-baseline-threshold=NETWORK_DDOS_IMPACTED_BASELINE_THRESHOLD] [--network-ddos-protection=NETWORK_DDOS_PROTECTION] [--recaptcha-redirect-site-key=RECAPTCHA_REDIRECT_SITE_KEY] [--request-body-inspection-size=REQUEST_BODY_INSPECTION_SIZE] [--user-ip-request-headers=[USER_IP_REQUEST_HEADER,...]] + [--clear-network-ddos-impacted-baseline-threshold + | --network-ddos-impacted-baseline-threshold=NETWORK_DDOS_IMPACTED_BASELINE_THRESHOLD] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -91,10 +92,6 @@ FLAGS instances with external IPs. NETWORK_DDOS_ADAPTIVE_PROTECTION must be one of: DISABLED, ENABLED, PREVIEW. - --network-ddos-impacted-baseline-threshold=NETWORK_DDOS_IMPACTED_BASELINE_THRESHOLD - Threshold below which rules with collateral damage below this value - will be deployed - --network-ddos-protection=NETWORK_DDOS_PROTECTION The DDoS protection level for network load balancing and instances with external IPs. NETWORK_DDOS_PROTECTION must be one of: STANDARD, @@ -112,6 +109,16 @@ FLAGS A comma-separated list of request header names to use for resolving the caller's user IP address. + At most one of these can be specified: + + --clear-network-ddos-impacted-baseline-threshold + If provided, clears the Network DDoS impacted baseline threshold from + the security policy. + + --network-ddos-impacted-baseline-threshold=NETWORK_DDOS_IMPACTED_BASELINE_THRESHOLD + Threshold below which rules with collateral damage below this value + will be deployed + At most one of these can be specified: --global diff --git a/gcloud/alpha/compute/tpus/create b/gcloud/alpha/compute/tpus/create index 29abcbd10..5c9346e05 100644 --- a/gcloud/alpha/compute/tpus/create +++ b/gcloud/alpha/compute/tpus/create @@ -11,7 +11,10 @@ SYNOPSIS --platform-config-file=PLATFORM_CONFIG_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create a new Cloud TPU. + (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm create instead. + + Create a new Cloud TPU. EXAMPLES The following command creates a TPU with ID my-tpu in the default user diff --git a/gcloud/alpha/compute/tpus/delete b/gcloud/alpha/compute/tpus/delete index b62f3324f..537cf9a87 100644 --- a/gcloud/alpha/compute/tpus/delete +++ b/gcloud/alpha/compute/tpus/delete @@ -6,7 +6,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Deletes a Cloud TPU. + (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm delete instead. + + Deletes a Cloud TPU. EXAMPLES The following command deletes a TPU with ID my-tpu in zone us-central1-b: diff --git a/gcloud/alpha/compute/tpus/describe b/gcloud/alpha/compute/tpus/describe index dc621af9d..2e1647303 100644 --- a/gcloud/alpha/compute/tpus/describe +++ b/gcloud/alpha/compute/tpus/describe @@ -6,7 +6,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe a Cloud TPU. + (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm describe instead. + + Describe a Cloud TPU. EXAMPLES The following command describes a TPU with ID my-tpu in zone us-central1-b: diff --git a/gcloud/alpha/compute/tpus/help b/gcloud/alpha/compute/tpus/help index 8277db021..06f608831 100644 --- a/gcloud/alpha/compute/tpus/help +++ b/gcloud/alpha/compute/tpus/help @@ -50,25 +50,25 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create a new Cloud TPU. + (ALPHA) (DEPRECATED) Create a new Cloud TPU. delete - (ALPHA) Deletes a Cloud TPU. + (ALPHA) (DEPRECATED) Deletes a Cloud TPU. describe - (ALPHA) Describe a Cloud TPU. + (ALPHA) (DEPRECATED) Describe a Cloud TPU. list - (ALPHA) List Cloud TPUs. + (ALPHA) (DEPRECATED) List Cloud TPUs. reimage - (ALPHA) Reimages the OS on a Cloud TPU. + (ALPHA) (DEPRECATED) Reimages the OS on a Cloud TPU. start - (ALPHA) Start a Cloud TPU. + (ALPHA) (DEPRECATED) Start a Cloud TPU. stop - (ALPHA) Stop a Cloud TPU. + (ALPHA) (DEPRECATED) Stop a Cloud TPU. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/compute/tpus/list b/gcloud/alpha/compute/tpus/list index 1cb2cfcec..3ac9976c9 100644 --- a/gcloud/alpha/compute/tpus/list +++ b/gcloud/alpha/compute/tpus/list @@ -7,7 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Cloud TPUs + (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm list instead. + + List Cloud TPUs EXAMPLES The following command lists the status of TPUs in zone us-central1-b: diff --git a/gcloud/alpha/compute/tpus/reimage b/gcloud/alpha/compute/tpus/reimage index b918f8bac..c9c9537d0 100644 --- a/gcloud/alpha/compute/tpus/reimage +++ b/gcloud/alpha/compute/tpus/reimage @@ -6,7 +6,10 @@ SYNOPSIS [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Reimages the OS on a Cloud TPU. + (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm reimage instead. + + Reimages the OS on a Cloud TPU. EXAMPLES The following command reimages a TPU with ID my-tpu in zone us-central1-b diff --git a/gcloud/alpha/compute/tpus/start b/gcloud/alpha/compute/tpus/start index 48ddee5b9..6449a30bd 100644 --- a/gcloud/alpha/compute/tpus/start +++ b/gcloud/alpha/compute/tpus/start @@ -6,7 +6,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Start a Cloud TPU. + (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm start instead. + + Start a Cloud TPU. EXAMPLES The following command starts a TPU with ID my-tpu in zone us-central1-b: diff --git a/gcloud/alpha/compute/tpus/stop b/gcloud/alpha/compute/tpus/stop index b96b2c65b..58131d0a3 100644 --- a/gcloud/alpha/compute/tpus/stop +++ b/gcloud/alpha/compute/tpus/stop @@ -6,7 +6,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Stop a Cloud TPU. + (ALPHA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm stop instead. + + Stop a Cloud TPU. EXAMPLES The following command stops a TPU with ID my-tpu in zone us-central1-b: diff --git a/gcloud/alpha/container/attached/clusters/register b/gcloud/alpha/container/attached/clusters/register index aeeb34492..9121e6d3d 100644 --- a/gcloud/alpha/container/attached/clusters/register +++ b/gcloud/alpha/container/attached/clusters/register @@ -14,7 +14,8 @@ SYNOPSIS [--description=DESCRIPTION] [--enable-managed-prometheus] [--logging=COMPONENT,[COMPONENT,...]] [--system-component-labels=[LABEL,...]] - [--system-component-tolerations=[TOLERATION,...]] [--validate-only] + [--system-component-tolerations=[TOLERATION,...]] + [--tags=TAG,[TAG,...]] [--validate-only] [--disable-cloud-monitoring | --enable-cloud-monitoring] [--proxy-secret-name=PROXY_SECRET_NAME --proxy-secret-namespace=PROXY_SECRET_NAMESPACE] @@ -201,6 +202,14 @@ OPTIONAL FLAGS --system-component-tolerations=[TOLERATION,...] Kubernetes tolerations to be applied to system component pods. + --tags=TAG,[TAG,...] + Tag keys/values directly bound to this resource. + + The short name of a tag key or value can have a maximum length of 256 + characters. The permitted character set for the short name includes + UTF-8 encoded Unicode characters except single quotes, double quotes, + backslashes, and forward slashes. + --validate-only Validate the cluster to create, but don't actually perform it. diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 5b3be496d..b1ee2fbf3 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -194,15 +194,14 @@ FLAGS (Optional) The NVIDIA driver version to install. GPU_DRIVER_VERSION must be one of: - `default`: Install the default driver version for this GKE version. + `default`: Install the default driver version for this GKE version. For GKE version 1.30.1-gke.1156000 and later, this is the default option. `latest`: Install the latest driver version available for this GKE version. Can only be used for nodes that use Container-Optimized OS. `disabled`: Skip automatic driver installation. You must manually install a - driver after you create the cluster. If you omit the flag `gpu-driver-version`, - this is the default option. To learn how to manually install the GPU driver, - refer to: https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers + driver after you create the cluster. For GKE version 1.30.1-gke.1156000 and earlier, this is the default option. + To manually install the GPU driver, refer to https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers. gpu-partition-size (Optional) The GPU partition size used when running multi-instance @@ -1096,9 +1095,11 @@ FLAGS $ gcloud alpha container clusters create example-cluster \ --node-labels=label-a=value1,label-2=value2 - New nodes, including ones created by resize or recreate, will have - these labels on the Kubernetes API node object and can be used in - nodeSelectors. See + Updating the node pool's --node-labels flag applies the labels to the + Kubernetes Node objects for existing nodes in-place; it does not + re-create or replace nodes. New nodes, including ones created by + resizing or re-creating nodes, will have these labels on the Kubernetes + API Node object. The labels can be used in the nodeSelector field. See https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ for examples. @@ -1605,8 +1606,18 @@ FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1, 2} + net.ipv4.tcp_mtu_probing Must be {0, 1, 2} net.ipv4.tcp_max_orphans Must be between [16384, 262144] + net.ipv4.tcp_max_tw_buckets Must be between + [4096, 2147483647] + net.ipv4.tcp_syn_retries Must be between + [1, 127] + net.ipv4.tcp_ecn Must be {0, 1, 2} + net.ipv4.tcp_congestion_control Must be string + containing only + letters and + numbers net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -1632,6 +1643,16 @@ FLAGS [0, 184467440736927743 99] + kernel.perf_event_paranoid Must be {-1, 0, 1, + 2, 3} + kernel.sched_rt_runtime_us Must be [-1, + 1000000] + kernel.softlockup_panic Must be {0, 1} + kernel.yama.ptrace_scope Must be {0, 1, 2, + 3} + kernel.kptr_restrict Must be {0, 1, 2} + kernel.dmesg_restrict Must be {0, 1} + kernel.sysrq Must be [0, 511] fs.aio-max-nr Must be between [65536, 4194304] fs.file-max Must be between @@ -1645,10 +1666,14 @@ FLAGS 2147483584] vm.dirty_background_ratio Must be between [1, 100] + vm.dirty_background_bytes Must be between + [0, 68719476736] vm.dirty_expire_centisecs Must be between [0, 6000] vm.dirty_ratio Must be between [1, 100] + vm.dirty_bytes Must be between + [0, 68719476736] vm.dirty_writeback_centisecs Must be between [0, 1000] vm.max_map_count Must be between diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 651eb6588..8d711c498 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -67,8 +67,8 @@ SYNOPSIS --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE | --enable-binauthz | --clear-fleet-project --enable-fleet --fleet-project=PROJECT_ID_OR_NUMBER - --membership-type=MEMBERSHIP_TYPE | --clear-maintenance-window - | --remove-maintenance-exclusion=NAME + --membership-type=MEMBERSHIP_TYPE --unset-membership-type + | --clear-maintenance-window | --remove-maintenance-exclusion=NAME | [--add-maintenance-exclusion-end=TIME_STAMP : --add-maintenance-exclusion-name=NAME --add-maintenance-exclusion-scope=SCOPE @@ -1056,6 +1056,11 @@ REQUIRED FLAGS LIGHTWEIGHT Fleet membership representing this cluster will be lightweight. + --unset-membership-type + Set the membership type for the cluster's fleet membership to empty. + Example: $ gcloud alpha container clusters update + --unset-membership-type + At most one of these can be specified: --clear-maintenance-window diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index 079970249..b15c2937e 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -126,15 +126,14 @@ FLAGS (Optional) The NVIDIA driver version to install. GPU_DRIVER_VERSION must be one of: - `default`: Install the default driver version for this GKE version. + `default`: Install the default driver version for this GKE version. For GKE version 1.30.1-gke.1156000 and later, this is the default option. `latest`: Install the latest driver version available for this GKE version. Can only be used for nodes that use Container-Optimized OS. `disabled`: Skip automatic driver installation. You must manually install a - driver after you create the cluster. If you omit the flag `gpu-driver-version`, - this is the default option. To learn how to manually install the GPU driver, - refer to: https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers + driver after you create the cluster. For GKE version 1.30.1-gke.1156000 and earlier, this is the default option. + To manually install the GPU driver, refer to https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers. gpu-partition-size (Optional) The GPU partition size used when running multi-instance @@ -554,9 +553,11 @@ FLAGS --cluster=example-cluster \ --node-labels=label1=value1,label2=value2 - New nodes, including ones created by resize or recreate, will have - these labels on the Kubernetes API node object and can be used in - nodeSelectors. See + Updating the node pool's --node-labels flag applies the labels to the + Kubernetes Node objects for existing nodes in-place; it does not + re-create or replace nodes. New nodes, including ones created by + resizing or re-creating nodes, will have these labels on the Kubernetes + API Node object. The labels can be used in the nodeSelector field. See https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ for examples. @@ -985,8 +986,18 @@ FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1, 2} + net.ipv4.tcp_mtu_probing Must be {0, 1, 2} net.ipv4.tcp_max_orphans Must be between [16384, 262144] + net.ipv4.tcp_max_tw_buckets Must be between + [4096, 2147483647] + net.ipv4.tcp_syn_retries Must be between + [1, 127] + net.ipv4.tcp_ecn Must be {0, 1, 2} + net.ipv4.tcp_congestion_control Must be string + containing only + letters and + numbers net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -1012,6 +1023,16 @@ FLAGS [0, 184467440736927743 99] + kernel.perf_event_paranoid Must be {-1, 0, 1, + 2, 3} + kernel.sched_rt_runtime_us Must be [-1, + 1000000] + kernel.softlockup_panic Must be {0, 1} + kernel.yama.ptrace_scope Must be {0, 1, 2, + 3} + kernel.kptr_restrict Must be {0, 1, 2} + kernel.dmesg_restrict Must be {0, 1} + kernel.sysrq Must be [0, 511] fs.aio-max-nr Must be between [65536, 4194304] fs.file-max Must be between @@ -1025,10 +1046,14 @@ FLAGS 2147483584] vm.dirty_background_ratio Must be between [1, 100] + vm.dirty_background_bytes Must be between + [0, 68719476736] vm.dirty_expire_centisecs Must be between [0, 6000] vm.dirty_ratio Must be between [1, 100] + vm.dirty_bytes Must be between + [0, 68719476736] vm.dirty_writeback_centisecs Must be between [0, 1000] vm.max_map_count Must be between diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index a54e4a8dc..7853f6d68 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -79,15 +79,14 @@ REQUIRED FLAGS (Optional) The NVIDIA driver version to install. GPU_DRIVER_VERSION must be one of: - `default`: Install the default driver version for this GKE version. + `default`: Install the default driver version for this GKE version. For GKE version 1.30.1-gke.1156000 and later, this is the default option. `latest`: Install the latest driver version available for this GKE version. Can only be used for nodes that use Container-Optimized OS. `disabled`: Skip automatic driver installation. You must manually install a - driver after you create the cluster. If you omit the flag `gpu-driver-version`, - this is the default option. To learn how to manually install the GPU driver, - refer to: https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers + driver after you create the cluster. For GKE version 1.30.1-gke.1156000 and earlier, this is the default option. + To manually install the GPU driver, refer to https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers. gpu-partition-size (Optional) The GPU partition size used when running @@ -217,9 +216,12 @@ REQUIRED FLAGS --cluster=example-cluster \ --node-labels=label1=value1,label2=value2 - New nodes, including ones created by resize or recreate, will have - these labels on the Kubernetes API node object and can be used in - nodeSelectors. See + Updating the node pool's --node-labels flag applies the labels to the + Kubernetes Node objects for existing nodes in-place; it does not + re-create or replace nodes. New nodes, including ones created by + resizing or re-creating nodes, will have these labels on the + Kubernetes API Node object. The labels can be used in the + nodeSelector field. See https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ for examples. @@ -499,8 +501,21 @@ REQUIRED FLAGS integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1, 2} + net.ipv4.tcp_mtu_probing Must be {0, 1, + 2} net.ipv4.tcp_max_orphans Must be between [16384, 262144] + net.ipv4.tcp_max_tw_buckets Must be between + [4096, + 2147483647] + net.ipv4.tcp_syn_retries Must be between + [1, 127] + net.ipv4.tcp_ecn Must be {0, 1, + 2} + net.ipv4.tcp_congestion_control Must be string + containing only + letters and + numbers net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -528,6 +543,17 @@ REQUIRED FLAGS [0, 1844674407369277 4399] + kernel.perf_event_paranoid Must be {-1, 0, + 1, 2, 3} + kernel.sched_rt_runtime_us Must be [-1, + 1000000] + kernel.softlockup_panic Must be {0, 1} + kernel.yama.ptrace_scope Must be {0, 1, + 2, 3} + kernel.kptr_restrict Must be {0, 1, + 2} + kernel.dmesg_restrict Must be {0, 1} + kernel.sysrq Must be [0, 511] fs.aio-max-nr Must be between [65536, 4194304] fs.file-max Must be between @@ -542,10 +568,14 @@ REQUIRED FLAGS 2147483584] vm.dirty_background_ratio Must be between [1, 100] + vm.dirty_background_bytes Must be between + [0, 68719476736] vm.dirty_expire_centisecs Must be between [0, 6000] vm.dirty_ratio Must be between [1, 100] + vm.dirty_bytes Must be between + [0, 68719476736] vm.dirty_writeback_centisecs Must be between [0, 1000] vm.max_map_count Must be between diff --git a/gcloud/alpha/dataplex/encryption-config/help b/gcloud/alpha/dataplex/encryption-config/help index 40161a61a..8491ec56a 100644 --- a/gcloud/alpha/dataplex/encryption-config/help +++ b/gcloud/alpha/dataplex/encryption-config/help @@ -22,6 +22,9 @@ COMMANDS describe (ALPHA) Describe an EncryptionConfig. + update + (ALPHA) Update an Encryption Config. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/dataplex/encryption-config/update b/gcloud/alpha/dataplex/encryption-config/update new file mode 100644 index 000000000..59a31f574 --- /dev/null +++ b/gcloud/alpha/dataplex/encryption-config/update @@ -0,0 +1,75 @@ +NAME + gcloud alpha dataplex encryption-config update - update an Encryption + Config + +SYNOPSIS + gcloud alpha dataplex encryption-config update + (ENCRYPTION_CONFIG : --location=LOCATION --organization=ORGANIZATION) + [--enable-metastore-encryption] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an Encryption Config. + +EXAMPLES + To update EncryptionConfig in organization 123 and location us-central1, + run: + + $ gcloud alpha dataplex encryption-config update \ + organizations/123/locations/us-central1/encryptionConfigs/\ + default --enable-metastore-encryption + +POSITIONAL ARGUMENTS + Encryption config resource - Arguments and flags that define the Dataplex + EncryptionConfig you want to update. The arguments in this group can be + used to specify the attributes of this resource. + + This must be specified. + + ENCRYPTION_CONFIG + ID of the encryption config or fully qualified identifier for the + encryption config. + + To set the encryption_config attribute: + ▸ provide the argument encryption_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument encryption_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + + --organization=ORGANIZATION + The name of encryption config to use. + + To set the organization attribute: + ▸ provide the argument encryption_config on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. + +FLAGS + --enable-metastore-encryption + Helps user to explicitly enable cmek encryption for dataplex metadata + storage. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud dataplex encryption-config update + diff --git a/gcloud/alpha/edge-cloud/container/clusters/create b/gcloud/alpha/edge-cloud/container/clusters/create index 8578352d7..3f3c9b641 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/create +++ b/gcloud/alpha/edge-cloud/container/clusters/create @@ -231,7 +231,7 @@ FLAGS --maintenance-window-end=MAINTENANCE_WINDOW_END End time of the recurring cluster maintenance window in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE @@ -242,7 +242,7 @@ FLAGS --maintenance-window-start=MAINTENANCE_WINDOW_START Start time of the recurring cluster maintenance window in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" --offline-reboot-ttl=OFFLINE_REBOOT_TTL diff --git a/gcloud/alpha/edge-cloud/container/clusters/update b/gcloud/alpha/edge-cloud/container/clusters/update index a2324c3e4..3c96572f4 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/update +++ b/gcloud/alpha/edge-cloud/container/clusters/update @@ -107,7 +107,7 @@ FLAGS --add-maintenance-exclusion-end=ADD_MAINTENANCE_EXCLUSION_END End time of the maintenance exclusion window in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00". --add-maintenance-exclusion-name=ADD_MAINTENANCE_EXCLUSION_NAME @@ -116,7 +116,7 @@ FLAGS --add-maintenance-exclusion-start=ADD_MAINTENANCE_EXCLUSION_START Start time of the maintenance exclusion window (can occur in the - past) in the RFC 3339 (https://www.ietf.org/rfc/rfc3339.txt) + past) in the RFC 3339 (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00". Updates cluster maintenance window setting (more than one flags can be @@ -124,7 +124,7 @@ FLAGS --maintenance-window-end=MAINTENANCE_WINDOW_END End time of the recurring cluster maintenance window in the RFC - 3339 (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + 3339 (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE @@ -135,7 +135,7 @@ FLAGS --maintenance-window-start=MAINTENANCE_WINDOW_START Start time of the recurring cluster maintenance window in the RFC - 3339 (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + 3339 (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" At most one of these can be specified: diff --git a/gcloud/alpha/iam/workforce-pools/providers/scim-tenants/delete b/gcloud/alpha/iam/workforce-pools/providers/scim-tenants/delete index 7277f4832..d31bba282 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/scim-tenants/delete +++ b/gcloud/alpha/iam/workforce-pools/providers/scim-tenants/delete @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha iam workforce-pools providers scim-tenants delete (SCIM_TENANT : --location=LOCATION - --provider=PROVIDER --workforce-pool=WORKFORCE_POOL) [--hard-delete] + --provider=PROVIDER --workforce-pool=WORKFORCE_POOL) [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -70,12 +70,6 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --workforce-pool on the command line. -FLAGS - --hard-delete - If set, hard delete the scim tenant. This will delete the scim tenant - resources i.e. the scim tenant project and service account associated - with it. This action cannot be undone. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/migration/vms/disk-migrations/cancel b/gcloud/alpha/migration/vms/disk-migrations/cancel new file mode 100644 index 000000000..57c4c28f3 --- /dev/null +++ b/gcloud/alpha/migration/vms/disk-migrations/cancel @@ -0,0 +1,78 @@ +NAME + gcloud alpha migration vms disk-migrations cancel - cancel a disk migration + resource process + +SYNOPSIS + gcloud alpha migration vms disk-migrations cancel + (DISK_MIGRATION : --location=LOCATION --source=SOURCE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms disk-migrations cancel cancels an + ongoing disk migration resource process. To use this command, you must + enable VM Migration API in your project. + +EXAMPLES + To cancel an ongoing my-disk-migration resource process in us-central1 in + the AWS source my-aws-source in the default project, run: $ gcloud alpha migration vms disk-migrations cancel \ + my-disk-migration --location=us-central1 --source=my-aws-source + +POSITIONAL ARGUMENTS + Disk migration resource - The disk migration resource you want to cancel + its ongoing process. The arguments in this group can be used to specify + the attributes of this 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 disk_migration on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DISK_MIGRATION + ID of the disk_migration or fully qualified identifier for the + disk_migration. + + To set the disk_migration attribute: + ▸ provide the argument disk_migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --source=SOURCE + The client source environment object. + + To set the source attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --source on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/disk-migrations/create b/gcloud/alpha/migration/vms/disk-migrations/create new file mode 100644 index 000000000..634f89161 --- /dev/null +++ b/gcloud/alpha/migration/vms/disk-migrations/create @@ -0,0 +1,134 @@ +NAME + gcloud alpha migration vms disk-migrations create - create a disk migration + resource to migrate a disk to Compute Engine + +SYNOPSIS + gcloud alpha migration vms disk-migrations create + (DISK_MIGRATION : --location=LOCATION --source=SOURCE) + --source-volume-id=SOURCE_VOLUME_ID [--disk-id=DISK_ID] + [--disk-type=DISK_TYPE] [--kms-key=KMS_KEY] [--labels=[KEY=VALUE,...]] + [--target-project=TARGET_PROJECT] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms disk-migrations create lets you create + disk migration resource. You must create a disk migration resource before + you can migrate your disk from any migration source to a Compute Engine + disk. The disk migration resource tracks the progress of the disk + migration. To use this command, you must enable VM Migration API in your + project. + + Note that this command only creates a disk migration resource. It does not + initiate the disk migration process. After creating the disk migration + resource, you must initiate the migration process using the run command. + +EXAMPLES + To create a disk migration resource to migrate a volume vol-12345 from an + AWS source my-aws-source to my-target-project in us-central1, create the + my-disk-migration disk migration resource in my-project in us-central1, + run: + + $ gcloud alpha migration vms disk-migrations create \ + my-disk-migration --project=my-project --location=us-central1 \ + --source=my-aws-source --source-volume-id=vol-12345 \ + --disk-id=gcp-disk1 \ + --target-project=projects/my-project/locations/global/\ + targetProjects/my-target-project + +POSITIONAL ARGUMENTS + Disk migration resource - The disk migration resource you want to create. + This would be the disk ID if --disk-id is not given. The arguments in this + group can be used to specify the attributes of this 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 disk_migration on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DISK_MIGRATION + ID of the disk_migration or fully qualified identifier for the + disk_migration. + + To set the disk_migration attribute: + ▸ provide the argument disk_migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --source=SOURCE + The client source environment object. + + To set the source attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --source on the command line. + +REQUIRED FLAGS + --source-volume-id=SOURCE_VOLUME_ID + The ID of the source volume that you want to migrate to Compute Engine. + +OPTIONAL FLAGS + --disk-id=DISK_ID + The ID of the disk that will be migrated to Compute Engine. The default + value is the disk migration resource name. + + --disk-type=DISK_TYPE + The Compute Engine disk type to use for the migrated disk. The default + value is COMPUTE_ENGINE_DISK_TYPE_STANDARD. DISK_TYPE must be one of: + + compute-engine-disk-type-balanced + Compute Engine Disk Type Balanced. + compute-engine-disk-type-hyperdisk-balanced + Compute Engine Disk Type hyperdisk-balanced. + compute-engine-disk-type-ssd + Compute Engine Disk Type SSD. + compute-engine-disk-type-standard + Compute Engine Disk Type Standard. + + --kms-key=KMS_KEY + Fully qualified identifier for the Cloud KMS (Key Management Service) + cryptokey that will be used to protect the disk. + + --labels=[KEY=VALUE,...] + A map of labels to associate with the disk. + + --target-project=TARGET_PROJECT + The target project resource path to which the disk will be migrated. + Default is the host project. To get a list of the target projects run + the gcloud alpha migration vms target-projects list command. + + --zone=ZONE + The zone in which to create the disk. The default value is the first + zone of the Google Cloud location parameter given. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/disk-migrations/delete b/gcloud/alpha/migration/vms/disk-migrations/delete new file mode 100644 index 000000000..d74751d20 --- /dev/null +++ b/gcloud/alpha/migration/vms/disk-migrations/delete @@ -0,0 +1,82 @@ +NAME + gcloud alpha migration vms disk-migrations delete - delete a disk migration + resource + +SYNOPSIS + gcloud alpha migration vms disk-migrations delete + (DISK_MIGRATION : --location=LOCATION --source=SOURCE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms disk-migrations delete deletes a disk + migration resource. To use this command, you must enable VM Migration API + in your project. + + This command does not delete any disks on Google Compute Engine. + +EXAMPLES + To delete my-disk-migration resource in us-central1 in the AWS source + my-aws-source in the default project, run: + + $ gcloud alpha migration vms disk-migrations delete \ + my-image-import --location=us-central1 --source=my-aws-source + +POSITIONAL ARGUMENTS + Disk migration resource - The disk migration resource you want to delete. + The arguments in this group can be used to specify the attributes of this + 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 disk_migration on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DISK_MIGRATION + ID of the disk_migration or fully qualified identifier for the + disk_migration. + + To set the disk_migration attribute: + ▸ provide the argument disk_migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --source=SOURCE + The client source environment object. + + To set the source attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --source on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/disk-migrations/describe b/gcloud/alpha/migration/vms/disk-migrations/describe new file mode 100644 index 000000000..2b4eacb4f --- /dev/null +++ b/gcloud/alpha/migration/vms/disk-migrations/describe @@ -0,0 +1,81 @@ +NAME + gcloud alpha migration vms disk-migrations describe - describe a disk + migration resource + +SYNOPSIS + gcloud alpha migration vms disk-migrations describe + (DISK_MIGRATION : --location=LOCATION --source=SOURCE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms disk-migrations describe describes a + disk migration resource. The disk migration resource tracks the disk + migration progress. To use this command, you must enable VM Migration API + in your project. + +EXAMPLES + To describe my-disk-migration resource in us-central1 in the AWS source + my-aws-source in the default project, run: + + $ gcloud alpha migration vms disk-migrations describe \ + my-disk-migration --location=us-central1 --source=my-aws-source + +POSITIONAL ARGUMENTS + Disk migration resource - The disk migration resource you want to + describe. The arguments in this group can be used to specify the + attributes of this 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 disk_migration on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DISK_MIGRATION + ID of the disk_migration or fully qualified identifier for the + disk_migration. + + To set the disk_migration attribute: + ▸ provide the argument disk_migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --source=SOURCE + The client source environment object. + + To set the source attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --source on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/disk-migrations/fetch-inventory b/gcloud/alpha/migration/vms/disk-migrations/fetch-inventory new file mode 100644 index 000000000..2ab66ec83 --- /dev/null +++ b/gcloud/alpha/migration/vms/disk-migrations/fetch-inventory @@ -0,0 +1,105 @@ +NAME + gcloud alpha migration vms disk-migrations fetch-inventory - lists source + environment volume inventory + +SYNOPSIS + gcloud alpha migration vms disk-migrations fetch-inventory + (SOURCE : --location=LOCATION) [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms disk-migrations fetch-inventory prints a + detailed list of the source environment volume inventory. To use this + command, you must enable VM Migration API in your project. + +EXAMPLES + To list the source environment volume resources in us-central1 in the AWS + source my-aws-source in the default project, run: + + $ gcloud alpha migration vms disk-migrations fetch-inventory \ + my-aws-source --location=us-central1 + +POSITIONAL ARGUMENTS + Source resource - The source environment resource of the disk migration + resources. This is the parent resource of the disk migration resources. + The arguments in this group can be used to specify the attributes of this + 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 on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + SOURCE + ID of the source or fully qualified identifier for the source. + + To set the source attribute: + ▸ provide the argument source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument source on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/disk-migrations/help b/gcloud/alpha/migration/vms/disk-migrations/help new file mode 100644 index 000000000..26f5d60c1 --- /dev/null +++ b/gcloud/alpha/migration/vms/disk-migrations/help @@ -0,0 +1,70 @@ +NAME + gcloud alpha migration vms disk-migrations - migrates disks to Compute + Engine + +SYNOPSIS + gcloud alpha migration vms disk-migrations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The gcloud alpha migration vms disk-migrations command lets you + create and manage disk migration resource. You must create a disk migration + resource before you can migrate your disk from any migration source to a + Compute Engine disk. The disk migration resource tracks the progress of the + disk migration. To use this command, you must enable VM Migration API in + your project. + + Note that this command only creates a disk migration resource. It does not + initiate the disk migration process. After creating the disk migration + resource, you must initiate the migration process using the run command. + + The disk is migrated to a Google Cloud Project, designated by the Target + Project resource. To get a list of Target Projects, run the gcloud alpha + migration vms target-projects list command. For information on adding + target projects, see + https://cloud.google.com/migrate/virtual-machines/docs/5.0/how-to/target-project. + + A project can support a maximum of 200 Disk/VM Migration active resources + per project; 1000 ready disk migration resources, and 500 finished disk + migration resources. Hence we recommend that you delete a completed disk + migrations to avoid reaching the disk migration resources limit. Deletion + of disk migration resource does not affect the migrated disk. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancel a disk migration resource process. + + create + (ALPHA) Create a disk migration resource to migrate a disk to Compute + Engine. + + delete + (ALPHA) Delete a disk migration resource. + + describe + (ALPHA) Describe a disk migration resource. + + fetch-inventory + (ALPHA) Lists source environment volume inventory. + + list + (ALPHA) List disk migration resources. + + run + (ALPHA) Run a disk migration resource process. + + update + (ALPHA) Update a disk migration resource target details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/disk-migrations/list b/gcloud/alpha/migration/vms/disk-migrations/list new file mode 100644 index 000000000..aa826039c --- /dev/null +++ b/gcloud/alpha/migration/vms/disk-migrations/list @@ -0,0 +1,105 @@ +NAME + gcloud alpha migration vms disk-migrations list - list disk migration + resources + +SYNOPSIS + gcloud alpha migration vms disk-migrations list + (--source=SOURCE : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms disk-migrations list prints a detailed + list of disk migration resources. To use this command, you must enable VM + Migration API in your project. + +EXAMPLES + To list the disk migration resources in us-central1 in the AWS source + my-aws-source in the default project, run: + + $ gcloud alpha migration vms disk-migrations list \ + --location=us-central1 --source=my-aws-source + +REQUIRED FLAGS + Source resource - The source environment resource of the disk migration + resources. This is the parent resource of the disk migration resources. + The arguments in this group can be used to specify the attributes of this + 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 on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --source=SOURCE + ID of the source or fully qualified identifier for the source. + + To set the source attribute: + ▸ provide the argument --source on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument --source on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/disk-migrations/run b/gcloud/alpha/migration/vms/disk-migrations/run new file mode 100644 index 000000000..23e11cf68 --- /dev/null +++ b/gcloud/alpha/migration/vms/disk-migrations/run @@ -0,0 +1,78 @@ +NAME + gcloud alpha migration vms disk-migrations run - run a disk migration + resource process + +SYNOPSIS + gcloud alpha migration vms disk-migrations run + (DISK_MIGRATION : --location=LOCATION --source=SOURCE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms disk-migrations run initiates a disk + migration resource process. To use this command, you must enable VM + Migration API in your project. + +EXAMPLES + To run my-disk-migration resource process in us-central1 in the AWS source + my-aws-source in the default project, run: $ gcloud alpha migration vms disk-migrations run my-disk-migration \ + --location=us-central1 --source=my-aws-source + +POSITIONAL ARGUMENTS + Disk migration resource - The disk migration resource you want to initiate + its process. The arguments in this group can be used to specify the + attributes of this 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 disk_migration on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DISK_MIGRATION + ID of the disk_migration or fully qualified identifier for the + disk_migration. + + To set the disk_migration attribute: + ▸ provide the argument disk_migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --source=SOURCE + The client source environment object. + + To set the source attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --source on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/disk-migrations/update b/gcloud/alpha/migration/vms/disk-migrations/update new file mode 100644 index 000000000..b5d825618 --- /dev/null +++ b/gcloud/alpha/migration/vms/disk-migrations/update @@ -0,0 +1,117 @@ +NAME + gcloud alpha migration vms disk-migrations update - update a disk migration + resource target details + +SYNOPSIS + gcloud alpha migration vms disk-migrations update + (DISK_MIGRATION : --location=LOCATION --source=SOURCE) + [--disk-id=DISK_ID] [--disk-type=DISK_TYPE] [--kms-key=KMS_KEY] + [--labels=[KEY=VALUE,...]] [--target-project=TARGET_PROJECT] + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms disk-migrations update updates a disk + migration resource. To use this command, you must enable VM Migration API + in your project. + +EXAMPLES + To update a disk migration resource my-disk-migration from AWS source + my-aws-source disk type to pd-ssd, run: + + $ gcloud alpha migration vms disk-migrations update \ + my-disk-migration --project=my-project --location=us-central1 \ + --source=my-aws-source --disk-type=COMPUTE_ENGINE_DISK_TYPE_SSD + +POSITIONAL ARGUMENTS + Disk migration resource - The disk migration resource you want to udpate. + The arguments in this group can be used to specify the attributes of this + 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 disk_migration on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + DISK_MIGRATION + ID of the disk_migration or fully qualified identifier for the + disk_migration. + + To set the disk_migration attribute: + ▸ provide the argument disk_migration on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + + --source=SOURCE + The client source environment object. + + To set the source attribute: + ▸ provide the argument disk_migration on the command line with a + fully specified name; + ▸ provide the argument --source on the command line. + +FLAGS + --disk-id=DISK_ID + The ID of the disk that will be migrated to Compute Engine. The default + value is the disk migration resource name. + + --disk-type=DISK_TYPE + The Compute Engine disk type to use for the migrated disk. The default + value is COMPUTE_ENGINE_DISK_TYPE_STANDARD. DISK_TYPE must be one of: + + compute-engine-disk-type-balanced + Compute Engine Disk Type Balanced. + compute-engine-disk-type-hyperdisk-balanced + Compute Engine Disk Type hyperdisk-balanced. + compute-engine-disk-type-ssd + Compute Engine Disk Type SSD. + compute-engine-disk-type-standard + Compute Engine Disk Type Standard. + + --kms-key=KMS_KEY + Fully qualified identifier for the Cloud KMS (Key Management Service) + cryptokey that will be used to protect the disk. + + --labels=[KEY=VALUE,...] + A map of labels to associate with the disk. + + --target-project=TARGET_PROJECT + The target project resource path to which the disk will be migrated. + Default is the host project. To get a list of the target projects run + the gcloud alpha migration vms target-projects list command. + + --zone=ZONE + The zone in which to create the disk. The default value is the first + zone of the Google Cloud location parameter given. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/help b/gcloud/alpha/migration/vms/help index 1b644114f..ab36fdcf3 100644 --- a/gcloud/alpha/migration/vms/help +++ b/gcloud/alpha/migration/vms/help @@ -20,6 +20,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + disk-migrations + (ALPHA) Migrates disks to Compute Engine. + image-imports (ALPHA) Imports images to Google Compute Engine from Google Cloud Storage. diff --git a/gcloud/alpha/recommender/insights/describe b/gcloud/alpha/recommender/insights/describe index 014f624b7..efad2cdcd 100644 --- a/gcloud/alpha/recommender/insights/describe +++ b/gcloud/alpha/recommender/insights/describe @@ -15,8 +15,9 @@ DESCRIPTION EXAMPLES To describe an insight: - $ gcloud alpha recommender insights describe INSIGHT_ID \ - --project=${PROJECT} --location=${LOCATION} + $ gcloud alpha recommender insights describe \ + --insight-type=${INSIGHT_TYPE} --project=${PROJECT} \ + --location=${LOCATION} POSITIONAL ARGUMENTS INSIGHT diff --git a/gcloud/alpha/sql/connect b/gcloud/alpha/sql/connect index cd632eb27..e8b8d89a6 100644 --- a/gcloud/alpha/sql/connect +++ b/gcloud/alpha/sql/connect @@ -2,10 +2,10 @@ NAME gcloud alpha sql connect - connects to a Cloud SQL instance SYNOPSIS - gcloud alpha sql connect INSTANCE [--auto-iam-authn] - [--database=DATABASE, -d DATABASE] [--debug-logs] - [--port=PORT; default=9470] [--run-connection-test] [--skip-ssl] - [--sqladmin-api-endpoint=SQLADMIN_API_ENDPOINT] [--user=USER, -u USER] + gcloud alpha sql connect INSTANCE [--database=DATABASE, -d DATABASE] + [--debug-logs] [--port=PORT; default=9470] [--run-connection-test] + [--skip-ssl] [--sqladmin-api-endpoint=SQLADMIN_API_ENDPOINT] + [--auto-iam-authn | --user=USER, -u USER] [--auto-ip | --private-ip | --psc] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -21,10 +21,6 @@ POSITIONAL ARGUMENTS Cloud SQL instance ID. FLAGS - --auto-iam-authn - Enables IAM database authentication for connections to MySQL and - Postgres instances. - --database=DATABASE, -d DATABASE The PostgreSQL or SQL Server database to connect to. @@ -44,8 +40,16 @@ FLAGS --sqladmin-api-endpoint=SQLADMIN_API_ENDPOINT Cloud SQL Admin API endpoint for Cloud SQL Proxy to use. - --user=USER, -u USER - Cloud SQL instance user to connect as. + User selection settings for Cloud SQL Proxy connection. + + At most one of these can be specified: + + --auto-iam-authn + Enables IAM database authentication for connections to MySQL and + Postgres instances. + + --user=USER, -u USER + Cloud SQL instance user to connect as. IP address selection settings for Cloud SQL Proxy connection. diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 6eabed8c4..0817d280e 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -53,6 +53,7 @@ SYNOPSIS [--remove-deny-maintenance-period] [--replication=REPLICATION] [--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE] [--[no-]require-ssl] [--[no-]retain-backups-on-delete] + [--server-ca-mode=SERVER_CA_MODE] [--server-ca-pool=SERVER_CA_POOL] [--simulate-maintenance-event] [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] @@ -450,6 +451,21 @@ FLAGS deleted. Use --retain-backups-on-delete to enable and --no-retain-backups-on-delete to disable. + --server-ca-mode=SERVER_CA_MODE + Set the server CA mode of the instance. SERVER_CA_MODE must be one of: + + CUSTOMER_MANAGED_CAS_CA + Customer-managed CA hosted on Google Cloud's Certificate Authority + Service (CAS). + GOOGLE_MANAGED_CAS_CA + Google-managed regional CA part of root CA hierarchy hosted on + Google Cloud's Certificate Authority Service (CAS). + GOOGLE_MANAGED_INTERNAL_CA + Google-managed self-signed internal CA. + + --server-ca-pool=SERVER_CA_POOL + Set the server CA pool of the instance. + --simulate-maintenance-event Simulate a maintenance event without changing the version. Only applicable to instances that support near-zero downtime planned diff --git a/gcloud/alpha/sql/instances/reset-ssl-config b/gcloud/alpha/sql/instances/reset-ssl-config index 3c06b5948..6a7fc0e36 100644 --- a/gcloud/alpha/sql/instances/reset-ssl-config +++ b/gcloud/alpha/sql/instances/reset-ssl-config @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha sql instances reset-ssl-config INSTANCE [--async] - [GCLOUD_WIDE_FLAG ...] + [--mode=MODE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Reset SSL materials according to the reset SSL mode. @@ -18,6 +18,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --mode=MODE + Selectively refresh the SSL materials. MODE must be one of: + + ALL + Refresh all TLS configs. This is the default behaviour. + SYNC_FROM_PRIMARY + Refreshes the replication-related TLS configuration settings + provided by the primary instance. Not applicable to on-premises + replication instances. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/storage/cp b/gcloud/alpha/storage/cp index 72c37145a..eb836a626 100644 --- a/gcloud/alpha/storage/cp +++ b/gcloud/alpha/storage/cp @@ -23,7 +23,12 @@ SYNOPSIS --content-disposition=CONTENT_DISPOSITION --content-encoding=CONTENT_ENCODING --content-language=CONTENT_LANGUAGE --content-type=CONTENT_TYPE - --custom-time=CUSTOM_TIME --clear-custom-metadata + --custom-time=CUSTOM_TIME --clear-custom-contexts + | --custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + | --custom-contexts-file=CUSTOM_CONTEXTS_FILE + | --remove-custom-contexts=[CUSTOM_CONTEXTS_KEYS,...] + --update-custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + --clear-custom-metadata | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] | --remove-custom-metadata=[METADATA_KEYS,...] --update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]] @@ -69,6 +74,14 @@ EXAMPLES $ gcloud alpha storage cp ~/Downloads/**/dir gs://my-bucket + The contexts are preserved when copying to Google Cloud Storage. To + overwrite contexts on the destination object, use --custom-contexts or + --custom-contexts-file. For example: + + $ gcloud alpha storage cp gs://my-bucket/object \ + gs://destination-bucket/object \ + --custom-contexts=key1=value1,key2=value2 + POSITIONAL ARGUMENTS [SOURCE ...] The source path(s) to copy. @@ -313,6 +326,54 @@ OBJECT METADATA FLAGS --custom-time=CUSTOM_TIME Custom time for Cloud Storage objects in RFC 3339 format. + Group that allow users to handle object contexts. + + At most one of these can be specified: + + --clear-custom-contexts + Clears all custom contexts on objects. + + --custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + Sets custom contexts on objects. The existing custom contexts (if + any) would be overwritten. + + --custom-contexts-file=CUSTOM_CONTEXTS_FILE + Path to a local JSON or YAML file containing custom contexts one + wants to set on an object. For example: + + 1. The following JSON document shows two key value pairs, i.e. (key1, + value1) and (key2, value2): + + { + "key1": {"value": "value1"}, + "key2": {"value": "value2"} + } + + 2. The following YAML document shows two key value pairs, i.e. (key1, + value1) and (key2, value2): + + key1: + value: value1 + key2: + value: value2 + + Note: Currently object contexts only supports string format for + values. + + Flags that preserve the existing contexts on the object, and can be + specified together. However they cannot be specified with + --clear-custom-contexts, --custom-contexts or --custom-contexts-file. If + --update-custom-contexts and --remove-custom-contexts are specified + together, the --remove-custom-contexts would be applied first on object. + + --remove-custom-contexts=[CUSTOM_CONTEXTS_KEYS,...] + Removes the custom contexts on the object, if an entry is not + found, it would be ignored. + + --update-custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + Updates the custom contexts on the object, if an entry is found, it + would be overwritten, otherwise the entry would be added. + At most one of these can be specified: --clear-custom-metadata diff --git a/gcloud/alpha/storage/du b/gcloud/alpha/storage/du index 696ba2f4b..ac8ac978a 100644 --- a/gcloud/alpha/storage/du +++ b/gcloud/alpha/storage/du @@ -7,9 +7,9 @@ SYNOPSIS [--all-versions, -a] [--exclude-name-pattern=EXCLUDE_NAME_PATTERN, -e EXCLUDE_NAME_PATTERN] [--exclude-name-pattern-file=EXCLUDE_NAME_PATTERN_FILE, - -X EXCLUDE_NAME_PATTERN_FILE] [--readable-sizes, -r] - [--summarize, -s] [--total, -c] [--zero-terminator, -0] - [GCLOUD_WIDE_FLAG ...] + -X EXCLUDE_NAME_PATTERN_FILE] [--metadata-filter=METADATA_FILTER] + [--readable-sizes, -r] [--summarize, -s] [--total, -c] + [--zero-terminator, -0] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Displays the amount of space in bytes used by the objects in a @@ -52,6 +52,12 @@ EXAMPLES $ gcloud alpha storage du --summarize --readable-sizes --total + The following command summarizes the size of objects that match the + specified filter. + + $ gcloud alpha storage du gs://my-bucket \ + --metadata-filter='contexts."foo"="bar"' --summarize + POSITIONAL ARGUMENTS [URL ...] The url of objects to list. @@ -76,6 +82,15 @@ FLAGS Similar to -e, but excludes patterns from the given file. The patterns to exclude should be listed one per line. + --metadata-filter=METADATA_FILTER + Server side filtering for objects. Works only for Google Cloud Storage + URLs. The filter only works for objects, and not directories or + buckets, which means commands like storage ls and storage du will still + list directories or buckets even if they do not contain any objects + matching the filter. See + https://cloud.google.com/storage/docs/listing-objects#filter-by-object-contexts-syntax + for more details. + --readable-sizes, -r Prints object sizes in human-readable format. For example, 1 KiB, 234 MiB, or 2GiB. diff --git a/gcloud/alpha/storage/ls b/gcloud/alpha/storage/ls index 82f115847..70fd3c24e 100644 --- a/gcloud/alpha/storage/ls +++ b/gcloud/alpha/storage/ls @@ -5,9 +5,9 @@ SYNOPSIS gcloud alpha storage ls [PATH ...] [--additional-headers=HEADER=VALUE] [--all-versions, -a] [--buckets, -b] [--etag, -e] [--exhaustive] [--fetch-encrypted-object-hashes] [--format=FORMAT] - [--next-page-token=NEXT_PAGE_TOKEN] [--read-paths-from-stdin, -I] - [--readable-sizes] [--recursive, -R, -r] [--soft-deleted] - [--full, -L | --json, -j | --long, -l] + [--metadata-filter=METADATA_FILTER] [--next-page-token=NEXT_PAGE_TOKEN] + [--read-paths-from-stdin, -I] [--readable-sizes] [--recursive, -R, -r] + [--soft-deleted] [--full, -L | --json, -j | --long, -l] [--decryption-keys=[DECRYPTION_KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -64,6 +64,14 @@ EXAMPLES Recursive listings are similar to ** except recursive listings include line breaks and header formatting for each subdirectory. + The following command filters objects based on specified filter while + listing. Note that the flag is only supported for Google Cloud Storage URLs + and only applies to objects. This means that directories or buckets will + still be listed even if they do not contain objects that match the filter. + + $ gcloud alpha storage ls gs://my-bucket \ + --metadata-filter='contexts."foo"="bar"' + POSITIONAL ARGUMENTS [PATH ...] The path of objects and directories to list. The path must begin with @@ -108,6 +116,15 @@ FLAGS "--format=gsutil"). Other format values (e.g. "json") do not work. See different ls flags and commands for alternative formatting. + --metadata-filter=METADATA_FILTER + Server side filtering for objects. Works only for Google Cloud Storage + URLs. The filter only works for objects, and not directories or + buckets, which means commands like storage ls and storage du will still + list directories or buckets even if they do not contain any objects + matching the filter. See + https://cloud.google.com/storage/docs/listing-objects#filter-by-object-contexts-syntax + for more details. + --next-page-token=NEXT_PAGE_TOKEN Page token for resuming LIST calls. diff --git a/gcloud/alpha/storage/mv b/gcloud/alpha/storage/mv index 726985d61..d0503a18d 100644 --- a/gcloud/alpha/storage/mv +++ b/gcloud/alpha/storage/mv @@ -22,7 +22,12 @@ SYNOPSIS --content-disposition=CONTENT_DISPOSITION --content-encoding=CONTENT_ENCODING --content-language=CONTENT_LANGUAGE --content-type=CONTENT_TYPE - --custom-time=CUSTOM_TIME --clear-custom-metadata + --custom-time=CUSTOM_TIME --clear-custom-contexts + | --custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + | --custom-contexts-file=CUSTOM_CONTEXTS_FILE + | --remove-custom-contexts=[CUSTOM_CONTEXTS_KEYS,...] + --update-custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + --clear-custom-metadata | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] | --remove-custom-metadata=[METADATA_KEYS,...] --update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]] @@ -80,6 +85,12 @@ EXAMPLES $ gcloud alpha storage mv gs://my_bucket/oldprefix \ gs://my_bucket/newprefix + The following command would clear all custom contexts from the destination + object while moving the object to the destination bucket. + + $ gcloud alpha storage mv gs://my-bucket/object \ + gs://destination-bucket/object --clear-custom-contexts + POSITIONAL ARGUMENTS [SOURCE ...] The source path(s) to copy. @@ -320,6 +331,54 @@ OBJECT METADATA FLAGS --custom-time=CUSTOM_TIME Custom time for Cloud Storage objects in RFC 3339 format. + Group that allow users to handle object contexts. + + At most one of these can be specified: + + --clear-custom-contexts + Clears all custom contexts on objects. + + --custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + Sets custom contexts on objects. The existing custom contexts (if + any) would be overwritten. + + --custom-contexts-file=CUSTOM_CONTEXTS_FILE + Path to a local JSON or YAML file containing custom contexts one + wants to set on an object. For example: + + 1. The following JSON document shows two key value pairs, i.e. (key1, + value1) and (key2, value2): + + { + "key1": {"value": "value1"}, + "key2": {"value": "value2"} + } + + 2. The following YAML document shows two key value pairs, i.e. (key1, + value1) and (key2, value2): + + key1: + value: value1 + key2: + value: value2 + + Note: Currently object contexts only supports string format for + values. + + Flags that preserve the existing contexts on the object, and can be + specified together. However they cannot be specified with + --clear-custom-contexts, --custom-contexts or --custom-contexts-file. If + --update-custom-contexts and --remove-custom-contexts are specified + together, the --remove-custom-contexts would be applied first on object. + + --remove-custom-contexts=[CUSTOM_CONTEXTS_KEYS,...] + Removes the custom contexts on the object, if an entry is not + found, it would be ignored. + + --update-custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + Updates the custom contexts on the object, if an entry is found, it + would be overwritten, otherwise the entry would be added. + At most one of these can be specified: --clear-custom-metadata diff --git a/gcloud/alpha/storage/objects/compose b/gcloud/alpha/storage/objects/compose index 70df7a85d..de995ac8a 100644 --- a/gcloud/alpha/storage/objects/compose +++ b/gcloud/alpha/storage/objects/compose @@ -5,6 +5,8 @@ NAME SYNOPSIS gcloud alpha storage objects compose SOURCE [SOURCE ...] DESTINATION [--additional-headers=HEADER=VALUE] + [--custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + | --custom-contexts-file=CUSTOM_CONTEXTS_FILE] [--if-generation-match=GENERATION --if-metageneration-match=METAGENERATION] [--retain-until=DATETIME --retention-mode=RETENTION_MODE] @@ -26,6 +28,14 @@ EXAMPLES $ gcloud alpha storage objects compose gs://bucket/a.txt \ gs://bucket/b.txt gs://bucket/target.txt + Contexts are merged from source objects on the composed object by default. + However, the following command overwrites custom contexts on composed + object: + + $ gcloud alpha storage objects compose gs://bucket/a.txt \ + gs://bucket/b.txt gs://bucket/target.txt \ + --custom-contexts=key1=value1,key2=value2 + POSITIONAL ARGUMENTS SOURCE [SOURCE ...] The list of source objects that will be concatenated into a single @@ -41,6 +51,38 @@ FLAGS Overrides the default storage/additional_headers property value for this command invocation. +OBJECT CONTEXTS FLAGS + Group that allow users to handle object contexts. + + At most one of these can be specified: + + --custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + Sets custom contexts on objects. The existing custom contexts (if + any) would be overwritten. + + --custom-contexts-file=CUSTOM_CONTEXTS_FILE + Path to a local JSON or YAML file containing custom contexts one + wants to set on an object. For example: + + 1. The following JSON document shows two key value pairs, i.e. (key1, + value1) and (key2, value2): + + { + "key1": {"value": "value1"}, + "key2": {"value": "value2"} + } + + 2. The following YAML document shows two key value pairs, i.e. (key1, + value1) and (key2, value2): + + key1: + value: value1 + key2: + value: value2 + + Note: Currently object contexts only supports string format for + values. + PRECONDITION FLAGS --if-generation-match=GENERATION Execute only if the generation matches the generation of the requested diff --git a/gcloud/alpha/storage/objects/describe b/gcloud/alpha/storage/objects/describe index a493ee7ec..020115513 100644 --- a/gcloud/alpha/storage/objects/describe +++ b/gcloud/alpha/storage/objects/describe @@ -21,6 +21,11 @@ EXAMPLES $ gcloud alpha storage objects describe gs://bucket/my-object \ --format="json(name)" + Describe only contexts attached to objects as key value pairs. + + $ gcloud alpha storage objects describe gs://my-bucket/object \ + --format=contextsonly + POSITIONAL ARGUMENTS URL Specifies URL of object to describe. diff --git a/gcloud/alpha/storage/objects/list b/gcloud/alpha/storage/objects/list index 655d6b28b..bf0421c37 100644 --- a/gcloud/alpha/storage/objects/list +++ b/gcloud/alpha/storage/objects/list @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha storage objects list URLS [URLS ...] [--additional-headers=HEADER=VALUE] [--exhaustive] - [--fetch-encrypted-object-hashes] [--next-page-token=NEXT_PAGE_TOKEN] - [--raw] [--soft-deleted] [--stat] + [--fetch-encrypted-object-hashes] [--metadata-filter=METADATA_FILTER] + [--next-page-token=NEXT_PAGE_TOKEN] [--raw] [--soft-deleted] [--stat] [--decryption-keys=[DECRYPTION_KEY,...]] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -36,6 +36,11 @@ EXAMPLES $ gcloud alpha storage objects list gs://my-bucket \ --format="json(name)" + List only contexts attached to objects as key value pairs. + + $ gcloud alpha storage objects list gs://my-bucket \ + --format=contextsonly + POSITIONAL ARGUMENTS URLS [URLS ...] Specifies URL of objects to list. @@ -58,6 +63,15 @@ FLAGS encrypted object in order to fetch hashes. This can significantly increase the cost of the command. + --metadata-filter=METADATA_FILTER + Server side filtering for objects. Works only for Google Cloud Storage + URLs. The filter only works for objects, and not directories or + buckets, which means commands like storage ls and storage du will still + list directories or buckets even if they do not contain any objects + matching the filter. See + https://cloud.google.com/storage/docs/listing-objects#filter-by-object-contexts-syntax + for more details. + --next-page-token=NEXT_PAGE_TOKEN Page token for resuming LIST calls. diff --git a/gcloud/alpha/storage/objects/update b/gcloud/alpha/storage/objects/update index e871d05c5..8923ea9ee 100644 --- a/gcloud/alpha/storage/objects/update +++ b/gcloud/alpha/storage/objects/update @@ -20,7 +20,12 @@ SYNOPSIS --content-disposition=CONTENT_DISPOSITION --content-encoding=CONTENT_ENCODING --content-language=CONTENT_LANGUAGE --content-type=CONTENT_TYPE - --custom-time=CUSTOM_TIME --clear-custom-metadata + --custom-time=CUSTOM_TIME --clear-custom-contexts + | --custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + | --custom-contexts-file=CUSTOM_CONTEXTS_FILE + | --remove-custom-contexts=[CUSTOM_CONTEXTS_KEYS,...] + --update-custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + --clear-custom-metadata | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] | --remove-custom-metadata=[METADATA_KEYS,...] --update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]] @@ -57,6 +62,18 @@ EXAMPLES $ gcloud alpha storage objects update gs://bucket/*.jpg \ --storage-class=NEARLINE --if-metageneration-match=123456789 + The following command overwrites the custom contexts of an object: + + $ gcloud alpha storage objects update gs://bucket/my-object \ + --custom-contexts=key1=value1,key2=value2 + + The following example simultaneously updates and removes custom contexts, + with remove being applied first: + + $ gcloud alpha storage objects update gs://bucket/my-object \ + --update-custom-contexts=key2=value3 \ + --remove-custom-contexts=key2,key3 + POSITIONAL ARGUMENTS [URL ...] Specifies URLs of objects to update. @@ -191,6 +208,54 @@ OBJECT METADATA FLAGS --custom-time=CUSTOM_TIME Custom time for Cloud Storage objects in RFC 3339 format. + Group that allow users to handle object contexts. + + At most one of these can be specified: + + --clear-custom-contexts + Clears all custom contexts on objects. + + --custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + Sets custom contexts on objects. The existing custom contexts (if + any) would be overwritten. + + --custom-contexts-file=CUSTOM_CONTEXTS_FILE + Path to a local JSON or YAML file containing custom contexts one + wants to set on an object. For example: + + 1. The following JSON document shows two key value pairs, i.e. (key1, + value1) and (key2, value2): + + { + "key1": {"value": "value1"}, + "key2": {"value": "value2"} + } + + 2. The following YAML document shows two key value pairs, i.e. (key1, + value1) and (key2, value2): + + key1: + value: value1 + key2: + value: value2 + + Note: Currently object contexts only supports string format for + values. + + Flags that preserve the existing contexts on the object, and can be + specified together. However they cannot be specified with + --clear-custom-contexts, --custom-contexts or --custom-contexts-file. If + --update-custom-contexts and --remove-custom-contexts are specified + together, the --remove-custom-contexts would be applied first on object. + + --remove-custom-contexts=[CUSTOM_CONTEXTS_KEYS,...] + Removes the custom contexts on the object, if an entry is not + found, it would be ignored. + + --update-custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + Updates the custom contexts on the object, if an entry is found, it + would be overwritten, otherwise the entry would be added. + At most one of these can be specified: --clear-custom-metadata diff --git a/gcloud/alpha/storage/rsync b/gcloud/alpha/storage/rsync index 34ffb9de1..7c2b607af 100644 --- a/gcloud/alpha/storage/rsync +++ b/gcloud/alpha/storage/rsync @@ -20,7 +20,12 @@ SYNOPSIS --content-disposition=CONTENT_DISPOSITION --content-encoding=CONTENT_ENCODING --content-language=CONTENT_LANGUAGE --content-type=CONTENT_TYPE - --custom-time=CUSTOM_TIME --clear-custom-metadata + --custom-time=CUSTOM_TIME --clear-custom-contexts + | --custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + | --custom-contexts-file=CUSTOM_CONTEXTS_FILE + | --remove-custom-contexts=[CUSTOM_CONTEXTS_KEYS,...] + --update-custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + --clear-custom-metadata | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] | --remove-custom-metadata=[METADATA_KEYS,...] --update-custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...]] @@ -94,6 +99,13 @@ EXAMPLES $ gcloud alpha storage rsync dir gs://my-bucket \ --exclude=".*\.txt$|.*\.jpg$" + The contexts are preserved when using rsync to sync to Google Cloud + Storage. However, the following command would clear all custom contexts + from the destination object while syncing to the destination bucket. + + $ gcloud alpha storage rsync gs://my-bucket/ \ + gs://destination-bucket/ --clear-custom-contexts + POSITIONAL ARGUMENTS SOURCE The source container path. @@ -251,6 +263,54 @@ OBJECT METADATA FLAGS --custom-time=CUSTOM_TIME Custom time for Cloud Storage objects in RFC 3339 format. + Group that allow users to handle object contexts. + + At most one of these can be specified: + + --clear-custom-contexts + Clears all custom contexts on objects. + + --custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + Sets custom contexts on objects. The existing custom contexts (if + any) would be overwritten. + + --custom-contexts-file=CUSTOM_CONTEXTS_FILE + Path to a local JSON or YAML file containing custom contexts one + wants to set on an object. For example: + + 1. The following JSON document shows two key value pairs, i.e. (key1, + value1) and (key2, value2): + + { + "key1": {"value": "value1"}, + "key2": {"value": "value2"} + } + + 2. The following YAML document shows two key value pairs, i.e. (key1, + value1) and (key2, value2): + + key1: + value: value1 + key2: + value: value2 + + Note: Currently object contexts only supports string format for + values. + + Flags that preserve the existing contexts on the object, and can be + specified together. However they cannot be specified with + --clear-custom-contexts, --custom-contexts or --custom-contexts-file. If + --update-custom-contexts and --remove-custom-contexts are specified + together, the --remove-custom-contexts would be applied first on object. + + --remove-custom-contexts=[CUSTOM_CONTEXTS_KEYS,...] + Removes the custom contexts on the object, if an entry is not + found, it would be ignored. + + --update-custom-contexts=[CUSTOM_CONTEXTS_KEYS_AND_VALUES,...] + Updates the custom contexts on the object, if an entry is found, it + would be overwritten, otherwise the entry would be added. + At most one of these can be specified: --clear-custom-metadata diff --git a/gcloud/alpha/transfer/jobs/create b/gcloud/alpha/transfer/jobs/create index 36d4e7fea..2db45ef0a 100644 --- a/gcloud/alpha/transfer/jobs/create +++ b/gcloud/alpha/transfer/jobs/create @@ -176,9 +176,9 @@ FLAGS --replication Enable replication to automatically copy all new and existing objects - from the source to the destination. Important: Objects deleted from - the source bucket will not be deleted from the destination bucket. - Please note that it is an event-driven transfer. + from the source to the destination. Note: Objects deleted from the + source bucket will not be deleted from the destination bucket. Please + note that it is an event-driven transfer. EVENT STREAM diff --git a/gcloud/beta/colab/schedules/create b/gcloud/beta/colab/schedules/create index 78ffe690a..c94203f51 100644 --- a/gcloud/beta/colab/schedules/create +++ b/gcloud/beta/colab/schedules/create @@ -81,7 +81,7 @@ REQUIRED FLAGS scheduled_run_count >= max_run_count. If neither end time nor max_run_count is specified, new runs will keep getting scheduled until this Schedule is paused or deleted. Must be in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" --max-concurrent-runs=MAX_CONCURRENT_RUNS; default=1 @@ -96,7 +96,7 @@ REQUIRED FLAGS --start-time=START_TIME The timestamp after which the first run can be scheduled. Defaults to the schedule creation time. Must be in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" Configuration of the execution job. diff --git a/gcloud/beta/colab/schedules/update b/gcloud/beta/colab/schedules/update index 411f1c27e..fd4361e33 100644 --- a/gcloud/beta/colab/schedules/update +++ b/gcloud/beta/colab/schedules/update @@ -79,7 +79,7 @@ REQUIRED FLAGS scheduled_run_count >= max_run_count. If neither end time nor max_run_count is specified, new runs will keep getting scheduled until this Schedule is paused or deleted. Must be in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" --max-concurrent-runs=MAX_CONCURRENT_RUNS @@ -94,7 +94,7 @@ REQUIRED FLAGS --start-time=START_TIME The timestamp after which the first run can be scheduled. Defaults to the schedule creation time. Must be in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" GCLOUD WIDE FLAGS diff --git a/gcloud/beta/compute/backend-services/add-backend b/gcloud/beta/compute/backend-services/add-backend index b4a375788..123d12444 100644 --- a/gcloud/beta/compute/backend-services/add-backend +++ b/gcloud/beta/compute/backend-services/add-backend @@ -14,14 +14,15 @@ SYNOPSIS [--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER] [--description=DESCRIPTION] [--failover] [--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE] + [--traffic-duration=TRAFFIC_DURATION] [--custom-metrics=[CUSTOM_METRICS,...] | --custom-metrics-file=[CUSTOM_METRICS,...]] [--global | --region=REGION] [--max-connections=MAX_CONNECTIONS | --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT | --max-connections-per-instance=MAX_CONNECTIONS_PER_INSTANCE - | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT - | --max-rate-per-instance=MAX_RATE_PER_INSTANCE] + | --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS + | --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT | --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT | --max-rate-per-instance=MAX_RATE_PER_INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -188,6 +189,19 @@ OPTIONAL FLAGS CUSTOM_METRICS Spreads load based on custom defined and reported metrics. + IN_FLIGHT + Available if the backend service's load balancing scheme is + INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL_MANAGED. + Available if the backend service's protocol is one of HTTP, HTTPS, + or HTTP/2. + + Spreads load based on how many in-flight requests the backend can + handle. + + You must specify exactly one of these additional parameters: + --max-in-flight-requests, --max-in-flight-requests-per-instance, or + --max-in-flight-requests-per-endpoint, and --traffic-duration=LONG. + RATE Available if the backend service's load balancing scheme is INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL. Available if @@ -256,6 +270,20 @@ OPTIONAL FLAGS Backends with this preference setting are used up to their capacity limits first, while optimizing overall network latency. + --traffic-duration=TRAFFIC_DURATION + The expected traffic duration for this service. TRAFFIC_DURATION must + be one of: + + LONG + Most of the requests are expected to take more than multiple + seconds to finish. + + SHORT + Most requests are expected to finish with a sub-second latency. + + TRAFFIC_DURATION_UNSPECIFIED + Default value. Defaults to SHORT. + At most one of these can be specified: --custom-metrics=[CUSTOM_METRICS,...] @@ -372,6 +400,29 @@ OPTIONAL FLAGS number of instances in the instance group, and then dividing by the number of healthy instances. + --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS + Maximum number of in-flight requests that the backend can handle. + + This cannot be used when the endpoint type of an attached network + endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or + SERVERLESS. + + --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT + Only valid for network endpoint group backends. Defines the maximum + number of in-flight requests per endpoint. + + This cannot be used when the endpoint type of an attached network + endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or + SERVERLESS. + + --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE + Only valid for instance group backends. Defines the maximum number of + in-flight requests per instance. + + This cannot be used when the endpoint type of an attached network + endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or + SERVERLESS. + --max-rate=MAX_RATE Maximum number of HTTP requests per second (RPS) that the backend can handle. Valid for network endpoint group and instance group backends diff --git a/gcloud/beta/compute/backend-services/update-backend b/gcloud/beta/compute/backend-services/update-backend index 9ba21e668..864bf1cb8 100644 --- a/gcloud/beta/compute/backend-services/update-backend +++ b/gcloud/beta/compute/backend-services/update-backend @@ -12,14 +12,15 @@ SYNOPSIS [--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER] [--description=DESCRIPTION] [--failover] [--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE] + [--traffic-duration=TRAFFIC_DURATION] [--clear-custom-metrics | --custom-metrics=[CUSTOM_METRICS,...] | --custom-metrics-file=[CUSTOM_METRICS,...]] [--global | --region=REGION] [--max-connections=MAX_CONNECTIONS | --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT | --max-connections-per-instance=MAX_CONNECTIONS_PER_INSTANCE - | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT - | --max-rate-per-instance=MAX_RATE_PER_INSTANCE] + | --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS + | --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT | --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT | --max-rate-per-instance=MAX_RATE_PER_INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -160,6 +161,19 @@ OPTIONAL FLAGS CUSTOM_METRICS Spreads load based on custom defined and reported metrics. + IN_FLIGHT + Available if the backend service's load balancing scheme is + INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL_MANAGED. + Available if the backend service's protocol is one of HTTP, HTTPS, + or HTTP/2. + + Spreads load based on how many in-flight requests the backend can + handle. + + You must specify exactly one of these additional parameters: + --max-in-flight-requests, --max-in-flight-requests-per-instance, or + --max-in-flight-requests-per-endpoint, and --traffic-duration=LONG. + RATE Available if the backend service's load balancing scheme is INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL. Available if @@ -225,6 +239,20 @@ OPTIONAL FLAGS Backends with this preference setting are used up to their capacity limits first, while optimizing overall network latency. + --traffic-duration=TRAFFIC_DURATION + The expected traffic duration for this service. TRAFFIC_DURATION must + be one of: + + LONG + Most of the requests are expected to take more than multiple + seconds to finish. + + SHORT + Most requests are expected to finish with a sub-second latency. + + TRAFFIC_DURATION_UNSPECIFIED + Default value. Defaults to SHORT. + At most one of these can be specified: --clear-custom-metrics @@ -336,6 +364,17 @@ OPTIONAL FLAGS number of instances in the instance group, and then dividing by the number of healthy instances. + --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS + Maximum number of in-flight requests that the backend can handle. + + --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT + Only valid for network endpoint group backends. Defines the maximum + number of in-flight requests per endpoint. + + --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE + Only valid for instance group backends. Defines the maximum number of + in-flight requests per instance. + --max-rate=MAX_RATE Maximum number of HTTP requests per second (RPS) that the backend can handle. Valid for network endpoint group and instance group backends diff --git a/gcloud/beta/compute/health-sources/create b/gcloud/beta/compute/health-sources/create new file mode 100644 index 000000000..f8667d291 --- /dev/null +++ b/gcloud/beta/compute/health-sources/create @@ -0,0 +1,100 @@ +NAME + gcloud beta compute health-sources create - create a health source + +SYNOPSIS + gcloud beta compute health-sources create (HEALTH_SOURCE : --region=REGION) + --health-aggregation-policy=HEALTH_AGGREGATION_POLICY + --sources=[SOURCES,...] [--async] [--description=DESCRIPTION] + [--source-type=SOURCE_TYPE; default="backend-service"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a health source. + +EXAMPLES + The following command creates a new health source: + + $ gcloud beta compute health-sources create \ + --region= --source-type=BACKEND_SERVICE \ + --sources=my-backend-service \ + --health-aggregation-policy=my-health-aggregation-policy + +POSITIONAL ARGUMENTS + Health source resource - The name of the health source you want to create. + The arguments in this group can be used to specify the attributes of this + 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 health_source on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_SOURCE + ID of the health source or fully qualified identifier for the health + source. + + To set the health_source attribute: + ▸ provide the argument health_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_source on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + --health-aggregation-policy=HEALTH_AGGREGATION_POLICY + URL to the health aggregation policy resource. Must be set. Must be + regional and in the same region as the HealthSource. Can be mutated. + + --sources=[SOURCES,...] + URLs to the source resources. Must be size 1. Must be a BackendService + if the sourceType is BACKEND_SERVICE. The BackendService must have load + balancing scheme INTERNAL or INTERNAL_MANAGED and must be regional and + in the same region as the HealthSource (cross-region deployment for + INTERNAL_MANAGED is not supported). The BackendService may use only + IGs, MIGs, or NEGs of type GCE_VM_IP or GCE_VM_IP_PORT. The + BackendService may not use haPolicy. Can be mutated. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A textual description of the HealthSource. + + --source-type=SOURCE_TYPE; default="backend-service" + Specifies the type of the HealthSource. The only allowed value is + BACKEND_SERVICE. Must be specified when the HealthSource is created, + and cannot be mutated. SOURCE_TYPE must be (only one value is + supported): backend-service. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute health-sources create + diff --git a/gcloud/beta/compute/health-sources/delete b/gcloud/beta/compute/health-sources/delete new file mode 100644 index 000000000..668698353 --- /dev/null +++ b/gcloud/beta/compute/health-sources/delete @@ -0,0 +1,72 @@ +NAME + gcloud beta compute health-sources delete - delete a health source + +SYNOPSIS + gcloud beta compute health-sources delete (HEALTH_SOURCE : --region=REGION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a health source. + +EXAMPLES + To delete a single health source, run the following command: + + $ gcloud beta compute health-sources delete \ + --region= + +POSITIONAL ARGUMENTS + Health source resource - Name of the health source you want to delete. The + arguments in this group can be used to specify the attributes of this + 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 health_source on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_SOURCE + ID of the health source or fully qualified identifier for the health + source. + + To set the health_source attribute: + ▸ provide the argument health_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_source on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute health-sources delete + diff --git a/gcloud/beta/compute/health-sources/describe b/gcloud/beta/compute/health-sources/describe new file mode 100644 index 000000000..9caf6b9f5 --- /dev/null +++ b/gcloud/beta/compute/health-sources/describe @@ -0,0 +1,68 @@ +NAME + gcloud beta compute health-sources describe - describe a health source + +SYNOPSIS + gcloud beta compute health-sources describe + (HEALTH_SOURCE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a health source. + +EXAMPLES + To retrieve a single health source and print its properties, run the + following command: + + $ gcloud beta compute health-sources describe \ + --region= + +POSITIONAL ARGUMENTS + Health source resource - Name of the health source you want to inspect. + The arguments in this group can be used to specify the attributes of this + 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 health_source on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_SOURCE + ID of the health source or fully qualified identifier for the health + source. + + To set the health_source attribute: + ▸ provide the argument health_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_source on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute health-sources describe + diff --git a/gcloud/beta/compute/health-sources/help b/gcloud/beta/compute/health-sources/help new file mode 100644 index 000000000..a7f2fabf0 --- /dev/null +++ b/gcloud/beta/compute/health-sources/help @@ -0,0 +1,38 @@ +NAME + gcloud beta compute health-sources - manage health sources + +SYNOPSIS + gcloud beta compute health-sources COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage health sources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a health source. + + delete + (BETA) Delete a health source. + + describe + (BETA) Describe a health source. + + list + (BETA) List health sources. + + update + (BETA) Update a health source. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute health-sources + diff --git a/gcloud/beta/compute/health-sources/list b/gcloud/beta/compute/health-sources/list new file mode 100644 index 000000000..2184c3670 --- /dev/null +++ b/gcloud/beta/compute/health-sources/list @@ -0,0 +1,77 @@ +NAME + gcloud beta compute health-sources list - list health sources + +SYNOPSIS + gcloud beta compute health-sources list [NAME ...] + [--regexp=REGEXP, -r REGEXP] [--regions=REGION,[REGION,...]] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List health sources. + +POSITIONAL ARGUMENTS + [NAME ...] + (DEPRECATED) If provided, show details for the specified names and/or + URIs of resources. + + Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" + instead. + +FLAGS + --regexp=REGEXP, -r REGEXP + (DEPRECATED) Regular expression to filter the names of the results on. + Any names that do not match the entire regular expression will be + filtered out. + + Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. + + --regions=REGION,[REGION,...] + If provided, only resources from the given regions are queried. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute health-sources list + diff --git a/gcloud/beta/compute/health-sources/update b/gcloud/beta/compute/health-sources/update new file mode 100644 index 000000000..af002c218 --- /dev/null +++ b/gcloud/beta/compute/health-sources/update @@ -0,0 +1,96 @@ +NAME + gcloud beta compute health-sources update - update a health source + +SYNOPSIS + gcloud beta compute health-sources update (HEALTH_SOURCE : --region=REGION) + (--description=DESCRIPTION + --health-aggregation-policy=HEALTH_AGGREGATION_POLICY + --sources=[SOURCES,...]) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a health source. + +EXAMPLES + The following command updates a new health source named "my-health-source": + + $ gcloud beta compute health-sources update \ + --region= --source-type=BACKEND_SERVICE \ + --sources=my-backend-service \ + --health-aggregation-policy=my-health-aggregation-policy + +POSITIONAL ARGUMENTS + Health source resource - The name of the health source you want to create. + The arguments in this group can be used to specify the attributes of this + 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 health_source on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + HEALTH_SOURCE + ID of the health source or fully qualified identifier for the health + source. + + To set the health_source attribute: + ▸ provide the argument health_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Google Compute Engine region. + + To set the region attribute: + ▸ provide the argument health_source on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + At least one of these must be specified: + + --description=DESCRIPTION + A textual description of the health source. + + --health-aggregation-policy=HEALTH_AGGREGATION_POLICY + URL to the health aggregation policy resource. Must be set. Must be + regional and in the same region as the HealthSource. Can be mutated. + + --sources=[SOURCES,...] + URLs to the source resources. Must be size 1. Must be a + BackendService if the sourceType is BACKEND_SERVICE. The + BackendService must have load balancing scheme INTERNAL or + INTERNAL_MANAGED and must be regional and in the same region as the + HealthSource (cross-region deployment for INTERNAL_MANAGED is not + supported). The BackendService may use only IGs, MIGs, or NEGs of + type GCE_VM_IP or GCE_VM_IP_PORT. The BackendService may not use + haPolicy. Can be mutated. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/beta API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute health-sources update + diff --git a/gcloud/beta/compute/help b/gcloud/beta/compute/help index cfdb04ecc..0440fdd0e 100644 --- a/gcloud/beta/compute/help +++ b/gcloud/beta/compute/help @@ -74,6 +74,9 @@ GROUPS health-checks (BETA) Read and manipulate health checks for load balanced instances. + health-sources + (BETA) Manage health sources. + http-health-checks (BETA) Read and manipulate HTTP health checks for load balanced instances. diff --git a/gcloud/beta/compute/routers/create b/gcloud/beta/compute/routers/create index 075c7b669..7b8770287 100644 --- a/gcloud/beta/compute/routers/create +++ b/gcloud/beta/compute/routers/create @@ -101,7 +101,11 @@ OPTIONAL FLAGS CLOUDSDK_COMPUTE_REGION. --resource-manager-tags=[KEY=VALUE,...] - A comma-separated list of Resource Manager tags to apply to the router. + Comma-separated list of Resource Manager tags to attach to the router. + Key-value pairs must be provided in the form + tagKeys/{TagKey_Numeric_ID}=tagValues/{TagValue_Numeric_ID}. See + Listing tag keys + (https://cloud.google.com/resource-manager/docs/tags/tags-creating-and-managing#listing_keys). --set-advertisement-groups=[GROUP,...] The list of pre-defined groups of IP ranges to dynamically advertise on diff --git a/gcloud/beta/compute/tpus/create b/gcloud/beta/compute/tpus/create index 59a322ac3..8b0704a1f 100644 --- a/gcloud/beta/compute/tpus/create +++ b/gcloud/beta/compute/tpus/create @@ -9,7 +9,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a new Cloud TPU. + (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm create instead. + + Create a new Cloud TPU. EXAMPLES The following command creates a TPU with ID my-tpu in the default user diff --git a/gcloud/beta/compute/tpus/delete b/gcloud/beta/compute/tpus/delete index a6a21d9fc..78eaee343 100644 --- a/gcloud/beta/compute/tpus/delete +++ b/gcloud/beta/compute/tpus/delete @@ -6,7 +6,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Deletes a Cloud TPU. + (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm delete instead. + + Deletes a Cloud TPU. EXAMPLES The following command deletes a TPU with ID my-tpu in zone us-central1-b: diff --git a/gcloud/beta/compute/tpus/describe b/gcloud/beta/compute/tpus/describe index 00802b710..d9e0d11a1 100644 --- a/gcloud/beta/compute/tpus/describe +++ b/gcloud/beta/compute/tpus/describe @@ -6,7 +6,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe a Cloud TPU. + (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm describe instead. + + Describe a Cloud TPU. EXAMPLES The following command describes a TPU with ID my-tpu in zone us-central1-b: diff --git a/gcloud/beta/compute/tpus/help b/gcloud/beta/compute/tpus/help index 3d05a12c5..6cf0dd105 100644 --- a/gcloud/beta/compute/tpus/help +++ b/gcloud/beta/compute/tpus/help @@ -38,25 +38,25 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create a new Cloud TPU. + (BETA) (DEPRECATED) Create a new Cloud TPU. delete - (BETA) Deletes a Cloud TPU. + (BETA) (DEPRECATED) Deletes a Cloud TPU. describe - (BETA) Describe a Cloud TPU. + (BETA) (DEPRECATED) Describe a Cloud TPU. list - (BETA) List Cloud TPUs. + (BETA) (DEPRECATED) List Cloud TPUs. reimage - (BETA) Reimages the OS on a Cloud TPU. + (BETA) (DEPRECATED) Reimages the OS on a Cloud TPU. start - (BETA) Start a Cloud TPU. + (BETA) (DEPRECATED) Start a Cloud TPU. stop - (BETA) Stop a Cloud TPU. + (BETA) (DEPRECATED) Stop a Cloud TPU. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/compute/tpus/list b/gcloud/beta/compute/tpus/list index 0ee41bc0a..7a320d14e 100644 --- a/gcloud/beta/compute/tpus/list +++ b/gcloud/beta/compute/tpus/list @@ -7,7 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Cloud TPUs + (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm list instead. + + List Cloud TPUs EXAMPLES The following command lists the status of TPUs in zone us-central1-b: diff --git a/gcloud/beta/compute/tpus/reimage b/gcloud/beta/compute/tpus/reimage index 7e2708b19..e580a4605 100644 --- a/gcloud/beta/compute/tpus/reimage +++ b/gcloud/beta/compute/tpus/reimage @@ -6,7 +6,10 @@ SYNOPSIS [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Reimages the OS on a Cloud TPU. + (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm reimage instead. + + Reimages the OS on a Cloud TPU. EXAMPLES The following command reimages a TPU with ID my-tpu in zone us-central1-b diff --git a/gcloud/beta/compute/tpus/start b/gcloud/beta/compute/tpus/start index ceed0aab9..e0bcab259 100644 --- a/gcloud/beta/compute/tpus/start +++ b/gcloud/beta/compute/tpus/start @@ -6,7 +6,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Start a Cloud TPU. + (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm start instead. + + Start a Cloud TPU. EXAMPLES The following command starts a TPU with ID my-tpu in zone us-central1-b: diff --git a/gcloud/beta/compute/tpus/stop b/gcloud/beta/compute/tpus/stop index d07018386..03401e788 100644 --- a/gcloud/beta/compute/tpus/stop +++ b/gcloud/beta/compute/tpus/stop @@ -6,7 +6,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Stop a Cloud TPU. + (BETA) (DEPRECATED) This command is being deprecated. Please use gcloud + compute tpus tpu-vm stop instead. + + Stop a Cloud TPU. EXAMPLES The following command stops a TPU with ID my-tpu in zone us-central1-b: diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index d78a3ef20..abca0eb46 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -189,15 +189,14 @@ FLAGS (Optional) The NVIDIA driver version to install. GPU_DRIVER_VERSION must be one of: - `default`: Install the default driver version for this GKE version. + `default`: Install the default driver version for this GKE version. For GKE version 1.30.1-gke.1156000 and later, this is the default option. `latest`: Install the latest driver version available for this GKE version. Can only be used for nodes that use Container-Optimized OS. `disabled`: Skip automatic driver installation. You must manually install a - driver after you create the cluster. If you omit the flag `gpu-driver-version`, - this is the default option. To learn how to manually install the GPU driver, - refer to: https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers + driver after you create the cluster. For GKE version 1.30.1-gke.1156000 and earlier, this is the default option. + To manually install the GPU driver, refer to https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers. gpu-partition-size (Optional) The GPU partition size used when running multi-instance @@ -1077,9 +1076,11 @@ FLAGS $ gcloud beta container clusters create example-cluster \ --node-labels=label-a=value1,label-2=value2 - New nodes, including ones created by resize or recreate, will have - these labels on the Kubernetes API node object and can be used in - nodeSelectors. See + Updating the node pool's --node-labels flag applies the labels to the + Kubernetes Node objects for existing nodes in-place; it does not + re-create or replace nodes. New nodes, including ones created by + resizing or re-creating nodes, will have these labels on the Kubernetes + API Node object. The labels can be used in the nodeSelector field. See https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ for examples. @@ -1571,8 +1572,18 @@ FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1, 2} + net.ipv4.tcp_mtu_probing Must be {0, 1, 2} net.ipv4.tcp_max_orphans Must be between [16384, 262144] + net.ipv4.tcp_max_tw_buckets Must be between + [4096, 2147483647] + net.ipv4.tcp_syn_retries Must be between + [1, 127] + net.ipv4.tcp_ecn Must be {0, 1, 2} + net.ipv4.tcp_congestion_control Must be string + containing only + letters and + numbers net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -1598,6 +1609,16 @@ FLAGS [0, 184467440736927743 99] + kernel.perf_event_paranoid Must be {-1, 0, 1, + 2, 3} + kernel.sched_rt_runtime_us Must be [-1, + 1000000] + kernel.softlockup_panic Must be {0, 1} + kernel.yama.ptrace_scope Must be {0, 1, 2, + 3} + kernel.kptr_restrict Must be {0, 1, 2} + kernel.dmesg_restrict Must be {0, 1} + kernel.sysrq Must be [0, 511] fs.aio-max-nr Must be between [65536, 4194304] fs.file-max Must be between @@ -1611,10 +1632,14 @@ FLAGS 2147483584] vm.dirty_background_ratio Must be between [1, 100] + vm.dirty_background_bytes Must be between + [0, 68719476736] vm.dirty_expire_centisecs Must be between [0, 6000] vm.dirty_ratio Must be between [1, 100] + vm.dirty_bytes Must be between + [0, 68719476736] vm.dirty_writeback_centisecs Must be between [0, 1000] vm.max_map_count Must be between diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 6818038f9..c19a40e91 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -65,8 +65,8 @@ SYNOPSIS --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE | --enable-binauthz | --clear-fleet-project --enable-fleet --fleet-project=PROJECT_ID_OR_NUMBER - --membership-type=MEMBERSHIP_TYPE | --clear-maintenance-window - | --remove-maintenance-exclusion=NAME + --membership-type=MEMBERSHIP_TYPE --unset-membership-type + | --clear-maintenance-window | --remove-maintenance-exclusion=NAME | [--add-maintenance-exclusion-end=TIME_STAMP : --add-maintenance-exclusion-name=NAME --add-maintenance-exclusion-scope=SCOPE @@ -1035,6 +1035,11 @@ REQUIRED FLAGS LIGHTWEIGHT Fleet membership representing this cluster will be lightweight. + --unset-membership-type + Set the membership type for the cluster's fleet membership to empty. + Example: $ gcloud beta container clusters update + --unset-membership-type + At most one of these can be specified: --clear-maintenance-window diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 9e0702e0f..bf1694aea 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -122,15 +122,14 @@ FLAGS (Optional) The NVIDIA driver version to install. GPU_DRIVER_VERSION must be one of: - `default`: Install the default driver version for this GKE version. + `default`: Install the default driver version for this GKE version. For GKE version 1.30.1-gke.1156000 and later, this is the default option. `latest`: Install the latest driver version available for this GKE version. Can only be used for nodes that use Container-Optimized OS. `disabled`: Skip automatic driver installation. You must manually install a - driver after you create the cluster. If you omit the flag `gpu-driver-version`, - this is the default option. To learn how to manually install the GPU driver, - refer to: https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers + driver after you create the cluster. For GKE version 1.30.1-gke.1156000 and earlier, this is the default option. + To manually install the GPU driver, refer to https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers. gpu-partition-size (Optional) The GPU partition size used when running multi-instance @@ -527,9 +526,11 @@ FLAGS --cluster=example-cluster \ --node-labels=label1=value1,label2=value2 - New nodes, including ones created by resize or recreate, will have - these labels on the Kubernetes API node object and can be used in - nodeSelectors. See + Updating the node pool's --node-labels flag applies the labels to the + Kubernetes Node objects for existing nodes in-place; it does not + re-create or replace nodes. New nodes, including ones created by + resizing or re-creating nodes, will have these labels on the Kubernetes + API Node object. The labels can be used in the nodeSelector field. See https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ for examples. @@ -956,8 +957,18 @@ FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1, 2} + net.ipv4.tcp_mtu_probing Must be {0, 1, 2} net.ipv4.tcp_max_orphans Must be between [16384, 262144] + net.ipv4.tcp_max_tw_buckets Must be between + [4096, 2147483647] + net.ipv4.tcp_syn_retries Must be between + [1, 127] + net.ipv4.tcp_ecn Must be {0, 1, 2} + net.ipv4.tcp_congestion_control Must be string + containing only + letters and + numbers net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -983,6 +994,16 @@ FLAGS [0, 184467440736927743 99] + kernel.perf_event_paranoid Must be {-1, 0, 1, + 2, 3} + kernel.sched_rt_runtime_us Must be [-1, + 1000000] + kernel.softlockup_panic Must be {0, 1} + kernel.yama.ptrace_scope Must be {0, 1, 2, + 3} + kernel.kptr_restrict Must be {0, 1, 2} + kernel.dmesg_restrict Must be {0, 1} + kernel.sysrq Must be [0, 511] fs.aio-max-nr Must be between [65536, 4194304] fs.file-max Must be between @@ -996,10 +1017,14 @@ FLAGS 2147483584] vm.dirty_background_ratio Must be between [1, 100] + vm.dirty_background_bytes Must be between + [0, 68719476736] vm.dirty_expire_centisecs Must be between [0, 6000] vm.dirty_ratio Must be between [1, 100] + vm.dirty_bytes Must be between + [0, 68719476736] vm.dirty_writeback_centisecs Must be between [0, 1000] vm.max_map_count Must be between diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index 26fd868ba..b80bbc98b 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -79,15 +79,14 @@ REQUIRED FLAGS (Optional) The NVIDIA driver version to install. GPU_DRIVER_VERSION must be one of: - `default`: Install the default driver version for this GKE version. + `default`: Install the default driver version for this GKE version. For GKE version 1.30.1-gke.1156000 and later, this is the default option. `latest`: Install the latest driver version available for this GKE version. Can only be used for nodes that use Container-Optimized OS. `disabled`: Skip automatic driver installation. You must manually install a - driver after you create the cluster. If you omit the flag `gpu-driver-version`, - this is the default option. To learn how to manually install the GPU driver, - refer to: https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers + driver after you create the cluster. For GKE version 1.30.1-gke.1156000 and earlier, this is the default option. + To manually install the GPU driver, refer to https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers. gpu-partition-size (Optional) The GPU partition size used when running @@ -217,9 +216,12 @@ REQUIRED FLAGS --cluster=example-cluster \ --node-labels=label1=value1,label2=value2 - New nodes, including ones created by resize or recreate, will have - these labels on the Kubernetes API node object and can be used in - nodeSelectors. See + Updating the node pool's --node-labels flag applies the labels to the + Kubernetes Node objects for existing nodes in-place; it does not + re-create or replace nodes. New nodes, including ones created by + resizing or re-creating nodes, will have these labels on the + Kubernetes API Node object. The labels can be used in the + nodeSelector field. See https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ for examples. @@ -499,8 +501,21 @@ REQUIRED FLAGS integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1, 2} + net.ipv4.tcp_mtu_probing Must be {0, 1, + 2} net.ipv4.tcp_max_orphans Must be between [16384, 262144] + net.ipv4.tcp_max_tw_buckets Must be between + [4096, + 2147483647] + net.ipv4.tcp_syn_retries Must be between + [1, 127] + net.ipv4.tcp_ecn Must be {0, 1, + 2} + net.ipv4.tcp_congestion_control Must be string + containing only + letters and + numbers net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -528,6 +543,17 @@ REQUIRED FLAGS [0, 1844674407369277 4399] + kernel.perf_event_paranoid Must be {-1, 0, + 1, 2, 3} + kernel.sched_rt_runtime_us Must be [-1, + 1000000] + kernel.softlockup_panic Must be {0, 1} + kernel.yama.ptrace_scope Must be {0, 1, + 2, 3} + kernel.kptr_restrict Must be {0, 1, + 2} + kernel.dmesg_restrict Must be {0, 1} + kernel.sysrq Must be [0, 511] fs.aio-max-nr Must be between [65536, 4194304] fs.file-max Must be between @@ -542,10 +568,14 @@ REQUIRED FLAGS 2147483584] vm.dirty_background_ratio Must be between [1, 100] + vm.dirty_background_bytes Must be between + [0, 68719476736] vm.dirty_expire_centisecs Must be between [0, 6000] vm.dirty_ratio Must be between [1, 100] + vm.dirty_bytes Must be between + [0, 68719476736] vm.dirty_writeback_centisecs Must be between [0, 1000] vm.max_map_count Must be between diff --git a/gcloud/beta/recommender/insights/describe b/gcloud/beta/recommender/insights/describe index 1ecb3c781..b8681f109 100644 --- a/gcloud/beta/recommender/insights/describe +++ b/gcloud/beta/recommender/insights/describe @@ -15,8 +15,9 @@ DESCRIPTION EXAMPLES To describe an insight: - $ gcloud beta recommender insights describe INSIGHT_ID \ - --project=${PROJECT} --location=${LOCATION} + $ gcloud beta recommender insights describe \ + --insight-type=${INSIGHT_TYPE} --project=${PROJECT} \ + --location=${LOCATION} POSITIONAL ARGUMENTS INSIGHT diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 8bb9e87a7..bafbbb539 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -53,6 +53,7 @@ SYNOPSIS [--remove-deny-maintenance-period] [--replication=REPLICATION] [--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE] [--[no-]require-ssl] [--[no-]retain-backups-on-delete] + [--server-ca-mode=SERVER_CA_MODE] [--server-ca-pool=SERVER_CA_POOL] [--simulate-maintenance-event] [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] @@ -450,6 +451,21 @@ FLAGS deleted. Use --retain-backups-on-delete to enable and --no-retain-backups-on-delete to disable. + --server-ca-mode=SERVER_CA_MODE + Set the server CA mode of the instance. SERVER_CA_MODE must be one of: + + CUSTOMER_MANAGED_CAS_CA + Customer-managed CA hosted on Google Cloud's Certificate Authority + Service (CAS). + GOOGLE_MANAGED_CAS_CA + Google-managed regional CA part of root CA hierarchy hosted on + Google Cloud's Certificate Authority Service (CAS). + GOOGLE_MANAGED_INTERNAL_CA + Google-managed self-signed internal CA. + + --server-ca-pool=SERVER_CA_POOL + Set the server CA pool of the instance. + --simulate-maintenance-event Simulate a maintenance event without changing the version. Only applicable to instances that support near-zero downtime planned diff --git a/gcloud/beta/sql/instances/reset-ssl-config b/gcloud/beta/sql/instances/reset-ssl-config index 011a21983..b6119d9df 100644 --- a/gcloud/beta/sql/instances/reset-ssl-config +++ b/gcloud/beta/sql/instances/reset-ssl-config @@ -3,7 +3,7 @@ NAME to the reset SSL mode SYNOPSIS - gcloud beta sql instances reset-ssl-config INSTANCE [--async] + gcloud beta sql instances reset-ssl-config INSTANCE [--async] [--mode=MODE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -18,6 +18,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --mode=MODE + Selectively refresh the SSL materials. MODE must be one of: + + ALL + Refresh all TLS configs. This is the default behaviour. + SYNC_FROM_PRIMARY + Refreshes the replication-related TLS configuration settings + provided by the primary instance. Not applicable to on-premises + replication instances. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/workbench/schedules/create b/gcloud/beta/workbench/schedules/create index 1aa2a21f3..65d018982 100644 --- a/gcloud/beta/workbench/schedules/create +++ b/gcloud/beta/workbench/schedules/create @@ -105,7 +105,7 @@ REQUIRED FLAGS scheduled_run_count >= max_run_count. If neither end time nor max_run_count is specified, new runs will keep getting scheduled until this Schedule is paused or deleted. Must be in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" --max-concurrent-runs=MAX_CONCURRENT_RUNS; default=1 @@ -120,7 +120,7 @@ REQUIRED FLAGS --start-time=START_TIME The timestamp after which the first run can be scheduled. Defaults to the schedule creation time. Must be in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" Configuration of the execution job. diff --git a/gcloud/beta/workbench/schedules/update b/gcloud/beta/workbench/schedules/update index 2181808c7..43f609163 100644 --- a/gcloud/beta/workbench/schedules/update +++ b/gcloud/beta/workbench/schedules/update @@ -79,7 +79,7 @@ REQUIRED FLAGS scheduled_run_count >= max_run_count. If neither end time nor max_run_count is specified, new runs will keep getting scheduled until this Schedule is paused or deleted. Must be in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" --max-concurrent-runs=MAX_CONCURRENT_RUNS @@ -94,7 +94,7 @@ REQUIRED FLAGS --start-time=START_TIME The timestamp after which the first run can be scheduled. Defaults to the schedule creation time. Must be in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" GCLOUD WIDE FLAGS diff --git a/gcloud/colab/schedules/create b/gcloud/colab/schedules/create index d1bf8ec0d..331b9cf5f 100644 --- a/gcloud/colab/schedules/create +++ b/gcloud/colab/schedules/create @@ -81,7 +81,7 @@ REQUIRED FLAGS scheduled_run_count >= max_run_count. If neither end time nor max_run_count is specified, new runs will keep getting scheduled until this Schedule is paused or deleted. Must be in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" --max-concurrent-runs=MAX_CONCURRENT_RUNS; default=1 @@ -96,7 +96,7 @@ REQUIRED FLAGS --start-time=START_TIME The timestamp after which the first run can be scheduled. Defaults to the schedule creation time. Must be in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" Configuration of the execution job. diff --git a/gcloud/colab/schedules/update b/gcloud/colab/schedules/update index 450eea6ae..14ed0be00 100644 --- a/gcloud/colab/schedules/update +++ b/gcloud/colab/schedules/update @@ -78,7 +78,7 @@ REQUIRED FLAGS scheduled_run_count >= max_run_count. If neither end time nor max_run_count is specified, new runs will keep getting scheduled until this Schedule is paused or deleted. Must be in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" --max-concurrent-runs=MAX_CONCURRENT_RUNS @@ -93,7 +93,7 @@ REQUIRED FLAGS --start-time=START_TIME The timestamp after which the first run can be scheduled. Defaults to the schedule creation time. Must be in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2026-01-01T00:00:00Z" or "2026-01-01T00:00:00-05:00" GCLOUD WIDE FLAGS diff --git a/gcloud/compute/routers/create b/gcloud/compute/routers/create index cd9fb741d..9544fe9fe 100644 --- a/gcloud/compute/routers/create +++ b/gcloud/compute/routers/create @@ -7,6 +7,7 @@ SYNOPSIS [--bgp-identifier-range=BGP_IDENTIFIER_RANGE] [--description=DESCRIPTION] [--encrypted-interconnect-router] [--keepalive-interval=KEEPALIVE_INTERVAL] [--region=REGION] + [--resource-manager-tags=[KEY=VALUE,...]] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] [GCLOUD_WIDE_FLAG ...] @@ -93,6 +94,13 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + --resource-manager-tags=[KEY=VALUE,...] + Comma-separated list of Resource Manager tags to attach to the router. + Key-value pairs must be provided in the form + tagKeys/{TagKey_Numeric_ID}=tagValues/{TagValue_Numeric_ID}. See + Listing tag keys + (https://cloud.google.com/resource-manager/docs/tags/tags-creating-and-managing#listing_keys). + --set-advertisement-groups=[GROUP,...] The list of pre-defined groups of IP ranges to dynamically advertise on this router. This list can only be specified in custom advertisement diff --git a/gcloud/compute/tpus/create b/gcloud/compute/tpus/create index 28c20fedb..ae6920392 100644 --- a/gcloud/compute/tpus/create +++ b/gcloud/compute/tpus/create @@ -8,6 +8,9 @@ SYNOPSIS [--preemptible] [--range=RANGE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) This command is being deprecated. Please use gcloud compute + tpus tpu-vm create instead. + Create a new Cloud TPU. EXAMPLES diff --git a/gcloud/compute/tpus/delete b/gcloud/compute/tpus/delete index 3ecb8c619..aee3bbfcc 100644 --- a/gcloud/compute/tpus/delete +++ b/gcloud/compute/tpus/delete @@ -6,6 +6,9 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) This command is being deprecated. Please use gcloud compute + tpus tpu-vm delete instead. + Deletes a Cloud TPU. EXAMPLES diff --git a/gcloud/compute/tpus/describe b/gcloud/compute/tpus/describe index 0a35972f7..d3f905a2f 100644 --- a/gcloud/compute/tpus/describe +++ b/gcloud/compute/tpus/describe @@ -5,6 +5,9 @@ SYNOPSIS gcloud compute tpus describe (TPU : --zone=ZONE) [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) This command is being deprecated. Please use gcloud compute + tpus tpu-vm describe instead. + Describe a Cloud TPU. EXAMPLES diff --git a/gcloud/compute/tpus/help b/gcloud/compute/tpus/help index 38b342ea7..b9f8db1ad 100644 --- a/gcloud/compute/tpus/help +++ b/gcloud/compute/tpus/help @@ -47,25 +47,25 @@ COMMANDS COMMAND is one of the following: create - Create a new Cloud TPU. + (DEPRECATED) Create a new Cloud TPU. delete - Deletes a Cloud TPU. + (DEPRECATED) Deletes a Cloud TPU. describe - Describe a Cloud TPU. + (DEPRECATED) Describe a Cloud TPU. list - List Cloud TPUs. + (DEPRECATED) List Cloud TPUs. reimage - Reimages the OS on a Cloud TPU. + (DEPRECATED) Reimages the OS on a Cloud TPU. start - Start a Cloud TPU. + (DEPRECATED) Start a Cloud TPU. stop - Stop a Cloud TPU. + (DEPRECATED) Stop a Cloud TPU. NOTES These variants are also available: diff --git a/gcloud/compute/tpus/list b/gcloud/compute/tpus/list index c064bf7f8..552b830ca 100644 --- a/gcloud/compute/tpus/list +++ b/gcloud/compute/tpus/list @@ -7,6 +7,9 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) This command is being deprecated. Please use gcloud compute + tpus tpu-vm list instead. + List Cloud TPUs EXAMPLES diff --git a/gcloud/compute/tpus/reimage b/gcloud/compute/tpus/reimage index 2f97179e4..e5d3eb367 100644 --- a/gcloud/compute/tpus/reimage +++ b/gcloud/compute/tpus/reimage @@ -6,6 +6,9 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) This command is being deprecated. Please use gcloud compute + tpus tpu-vm reimage instead. + Reimages the OS on a Cloud TPU. EXAMPLES diff --git a/gcloud/compute/tpus/start b/gcloud/compute/tpus/start index 0acc858fb..0787a36f9 100644 --- a/gcloud/compute/tpus/start +++ b/gcloud/compute/tpus/start @@ -6,6 +6,9 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) This command is being deprecated. Please use gcloud compute + tpus tpu-vm start instead. + Start a Cloud TPU. EXAMPLES diff --git a/gcloud/compute/tpus/stop b/gcloud/compute/tpus/stop index 319ffda19..8c664ec6c 100644 --- a/gcloud/compute/tpus/stop +++ b/gcloud/compute/tpus/stop @@ -6,6 +6,9 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) This command is being deprecated. Please use gcloud compute + tpus tpu-vm stop instead. + Stop a Cloud TPU. EXAMPLES diff --git a/gcloud/container/attached/clusters/register b/gcloud/container/attached/clusters/register index 874222173..9585a416a 100644 --- a/gcloud/container/attached/clusters/register +++ b/gcloud/container/attached/clusters/register @@ -13,7 +13,8 @@ SYNOPSIS [--description=DESCRIPTION] [--enable-managed-prometheus] [--logging=COMPONENT,[COMPONENT,...]] [--system-component-labels=[LABEL,...]] - [--system-component-tolerations=[TOLERATION,...]] [--validate-only] + [--system-component-tolerations=[TOLERATION,...]] + [--tags=TAG,[TAG,...]] [--validate-only] [--disable-cloud-monitoring | --enable-cloud-monitoring] [--proxy-secret-name=PROXY_SECRET_NAME --proxy-secret-namespace=PROXY_SECRET_NAMESPACE] @@ -197,6 +198,14 @@ OPTIONAL FLAGS --system-component-tolerations=[TOLERATION,...] Kubernetes tolerations to be applied to system component pods. + --tags=TAG,[TAG,...] + Tag keys/values directly bound to this resource. + + The short name of a tag key or value can have a maximum length of 256 + characters. The permitted character set for the short name includes + UTF-8 encoded Unicode characters except single quotes, double quotes, + backslashes, and forward slashes. + --validate-only Validate the cluster to create, but don't actually perform it. diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index ad2492621..d3f2b4c41 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -61,6 +61,7 @@ SYNOPSIS [--max-pods-per-node=MAX_PODS_PER_NODE] [--max-surge-upgrade=MAX_SURGE_UPGRADE; default=1] [--max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE] + [--membership-type=MEMBERSHIP_TYPE] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] [--min-cpu-platform=PLATFORM] [--monitoring=[COMPONENT,...]] @@ -182,15 +183,14 @@ FLAGS (Optional) The NVIDIA driver version to install. GPU_DRIVER_VERSION must be one of: - `default`: Install the default driver version for this GKE version. + `default`: Install the default driver version for this GKE version. For GKE version 1.30.1-gke.1156000 and later, this is the default option. `latest`: Install the latest driver version available for this GKE version. Can only be used for nodes that use Container-Optimized OS. `disabled`: Skip automatic driver installation. You must manually install a - driver after you create the cluster. If you omit the flag `gpu-driver-version`, - this is the default option. To learn how to manually install the GPU driver, - refer to: https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers + driver after you create the cluster. For GKE version 1.30.1-gke.1156000 and earlier, this is the default option. + To manually install the GPU driver, refer to https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers. gpu-partition-size (Optional) The GPU partition size used when running multi-instance @@ -907,6 +907,14 @@ FLAGS Must be used in conjunction with '--max-surge-upgrade'. + --membership-type=MEMBERSHIP_TYPE + Specify a membership type for the cluster's fleet membership. Example: + $ gcloud container clusters create --membership-type=LIGHTWEIGHT. \ + MEMBERSHIP_TYPE must be (only one value is supported): + + LIGHTWEIGHT + Fleet membership representing this cluster will be lightweight. + --metadata=KEY=VALUE,[KEY=VALUE,...] Compute Engine metadata to be made available to the guest operating system running on nodes within the node pool. @@ -1003,9 +1011,11 @@ FLAGS $ gcloud container clusters create example-cluster \ --node-labels=label-a=value1,label-2=value2 - New nodes, including ones created by resize or recreate, will have - these labels on the Kubernetes API node object and can be used in - nodeSelectors. See + Updating the node pool's --node-labels flag applies the labels to the + Kubernetes Node objects for existing nodes in-place; it does not + re-create or replace nodes. New nodes, including ones created by + resizing or re-creating nodes, will have these labels on the Kubernetes + API Node object. The labels can be used in the nodeSelector field. See https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ for examples. @@ -1517,8 +1527,18 @@ FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1, 2} + net.ipv4.tcp_mtu_probing Must be {0, 1, 2} net.ipv4.tcp_max_orphans Must be between [16384, 262144] + net.ipv4.tcp_max_tw_buckets Must be between + [4096, 2147483647] + net.ipv4.tcp_syn_retries Must be between + [1, 127] + net.ipv4.tcp_ecn Must be {0, 1, 2} + net.ipv4.tcp_congestion_control Must be string + containing only + letters and + numbers net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -1544,6 +1564,16 @@ FLAGS [0, 184467440736927743 99] + kernel.perf_event_paranoid Must be {-1, 0, 1, + 2, 3} + kernel.sched_rt_runtime_us Must be [-1, + 1000000] + kernel.softlockup_panic Must be {0, 1} + kernel.yama.ptrace_scope Must be {0, 1, 2, + 3} + kernel.kptr_restrict Must be {0, 1, 2} + kernel.dmesg_restrict Must be {0, 1} + kernel.sysrq Must be [0, 511] fs.aio-max-nr Must be between [65536, 4194304] fs.file-max Must be between @@ -1557,10 +1587,14 @@ FLAGS 2147483584] vm.dirty_background_ratio Must be between [1, 100] + vm.dirty_background_bytes Must be between + [0, 68719476736] vm.dirty_expire_centisecs Must be between [0, 6000] vm.dirty_ratio Must be between [1, 100] + vm.dirty_bytes Must be between + [0, 68719476736] vm.dirty_writeback_centisecs Must be between [0, 1000] vm.max_map_count Must be between diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 1e3755601..7ef058f2a 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -28,12 +28,13 @@ SYNOPSIS [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] [--enable-ray-operator] [--fleet-project=PROJECT_ID_OR_NUMBER] [--hpa-profile=HPA_PROFILE] [--labels=[KEY=VALUE,...]] - [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] - [--network=NETWORK] [--private-endpoint-subnetwork=NAME] - [--release-channel=CHANNEL] [--security-group=SECURITY_GROUP] - [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] - [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] - [--tier=TIER] [--workload-policies=WORKLOAD_POLICIES] + [--logging=[COMPONENT,...]] [--membership-type=MEMBERSHIP_TYPE] + [--monitoring=[COMPONENT,...]] [--network=NETWORK] + [--private-endpoint-subnetwork=NAME] [--release-channel=CHANNEL] + [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] + [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] + [--subnetwork=SUBNETWORK] [--tier=TIER] + [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--additive-vpc-scope-dns-domain=ADDITIVE_VPC_SCOPE_DNS_DOMAIN | --disable-additive-vpc-scope] @@ -386,6 +387,15 @@ FLAGS --logging=SYSTEM,WORKLOAD,API_SERVER,CONTROLLER_MANAGER,\ SCHEDULER + --membership-type=MEMBERSHIP_TYPE + Specify a membership type for the cluster's fleet membership. Example: + $ gcloud container clusters create-auto \ + --membership-type=LIGHTWEIGHT. MEMBERSHIP_TYPE must be (only \ one + value is supported): + + LIGHTWEIGHT + Fleet membership representing this cluster will be lightweight. + --monitoring=[COMPONENT,...] Set the components that have monitoring enabled. Valid component values are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER, diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 4913db23a..4673b6709 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -9,7 +9,7 @@ SYNOPSIS | --autoprovisioning-enable-insecure-kubelet-readonly-port | --autoprovisioning-network-tags=[TAGS,...] | --autoprovisioning-resource-manager-tags=[KEY=VALUE,...] - | --autoscaling-profile=AUTOSCALING_PROFILE | --clear-fleet-project + | --autoscaling-profile=AUTOSCALING_PROFILE | --complete-credential-rotation | --complete-ip-rotation | --containerd-config-from-file=PATH_TO_FILE | --database-encryption-key=DATABASE_ENCRYPTION_KEY @@ -19,9 +19,8 @@ SYNOPSIS | --enable-autoscaling | --[no-]enable-cilium-clusterwide-network-policy | --enable-cost-allocation | --enable-default-compute-class - | --enable-fleet | --enable-fqdn-network-policy - | --enable-identity-service | --enable-image-streaming - | --enable-insecure-kubelet-readonly-port + | --enable-fqdn-network-policy | --enable-identity-service + | --enable-image-streaming | --enable-insecure-kubelet-readonly-port | --enable-intra-node-visibility | --enable-kubernetes-unstable-apis=API,[API,...] | --enable-l4-ilb-subsetting | --enable-legacy-authorization @@ -30,8 +29,7 @@ SYNOPSIS | --[no-]enable-ray-cluster-logging | --[no-]enable-ray-cluster-monitoring | --enable-service-externalips | --enable-shielded-nodes | --enable-stackdriver-kubernetes - | --enable-vertical-pod-autoscaling - | --fleet-project=PROJECT_ID_OR_NUMBER | --gateway-api=GATEWAY_API + | --enable-vertical-pod-autoscaling | --gateway-api=GATEWAY_API | --generate-password | --hpa-profile=HPA_PROFILE | --in-transit-encryption=IN_TRANSIT_ENCRYPTION | --logging-variant=LOGGING_VARIANT | --maintenance-window=START_TIME @@ -61,8 +59,10 @@ SYNOPSIS --monitoring=[COMPONENT,...] --disable-managed-prometheus | --enable-managed-prometheus | --binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE - | --enable-binauthz | --clear-maintenance-window - | --remove-maintenance-exclusion=NAME + | --enable-binauthz | --clear-fleet-project --enable-fleet + --fleet-project=PROJECT_ID_OR_NUMBER + --membership-type=MEMBERSHIP_TYPE --unset-membership-type + | --clear-maintenance-window | --remove-maintenance-exclusion=NAME | [--add-maintenance-exclusion-end=TIME_STAMP : --add-maintenance-exclusion-name=NAME --add-maintenance-exclusion-scope=SCOPE @@ -244,10 +244,6 @@ REQUIRED FLAGS Set autoscaling behaviour, choices are 'optimize-utilization' and 'balanced'. Default is 'balanced'. - --clear-fleet-project - Remove the cluster from current fleet host project. Example: $ gcloud - container clusters update --clear-fleet-project - --complete-credential-rotation Complete the IP and credential rotation for this cluster. For example: @@ -369,12 +365,6 @@ REQUIRED FLAGS To disable Default Compute Class in an existing cluster, explicitly set flag --no-enable-default-compute-class. - --enable-fleet - Set cluster project as the fleet host project. This will register the - cluster to the same project. To register the cluster to a fleet in a - different project, please use --fleet-project=FLEET_HOST_PROJECT. - Example: $ gcloud container clusters update --enable-fleet - --enable-fqdn-network-policy Enable FQDN Network Policies on the cluster. FQDN Network Policies are disabled by default. @@ -489,14 +479,6 @@ REQUIRED FLAGS --enable-vertical-pod-autoscaling Enable vertical pod autoscaling for a cluster. - --fleet-project=PROJECT_ID_OR_NUMBER - Sets fleet host project for the cluster. If specified, the current - cluster will be registered as a fleet membership under the fleet host - project. - - Example: $ gcloud container clusters update - --fleet-project=my-project - --gateway-api=GATEWAY_API Enables GKE Gateway controller in this cluster. The value of the flag specifies which Open Source Gateway API release channel will be used @@ -948,6 +930,37 @@ REQUIRED FLAGS The --enable-binauthz flag is deprecated. Please use --binauthz-evaluation-mode instead. + --clear-fleet-project + Remove the cluster from current fleet host project. Example: $ gcloud + container clusters update --clear-fleet-project + + --enable-fleet + Set cluster project as the fleet host project. This will register the + cluster to the same project. To register the cluster to a fleet in a + different project, please use --fleet-project=FLEET_HOST_PROJECT. + Example: $ gcloud container clusters update --enable-fleet + + --fleet-project=PROJECT_ID_OR_NUMBER + Sets fleet host project for the cluster. If specified, the current + cluster will be registered as a fleet membership under the fleet host + project. + + Example: $ gcloud container clusters update + --fleet-project=my-project + + --membership-type=MEMBERSHIP_TYPE + Specify a membership type for the cluster's fleet membership. + Example: $ gcloud container clusters update + --membership-type=LIGHTWEIGHT. \ MEMBERSHIP_TYPE must be (only one + value is supported): + + LIGHTWEIGHT + Fleet membership representing this cluster will be lightweight. + + --unset-membership-type + Set the membership type for the cluster's fleet membership to empty. + Example: $ gcloud container clusters update --unset-membership-type + At most one of these can be specified: --clear-maintenance-window diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 49d8f3c6f..74f086823 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -119,15 +119,14 @@ FLAGS (Optional) The NVIDIA driver version to install. GPU_DRIVER_VERSION must be one of: - `default`: Install the default driver version for this GKE version. + `default`: Install the default driver version for this GKE version. For GKE version 1.30.1-gke.1156000 and later, this is the default option. `latest`: Install the latest driver version available for this GKE version. Can only be used for nodes that use Container-Optimized OS. `disabled`: Skip automatic driver installation. You must manually install a - driver after you create the cluster. If you omit the flag `gpu-driver-version`, - this is the default option. To learn how to manually install the GPU driver, - refer to: https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers + driver after you create the cluster. For GKE version 1.30.1-gke.1156000 and earlier, this is the default option. + To manually install the GPU driver, refer to https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers. gpu-partition-size (Optional) The GPU partition size used when running multi-instance @@ -515,9 +514,11 @@ FLAGS --cluster=example-cluster \ --node-labels=label1=value1,label2=value2 - New nodes, including ones created by resize or recreate, will have - these labels on the Kubernetes API node object and can be used in - nodeSelectors. See + Updating the node pool's --node-labels flag applies the labels to the + Kubernetes Node objects for existing nodes in-place; it does not + re-create or replace nodes. New nodes, including ones created by + resizing or re-creating nodes, will have these labels on the Kubernetes + API Node object. The labels can be used in the nodeSelector field. See https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ for examples. @@ -944,8 +945,18 @@ FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1, 2} + net.ipv4.tcp_mtu_probing Must be {0, 1, 2} net.ipv4.tcp_max_orphans Must be between [16384, 262144] + net.ipv4.tcp_max_tw_buckets Must be between + [4096, 2147483647] + net.ipv4.tcp_syn_retries Must be between + [1, 127] + net.ipv4.tcp_ecn Must be {0, 1, 2} + net.ipv4.tcp_congestion_control Must be string + containing only + letters and + numbers net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -971,6 +982,16 @@ FLAGS [0, 184467440736927743 99] + kernel.perf_event_paranoid Must be {-1, 0, 1, + 2, 3} + kernel.sched_rt_runtime_us Must be [-1, + 1000000] + kernel.softlockup_panic Must be {0, 1} + kernel.yama.ptrace_scope Must be {0, 1, 2, + 3} + kernel.kptr_restrict Must be {0, 1, 2} + kernel.dmesg_restrict Must be {0, 1} + kernel.sysrq Must be [0, 511] fs.aio-max-nr Must be between [65536, 4194304] fs.file-max Must be between @@ -984,10 +1005,14 @@ FLAGS 2147483584] vm.dirty_background_ratio Must be between [1, 100] + vm.dirty_background_bytes Must be between + [0, 68719476736] vm.dirty_expire_centisecs Must be between [0, 6000] vm.dirty_ratio Must be between [1, 100] + vm.dirty_bytes Must be between + [0, 68719476736] vm.dirty_writeback_centisecs Must be between [0, 1000] vm.max_map_count Must be between diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index ac465355c..09d3771b0 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -79,15 +79,14 @@ REQUIRED FLAGS (Optional) The NVIDIA driver version to install. GPU_DRIVER_VERSION must be one of: - `default`: Install the default driver version for this GKE version. + `default`: Install the default driver version for this GKE version. For GKE version 1.30.1-gke.1156000 and later, this is the default option. `latest`: Install the latest driver version available for this GKE version. Can only be used for nodes that use Container-Optimized OS. `disabled`: Skip automatic driver installation. You must manually install a - driver after you create the cluster. If you omit the flag `gpu-driver-version`, - this is the default option. To learn how to manually install the GPU driver, - refer to: https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers + driver after you create the cluster. For GKE version 1.30.1-gke.1156000 and earlier, this is the default option. + To manually install the GPU driver, refer to https://cloud.google.com/kubernetes-engine/docs/how-to/gpus#installing_drivers. gpu-partition-size (Optional) The GPU partition size used when running @@ -217,9 +216,12 @@ REQUIRED FLAGS --cluster=example-cluster \ --node-labels=label1=value1,label2=value2 - New nodes, including ones created by resize or recreate, will have - these labels on the Kubernetes API node object and can be used in - nodeSelectors. See + Updating the node pool's --node-labels flag applies the labels to the + Kubernetes Node objects for existing nodes in-place; it does not + re-create or replace nodes. New nodes, including ones created by + resizing or re-creating nodes, will have these labels on the + Kubernetes API Node object. The labels can be used in the + nodeSelector field. See https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ for examples. @@ -499,8 +501,21 @@ REQUIRED FLAGS integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1, 2} + net.ipv4.tcp_mtu_probing Must be {0, 1, + 2} net.ipv4.tcp_max_orphans Must be between [16384, 262144] + net.ipv4.tcp_max_tw_buckets Must be between + [4096, + 2147483647] + net.ipv4.tcp_syn_retries Must be between + [1, 127] + net.ipv4.tcp_ecn Must be {0, 1, + 2} + net.ipv4.tcp_congestion_control Must be string + containing only + letters and + numbers net.netfilter.nf_conntrack_max Must be between [65536, 4194304] net.netfilter.nf_conntrack_buckets Must be between @@ -528,6 +543,17 @@ REQUIRED FLAGS [0, 1844674407369277 4399] + kernel.perf_event_paranoid Must be {-1, 0, + 1, 2, 3} + kernel.sched_rt_runtime_us Must be [-1, + 1000000] + kernel.softlockup_panic Must be {0, 1} + kernel.yama.ptrace_scope Must be {0, 1, + 2, 3} + kernel.kptr_restrict Must be {0, 1, + 2} + kernel.dmesg_restrict Must be {0, 1} + kernel.sysrq Must be [0, 511] fs.aio-max-nr Must be between [65536, 4194304] fs.file-max Must be between @@ -542,10 +568,14 @@ REQUIRED FLAGS 2147483584] vm.dirty_background_ratio Must be between [1, 100] + vm.dirty_background_bytes Must be between + [0, 68719476736] vm.dirty_expire_centisecs Must be between [0, 6000] vm.dirty_ratio Must be between [1, 100] + vm.dirty_bytes Must be between + [0, 68719476736] vm.dirty_writeback_centisecs Must be between [0, 1000] vm.max_map_count Must be between diff --git a/gcloud/dataplex/encryption-config/help b/gcloud/dataplex/encryption-config/help index 93de71e7e..c312bf035 100644 --- a/gcloud/dataplex/encryption-config/help +++ b/gcloud/dataplex/encryption-config/help @@ -21,6 +21,9 @@ COMMANDS describe Describe an EncryptionConfig. + update + Update an Encryption Config. + NOTES This variant is also available: diff --git a/gcloud/dataplex/encryption-config/update b/gcloud/dataplex/encryption-config/update new file mode 100644 index 000000000..e32076322 --- /dev/null +++ b/gcloud/dataplex/encryption-config/update @@ -0,0 +1,71 @@ +NAME + gcloud dataplex encryption-config update - update an Encryption Config + +SYNOPSIS + gcloud dataplex encryption-config update + (ENCRYPTION_CONFIG : --location=LOCATION --organization=ORGANIZATION) + [--enable-metastore-encryption] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an Encryption Config. + +EXAMPLES + To update EncryptionConfig in organization 123 and location us-central1, + run: + + $ gcloud dataplex encryption-config update \ + organizations/123/locations/us-central1/encryptionConfigs/\ + default --enable-metastore-encryption + +POSITIONAL ARGUMENTS + Encryption config resource - Arguments and flags that define the Dataplex + EncryptionConfig you want to update. The arguments in this group can be + used to specify the attributes of this resource. + + This must be specified. + + ENCRYPTION_CONFIG + ID of the encryption config or fully qualified identifier for the + encryption config. + + To set the encryption_config attribute: + ▸ provide the argument encryption_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Dataplex resource. + + To set the location attribute: + ▸ provide the argument encryption_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + + --organization=ORGANIZATION + The name of encryption config to use. + + To set the organization attribute: + ▸ provide the argument encryption_config on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. + +FLAGS + --enable-metastore-encryption + Helps user to explicitly enable cmek encryption for dataplex metadata + storage. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha dataplex encryption-config update + diff --git a/gcloud/edge-cloud/container/clusters/create b/gcloud/edge-cloud/container/clusters/create index 5e2412b06..53c2c328c 100644 --- a/gcloud/edge-cloud/container/clusters/create +++ b/gcloud/edge-cloud/container/clusters/create @@ -155,7 +155,7 @@ FLAGS --maintenance-window-end=MAINTENANCE_WINDOW_END End time of the recurring cluster maintenance window in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE @@ -166,7 +166,7 @@ FLAGS --maintenance-window-start=MAINTENANCE_WINDOW_START Start time of the recurring cluster maintenance window in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" --offline-reboot-ttl=OFFLINE_REBOOT_TTL diff --git a/gcloud/edge-cloud/container/clusters/update b/gcloud/edge-cloud/container/clusters/update index 13aaed09e..c7359525d 100644 --- a/gcloud/edge-cloud/container/clusters/update +++ b/gcloud/edge-cloud/container/clusters/update @@ -100,7 +100,7 @@ FLAGS --add-maintenance-exclusion-end=ADD_MAINTENANCE_EXCLUSION_END End time of the maintenance exclusion window in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00". --add-maintenance-exclusion-name=ADD_MAINTENANCE_EXCLUSION_NAME @@ -109,7 +109,7 @@ FLAGS --add-maintenance-exclusion-start=ADD_MAINTENANCE_EXCLUSION_START Start time of the maintenance exclusion window (can occur in the - past) in the RFC 3339 (https://www.ietf.org/rfc/rfc3339.txt) + past) in the RFC 3339 (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00". Updates cluster maintenance window setting (more than one flags can be @@ -117,7 +117,7 @@ FLAGS --maintenance-window-end=MAINTENANCE_WINDOW_END End time of the recurring cluster maintenance window in the RFC - 3339 (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + 3339 (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE @@ -128,7 +128,7 @@ FLAGS --maintenance-window-start=MAINTENANCE_WINDOW_START Start time of the recurring cluster maintenance window in the RFC - 3339 (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + 3339 (https://www.rfc-editor.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" At most one of these can be specified: diff --git a/gcloud/lustre/instances/create b/gcloud/lustre/instances/create index 87109194e..12e56f76f 100644 --- a/gcloud/lustre/instances/create +++ b/gcloud/lustre/instances/create @@ -6,8 +6,13 @@ SYNOPSIS --capacity-gib=CAPACITY_GIB --filesystem=FILESYSTEM --network=NETWORK --per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT [--async] [--description=DESCRIPTION] [--gke-support-enabled] - [--labels=[LABELS,...]] [--request-id=REQUEST_ID] - [GCLOUD_WIDE_FLAG ...] + [--labels=[LABELS,...]] [--placement-policy=PLACEMENT_POLICY] + [--request-id=REQUEST_ID] + [[--default-squash-mode=DEFAULT_SQUASH_MODE + : --access-rules=[ipAddressRanges=IPADDRESSRANGES], + [name=NAME],[squashMode=SQUASHMODE] + --default-squash-gid=DEFAULT_SQUASH_GID + --default-squash-uid=DEFAULT_SQUASH_UID]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Creates a Managed Lustre instance. @@ -55,7 +60,11 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --capacity-gib=CAPACITY_GIB The storage capacity of the instance in gibibytes (GiB). Allowed values - are from 18000 to 954000, in increments of 9000. + are from 18000 to 7632000, depending on the perUnitStorageThroughput. + See Performance tiers and maximum storage capacities + (https://cloud.google.com/managed-lustre/docs/create-instance#performance-tiers) + for specific minimums, maximums, and step sizes for each performance + tier. --filesystem=FILESYSTEM The filesystem name for this instance. This name is used by client-side @@ -84,7 +93,9 @@ REQUIRED FLAGS --per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT The throughput of the instance in MB/s/TiB. Valid values are 125, 250, - 500, 1000. + 500, 1000. See Performance tiers and maximum storage capacities + (https://cloud.google.com/managed-lustre/docs/create-instance#performance-tiers) + for more information. OPTIONAL FLAGS --async @@ -122,6 +133,10 @@ OPTIONAL FLAGS --labels=path_to_file.(yaml|json) + --placement-policy=PLACEMENT_POLICY + The placement policy name for the instance in the format of + projects/{project}/locations/{location}/resourcePolicies/{resource_policy} + --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to @@ -137,6 +152,87 @@ OPTIONAL FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). + IP-based access rules for the Managed Lustre instance. These options + define the root user squash configuration. + + --default-squash-mode=DEFAULT_SQUASH_MODE + The squash mode for the default access rule. DEFAULT_SQUASH_MODE must + be one of: + + no-squash + Squash is disabled. + + If set inside an + [AccessRule][google.cloud.lustre.v1.AccessRulesOptions.AccessRule], + root users matching the [ip_ranges][AccessRule.ip_ranges] are not + squashed. + + If set as the + [default_squash_mode][google.cloud.lustre.v1.AccessRulesOptions.default_squash_mode], + root squash is disabled for this instance. + + If the default squash mode is NO_SQUASH, do not set the + [default_squash_uid][google.cloud.lustre.v1.AccessRulesOptions.default_squash_uid] + or + [default_squash_gid][google.cloud.lustre.v1.AccessRulesOptions.default_squash_gid], + or an invalid argument error is returned. + root-squash + Root user squash is enabled. + + Not supported inside an + [AccessRule][google.cloud.lustre.v1.AccessRulesOptions.AccessRule]. + + If set as the + [default_squash_mode][google.cloud.lustre.v1.AccessRulesOptions.default_squash_mode], + root users not matching any of the + [access_rules][google.cloud.lustre.v1.AccessRulesOptions.access_rules] + are squashed to the + [default_squash_uid][google.cloud.lustre.v1.AccessRulesOptions.default_squash_uid] + and + [default_squash_gid][google.cloud.lustre.v1.AccessRulesOptions.default_squash_gid]. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --access-rules=[ipAddressRanges=IPADDRESSRANGES],[name=NAME],[squashMode=SQUASHMODE] + The access rules for the instance. + + ipAddressRanges + The IP address ranges to which to apply this access rule. Accepts + non-overlapping CIDR ranges (e.g., 192.168.1.0/24) and IP + addresses (e.g., 192.168.1.0). + + name + The name of the access rule policy group. Must be 16 characters + or less and include only alphanumeric characters or ''. + + squashMode + Squash mode for the access rule. + + Shorthand Example: + + --access-rules=ipAddressRanges=[string],name=string,squashMode=string --access-rules=ipAddressRanges=[string],name=string,squashMode=string + + JSON Example: + + --access-rules='[{"ipAddressRanges": ["string"], "name": "string", "squashMode": "string"}]' + + File Example: + + --access-rules=path_to_file.(yaml|json) + + --default-squash-gid=DEFAULT_SQUASH_GID + The user squash GID for the default access rule. This user squash GID + applies to all root users connecting from clients that are not + matched by any of the access rules. If not set, the default is 0 (no + GID squash). + + --default-squash-uid=DEFAULT_SQUASH_UID + The user squash UID for the default access rule. This user squash UID + applies to all root users connecting from clients that are not + matched by any of the access rules. If not set, the default is 0 (no + UID squash). + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/lustre/instances/update b/gcloud/lustre/instances/update index 97c5457e4..7d50e4ff6 100644 --- a/gcloud/lustre/instances/update +++ b/gcloud/lustre/instances/update @@ -7,7 +7,16 @@ SYNOPSIS [--capacity-gib=CAPACITY_GIB] [--description=DESCRIPTION] [--[no-]gke-support-enabled] [--per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT] - [--request-id=REQUEST_ID] + [--placement-policy=PLACEMENT_POLICY] [--request-id=REQUEST_ID] + [--clear- --default-squash-gid=DEFAULT_SQUASH_GID + --default-squash-mode=DEFAULT_SQUASH_MODE + --default-squash-uid=DEFAULT_SQUASH_UID + --access-rules=[ipAddressRanges=IPADDRESSRANGES], + [name=NAME],[squashMode=SQUASHMODE] + | --add-access-rules=[ipAddressRanges=IPADDRESSRANGES], + [name=NAME],[squashMode=SQUASHMODE] --clear-access-rules + | --remove-access-rules=[ipAddressRanges=IPADDRESSRANGES], + [name=NAME],[squashMode=SQUASHMODE]] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] @@ -60,7 +69,11 @@ FLAGS --capacity-gib=CAPACITY_GIB The storage capacity of the instance in gibibytes (GiB). Allowed values - are from 18000 to 954000, in increments of 9000. + are from 18000 to 7632000, depending on the perUnitStorageThroughput. + See Performance tiers and maximum storage capacities + (https://cloud.google.com/managed-lustre/docs/create-instance#performance-tiers) + for specific minimums, maximums, and step sizes for each performance + tier. --description=DESCRIPTION A user-readable description of the instance. @@ -73,7 +86,13 @@ FLAGS --per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT The throughput of the instance in MB/s/TiB. Valid values are 125, 250, - 500, 1000. + 500, 1000. See Performance tiers and maximum storage capacities + (https://cloud.google.com/managed-lustre/docs/create-instance#performance-tiers) + for more information. + + --placement-policy=PLACEMENT_POLICY + The placement policy name for the instance in the format of + projects/{project}/locations/{location}/resourcePolicies/{resource_policy} --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request @@ -90,6 +109,153 @@ FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). + IP-based access rules for the Managed Lustre instance. These options + define the root user squash configuration. + + --clear- + Set instance.accessRulesOptions back to default value. + + --default-squash-gid=DEFAULT_SQUASH_GID + The user squash GID for the default access rule. This user squash GID + applies to all root users connecting from clients that are not + matched by any of the access rules. If not set, the default is 0 (no + GID squash). + + --default-squash-mode=DEFAULT_SQUASH_MODE + The squash mode for the default access rule. DEFAULT_SQUASH_MODE must + be one of: + + no-squash + Squash is disabled. + + If set inside an + [AccessRule][google.cloud.lustre.v1.AccessRulesOptions.AccessRule], + root users matching the [ip_ranges][AccessRule.ip_ranges] are not + squashed. + + If set as the + [default_squash_mode][google.cloud.lustre.v1.AccessRulesOptions.default_squash_mode], + root squash is disabled for this instance. + + If the default squash mode is NO_SQUASH, do not set the + [default_squash_uid][google.cloud.lustre.v1.AccessRulesOptions.default_squash_uid] + or + [default_squash_gid][google.cloud.lustre.v1.AccessRulesOptions.default_squash_gid], + or an invalid argument error is returned. + root-squash + Root user squash is enabled. + + Not supported inside an + [AccessRule][google.cloud.lustre.v1.AccessRulesOptions.AccessRule]. + + If set as the + [default_squash_mode][google.cloud.lustre.v1.AccessRulesOptions.default_squash_mode], + root users not matching any of the + [access_rules][google.cloud.lustre.v1.AccessRulesOptions.access_rules] + are squashed to the + [default_squash_uid][google.cloud.lustre.v1.AccessRulesOptions.default_squash_uid] + and + [default_squash_gid][google.cloud.lustre.v1.AccessRulesOptions.default_squash_gid]. + + --default-squash-uid=DEFAULT_SQUASH_UID + The user squash UID for the default access rule. This user squash UID + applies to all root users connecting from clients that are not + matched by any of the access rules. If not set, the default is 0 (no + UID squash). + + Update access_rules. + + At most one of these can be specified: + + --access-rules=[ipAddressRanges=IPADDRESSRANGES],[name=NAME],[squashMode=SQUASHMODE] + Set access_rules to new value. The access rules for the instance. + + ipAddressRanges + The IP address ranges to which to apply this access rule. + Accepts non-overlapping CIDR ranges (e.g., 192.168.1.0/24) and + IP addresses (e.g., 192.168.1.0). + + name + The name of the access rule policy group. Must be 16 characters + or less and include only alphanumeric characters or ''. + + squashMode + Squash mode for the access rule. + + Shorthand Example: + + --access-rules=ipAddressRanges=[string],name=string,squashMode=string --access-rules=ipAddressRanges=[string],name=string,squashMode=string + + JSON Example: + + --access-rules='[{"ipAddressRanges": ["string"], "name": "string", "squashMode": "string"}]' + + File Example: + + --access-rules=path_to_file.(yaml|json) + + --add-access-rules=[ipAddressRanges=IPADDRESSRANGES],[name=NAME],[squashMode=SQUASHMODE] + Add new value to access_rules list. The access rules for the + instance. + + ipAddressRanges + The IP address ranges to which to apply this access rule. + Accepts non-overlapping CIDR ranges (e.g., 192.168.1.0/24) and + IP addresses (e.g., 192.168.1.0). + + name + The name of the access rule policy group. Must be 16 characters + or less and include only alphanumeric characters or ''. + + squashMode + Squash mode for the access rule. + + Shorthand Example: + + --add-access-rules=ipAddressRanges=[string],name=string,squashMode=string --add-access-rules=ipAddressRanges=[string],name=string,squashMode=string + + JSON Example: + + --add-access-rules='[{"ipAddressRanges": ["string"], "name": "string", "squashMode": "string"}]' + + File Example: + + --add-access-rules=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-access-rules + Clear access_rules value and set to empty list. + + --remove-access-rules=[ipAddressRanges=IPADDRESSRANGES],[name=NAME],[squashMode=SQUASHMODE] + Remove existing value from access_rules list. The access rules + for the instance. + + ipAddressRanges + The IP address ranges to which to apply this access rule. + Accepts non-overlapping CIDR ranges (e.g., 192.168.1.0/24) + and IP addresses (e.g., 192.168.1.0). + + name + The name of the access rule policy group. Must be 16 + characters or less and include only alphanumeric characters + or ''. + + squashMode + Squash mode for the access rule. + + Shorthand Example: + + --remove-access-rules=ipAddressRanges=[string],name=string,squashMode=string --remove-access-rules=ipAddressRanges=[string],name=string,squashMode=string + + JSON Example: + + --remove-access-rules='[{"ipAddressRanges": ["string"], "name": "string", "squashMode": "string"}]' + + File Example: + + --remove-access-rules=path_to_file.(yaml|json) + Update labels. At most one of these can be specified: diff --git a/gcloud/oracle-database/autonomous-databases/create b/gcloud/oracle-database/autonomous-databases/create index 4d8fc7e13..54754b81d 100644 --- a/gcloud/oracle-database/autonomous-databases/create +++ b/gcloud/oracle-database/autonomous-databases/create @@ -12,7 +12,7 @@ SYNOPSIS [[--properties-db-workload=PROPERTIES_DB_WORKLOAD --properties-license-type=PROPERTIES_LICENSE_TYPE : --properties-allowlisted-ips=[PROPERTIES_ALLOWLISTED_IPS,...] - --properties-backup-retention-period-days=PROPERTIES_BACKUP_RETENTION_PERIOD_DAYS --properties-character-set=PROPERTIES_CHARACTER_SET --properties-compute-count=PROPERTIES_COMPUTE_COUNT --properties-cpu-core-count=PROPERTIES_CPU_CORE_COUNT --properties-customer-contacts=[email=EMAIL] --properties-data-storage-size-gb=PROPERTIES_DATA_STORAGE_SIZE_GB --properties-data-storage-size-tb=PROPERTIES_DATA_STORAGE_SIZE_TB --properties-db-edition=PROPERTIES_DB_EDITION --properties-db-version=PROPERTIES_DB_VERSION --properties-is-auto-scaling-enabled --properties-is-storage-auto-scaling-enabled --properties-maintenance-schedule-type=PROPERTIES_MAINTENANCE_SCHEDULE_TYPE --properties-mtls-connection-required --properties-n-character-set=PROPERTIES_N_CHARACTER_SET --properties-private-endpoint-ip=PROPERTIES_PRIVATE_ENDPOINT_IP --properties-private-endpoint-label=PROPERTIES_PRIVATE_ENDPOINT_LABEL --properties-secret-id=PROPERTIES_SECRET_ID --properties-vault-id=PROPERTIES_VAULT_ID]] + --properties-backup-retention-period-days=PROPERTIES_BACKUP_RETENTION_PERIOD_DAYS --properties-character-set=PROPERTIES_CHARACTER_SET --properties-compute-count=PROPERTIES_COMPUTE_COUNT --properties-cpu-core-count=PROPERTIES_CPU_CORE_COUNT --properties-customer-contacts=[email=EMAIL] --properties-data-storage-size-gb=PROPERTIES_DATA_STORAGE_SIZE_GB --properties-data-storage-size-tb=PROPERTIES_DATA_STORAGE_SIZE_TB --properties-db-edition=PROPERTIES_DB_EDITION --properties-db-version=PROPERTIES_DB_VERSION --properties-is-auto-scaling-enabled --properties-is-storage-auto-scaling-enabled --properties-maintenance-schedule-type=PROPERTIES_MAINTENANCE_SCHEDULE_TYPE --properties-mtls-connection-required --properties-n-character-set=PROPERTIES_N_CHARACTER_SET --properties-private-endpoint-ip=PROPERTIES_PRIVATE_ENDPOINT_IP --properties-private-endpoint-label=PROPERTIES_PRIVATE_ENDPOINT_LABEL --properties-secret-id=PROPERTIES_SECRET_ID --properties-vault-id=PROPERTIES_VAULT_ID --encryption-key-kms=ENCRYPTION_KEY_KMS --encryption-key-provider=ENCRYPTION_KEY_PROVIDER]] [--source-config-automatic-backups-replication-enabled --source-config-autonomous-database=SOURCE_CONFIG_AUTONOMOUS_DATABASE] [GCLOUD_WIDE_FLAG ...] @@ -319,6 +319,24 @@ FLAGS --properties-vault-id=PROPERTIES_VAULT_ID The ID of the Oracle Cloud Infrastructure vault. + The encryption key used to encrypt the Autonomous Database. + + --encryption-key-kms=ENCRYPTION_KEY_KMS + The KMS key used to encrypt the Autonomous Database. This field is + required if the provider is GOOGLE_MANAGED. The name of the KMS key + resource in the following format: + projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}. + + --encryption-key-provider=ENCRYPTION_KEY_PROVIDER + The provider of the encryption key. ENCRYPTION_KEY_PROVIDER must be + one of: + + google-managed + Google Managed KMS key, if selected, please provide the KMS key + name. + oracle-managed + Oracle Managed. + The source configuration for the standby Autonomous Database. --source-config-automatic-backups-replication-enabled diff --git a/gcloud/oracle-database/autonomous-databases/help b/gcloud/oracle-database/autonomous-databases/help index f3d30cfa2..115a576a2 100644 --- a/gcloud/oracle-database/autonomous-databases/help +++ b/gcloud/oracle-database/autonomous-databases/help @@ -48,3 +48,6 @@ COMMANDS switchover Switchovers an AutonomousDatabase to a new primary. + + update + Update autonomousDatabases. diff --git a/gcloud/oracle-database/autonomous-databases/update b/gcloud/oracle-database/autonomous-databases/update new file mode 100644 index 000000000..785acd5b1 --- /dev/null +++ b/gcloud/oracle-database/autonomous-databases/update @@ -0,0 +1,512 @@ +NAME + gcloud oracle-database autonomous-databases update - update + autonomousDatabases + +SYNOPSIS + gcloud oracle-database autonomous-databases update AUTONOMOUS_DATABASE + [--admin-password=ADMIN_PASSWORD] [--async] [--cidr=CIDR] + [--clear-odb-network] [--database=DATABASE] + [--display-name=DISPLAY_NAME] [--location=LOCATION] + [--odb-network=ODB_NETWORK] [--request-id=REQUEST_ID] + [--clear-network | --network=NETWORK] + [--clear-odb-subnet | --odb-subnet=ODB_SUBNET] + [--clear-properties + --properties-backup-retention-period-days=PROPERTIES_BACKUP_RETENTION_PERIOD_DAYS --properties-character-set=PROPERTIES_CHARACTER_SET --properties-compute-count=PROPERTIES_COMPUTE_COUNT --properties-cpu-core-count=PROPERTIES_CPU_CORE_COUNT --properties-data-storage-size-gb=PROPERTIES_DATA_STORAGE_SIZE_GB --properties-data-storage-size-tb=PROPERTIES_DATA_STORAGE_SIZE_TB --properties-db-edition=PROPERTIES_DB_EDITION --properties-db-version=PROPERTIES_DB_VERSION --properties-db-workload=PROPERTIES_DB_WORKLOAD --[no-]properties-is-auto-scaling-enabled --[no-]properties-is-storage-auto-scaling-enabled --properties-license-type=PROPERTIES_LICENSE_TYPE --properties-maintenance-schedule-type=PROPERTIES_MAINTENANCE_SCHEDULE_TYPE --[no-]properties-mtls-connection-required --properties-n-character-set=PROPERTIES_N_CHARACTER_SET --properties-private-endpoint-ip=PROPERTIES_PRIVATE_ENDPOINT_IP --properties-private-endpoint-label=PROPERTIES_PRIVATE_ENDPOINT_LABEL --properties-secret-id=PROPERTIES_SECRET_ID --properties-vault-id=PROPERTIES_VAULT_ID --encryption-key-kms=ENCRYPTION_KEY_KMS --encryption-key-provider=ENCRYPTION_KEY_PROVIDER --properties-allowlisted-ips=[PROPERTIES_ALLOWLISTED_IPS, + ...] + | --add-properties-allowlisted-ips=[ADD_PROPERTIES_ALLOWLISTED_IPS, + ...] --clear-properties-allowlisted-ips + | --remove-properties-allowlisted-ips=[REMOVE_PROPERTIES_ALLOWLISTED_IPS, + ...] --properties-customer-contacts=[email=EMAIL] + | --add-properties-customer-contacts=[email=EMAIL] + --clear-properties-customer-contacts + | --remove-properties-customer-contacts=[email=EMAIL]] + [--clear-source-config + --[no-]source-config-automatic-backups-replication-enabled + --clear-source-config-autonomous-database + | --source-config-autonomous-database=SOURCE_CONFIG_AUTONOMOUS_DATABASE] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an autonomousDatabase + +EXAMPLES + To update the autonomousDatabase, run: + + $ gcloud oracle-database autonomous-databases update + +POSITIONAL ARGUMENTS + AutonomousDatabase resource - Identifier. The name of the Autonomous + Database resource in the following format: + projects/{project}/locations/{region}/autonomousDatabases/{autonomous_database} + 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 autonomous_database 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 autonomous_database on the command line with a + fully specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + AUTONOMOUS_DATABASE + ID of the autonomousDatabase or fully qualified identifier for the + autonomousDatabase. + + To set the autonomous_database attribute: + ▸ provide the argument autonomous_database on the command line. + +FLAGS + --admin-password=ADMIN_PASSWORD + The password for the default ADMIN user. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --cidr=CIDR + The subnet CIDR range for the Autonomous Database. + + Update odb_network. + + --clear-odb-network + Clear odb_network value and set to null. + + --database=DATABASE + The name of the Autonomous Database. The database name must be unique + in the project. The name must begin with a letter and can contain a + maximum of 30 alphanumeric characters. + + --display-name=DISPLAY_NAME + The display name for the Autonomous Database. The name does not have to + be unique within your project. + + --location=LOCATION + For resources [autonomous_database, odb-network, odb-subnet, + source-config-autonomous-database], provides fallback value for + resource location attribute. When the resource's full URI path is not + provided, location will fallback to this flag value. + + --odb-network=ODB_NETWORK + For resources [odb-network, odb-subnet], provides fallback value for + resource odb-network attribute. When the resource's full URI path is + not provided, odb-network will fallback to this flag value. + + --request-id=REQUEST_ID + An optional ID to identify the request. This value is used to identify + duplicate requests. If you make a request with the same request ID and + the original request is still in progress or completed, the server + ignores the second request. This prevents clients from accidentally + creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + Update network. + + At most one of these can be specified: + + --clear-network + Clear network value and set to null. + + Network resource - Set network to new value. + + The name of the VPC network used by the Autonomous Database in the + following format: projects/{project}/global/networks/{network} 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 --network on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --network=NETWORK + ID of the network or fully qualified identifier for the network. + + To set the network attribute: + ▫ provide the argument --network on the command line. + + Update odb_subnet. + + At most one of these can be specified: + + --clear-odb-subnet + Clear odb_subnet value and set to null. + + OdbSubnet resource - Set odb_subnet to new value. + + The name of the OdbSubnet associated with the Autonomous Database. + Format: + projects/{project}/locations/{location}/odbNetworks/{odb_network}/odbSubnets/{odb_subnet} + 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 --odb-subnet 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 --odb-subnet on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + To set the odb-network attribute: + ▸ provide the argument --odb-subnet on the command line with a fully + specified name; + ▸ provide the argument --odb-network on the command line. + + --odb-subnet=ODB_SUBNET + ID of the odbSubnet or fully qualified identifier for the + odbSubnet. + + To set the odb-subnet attribute: + ▫ provide the argument --odb-subnet on the command line. + + The properties of an Autonomous Database. + + --clear-properties + Set autonomousDatabase.properties back to default value. + + --properties-backup-retention-period-days=PROPERTIES_BACKUP_RETENTION_PERIOD_DAYS + The retention period for the Autonomous Database. This field is + specified in days, can range from 1 day to 60 days, and has a default + value of 60 days. + + --properties-character-set=PROPERTIES_CHARACTER_SET + The character set for the Autonomous Database. The default is + AL32UTF8. + + --properties-compute-count=PROPERTIES_COMPUTE_COUNT + The number of compute servers for the Autonomous Database. + + --properties-cpu-core-count=PROPERTIES_CPU_CORE_COUNT + The number of CPU cores to be made available to the database. + + --properties-data-storage-size-gb=PROPERTIES_DATA_STORAGE_SIZE_GB + The size of the data stored in the database, in gigabytes. + + --properties-data-storage-size-tb=PROPERTIES_DATA_STORAGE_SIZE_TB + The size of the data stored in the database, in terabytes. + + --properties-db-edition=PROPERTIES_DB_EDITION + The edition of the Autonomous Databases. PROPERTIES_DB_EDITION must + be one of: + + enterprise-edition + Enterprise Database Edition + standard-edition + Standard Database Edition + + --properties-db-version=PROPERTIES_DB_VERSION + The Oracle Database version for the Autonomous Database. + + --properties-db-workload=PROPERTIES_DB_WORKLOAD + The workload type of the Autonomous Database. PROPERTIES_DB_WORKLOAD + must be one of: + + ajd + Autonomous JSON Database. + apex + Autonomous Database with the Oracle APEX Application Development + workload type. + dw + Autonomous Data Warehouse database. + oltp + Autonomous Transaction Processing database. + + --[no-]properties-is-auto-scaling-enabled + This field indicates if auto scaling is enabled for the Autonomous + Database CPU core count. Use --properties-is-auto-scaling-enabled to + enable and --no-properties-is-auto-scaling-enabled to disable. + + --[no-]properties-is-storage-auto-scaling-enabled + This field indicates if auto scaling is enabled for the Autonomous + Database storage. Use --properties-is-storage-auto-scaling-enabled to + enable and --no-properties-is-storage-auto-scaling-enabled to + disable. + + --properties-license-type=PROPERTIES_LICENSE_TYPE + The license type used for the Autonomous Database. + PROPERTIES_LICENSE_TYPE must be one of: + + bring-your-own-license + Bring your own license + license-included + License included part of offer + + --properties-maintenance-schedule-type=PROPERTIES_MAINTENANCE_SCHEDULE_TYPE + The maintenance schedule of the Autonomous Database. + PROPERTIES_MAINTENANCE_SCHEDULE_TYPE must be one of: + + early + An EARLY maintenance schedule patches the database before the + regular scheduled maintenance. + regular + A REGULAR maintenance schedule follows the normal maintenance + cycle. + + --[no-]properties-mtls-connection-required + This field specifies if the Autonomous Database requires mTLS + connections. Use --properties-mtls-connection-required to enable and + --no-properties-mtls-connection-required to disable. + + --properties-n-character-set=PROPERTIES_N_CHARACTER_SET + The national character set for the Autonomous Database. The default + is AL16UTF16. + + --properties-private-endpoint-ip=PROPERTIES_PRIVATE_ENDPOINT_IP + The private endpoint IP address for the Autonomous Database. + + --properties-private-endpoint-label=PROPERTIES_PRIVATE_ENDPOINT_LABEL + The private endpoint label for the Autonomous Database. + + --properties-secret-id=PROPERTIES_SECRET_ID + The ID of the Oracle Cloud Infrastructure vault secret. + + --properties-vault-id=PROPERTIES_VAULT_ID + The ID of the Oracle Cloud Infrastructure vault. + + The encryption key used to encrypt the Autonomous Database. + + --encryption-key-kms=ENCRYPTION_KEY_KMS + The KMS key used to encrypt the Autonomous Database. This field is + required if the provider is GOOGLE_MANAGED. The name of the KMS key + resource in the following format: + projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}. + + --encryption-key-provider=ENCRYPTION_KEY_PROVIDER + The provider of the encryption key. ENCRYPTION_KEY_PROVIDER must be + one of: + + google-managed + Google Managed KMS key, if selected, please provide the KMS key + name. + oracle-managed + Oracle Managed. + + Update properties_allowlisted_ips. + + At most one of these can be specified: + + --properties-allowlisted-ips=[PROPERTIES_ALLOWLISTED_IPS,...] + Set properties_allowlisted_ips to new value. + + --add-properties-allowlisted-ips=[ADD_PROPERTIES_ALLOWLISTED_IPS,...] + Add new value to properties_allowlisted_ips list. + + At most one of these can be specified: + + --clear-properties-allowlisted-ips + Clear properties_allowlisted_ips value and set to empty list. + + --remove-properties-allowlisted-ips=[REMOVE_PROPERTIES_ALLOWLISTED_IPS,...] + Remove existing value from properties_allowlisted_ips list. + + Update properties_customer_contacts. + + At most one of these can be specified: + + --properties-customer-contacts=[email=EMAIL] + Set properties_customer_contacts to new value. The list of customer + contacts. + + email + The email address used by Oracle to send notifications + regarding databases and infrastructure. + + Shorthand Example: + + --properties-customer-contacts=email=string --properties-customer-contacts=email=string + + JSON Example: + + --properties-customer-contacts='[{"email": "string"}]' + + File Example: + + --properties-customer-contacts=path_to_file.(yaml|json) + + --add-properties-customer-contacts=[email=EMAIL] + Add new value to properties_customer_contacts list. The list of + customer contacts. + + email + The email address used by Oracle to send notifications + regarding databases and infrastructure. + + Shorthand Example: + + --add-properties-customer-contacts=email=string --add-properties-customer-contacts=email=string + + JSON Example: + + --add-properties-customer-contacts='[{"email": "string"}]' + + File Example: + + --add-properties-customer-contacts=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-properties-customer-contacts + Clear properties_customer_contacts value and set to empty list. + + --remove-properties-customer-contacts=[email=EMAIL] + Remove existing value from properties_customer_contacts list. The + list of customer contacts. + + email + The email address used by Oracle to send notifications + regarding databases and infrastructure. + + Shorthand Example: + + --remove-properties-customer-contacts=email=string --remove-properties-customer-contacts=email=string + + JSON Example: + + --remove-properties-customer-contacts='[{"email": "string"}]' + + File Example: + + --remove-properties-customer-contacts=path_to_file.(yaml|json) + + The source configuration for the standby Autonomous Database. + + --clear-source-config + Set autonomousDatabase.sourceConfig back to default value. + + --[no-]source-config-automatic-backups-replication-enabled + This field specifies if the replication of automatic backups is + enabled when creating a Data Guard. Use + --source-config-automatic-backups-replication-enabled to enable and + --no-source-config-automatic-backups-replication-enabled to disable. + + Update source_config_autonomous_database. + + At most one of these can be specified: + + --clear-source-config-autonomous-database + Clear source_config_autonomous_database value and set to null. + + AutonomousDatabase resource - Set source_config_autonomous_database to + new value. + + The name of the primary Autonomous Database that is used to create a + Peer Autonomous Database from a source. 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-config-autonomous-database 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-config-autonomous-database on the + command line with a fully specified name; + ▫ provide the argument --location on the command line. + + --source-config-autonomous-database=SOURCE_CONFIG_AUTONOMOUS_DATABASE + ID of the autonomousDatabase or fully qualified identifier for + the autonomousDatabase. + + To set the autonomous-database attribute: + ◇ provide the argument --source-config-autonomous-database on + the command line. + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. The labels or tags associated with the + Autonomous Database. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. The labels or tags + associated with the Autonomous Database. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/recommender/insights/describe b/gcloud/recommender/insights/describe index 15f99622f..a107d86a6 100644 --- a/gcloud/recommender/insights/describe +++ b/gcloud/recommender/insights/describe @@ -15,8 +15,9 @@ DESCRIPTION EXAMPLES To describe an insight: - $ gcloud recommender insights describe INSIGHT_ID \ - --project=${PROJECT} --location=${LOCATION} + $ gcloud recommender insights describe \ + --insight-type=${INSIGHT_TYPE} --project=${PROJECT} \ + --location=${LOCATION} POSITIONAL ARGUMENTS INSIGHT diff --git a/gcloud/run/deploy b/gcloud/run/deploy index 616cfb42c..44dd1416c 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -7,7 +7,7 @@ SYNOPSIS [--breakglass=JUSTIFICATION] [--clear-vpc-connector] [--concurrency=CONCURRENCY] [--container=CONTAINER] [--[no-]cpu-boost] [--[no-]cpu-throttling] [--[no-]default-url] - [--description=DESCRIPTION] + [--[no-]deploy-health-check] [--description=DESCRIPTION] [--execution-environment=EXECUTION_ENVIRONMENT] [--gpu-type=GPU_TYPE] [--[no-]gpu-zonal-redundancy] [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] [--max=MAX] [--max-instances=MAX_INSTANCES] @@ -164,6 +164,14 @@ FLAGS if not specified. Use --default-url to enable and --no-default-url to disable. + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + --description=DESCRIPTION Provides an optional, human-readable description of the service. diff --git a/gcloud/run/multi-region-services/update b/gcloud/run/multi-region-services/update index 1d8cdfa56..ad50e29c2 100644 --- a/gcloud/run/multi-region-services/update +++ b/gcloud/run/multi-region-services/update @@ -8,6 +8,7 @@ SYNOPSIS [--async] [--breakglass=JUSTIFICATION] [--clear-vpc-connector] [--concurrency=CONCURRENCY] [--container=CONTAINER] [--[no-]cpu-boost] [--[no-]cpu-throttling] [--[no-]default-url] + [--[no-]deploy-health-check] [--execution-environment=EXECUTION_ENVIRONMENT] [--gpu-type=GPU_TYPE] [--[no-]gpu-zonal-redundancy] [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] [--max=MAX] [--max-instances=MAX_INSTANCES] @@ -131,6 +132,14 @@ FLAGS if not specified. Use --default-url to enable and --no-default-url to disable. + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + --execution-environment=EXECUTION_ENVIRONMENT Selects the execution environment where the application will run. EXECUTION_ENVIRONMENT must be one of: diff --git a/gcloud/run/services/update b/gcloud/run/services/update index 11ef7efc1..7504e98b9 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -7,6 +7,7 @@ SYNOPSIS [--breakglass=JUSTIFICATION] [--clear-vpc-connector] [--concurrency=CONCURRENCY] [--container=CONTAINER] [--[no-]cpu-boost] [--[no-]cpu-throttling] [--[no-]default-url] + [--[no-]deploy-health-check] [--execution-environment=EXECUTION_ENVIRONMENT] [--gpu-type=GPU_TYPE] [--[no-]gpu-zonal-redundancy] [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] [--max=MAX] [--max-instances=MAX_INSTANCES] @@ -129,6 +130,14 @@ FLAGS if not specified. Use --default-url to enable and --no-default-url to disable. + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + --execution-environment=EXECUTION_ENVIRONMENT Selects the execution environment where the application will run. EXECUTION_ENVIRONMENT must be one of: diff --git a/gcloud/sql/flags/list b/gcloud/sql/flags/list index 6795059cd..05eeb5e7a 100644 --- a/gcloud/sql/flags/list +++ b/gcloud/sql/flags/list @@ -20,8 +20,8 @@ FLAGS supported minor versions. DATABASE_VERSION must be one of: MYSQL_5_6, MYSQL_5_7, MYSQL_8_0, MYSQL_8_4, POSTGRES_9_6, POSTGRES_10, POSTGRES_11, POSTGRES_12, POSTGRES_13, POSTGRES_14, POSTGRES_15, - POSTGRES_16, POSTGRES_17, SQLSERVER_2017_EXPRESS, SQLSERVER_2017_WEB, - SQLSERVER_2017_STANDARD, SQLSERVER_2017_ENTERPRISE, + POSTGRES_16, POSTGRES_17, POSTGRES_18, SQLSERVER_2017_EXPRESS, + SQLSERVER_2017_WEB, SQLSERVER_2017_STANDARD, SQLSERVER_2017_ENTERPRISE, SQLSERVER_2019_EXPRESS, SQLSERVER_2019_WEB, SQLSERVER_2019_STANDARD, SQLSERVER_2019_ENTERPRISE, SQLSERVER_2022_EXPRESS, SQLSERVER_2022_WEB, SQLSERVER_2022_STANDARD, SQLSERVER_2022_ENTERPRISE. diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index 3cb3679f4..74b0f87a1 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -234,8 +234,8 @@ FLAGS supported minor versions. DATABASE_VERSION must be one of: MYSQL_5_6, MYSQL_5_7, MYSQL_8_0, MYSQL_8_4, POSTGRES_9_6, POSTGRES_10, POSTGRES_11, POSTGRES_12, POSTGRES_13, POSTGRES_14, POSTGRES_15, - POSTGRES_16, POSTGRES_17, SQLSERVER_2017_EXPRESS, SQLSERVER_2017_WEB, - SQLSERVER_2017_STANDARD, SQLSERVER_2017_ENTERPRISE, + POSTGRES_16, POSTGRES_17, POSTGRES_18, SQLSERVER_2017_EXPRESS, + SQLSERVER_2017_WEB, SQLSERVER_2017_STANDARD, SQLSERVER_2017_ENTERPRISE, SQLSERVER_2019_EXPRESS, SQLSERVER_2019_WEB, SQLSERVER_2019_STANDARD, SQLSERVER_2019_ENTERPRISE, SQLSERVER_2022_EXPRESS, SQLSERVER_2022_WEB, SQLSERVER_2022_STANDARD, SQLSERVER_2022_ENTERPRISE. diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index 90f81001d..495e3e1eb 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -48,6 +48,7 @@ SYNOPSIS [--[no-]recreate-replicas-on-primary-crash] [--remove-deny-maintenance-period] [--replication=REPLICATION] [--[no-]require-ssl] [--[no-]retain-backups-on-delete] + [--server-ca-mode=SERVER_CA_MODE] [--server-ca-pool=SERVER_CA_POOL] [--simulate-maintenance-event] [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] @@ -169,8 +170,8 @@ FLAGS supported minor versions. DATABASE_VERSION must be one of: MYSQL_5_6, MYSQL_5_7, MYSQL_8_0, MYSQL_8_4, POSTGRES_9_6, POSTGRES_10, POSTGRES_11, POSTGRES_12, POSTGRES_13, POSTGRES_14, POSTGRES_15, - POSTGRES_16, POSTGRES_17, SQLSERVER_2017_EXPRESS, SQLSERVER_2017_WEB, - SQLSERVER_2017_STANDARD, SQLSERVER_2017_ENTERPRISE, + POSTGRES_16, POSTGRES_17, POSTGRES_18, SQLSERVER_2017_EXPRESS, + SQLSERVER_2017_WEB, SQLSERVER_2017_STANDARD, SQLSERVER_2017_ENTERPRISE, SQLSERVER_2019_EXPRESS, SQLSERVER_2019_WEB, SQLSERVER_2019_STANDARD, SQLSERVER_2019_ENTERPRISE, SQLSERVER_2022_EXPRESS, SQLSERVER_2022_WEB, SQLSERVER_2022_STANDARD, SQLSERVER_2022_ENTERPRISE. @@ -433,6 +434,21 @@ FLAGS deleted. Use --retain-backups-on-delete to enable and --no-retain-backups-on-delete to disable. + --server-ca-mode=SERVER_CA_MODE + Set the server CA mode of the instance. SERVER_CA_MODE must be one of: + + CUSTOMER_MANAGED_CAS_CA + Customer-managed CA hosted on Google Cloud's Certificate Authority + Service (CAS). + GOOGLE_MANAGED_CAS_CA + Google-managed regional CA part of root CA hierarchy hosted on + Google Cloud's Certificate Authority Service (CAS). + GOOGLE_MANAGED_INTERNAL_CA + Google-managed self-signed internal CA. + + --server-ca-pool=SERVER_CA_POOL + Set the server CA pool of the instance. + --simulate-maintenance-event Simulate a maintenance event without changing the version. Only applicable to instances that support near-zero downtime planned diff --git a/gcloud/sql/instances/reset-ssl-config b/gcloud/sql/instances/reset-ssl-config index 29a3e1e4b..4d06180a2 100644 --- a/gcloud/sql/instances/reset-ssl-config +++ b/gcloud/sql/instances/reset-ssl-config @@ -3,7 +3,7 @@ NAME the reset SSL mode SYNOPSIS - gcloud sql instances reset-ssl-config INSTANCE [--async] + gcloud sql instances reset-ssl-config INSTANCE [--async] [--mode=MODE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -18,6 +18,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --mode=MODE + Selectively refresh the SSL materials. MODE must be one of: + + ALL + Refresh all TLS configs. This is the default behaviour. + SYNC_FROM_PRIMARY + Refreshes the replication-related TLS configuration settings + provided by the primary instance. Not applicable to on-premises + replication instances. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/transfer/jobs/create b/gcloud/transfer/jobs/create index dffd6ec45..d02f99c08 100644 --- a/gcloud/transfer/jobs/create +++ b/gcloud/transfer/jobs/create @@ -8,7 +8,7 @@ SYNOPSIS --source-agent-pool=SOURCE_AGENT_POOL --destination-agent-pool=DESTINATION_AGENT_POOL --intermediate-storage-path=INTERMEDIATE_STORAGE_PATH - --manifest-file=MANIFEST_FILE] + --manifest-file=MANIFEST_FILE] [--replication] [--event-stream-name=EVENT_STREAM_NAME --event-stream-starts=EVENT_STREAM_STARTS --event-stream-expires=EVENT_STREAM_EXPIRES] @@ -171,6 +171,14 @@ FLAGS destination://path/to/manifest.csv). For manifest file formatting, see https://cloud.google.com/storage-transfer/docs/manifest. + REPLICATION OPTIONS + + --replication + Enable replication to automatically copy all new and existing objects + from the source to the destination. Note: Objects deleted from the + source bucket will not be deleted from the destination bucket. Please + note that it is an event-driven transfer. + EVENT STREAM Configure an event stream to transfer data whenever it is added or changed diff --git a/gcloud/transfer/jobs/list b/gcloud/transfer/jobs/list index 140aba1f2..b6135c2b8 100644 --- a/gcloud/transfer/jobs/list +++ b/gcloud/transfer/jobs/list @@ -5,7 +5,7 @@ SYNOPSIS gcloud transfer jobs list [--limit=LIMIT] [--page-size=PAGE_SIZE; default=256] [--job-names=[JOB_NAMES,...]] [--job-statuses=[JOB_STATUSES,...]] [--expand-table] - [GCLOUD_WIDE_FLAG ...] + [--job-type=JOB_TYPE; default="transfer"] [GCLOUD_WIDE_FLAG ...] DESCRIPTION List Transfer Service transfer jobs in a given project to show their @@ -55,6 +55,10 @@ FLAGS frequency, lastest operation name, job status) in command output. Tip: increase the size of your terminal before running the command. + --job-type=JOB_TYPE; default="transfer" + The type of the job you want to list. JOB_TYPE must be one of: + transfer, replication. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format,