diff --git a/gcloud/_version b/gcloud/_version index efb50789e..6bec861e4 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 445.0.0 -alpha 2023.09.01 -beta 2023.09.01 -bq 2.0.97 +Google Cloud SDK 446.0.0 +alpha 2023.09.08 +beta 2023.09.08 +bq 2.0.98 bundled-python3-unix 3.9.16 -core 2023.09.01 +core 2023.09.08 gcloud-crc32c 1.0.0 gsutil 5.25 diff --git a/gcloud/alloydb/clusters/restore b/gcloud/alloydb/clusters/restore index 4e0b195f0..792749c1f 100644 --- a/gcloud/alloydb/clusters/restore +++ b/gcloud/alloydb/clusters/restore @@ -42,7 +42,12 @@ REQUIRED FLAGS Exactly one of these must be specified: --backup=BACKUP - AlloyDB backup ID + The AlloyDB backup to restore from. This must either be the full + backup name + (projects/myProject/locations/us-central1/backups/myBackup) or the + backup ID (myBackup). In the second case, the project and location + are assumed to be the same as the restored cluster that is being + created. Restore a cluster from a source cluster at a given point in time. @@ -54,7 +59,12 @@ REQUIRED FLAGS in this group are specified. --source-cluster=SOURCE_CLUSTER - Source cluster name. + The AlloyDB source cluster to restore from. This must either be the + full cluster name + (projects/myProject/locations/us-central1/backups/myCluster) or the + cluster ID (myCluster). In the second case, the project and + location are assumed to be the same as the restored cluster that is + being created. This flag argument must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/alpha/alloydb/clusters/restore b/gcloud/alpha/alloydb/clusters/restore index 5f1e1f9cf..0dcb6903e 100644 --- a/gcloud/alpha/alloydb/clusters/restore +++ b/gcloud/alpha/alloydb/clusters/restore @@ -42,7 +42,12 @@ REQUIRED FLAGS Exactly one of these must be specified: --backup=BACKUP - AlloyDB backup ID + The AlloyDB backup to restore from. This must either be the full + backup name + (projects/myProject/locations/us-central1/backups/myBackup) or the + backup ID (myBackup). In the second case, the project and location + are assumed to be the same as the restored cluster that is being + created. Restore a cluster from a source cluster at a given point in time. @@ -54,7 +59,12 @@ REQUIRED FLAGS in this group are specified. --source-cluster=SOURCE_CLUSTER - Source cluster name. + The AlloyDB source cluster to restore from. This must either be the + full cluster name + (projects/myProject/locations/us-central1/backups/myCluster) or the + cluster ID (myCluster). In the second case, the project and + location are assumed to be the same as the restored cluster that is + being created. This flag argument must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/alpha/billing/budgets/create b/gcloud/alpha/billing/budgets/create index 4046874ba..93c553426 100644 --- a/gcloud/alpha/billing/budgets/create +++ b/gcloud/alpha/billing/budgets/create @@ -12,6 +12,7 @@ SYNOPSIS [--filter-credit-types=[FILTER_CREDIT_TYPES,...]] [--filter-labels=[KEY=VALUE,...]] [--filter-projects=[FILTER_PROJECTS,...]] + [--filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...]] [--filter-services=[FILTER_SERVICES,...]] [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]] [--threshold-rule=[basis=BASIS],[percent=PERCENT]] @@ -108,6 +109,15 @@ OPTIONAL FLAGS usage from only this set of projects should be included in the budget. If omitted, all projects will be included. + --filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...] + A set of folder and organization names of the form folders/{folderId} + or organizations/{organizationId}, specifying that usage from only this + set of folders and organizations should be included in the budget. If + omitted, the budget includes all usage that the billing account pays + for. If the folder or organization contains projects that are paid for + by a different Cloud Billing account, the budget doesn't apply to those + projects. + --filter-services=[FILTER_SERVICES,...] Set of services of the form services/{service_id}, specifying that usage from only this set of services should be included in the budget. diff --git a/gcloud/alpha/billing/budgets/update b/gcloud/alpha/billing/budgets/update index 16734f8ed..abebb0284 100644 --- a/gcloud/alpha/billing/budgets/update +++ b/gcloud/alpha/billing/budgets/update @@ -11,6 +11,7 @@ SYNOPSIS [--filter-credit-types=[FILTER_CREDIT_TYPES,...]] [--filter-labels=[KEY=VALUE,...]] [--filter-projects=[FILTER_PROJECTS,...]] + [--filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...]] [--filter-services=[FILTER_SERVICES,...]] [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]] [--budget-amount=BUDGET_AMOUNT | --last-period-amount] @@ -109,6 +110,15 @@ FLAGS usage from only this set of projects should be included in the budget. If omitted, all projects will be included. + --filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...] + A set of folder and organization names of the form folders/{folderId} + or organizations/{organizationId}, specifying that usage from only this + set of folders and organizations should be included in the budget. If + omitted, the budget includes all usage that the billing account pays + for. If the folder or organization contains projects that are paid for + by a different Cloud Billing account, the budget doesn't apply to those + projects. + --filter-services=[FILTER_SERVICES,...] Set of services of the form services/{service_id}, specifying that usage from only this set of services should be included in the budget. diff --git a/gcloud/alpha/certificate-manager/trust-configs/delete b/gcloud/alpha/certificate-manager/trust-configs/delete index 285bd782e..dc3ba58e1 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/delete +++ b/gcloud/alpha/certificate-manager/trust-configs/delete @@ -73,7 +73,9 @@ 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: + access allowlist. These variants are also available: + + $ gcloud certificate-manager trust-configs delete $ gcloud beta certificate-manager trust-configs delete diff --git a/gcloud/alpha/certificate-manager/trust-configs/describe b/gcloud/alpha/certificate-manager/trust-configs/describe index a4e5da2ec..167a2c9fc 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/describe +++ b/gcloud/alpha/certificate-manager/trust-configs/describe @@ -64,7 +64,9 @@ 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: + access allowlist. These variants are also available: + + $ gcloud certificate-manager trust-configs describe $ gcloud beta certificate-manager trust-configs describe diff --git a/gcloud/alpha/certificate-manager/trust-configs/export b/gcloud/alpha/certificate-manager/trust-configs/export index ff31d7271..6de3b3282 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/export +++ b/gcloud/alpha/certificate-manager/trust-configs/export @@ -73,7 +73,9 @@ 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: + access allowlist. These variants are also available: + + $ gcloud certificate-manager trust-configs export $ gcloud beta certificate-manager trust-configs export diff --git a/gcloud/alpha/certificate-manager/trust-configs/help b/gcloud/alpha/certificate-manager/trust-configs/help index 2eea1919e..dfe82dcef 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/help +++ b/gcloud/alpha/certificate-manager/trust-configs/help @@ -36,7 +36,9 @@ 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: + access allowlist. These variants are also available: + + $ gcloud certificate-manager trust-configs $ gcloud beta certificate-manager trust-configs diff --git a/gcloud/alpha/certificate-manager/trust-configs/import b/gcloud/alpha/certificate-manager/trust-configs/import index 4029ec44d..d9589bc3a 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/import +++ b/gcloud/alpha/certificate-manager/trust-configs/import @@ -79,7 +79,9 @@ 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: + access allowlist. These variants are also available: + + $ gcloud certificate-manager trust-configs import $ gcloud beta certificate-manager trust-configs import diff --git a/gcloud/alpha/certificate-manager/trust-configs/list b/gcloud/alpha/certificate-manager/trust-configs/list index bbd4e232e..c2bcd2b4e 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/list +++ b/gcloud/alpha/certificate-manager/trust-configs/list @@ -82,7 +82,9 @@ 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: + access allowlist. These variants are also available: + + $ gcloud certificate-manager trust-configs list $ gcloud beta certificate-manager trust-configs list diff --git a/gcloud/alpha/compute/help b/gcloud/alpha/compute/help index 05e082336..a84fddd37 100644 --- a/gcloud/alpha/compute/help +++ b/gcloud/alpha/compute/help @@ -166,6 +166,9 @@ GROUPS shared-vpc (ALPHA) Configure shared VPC. + snapshot-settings + (ALPHA) Describe and update Compute Engine snapshot settings. + snapshots (ALPHA) List, describe, and delete Compute Engine snapshots. diff --git a/gcloud/alpha/compute/images/export b/gcloud/alpha/compute/images/export index 6090e0785..40bb443df 100644 --- a/gcloud/alpha/compute/images/export +++ b/gcloud/alpha/compute/images/export @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud alpha compute images export --destination-uri=DESTINATION_URI (--image=IMAGE | --image-family=IMAGE_FAMILY) [--async] + [--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--export-format=EXPORT_FORMAT] [--image-project=IMAGE_PROJECT] [--log-location=LOG_LOCATION] [--network=NETWORK] [--subnet=SUBNET] @@ -51,6 +52,28 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT + Image import amd export tools use Cloud Build to import and export + images to and from your project. Cloud Build uses a specific service + account to execute builds on your behalf. The Cloud Build service + account generates access token for other service accounts and it is + also used for authentication when building the artifacts for the image + import tool. + + Use this flag to to specify a custom Cloud Build service account for + image import and export. If you don't specify this flag, Cloud Build + runs using your project's default Cloud Build service account. To set + this option, specify the email address corresponding to the required + Cloud Build service account. Note: You must specify the --logs-location + flag when you set the custom Cloud Build service account. + + At minimum, the specified Cloud Build service account needs to have the + following roles assigned: + + ◆ roles/compute.admin + ◆ roles/iam.serviceAccountTokenCreator + ◆ roles/iam.serviceAccountUser + --compute-service-account=COMPUTE_SERVICE_ACCOUNT A temporary virtual machine instance is created in your project during image export. Image export tooling on this temporary instance must be @@ -66,8 +89,8 @@ OPTIONAL FLAGS export on the temporary instance uses the project's default Compute Engine service account. - At minimum, the specified Compute Engine service account needs to have - the following roles assigned: + At a minimum, you need to grant the following roles to the specified + Cloud Build service account: ◆ roles/compute.storageAdmin ◆ roles/storage.objectAdmin diff --git a/gcloud/alpha/compute/images/import b/gcloud/alpha/compute/images/import index 9a0900d46..429df1551 100644 --- a/gcloud/alpha/compute/images/import +++ b/gcloud/alpha/compute/images/import @@ -10,6 +10,7 @@ SYNOPSIS (--aws-source-ami-file-path=AWS_SOURCE_AMI_FILE_PATH | --aws-ami-export-location=AWS_AMI_EXPORT_LOCATION --aws-ami-id=AWS_AMI_ID)) [--no-address] [--async] + [--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--description=DESCRIPTION] [--family=FAMILY] [--no-guest-environment] [--guest-os-features=[GUEST_OS_FEATURE,...]] @@ -145,6 +146,28 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT + Image import amd export tools use Cloud Build to import and export + images to and from your project. Cloud Build uses a specific service + account to execute builds on your behalf. The Cloud Build service + account generates access token for other service accounts and it is + also used for authentication when building the artifacts for the image + import tool. + + Use this flag to to specify a custom Cloud Build service account for + image import and export. If you don't specify this flag, Cloud Build + runs using your project's default Cloud Build service account. To set + this option, specify the email address corresponding to the required + Cloud Build service account. Note: You must specify the --logs-location + flag when you set the custom Cloud Build service account. + + At minimum, the specified Cloud Build service account needs to have the + following roles assigned: + + ◆ roles/compute.admin + ◆ roles/iam.serviceAccountTokenCreator + ◆ roles/iam.serviceAccountUser + --compute-service-account=COMPUTE_SERVICE_ACCOUNT A temporary virtual machine instance is created in your project during image import. Image import tooling on this temporary instance must be @@ -160,8 +183,8 @@ OPTIONAL FLAGS import on the temporary instance uses the project's default Compute Engine service account. - At minimum, the specified Compute Engine service account needs to have - the following roles assigned: + At a minimum, you need to grant the following roles to the specified + Cloud Build service account: ◆ roles/compute.storageAdmin ◆ roles/storage.objectViewer diff --git a/gcloud/alpha/compute/instance-groups/managed/create b/gcloud/alpha/compute/instance-groups/managed/create index 84dd7fa46..2ea91f117 100644 --- a/gcloud/alpha/compute/instance-groups/managed/create +++ b/gcloud/alpha/compute/instance-groups/managed/create @@ -9,13 +9,14 @@ SYNOPSIS [--description=DESCRIPTION] [--[no-]force-update-on-repair] [--initial-delay=INITIAL_DELAY] [--instance-redistribution-type=TYPE] [--list-managed-instances-results=MODE] - [--standby-pool-initial-delay=STANDBY_POOL_INITIAL_DELAY] - [--standby-pool-mode=STANDBY_POOL_MODE] + [--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY] + [--standby-policy-mode=STANDBY_POLICY_MODE] [--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]] [--stateful-external-ip=[enabled], [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] [--stateful-internal-ip=[enabled], [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] + [--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE] [--target-distribution-shape=SHAPE] [--target-pool=[TARGET_POOL,...]] [--zones=ZONE,[ZONE,...]] [--health-check=HEALTH_CHECK | --http-health-check=HTTP_HEALTH_CHECK @@ -142,12 +143,12 @@ OPTIONAL FLAGS Pagination is enabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are respected. - --standby-pool-initial-delay=STANDBY_POOL_INITIAL_DELAY + --standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY Specifies the initialization delay for stopping/suspending instances. - --standby-pool-mode=STANDBY_POOL_MODE + --standby-policy-mode=STANDBY_POLICY_MODE Defines behaviour of using instances from standby pool to resize MIG. - STANDBY_POOL_MODE must be one of: + STANDBY_POLICY_MODE must be one of: MANUAL MIG does not automatically stop/start or suspend/resume VMs. @@ -245,6 +246,12 @@ OPTIONAL FLAGS the instance is deleted manually or when the group size is decreased. + --stopped-size=STOPPED_SIZE + Specifies the number of stopped instances. + + --suspended-size=SUSPENDED_SIZE + Specifies the number of suspended instances. + --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its instances across zones within the region. The default shape is even. diff --git a/gcloud/alpha/compute/instance-groups/managed/update b/gcloud/alpha/compute/instance-groups/managed/update index 626129781..7e14ce83b 100644 --- a/gcloud/alpha/compute/instance-groups/managed/update +++ b/gcloud/alpha/compute/instance-groups/managed/update @@ -11,13 +11,14 @@ SYNOPSIS [--remove-stateful-disks=DEVICE_NAME,[DEVICE_NAME,...]] [--remove-stateful-external-ips=INTERFACE_NAME,[...]] [--remove-stateful-internal-ips=INTERFACE_NAME,[...]] - [--standby-pool-initial-delay=STANDBY_POOL_INITIAL_DELAY] - [--standby-pool-mode=STANDBY_POOL_MODE] + [--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY] + [--standby-policy-mode=STANDBY_POLICY_MODE] [--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]] [--stateful-external-ip=[enabled], [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] [--stateful-internal-ip=[enabled], [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] + [--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE] [--target-distribution-shape=SHAPE] [--clear-autohealing | --initial-delay=INITIAL_DELAY --health-check=HEALTH_CHECK @@ -132,12 +133,12 @@ FLAGS Remove stateful configuration for the specified interfaces for internal IPs. - --standby-pool-initial-delay=STANDBY_POOL_INITIAL_DELAY + --standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY Specifies the initialization delay for stopping/suspending instances. - --standby-pool-mode=STANDBY_POOL_MODE + --standby-policy-mode=STANDBY_POLICY_MODE Defines behaviour of using instances from standby pool to resize MIG. - STANDBY_POOL_MODE must be one of: + STANDBY_POLICY_MODE must be one of: MANUAL MIG does not automatically stop/start or suspend/resume VMs. @@ -248,6 +249,12 @@ FLAGS the instance is deleted manually or when the group size is decreased. + --stopped-size=STOPPED_SIZE + Specifies the number of stopped instances. + + --suspended-size=SUSPENDED_SIZE + Specifies the number of suspended instances. + --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its instances across zones within the region. The default shape is even. diff --git a/gcloud/alpha/compute/instances/import b/gcloud/alpha/compute/instances/import index a41f9b584..b72de0623 100644 --- a/gcloud/alpha/compute/instances/import +++ b/gcloud/alpha/compute/instances/import @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha compute instances import INSTANCE_NAME --source-uri=SOURCE_URI [--no-address] [--async] [--byol] [--can-ip-forward] + [--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--deletion-protection] [--description=DESCRIPTION] [--no-guest-environment] [--guest-os-features=[GUEST_OS_FEATURE,...]] @@ -89,6 +90,28 @@ OPTIONAL FLAGS If provided, allows the instances to send and receive packets with non-matching destination or source IP addresses. + --cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT + Image import amd export tools use Cloud Build to import and export + images to and from your project. Cloud Build uses a specific service + account to execute builds on your behalf. The Cloud Build service + account generates access token for other service accounts and it is + also used for authentication when building the artifacts for the image + import tool. + + Use this flag to to specify a custom Cloud Build service account for + image import and export. If you don't specify this flag, Cloud Build + runs using your project's default Cloud Build service account. To set + this option, specify the email address corresponding to the required + Cloud Build service account. Note: You must specify the --logs-location + flag when you set the custom Cloud Build service account. + + At minimum, the specified Cloud Build service account needs to have the + following roles assigned: + + ◆ roles/compute.admin + ◆ roles/iam.serviceAccountTokenCreator + ◆ roles/iam.serviceAccountUser + --compute-service-account=COMPUTE_SERVICE_ACCOUNT A temporary virtual machine instance is created in your project during instance import. Instance import tooling on this temporary instance @@ -104,8 +127,8 @@ OPTIONAL FLAGS import on the temporary instance uses the project's default Compute Engine service account. - At minimum, the specified Compute Engine service account needs to have - the following roles assigned: + At a minimum, you need to grant the following roles to the specified + Cloud Build service account: ◆ roles/compute.storageAdmin ◆ roles/storage.objectViewer diff --git a/gcloud/alpha/compute/machine-images/import b/gcloud/alpha/compute/machine-images/import index fc05c8192..aa3c3554d 100644 --- a/gcloud/alpha/compute/machine-images/import +++ b/gcloud/alpha/compute/machine-images/import @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha compute machine-images import IMAGE --source-uri=SOURCE_URI [--no-address] [--async] [--byol] [--can-ip-forward] + [--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--description=DESCRIPTION] [--no-guest-environment] [--guest-flush] [--guest-os-features=[GUEST_OS_FEATURE,...]] [--labels=[KEY=VALUE,...]] @@ -88,6 +89,28 @@ OPTIONAL FLAGS send and receive packets with non-matching destination or source IP addresses. + --cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT + Image import amd export tools use Cloud Build to import and export + images to and from your project. Cloud Build uses a specific service + account to execute builds on your behalf. The Cloud Build service + account generates access token for other service accounts and it is + also used for authentication when building the artifacts for the image + import tool. + + Use this flag to to specify a custom Cloud Build service account for + image import and export. If you don't specify this flag, Cloud Build + runs using your project's default Cloud Build service account. To set + this option, specify the email address corresponding to the required + Cloud Build service account. Note: You must specify the --logs-location + flag when you set the custom Cloud Build service account. + + At minimum, the specified Cloud Build service account needs to have the + following roles assigned: + + ◆ roles/compute.admin + ◆ roles/iam.serviceAccountTokenCreator + ◆ roles/iam.serviceAccountUser + --compute-service-account=COMPUTE_SERVICE_ACCOUNT A temporary virtual machine instance is created in your project during machine image import. Machine image import tooling on this temporary @@ -103,8 +126,8 @@ OPTIONAL FLAGS image import on the temporary instance uses the project's default Compute Engine service account. - At minimum, the specified Compute Engine service account needs to have - the following roles assigned: + At a minimum, you need to grant the following roles to the specified + Cloud Build service account: ◆ roles/compute.storageAdmin ◆ roles/storage.objectViewer diff --git a/gcloud/alpha/compute/snapshot-settings/describe b/gcloud/alpha/compute/snapshot-settings/describe new file mode 100644 index 000000000..40baf57d5 --- /dev/null +++ b/gcloud/alpha/compute/snapshot-settings/describe @@ -0,0 +1,36 @@ +NAME + gcloud alpha compute snapshot-settings describe - describe snapshot + settings + +SYNOPSIS + gcloud alpha compute snapshot-settings describe [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe the snapshot settings of a project. + +EXAMPLES + To display the snapshot settings of a project called my-project, run: + + $ gcloud alpha compute snapshot-settings describe \ + --project=my-project + +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 snapshot-settings describe + diff --git a/gcloud/alpha/compute/snapshot-settings/help b/gcloud/alpha/compute/snapshot-settings/help new file mode 100644 index 000000000..07fd02868 --- /dev/null +++ b/gcloud/alpha/compute/snapshot-settings/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha compute snapshot-settings - describe and update Compute Engine + snapshot settings + +SYNOPSIS + gcloud alpha compute snapshot-settings COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe and update Compute Engine snapshot settings. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe snapshot settings. + + update + (ALPHA) Update snapshot settings. + +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 snapshot-settings + diff --git a/gcloud/alpha/compute/snapshot-settings/update b/gcloud/alpha/compute/snapshot-settings/update new file mode 100644 index 000000000..f679d3009 --- /dev/null +++ b/gcloud/alpha/compute/snapshot-settings/update @@ -0,0 +1,71 @@ +NAME + gcloud alpha compute snapshot-settings update - update snapshot settings + +SYNOPSIS + gcloud alpha compute snapshot-settings update [--async] + [--storage-location-names=[STORAGE_LOCATION_NAMES,...]] + [--storage-location-policy=STORAGE_LOCATION_POLICY] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update the snapshot settings of a project. + +EXAMPLES + To update the snapshot settings and set the storage location policy to the + nearest multi-region as the source disk, run: + + $ gcloud alpha compute snapshot-settings update \ + --storage-location-policy=nearest-multi-region + + To update the snapshot settings and set the storage location policy to the + same region as the source disk, run: + + $ gcloud alpha compute snapshot-settings update \ + --storage-location-policy=local-region + + To update the snapshot settings and set the storage location policy to + store snapshots in a specific location like us-west1, run: + + $ gcloud alpha compute snapshot-settings update \ + --storage-location-policy=specific-locations \ + --storage-location-names=us-west1 + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --storage-location-names=[STORAGE_LOCATION_NAMES,...] + The custom storage locations that you specify for the project's + snapshots. Use this flag only when you use the SPECIFIC_LOCATIONS value + for the --storage-location-policy flag. For more information, refer to + the snapshot settings documentation at + https://cloud.google.com/compute/docs/disks/snapshot-settings. + + --storage-location-policy=STORAGE_LOCATION_POLICY + The storage location policy. For more information, refer to the + snapshot settings documentation at + https://cloud.google.com/compute/docs/disks/snapshot-settings. + STORAGE_LOCATION_POLICY must be one of: local-region, + nearest-multi-region, specific-locations. + +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 snapshot-settings update + diff --git a/gcloud/alpha/container/aws/node-pools/create b/gcloud/alpha/container/aws/node-pools/create index 301cdbfe6..66b9feb73 100644 --- a/gcloud/alpha/container/aws/node-pools/create +++ b/gcloud/alpha/container/aws/node-pools/create @@ -12,6 +12,8 @@ SYNOPSIS [--annotations=ANNOTATION,[ANNOTATION,...]] [--async] [--enable-autorepair] [--image-type=IMAGE_TYPE] [--instance-placement=INSTANCE_PLACEMENT] + [--max-surge-update=MAX_SURGE_UPDATE] + [--max-unavailable-update=MAX_UNAVAILABLE_UPDATE] [--node-labels=NODE_LABEL,[NODE_LABEL,...]] [--node-taints=NODE_TAINT,[NODE_TAINT,...]] [--root-volume-iops=ROOT_VOLUME_IOPS] @@ -141,6 +143,29 @@ OPTIONAL FLAGS Type of the tenancy. INSTANCE_PLACEMENT must be one of: dedicated, default, host. + --max-surge-update=MAX_SURGE_UPDATE + Maximum number of extra (surge) nodes to be created beyond the current + size of the node pool during its update process. Use + --max-unavailable-update as well, if needed, to control the overall + surge settings. + + To create an extra node each time the node pool is rolling updated, + run: + + $ gcloud alpha container aws node-pools create \ + --max-surge-update=1 --max-unavailable-update=0 + + --max-unavailable-update=MAX_UNAVAILABLE_UPDATE + Maximum number of nodes that can be simultaneously unavailable during + this node pool's update process. Use --max-surge-update as well, if + needed, to control the overall surge settings. + + To update 3 nodes in parallel (1 + 2), but keep at least 4 nodes (6 - + 2) available each time the node pool is rolling updated, run: + + $ gcloud alpha container aws node-pools create --min-nodes=6 \ + --max-surge-update=1 --max-unavailable-update=2 + --node-labels=NODE_LABEL,[NODE_LABEL,...] Labels assigned to the node pool's nodes. diff --git a/gcloud/alpha/container/aws/node-pools/update b/gcloud/alpha/container/aws/node-pools/update index b611ce25d..b15dbf232 100644 --- a/gcloud/alpha/container/aws/node-pools/update +++ b/gcloud/alpha/container/aws/node-pools/update @@ -7,6 +7,8 @@ SYNOPSIS (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] [--config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN] [--enable-autorepair] [--iam-instance-profile=IAM_INSTANCE_PROFILE] + [--instance-type=INSTANCE_TYPE] [--max-surge-update=MAX_SURGE_UPDATE] + [--max-unavailable-update=MAX_UNAVAILABLE_UPDATE] [--node-version=NODE_VERSION] [--root-volume-iops=ROOT_VOLUME_IOPS] [--root-volume-kms-key-arn=ROOT_VOLUME_KMS_KEY_ARN] [--root-volume-size=ROOT_VOLUME_SIZE] @@ -92,6 +94,33 @@ FLAGS --iam-instance-profile=IAM_INSTANCE_PROFILE Name or ARN of the IAM instance profile associated with the node pool. + --instance-type=INSTANCE_TYPE + AWS EC2 instance type for the node pool's nodes. + + --max-surge-update=MAX_SURGE_UPDATE + Maximum number of extra (surge) nodes to be created beyond the current + size of the node pool during its update process. Use + --max-unavailable-update as well, if needed, to control the overall + surge settings. + + To create an extra node each time the node pool is rolling updated, + run: + + $ gcloud alpha container aws node-pools update \ + --max-surge-update=1 --max-unavailable-update=0 + + --max-unavailable-update=MAX_UNAVAILABLE_UPDATE + Maximum number of nodes that can be simultaneously unavailable during + this node pool's update process. Use --max-surge-update as well, if + needed, to control the overall surge settings. + + To modify a node pool with 6 nodes such that, 3 nodes are updated in + parallel (1 + 2), but keep at least 4 nodes (6 - 2) available each time + this node pool is rolling updated, run: + + $ gcloud alpha container aws node-pools update \ + --max-surge-update=1 --max-unavailable-update=2 + --node-version=NODE_VERSION Kubernetes version to use for the node pool. diff --git a/gcloud/alpha/container/binauthz/continuous-validation/enable b/gcloud/alpha/container/binauthz/continuous-validation/enable index 319929cd7..66c29a1bb 100644 --- a/gcloud/alpha/container/binauthz/continuous-validation/enable +++ b/gcloud/alpha/container/binauthz/continuous-validation/enable @@ -1,5 +1,5 @@ NAME - gcloud alpha container binauthz continuous-validation enable - disable + gcloud alpha container binauthz continuous-validation enable - enable Binary Authorization Continuous Validation for the project SYNOPSIS diff --git a/gcloud/alpha/container/binauthz/continuous-validation/help b/gcloud/alpha/container/binauthz/continuous-validation/help index 1dbba114c..54c2b5592 100644 --- a/gcloud/alpha/container/binauthz/continuous-validation/help +++ b/gcloud/alpha/container/binauthz/continuous-validation/help @@ -26,7 +26,7 @@ COMMANDS project. enable - (ALPHA) Disable Binary Authorization Continuous Validation for the + (ALPHA) Enable Binary Authorization Continuous Validation for the project. NOTES diff --git a/gcloud/alpha/dataplex/datascans/create/data-profile b/gcloud/alpha/dataplex/datascans/create/data-profile index c9e43e386..b2c686064 100644 --- a/gcloud/alpha/dataplex/datascans/create/data-profile +++ b/gcloud/alpha/dataplex/datascans/create/data-profile @@ -24,11 +24,14 @@ DESCRIPTION EXAMPLES To create a data profile scan data-profile-datascan in project test-project - located in us-central1, run: + located in us-central1 on bigquery resource table test-table in dataset + test-dataset, run: $ gcloud alpha dataplex datascans create data-profile \ data-profile-datascan --project=test-project \ - --location=us-central1 + --location=us-central1 \ + --data-source-resource="//bigquery.googleapis.com/projects/test-\ + project/datasets/test-dataset/tables/test-table" POSITIONAL ARGUMENTS Datascan resource - Arguments and flags that define the Dataplex datascan diff --git a/gcloud/alpha/dataplex/datascans/create/data-quality b/gcloud/alpha/dataplex/datascans/create/data-quality index b0db7f039..27569d8b9 100644 --- a/gcloud/alpha/dataplex/datascans/create/data-quality +++ b/gcloud/alpha/dataplex/datascans/create/data-quality @@ -20,11 +20,14 @@ DESCRIPTION EXAMPLES To create a data quality scan data-quality-datascan in project test-project - located in us-central1 with data spec file data-quality-spec.json, run: + located in us-central1 on bigquery resource table test-table in dataset + test-dataset with data spec file data-quality-spec.json, run: $ gcloud alpha dataplex datascans create data-quality \ data-quality-datascan --project=test-project \ --location=us-central1 \ + --data-source-resource="//bigquery.googleapis.com/projects/test-\ + project/datasets/test-dataset/tables/test-table" \ --data-quality-spec-file="data-quality-spec.json" POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/deploy/delivery-pipelines/help b/gcloud/alpha/deploy/delivery-pipelines/help index a913b93d0..90e4bad7f 100644 --- a/gcloud/alpha/deploy/delivery-pipelines/help +++ b/gcloud/alpha/deploy/delivery-pipelines/help @@ -1,13 +1,12 @@ NAME gcloud alpha deploy delivery-pipelines - create and manage Delivery - Pipeline resources for Google Cloud Deploy + Pipeline resources for Cloud Deploy SYNOPSIS gcloud alpha deploy delivery-pipelines COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create and manage Delivery Pipeline resources for Google Cloud - Deploy. + (ALPHA) Create and manage Delivery Pipeline resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/deploy/help b/gcloud/alpha/deploy/help index 28f172816..d447f0ae6 100644 --- a/gcloud/alpha/deploy/help +++ b/gcloud/alpha/deploy/help @@ -1,11 +1,11 @@ NAME - gcloud alpha deploy - create and manage Google Cloud Deploy resources + gcloud alpha deploy - create and manage Cloud Deploy resources SYNOPSIS gcloud alpha deploy GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create and manage Google Cloud Deploy resources. + (ALPHA) Create and manage Cloud Deploy resources. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -16,20 +16,19 @@ GROUPS GROUP is one of the following: delivery-pipelines - (ALPHA) Create and manage Delivery Pipeline resources for Google Cloud - Deploy. + (ALPHA) Create and manage Delivery Pipeline resources for Cloud Deploy. job-runs - (ALPHA) Manages job runs resources for Google Cloud Deploy. + (ALPHA) Manages job runs resources for Cloud Deploy. releases - (ALPHA) Create and manage Release resources for Google Cloud Deploy. + (ALPHA) Create and manage Release resources for Cloud Deploy. rollouts - (ALPHA) Create and manage Rollout resources for Google Cloud Deploy. + (ALPHA) Create and manage Rollout resources for Cloud Deploy. targets - (ALPHA) Create and manage Target resources for Google Cloud Deploy. + (ALPHA) Create and manage Target resources for Cloud Deploy. COMMANDS COMMAND is one of the following: diff --git a/gcloud/alpha/deploy/job-runs/help b/gcloud/alpha/deploy/job-runs/help index 17c732c5d..242586cec 100644 --- a/gcloud/alpha/deploy/job-runs/help +++ b/gcloud/alpha/deploy/job-runs/help @@ -1,12 +1,11 @@ NAME - gcloud alpha deploy job-runs - manages job runs resources for Google Cloud - Deploy + gcloud alpha deploy job-runs - manages job runs resources for Cloud Deploy SYNOPSIS gcloud alpha deploy job-runs COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manages job runs resources for Google Cloud Deploy. + (ALPHA) Manages job runs resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/deploy/releases/help b/gcloud/alpha/deploy/releases/help index 5bff7dcb8..7144ee1f2 100644 --- a/gcloud/alpha/deploy/releases/help +++ b/gcloud/alpha/deploy/releases/help @@ -1,12 +1,12 @@ NAME gcloud alpha deploy releases - create and manage Release resources for - Google Cloud Deploy + Cloud Deploy SYNOPSIS gcloud alpha deploy releases COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create and manage Release resources for Google Cloud Deploy. + (ALPHA) Create and manage Release resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/deploy/rollouts/help b/gcloud/alpha/deploy/rollouts/help index 5415c528b..f34389e9d 100644 --- a/gcloud/alpha/deploy/rollouts/help +++ b/gcloud/alpha/deploy/rollouts/help @@ -1,12 +1,12 @@ NAME gcloud alpha deploy rollouts - create and manage Rollout resources for - Google Cloud Deploy + Cloud Deploy SYNOPSIS gcloud alpha deploy rollouts COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create and manage Rollout resources for Google Cloud Deploy. + (ALPHA) Create and manage Rollout resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/deploy/targets/help b/gcloud/alpha/deploy/targets/help index cdb604729..f591d7c64 100644 --- a/gcloud/alpha/deploy/targets/help +++ b/gcloud/alpha/deploy/targets/help @@ -1,12 +1,12 @@ NAME - gcloud alpha deploy targets - create and manage Target resources for Google - Cloud Deploy + gcloud alpha deploy targets - create and manage Target resources for Cloud + Deploy SYNOPSIS gcloud alpha deploy targets COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create and manage Target resources for Google Cloud Deploy. + (ALPHA) Create and manage Target resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/monitoring/metrics-scopes/create b/gcloud/alpha/monitoring/metrics-scopes/create index ec706045f..67ba456cc 100644 --- a/gcloud/alpha/monitoring/metrics-scopes/create +++ b/gcloud/alpha/monitoring/metrics-scopes/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha monitoring metrics-scopes create - MONITORED_PROJECT_ID_OR_NUMBER [GCLOUD_WIDE_FLAG ...] + MONITORED_RESOURCE_CONTAINER_NAME [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command can fail for the following reasons: @@ -21,20 +21,22 @@ EXAMPLES monitored-project-1 to a metrics scope with project id metrics-scope-1 assuming the metrics-scope-1 is the default project: - $ gcloud alpha monitoring metrics-scopes create monitored-project-1 + $ gcloud alpha monitoring metrics-scopes create \ + projects/monitored-project-1 The following command adds a monitored project with the ID monitored-project-1 to a metrics scope with project id metrics-scope-1: $ gcloud alpha monitoring metrics-scopes create \ - monitored-project-1 --project=metrics-scope-1 + projects/monitored-project-1 --project=metrics-scope-1 $ gcloud alpha monitoring metrics-scopes create \ locations/global/metricsScopes/metrics-scope-1/projects/\ monitored-project-1 POSITIONAL ARGUMENTS - MONITORED_PROJECT_ID_OR_NUMBER - Monitored project ID or number for the project you want to create. + MONITORED_RESOURCE_CONTAINER_NAME + Monitored resource container (example - projects/PROJECT_ID) project + you want to create. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/monitoring/metrics-scopes/delete b/gcloud/alpha/monitoring/metrics-scopes/delete index 29fb3df9d..f9dc3ee70 100644 --- a/gcloud/alpha/monitoring/metrics-scopes/delete +++ b/gcloud/alpha/monitoring/metrics-scopes/delete @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha monitoring metrics-scopes delete - MONITORED_PROJECT_ID_OR_NUMBER [GCLOUD_WIDE_FLAG ...] + MONITORED_RESOURCE_CONTAINER_NAME [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command can fail for the following reasons: @@ -20,20 +20,22 @@ EXAMPLES monitored-project-1 to a metrics scope with project id metrics-scope-1 assuming the metrics-scope-1 is the default project: - $ gcloud alpha monitoring metrics-scopes delete monitored-project-1 + $ gcloud alpha monitoring metrics-scopes delete \ + projects/monitored-project-1 The following command adds a monitored project with the ID monitored-project-1 to a metrics scope with project id metrics-scope-1: $ gcloud alpha monitoring metrics-scopes delete \ - monitored-project-1 --project=metrics-scope-1 + projects/monitored-project-1 --project=metrics-scope-1 $ gcloud alpha monitoring metrics-scopes delete \ locations/global/metricsScopes/metrics-scope-1/projects/\ monitored-project-1 POSITIONAL ARGUMENTS - MONITORED_PROJECT_ID_OR_NUMBER - Monitored project ID or number for the project you want to delete. + MONITORED_RESOURCE_CONTAINER_NAME + Monitored resource container (example - projects/PROJECT_ID) project + you want to delete. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/monitoring/metrics-scopes/help b/gcloud/alpha/monitoring/metrics-scopes/help index 96187ee34..bf1024750 100644 --- a/gcloud/alpha/monitoring/metrics-scopes/help +++ b/gcloud/alpha/monitoring/metrics-scopes/help @@ -30,7 +30,8 @@ COMMANDS (ALPHA) Describe a Cloud Monitoring metrics scope. list - (ALPHA) List the metrics scopes monitoring the specified project. + (ALPHA) List the metrics scopes monitoring the specified monitored + resource container. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/monitoring/metrics-scopes/list b/gcloud/alpha/monitoring/metrics-scopes/list index f511bb772..401d2eb81 100644 --- a/gcloud/alpha/monitoring/metrics-scopes/list +++ b/gcloud/alpha/monitoring/metrics-scopes/list @@ -1,11 +1,12 @@ NAME gcloud alpha monitoring metrics-scopes list - list the metrics scopes - monitoring the specified project + monitoring the specified monitored resource container SYNOPSIS - gcloud alpha monitoring metrics-scopes list PROJECT_ID_OR_NUMBER - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + gcloud alpha monitoring metrics-scopes list + MONITORED_RESOURCE_CONTAINER_NAME [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command can fail for the following reasons: @@ -19,11 +20,12 @@ DESCRIPTION EXAMPLES To list the metrics scopes monitoring MY-PROJECT-ID - $ gcloud alpha monitoring metrics-scopes list MY-PROJECT-ID + $ gcloud alpha monitoring metrics-scopes list projects/MY-PROJECT-ID POSITIONAL ARGUMENTS - PROJECT_ID_OR_NUMBER - ID or number for the project you want to list. + MONITORED_RESOURCE_CONTAINER_NAME + Monitored resource container (example - projects/PROJECT_ID) project + you want to list. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/netapp/storage-pools/create b/gcloud/alpha/netapp/storage-pools/create index 7b0aecbb9..84339f1e2 100644 --- a/gcloud/alpha/netapp/storage-pools/create +++ b/gcloud/alpha/netapp/storage-pools/create @@ -91,6 +91,10 @@ REQUIRED FLAGS Premium Service Level for Cloud NetApp Storage Pool. The Premium Service Level has a throughput per TiB of allocated volume size of 64 MiB/s. + standard + Standard Service Level for Cloud NetApp Storage Pool. The Standard + Service Level has a throughput per TiB of allocated volume size of + 128 MiB/s. OPTIONAL FLAGS Active directory resource - The Active Directory to attach to the Storage diff --git a/gcloud/alpha/network-security/server-tls-policies/describe b/gcloud/alpha/network-security/server-tls-policies/describe index ec3ef5890..52a523b6e 100644 --- a/gcloud/alpha/network-security/server-tls-policies/describe +++ b/gcloud/alpha/network-security/server-tls-policies/describe @@ -63,7 +63,9 @@ 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: + access allowlist. These variants are also available: + + $ gcloud network-security server-tls-policies describe $ gcloud beta network-security server-tls-policies describe diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 271b95f37..ac4b04f3f 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -318,19 +318,27 @@ FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. + Specify which of the outbound traffic to send through Direct VPC + egress or the VPC connector for this resource. This resource must + have Direct VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC - connector. Provides the same functionality as 'all-traffic'. - Prefer to use 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + (RFC 1918 and Private Google Access IPs) through Direct VPC + egress or the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. These flags modify the Cloud SQL instances this Service connects to. You can specify a name of a Cloud SQL instance if it's in the same project diff --git a/gcloud/alpha/run/jobs/create b/gcloud/alpha/run/jobs/create index 0e7ff8869..59a1aec36 100644 --- a/gcloud/alpha/run/jobs/create +++ b/gcloud/alpha/run/jobs/create @@ -143,19 +143,27 @@ OPTIONAL FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. - VPC_EGRESS must be one of: + Specify which of the outbound traffic to send through Direct VPC egress + or the VPC connector for this resource. This resource must have Direct + VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must + be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC connector. - Provides the same functionality as 'all-traffic'. Prefer to use - 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only - Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + Default option. Sends outbound traffic to private IP addresses (RFC + 1918 and Private Google Access IPs) through Direct VPC egress or + the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. At most one of these can be specified: diff --git a/gcloud/alpha/run/jobs/deploy b/gcloud/alpha/run/jobs/deploy index 1c58c7853..71842dd34 100644 --- a/gcloud/alpha/run/jobs/deploy +++ b/gcloud/alpha/run/jobs/deploy @@ -142,19 +142,27 @@ FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. - VPC_EGRESS must be one of: + Specify which of the outbound traffic to send through Direct VPC egress + or the VPC connector for this resource. This resource must have Direct + VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must + be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC connector. - Provides the same functionality as 'all-traffic'. Prefer to use - 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only - Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + Default option. Sends outbound traffic to private IP addresses (RFC + 1918 and Private Google Access IPs) through Direct VPC egress or + the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. At most one of these can be specified: diff --git a/gcloud/alpha/run/jobs/update b/gcloud/alpha/run/jobs/update index c7ccd347d..da858832e 100644 --- a/gcloud/alpha/run/jobs/update +++ b/gcloud/alpha/run/jobs/update @@ -131,19 +131,27 @@ FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. - VPC_EGRESS must be one of: + Specify which of the outbound traffic to send through Direct VPC egress + or the VPC connector for this resource. This resource must have Direct + VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must + be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC connector. - Provides the same functionality as 'all-traffic'. Prefer to use - 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only - Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + Default option. Sends outbound traffic to private IP addresses (RFC + 1918 and Private Google Access IPs) through Direct VPC egress or + the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. These flags modify the Cloud SQL instances this Service connects to. You can specify a name of a Cloud SQL instance if it's in the same project and diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 13405a46e..6a2fa6813 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -223,19 +223,27 @@ FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. + Specify which of the outbound traffic to send through Direct VPC + egress or the VPC connector for this resource. This resource must + have Direct VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC - connector. Provides the same functionality as 'all-traffic'. - Prefer to use 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + (RFC 1918 and Private Google Access IPs) through Direct VPC + egress or the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. These flags modify the Cloud SQL instances this Service connects to. You can specify a name of a Cloud SQL instance if it's in the same project diff --git a/gcloud/beta/alloydb/clusters/restore b/gcloud/beta/alloydb/clusters/restore index 257de8d41..3fdc7884a 100644 --- a/gcloud/beta/alloydb/clusters/restore +++ b/gcloud/beta/alloydb/clusters/restore @@ -42,7 +42,12 @@ REQUIRED FLAGS Exactly one of these must be specified: --backup=BACKUP - AlloyDB backup ID + The AlloyDB backup to restore from. This must either be the full + backup name + (projects/myProject/locations/us-central1/backups/myBackup) or the + backup ID (myBackup). In the second case, the project and location + are assumed to be the same as the restored cluster that is being + created. Restore a cluster from a source cluster at a given point in time. @@ -54,7 +59,12 @@ REQUIRED FLAGS in this group are specified. --source-cluster=SOURCE_CLUSTER - Source cluster name. + The AlloyDB source cluster to restore from. This must either be the + full cluster name + (projects/myProject/locations/us-central1/backups/myCluster) or the + cluster ID (myCluster). In the second case, the project and + location are assumed to be the same as the restored cluster that is + being created. This flag argument must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/beta/billing/budgets/create b/gcloud/beta/billing/budgets/create index eed2d3862..5c78bb876 100644 --- a/gcloud/beta/billing/budgets/create +++ b/gcloud/beta/billing/budgets/create @@ -12,6 +12,7 @@ SYNOPSIS [--filter-credit-types=[FILTER_CREDIT_TYPES,...]] [--filter-labels=[KEY=VALUE,...]] [--filter-projects=[FILTER_PROJECTS,...]] + [--filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...]] [--filter-services=[FILTER_SERVICES,...]] [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]] [--threshold-rule=[basis=BASIS],[percent=PERCENT]] @@ -108,6 +109,15 @@ OPTIONAL FLAGS usage from only this set of projects should be included in the budget. If omitted, all projects will be included. + --filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...] + A set of folder and organization names of the form folders/{folderId} + or organizations/{organizationId}, specifying that usage from only this + set of folders and organizations should be included in the budget. If + omitted, the budget includes all usage that the billing account pays + for. If the folder or organization contains projects that are paid for + by a different Cloud Billing account, the budget doesn't apply to those + projects. + --filter-services=[FILTER_SERVICES,...] Set of services of the form services/{service_id}, specifying that usage from only this set of services should be included in the budget. diff --git a/gcloud/beta/billing/budgets/update b/gcloud/beta/billing/budgets/update index 0faad49de..53282e6fc 100644 --- a/gcloud/beta/billing/budgets/update +++ b/gcloud/beta/billing/budgets/update @@ -11,6 +11,7 @@ SYNOPSIS [--filter-credit-types=[FILTER_CREDIT_TYPES,...]] [--filter-labels=[KEY=VALUE,...]] [--filter-projects=[FILTER_PROJECTS,...]] + [--filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...]] [--filter-services=[FILTER_SERVICES,...]] [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]] [--budget-amount=BUDGET_AMOUNT | --last-period-amount] @@ -109,6 +110,15 @@ FLAGS usage from only this set of projects should be included in the budget. If omitted, all projects will be included. + --filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...] + A set of folder and organization names of the form folders/{folderId} + or organizations/{organizationId}, specifying that usage from only this + set of folders and organizations should be included in the budget. If + omitted, the budget includes all usage that the billing account pays + for. If the folder or organization contains projects that are paid for + by a different Cloud Billing account, the budget doesn't apply to those + projects. + --filter-services=[FILTER_SERVICES,...] Set of services of the form services/{service_id}, specifying that usage from only this set of services should be included in the budget. diff --git a/gcloud/beta/certificate-manager/trust-configs/delete b/gcloud/beta/certificate-manager/trust-configs/delete index 07e910c8d..58f17c2a1 100644 --- a/gcloud/beta/certificate-manager/trust-configs/delete +++ b/gcloud/beta/certificate-manager/trust-configs/delete @@ -70,8 +70,10 @@ API REFERENCE this API can be found at: https://cloud.google.com/certificate-manager NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud certificate-manager trust-configs delete $ gcloud alpha certificate-manager trust-configs delete diff --git a/gcloud/beta/certificate-manager/trust-configs/describe b/gcloud/beta/certificate-manager/trust-configs/describe index 9e621d048..78fa9da0b 100644 --- a/gcloud/beta/certificate-manager/trust-configs/describe +++ b/gcloud/beta/certificate-manager/trust-configs/describe @@ -61,8 +61,10 @@ API REFERENCE this API can be found at: https://cloud.google.com/certificate-manager NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud certificate-manager trust-configs describe $ gcloud alpha certificate-manager trust-configs describe diff --git a/gcloud/beta/certificate-manager/trust-configs/export b/gcloud/beta/certificate-manager/trust-configs/export index a3d7c6fab..8f69990b3 100644 --- a/gcloud/beta/certificate-manager/trust-configs/export +++ b/gcloud/beta/certificate-manager/trust-configs/export @@ -70,8 +70,10 @@ API REFERENCE this API can be found at: https://cloud.google.com/certificate-manager NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud certificate-manager trust-configs export $ gcloud alpha certificate-manager trust-configs export diff --git a/gcloud/beta/certificate-manager/trust-configs/help b/gcloud/beta/certificate-manager/trust-configs/help index de5de6c8a..7d75af222 100644 --- a/gcloud/beta/certificate-manager/trust-configs/help +++ b/gcloud/beta/certificate-manager/trust-configs/help @@ -33,8 +33,10 @@ COMMANDS (BETA) List all TrustConfigs in a project. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud certificate-manager trust-configs $ gcloud alpha certificate-manager trust-configs diff --git a/gcloud/beta/certificate-manager/trust-configs/import b/gcloud/beta/certificate-manager/trust-configs/import index 80e772899..2a5b75b92 100644 --- a/gcloud/beta/certificate-manager/trust-configs/import +++ b/gcloud/beta/certificate-manager/trust-configs/import @@ -76,8 +76,10 @@ API REFERENCE this API can be found at: https://cloud.google.com/certificate-manager NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud certificate-manager trust-configs import $ gcloud alpha certificate-manager trust-configs import diff --git a/gcloud/beta/certificate-manager/trust-configs/list b/gcloud/beta/certificate-manager/trust-configs/list index c4eb65819..032589918 100644 --- a/gcloud/beta/certificate-manager/trust-configs/list +++ b/gcloud/beta/certificate-manager/trust-configs/list @@ -79,8 +79,10 @@ API REFERENCE this API can be found at: https://cloud.google.com/certificate-manager NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud certificate-manager trust-configs list $ gcloud alpha certificate-manager trust-configs list diff --git a/gcloud/beta/compute/help b/gcloud/beta/compute/help index 97275c644..044cd8b09 100644 --- a/gcloud/beta/compute/help +++ b/gcloud/beta/compute/help @@ -162,6 +162,9 @@ GROUPS shared-vpc (BETA) Configure shared VPC. + snapshot-settings + (BETA) Describe and update Compute Engine snapshot settings. + snapshots (BETA) List, describe, and delete Compute Engine snapshots. diff --git a/gcloud/beta/compute/images/export b/gcloud/beta/compute/images/export index 605a3c380..8b21e6b99 100644 --- a/gcloud/beta/compute/images/export +++ b/gcloud/beta/compute/images/export @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud beta compute images export --destination-uri=DESTINATION_URI (--image=IMAGE | --image-family=IMAGE_FAMILY) [--async] + [--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--export-format=EXPORT_FORMAT] [--image-project=IMAGE_PROJECT] [--log-location=LOG_LOCATION] [--network=NETWORK] [--subnet=SUBNET] @@ -51,6 +52,28 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT + Image import amd export tools use Cloud Build to import and export + images to and from your project. Cloud Build uses a specific service + account to execute builds on your behalf. The Cloud Build service + account generates access token for other service accounts and it is + also used for authentication when building the artifacts for the image + import tool. + + Use this flag to to specify a custom Cloud Build service account for + image import and export. If you don't specify this flag, Cloud Build + runs using your project's default Cloud Build service account. To set + this option, specify the email address corresponding to the required + Cloud Build service account. Note: You must specify the --logs-location + flag when you set the custom Cloud Build service account. + + At minimum, the specified Cloud Build service account needs to have the + following roles assigned: + + ◆ roles/compute.admin + ◆ roles/iam.serviceAccountTokenCreator + ◆ roles/iam.serviceAccountUser + --compute-service-account=COMPUTE_SERVICE_ACCOUNT A temporary virtual machine instance is created in your project during image export. Image export tooling on this temporary instance must be @@ -66,8 +89,8 @@ OPTIONAL FLAGS export on the temporary instance uses the project's default Compute Engine service account. - At minimum, the specified Compute Engine service account needs to have - the following roles assigned: + At a minimum, you need to grant the following roles to the specified + Cloud Build service account: ◆ roles/compute.storageAdmin ◆ roles/storage.objectAdmin diff --git a/gcloud/beta/compute/images/import b/gcloud/beta/compute/images/import index 109491719..de9a1913b 100644 --- a/gcloud/beta/compute/images/import +++ b/gcloud/beta/compute/images/import @@ -10,6 +10,7 @@ SYNOPSIS (--aws-source-ami-file-path=AWS_SOURCE_AMI_FILE_PATH | --aws-ami-export-location=AWS_AMI_EXPORT_LOCATION --aws-ami-id=AWS_AMI_ID)) [--no-address] [--async] + [--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--description=DESCRIPTION] [--family=FAMILY] [--no-guest-environment] [--guest-os-features=[GUEST_OS_FEATURE,...]] @@ -145,6 +146,28 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT + Image import amd export tools use Cloud Build to import and export + images to and from your project. Cloud Build uses a specific service + account to execute builds on your behalf. The Cloud Build service + account generates access token for other service accounts and it is + also used for authentication when building the artifacts for the image + import tool. + + Use this flag to to specify a custom Cloud Build service account for + image import and export. If you don't specify this flag, Cloud Build + runs using your project's default Cloud Build service account. To set + this option, specify the email address corresponding to the required + Cloud Build service account. Note: You must specify the --logs-location + flag when you set the custom Cloud Build service account. + + At minimum, the specified Cloud Build service account needs to have the + following roles assigned: + + ◆ roles/compute.admin + ◆ roles/iam.serviceAccountTokenCreator + ◆ roles/iam.serviceAccountUser + --compute-service-account=COMPUTE_SERVICE_ACCOUNT A temporary virtual machine instance is created in your project during image import. Image import tooling on this temporary instance must be @@ -160,8 +183,8 @@ OPTIONAL FLAGS import on the temporary instance uses the project's default Compute Engine service account. - At minimum, the specified Compute Engine service account needs to have - the following roles assigned: + At a minimum, you need to grant the following roles to the specified + Cloud Build service account: ◆ roles/compute.storageAdmin ◆ roles/storage.objectViewer diff --git a/gcloud/beta/compute/instances/import b/gcloud/beta/compute/instances/import index 4f70ecc8f..5c8f03e82 100644 --- a/gcloud/beta/compute/instances/import +++ b/gcloud/beta/compute/instances/import @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta compute instances import INSTANCE_NAME --source-uri=SOURCE_URI [--no-address] [--async] [--byol] [--can-ip-forward] + [--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--deletion-protection] [--description=DESCRIPTION] [--no-guest-environment] [--guest-os-features=[GUEST_OS_FEATURE,...]] @@ -89,6 +90,28 @@ OPTIONAL FLAGS If provided, allows the instances to send and receive packets with non-matching destination or source IP addresses. + --cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT + Image import amd export tools use Cloud Build to import and export + images to and from your project. Cloud Build uses a specific service + account to execute builds on your behalf. The Cloud Build service + account generates access token for other service accounts and it is + also used for authentication when building the artifacts for the image + import tool. + + Use this flag to to specify a custom Cloud Build service account for + image import and export. If you don't specify this flag, Cloud Build + runs using your project's default Cloud Build service account. To set + this option, specify the email address corresponding to the required + Cloud Build service account. Note: You must specify the --logs-location + flag when you set the custom Cloud Build service account. + + At minimum, the specified Cloud Build service account needs to have the + following roles assigned: + + ◆ roles/compute.admin + ◆ roles/iam.serviceAccountTokenCreator + ◆ roles/iam.serviceAccountUser + --compute-service-account=COMPUTE_SERVICE_ACCOUNT A temporary virtual machine instance is created in your project during instance import. Instance import tooling on this temporary instance @@ -104,8 +127,8 @@ OPTIONAL FLAGS import on the temporary instance uses the project's default Compute Engine service account. - At minimum, the specified Compute Engine service account needs to have - the following roles assigned: + At a minimum, you need to grant the following roles to the specified + Cloud Build service account: ◆ roles/compute.storageAdmin ◆ roles/storage.objectViewer diff --git a/gcloud/beta/compute/machine-images/import b/gcloud/beta/compute/machine-images/import index 369aad37f..3552b418f 100644 --- a/gcloud/beta/compute/machine-images/import +++ b/gcloud/beta/compute/machine-images/import @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta compute machine-images import IMAGE --source-uri=SOURCE_URI [--no-address] [--async] [--byol] [--can-ip-forward] + [--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--description=DESCRIPTION] [--no-guest-environment] [--guest-flush] [--guest-os-features=[GUEST_OS_FEATURE,...]] [--labels=[KEY=VALUE,...]] @@ -88,6 +89,28 @@ OPTIONAL FLAGS send and receive packets with non-matching destination or source IP addresses. + --cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT + Image import amd export tools use Cloud Build to import and export + images to and from your project. Cloud Build uses a specific service + account to execute builds on your behalf. The Cloud Build service + account generates access token for other service accounts and it is + also used for authentication when building the artifacts for the image + import tool. + + Use this flag to to specify a custom Cloud Build service account for + image import and export. If you don't specify this flag, Cloud Build + runs using your project's default Cloud Build service account. To set + this option, specify the email address corresponding to the required + Cloud Build service account. Note: You must specify the --logs-location + flag when you set the custom Cloud Build service account. + + At minimum, the specified Cloud Build service account needs to have the + following roles assigned: + + ◆ roles/compute.admin + ◆ roles/iam.serviceAccountTokenCreator + ◆ roles/iam.serviceAccountUser + --compute-service-account=COMPUTE_SERVICE_ACCOUNT A temporary virtual machine instance is created in your project during machine image import. Machine image import tooling on this temporary @@ -103,8 +126,8 @@ OPTIONAL FLAGS image import on the temporary instance uses the project's default Compute Engine service account. - At minimum, the specified Compute Engine service account needs to have - the following roles assigned: + At a minimum, you need to grant the following roles to the specified + Cloud Build service account: ◆ roles/compute.storageAdmin ◆ roles/storage.objectViewer diff --git a/gcloud/beta/compute/snapshot-settings/describe b/gcloud/beta/compute/snapshot-settings/describe new file mode 100644 index 000000000..01af10009 --- /dev/null +++ b/gcloud/beta/compute/snapshot-settings/describe @@ -0,0 +1,32 @@ +NAME + gcloud beta compute snapshot-settings describe - describe snapshot settings + +SYNOPSIS + gcloud beta compute snapshot-settings describe [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe the snapshot settings of a project. + +EXAMPLES + To display the snapshot settings of a project called my-project, run: + + $ gcloud beta compute snapshot-settings describe --project=my-project + +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 snapshot-settings describe + diff --git a/gcloud/beta/compute/snapshot-settings/help b/gcloud/beta/compute/snapshot-settings/help new file mode 100644 index 000000000..a0a41e258 --- /dev/null +++ b/gcloud/beta/compute/snapshot-settings/help @@ -0,0 +1,30 @@ +NAME + gcloud beta compute snapshot-settings - describe and update Compute Engine + snapshot settings + +SYNOPSIS + gcloud beta compute snapshot-settings COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe and update Compute Engine snapshot settings. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describe snapshot settings. + + update + (BETA) Update snapshot settings. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute snapshot-settings + diff --git a/gcloud/beta/compute/snapshot-settings/update b/gcloud/beta/compute/snapshot-settings/update new file mode 100644 index 000000000..e10a75b57 --- /dev/null +++ b/gcloud/beta/compute/snapshot-settings/update @@ -0,0 +1,68 @@ +NAME + gcloud beta compute snapshot-settings update - update snapshot settings + +SYNOPSIS + gcloud beta compute snapshot-settings update [--async] + [--storage-location-names=[STORAGE_LOCATION_NAMES,...]] + [--storage-location-policy=STORAGE_LOCATION_POLICY] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the snapshot settings of a project. + +EXAMPLES + To update the snapshot settings and set the storage location policy to the + nearest multi-region as the source disk, run: + + $ gcloud beta compute snapshot-settings update \ + --storage-location-policy=nearest-multi-region + + To update the snapshot settings and set the storage location policy to the + same region as the source disk, run: + + $ gcloud alpha compute snapshot-settings update \ --storage-location-policy=local-region + + To update the snapshot settings and set the storage location policy to + store snapshots in a specific location like us-west1, run: + + $ gcloud beta compute snapshot-settings update \ + --storage-location-policy=specific-locations \ + --storage-location-names=us-west1 + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --storage-location-names=[STORAGE_LOCATION_NAMES,...] + The custom storage locations that you specify for the project's + snapshots. Use this flag only when you use the SPECIFIC_LOCATIONS value + for the --storage-location-policy flag. For more information, refer to + the snapshot settings documentation at + https://cloud.google.com/compute/docs/disks/snapshot-settings. + + --storage-location-policy=STORAGE_LOCATION_POLICY + The storage location policy. For more information, refer to the + snapshot settings documentation at + https://cloud.google.com/compute/docs/disks/snapshot-settings. + STORAGE_LOCATION_POLICY must be one of: local-region, + nearest-multi-region, specific-locations. + +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 snapshot-settings update + diff --git a/gcloud/beta/deploy/delivery-pipelines/help b/gcloud/beta/deploy/delivery-pipelines/help index e033af08b..2087ef46c 100644 --- a/gcloud/beta/deploy/delivery-pipelines/help +++ b/gcloud/beta/deploy/delivery-pipelines/help @@ -1,13 +1,12 @@ NAME gcloud beta deploy delivery-pipelines - create and manage Delivery Pipeline - resources for Google Cloud Deploy + resources for Cloud Deploy SYNOPSIS gcloud beta deploy delivery-pipelines COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create and manage Delivery Pipeline resources for Google Cloud - Deploy. + (BETA) Create and manage Delivery Pipeline resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/deploy/help b/gcloud/beta/deploy/help index dcd5e6706..d7026c384 100644 --- a/gcloud/beta/deploy/help +++ b/gcloud/beta/deploy/help @@ -1,11 +1,11 @@ NAME - gcloud beta deploy - create and manage Google Cloud Deploy resources + gcloud beta deploy - create and manage Cloud Deploy resources SYNOPSIS gcloud beta deploy GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create and manage Google Cloud Deploy resources. + (BETA) Create and manage Cloud Deploy resources. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -16,20 +16,19 @@ GROUPS GROUP is one of the following: delivery-pipelines - (BETA) Create and manage Delivery Pipeline resources for Google Cloud - Deploy. + (BETA) Create and manage Delivery Pipeline resources for Cloud Deploy. job-runs - (BETA) Manages job runs resources for Google Cloud Deploy. + (BETA) Manages job runs resources for Cloud Deploy. releases - (BETA) Create and manage Release resources for Google Cloud Deploy. + (BETA) Create and manage Release resources for Cloud Deploy. rollouts - (BETA) Create and manage Rollout resources for Google Cloud Deploy. + (BETA) Create and manage Rollout resources for Cloud Deploy. targets - (BETA) Create and manage Target resources for Google Cloud Deploy. + (BETA) Create and manage Target resources for Cloud Deploy. COMMANDS COMMAND is one of the following: diff --git a/gcloud/beta/deploy/job-runs/help b/gcloud/beta/deploy/job-runs/help index 617c9a59c..dfe3ca41c 100644 --- a/gcloud/beta/deploy/job-runs/help +++ b/gcloud/beta/deploy/job-runs/help @@ -1,12 +1,11 @@ NAME - gcloud beta deploy job-runs - manages job runs resources for Google Cloud - Deploy + gcloud beta deploy job-runs - manages job runs resources for Cloud Deploy SYNOPSIS gcloud beta deploy job-runs COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Manages job runs resources for Google Cloud Deploy. + (BETA) Manages job runs resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/deploy/releases/help b/gcloud/beta/deploy/releases/help index b7df18d02..0bd1913f6 100644 --- a/gcloud/beta/deploy/releases/help +++ b/gcloud/beta/deploy/releases/help @@ -1,12 +1,12 @@ NAME - gcloud beta deploy releases - create and manage Release resources for - Google Cloud Deploy + gcloud beta deploy releases - create and manage Release resources for Cloud + Deploy SYNOPSIS gcloud beta deploy releases COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create and manage Release resources for Google Cloud Deploy. + (BETA) Create and manage Release resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/deploy/rollouts/help b/gcloud/beta/deploy/rollouts/help index fd8ce4f26..939b24020 100644 --- a/gcloud/beta/deploy/rollouts/help +++ b/gcloud/beta/deploy/rollouts/help @@ -1,12 +1,12 @@ NAME - gcloud beta deploy rollouts - create and manage Rollout resources for - Google Cloud Deploy + gcloud beta deploy rollouts - create and manage Rollout resources for Cloud + Deploy SYNOPSIS gcloud beta deploy rollouts COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create and manage Rollout resources for Google Cloud Deploy. + (BETA) Create and manage Rollout resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/deploy/targets/help b/gcloud/beta/deploy/targets/help index debd90e84..8ba45369c 100644 --- a/gcloud/beta/deploy/targets/help +++ b/gcloud/beta/deploy/targets/help @@ -1,12 +1,12 @@ NAME - gcloud beta deploy targets - create and manage Target resources for Google - Cloud Deploy + gcloud beta deploy targets - create and manage Target resources for Cloud + Deploy SYNOPSIS gcloud beta deploy targets COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create and manage Target resources for Google Cloud Deploy. + (BETA) Create and manage Target resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/monitoring/metrics-scopes/create b/gcloud/beta/monitoring/metrics-scopes/create index 4bec834b8..1799bb64a 100644 --- a/gcloud/beta/monitoring/metrics-scopes/create +++ b/gcloud/beta/monitoring/metrics-scopes/create @@ -3,8 +3,8 @@ NAME in a metrics scope SYNOPSIS - gcloud beta monitoring metrics-scopes create MONITORED_PROJECT_ID_OR_NUMBER - [GCLOUD_WIDE_FLAG ...] + gcloud beta monitoring metrics-scopes create + MONITORED_RESOURCE_CONTAINER_NAME [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -21,20 +21,22 @@ EXAMPLES monitored-project-1 to a metrics scope with project id metrics-scope-1 assuming the metrics-scope-1 is the default project: - $ gcloud beta monitoring metrics-scopes create monitored-project-1 + $ gcloud beta monitoring metrics-scopes create \ + projects/monitored-project-1 The following command adds a monitored project with the ID monitored-project-1 to a metrics scope with project id metrics-scope-1: - $ gcloud beta monitoring metrics-scopes create monitored-project-1 \ - --project=metrics-scope-1 + $ gcloud beta monitoring metrics-scopes create \ + projects/monitored-project-1 --project=metrics-scope-1 $ gcloud beta monitoring metrics-scopes create \ locations/global/metricsScopes/metrics-scope-1/projects/\ monitored-project-1 POSITIONAL ARGUMENTS - MONITORED_PROJECT_ID_OR_NUMBER - Monitored project ID or number for the project you want to create. + MONITORED_RESOURCE_CONTAINER_NAME + Monitored resource container (example - projects/PROJECT_ID) project + you want to create. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/monitoring/metrics-scopes/delete b/gcloud/beta/monitoring/metrics-scopes/delete index 22badb43c..71a765a5f 100644 --- a/gcloud/beta/monitoring/metrics-scopes/delete +++ b/gcloud/beta/monitoring/metrics-scopes/delete @@ -3,8 +3,8 @@ NAME in a metrics scope SYNOPSIS - gcloud beta monitoring metrics-scopes delete MONITORED_PROJECT_ID_OR_NUMBER - [GCLOUD_WIDE_FLAG ...] + gcloud beta monitoring metrics-scopes delete + MONITORED_RESOURCE_CONTAINER_NAME [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -20,20 +20,22 @@ EXAMPLES monitored-project-1 to a metrics scope with project id metrics-scope-1 assuming the metrics-scope-1 is the default project: - $ gcloud beta monitoring metrics-scopes delete monitored-project-1 + $ gcloud beta monitoring metrics-scopes delete \ + projects/monitored-project-1 The following command adds a monitored project with the ID monitored-project-1 to a metrics scope with project id metrics-scope-1: - $ gcloud beta monitoring metrics-scopes delete monitored-project-1 \ - --project=metrics-scope-1 + $ gcloud beta monitoring metrics-scopes delete \ + projects/monitored-project-1 --project=metrics-scope-1 $ gcloud beta monitoring metrics-scopes delete \ locations/global/metricsScopes/metrics-scope-1/projects/\ monitored-project-1 POSITIONAL ARGUMENTS - MONITORED_PROJECT_ID_OR_NUMBER - Monitored project ID or number for the project you want to delete. + MONITORED_RESOURCE_CONTAINER_NAME + Monitored resource container (example - projects/PROJECT_ID) project + you want to delete. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/monitoring/metrics-scopes/help b/gcloud/beta/monitoring/metrics-scopes/help index 9e174c2cd..1852b39fe 100644 --- a/gcloud/beta/monitoring/metrics-scopes/help +++ b/gcloud/beta/monitoring/metrics-scopes/help @@ -30,7 +30,8 @@ COMMANDS (BETA) Describe a Cloud Monitoring metrics scope. list - (BETA) List the metrics scopes monitoring the specified project. + (BETA) List the metrics scopes monitoring the specified monitored + resource container. NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/monitoring/metrics-scopes/list b/gcloud/beta/monitoring/metrics-scopes/list index d4f459098..87a8abb3d 100644 --- a/gcloud/beta/monitoring/metrics-scopes/list +++ b/gcloud/beta/monitoring/metrics-scopes/list @@ -1,11 +1,12 @@ NAME gcloud beta monitoring metrics-scopes list - list the metrics scopes - monitoring the specified project + monitoring the specified monitored resource container SYNOPSIS - gcloud beta monitoring metrics-scopes list PROJECT_ID_OR_NUMBER - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + gcloud beta monitoring metrics-scopes list + MONITORED_RESOURCE_CONTAINER_NAME [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -19,11 +20,12 @@ DESCRIPTION EXAMPLES To list the metrics scopes monitoring MY-PROJECT-ID - $ gcloud beta monitoring metrics-scopes list MY-PROJECT-ID + $ gcloud beta monitoring metrics-scopes list projects/MY-PROJECT-ID POSITIONAL ARGUMENTS - PROJECT_ID_OR_NUMBER - ID or number for the project you want to list. + MONITORED_RESOURCE_CONTAINER_NAME + Monitored resource container (example - projects/PROJECT_ID) project + you want to list. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/netapp/storage-pools/create b/gcloud/beta/netapp/storage-pools/create index 17106d6e1..4c2cadbc7 100644 --- a/gcloud/beta/netapp/storage-pools/create +++ b/gcloud/beta/netapp/storage-pools/create @@ -91,6 +91,10 @@ REQUIRED FLAGS Premium Service Level for Cloud NetApp Storage Pool. The Premium Service Level has a throughput per TiB of allocated volume size of 64 MiB/s. + standard + Standard Service Level for Cloud NetApp Storage Pool. The Standard + Service Level has a throughput per TiB of allocated volume size of + 128 MiB/s. OPTIONAL FLAGS Active directory resource - The Active Directory to attach to the Storage diff --git a/gcloud/beta/network-security/server-tls-policies/describe b/gcloud/beta/network-security/server-tls-policies/describe index 9acce2ade..b1467b7fa 100644 --- a/gcloud/beta/network-security/server-tls-policies/describe +++ b/gcloud/beta/network-security/server-tls-policies/describe @@ -60,8 +60,10 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud network-security server-tls-policies describe $ gcloud alpha network-security server-tls-policies describe diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 3c53cabd5..56f8a88eb 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -427,19 +427,27 @@ FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. + Specify which of the outbound traffic to send through Direct VPC + egress or the VPC connector for this resource. This resource must + have Direct VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC - connector. Provides the same functionality as 'all-traffic'. - Prefer to use 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + (RFC 1918 and Private Google Access IPs) through Direct VPC + egress or the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. These flags modify the Cloud SQL instances this Service connects to. You can specify a name of a Cloud SQL instance if it's in the same project diff --git a/gcloud/beta/run/jobs/create b/gcloud/beta/run/jobs/create index ebd517fb6..f8fec4713 100644 --- a/gcloud/beta/run/jobs/create +++ b/gcloud/beta/run/jobs/create @@ -142,19 +142,27 @@ OPTIONAL FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. - VPC_EGRESS must be one of: + Specify which of the outbound traffic to send through Direct VPC egress + or the VPC connector for this resource. This resource must have Direct + VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must + be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC connector. - Provides the same functionality as 'all-traffic'. Prefer to use - 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only - Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + Default option. Sends outbound traffic to private IP addresses (RFC + 1918 and Private Google Access IPs) through Direct VPC egress or + the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. At most one of these can be specified: diff --git a/gcloud/beta/run/jobs/deploy b/gcloud/beta/run/jobs/deploy index 1649abe58..2a65be9dc 100644 --- a/gcloud/beta/run/jobs/deploy +++ b/gcloud/beta/run/jobs/deploy @@ -141,19 +141,27 @@ FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. - VPC_EGRESS must be one of: + Specify which of the outbound traffic to send through Direct VPC egress + or the VPC connector for this resource. This resource must have Direct + VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must + be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC connector. - Provides the same functionality as 'all-traffic'. Prefer to use - 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only - Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + Default option. Sends outbound traffic to private IP addresses (RFC + 1918 and Private Google Access IPs) through Direct VPC egress or + the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. At most one of these can be specified: diff --git a/gcloud/beta/run/jobs/update b/gcloud/beta/run/jobs/update index 24cff2ded..ded41616c 100644 --- a/gcloud/beta/run/jobs/update +++ b/gcloud/beta/run/jobs/update @@ -131,19 +131,27 @@ FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. - VPC_EGRESS must be one of: + Specify which of the outbound traffic to send through Direct VPC egress + or the VPC connector for this resource. This resource must have Direct + VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must + be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC connector. - Provides the same functionality as 'all-traffic'. Prefer to use - 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only - Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + Default option. Sends outbound traffic to private IP addresses (RFC + 1918 and Private Google Access IPs) through Direct VPC egress or + the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. These flags modify the Cloud SQL instances this Service connects to. You can specify a name of a Cloud SQL instance if it's in the same project and diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 8c1f71108..87ea0aa1e 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -256,19 +256,27 @@ FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. + Specify which of the outbound traffic to send through Direct VPC + egress or the VPC connector for this resource. This resource must + have Direct VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC - connector. Provides the same functionality as 'all-traffic'. - Prefer to use 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + (RFC 1918 and Private Google Access IPs) through Direct VPC + egress or the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. These flags modify the Cloud SQL instances this Service connects to. You can specify a name of a Cloud SQL instance if it's in the same project diff --git a/gcloud/billing/budgets/create b/gcloud/billing/budgets/create index ed26b0b07..7a2a1c074 100644 --- a/gcloud/billing/budgets/create +++ b/gcloud/billing/budgets/create @@ -10,6 +10,7 @@ SYNOPSIS [--filter-credit-types=[FILTER_CREDIT_TYPES,...]] [--filter-labels=[KEY=VALUE,...]] [--filter-projects=[FILTER_PROJECTS,...]] + [--filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...]] [--filter-services=[FILTER_SERVICES,...]] [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]] [--notifications-rule-monitoring-notification-channels=[NOTIFICATIONS_RULE_MONITORING_NOTIFICATION_CHANNELS, @@ -95,6 +96,15 @@ OPTIONAL FLAGS usage from only this set of projects should be included in the budget. If omitted, all projects will be included. + --filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...] + A set of folder and organization names of the form folders/{folderId} + or organizations/{organizationId}, specifying that usage from only this + set of folders and organizations should be included in the budget. If + omitted, the budget includes all usage that the billing account pays + for. If the folder or organization contains projects that are paid for + by a different Cloud Billing account, the budget doesn't apply to those + projects. + --filter-services=[FILTER_SERVICES,...] Set of services of the form services/{service_id}, specifying that usage from only this set of services should be included in the budget. diff --git a/gcloud/billing/budgets/update b/gcloud/billing/budgets/update index af3bb3780..704240ff6 100644 --- a/gcloud/billing/budgets/update +++ b/gcloud/billing/budgets/update @@ -8,6 +8,7 @@ SYNOPSIS [--filter-credit-types=[FILTER_CREDIT_TYPES,...]] [--filter-labels=[KEY=VALUE,...]] [--filter-projects=[FILTER_PROJECTS,...]] + [--filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...]] [--filter-services=[FILTER_SERVICES,...]] [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]] [--notifications-rule-monitoring-notification-channels=[NOTIFICATIONS_RULE_MONITORING_NOTIFICATION_CHANNELS, @@ -95,6 +96,15 @@ FLAGS usage from only this set of projects should be included in the budget. If omitted, all projects will be included. + --filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...] + A set of folder and organization names of the form folders/{folderId} + or organizations/{organizationId}, specifying that usage from only this + set of folders and organizations should be included in the budget. If + omitted, the budget includes all usage that the billing account pays + for. If the folder or organization contains projects that are paid for + by a different Cloud Billing account, the budget doesn't apply to those + projects. + --filter-services=[FILTER_SERVICES,...] Set of services of the form services/{service_id}, specifying that usage from only this set of services should be included in the budget. diff --git a/gcloud/certificate-manager/help b/gcloud/certificate-manager/help index 7ee7f0919..2ac05eab1 100644 --- a/gcloud/certificate-manager/help +++ b/gcloud/certificate-manager/help @@ -31,6 +31,9 @@ GROUPS operations Manage Certificate Manager operations. + trust-configs + Manage Certificate Manager trust configs. + NOTES These variants are also available: diff --git a/gcloud/certificate-manager/trust-configs/delete b/gcloud/certificate-manager/trust-configs/delete new file mode 100644 index 000000000..239b50070 --- /dev/null +++ b/gcloud/certificate-manager/trust-configs/delete @@ -0,0 +1,78 @@ +NAME + gcloud certificate-manager trust-configs delete - delete TrustConfig + +SYNOPSIS + gcloud certificate-manager trust-configs delete + (TRUST_CONFIG : --location=LOCATION) [--async] [--etag=ETAG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete the specified TrustConfig. + +EXAMPLES + To delete a TrustConfig called 'my-trust-config', run: + + $ gcloud certificate-manager trust-configs delete my-trust-config \ + --location=global + +POSITIONAL ARGUMENTS + TrustConfig resource - Name of the TrustConfig 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 trust_config on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + TRUST_CONFIG + ID of the trustConfig or fully qualified identifier for the + trustConfig. + + To set the trust_config attribute: + ▸ provide the argument trust_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Certificate Manager location. + + To set the location attribute: + ▸ provide the argument trust_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ default value of location is [global]. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --etag=ETAG + The current etag of the asset. If an etag is provided and does not + match the current etag of the asset, the deletion will be blocked. + +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 certificatemanager/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/certificate-manager + +NOTES + These variants are also available: + + $ gcloud alpha certificate-manager trust-configs delete + + $ gcloud beta certificate-manager trust-configs delete + diff --git a/gcloud/certificate-manager/trust-configs/describe b/gcloud/certificate-manager/trust-configs/describe new file mode 100644 index 000000000..5e572ca6c --- /dev/null +++ b/gcloud/certificate-manager/trust-configs/describe @@ -0,0 +1,68 @@ +NAME + gcloud certificate-manager trust-configs describe - show details about a + TrustConfig + +SYNOPSIS + gcloud certificate-manager trust-configs describe + (TRUST_CONFIG : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details about a TrustConfig. + +EXAMPLES + To show details about an existing trust config, run: + + $ gcloud certificate-manager trust-configs describe my-trust-config + +POSITIONAL ARGUMENTS + TrustConfig resource - The TrustConfig 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 trust_config on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + TRUST_CONFIG + ID of the trustConfig or fully qualified identifier for the + trustConfig. + + To set the trust_config attribute: + ▸ provide the argument trust_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Certificate Manager location. + + To set the location attribute: + ▸ provide the argument trust_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ default value of location is [global]. + +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 certificatemanager/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/certificate-manager + +NOTES + These variants are also available: + + $ gcloud alpha certificate-manager trust-configs describe + + $ gcloud beta certificate-manager trust-configs describe + diff --git a/gcloud/certificate-manager/trust-configs/export b/gcloud/certificate-manager/trust-configs/export new file mode 100644 index 000000000..4942bae35 --- /dev/null +++ b/gcloud/certificate-manager/trust-configs/export @@ -0,0 +1,77 @@ +NAME + gcloud certificate-manager trust-configs export - export TrustConfig + +SYNOPSIS + gcloud certificate-manager trust-configs export + (TRUST_CONFIG : --location=LOCATION) [--destination=DESTINATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Export a TrustConfig. + +EXAMPLES + To export a TrustConfig, run: + + $ gcloud certificate-manager trust-configs export my-trust-config \ + --destination=my-trust-config.yaml --location=global + +POSITIONAL ARGUMENTS + TrustConfig resource - Name of the TrustConfig to export. 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 trust_config on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + TRUST_CONFIG + ID of the trustConfig or fully qualified identifier for the + trustConfig. + + To set the trust_config attribute: + ▸ provide the argument trust_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Certificate Manager location. + + To set the location attribute: + ▸ provide the argument trust_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ default value of location is [global]. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. The + exported data will not contain any output-only fields. Alternatively, + you may omit this flag to write to standard output. For a schema + describing the export/import format, see + $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + +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 certificatemanager/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/certificate-manager + +NOTES + These variants are also available: + + $ gcloud alpha certificate-manager trust-configs export + + $ gcloud beta certificate-manager trust-configs export + diff --git a/gcloud/certificate-manager/trust-configs/help b/gcloud/certificate-manager/trust-configs/help new file mode 100644 index 000000000..e9e7234ec --- /dev/null +++ b/gcloud/certificate-manager/trust-configs/help @@ -0,0 +1,40 @@ +NAME + gcloud certificate-manager trust-configs - manage Certificate Manager trust + configs + +SYNOPSIS + gcloud certificate-manager trust-configs COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Certificate Manager trust configs. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + Delete TrustConfig. + + describe + Show details about a TrustConfig. + + export + Export TrustConfig. + + import + Import TrustConfig. + + list + List all TrustConfigs in a project. + +NOTES + These variants are also available: + + $ gcloud alpha certificate-manager trust-configs + + $ gcloud beta certificate-manager trust-configs + diff --git a/gcloud/certificate-manager/trust-configs/import b/gcloud/certificate-manager/trust-configs/import new file mode 100644 index 000000000..3195e07c3 --- /dev/null +++ b/gcloud/certificate-manager/trust-configs/import @@ -0,0 +1,84 @@ +NAME + gcloud certificate-manager trust-configs import - import TrustConfig + +SYNOPSIS + gcloud certificate-manager trust-configs import + (TRUST_CONFIG : --location=LOCATION) [--async] [--source=SOURCE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Import a TrustConfig. + +EXAMPLES + To import a TrustConfig from a YAML file, run: + + $ gcloud certificate-manager trust-configs import my-trust-config \ + --source=my-trust-config.yaml --location=global + +POSITIONAL ARGUMENTS + TrustConfig resource - Name of the TrustConfig to import. 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 trust_config on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + TRUST_CONFIG + ID of the trustConfig or fully qualified identifier for the + trustConfig. + + To set the trust_config attribute: + ▸ provide the argument trust_config on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Certificate Manager location. + + To set the location attribute: + ▸ provide the argument trust_config on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ default value of location is [global]. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --source=SOURCE + Path to a YAML file containing the configuration export data. The YAML + file must not contain any output-only fields. Alternatively, you may + omit this flag to read from standard input. For a schema describing the + export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + + $CLOUDSDKROOT is can be obtained with the following command: + + $ gcloud info --format='value(installation.sdk_root)' + +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 certificatemanager/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/certificate-manager + +NOTES + These variants are also available: + + $ gcloud alpha certificate-manager trust-configs import + + $ gcloud beta certificate-manager trust-configs import + diff --git a/gcloud/certificate-manager/trust-configs/list b/gcloud/certificate-manager/trust-configs/list new file mode 100644 index 000000000..e08e4a5f3 --- /dev/null +++ b/gcloud/certificate-manager/trust-configs/list @@ -0,0 +1,87 @@ +NAME + gcloud certificate-manager trust-configs list - list all TrustConfigs in a + project + +SYNOPSIS + gcloud certificate-manager trust-configs list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List existing TrustConfigs. + +EXAMPLES + To list existing TrustConfigs, run: + + $ gcloud certificate-manager trust-configs list + +FLAGS + Location resource - The location (defaults to global) of the resources. + 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 --location on the command line with a fully + specified name; + ◆ default value of location is [global] with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ default value of location is [global]. + +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 certificatemanager/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/certificate-manager + +NOTES + These variants are also available: + + $ gcloud alpha certificate-manager trust-configs list + + $ gcloud beta certificate-manager trust-configs list + diff --git a/gcloud/composer/environments/update b/gcloud/composer/environments/update index 84a2ad2de..c2eb942ef 100644 --- a/gcloud/composer/environments/update +++ b/gcloud/composer/environments/update @@ -16,6 +16,9 @@ SYNOPSIS --snapshot-creation-schedule=SNAPSHOT_CREATION_SCHEDULE --snapshot-location=SNAPSHOT_LOCATION --snapshot-schedule-timezone=SNAPSHOT_SCHEDULE_TIMEZONE + | --maintenance-window-end=MAINTENANCE_WINDOW_END + --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE + --maintenance-window-start=MAINTENANCE_WINDOW_START | --max-workers=MAX_WORKERS --min-workers=MIN_WORKERS --scheduler-count=SCHEDULER_COUNT --scheduler-cpu=SCHEDULER_CPU --scheduler-memory=SCHEDULER_MEMORY @@ -171,6 +174,37 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + Group of arguments for setting the maintenance window value. + + --maintenance-window-end=MAINTENANCE_WINDOW_END + End time of the mantenance window in the form of the full date. + Only the time of the day is used as a reference for an ending time + of the window with a provided recurrence. Specified date must take + place after the one specified as a start date, the difference + between will be used as a length of a single maintenance window. + See $ gcloud topic datetimes for information on time formats. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE + An RFC 5545 RRULE, specifying how the maintenance window will + recur. The minimum requirement for the length of the maintenance + window is 12 hours a week. Only FREQ=DAILY and FREQ=WEEKLY rules + are supported. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --maintenance-window-start=MAINTENANCE_WINDOW_START + Start time of the mantenance window in the form of the full date. + Only the time of the day is used as a reference for a starting time + of the window with a provided recurrence. See $ gcloud topic + datetimes for information on time formats. + + This flag argument must be specified if any of the other arguments + in this group are specified. + Group of arguments for setting workloads configuration in Composer 2.X or greater (--scheduler-count flag is available for Composer 1.X as well). diff --git a/gcloud/compute/images/export b/gcloud/compute/images/export index 6f23d6557..edd42fe50 100644 --- a/gcloud/compute/images/export +++ b/gcloud/compute/images/export @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud compute images export --destination-uri=DESTINATION_URI (--image=IMAGE | --image-family=IMAGE_FAMILY) [--async] + [--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--export-format=EXPORT_FORMAT] [--image-project=IMAGE_PROJECT] [--log-location=LOG_LOCATION] [--network=NETWORK] [--subnet=SUBNET] @@ -51,6 +52,28 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT + Image import amd export tools use Cloud Build to import and export + images to and from your project. Cloud Build uses a specific service + account to execute builds on your behalf. The Cloud Build service + account generates access token for other service accounts and it is + also used for authentication when building the artifacts for the image + import tool. + + Use this flag to to specify a custom Cloud Build service account for + image import and export. If you don't specify this flag, Cloud Build + runs using your project's default Cloud Build service account. To set + this option, specify the email address corresponding to the required + Cloud Build service account. Note: You must specify the --logs-location + flag when you set the custom Cloud Build service account. + + At minimum, the specified Cloud Build service account needs to have the + following roles assigned: + + ◆ roles/compute.admin + ◆ roles/iam.serviceAccountTokenCreator + ◆ roles/iam.serviceAccountUser + --compute-service-account=COMPUTE_SERVICE_ACCOUNT A temporary virtual machine instance is created in your project during image export. Image export tooling on this temporary instance must be @@ -66,8 +89,8 @@ OPTIONAL FLAGS export on the temporary instance uses the project's default Compute Engine service account. - At minimum, the specified Compute Engine service account needs to have - the following roles assigned: + At a minimum, you need to grant the following roles to the specified + Cloud Build service account: ◆ roles/compute.storageAdmin ◆ roles/storage.objectAdmin diff --git a/gcloud/compute/images/import b/gcloud/compute/images/import index 9429e2a8a..42f49a922 100644 --- a/gcloud/compute/images/import +++ b/gcloud/compute/images/import @@ -10,6 +10,7 @@ SYNOPSIS (--aws-source-ami-file-path=AWS_SOURCE_AMI_FILE_PATH | --aws-ami-export-location=AWS_AMI_EXPORT_LOCATION --aws-ami-id=AWS_AMI_ID)) [--no-address] [--async] + [--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--description=DESCRIPTION] [--family=FAMILY] [--no-guest-environment] [--guest-os-features=[GUEST_OS_FEATURE,...]] @@ -145,6 +146,28 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT + Image import amd export tools use Cloud Build to import and export + images to and from your project. Cloud Build uses a specific service + account to execute builds on your behalf. The Cloud Build service + account generates access token for other service accounts and it is + also used for authentication when building the artifacts for the image + import tool. + + Use this flag to to specify a custom Cloud Build service account for + image import and export. If you don't specify this flag, Cloud Build + runs using your project's default Cloud Build service account. To set + this option, specify the email address corresponding to the required + Cloud Build service account. Note: You must specify the --logs-location + flag when you set the custom Cloud Build service account. + + At minimum, the specified Cloud Build service account needs to have the + following roles assigned: + + ◆ roles/compute.admin + ◆ roles/iam.serviceAccountTokenCreator + ◆ roles/iam.serviceAccountUser + --compute-service-account=COMPUTE_SERVICE_ACCOUNT A temporary virtual machine instance is created in your project during image import. Image import tooling on this temporary instance must be @@ -160,8 +183,8 @@ OPTIONAL FLAGS import on the temporary instance uses the project's default Compute Engine service account. - At minimum, the specified Compute Engine service account needs to have - the following roles assigned: + At a minimum, you need to grant the following roles to the specified + Cloud Build service account: ◆ roles/compute.storageAdmin ◆ roles/storage.objectViewer diff --git a/gcloud/compute/instances/import b/gcloud/compute/instances/import index ab8d68e35..2357caf09 100644 --- a/gcloud/compute/instances/import +++ b/gcloud/compute/instances/import @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud compute instances import INSTANCE_NAME --source-uri=SOURCE_URI [--no-address] [--async] [--byol] [--can-ip-forward] + [--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--deletion-protection] [--description=DESCRIPTION] [--no-guest-environment] [--guest-os-features=[GUEST_OS_FEATURE,...]] @@ -89,6 +90,28 @@ OPTIONAL FLAGS If provided, allows the instances to send and receive packets with non-matching destination or source IP addresses. + --cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT + Image import amd export tools use Cloud Build to import and export + images to and from your project. Cloud Build uses a specific service + account to execute builds on your behalf. The Cloud Build service + account generates access token for other service accounts and it is + also used for authentication when building the artifacts for the image + import tool. + + Use this flag to to specify a custom Cloud Build service account for + image import and export. If you don't specify this flag, Cloud Build + runs using your project's default Cloud Build service account. To set + this option, specify the email address corresponding to the required + Cloud Build service account. Note: You must specify the --logs-location + flag when you set the custom Cloud Build service account. + + At minimum, the specified Cloud Build service account needs to have the + following roles assigned: + + ◆ roles/compute.admin + ◆ roles/iam.serviceAccountTokenCreator + ◆ roles/iam.serviceAccountUser + --compute-service-account=COMPUTE_SERVICE_ACCOUNT A temporary virtual machine instance is created in your project during instance import. Instance import tooling on this temporary instance @@ -104,8 +127,8 @@ OPTIONAL FLAGS import on the temporary instance uses the project's default Compute Engine service account. - At minimum, the specified Compute Engine service account needs to have - the following roles assigned: + At a minimum, you need to grant the following roles to the specified + Cloud Build service account: ◆ roles/compute.storageAdmin ◆ roles/storage.objectViewer diff --git a/gcloud/compute/machine-images/import b/gcloud/compute/machine-images/import index 1b78850b6..e15a98219 100644 --- a/gcloud/compute/machine-images/import +++ b/gcloud/compute/machine-images/import @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud compute machine-images import IMAGE --source-uri=SOURCE_URI [--no-address] [--async] [--byol] [--can-ip-forward] + [--cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--description=DESCRIPTION] [--no-guest-environment] [--guest-flush] [--guest-os-features=[GUEST_OS_FEATURE,...]] [--labels=[KEY=VALUE,...]] @@ -88,6 +89,28 @@ OPTIONAL FLAGS send and receive packets with non-matching destination or source IP addresses. + --cloudbuild-service-account=CLOUDBUILD_SERVICE_ACCOUNT + Image import amd export tools use Cloud Build to import and export + images to and from your project. Cloud Build uses a specific service + account to execute builds on your behalf. The Cloud Build service + account generates access token for other service accounts and it is + also used for authentication when building the artifacts for the image + import tool. + + Use this flag to to specify a custom Cloud Build service account for + image import and export. If you don't specify this flag, Cloud Build + runs using your project's default Cloud Build service account. To set + this option, specify the email address corresponding to the required + Cloud Build service account. Note: You must specify the --logs-location + flag when you set the custom Cloud Build service account. + + At minimum, the specified Cloud Build service account needs to have the + following roles assigned: + + ◆ roles/compute.admin + ◆ roles/iam.serviceAccountTokenCreator + ◆ roles/iam.serviceAccountUser + --compute-service-account=COMPUTE_SERVICE_ACCOUNT A temporary virtual machine instance is created in your project during machine image import. Machine image import tooling on this temporary @@ -103,8 +126,8 @@ OPTIONAL FLAGS image import on the temporary instance uses the project's default Compute Engine service account. - At minimum, the specified Compute Engine service account needs to have - the following roles assigned: + At a minimum, you need to grant the following roles to the specified + Cloud Build service account: ◆ roles/compute.storageAdmin ◆ roles/storage.objectViewer diff --git a/gcloud/container/aws/node-pools/update b/gcloud/container/aws/node-pools/update index 857939085..a55ba0989 100644 --- a/gcloud/container/aws/node-pools/update +++ b/gcloud/container/aws/node-pools/update @@ -7,7 +7,8 @@ SYNOPSIS (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] [--config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN] [--enable-autorepair] [--iam-instance-profile=IAM_INSTANCE_PROFILE] - [--node-version=NODE_VERSION] [--root-volume-iops=ROOT_VOLUME_IOPS] + [--instance-type=INSTANCE_TYPE] [--node-version=NODE_VERSION] + [--root-volume-iops=ROOT_VOLUME_IOPS] [--root-volume-kms-key-arn=ROOT_VOLUME_KMS_KEY_ARN] [--root-volume-size=ROOT_VOLUME_SIZE] [--root-volume-throughput=ROOT_VOLUME_THROUGHPUT] @@ -92,6 +93,9 @@ FLAGS --iam-instance-profile=IAM_INSTANCE_PROFILE Name or ARN of the IAM instance profile associated with the node pool. + --instance-type=INSTANCE_TYPE + AWS EC2 instance type for the node pool's nodes. + --node-version=NODE_VERSION Kubernetes version to use for the node pool. diff --git a/gcloud/dataplex/datascans/create/data-profile b/gcloud/dataplex/datascans/create/data-profile index fb8ea0685..632d55c16 100644 --- a/gcloud/dataplex/datascans/create/data-profile +++ b/gcloud/dataplex/datascans/create/data-profile @@ -24,11 +24,14 @@ DESCRIPTION EXAMPLES To create a data profile scan data-profile-datascan in project test-project - located in us-central1, run: + located in us-central1 on bigquery resource table test-table in dataset + test-dataset, run: $ gcloud dataplex datascans create data-profile \ data-profile-datascan --project=test-project \ - --location=us-central1 + --location=us-central1 \ + --data-source-resource="//bigquery.googleapis.com/projects/test-\ + project/datasets/test-dataset/tables/test-table" POSITIONAL ARGUMENTS Datascan resource - Arguments and flags that define the Dataplex datascan diff --git a/gcloud/dataplex/datascans/create/data-quality b/gcloud/dataplex/datascans/create/data-quality index 197aa0b24..d4c28d252 100644 --- a/gcloud/dataplex/datascans/create/data-quality +++ b/gcloud/dataplex/datascans/create/data-quality @@ -20,11 +20,14 @@ DESCRIPTION EXAMPLES To create a data quality scan data-quality-datascan in project test-project - located in us-central1 with data spec file data-quality-spec.json, run: + located in us-central1 on bigquery resource table test-table in dataset + test-dataset with data spec file data-quality-spec.json, run: $ gcloud dataplex datascans create data-quality \ data-quality-datascan --project=test-project \ --location=us-central1 \ + --data-source-resource="//bigquery.googleapis.com/projects/test-\ + project/datasets/test-dataset/tables/test-table" \ --data-quality-spec-file="data-quality-spec.json" POSITIONAL ARGUMENTS diff --git a/gcloud/deploy/delivery-pipelines/help b/gcloud/deploy/delivery-pipelines/help index 02e9f8149..a00bc5266 100644 --- a/gcloud/deploy/delivery-pipelines/help +++ b/gcloud/deploy/delivery-pipelines/help @@ -1,12 +1,12 @@ NAME gcloud deploy delivery-pipelines - create and manage Delivery Pipeline - resources for Google Cloud Deploy + resources for Cloud Deploy SYNOPSIS gcloud deploy delivery-pipelines COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Create and manage Delivery Pipeline resources for Google Cloud Deploy. + Create and manage Delivery Pipeline resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/deploy/help b/gcloud/deploy/help index 9faf9d6c2..4379bd0dd 100644 --- a/gcloud/deploy/help +++ b/gcloud/deploy/help @@ -1,11 +1,11 @@ NAME - gcloud deploy - create and manage Google Cloud Deploy resources + gcloud deploy - create and manage Cloud Deploy resources SYNOPSIS gcloud deploy GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Create and manage Google Cloud Deploy resources. + Create and manage Cloud Deploy resources. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -16,19 +16,19 @@ GROUPS GROUP is one of the following: delivery-pipelines - Create and manage Delivery Pipeline resources for Google Cloud Deploy. + Create and manage Delivery Pipeline resources for Cloud Deploy. job-runs - Manages job runs resources for Google Cloud Deploy. + Manages job runs resources for Cloud Deploy. releases - Create and manage Release resources for Google Cloud Deploy. + Create and manage Release resources for Cloud Deploy. rollouts - Create and manage Rollout resources for Google Cloud Deploy. + Create and manage Rollout resources for Cloud Deploy. targets - Create and manage Target resources for Google Cloud Deploy. + Create and manage Target resources for Cloud Deploy. COMMANDS COMMAND is one of the following: diff --git a/gcloud/deploy/job-runs/help b/gcloud/deploy/job-runs/help index d2b17274a..503905df6 100644 --- a/gcloud/deploy/job-runs/help +++ b/gcloud/deploy/job-runs/help @@ -1,11 +1,11 @@ NAME - gcloud deploy job-runs - manages job runs resources for Google Cloud Deploy + gcloud deploy job-runs - manages job runs resources for Cloud Deploy SYNOPSIS gcloud deploy job-runs COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Manages job runs resources for Google Cloud Deploy. + Manages job runs resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/deploy/releases/help b/gcloud/deploy/releases/help index 29f8fc21d..7a0c9b5f2 100644 --- a/gcloud/deploy/releases/help +++ b/gcloud/deploy/releases/help @@ -1,12 +1,12 @@ NAME - gcloud deploy releases - create and manage Release resources for Google - Cloud Deploy + gcloud deploy releases - create and manage Release resources for Cloud + Deploy SYNOPSIS gcloud deploy releases COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Create and manage Release resources for Google Cloud Deploy. + Create and manage Release resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/deploy/rollouts/help b/gcloud/deploy/rollouts/help index 2d272a268..fac80107e 100644 --- a/gcloud/deploy/rollouts/help +++ b/gcloud/deploy/rollouts/help @@ -1,12 +1,12 @@ NAME - gcloud deploy rollouts - create and manage Rollout resources for Google - Cloud Deploy + gcloud deploy rollouts - create and manage Rollout resources for Cloud + Deploy SYNOPSIS gcloud deploy rollouts COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Create and manage Rollout resources for Google Cloud Deploy. + Create and manage Rollout resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/deploy/targets/help b/gcloud/deploy/targets/help index 4c06f32b5..a8824320f 100644 --- a/gcloud/deploy/targets/help +++ b/gcloud/deploy/targets/help @@ -1,12 +1,11 @@ NAME - gcloud deploy targets - create and manage Target resources for Google Cloud - Deploy + gcloud deploy targets - create and manage Target resources for Cloud Deploy SYNOPSIS gcloud deploy targets COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Create and manage Target resources for Google Cloud Deploy. + Create and manage Target resources for Cloud Deploy. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/edge-cloud/container/clusters/create b/gcloud/edge-cloud/container/clusters/create index 5885ee27d..47fe3f181 100644 --- a/gcloud/edge-cloud/container/clusters/create +++ b/gcloud/edge-cloud/container/clusters/create @@ -6,13 +6,21 @@ SYNOPSIS gcloud edge-cloud container clusters create (CLUSTER : --location=LOCATION) [--admin-users=ADMIN_USERS] [--async] [--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR; default="10.0.0.0/17"] + [--control-plane-machine-filter=CONTROL_PLANE_MACHINE_FILTER] + [--control-plane-node-count=CONTROL_PLANE_NODE_COUNT] + [--control-plane-node-location=CONTROL_PLANE_NODE_LOCATION] + [--control-plane-shared-deployment-policy=CONTROL_PLANE_SHARED_DEPLOYMENT_POLICY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] + [--external-lb-ipv4-address-pools=[EXTERNAL_LB_IPV4_ADDRESS,...]] [--fleet-project=FLEET_PROJECT] [--labels=[KEY=VALUE,...]] [--lro-timeout=LRO_TIMEOUT] [--maintenance-window-end=MAINTENANCE_WINDOW_END] [--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE] [--maintenance-window-start=MAINTENANCE_WINDOW_START] + [--release-channel=RELEASE_CHANNEL; + default="RELEASE_CHANNEL_UNSPECIFIED"] [--services-ipv4-cidr=SERVICES_IPV4_CIDR; default="10.96.0.0/12"] + [--system-addons-config=SYSTEM_ADDONS_CONFIG] [--version=VERSION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -70,9 +78,43 @@ FLAGS All pods in the cluster are assigned an RFC1918 IPv4 address from this block. This field cannot be changed after creation. + --control-plane-machine-filter=CONTROL_PLANE_MACHINE_FILTER + Only machines matching this filter will be allowed to host local + control plane nodes. The filtering language accepts strings like + "name=", and is documented here: AIP-160 + (https://google.aip.dev/160). + + --control-plane-node-count=CONTROL_PLANE_NODE_COUNT + The number of local control plane nodes in a cluster. Use one to create + a single-node control plane or use three to create a high availability + control plane. Any other numbers of nodes will not be accepted. + + --control-plane-node-location=CONTROL_PLANE_NODE_LOCATION + Google Edge Cloud zone where the local control plane nodes will be + created. + + --control-plane-shared-deployment-policy=CONTROL_PLANE_SHARED_DEPLOYMENT_POLICY + Policy configuration about how user application is deployed for local + control plane cluster. It supports two values, ALLOWED and DISALLOWED. + ALLOWED means that user application can be deployed on control plane + nodes. DISALLOWED means that user application can not be deployed on + control plane nodes. Instead, it can only be deployed on worker nodes. + By default, this value is DISALLOWED. The input is case insensitive. + --default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE The default maximum number of pods per node. + --external-lb-ipv4-address-pools=[EXTERNAL_LB_IPV4_ADDRESS,...] + IPv4 address pools that are used for data plane load balancing of local + control plane clusters. Existing pools cannot be updated after cluster + creation; only adding new pools is allowed. Each address pool must be + specified as one of the following two types of values: 1. A IPv4 + address range, for example, "10.0.0.1-10.0.0.10". A range that contains + a single IP (e.g. "10.0.0.1-10.0.0.1") is allowed. 2. A IPv4 CIDR + block, for example, "10.0.0.1/24" Use comma when specifying multiple + address pools, for example: --external-lb-ipv4-address-pools + 10.0.0.1-10.0.0.10,10.0.0.1/24 + --fleet-project=FLEET_PROJECT Name of the Fleet host project where the cluster is registered. @@ -102,10 +144,31 @@ FLAGS (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + --release-channel=RELEASE_CHANNEL; default="RELEASE_CHANNEL_UNSPECIFIED" + Release channel a cluster is subscribed to. It supports two values, + NONE and REGULAR. NONE is used to opt out of any release channel. + Clusters subscribed to the REGULAR channel will be automatically + upgraded to versions that are considered GA quality, and cannot be + manually upgraded. Additionally, if the REGULAR channel is used, a + specific target version cannot be set with the 'version' flag. If left + unspecified, the release channel will default to REGULAR. + --services-ipv4-cidr=SERVICES_IPV4_CIDR; default="10.96.0.0/12" All services in the cluster are assigned an RFC1918 IPv4 address from this block. This field cannot be changed after creation. + --system-addons-config=SYSTEM_ADDONS_CONFIG + If specified as a YAML/JSON file, customized configuration in this file + will be applied to the system add-ons. + + For example, + + { "systemAddonsConfig": { "ingress": { "disabled": true, "ipv4_vip": + "10.0.0.1" } } } + + --version=VERSION + Target cluster version. For example: "1.5.0". + 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/filestore/instances/create b/gcloud/filestore/instances/create index 8af37e161..fb7e10cc7 100644 --- a/gcloud/filestore/instances/create +++ b/gcloud/filestore/instances/create @@ -100,6 +100,8 @@ REQUIRED FLAGS capacities for each tier are as follows: ▸ BASIC_HDD: 1TB-63.9TB in 1GB increments or its multiples. ▸ BASIC_SSD: 2.5TB-63.9TB in 1GB increments or its multiples. + ▸ HIGH_SCALE_SSD: 10TB-100TB in 2.5TB increments or its + multiples. ▸ ENTERPRISE: 1TB-10TB in 256GB increments or its multiples. name diff --git a/gcloud/filestore/instances/update b/gcloud/filestore/instances/update index 0cea41792..2027c0b3d 100644 --- a/gcloud/filestore/instances/update +++ b/gcloud/filestore/instances/update @@ -146,6 +146,7 @@ FLAGS capacities for each tier are as follows: ▸ BASIC_HDD: 1TB-63.9TB in 1GB increments or its multiples. ▸ BASIC_SSD: 2.5TB-63.9TB in 1GB increments or its multiples. + ▸ HIGH_SCALE_SSD: 10TB-100TB in 2.5TB increments or its multiples. ▸ ENTERPRISE: 1TB-10TB in 256GB increments or its multiples. name diff --git a/gcloud/network-security/server-tls-policies/describe b/gcloud/network-security/server-tls-policies/describe new file mode 100644 index 000000000..3be07a14b --- /dev/null +++ b/gcloud/network-security/server-tls-policies/describe @@ -0,0 +1,68 @@ +NAME + gcloud network-security server-tls-policies describe - describe + ServerTlsPolicy + +SYNOPSIS + gcloud network-security server-tls-policies describe + (SERVER_TLS_POLICY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe the specified ServerTlsPolicy. + +EXAMPLES + To describe a ServerTlsPolicy called 'my-server-tls-policy', run: + + $ gcloud network-security server-tls-policies describe \ + my-server-tls-policy --location=global + +POSITIONAL ARGUMENTS + Server TLS policy resource - The ServerTlsPolicy 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 server_tls_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVER_TLS_POLICY + ID of the server TLS policy or fully qualified identifier for the + server TLS policy. + + To set the server_tls_policy attribute: + ▸ provide the argument server_tls_policy 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 Id. + + To set the location attribute: + ▸ provide the argument server_tls_policy on the command line with a + fully specified name; + ▸ provide the argument --location 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 networksecurity/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + These variants are also available: + + $ gcloud alpha network-security server-tls-policies describe + + $ gcloud beta network-security server-tls-policies describe + diff --git a/gcloud/network-security/server-tls-policies/help b/gcloud/network-security/server-tls-policies/help index 17f8aef22..a9587933f 100644 --- a/gcloud/network-security/server-tls-policies/help +++ b/gcloud/network-security/server-tls-policies/help @@ -19,6 +19,9 @@ COMMANDS delete Delete ServerTlsPolicy. + describe + Describe ServerTlsPolicy. + export Export ServerTlsPolicy. diff --git a/gcloud/run/deploy b/gcloud/run/deploy index e59990bfa..34fbf66dd 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -420,19 +420,27 @@ FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. + Specify which of the outbound traffic to send through Direct VPC + egress or the VPC connector for this resource. This resource must + have Direct VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC - connector. Provides the same functionality as 'all-traffic'. - Prefer to use 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + (RFC 1918 and Private Google Access IPs) through Direct VPC + egress or the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. These flags modify the Cloud SQL instances this Service connects to. You can specify a name of a Cloud SQL instance if it's in the same project diff --git a/gcloud/run/jobs/create b/gcloud/run/jobs/create index 473bcc806..9bdb11648 100644 --- a/gcloud/run/jobs/create +++ b/gcloud/run/jobs/create @@ -141,19 +141,27 @@ OPTIONAL FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. - VPC_EGRESS must be one of: + Specify which of the outbound traffic to send through Direct VPC egress + or the VPC connector for this resource. This resource must have Direct + VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must + be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC connector. - Provides the same functionality as 'all-traffic'. Prefer to use - 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only - Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + Default option. Sends outbound traffic to private IP addresses (RFC + 1918 and Private Google Access IPs) through Direct VPC egress or + the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. At most one of these can be specified: diff --git a/gcloud/run/jobs/deploy b/gcloud/run/jobs/deploy index e508075f5..7576b0ea7 100644 --- a/gcloud/run/jobs/deploy +++ b/gcloud/run/jobs/deploy @@ -138,19 +138,27 @@ FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. - VPC_EGRESS must be one of: + Specify which of the outbound traffic to send through Direct VPC egress + or the VPC connector for this resource. This resource must have Direct + VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must + be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC connector. - Provides the same functionality as 'all-traffic'. Prefer to use - 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only - Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + Default option. Sends outbound traffic to private IP addresses (RFC + 1918 and Private Google Access IPs) through Direct VPC egress or + the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. At most one of these can be specified: diff --git a/gcloud/run/jobs/update b/gcloud/run/jobs/update index 387931f71..a470acb24 100644 --- a/gcloud/run/jobs/update +++ b/gcloud/run/jobs/update @@ -128,19 +128,27 @@ FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. - VPC_EGRESS must be one of: + Specify which of the outbound traffic to send through Direct VPC egress + or the VPC connector for this resource. This resource must have Direct + VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must + be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC connector. - Provides the same functionality as 'all-traffic'. Prefer to use - 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only - Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + Default option. Sends outbound traffic to private IP addresses (RFC + 1918 and Private Google Access IPs) through Direct VPC egress or + the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. These flags modify the Cloud SQL instances this Service connects to. You can specify a name of a Cloud SQL instance if it's in the same project and diff --git a/gcloud/run/services/update b/gcloud/run/services/update index 94181e94c..82cb1ea76 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -249,19 +249,27 @@ FLAGS Set a VPC connector for this resource. --vpc-egress=VPC_EGRESS - The outbound traffic to send through the VPC connector for this - resource. This resource must have a VPC connector to set VPC egress. + Specify which of the outbound traffic to send through Direct VPC + egress or the VPC connector for this resource. This resource must + have Direct VPC egress enabled or a VPC connector to set this flag. VPC_EGRESS must be one of: all - (DEPRECATED) Sends all outbound traffic through the VPC - connector. Provides the same functionality as 'all-traffic'. - Prefer to use 'all-traffic' instead. + (DEPRECATED) Sends all outbound traffic through Direct VPC egress + or the VPC connector. Provides the same functionality as + 'all-traffic'. Prefer to use 'all-traffic' instead. all-traffic - Sends all outbound traffic through the VPC connector. + Sends all outbound traffic through Direct VPC egress or the VPC + connector. private-ranges-only Default option. Sends outbound traffic to private IP addresses - defined by RFC1918 through the VPC connector. + (RFC 1918 and Private Google Access IPs) through Direct VPC + egress or the VPC connector. + + Traffic to other Cloud Run services might require additional + configuration. See + https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services + for more information. These flags modify the Cloud SQL instances this Service connects to. You can specify a name of a Cloud SQL instance if it's in the same project