diff --git a/gcloud/_version b/gcloud/_version index c5cda48ad..46c979b39 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 497.0.0 -alpha 2024.10.11 -beta 2024.10.11 +Google Cloud SDK 498.0.0 +alpha 2024.10.18 +beta 2024.10.18 bq 2.1.9 bundled-python3-unix 3.11.9 -core 2024.10.11 +core 2024.10.18 gcloud-crc32c 1.0.0 gsutil 5.31 diff --git a/gcloud/alloydb/clusters/create b/gcloud/alloydb/clusters/create index e5a356ea4..e95b22189 100644 --- a/gcloud/alloydb/clusters/create +++ b/gcloud/alloydb/clusters/create @@ -7,7 +7,7 @@ SYNOPSIS [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async] [--database-version=DATABASE_VERSION] [--enable-private-service-connect] [--network=NETWORK] - [--subscription-type=SUBSCRIPTION_TYPE] + [--subscription-type=SUBSCRIPTION_TYPE] [--tags=[KEY=VALUE,...]] [--continuous-backup-recovery-window-days=RECOVERY_PERIOD --enable-continuous-backup [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY @@ -76,6 +76,12 @@ OPTIONAL FLAGS Subscription type of the cluster. SUBSCRIPTION_TYPE must be one of: STANDARD, TRIAL. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. + + Example: 123/environment=production,123/costCenter=marketing + Continuous Backup configuration. If unspecified, continuous backups are enabled. diff --git a/gcloud/alpha/ai/endpoints/create b/gcloud/alpha/ai/endpoints/create index 04bf84d56..4e08e5f46 100644 --- a/gcloud/alpha/ai/endpoints/create +++ b/gcloud/alpha/ai/endpoints/create @@ -5,8 +5,8 @@ SYNOPSIS gcloud alpha ai endpoints create --display-name=DISPLAY_NAME [--description=DESCRIPTION] [--encryption-kms-key-name=ENCRYPTION_KMS_KEY_NAME] - [--endpoint-id=ENDPOINT_ID] [--labels=[KEY=VALUE,...]] - [--network=NETWORK] [--region=REGION] + [--endpoint-id=ENDPOINT_ID] [--gdce-zone=GDCE_ZONE] + [--labels=[KEY=VALUE,...]] [--network=NETWORK] [--region=REGION] [--request-response-logging-rate=REQUEST_RESPONSE_LOGGING_RATE --request-response-logging-table=REQUEST_RESPONSE_LOGGING_TABLE] [GCLOUD_WIDE_FLAG ...] @@ -36,6 +36,9 @@ OPTIONAL FLAGS --endpoint-id=ENDPOINT_ID User-specified ID of the endpoint. + --gdce-zone=GDCE_ZONE + The name of the GDCE zone. If set, the endpoint is in GDCE. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/alpha/alloydb/clusters/create b/gcloud/alpha/alloydb/clusters/create index dde684128..0c18952de 100644 --- a/gcloud/alpha/alloydb/clusters/create +++ b/gcloud/alpha/alloydb/clusters/create @@ -7,7 +7,7 @@ SYNOPSIS --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async] [--database-version=DATABASE_VERSION] [--enable-private-service-connect] [--network=NETWORK] - [--subscription-type=SUBSCRIPTION_TYPE] + [--subscription-type=SUBSCRIPTION_TYPE] [--tags=[KEY=VALUE,...]] [--continuous-backup-recovery-window-days=RECOVERY_PERIOD --enable-continuous-backup [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY @@ -76,6 +76,12 @@ OPTIONAL FLAGS Subscription type of the cluster. SUBSCRIPTION_TYPE must be one of: STANDARD, TRIAL. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. + + Example: 123/environment=production,123/costCenter=marketing + Continuous Backup configuration. If unspecified, continuous backups are enabled. diff --git a/gcloud/alpha/alloydb/clusters/upgrade b/gcloud/alpha/alloydb/clusters/upgrade index e392b2c61..f907dd8ab 100644 --- a/gcloud/alpha/alloydb/clusters/upgrade +++ b/gcloud/alpha/alloydb/clusters/upgrade @@ -45,5 +45,7 @@ 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. + access allowlist. This variant is also available: + + $ gcloud beta alloydb clusters upgrade diff --git a/gcloud/alpha/audit-manager/audit-reports/generate b/gcloud/alpha/audit-manager/audit-reports/generate index 23d5c460d..243426cea 100644 --- a/gcloud/alpha/audit-manager/audit-reports/generate +++ b/gcloud/alpha/audit-manager/audit-reports/generate @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud alpha audit-manager audit-reports generate - --compliance-standard=COMPLIANCE_STANDARD --gcs-uri=GCS_URI + --compliance-framework=COMPLIANCE_FRAMEWORK --gcs-uri=GCS_URI --location=LOCATION --report-format=REPORT_FORMAT (--folder=FOLDER | --project=PROJECT) [GCLOUD_WIDE_FLAG ...] @@ -12,16 +12,16 @@ DESCRIPTION EXAMPLES To generate an Audit Report in the us-central1 region, for a project with - ID 123 for compliance standard fedramp_moderate in odf format and store it + ID 123 for compliance framework fedramp_moderate in odf format and store it in gs://testbucketauditmanager bucket, run: $ gcloud alpha audit-manager audit-reports generate --project=123 \ - --location=us-central1 --compliance-standard=fedramp_moderate \ + --location=us-central1 --compliance-framework=fedramp_moderate \ --report-format=odf --gcs-uri=gs://testbucketauditmanager REQUIRED FLAGS - --compliance-standard=COMPLIANCE_STANDARD - Compliance Standard against which the Report must be generated. Eg: + --compliance-framework=COMPLIANCE_FRAMEWORK + Compliance Framework against which the Report must be generated. Eg: FEDRAMP_MODERATE --gcs-uri=GCS_URI diff --git a/gcloud/alpha/audit-manager/audit-scopes/generate b/gcloud/alpha/audit-manager/audit-scopes/generate index 4a8673658..79e5d9905 100644 --- a/gcloud/alpha/audit-manager/audit-scopes/generate +++ b/gcloud/alpha/audit-manager/audit-scopes/generate @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud alpha audit-manager audit-scopes generate - --compliance-standard=COMPLIANCE_STANDARD --location=LOCATION + --compliance-framework=COMPLIANCE_FRAMEWORK --location=LOCATION --output-file-name=OUTPUT_FILE_NAME --report-format=REPORT_FORMAT (--folder=FOLDER | --project=PROJECT) [--output-directory=OUTPUT_DIRECTORY] [GCLOUD_WIDE_FLAG ...] @@ -13,17 +13,17 @@ DESCRIPTION EXAMPLES To generate an Audit Scope in the us-central1 region, for a project with ID - 123 for compliance standard fedramp_moderate in odf format, run: + 123 for compliance framework fedramp_moderate in odf format, run: $ gcloud alpha audit-manager audit-scopes generate --project="123" \ --location="us-central1" \ - --compliance-standard="fedramp_moderate" --report-format="odf" \ - --output-directory="scopes/currentyear" \ + --compliance-framework="fedramp_moderate" \ + --report-format="odf" --output-directory="scopes/currentyear" \ --output-file-name="auditreport" REQUIRED FLAGS - --compliance-standard=COMPLIANCE_STANDARD - Compliance Standard against which the Report must be generated. Eg: + --compliance-framework=COMPLIANCE_FRAMEWORK + Compliance Framework against which the Report must be generated. Eg: FEDRAMP_MODERATE --location=LOCATION diff --git a/gcloud/alpha/backup-dr/backup-plan-associations/create b/gcloud/alpha/backup-dr/backup-plan-associations/create index c151e3fe8..8bec84431 100644 --- a/gcloud/alpha/backup-dr/backup-plan-associations/create +++ b/gcloud/alpha/backup-dr/backup-plan-associations/create @@ -6,8 +6,8 @@ SYNOPSIS gcloud alpha backup-dr backup-plan-associations create (BACKUP_PLAN_ASSOCIATION : --location=LOCATION --workload-project=WORKLOAD_PROJECT) - --backup-plan=BACKUP_PLAN --resource=RESOURCE [--async] - [GCLOUD_WIDE_FLAG ...] + --backup-plan=BACKUP_PLAN --resource=RESOURCE + --resource-type=RESOURCE_TYPE [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new backup plan association in the project. It can only be @@ -91,6 +91,10 @@ REQUIRED FLAGS The resource to which the backup plan is to be applied. E.g., projects/sample-project/zones/us-central1-a/instances/sample-instance + --resource-type=RESOURCE_TYPE + Type of resource to which the backup plan should be applied. E.g., + compute..com/Instance + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/compute/commitments/create b/gcloud/alpha/compute/commitments/create index b57a2bf2d..bd4999b01 100644 --- a/gcloud/alpha/compute/commitments/create +++ b/gcloud/alpha/compute/commitments/create @@ -107,14 +107,14 @@ OPTIONAL FLAGS Type of commitment. memory-optimized indicates that the commitment is for memory-optimized VMs. TYPE must be one of: accelerator-optimized, accelerator-optimized-a3, accelerator-optimized-a3-mega, - compute-optimized, compute-optimized-c2d, compute-optimized-c3, - compute-optimized-c3d, compute-optimized-h3, general-purpose, - general-purpose-c4, general-purpose-e2, general-purpose-n2, - general-purpose-n2d, general-purpose-n4, general-purpose-t2d, - graphics-optimized, memory-optimized, memory-optimized-m3, - memory-optimized-x4, memory-optimized-x4-16tb, - memory-optimized-x4-24tb, memory-optimized-x4-32tb, - storage-optimized-z3. + accelerator-optimized-a3-ultra, compute-optimized, + compute-optimized-c2d, compute-optimized-c3, compute-optimized-c3d, + compute-optimized-h3, general-purpose, general-purpose-c4, + general-purpose-e2, general-purpose-n2, general-purpose-n2d, + general-purpose-n4, general-purpose-t2d, graphics-optimized, + memory-optimized, memory-optimized-m3, memory-optimized-x4, + memory-optimized-x4-16tb, memory-optimized-x4-24tb, + memory-optimized-x4-32tb, storage-optimized-z3. Manage the reservations to be created with the commitment. diff --git a/gcloud/alpha/compute/instance-groups/managed/create b/gcloud/alpha/compute/instance-groups/managed/create index 17b3c18b5..3c8658094 100644 --- a/gcloud/alpha/compute/instance-groups/managed/create +++ b/gcloud/alpha/compute/instance-groups/managed/create @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud alpha compute instance-groups managed create NAME --size=SIZE - --template=TEMPLATE [--base-instance-name=BASE_INSTANCE_NAME] + --template=TEMPLATE + [--action-on-vm-failed-health-check=ACTION_ON_FAILED_HEALTH_CHECK] + [--base-instance-name=BASE_INSTANCE_NAME] [--default-action-on-vm-failure=ACTION_ON_VM_FAILURE] [--description=DESCRIPTION] [--[no-]force-update-on-repair] [--initial-delay=INITIAL_DELAY] [--instance-redistribution-type=TYPE] @@ -76,21 +78,36 @@ REQUIRED FLAGS instance template is either a global or regional resource. OPTIONAL FLAGS + --action-on-vm-failed-health-check=ACTION_ON_FAILED_HEALTH_CHECK + Specifies the action that a MIG performs on an unhealthy VM. A VM is + marked as unhealthy when the application running on that VM fails a + health check. By default, the value of the flag is set to + default-action. ACTION_ON_FAILED_HEALTH_CHECK must be one of: + + default-action + (Default) MIG uses the same action configured for the + defaultActionOnFailure field. + do-nothing + MIG does not repair an unhealthy VM. + repair + MIG automatically repairs an unhealthy VM by recreating it. + --base-instance-name=BASE_INSTANCE_NAME Base name to use for the Compute Engine instances that will be created with the managed instance group. If not provided base instance name will be the prefix of instance group name. --default-action-on-vm-failure=ACTION_ON_VM_FAILURE - Specifies the action that a MIG performs on a failed or an unhealthy - VM. A VM is marked as unhealthy when the application running on that VM - fails a health check. By default, the value of the flag is set to - repair. ACTION_ON_VM_FAILURE must be one of: + Specifies the action that a MIG performs on a failed VM. If the value + of the onFailedHealthCheck field is DEFAULT_ACTION, then the same + action also applies to the VMs on which your application fails a health + check. By default, the value of the flag is set to repair. + ACTION_ON_VM_FAILURE must be one of: - do-nothing - MIG does not repair a failed or an unhealthy VM. repair - MIG automatically repairs a failed or an unhealthy VM. + (Default) MIG automatically repairs a failed VM by recreating it. + do-nothing + MIG does not repair a failed VM. --description=DESCRIPTION An optional description for this group. diff --git a/gcloud/alpha/compute/instance-groups/managed/update b/gcloud/alpha/compute/instance-groups/managed/update index 880049788..bec4e2bf7 100644 --- a/gcloud/alpha/compute/instance-groups/managed/update +++ b/gcloud/alpha/compute/instance-groups/managed/update @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud alpha compute instance-groups managed update NAME + [--action-on-vm-failed-health-check=ACTION_ON_FAILED_HEALTH_CHECK] [--default-action-on-vm-failure=ACTION_ON_VM_FAILURE] [--description=DESCRIPTION] [--[no-]force-update-on-repair] [--instance-redistribution-type=TYPE] @@ -70,16 +71,31 @@ POSITIONAL ARGUMENTS Name of the managed instance group to update. FLAGS - --default-action-on-vm-failure=ACTION_ON_VM_FAILURE - Specifies the action that a MIG performs on a failed or an unhealthy - VM. A VM is marked as unhealthy when the application running on that VM - fails a health check. By default, the value of the flag is set to - repair. ACTION_ON_VM_FAILURE must be one of: + --action-on-vm-failed-health-check=ACTION_ON_FAILED_HEALTH_CHECK + Specifies the action that a MIG performs on an unhealthy VM. A VM is + marked as unhealthy when the application running on that VM fails a + health check. By default, the value of the flag is set to + default-action. ACTION_ON_FAILED_HEALTH_CHECK must be one of: + default-action + (Default) MIG uses the same action configured for the + defaultActionOnFailure field. do-nothing - MIG does not repair a failed or an unhealthy VM. + MIG does not repair an unhealthy VM. repair - MIG automatically repairs a failed or an unhealthy VM. + MIG automatically repairs an unhealthy VM by recreating it. + + --default-action-on-vm-failure=ACTION_ON_VM_FAILURE + Specifies the action that a MIG performs on a failed VM. If the value + of the onFailedHealthCheck field is DEFAULT_ACTION, then the same + action also applies to the VMs on which your application fails a health + check. By default, the value of the flag is set to repair. + ACTION_ON_VM_FAILURE must be one of: + + repair + (Default) MIG automatically repairs a failed VM by recreating it. + do-nothing + MIG does not repair a failed VM. --description=DESCRIPTION An optional description for this group. To clear the description, set diff --git a/gcloud/alpha/compute/interconnects/groups/create b/gcloud/alpha/compute/interconnects/groups/create new file mode 100644 index 000000000..237b5a838 --- /dev/null +++ b/gcloud/alpha/compute/interconnects/groups/create @@ -0,0 +1,51 @@ +NAME + gcloud alpha compute interconnects groups create - create a Compute Engine + interconnect group + +SYNOPSIS + gcloud alpha compute interconnects groups create NAME + --intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects groups create is used to create + interconnect groups. An interconnect group connects a set of redundant + interconnects between Google and the customer. + + For an example, refer to the EXAMPLES section below. + +EXAMPLES + To create an interconnect group capable of PRODUCTION_NON_CRITICAL, run: + + $ gcloud alpha compute interconnects groups create \ + example-interconnect-group \ + --intended-topology-capability=PRODUCTION_NON_CRITICAL \ + --description="Example interconnect group" + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect group to create. + +REQUIRED FLAGS + --intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY + The reliability the user intends this group to be capable of, in terms + of the Interconnect product SLAs. + +OPTIONAL FLAGS + --description=DESCRIPTION + An optional, textual description for the interconnect group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/groups/help b/gcloud/alpha/compute/interconnects/groups/help new file mode 100644 index 000000000..c6d54315e --- /dev/null +++ b/gcloud/alpha/compute/interconnects/groups/help @@ -0,0 +1,30 @@ +NAME + gcloud alpha compute interconnects groups - create or manipulate + interconnect groups + +SYNOPSIS + gcloud alpha compute interconnects groups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create or manipulate interconnect groups. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a Compute Engine interconnect group. + + update + (ALPHA) Update a Compute Engine interconnect group. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/groups/update b/gcloud/alpha/compute/interconnects/groups/update new file mode 100644 index 000000000..4768da50b --- /dev/null +++ b/gcloud/alpha/compute/interconnects/groups/update @@ -0,0 +1,41 @@ +NAME + gcloud alpha compute interconnects groups update - update a Compute Engine + interconnect group + +SYNOPSIS + gcloud alpha compute interconnects groups update NAME + --intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute interconnects groups update is used to update + interconnect groups. An interconnect group represents a set of redundant + interconnects between Google and the customer. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect group to update. + +REQUIRED FLAGS + --intended-topology-capability=INTENDED_TOPOLOGY_CAPABILITY + The reliability the user intends this group to be capable of, in terms + of the Interconnect product SLAs. + +OPTIONAL FLAGS + --description=DESCRIPTION + An optional, textual description for the interconnect group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/interconnects/help b/gcloud/alpha/compute/interconnects/help index 3976996ef..b52350889 100644 --- a/gcloud/alpha/compute/interconnects/help +++ b/gcloud/alpha/compute/interconnects/help @@ -26,6 +26,9 @@ GROUPS attachments (ALPHA) Read and manipulate Compute Engine interconnect attachments. + groups + (ALPHA) Create or manipulate interconnect groups. + locations (ALPHA) Read and manipulate Compute Engine interconnect locations. diff --git a/gcloud/alpha/compute/networks/subnets/create b/gcloud/alpha/compute/networks/subnets/create index 31976dc68..927f9771d 100644 --- a/gcloud/alpha/compute/networks/subnets/create +++ b/gcloud/alpha/compute/networks/subnets/create @@ -147,6 +147,8 @@ OPTIONAL FLAGS Reserved for Global Envoy-based Load Balancing. INTERNAL_HTTPS_LOAD_BALANCER Reserved for Internal HTTP(S) Load Balancing. + PEER_MIGRATION + Reserved for subnet migration between peered VPCs. PRIVATE Regular user created or automatically created subnet. PRIVATE_NAT diff --git a/gcloud/alpha/compute/networks/subnets/update b/gcloud/alpha/compute/networks/subnets/update index 4d28ca234..b37ccd19f 100644 --- a/gcloud/alpha/compute/networks/subnets/update +++ b/gcloud/alpha/compute/networks/subnets/update @@ -197,12 +197,16 @@ FLAGS enable-bidirectional-access, enable-outbound-vm-access. --purpose=PURPOSE - The purpose of the subnetwork is set to REGIONAL_MANAGED_PROXY to - migrate from the INTERNAL_HTTPS_LOAD_BALANCER purpose. PURPOSE must - be (only one value is supported): + The purpose of the subnetwork can be changed in a few scenarios. + PURPOSE must be one of: + PRIVATE + The default subnet type. Only PEER_MIGRATION subnets can be + changed to PRIVATE. REGIONAL_MANAGED_PROXY - The proxy-only subnet for regional HTTP(S) load balancers. + The proxy-only subnet for regional HTTP(S) load balancers. Only + INTERNAL_HTTPS_LOAD_BALANCER subnets can be changed to + REGIONAL_MANAGED_PROXY. --remove-secondary-ranges=PROPERTY=VALUE,[...] Removes secondary ranges from the subnetwork. diff --git a/gcloud/alpha/compute/snapshot-settings/describe b/gcloud/alpha/compute/snapshot-settings/describe index 06db505c5..d6503a9c4 100644 --- a/gcloud/alpha/compute/snapshot-settings/describe +++ b/gcloud/alpha/compute/snapshot-settings/describe @@ -3,7 +3,8 @@ NAME settings SYNOPSIS - gcloud alpha compute snapshot-settings describe [GCLOUD_WIDE_FLAG ...] + gcloud alpha compute snapshot-settings describe [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Describe the snapshot settings of a project. @@ -12,7 +13,11 @@ EXAMPLES To display the snapshot settings of a project called my-project, run: $ gcloud alpha compute snapshot-settings describe \ - --project=my-project + --project=my-project + +FLAGS + --region=REGION + region for regional snapshot settings GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -23,8 +28,9 @@ GCLOUD WIDE FLAGS 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/ + This command uses the compute/alpha or compute/beta or comptue/v1 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 diff --git a/gcloud/alpha/compute/snapshot-settings/update b/gcloud/alpha/compute/snapshot-settings/update index 48f8a1b4b..e341b7fe5 100644 --- a/gcloud/alpha/compute/snapshot-settings/update +++ b/gcloud/alpha/compute/snapshot-settings/update @@ -2,7 +2,10 @@ NAME gcloud alpha compute snapshot-settings update - update snapshot settings SYNOPSIS - gcloud alpha compute snapshot-settings update [--async] + gcloud alpha compute snapshot-settings update + [--add-access-locations=[ADD_ACCESS_LOCATIONS,...]] [--async] + [--region=REGION] + [--remove-access-locations=[REMOVE_ACCESS_LOCATIONS,...]] [--storage-location-names=[STORAGE_LOCATION_NAMES,...]] [--storage-location-policy=STORAGE_LOCATION_POLICY] [GCLOUD_WIDE_FLAG ...] @@ -15,26 +18,35 @@ EXAMPLES nearest multi-region as the source disk, run: $ gcloud alpha compute snapshot-settings update \ - --storage-location-policy=nearest-multi-region + --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 + --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 + --storage-location-policy=specific-locations \ + --storage-location-names=us-west1 FLAGS + --add-access-locations=[ADD_ACCESS_LOCATIONS,...] + Access locations to add to snapshot settings + --async Return immediately, without waiting for the operation in progress to complete. + --region=REGION + region for regional snapshot settings + + --remove-access-locations=[REMOVE_ACCESS_LOCATIONS,...] + Access locations to remove from snapshot settings + --storage-location-names=[STORAGE_LOCATION_NAMES,...] The custom storage location that you specify for the project's snapshots. You can specify only a single location. Use this flag only @@ -59,8 +71,9 @@ GCLOUD WIDE FLAGS 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/ + This command uses the compute/alpha or compute/beta or compute/v1 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 diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index 598b25dea..e664d0065 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -731,6 +731,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index 1a0d93699..934634a59 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -763,6 +763,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index c4f820ecb..085cec526 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -775,6 +775,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 34194f8e1..93f522c3e 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -778,6 +778,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 619bdadd6..b827be39a 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -739,6 +739,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/alpha/container/aws/node-pools/create b/gcloud/alpha/container/aws/node-pools/create index 6af7054ea..40e736d8c 100644 --- a/gcloud/alpha/container/aws/node-pools/create +++ b/gcloud/alpha/container/aws/node-pools/create @@ -12,6 +12,10 @@ SYNOPSIS [--annotations=ANNOTATION,[ANNOTATION,...]] [--async] [--enable-autorepair] [--image-type=IMAGE_TYPE] [--instance-placement=INSTANCE_PLACEMENT] + [--kubelet-config-cpu-cfs-quota=KUBELET_CONFIG_CPU_CFS_QUOTA] + [--kubelet-config-cpu-cfs-quota-period=KUBELET_CONFIG_CPU_CFS_QUOTA_PERIOD] + [--kubelet-config-cpu-manager-policy=KUBELET_CONFIG_CPU_MANAGER_POLICY] + [--kubelet-config-pod-pids-limit=KUBELET_CONFIG_POD_PIDS_LIMIT] [--max-surge-update=MAX_SURGE_UPDATE] [--max-unavailable-update=MAX_UNAVAILABLE_UPDATE] [--node-labels=NODE_LABEL,[NODE_LABEL,...]] @@ -143,6 +147,20 @@ OPTIONAL FLAGS Type of the tenancy. INSTANCE_PLACEMENT must be one of: dedicated, default, host. + --kubelet-config-cpu-cfs-quota=KUBELET_CONFIG_CPU_CFS_QUOTA + Enforce a Kubelet CPU CFS quota. + + --kubelet-config-cpu-cfs-quota-period=KUBELET_CONFIG_CPU_CFS_QUOTA_PERIOD + Kubelet CPU CFS quota period, within the range "1ms" to "1s". + + --kubelet-config-cpu-manager-policy=KUBELET_CONFIG_CPU_MANAGER_POLICY + Kubelet CPU manager policy. KUBELET_CONFIG_CPU_MANAGER_POLICY must be + one of: none, static. + + --kubelet-config-pod-pids-limit=KUBELET_CONFIG_POD_PIDS_LIMIT + Kubelet maximum number of PIDS in any pod, within the range 1024 to + 4194304. + --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 diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index 56210ca20..2f6ff26a3 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -18,15 +18,16 @@ SYNOPSIS [--enable-backup-restore] [--enable-cilium-clusterwide-network-policy] [--enable-dns-access] [--enable-fleet] [--enable-google-cloud-access] [--enable-ip-access] [--enable-kubernetes-unstable-apis=API,[API,...]] - [--enable-master-global-access] [--enable-ray-cluster-logging] - [--enable-ray-cluster-monitoring] [--enable-ray-operator] - [--enable-secret-manager] [--fleet-project=PROJECT_ID_OR_NUMBER] - [--labels=[KEY=VALUE,...]] [--logging=[COMPONENT,...]] - [--monitoring=[COMPONENT,...]] [--network=NETWORK] - [--private-endpoint-subnetwork=NAME] [--release-channel=[CHANNEL]] - [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] - [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] - [--subnetwork=SUBNETWORK] [--workload-policies=WORKLOAD_POLICIES] + [--enable-master-global-access] [--enable-multi-networking] + [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] + [--enable-ray-operator] [--enable-secret-manager] + [--fleet-project=PROJECT_ID_OR_NUMBER] [--labels=[KEY=VALUE,...]] + [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] + [--network=NETWORK] [--private-endpoint-subnetwork=NAME] + [--release-channel=[CHANNEL]] [--security-group=SECURITY_GROUP] + [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] + [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] + [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--additive-vpc-scope-dns-domain=ADDITIVE_VPC_SCOPE_DNS_DOMAIN | --disable-additive-vpc-scope] @@ -264,6 +265,10 @@ FLAGS endpoint from any Google Cloud region or on-premises environment regardless of the private cluster's region. + --enable-multi-networking + Enables multi-networking on the cluster. Multi-networking is disabled + by default. + --enable-ray-cluster-logging Enable automatic log processing sidecar for Ray clusters. diff --git a/gcloud/alpha/dataproc/clusters/create b/gcloud/alpha/dataproc/clusters/create index 302a6919f..0bbce2dff 100644 --- a/gcloud/alpha/dataproc/clusters/create +++ b/gcloud/alpha/dataproc/clusters/create @@ -46,7 +46,6 @@ SYNOPSIS [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] - [--worker-machine-type=WORKER_MACHINE_TYPE] [--worker-min-cpu-platform=PLATFORM] [--zone=ZONE, -z ZONE] [--expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE] [--gce-pd-kms-key=GCE_PD_KMS_KEY @@ -68,7 +67,9 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] - [GCLOUD_WIDE_FLAG ...] + [--worker-machine-type=WORKER_MACHINE_TYPE + | --worker-machine-types=type=MACHINE_TYPE[, + type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a cluster. @@ -427,9 +428,6 @@ FLAGS --worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE Interface to use to attach local SSDs to each worker in a cluster. - --worker-machine-type=WORKER_MACHINE_TYPE - The type of machine to use for workers. Defaults to server-specified. - --worker-min-cpu-platform=PLATFORM When specified, the VM is scheduled on the host with a specified CPU architecture or a more recent CPU platform that's available in that @@ -862,6 +860,25 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. + At most one of these can be specified: + + --worker-machine-type=WORKER_MACHINE_TYPE + The type of machine to use for primary workers. Defaults to + server-specified. + + --worker-machine-types=type=MACHINE_TYPE[,type=MACHINE_TYPE...][,rank=RANK] + Machine types + (https://cloud.google.com/dataproc/docs/concepts/compute/supported-machine-types) + for primary worker nodes to use with optional rank. A lower rank + number is given higher preference. Based on availablilty, Dataproc + tries to create primary worker VMs using the worker machine type with + the lowest rank, and then tries to use machine types with higher + ranks as necessary. Machine types with the same rank are given the + same preference. Example use: + --worker-machine-types="type=e2-standard-8,type=n2-standard-8,rank=0". + For more information, see Dataproc Flexible VMs + (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/flexible-vms) + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster index 9dd5afd0d..d474d1404 100644 --- a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster @@ -39,7 +39,6 @@ SYNOPSIS [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] - [--worker-machine-type=WORKER_MACHINE_TYPE] [--worker-min-cpu-platform=PLATFORM] [--zone=ZONE, -z ZONE] [--image=IMAGE | --image-version=VERSION] [--kerberos-config-file=KERBEROS_CONFIG_FILE | --enable-kerberos @@ -56,7 +55,9 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] - [GCLOUD_WIDE_FLAG ...] + [--worker-machine-type=WORKER_MACHINE_TYPE + | --worker-machine-types=type=MACHINE_TYPE[, + type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Set a managed cluster for the workflow template. @@ -359,9 +360,6 @@ FLAGS --worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE Interface to use to attach local SSDs to each worker in a cluster. - --worker-machine-type=WORKER_MACHINE_TYPE - The type of machine to use for workers. Defaults to server-specified. - --worker-min-cpu-platform=PLATFORM When specified, the VM is scheduled on the host with a specified CPU architecture or a more recent CPU platform that's available in that @@ -738,6 +736,25 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. + At most one of these can be specified: + + --worker-machine-type=WORKER_MACHINE_TYPE + The type of machine to use for primary workers. Defaults to + server-specified. + + --worker-machine-types=type=MACHINE_TYPE[,type=MACHINE_TYPE...][,rank=RANK] + Machine types + (https://cloud.google.com/dataproc/docs/concepts/compute/supported-machine-types) + for primary worker nodes to use with optional rank. A lower rank + number is given higher preference. Based on availablilty, Dataproc + tries to create primary worker VMs using the worker machine type with + the lowest rank, and then tries to use machine types with higher + ranks as necessary. Machine types with the same rank are given the + same preference. Example use: + --worker-machine-types="type=e2-standard-8,type=n2-standard-8,rank=0". + For more information, see Dataproc Flexible VMs + (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/flexible-vms) + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/redis/clusters/create b/gcloud/alpha/redis/clusters/create index 778b33917..d78a26ac0 100644 --- a/gcloud/alpha/redis/clusters/create +++ b/gcloud/alpha/redis/clusters/create @@ -4,12 +4,11 @@ NAME SYNOPSIS gcloud alpha redis clusters create (CLUSTER : --region=REGION) - --network=NETWORK [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] - [--auth-mode=AUTH_MODE] + [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] [--auth-mode=AUTH_MODE] [--cross-cluster-replication-role=CROSS_CLUSTER_REPLICATION_ROLE] [--deletion-protection] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] - [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [--network=NETWORK] [--node-type=NODE_TYPE] [--persistence-mode=PERSISTENCE_MODE] [--primary-cluster=PRIMARY_CLUSTER] [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] @@ -83,14 +82,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property redis/region. -REQUIRED FLAGS - --network=NETWORK - The network used to create your instance. It must use the format: - projects/NETWORK_PROJECT_ID/global/networks/NETWORK_ID. The network ID - used here must match the network ID used by the service connection - policy. Otherwise, the create operation fails - -OPTIONAL FLAGS +FLAGS --aof-append-fsync=AOF_APPEND_FSYNC Fsync configuration. AOF_APPEND_FSYNC must be one of: @@ -137,6 +129,12 @@ OPTIONAL FLAGS Hour of day (0 to 23) for the start of maintenance window, in UTC time zone. + --network=NETWORK + The network used to create your instance. It must use the format: + projects/NETWORK_PROJECT_ID/global/networks/NETWORK_ID. The network ID + used here must match the network ID used by the service connection + policy. Otherwise, the create operation fails + --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index ff6c50341..fdd184ed0 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -2,13 +2,35 @@ NAME gcloud alpha run deploy - create or update a Cloud Run service SYNOPSIS - gcloud alpha run deploy [[SERVICE] --namespace=NAMESPACE] [--async] - [--concurrency=CONCURRENCY] [--container=CONTAINER] - [--ingress=INGRESS; default="all"] [--max-instances=MAX_INSTANCES] - [--min-instances=MIN_INSTANCES] - [--platform=PLATFORM; default="managed"] - [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] - [--no-traffic] + gcloud alpha run deploy [[SERVICE] --namespace=NAMESPACE] + [--[no-]allow-unauthenticated] [--async] [--breakglass=JUSTIFICATION] + [--clear-vpc-connector] [--concurrency=CONCURRENCY] + [--container=CONTAINER] [--[no-]cpu-boost] [--[no-]cpu-throttling] + [--[no-]default-url] [--delegate-builds] [--[no-]deploy-health-check] + [--description=DESCRIPTION] + [--execution-environment=EXECUTION_ENVIRONMENT] + [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] + [--max-instances=MAX_INSTANCES] [--max-surge=MAX_SURGE] + [--max-unavailable=MAX_UNAVAILABLE] [--mesh=MESH] + [--min-instances=MIN_INSTANCES] [--region=REGION] + [--remove-containers=[CONTAINER,...]] + [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] + [--service-account=SERVICE_ACCOUNT] + [--service-max-instances=SERVICE_MAX_INSTANCES] + [--service-min-instances=SERVICE_MIN_INSTANCES] + [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] + [--no-traffic] [--vpc-connector=VPC_CONNECTOR] + [--vpc-egress=VPC_EGRESS] + [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --clear-cloudsql-instances + | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--add-custom-audiences=[CUSTOM-AUDIENCES,...] + | --clear-custom-audiences + | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + | --set-custom-audiences=[CUSTOM-AUDIENCES,...]] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --[no-]automatic-updates --clear-volume-mounts --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU @@ -29,41 +51,21 @@ SYNOPSIS | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...] --command=[COMMAND,...] | --function=FUNCTION --image=IMAGE | --source=SOURCE] + [--binary-authorization=POLICY | --clear-binary-authorization] + [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] + | --remove-config-maps=[KEY,...] + --update-config-maps=[KEY=VALUE,...]] + [--clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] + [--clear-key | --key=KEY] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] - [--connectivity=CONNECTIVITY --clear-config-maps - | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] - [--[no-]allow-unauthenticated --breakglass=JUSTIFICATION - --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling - --[no-]default-url --delegate-builds --[no-]deploy-health-check - --description=DESCRIPTION - --execution-environment=EXECUTION_ENVIRONMENT - --[no-]invoker-iam-check --max-surge=MAX_SURGE - --max-unavailable=MAX_UNAVAILABLE --mesh=MESH - --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX - --scaling=SCALING --service-max-instances=SERVICE_MAX_INSTANCES - --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity - --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --clear-cloudsql-instances - | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - | --clear-custom-audiences - | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --add-volume=[KEY=VALUE,...] --clear-volumes - --remove-volume=[VOLUME,...] --binary-authorization=POLICY - | --clear-binary-authorization --clear-encryption-key-shutdown-hours - | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - --clear-key | --key=KEY --clear-network + [--clear-network | --network=NETWORK --subnet=SUBNET --clear-network-tags - | --network-tags=[TAG,...] --clear-post-key-revocation-action-type + | --network-tags=[TAG,...]] + [--clear-post-key-revocation-action-type | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates or updates a Cloud Run service. @@ -112,10 +114,25 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS + --[no-]allow-unauthenticated + Whether to enable allowing unauthenticated access to the service. This + may take a few moments to take effect. Use --allow-unauthenticated to + enable and --no-allow-unauthenticated to disable. + --async Return immediately, without waiting for the operation in progress to complete. + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. + + --clear-vpc-connector + Remove the VPC connector for this resource. + --concurrency=CONCURRENCY Set the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified or provide the special value @@ -125,64 +142,138 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + --[no-]cpu-boost + Whether to allocate extra CPU to containers on startup to reduce the + perceived latency of a cold start request. Enabled by default when + unspecified on new services. Use --cpu-boost to enable and + --no-cpu-boost to disable. + + --[no-]cpu-throttling + Whether to throttle the CPU when the container is not actively serving + requests. Use --cpu-throttling to enable and --no-cpu-throttling to + disable. + + --[no-]default-url + Toggles the default url for a run service. This is enabled by default + if not specified. Use --default-url to enable and --no-default-url to + disable. + + --delegate-builds + Specifies that the source deploy for run will use the Build API to + submit the build. + + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + + --description=DESCRIPTION + Provides an optional, human-readable description of the service. + + --execution-environment=EXECUTION_ENVIRONMENT + Selects the execution environment where the application will run. + EXECUTION_ENVIRONMENT must be one of: + + gen1 + Run the application in a first generation execution environment. + gen2 + Run the application in a second generation execution environment. + --ingress=INGRESS; default="all" Set the ingress traffic sources allowed to call the service. For Cloud - Run (fully managed) the --[no-]allow-unauthenticated flag separately - controls the identities allowed to call the service. INGRESS must be - one of: + Run the --[no-]allow-unauthenticated flag separately controls the + identities allowed to call the service. INGRESS must be one of: all Inbound requests from all sources are allowed. internal - For Cloud Run (fully managed), only inbound requests from VPC - networks in the same project or VPC Service Controls perimeter, as - well as Pub/Sub subscriptions and Eventarc events in the same - project or VPC Service Controls perimeter are allowed. All other - requests are rejected. See - https://cloud.google.com/run/docs/securing/ingress for full details - on the definition of internal traffic for Cloud Run (fully - managed). For Cloud Run for Anthos, only inbound requests from the - same cluster are allowed. + For Cloud Run, only inbound requests from VPC networks in the same + project or VPC Service Controls perimeter, as well as Pub/Sub + subscriptions and Eventarc events in the same project or VPC + Service Controls perimeter are allowed. All other requests are + rejected. See https://cloud.google.com/run/docs/securing/ingress + for full details on the definition of internal traffic for Cloud + Run. internal-and-cloud-load-balancing - Only supported for Cloud Run (fully managed). Only inbound requests - from Google Cloud Load Balancing or a traffic source allowed by the - internal option are allowed. + Only inbound requests from Google Cloud Load Balancing or a traffic + source allowed by the internal option are allowed. + + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. --max-instances=MAX_INSTANCES The maximum number of container instances of the Service to run. Use 'default' to unset the limit and use the platform default. + --max-surge=MAX_SURGE + A maximum percentage of instances that will be moved in each step of + traffic split changes. Use "default" to unset the limit and use the + platform default. + + --max-unavailable=MAX_UNAVAILABLE + A maximum percentage of instances that may be unavailable during + traffic split changes. Use "default" to unset the limit and use the + platform default. + + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. Mesh + resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + --min-instances=MIN_INSTANCES The minimum number of container instances for this Revision of the Service to run or 'default' to remove any minimum. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --remove-containers=[CONTAINER,...] + List of containers to remove. + + --revision-suffix=REVISION_SUFFIX + Specify the suffix of the revision name. Revision names always start + with the service name automatically. For example, specifying + [--revision-suffix=v1] for a service named 'helloworld', would lead to + a revision named 'helloworld-v1'. Set empty string to clear the suffix + and resume server-assigned naming. + + --scaling=SCALING + The scaling mode to use for this resource. SCALING must be one of: + + automatic + The number of instances is scaled automatically based on the usage + metrics. + manual + The number of instances is fixed to a provided config value. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. For the managed platform, - this is the email address of an IAM service account. For the - Kubernetes-based platforms (gke, kubernetes), this is the name of a - Kubernetes service account in the same namespace as the service. If not - provided, the revision will use the default service account of the - project, or default Kubernetes namespace service account respectively. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. + + --service-max-instances=SERVICE_MAX_INSTANCES + The maximum number of container instances for this Service to run. This + instance limit will be divided among all Revisions receiving a + percentage of traffic. Once service-max-instances is enabled for a + service, it cannot be disabled. + + --service-min-instances=SERVICE_MIN_INSTANCES + The minimum number of container instances for this Service to run or + 'default' to remove any minimum. These instances will be divided among + all Revisions receiving a percentage of traffic. + + --[no-]session-affinity + Whether to enable session affinity for connections to the service. Use + --session-affinity to enable and --no-session-affinity to disable. --tag=TAG Traffic tag to assign to the newly created revision. @@ -204,6 +295,125 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. + --vpc-connector=VPC_CONNECTOR + Set a VPC connector for this resource. + + --vpc-egress=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 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 Direct VPC egress or the VPC + connector. + private-ranges-only + 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 + region as your Cloud Run service; otherwise specify + :: for the instance. + + At most one of these can be specified: + + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Append the given values to the current Cloud SQL instances. + + --clear-cloudsql-instances + Empty the current Cloud SQL instances. + + --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Remove the given values from the current Cloud SQL instances. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Completely replace the current Cloud SQL instances with the given + values. + + These flags modify the custom audiences that can be used in the audience + field of ID token for authenticated requests. + + At most one of these can be specified: + + --add-custom-audiences=[CUSTOM-AUDIENCES,...] + Append the given values to the current custom audiences. + + --clear-custom-audiences + Empty the current custom audiences. + + --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + Remove the given values from the current custom audiences. + + --set-custom-audiences=[CUSTOM-AUDIENCES,...] + Completely replace the current custom audiences with the given + values. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags + should be specified without leading dashes and separated by + semicolons. + ◆ bucket: (optional) the name of the bucket to use as the source of + this volume. + ◆ dynamic-mounting: (optional) A boolean. If true, the volume will be + mounted dynamically. Note: You will either need to specify a bucket + or set dynamic-mounting to true, but not both. + + in-memory: An ephemeral volume that stores data in the instance's + memory. With this type of volume, data is not shared between instances + and all data will be lost when the instance it is on is terminated. + Additional keys: + ◆ size-limit: (optional) A quantity representing the maximum amount + of memory allocated to this volume, such as "512Mi" or "3G". Data + stored in an in-memory volume consumes the memory allocation of the + container that wrote the data. If size-limit is not specified, the + maximum size will be half the total memory limit of all containers. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + secret: Represents a secret stored in Secret Manager as a volume. + Additional keys: + ◆ secret: (required) The name of the secret in Secret Manager. Must + be a secret in the same project being deployed or be an alias mapped + in the run.googleapis.com/secrets annotation. + ◆ version: (required) The version of the secret to make available in + the volume. + ◆ path: (required) The relative path within the volume to mount that + version. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + Container Flags The following flags apply to a single container. If the --container flag is specified these flags may only be @@ -233,12 +443,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. @@ -447,7 +653,7 @@ FLAGS --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/hello:latest). --source=SOURCE The location of the source to build. If a Dockerfile is present @@ -465,6 +671,63 @@ FLAGS global .gitignore is not respected. For more information on .gcloudignore, see gcloud topic gcloudignore. + At most one of these can be specified: + + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". + + --clear-binary-authorization + Remove any previously set Binary Authorization policy. + + Specify config map to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. The values associated with each of + these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may + omit the key within the config map to specify a mount of all keys within + the config map. For example: + '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will + create a volume with config map 'myconfig' and mount that volume at + '/my/path'. Because no config map key was specified, all keys in + 'myconfig' will be included. An environment variable named ENV will also + be created whose value is the value of 'key.json' in 'otherconfig. Not + supported on the fully managed version of Cloud Run. + + At most one of these can be specified: + + --clear-config-maps + Remove all config-maps. + + --set-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. All existing + config-maps will be removed first. + + Only --update-config-maps and --remove-config-maps can be used together. + If both are specified, --remove-config-maps will be applied first. + + --remove-config-maps=[KEY,...] + List of config-maps to be removed. + + --update-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. + + At most one of these can be specified: + + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. + + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server after + CMEK key revocation is detected. + + At most one of these can be specified: + + --clear-key + Remove any previously set CMEK key reference. + + --key=KEY + CMEK key reference to encrypt the container with. + At most one of these can be specified: --clear-labels @@ -496,428 +759,53 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - --connectivity=CONNECTIVITY - (DEPRECATED) Defaults to 'external'. If 'external', the service can - be invoked through the internet, in addition to through the cluster - network. - - The --connectivity flag is deprecated but will continue to be - supported. Prefer to use the --ingress flag instead. CONNECTIVITY - must be one of: - - external - Visible from outside the cluster. - internal - Visible only within the cluster. - - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. - - At most one of these can be specified: - - --clear-config-maps - Remove all config-maps. - - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used - together. If both are specified, --remove-config-maps will be applied - first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --[no-]allow-unauthenticated - Whether to enable allowing unauthenticated access to the service. - This may take a few moments to take effect. Use - --allow-unauthenticated to enable and --no-allow-unauthenticated to - disable. - - --breakglass=JUSTIFICATION - Justification to bypass Binary Authorization policy constraints and - allow the operation. See - https://cloud.google.com/binary-authorization/docs/using-breakglass - for more information. Next update or deploy command will - automatically clear existing breakglass justification. - - --clear-vpc-connector - Remove the VPC connector for this resource. - - --[no-]cpu-boost - Whether to allocate extra CPU to containers on startup to reduce the - perceived latency of a cold start request. Enabled by default when - unspecified on new services. Use --cpu-boost to enable and - --no-cpu-boost to disable. - - --[no-]cpu-throttling - Whether to throttle the CPU when the container is not actively - serving requests. Use --cpu-throttling to enable and - --no-cpu-throttling to disable. - - --[no-]default-url - Toggles the default url for a run service. This is enabled by default - if not specified. Use --default-url to enable and --no-default-url to - disable. - - --delegate-builds - Specifies that the source deploy for run will use the Build API to - submit the build. - - --[no-]deploy-health-check - Schedules a single instance of the Revision and waits for it to pass - its startup probe for the deployment to succeed. If disabled, the - startup probe runs only when the revision is first started via - invocation or by setting min-instances. This check is enabled by - default when unspecified. Use --deploy-health-check to enable and - --no-deploy-health-check to disable. - - --description=DESCRIPTION - Provides an optional, human-readable description of the service. - - --execution-environment=EXECUTION_ENVIRONMENT - Selects the execution environment where the application will run. - EXECUTION_ENVIRONMENT must be one of: - - gen1 - Run the application in a first generation execution environment. - gen2 - Run the application in a second generation execution environment. - - --[no-]invoker-iam-check - Optionally disable invoker IAM checks. This feature is available by - invitation only. More info at - https://cloud.google.com/run/docs/securing/managing-access#invoker_check. - Use --invoker-iam-check to enable and --no-invoker-iam-check to - disable. - - --max-surge=MAX_SURGE - A maximum percentage of instances that will be moved in each step of - traffic split changes. Use "default" to unset the limit and use the - platform default. - - --max-unavailable=MAX_UNAVAILABLE - A maximum percentage of instances that may be unavailable during - traffic split changes. Use "default" to unset the limit and use the - platform default. - - --mesh=MESH - Enables Cloud Service Mesh using the specified mesh resource name. - Mesh resource name must be in the format of - projects/PROJECT/locations/global/meshes/MESH_NAME. - - --remove-containers=[CONTAINER,...] - List of containers to remove. - - --revision-suffix=REVISION_SUFFIX - Specify the suffix of the revision name. Revision names always start - with the service name automatically. For example, specifying - [--revision-suffix=v1] for a service named 'helloworld', would lead - to a revision named 'helloworld-v1'. Set empty string to clear the - suffix and resume server-assigned naming. - - --scaling=SCALING - The scaling mode to use for this resource. SCALING must be one of: - - automatic - The number of instances is scaled automatically based on the - usage metrics. - manual - The number of instances is fixed to a provided config value. - - --service-max-instances=SERVICE_MAX_INSTANCES - The maximum number of container instances for this Service to run. - This instance limit will be divided among all Revisions receiving a - percentage of traffic. Once service-max-instances is enabled for a - service, it cannot be disabled. - - --service-min-instances=SERVICE_MIN_INSTANCES - The minimum number of container instances for this Service to run or - 'default' to remove any minimum. These instances will be divided - among all Revisions receiving a percentage of traffic. - - --[no-]session-affinity - Whether to enable session affinity for connections to the service. - Use --session-affinity to enable and --no-session-affinity to - disable. - - --vpc-connector=VPC_CONNECTOR - Set a VPC connector for this resource. - - --vpc-egress=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 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 Direct VPC egress or the VPC - connector. - private-ranges-only - 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 region as your Cloud Run service; otherwise specify - :: for the instance. - - At most one of these can be specified: - - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Append the given values to the current Cloud SQL instances. - - --clear-cloudsql-instances - Empty the current Cloud SQL instances. - - --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Remove the given values from the current Cloud SQL instances. - - --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Completely replace the current Cloud SQL instances with the given - values. - - These flags modify the custom audiences that can be used in the audience - field of ID token for authenticated requests. - - At most one of these can be specified: - - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - Append the given values to the current custom audiences. - - --clear-custom-audiences - Empty the current custom audiences. - - --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - Remove the given values from the current custom audiences. - - --set-custom-audiences=[CUSTOM-AUDIENCES,...] - Completely replace the current custom audiences with the given - values. - - --add-volume=[KEY=VALUE,...] - Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: - - cloud-storage: A volume representing a Cloud Storage bucket. This - volume type is mounted using Cloud Storage FUSE. See - https://cloud.google.com/storage/docs/gcs-fuse for the details and - limitations of this filesystem. Additional keys: - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags - should be specified without leading dashes and separated by - semicolons. - ◆ bucket: (optional) the name of the bucket to use as the source of - this volume. - ◆ dynamic-mounting: (optional) A boolean. If true, the volume will be - mounted dynamically. Note: You will either need to specify a bucket or - set dynamic-mounting to true, but not both. - - in-memory: An ephemeral volume that stores data in the instance's memory. - With this type of volume, data is not shared between instances and all - data will be lost when the instance it is on is terminated. Additional - keys: - ◆ size-limit: (optional) A quantity representing the maximum amount of - memory allocated to this volume, such as "512Mi" or "3G". Data stored - in an in-memory volume consumes the memory allocation of the container - that wrote the data. If size-limit is not specified, the maximum size - will be half the total memory limit of all containers. - - nfs: Represents a volume backed by an NFS server. Additional keys: - ◆ location: (required) The location of the NFS Server, in the form - SERVER:/PATH - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - - secret: Represents a secret stored in Secret Manager as a volume. - Additional keys: - ◆ secret: (required) The name of the secret in Secret Manager. Must be - a secret in the same project being deployed or be an alias mapped in - the run.googleapis.com/secrets annotation. - ◆ version: (required) The version of the secret to make available in - the volume. - ◆ path: (required) The relative path within the volume to mount that - version. - - --clear-volumes - Remove all existing volumes from the Cloud Run resource, including - volumes mounted as secrets - - --remove-volume=[VOLUME,...] - Removes volumes from the Cloud Run resource. - - At most one of these can be specified: - - --binary-authorization=POLICY - Binary Authorization policy to check against. This must be set to - "default". - - --clear-binary-authorization - Remove any previously set Binary Authorization policy. - - At most one of these can be specified: - - --clear-encryption-key-shutdown-hours - Remove any previously set CMEK key shutdown hours setting. - - --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - The number of hours to wait before an automatic shutdown server - after CMEK key revocation is detected. - - At most one of these can be specified: - - --clear-key - Remove any previously set CMEK key reference. - - --key=KEY - CMEK key reference to encrypt the container with. - - At most one of these can be specified: - - --clear-network - Disconnect this Cloud Run service from the VPC network it is - connected to. - - Direct VPC egress setting flags group. - - --network=NETWORK - The VPC network that the Cloud Run service will be able to send - traffic to. If --subnet is also specified, subnet must be a - subnetwork of the network specified by this --network flag. To - clear existing VPC network settings, use --clear-network. - - --subnet=SUBNET - The VPC subnetwork that the Cloud Run service will get IPs from. - The subnetwork must be /26 or larger. If --network is also - specified, subnet must be a subnetwork of the network specified - by the --network flag. If --network is not specified, network - will be looked up from this subnetwork. To clear existing VPC - network settings, use --clear-network. - - At most one of these can be specified: - - --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. - - --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. - - At most one of these can be specified: - - --clear-post-key-revocation-action-type - Remove any previously set post CMEK key revocation action type. - - --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE - Action type after CMEK key revocation. - POST_KEY_REVOCATION_ACTION_TYPE must be one of: - - prevent-new - No new instances will be started after CMEK key revocation. - shut-down - No new instances will be started and the existing instances - will be shut down after CMEK key revocation. - - Arguments to locate resources, depending on the platform used. + At most one of these can be specified: + + --clear-network + Disconnect this Cloud Run service from the VPC network it is + connected to. + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run service will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. + + --subnet=SUBNET + The VPC subnetwork that the Cloud Run service will get IPs from. + The subnetwork must be /26 or larger. If --network is also + specified, subnet must be a subnetwork of the network specified by + the --network flag. If --network is not specified, network will be + looked up from this subnetwork. To clear existing VPC network + settings, use --clear-network. + + At most one of these can be specified: + + --clear-network-tags + Clears all existing Compute Engine tags from the Cloud Run + service. + + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. To clear existing tags, use + --clear-network-tags. At most one of these can be specified: - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. + --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE + Action type after CMEK key revocation. + POST_KEY_REVOCATION_ACTION_TYPE must be one of: - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▸ set the property run/cluster with a fully specified name; - ▸ specify the cluster from a list of available clusters with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the - cluster. - - To set the cluster attribute: - ▫ provide the argument --cluster on the command line; - ▫ set the property run/cluster; - ▫ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ▫ provide the argument --cluster on the command line with a - fully specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --cluster-location on the command line; - ▫ set the property run/cluster_location; - ▫ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + prevent-new + No new instances will be started after CMEK key revocation. + shut-down + No new instances will be started and the existing instances will + be shut down after CMEK key revocation. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/domain-mappings/create b/gcloud/alpha/run/domain-mappings/create index c9434afc2..467a7c15e 100644 --- a/gcloud/alpha/run/domain-mappings/create +++ b/gcloud/alpha/run/domain-mappings/create @@ -4,10 +4,7 @@ NAME SYNOPSIS gcloud alpha run domain-mappings create --service=SERVICE (--domain=DOMAIN : --namespace=NAMESPACE) [--force-override] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create domain mappings. @@ -56,85 +53,9 @@ OPTIONAL FLAGS --force-override Map this domain even if it is already mapped to another service. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/domain-mappings/delete b/gcloud/alpha/run/domain-mappings/delete index f3881da0a..72303f045 100644 --- a/gcloud/alpha/run/domain-mappings/delete +++ b/gcloud/alpha/run/domain-mappings/delete @@ -4,10 +4,7 @@ NAME SYNOPSIS gcloud alpha run domain-mappings delete (--domain=DOMAIN : --namespace=NAMESPACE) [--[no-]async] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Delete domain mappings. @@ -51,89 +48,12 @@ REQUIRED FLAGS OPTIONAL FLAGS --[no-]async Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async for Cloud Run (fully managed) and - --async for Cloud Run for Anthos. Use --async to enable and --no-async + complete. Defaults to --no-async. Use --async to enable and --no-async to disable. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/domain-mappings/describe b/gcloud/alpha/run/domain-mappings/describe index b95a8877c..a5778e8a2 100644 --- a/gcloud/alpha/run/domain-mappings/describe +++ b/gcloud/alpha/run/domain-mappings/describe @@ -3,11 +3,8 @@ NAME SYNOPSIS gcloud alpha run domain-mappings describe - (--domain=DOMAIN : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + (--domain=DOMAIN : --namespace=NAMESPACE) [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Describe domain mappings. @@ -49,85 +46,9 @@ REQUIRED FLAGS ▸ set the property core/project. OPTIONAL FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/domain-mappings/help b/gcloud/alpha/run/domain-mappings/help index aa4e87b38..7e6e794b9 100644 --- a/gcloud/alpha/run/domain-mappings/help +++ b/gcloud/alpha/run/domain-mappings/help @@ -3,11 +3,8 @@ NAME mappings SYNOPSIS - gcloud alpha run domain-mappings COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud alpha run domain-mappings COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This set of commands can be used to view and manage your service's @@ -19,85 +16,9 @@ EXAMPLES $ gcloud alpha run domain-mappings list FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/run/domain-mappings/list b/gcloud/alpha/run/domain-mappings/list index aa20f2305..a979cff61 100644 --- a/gcloud/alpha/run/domain-mappings/list +++ b/gcloud/alpha/run/domain-mappings/list @@ -3,11 +3,8 @@ NAME SYNOPSIS gcloud alpha run domain-mappings list [--namespace=NAMESPACE] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -19,104 +16,23 @@ EXAMPLES $ gcloud alpha run domain-mappings list FLAGS - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: + Namespace resource - Namespace to list domain mappings in. This represents + a Cloud resource. - Namespace resource - Namespace to list domain mappings in. This - represents a Cloud resource. + --namespace=NAMESPACE + ID of the namespace or fully qualified identifier for the namespace. - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. + To set the namespace attribute: + ▸ provide the argument --namespace on the command line; + ▸ set the property run/namespace; + ▸ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▸ provide the argument project on the command line; + ▸ set the property core/project. - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/run/jobs/create b/gcloud/alpha/run/jobs/create index 82e7a6058..7d9f07d6c 100644 --- a/gcloud/alpha/run/jobs/create +++ b/gcloud/alpha/run/jobs/create @@ -96,10 +96,9 @@ FLAGS property [run/region]. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. This is the email address - of an IAM service account. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] You can specify a name of a Cloud SQL instance if it's in the same @@ -227,12 +226,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. diff --git a/gcloud/alpha/run/jobs/deploy b/gcloud/alpha/run/jobs/deploy index b74cdfee4..3b062bec3 100644 --- a/gcloud/alpha/run/jobs/deploy +++ b/gcloud/alpha/run/jobs/deploy @@ -101,10 +101,9 @@ FLAGS List of containers to remove. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. This is the email address - of an IAM service account. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] You can specify a name of a Cloud SQL instance if it's in the same @@ -233,12 +232,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. diff --git a/gcloud/alpha/run/jobs/update b/gcloud/alpha/run/jobs/update index 328a1477b..fdaf91b8b 100644 --- a/gcloud/alpha/run/jobs/update +++ b/gcloud/alpha/run/jobs/update @@ -96,10 +96,9 @@ FLAGS List of containers to remove. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. This is the email address - of an IAM service account. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. --task-timeout=TASK_TIMEOUT Set the maximum time (deadline) a job task attempt can run for. In the @@ -243,12 +242,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. diff --git a/gcloud/alpha/run/multi-region-services/delete b/gcloud/alpha/run/multi-region-services/delete index 41c4f9cbb..dcdfb74bd 100644 --- a/gcloud/alpha/run/multi-region-services/delete +++ b/gcloud/alpha/run/multi-region-services/delete @@ -4,11 +4,8 @@ NAME SYNOPSIS gcloud alpha run multi-region-services delete - (SERVICE : --namespace=NAMESPACE) [--[no-]async] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + (SERVICE : --namespace=NAMESPACE) [--[no-]async] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Deletes a multi-region service. @@ -50,89 +47,12 @@ POSITIONAL ARGUMENTS FLAGS --[no-]async Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async for Cloud Run (fully managed) and - --async for Cloud Run for Anthos. Use --async to enable and --no-async + complete. Defaults to --no-async. Use --async to enable and --no-async to disable. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/multi-region-services/describe b/gcloud/alpha/run/multi-region-services/describe index b984c18a1..c22ab83ca 100644 --- a/gcloud/alpha/run/multi-region-services/describe +++ b/gcloud/alpha/run/multi-region-services/describe @@ -4,11 +4,8 @@ NAME SYNOPSIS gcloud alpha run multi-region-services describe - (SERVICE : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + (SERVICE : --namespace=NAMESPACE) [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Command to describe a multi-region service. @@ -59,85 +56,9 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/multi-region-services/help b/gcloud/alpha/run/multi-region-services/help index a05adc279..a0b6af9d8 100644 --- a/gcloud/alpha/run/multi-region-services/help +++ b/gcloud/alpha/run/multi-region-services/help @@ -3,11 +3,8 @@ NAME services SYNOPSIS - gcloud alpha run multi-region-services COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud alpha run multi-region-services COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) The gcloud run multi-region-services command group lets you deploy @@ -23,85 +20,9 @@ EXAMPLES $ gcloud run deploy --help FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/run/multi-region-services/list b/gcloud/alpha/run/multi-region-services/list index 8c7484add..d10cee7c9 100644 --- a/gcloud/alpha/run/multi-region-services/list +++ b/gcloud/alpha/run/multi-region-services/list @@ -3,13 +3,9 @@ NAME services SYNOPSIS - gcloud alpha run multi-region-services list [--namespace=NAMESPACE] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha run multi-region-services list [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) List available multi-region services. @@ -20,104 +16,9 @@ EXAMPLES $ gcloud alpha run multi-region-services list FLAGS - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to list services in. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/run/multi-region-services/replace b/gcloud/alpha/run/multi-region-services/replace index 4d59fccf6..95c00a4cc 100644 --- a/gcloud/alpha/run/multi-region-services/replace +++ b/gcloud/alpha/run/multi-region-services/replace @@ -4,10 +4,7 @@ NAME SYNOPSIS gcloud alpha run multi-region-services replace FILE [--async] [--dry-run] - [--namespace=NAMESPACE] [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates or replaces a service from a YAML service specification. @@ -31,104 +28,9 @@ FLAGS If set to true, only validates the configuration. The configuration will not be applied. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to replace service. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/multi-region-services/update b/gcloud/alpha/run/multi-region-services/update index 11f42861c..ff3261b40 100644 --- a/gcloud/alpha/run/multi-region-services/update +++ b/gcloud/alpha/run/multi-region-services/update @@ -5,12 +5,34 @@ NAME SYNOPSIS gcloud alpha run multi-region-services update - [[SERVICE] --namespace=NAMESPACE] [--async] [--concurrency=CONCURRENCY] - [--container=CONTAINER] [--ingress=INGRESS; default="all"] - [--max-instances=MAX_INSTANCES] [--min-instances=MIN_INSTANCES] - [--platform=PLATFORM; default="managed"] - [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] - [--no-traffic] + [[SERVICE] --namespace=NAMESPACE] [--async] + [--breakglass=JUSTIFICATION] [--clear-vpc-connector] + [--concurrency=CONCURRENCY] [--container=CONTAINER] [--[no-]cpu-boost] + [--[no-]cpu-throttling] [--[no-]default-url] + [--[no-]deploy-health-check] [--description=DESCRIPTION] + [--execution-environment=EXECUTION_ENVIRONMENT] + [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] + [--max-instances=MAX_INSTANCES] [--max-surge=MAX_SURGE] + [--max-unavailable=MAX_UNAVAILABLE] [--mesh=MESH] + [--min-instances=MIN_INSTANCES] [--region=REGION] + [--remove-containers=[CONTAINER,...]] + [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] + [--service-account=SERVICE_ACCOUNT] + [--service-max-instances=SERVICE_MAX_INSTANCES] + [--service-min-instances=SERVICE_MIN_INSTANCES] + [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] + [--no-traffic] [--vpc-connector=VPC_CONNECTOR] + [--vpc-egress=VPC_EGRESS] + [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --clear-cloudsql-instances + | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--add-custom-audiences=[CUSTOM-AUDIENCES,...] + | --clear-custom-audiences + | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + | --set-custom-audiences=[CUSTOM-AUDIENCES,...]] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE --memory=MEMORY @@ -20,40 +42,21 @@ SYNOPSIS --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] - [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost - --[no-]cpu-throttling --[no-]default-url --[no-]deploy-health-check - --description=DESCRIPTION - --execution-environment=EXECUTION_ENVIRONMENT - --[no-]invoker-iam-check --max-surge=MAX_SURGE - --max-unavailable=MAX_UNAVAILABLE --mesh=MESH - --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX - --scaling=SCALING --service-max-instances=SERVICE_MAX_INSTANCES - --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity - --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --clear-cloudsql-instances - | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - | --clear-custom-audiences - | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --add-volume=[KEY=VALUE,...] --clear-volumes - --remove-volume=[VOLUME,...] --binary-authorization=POLICY - | --clear-binary-authorization --clear-encryption-key-shutdown-hours - | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - --clear-key | --key=KEY --clear-network - | --network=NETWORK --subnet=SUBNET --clear-network-tags - | --network-tags=[TAG,...] --clear-post-key-revocation-action-type - | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [--binary-authorization=POLICY | --clear-binary-authorization] + [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] + | --remove-config-maps=[KEY,...] + --update-config-maps=[KEY=VALUE,...]] + [--clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] + [--clear-key | --key=KEY] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] - [--connectivity=CONNECTIVITY --clear-config-maps - | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAG,...]] + [--clear-post-key-revocation-action-type + | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update environment variables, add/remove regions, and other @@ -97,6 +100,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. + + --clear-vpc-connector + Remove the VPC connector for this resource. + --concurrency=CONCURRENCY Set the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified or provide the special value @@ -106,64 +119,134 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + --[no-]cpu-boost + Whether to allocate extra CPU to containers on startup to reduce the + perceived latency of a cold start request. Enabled by default when + unspecified on new services. Use --cpu-boost to enable and + --no-cpu-boost to disable. + + --[no-]cpu-throttling + Whether to throttle the CPU when the container is not actively serving + requests. Use --cpu-throttling to enable and --no-cpu-throttling to + disable. + + --[no-]default-url + Toggles the default url for a run service. This is enabled by default + if not specified. Use --default-url to enable and --no-default-url to + disable. + + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + + --description=DESCRIPTION + Provides an optional, human-readable description of the service. + + --execution-environment=EXECUTION_ENVIRONMENT + Selects the execution environment where the application will run. + EXECUTION_ENVIRONMENT must be one of: + + gen1 + Run the application in a first generation execution environment. + gen2 + Run the application in a second generation execution environment. + --ingress=INGRESS; default="all" Set the ingress traffic sources allowed to call the service. For Cloud - Run (fully managed) the --[no-]allow-unauthenticated flag separately - controls the identities allowed to call the service. INGRESS must be - one of: + Run the --[no-]allow-unauthenticated flag separately controls the + identities allowed to call the service. INGRESS must be one of: all Inbound requests from all sources are allowed. internal - For Cloud Run (fully managed), only inbound requests from VPC - networks in the same project or VPC Service Controls perimeter, as - well as Pub/Sub subscriptions and Eventarc events in the same - project or VPC Service Controls perimeter are allowed. All other - requests are rejected. See - https://cloud.google.com/run/docs/securing/ingress for full details - on the definition of internal traffic for Cloud Run (fully - managed). For Cloud Run for Anthos, only inbound requests from the - same cluster are allowed. + For Cloud Run, only inbound requests from VPC networks in the same + project or VPC Service Controls perimeter, as well as Pub/Sub + subscriptions and Eventarc events in the same project or VPC + Service Controls perimeter are allowed. All other requests are + rejected. See https://cloud.google.com/run/docs/securing/ingress + for full details on the definition of internal traffic for Cloud + Run. internal-and-cloud-load-balancing - Only supported for Cloud Run (fully managed). Only inbound requests - from Google Cloud Load Balancing or a traffic source allowed by the - internal option are allowed. + Only inbound requests from Google Cloud Load Balancing or a traffic + source allowed by the internal option are allowed. + + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. --max-instances=MAX_INSTANCES The maximum number of container instances of the Service to run. Use 'default' to unset the limit and use the platform default. + --max-surge=MAX_SURGE + A maximum percentage of instances that will be moved in each step of + traffic split changes. Use "default" to unset the limit and use the + platform default. + + --max-unavailable=MAX_UNAVAILABLE + A maximum percentage of instances that may be unavailable during + traffic split changes. Use "default" to unset the limit and use the + platform default. + + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. Mesh + resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + --min-instances=MIN_INSTANCES The minimum number of container instances for this Revision of the Service to run or 'default' to remove any minimum. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --remove-containers=[CONTAINER,...] + List of containers to remove. + + --revision-suffix=REVISION_SUFFIX + Specify the suffix of the revision name. Revision names always start + with the service name automatically. For example, specifying + [--revision-suffix=v1] for a service named 'helloworld', would lead to + a revision named 'helloworld-v1'. Set empty string to clear the suffix + and resume server-assigned naming. + + --scaling=SCALING + The scaling mode to use for this resource. SCALING must be one of: + + automatic + The number of instances is scaled automatically based on the usage + metrics. + manual + The number of instances is fixed to a provided config value. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. For the managed platform, - this is the email address of an IAM service account. For the - Kubernetes-based platforms (gke, kubernetes), this is the name of a - Kubernetes service account in the same namespace as the service. If not - provided, the revision will use the default service account of the - project, or default Kubernetes namespace service account respectively. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. + + --service-max-instances=SERVICE_MAX_INSTANCES + The maximum number of container instances for this Service to run. This + instance limit will be divided among all Revisions receiving a + percentage of traffic. Once service-max-instances is enabled for a + service, it cannot be disabled. + + --service-min-instances=SERVICE_MIN_INSTANCES + The minimum number of container instances for this Service to run or + 'default' to remove any minimum. These instances will be divided among + all Revisions receiving a percentage of traffic. + + --[no-]session-affinity + Whether to enable session affinity for connections to the service. Use + --session-affinity to enable and --no-session-affinity to disable. --tag=TAG Traffic tag to assign to the newly created revision. @@ -185,6 +268,84 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. + --vpc-connector=VPC_CONNECTOR + Set a VPC connector for this resource. + + --vpc-egress=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 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 Direct VPC egress or the VPC + connector. + private-ranges-only + 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 + region as your Cloud Run service; otherwise specify + :: for the instance. + + At most one of these can be specified: + + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Append the given values to the current Cloud SQL instances. + + --clear-cloudsql-instances + Empty the current Cloud SQL instances. + + --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Remove the given values from the current Cloud SQL instances. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Completely replace the current Cloud SQL instances with the given + values. + + These flags modify the custom audiences that can be used in the audience + field of ID token for authenticated requests. + + At most one of these can be specified: + + --add-custom-audiences=[CUSTOM-AUDIENCES,...] + Append the given values to the current custom audiences. + + --clear-custom-audiences + Empty the current custom audiences. + + --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + Remove the given values from the current custom audiences. + + --set-custom-audiences=[CUSTOM-AUDIENCES,...] + Completely replace the current custom audiences with the given + values. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + Container Flags If the --container or --remove-containers flag is specified the following @@ -214,19 +375,15 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/hello:latest). --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. @@ -301,263 +458,62 @@ FLAGS --update-secrets=[KEY=VALUE,...] List of key-value pairs to set as secrets. - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + At most one of these can be specified: - --breakglass=JUSTIFICATION - Justification to bypass Binary Authorization policy constraints and - allow the operation. See - https://cloud.google.com/binary-authorization/docs/using-breakglass - for more information. Next update or deploy command will - automatically clear existing breakglass justification. + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". - --clear-vpc-connector - Remove the VPC connector for this resource. + --clear-binary-authorization + Remove any previously set Binary Authorization policy. - --[no-]cpu-boost - Whether to allocate extra CPU to containers on startup to reduce the - perceived latency of a cold start request. Enabled by default when - unspecified on new services. Use --cpu-boost to enable and - --no-cpu-boost to disable. + Specify config map to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. The values associated with each of + these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may + omit the key within the config map to specify a mount of all keys within + the config map. For example: + '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will + create a volume with config map 'myconfig' and mount that volume at + '/my/path'. Because no config map key was specified, all keys in + 'myconfig' will be included. An environment variable named ENV will also + be created whose value is the value of 'key.json' in 'otherconfig. Not + supported on the fully managed version of Cloud Run. - --[no-]cpu-throttling - Whether to throttle the CPU when the container is not actively - serving requests. Use --cpu-throttling to enable and - --no-cpu-throttling to disable. + At most one of these can be specified: - --[no-]default-url - Toggles the default url for a run service. This is enabled by default - if not specified. Use --default-url to enable and --no-default-url to - disable. + --clear-config-maps + Remove all config-maps. - --[no-]deploy-health-check - Schedules a single instance of the Revision and waits for it to pass - its startup probe for the deployment to succeed. If disabled, the - startup probe runs only when the revision is first started via - invocation or by setting min-instances. This check is enabled by - default when unspecified. Use --deploy-health-check to enable and - --no-deploy-health-check to disable. + --set-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. All existing + config-maps will be removed first. - --description=DESCRIPTION - Provides an optional, human-readable description of the service. + Only --update-config-maps and --remove-config-maps can be used together. + If both are specified, --remove-config-maps will be applied first. - --execution-environment=EXECUTION_ENVIRONMENT - Selects the execution environment where the application will run. - EXECUTION_ENVIRONMENT must be one of: + --remove-config-maps=[KEY,...] + List of config-maps to be removed. - gen1 - Run the application in a first generation execution environment. - gen2 - Run the application in a second generation execution environment. + --update-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. - --[no-]invoker-iam-check - Optionally disable invoker IAM checks. This feature is available by - invitation only. More info at - https://cloud.google.com/run/docs/securing/managing-access#invoker_check. - Use --invoker-iam-check to enable and --no-invoker-iam-check to - disable. + At most one of these can be specified: - --max-surge=MAX_SURGE - A maximum percentage of instances that will be moved in each step of - traffic split changes. Use "default" to unset the limit and use the - platform default. + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. - --max-unavailable=MAX_UNAVAILABLE - A maximum percentage of instances that may be unavailable during - traffic split changes. Use "default" to unset the limit and use the - platform default. + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server after + CMEK key revocation is detected. - --mesh=MESH - Enables Cloud Service Mesh using the specified mesh resource name. - Mesh resource name must be in the format of - projects/PROJECT/locations/global/meshes/MESH_NAME. + At most one of these can be specified: - --remove-containers=[CONTAINER,...] - List of containers to remove. + --clear-key + Remove any previously set CMEK key reference. - --revision-suffix=REVISION_SUFFIX - Specify the suffix of the revision name. Revision names always start - with the service name automatically. For example, specifying - [--revision-suffix=v1] for a service named 'helloworld', would lead - to a revision named 'helloworld-v1'. Set empty string to clear the - suffix and resume server-assigned naming. - - --scaling=SCALING - The scaling mode to use for this resource. SCALING must be one of: - - automatic - The number of instances is scaled automatically based on the - usage metrics. - manual - The number of instances is fixed to a provided config value. - - --service-max-instances=SERVICE_MAX_INSTANCES - The maximum number of container instances for this Service to run. - This instance limit will be divided among all Revisions receiving a - percentage of traffic. Once service-max-instances is enabled for a - service, it cannot be disabled. - - --service-min-instances=SERVICE_MIN_INSTANCES - The minimum number of container instances for this Service to run or - 'default' to remove any minimum. These instances will be divided - among all Revisions receiving a percentage of traffic. - - --[no-]session-affinity - Whether to enable session affinity for connections to the service. - Use --session-affinity to enable and --no-session-affinity to - disable. - - --vpc-connector=VPC_CONNECTOR - Set a VPC connector for this resource. - - --vpc-egress=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 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 Direct VPC egress or the VPC - connector. - private-ranges-only - 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 region as your Cloud Run service; otherwise specify - :: for the instance. - - At most one of these can be specified: - - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Append the given values to the current Cloud SQL instances. - - --clear-cloudsql-instances - Empty the current Cloud SQL instances. - - --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Remove the given values from the current Cloud SQL instances. - - --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Completely replace the current Cloud SQL instances with the given - values. - - These flags modify the custom audiences that can be used in the audience - field of ID token for authenticated requests. - - At most one of these can be specified: - - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - Append the given values to the current custom audiences. - - --clear-custom-audiences - Empty the current custom audiences. - - --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - Remove the given values from the current custom audiences. - - --set-custom-audiences=[CUSTOM-AUDIENCES,...] - Completely replace the current custom audiences with the given - values. - - --add-volume=[KEY=VALUE,...] - Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: - - --clear-volumes - Remove all existing volumes from the Cloud Run resource, including - volumes mounted as secrets - - --remove-volume=[VOLUME,...] - Removes volumes from the Cloud Run resource. - - At most one of these can be specified: - - --binary-authorization=POLICY - Binary Authorization policy to check against. This must be set to - "default". - - --clear-binary-authorization - Remove any previously set Binary Authorization policy. - - At most one of these can be specified: - - --clear-encryption-key-shutdown-hours - Remove any previously set CMEK key shutdown hours setting. - - --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - The number of hours to wait before an automatic shutdown server - after CMEK key revocation is detected. - - At most one of these can be specified: - - --clear-key - Remove any previously set CMEK key reference. - - --key=KEY - CMEK key reference to encrypt the container with. - - At most one of these can be specified: - - --clear-network - Disconnect this Cloud Run service from the VPC network it is - connected to. - - Direct VPC egress setting flags group. - - --network=NETWORK - The VPC network that the Cloud Run service will be able to send - traffic to. If --subnet is also specified, subnet must be a - subnetwork of the network specified by this --network flag. To - clear existing VPC network settings, use --clear-network. - - --subnet=SUBNET - The VPC subnetwork that the Cloud Run service will get IPs from. - The subnetwork must be /26 or larger. If --network is also - specified, subnet must be a subnetwork of the network specified - by the --network flag. If --network is not specified, network - will be looked up from this subnetwork. To clear existing VPC - network settings, use --clear-network. - - At most one of these can be specified: - - --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. - - --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. - - At most one of these can be specified: - - --clear-post-key-revocation-action-type - Remove any previously set post CMEK key revocation action type. - - --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE - Action type after CMEK key revocation. - POST_KEY_REVOCATION_ACTION_TYPE must be one of: - - prevent-new - No new instances will be started after CMEK key revocation. - shut-down - No new instances will be started and the existing instances - will be shut down after CMEK key revocation. + --key=KEY + CMEK key reference to encrypt the container with. At most one of these can be specified: @@ -590,119 +546,53 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: + At most one of these can be specified: - --connectivity=CONNECTIVITY - (DEPRECATED) Defaults to 'external'. If 'external', the service can - be invoked through the internet, in addition to through the cluster - network. + --clear-network + Disconnect this Cloud Run service from the VPC network it is + connected to. - The --connectivity flag is deprecated but will continue to be - supported. Prefer to use the --ingress flag instead. CONNECTIVITY - must be one of: + Direct VPC egress setting flags group. - external - Visible from outside the cluster. - internal - Visible only within the cluster. + --network=NETWORK + The VPC network that the Cloud Run service will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. + --subnet=SUBNET + The VPC subnetwork that the Cloud Run service will get IPs from. + The subnetwork must be /26 or larger. If --network is also + specified, subnet must be a subnetwork of the network specified by + the --network flag. If --network is not specified, network will be + looked up from this subnetwork. To clear existing VPC network + settings, use --clear-network. - At most one of these can be specified: + At most one of these can be specified: - --clear-config-maps - Remove all config-maps. + --clear-network-tags + Clears all existing Compute Engine tags from the Cloud Run + service. - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used - together. If both are specified, --remove-config-maps will be applied - first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - - Arguments to locate resources, depending on the platform used. + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. To clear existing tags, use + --clear-network-tags. At most one of these can be specified: - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. + --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE + Action type after CMEK key revocation. + POST_KEY_REVOCATION_ACTION_TYPE must be one of: - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▸ set the property run/cluster with a fully specified name; - ▸ specify the cluster from a list of available clusters with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the - cluster. - - To set the cluster attribute: - ▫ provide the argument --cluster on the command line; - ▫ set the property run/cluster; - ▫ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ▫ provide the argument --cluster on the command line with a - fully specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --cluster-location on the command line; - ▫ set the property run/cluster_location; - ▫ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + prevent-new + No new instances will be started after CMEK key revocation. + shut-down + No new instances will be started and the existing instances will + be shut down after CMEK key revocation. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/regions/help b/gcloud/alpha/run/regions/help index 842e3beb1..eb9150247 100644 --- a/gcloud/alpha/run/regions/help +++ b/gcloud/alpha/run/regions/help @@ -2,27 +2,11 @@ NAME gcloud alpha run regions - view available Cloud Run (fully managed) regions SYNOPSIS - gcloud alpha run regions COMMAND [--platform=PLATFORM; default="managed"] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha run regions COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) View available Cloud Run (fully managed) regions. -FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Not supported by this - command. - kubernetes - Use a Knative-compatible kubernetes cluster. Not supported by this - command. - GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/run/regions/list b/gcloud/alpha/run/regions/list index 04cd3da04..7ba6109b3 100644 --- a/gcloud/alpha/run/regions/list +++ b/gcloud/alpha/run/regions/list @@ -3,9 +3,9 @@ NAME regions SYNOPSIS - gcloud alpha run regions list [--platform=PLATFORM; default="managed"] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + gcloud alpha run regions list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) List available Cloud Run (fully managed) regions. @@ -15,21 +15,6 @@ EXAMPLES $ gcloud alpha run regions list -FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Not supported by this - command. - kubernetes - Use a Knative-compatible kubernetes cluster. Not supported by this - command. - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/run/revisions/delete b/gcloud/alpha/run/revisions/delete index 53d84c1af..813279e62 100644 --- a/gcloud/alpha/run/revisions/delete +++ b/gcloud/alpha/run/revisions/delete @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud alpha run revisions delete (REVISION : --namespace=NAMESPACE) - [--[no-]async] [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--[no-]async] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Delete a revision. @@ -48,89 +45,12 @@ POSITIONAL ARGUMENTS FLAGS --[no-]async Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async for Cloud Run (fully managed) and - --async for Cloud Run for Anthos. Use --async to enable and --no-async + complete. Defaults to --no-async. Use --async to enable and --no-async to disable. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/revisions/describe b/gcloud/alpha/run/revisions/describe index f3f4e3db0..95416e55d 100644 --- a/gcloud/alpha/run/revisions/describe +++ b/gcloud/alpha/run/revisions/describe @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud alpha run revisions describe (REVISION : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Obtain details about revisions. @@ -46,85 +43,9 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/revisions/help b/gcloud/alpha/run/revisions/help index 4da298dbf..776e41d9e 100644 --- a/gcloud/alpha/run/revisions/help +++ b/gcloud/alpha/run/revisions/help @@ -2,11 +2,8 @@ NAME gcloud alpha run revisions - view and manage your Cloud Run revisions SYNOPSIS - gcloud alpha run revisions GROUP | COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud alpha run revisions GROUP | COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This set of commands can be used to view and manage your existing @@ -18,85 +15,9 @@ EXAMPLES $ gcloud alpha run revisions list FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/run/revisions/list b/gcloud/alpha/run/revisions/list index a92035917..953fdf11d 100644 --- a/gcloud/alpha/run/revisions/list +++ b/gcloud/alpha/run/revisions/list @@ -2,13 +2,9 @@ NAME gcloud alpha run revisions list - list available revisions SYNOPSIS - gcloud alpha run revisions list [--namespace=NAMESPACE] - [--platform=PLATFORM; default="managed"] [--service=SERVICE] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha run revisions list [--region=REGION] [--service=SERVICE] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) List available revisions. @@ -19,108 +15,13 @@ EXAMPLES $ gcloud alpha run revisions list --service=foo FLAGS - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to list revisions in. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. --service=SERVICE Limit matched revisions to the given service. - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/run/revisions/logs/help b/gcloud/alpha/run/revisions/logs/help index e4fbedafa..175ce60bf 100644 --- a/gcloud/alpha/run/revisions/logs/help +++ b/gcloud/alpha/run/revisions/logs/help @@ -2,95 +2,16 @@ NAME gcloud alpha run revisions logs - read logs for Cloud Run revisions SYNOPSIS - gcloud alpha run revisions logs COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud alpha run revisions logs COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Read logs for Cloud Run revisions. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/run/revisions/logs/read b/gcloud/alpha/run/revisions/logs/read index 96ecef246..79cc6714e 100644 --- a/gcloud/alpha/run/revisions/logs/read +++ b/gcloud/alpha/run/revisions/logs/read @@ -4,11 +4,7 @@ NAME SYNOPSIS gcloud alpha run revisions logs read REVISION [--freshness=FRESHNESS; default="1d"] [--log-filter=LOG_FILTER] - [--order=ORDER; default="desc"] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--limit=LIMIT] + [--order=ORDER; default="desc"] [--region=REGION] [--limit=LIMIT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -61,85 +57,9 @@ FLAGS Ordering of returned log entries based on timestamp field. ORDER must be one of: desc, asc. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --limit=LIMIT diff --git a/gcloud/alpha/run/revisions/logs/tail b/gcloud/alpha/run/revisions/logs/tail index a837ab375..b313c6ae4 100644 --- a/gcloud/alpha/run/revisions/logs/tail +++ b/gcloud/alpha/run/revisions/logs/tail @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud alpha run revisions logs tail REVISION [--log-filter=LOG_FILTER] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha run revisions logs tail tails log-entries for a @@ -36,85 +33,9 @@ FLAGS information about filters can be found at: https://cloud.google.com/logging/docs/view/logging-query-language - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/services/add-iam-policy-binding b/gcloud/alpha/run/services/add-iam-policy-binding index 62de24481..cb57a45f1 100644 --- a/gcloud/alpha/run/services/add-iam-policy-binding +++ b/gcloud/alpha/run/services/add-iam-policy-binding @@ -4,11 +4,9 @@ NAME SYNOPSIS gcloud alpha run services add-iam-policy-binding SERVICE --member=PRINCIPAL - --role=ROLE [--platform=PLATFORM; default="managed"] + --role=ROLE [--region=REGION] [--condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Add an IAM policy binding to the IAM policy of a Cloud Run service. @@ -74,22 +72,9 @@ REQUIRED FLAGS organizations/{ORGANIZATION_ID}/roles/logging.viewer. OPTIONAL FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. At most one of these can be specified: @@ -129,69 +114,6 @@ OPTIONAL FLAGS available fields, see the help for --condition. Use a full or relative path to a local file containing the value of condition. - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/run/services/delete b/gcloud/alpha/run/services/delete index 113188116..6fa6489b9 100644 --- a/gcloud/alpha/run/services/delete +++ b/gcloud/alpha/run/services/delete @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud alpha run services delete (SERVICE : --namespace=NAMESPACE) - [--[no-]async] [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--[no-]async] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Delete a service. @@ -48,89 +45,12 @@ POSITIONAL ARGUMENTS FLAGS --[no-]async Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async for Cloud Run (fully managed) and - --async for Cloud Run for Anthos. Use --async to enable and --no-async + complete. Defaults to --no-async. Use --async to enable and --no-async to disable. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/services/describe b/gcloud/alpha/run/services/describe index 3a02b1007..a186d2fd8 100644 --- a/gcloud/alpha/run/services/describe +++ b/gcloud/alpha/run/services/describe @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud alpha run services describe (SERVICE : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Obtain details about a given service. @@ -55,85 +52,9 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/services/get-iam-policy b/gcloud/alpha/run/services/get-iam-policy index 02f35a551..6dbea449d 100644 --- a/gcloud/alpha/run/services/get-iam-policy +++ b/gcloud/alpha/run/services/get-iam-policy @@ -3,13 +3,9 @@ NAME Run service SYNOPSIS - gcloud alpha run services get-iam-policy SERVICE - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha run services get-iam-policy SERVICE [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command gets the IAM policy for a service. If formatted as @@ -51,85 +47,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument service on the command line. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/run/services/help b/gcloud/alpha/run/services/help index b35c8adeb..abbad826b 100644 --- a/gcloud/alpha/run/services/help +++ b/gcloud/alpha/run/services/help @@ -2,11 +2,8 @@ NAME gcloud alpha run services - view and manage your Cloud Run services SYNOPSIS - gcloud alpha run services GROUP | COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud alpha run services GROUP | COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This set of commands can be used to view and manage your existing @@ -20,85 +17,9 @@ EXAMPLES $ gcloud alpha run services list FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/run/services/list b/gcloud/alpha/run/services/list index 5cb0cee80..c55ce3908 100644 --- a/gcloud/alpha/run/services/list +++ b/gcloud/alpha/run/services/list @@ -2,11 +2,7 @@ NAME gcloud alpha run services list - list available services SYNOPSIS - gcloud alpha run services list [--namespace=NAMESPACE] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] + gcloud alpha run services list [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -19,104 +15,9 @@ EXAMPLES $ gcloud alpha run services list FLAGS - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to list services in. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/run/services/logs/help b/gcloud/alpha/run/services/logs/help index 3a6088a1f..81808b961 100644 --- a/gcloud/alpha/run/services/logs/help +++ b/gcloud/alpha/run/services/logs/help @@ -2,95 +2,16 @@ NAME gcloud alpha run services logs - read logs for Cloud Run services SYNOPSIS - gcloud alpha run services logs COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud alpha run services logs COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Read logs for Cloud Run services. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/run/services/logs/read b/gcloud/alpha/run/services/logs/read index 3511e6aeb..852556829 100644 --- a/gcloud/alpha/run/services/logs/read +++ b/gcloud/alpha/run/services/logs/read @@ -4,11 +4,7 @@ NAME SYNOPSIS gcloud alpha run services logs read SERVICE [--freshness=FRESHNESS; default="1d"] [--log-filter=LOG_FILTER] - [--order=ORDER; default="desc"] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--limit=LIMIT] + [--order=ORDER; default="desc"] [--region=REGION] [--limit=LIMIT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -61,85 +57,9 @@ FLAGS Ordering of returned log entries based on timestamp field. ORDER must be one of: desc, asc. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --limit=LIMIT diff --git a/gcloud/alpha/run/services/logs/tail b/gcloud/alpha/run/services/logs/tail index 2350a765e..5e6b0d843 100644 --- a/gcloud/alpha/run/services/logs/tail +++ b/gcloud/alpha/run/services/logs/tail @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud alpha run services logs tail SERVICE [--log-filter=LOG_FILTER] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha run services logs tail tails log-entries for a @@ -36,85 +33,9 @@ FLAGS information about filters can be found at: https://cloud.google.com/logging/docs/view/logging-query-language - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/services/proxy b/gcloud/alpha/run/services/proxy index d42133680..0796e60ac 100644 --- a/gcloud/alpha/run/services/proxy +++ b/gcloud/alpha/run/services/proxy @@ -4,11 +4,8 @@ NAME SYNOPSIS gcloud alpha run services proxy (SERVICE : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] [--port=PORT] [--tag=TAG] - [--token=TOKEN] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--port=PORT] [--region=REGION] [--tag=TAG] [--token=TOKEN] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Runs a server on localhost that proxies requests to the specified @@ -60,27 +57,14 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - --port=PORT Local port number to expose the proxied service. If not specified, it will be set to 8080. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + --tag=TAG Traffic tag of the service to expose via the proxy. If not specified, the default service URL will be proxied which may serve different @@ -94,69 +78,6 @@ FLAGS authenticated account will be used (e.g. gcloud auth print-identity-token). - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/run/services/remove-iam-policy-binding b/gcloud/alpha/run/services/remove-iam-policy-binding index 8b08b8cc6..7ad2e9b91 100644 --- a/gcloud/alpha/run/services/remove-iam-policy-binding +++ b/gcloud/alpha/run/services/remove-iam-policy-binding @@ -4,12 +4,9 @@ NAME SYNOPSIS gcloud alpha run services remove-iam-policy-binding SERVICE - --member=PRINCIPAL --role=ROLE [--platform=PLATFORM; default="managed"] + --member=PRINCIPAL --role=ROLE [--region=REGION] [--all | --condition=[KEY=VALUE,...] - | --condition-from-file=PATH_TO_FILE] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + | --condition-from-file=PATH_TO_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Remove an IAM policy binding from the IAM policy of a service. One @@ -76,22 +73,9 @@ REQUIRED FLAGS The role to remove the principal from. OPTIONAL FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. At most one of these can be specified: @@ -135,69 +119,6 @@ OPTIONAL FLAGS available fields, see the help for --condition. Use a full or relative path to a local file containing the value of condition. - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/run/services/replace b/gcloud/alpha/run/services/replace index bac0e33a1..68e143791 100644 --- a/gcloud/alpha/run/services/replace +++ b/gcloud/alpha/run/services/replace @@ -4,10 +4,7 @@ NAME SYNOPSIS gcloud alpha run services replace FILE [--async] [--dry-run] - [--namespace=NAMESPACE] [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates or replaces a service from a YAML service specification. @@ -31,104 +28,9 @@ FLAGS If set to true, only validates the configuration. The configuration will not be applied. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to replace service. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/services/set-iam-policy b/gcloud/alpha/run/services/set-iam-policy index 30b3e90f3..274534826 100644 --- a/gcloud/alpha/run/services/set-iam-policy +++ b/gcloud/alpha/run/services/set-iam-policy @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud alpha run services set-iam-policy SERVICE POLICY_FILE - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command replaces the existing IAM policy for a service, given @@ -61,85 +58,9 @@ POSITIONAL ARGUMENTS (https://cloud.google.com/iam/reference/rest/v1/Policy). FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 1f14553e5..9a49cc76d 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -4,12 +4,33 @@ NAME SYNOPSIS gcloud alpha run services update [[SERVICE] --namespace=NAMESPACE] - [--async] [--concurrency=CONCURRENCY] [--container=CONTAINER] - [--ingress=INGRESS; default="all"] [--max-instances=MAX_INSTANCES] - [--min-instances=MIN_INSTANCES] - [--platform=PLATFORM; default="managed"] - [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] - [--no-traffic] + [--async] [--breakglass=JUSTIFICATION] [--clear-vpc-connector] + [--concurrency=CONCURRENCY] [--container=CONTAINER] [--[no-]cpu-boost] + [--[no-]cpu-throttling] [--[no-]default-url] + [--[no-]deploy-health-check] [--description=DESCRIPTION] + [--execution-environment=EXECUTION_ENVIRONMENT] + [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] + [--max-instances=MAX_INSTANCES] [--max-surge=MAX_SURGE] + [--max-unavailable=MAX_UNAVAILABLE] [--mesh=MESH] + [--min-instances=MIN_INSTANCES] [--region=REGION] + [--remove-containers=[CONTAINER,...]] + [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] + [--service-account=SERVICE_ACCOUNT] + [--service-max-instances=SERVICE_MAX_INSTANCES] + [--service-min-instances=SERVICE_MIN_INSTANCES] + [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] + [--no-traffic] [--vpc-connector=VPC_CONNECTOR] + [--vpc-egress=VPC_EGRESS] + [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --clear-cloudsql-instances + | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--add-custom-audiences=[CUSTOM-AUDIENCES,...] + | --clear-custom-audiences + | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + | --set-custom-audiences=[CUSTOM-AUDIENCES,...]] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --image=IMAGE @@ -22,40 +43,21 @@ SYNOPSIS --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] - [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost - --[no-]cpu-throttling --[no-]default-url --[no-]deploy-health-check - --description=DESCRIPTION - --execution-environment=EXECUTION_ENVIRONMENT - --[no-]invoker-iam-check --max-surge=MAX_SURGE - --max-unavailable=MAX_UNAVAILABLE --mesh=MESH - --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX - --scaling=SCALING --service-max-instances=SERVICE_MAX_INSTANCES - --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity - --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --clear-cloudsql-instances - | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - | --clear-custom-audiences - | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --add-volume=[KEY=VALUE,...] --clear-volumes - --remove-volume=[VOLUME,...] --binary-authorization=POLICY - | --clear-binary-authorization --clear-encryption-key-shutdown-hours - | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - --clear-key | --key=KEY --clear-network - | --network=NETWORK --subnet=SUBNET --clear-network-tags - | --network-tags=[TAG,...] --clear-post-key-revocation-action-type - | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [--binary-authorization=POLICY | --clear-binary-authorization] + [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] + | --remove-config-maps=[KEY,...] + --update-config-maps=[KEY=VALUE,...]] + [--clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] + [--clear-key | --key=KEY] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] - [--connectivity=CONNECTIVITY --clear-config-maps - | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAG,...]] + [--clear-post-key-revocation-action-type + | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update Cloud Run environment variables and other configuration @@ -99,6 +101,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. + + --clear-vpc-connector + Remove the VPC connector for this resource. + --concurrency=CONCURRENCY Set the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified or provide the special value @@ -108,64 +120,134 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + --[no-]cpu-boost + Whether to allocate extra CPU to containers on startup to reduce the + perceived latency of a cold start request. Enabled by default when + unspecified on new services. Use --cpu-boost to enable and + --no-cpu-boost to disable. + + --[no-]cpu-throttling + Whether to throttle the CPU when the container is not actively serving + requests. Use --cpu-throttling to enable and --no-cpu-throttling to + disable. + + --[no-]default-url + Toggles the default url for a run service. This is enabled by default + if not specified. Use --default-url to enable and --no-default-url to + disable. + + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + + --description=DESCRIPTION + Provides an optional, human-readable description of the service. + + --execution-environment=EXECUTION_ENVIRONMENT + Selects the execution environment where the application will run. + EXECUTION_ENVIRONMENT must be one of: + + gen1 + Run the application in a first generation execution environment. + gen2 + Run the application in a second generation execution environment. + --ingress=INGRESS; default="all" Set the ingress traffic sources allowed to call the service. For Cloud - Run (fully managed) the --[no-]allow-unauthenticated flag separately - controls the identities allowed to call the service. INGRESS must be - one of: + Run the --[no-]allow-unauthenticated flag separately controls the + identities allowed to call the service. INGRESS must be one of: all Inbound requests from all sources are allowed. internal - For Cloud Run (fully managed), only inbound requests from VPC - networks in the same project or VPC Service Controls perimeter, as - well as Pub/Sub subscriptions and Eventarc events in the same - project or VPC Service Controls perimeter are allowed. All other - requests are rejected. See - https://cloud.google.com/run/docs/securing/ingress for full details - on the definition of internal traffic for Cloud Run (fully - managed). For Cloud Run for Anthos, only inbound requests from the - same cluster are allowed. + For Cloud Run, only inbound requests from VPC networks in the same + project or VPC Service Controls perimeter, as well as Pub/Sub + subscriptions and Eventarc events in the same project or VPC + Service Controls perimeter are allowed. All other requests are + rejected. See https://cloud.google.com/run/docs/securing/ingress + for full details on the definition of internal traffic for Cloud + Run. internal-and-cloud-load-balancing - Only supported for Cloud Run (fully managed). Only inbound requests - from Google Cloud Load Balancing or a traffic source allowed by the - internal option are allowed. + Only inbound requests from Google Cloud Load Balancing or a traffic + source allowed by the internal option are allowed. + + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. --max-instances=MAX_INSTANCES The maximum number of container instances of the Service to run. Use 'default' to unset the limit and use the platform default. + --max-surge=MAX_SURGE + A maximum percentage of instances that will be moved in each step of + traffic split changes. Use "default" to unset the limit and use the + platform default. + + --max-unavailable=MAX_UNAVAILABLE + A maximum percentage of instances that may be unavailable during + traffic split changes. Use "default" to unset the limit and use the + platform default. + + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. Mesh + resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + --min-instances=MIN_INSTANCES The minimum number of container instances for this Revision of the Service to run or 'default' to remove any minimum. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --remove-containers=[CONTAINER,...] + List of containers to remove. + + --revision-suffix=REVISION_SUFFIX + Specify the suffix of the revision name. Revision names always start + with the service name automatically. For example, specifying + [--revision-suffix=v1] for a service named 'helloworld', would lead to + a revision named 'helloworld-v1'. Set empty string to clear the suffix + and resume server-assigned naming. + + --scaling=SCALING + The scaling mode to use for this resource. SCALING must be one of: + + automatic + The number of instances is scaled automatically based on the usage + metrics. + manual + The number of instances is fixed to a provided config value. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. For the managed platform, - this is the email address of an IAM service account. For the - Kubernetes-based platforms (gke, kubernetes), this is the name of a - Kubernetes service account in the same namespace as the service. If not - provided, the revision will use the default service account of the - project, or default Kubernetes namespace service account respectively. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. + + --service-max-instances=SERVICE_MAX_INSTANCES + The maximum number of container instances for this Service to run. This + instance limit will be divided among all Revisions receiving a + percentage of traffic. Once service-max-instances is enabled for a + service, it cannot be disabled. + + --service-min-instances=SERVICE_MIN_INSTANCES + The minimum number of container instances for this Service to run or + 'default' to remove any minimum. These instances will be divided among + all Revisions receiving a percentage of traffic. + + --[no-]session-affinity + Whether to enable session affinity for connections to the service. Use + --session-affinity to enable and --no-session-affinity to disable. --tag=TAG Traffic tag to assign to the newly created revision. @@ -187,6 +269,125 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. + --vpc-connector=VPC_CONNECTOR + Set a VPC connector for this resource. + + --vpc-egress=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 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 Direct VPC egress or the VPC + connector. + private-ranges-only + 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 + region as your Cloud Run service; otherwise specify + :: for the instance. + + At most one of these can be specified: + + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Append the given values to the current Cloud SQL instances. + + --clear-cloudsql-instances + Empty the current Cloud SQL instances. + + --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Remove the given values from the current Cloud SQL instances. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Completely replace the current Cloud SQL instances with the given + values. + + These flags modify the custom audiences that can be used in the audience + field of ID token for authenticated requests. + + At most one of these can be specified: + + --add-custom-audiences=[CUSTOM-AUDIENCES,...] + Append the given values to the current custom audiences. + + --clear-custom-audiences + Empty the current custom audiences. + + --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + Remove the given values from the current custom audiences. + + --set-custom-audiences=[CUSTOM-AUDIENCES,...] + Completely replace the current custom audiences with the given + values. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags + should be specified without leading dashes and separated by + semicolons. + ◆ bucket: (optional) the name of the bucket to use as the source of + this volume. + ◆ dynamic-mounting: (optional) A boolean. If true, the volume will be + mounted dynamically. Note: You will either need to specify a bucket + or set dynamic-mounting to true, but not both. + + in-memory: An ephemeral volume that stores data in the instance's + memory. With this type of volume, data is not shared between instances + and all data will be lost when the instance it is on is terminated. + Additional keys: + ◆ size-limit: (optional) A quantity representing the maximum amount + of memory allocated to this volume, such as "512Mi" or "3G". Data + stored in an in-memory volume consumes the memory allocation of the + container that wrote the data. If size-limit is not specified, the + maximum size will be half the total memory limit of all containers. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + secret: Represents a secret stored in Secret Manager as a volume. + Additional keys: + ◆ secret: (required) The name of the secret in Secret Manager. Must + be a secret in the same project being deployed or be an alias mapped + in the run.googleapis.com/secrets annotation. + ◆ version: (required) The version of the secret to make available in + the volume. + ◆ path: (required) The relative path within the volume to mount that + version. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + Container Flags If the --container or --remove-containers flag is specified the following @@ -216,12 +417,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. @@ -232,7 +429,7 @@ FLAGS --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/hello:latest). --liveness-probe=[KEY=VALUE,...] Comma separated settings for liveness probe in the form KEY=VALUE. @@ -369,304 +566,62 @@ FLAGS --update-secrets=[KEY=VALUE,...] List of key-value pairs to set as secrets. - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + At most one of these can be specified: - --breakglass=JUSTIFICATION - Justification to bypass Binary Authorization policy constraints and - allow the operation. See - https://cloud.google.com/binary-authorization/docs/using-breakglass - for more information. Next update or deploy command will - automatically clear existing breakglass justification. + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". - --clear-vpc-connector - Remove the VPC connector for this resource. + --clear-binary-authorization + Remove any previously set Binary Authorization policy. - --[no-]cpu-boost - Whether to allocate extra CPU to containers on startup to reduce the - perceived latency of a cold start request. Enabled by default when - unspecified on new services. Use --cpu-boost to enable and - --no-cpu-boost to disable. + Specify config map to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. The values associated with each of + these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may + omit the key within the config map to specify a mount of all keys within + the config map. For example: + '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will + create a volume with config map 'myconfig' and mount that volume at + '/my/path'. Because no config map key was specified, all keys in + 'myconfig' will be included. An environment variable named ENV will also + be created whose value is the value of 'key.json' in 'otherconfig. Not + supported on the fully managed version of Cloud Run. - --[no-]cpu-throttling - Whether to throttle the CPU when the container is not actively - serving requests. Use --cpu-throttling to enable and - --no-cpu-throttling to disable. + At most one of these can be specified: - --[no-]default-url - Toggles the default url for a run service. This is enabled by default - if not specified. Use --default-url to enable and --no-default-url to - disable. + --clear-config-maps + Remove all config-maps. - --[no-]deploy-health-check - Schedules a single instance of the Revision and waits for it to pass - its startup probe for the deployment to succeed. If disabled, the - startup probe runs only when the revision is first started via - invocation or by setting min-instances. This check is enabled by - default when unspecified. Use --deploy-health-check to enable and - --no-deploy-health-check to disable. + --set-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. All existing + config-maps will be removed first. - --description=DESCRIPTION - Provides an optional, human-readable description of the service. + Only --update-config-maps and --remove-config-maps can be used together. + If both are specified, --remove-config-maps will be applied first. - --execution-environment=EXECUTION_ENVIRONMENT - Selects the execution environment where the application will run. - EXECUTION_ENVIRONMENT must be one of: + --remove-config-maps=[KEY,...] + List of config-maps to be removed. - gen1 - Run the application in a first generation execution environment. - gen2 - Run the application in a second generation execution environment. + --update-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. - --[no-]invoker-iam-check - Optionally disable invoker IAM checks. This feature is available by - invitation only. More info at - https://cloud.google.com/run/docs/securing/managing-access#invoker_check. - Use --invoker-iam-check to enable and --no-invoker-iam-check to - disable. + At most one of these can be specified: - --max-surge=MAX_SURGE - A maximum percentage of instances that will be moved in each step of - traffic split changes. Use "default" to unset the limit and use the - platform default. + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. - --max-unavailable=MAX_UNAVAILABLE - A maximum percentage of instances that may be unavailable during - traffic split changes. Use "default" to unset the limit and use the - platform default. + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server after + CMEK key revocation is detected. - --mesh=MESH - Enables Cloud Service Mesh using the specified mesh resource name. - Mesh resource name must be in the format of - projects/PROJECT/locations/global/meshes/MESH_NAME. + At most one of these can be specified: - --remove-containers=[CONTAINER,...] - List of containers to remove. + --clear-key + Remove any previously set CMEK key reference. - --revision-suffix=REVISION_SUFFIX - Specify the suffix of the revision name. Revision names always start - with the service name automatically. For example, specifying - [--revision-suffix=v1] for a service named 'helloworld', would lead - to a revision named 'helloworld-v1'. Set empty string to clear the - suffix and resume server-assigned naming. - - --scaling=SCALING - The scaling mode to use for this resource. SCALING must be one of: - - automatic - The number of instances is scaled automatically based on the - usage metrics. - manual - The number of instances is fixed to a provided config value. - - --service-max-instances=SERVICE_MAX_INSTANCES - The maximum number of container instances for this Service to run. - This instance limit will be divided among all Revisions receiving a - percentage of traffic. Once service-max-instances is enabled for a - service, it cannot be disabled. - - --service-min-instances=SERVICE_MIN_INSTANCES - The minimum number of container instances for this Service to run or - 'default' to remove any minimum. These instances will be divided - among all Revisions receiving a percentage of traffic. - - --[no-]session-affinity - Whether to enable session affinity for connections to the service. - Use --session-affinity to enable and --no-session-affinity to - disable. - - --vpc-connector=VPC_CONNECTOR - Set a VPC connector for this resource. - - --vpc-egress=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 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 Direct VPC egress or the VPC - connector. - private-ranges-only - 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 region as your Cloud Run service; otherwise specify - :: for the instance. - - At most one of these can be specified: - - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Append the given values to the current Cloud SQL instances. - - --clear-cloudsql-instances - Empty the current Cloud SQL instances. - - --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Remove the given values from the current Cloud SQL instances. - - --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Completely replace the current Cloud SQL instances with the given - values. - - These flags modify the custom audiences that can be used in the audience - field of ID token for authenticated requests. - - At most one of these can be specified: - - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - Append the given values to the current custom audiences. - - --clear-custom-audiences - Empty the current custom audiences. - - --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - Remove the given values from the current custom audiences. - - --set-custom-audiences=[CUSTOM-AUDIENCES,...] - Completely replace the current custom audiences with the given - values. - - --add-volume=[KEY=VALUE,...] - Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: - - cloud-storage: A volume representing a Cloud Storage bucket. This - volume type is mounted using Cloud Storage FUSE. See - https://cloud.google.com/storage/docs/gcs-fuse for the details and - limitations of this filesystem. Additional keys: - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - ◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags - should be specified without leading dashes and separated by - semicolons. - ◆ bucket: (optional) the name of the bucket to use as the source of - this volume. - ◆ dynamic-mounting: (optional) A boolean. If true, the volume will be - mounted dynamically. Note: You will either need to specify a bucket or - set dynamic-mounting to true, but not both. - - in-memory: An ephemeral volume that stores data in the instance's memory. - With this type of volume, data is not shared between instances and all - data will be lost when the instance it is on is terminated. Additional - keys: - ◆ size-limit: (optional) A quantity representing the maximum amount of - memory allocated to this volume, such as "512Mi" or "3G". Data stored - in an in-memory volume consumes the memory allocation of the container - that wrote the data. If size-limit is not specified, the maximum size - will be half the total memory limit of all containers. - - nfs: Represents a volume backed by an NFS server. Additional keys: - ◆ location: (required) The location of the NFS Server, in the form - SERVER:/PATH - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - - secret: Represents a secret stored in Secret Manager as a volume. - Additional keys: - ◆ secret: (required) The name of the secret in Secret Manager. Must be - a secret in the same project being deployed or be an alias mapped in - the run.googleapis.com/secrets annotation. - ◆ version: (required) The version of the secret to make available in - the volume. - ◆ path: (required) The relative path within the volume to mount that - version. - - --clear-volumes - Remove all existing volumes from the Cloud Run resource, including - volumes mounted as secrets - - --remove-volume=[VOLUME,...] - Removes volumes from the Cloud Run resource. - - At most one of these can be specified: - - --binary-authorization=POLICY - Binary Authorization policy to check against. This must be set to - "default". - - --clear-binary-authorization - Remove any previously set Binary Authorization policy. - - At most one of these can be specified: - - --clear-encryption-key-shutdown-hours - Remove any previously set CMEK key shutdown hours setting. - - --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - The number of hours to wait before an automatic shutdown server - after CMEK key revocation is detected. - - At most one of these can be specified: - - --clear-key - Remove any previously set CMEK key reference. - - --key=KEY - CMEK key reference to encrypt the container with. - - At most one of these can be specified: - - --clear-network - Disconnect this Cloud Run service from the VPC network it is - connected to. - - Direct VPC egress setting flags group. - - --network=NETWORK - The VPC network that the Cloud Run service will be able to send - traffic to. If --subnet is also specified, subnet must be a - subnetwork of the network specified by this --network flag. To - clear existing VPC network settings, use --clear-network. - - --subnet=SUBNET - The VPC subnetwork that the Cloud Run service will get IPs from. - The subnetwork must be /26 or larger. If --network is also - specified, subnet must be a subnetwork of the network specified - by the --network flag. If --network is not specified, network - will be looked up from this subnetwork. To clear existing VPC - network settings, use --clear-network. - - At most one of these can be specified: - - --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. - - --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. - - At most one of these can be specified: - - --clear-post-key-revocation-action-type - Remove any previously set post CMEK key revocation action type. - - --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE - Action type after CMEK key revocation. - POST_KEY_REVOCATION_ACTION_TYPE must be one of: - - prevent-new - No new instances will be started after CMEK key revocation. - shut-down - No new instances will be started and the existing instances - will be shut down after CMEK key revocation. + --key=KEY + CMEK key reference to encrypt the container with. At most one of these can be specified: @@ -699,119 +654,53 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: + At most one of these can be specified: - --connectivity=CONNECTIVITY - (DEPRECATED) Defaults to 'external'. If 'external', the service can - be invoked through the internet, in addition to through the cluster - network. + --clear-network + Disconnect this Cloud Run service from the VPC network it is + connected to. - The --connectivity flag is deprecated but will continue to be - supported. Prefer to use the --ingress flag instead. CONNECTIVITY - must be one of: + Direct VPC egress setting flags group. - external - Visible from outside the cluster. - internal - Visible only within the cluster. + --network=NETWORK + The VPC network that the Cloud Run service will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. + --subnet=SUBNET + The VPC subnetwork that the Cloud Run service will get IPs from. + The subnetwork must be /26 or larger. If --network is also + specified, subnet must be a subnetwork of the network specified by + the --network flag. If --network is not specified, network will be + looked up from this subnetwork. To clear existing VPC network + settings, use --clear-network. - At most one of these can be specified: + At most one of these can be specified: - --clear-config-maps - Remove all config-maps. + --clear-network-tags + Clears all existing Compute Engine tags from the Cloud Run + service. - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used - together. If both are specified, --remove-config-maps will be applied - first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - - Arguments to locate resources, depending on the platform used. + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. To clear existing tags, use + --clear-network-tags. At most one of these can be specified: - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. + --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE + Action type after CMEK key revocation. + POST_KEY_REVOCATION_ACTION_TYPE must be one of: - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▸ set the property run/cluster with a fully specified name; - ▸ specify the cluster from a list of available clusters with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the - cluster. - - To set the cluster attribute: - ▫ provide the argument --cluster on the command line; - ▫ set the property run/cluster; - ▫ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ▫ provide the argument --cluster on the command line with a - fully specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --cluster-location on the command line; - ▫ set the property run/cluster_location; - ▫ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + prevent-new + No new instances will be started after CMEK key revocation. + shut-down + No new instances will be started and the existing instances will + be shut down after CMEK key revocation. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/services/update-traffic b/gcloud/alpha/run/services/update-traffic index 97f74e3e6..6905b3e50 100644 --- a/gcloud/alpha/run/services/update-traffic +++ b/gcloud/alpha/run/services/update-traffic @@ -4,13 +4,9 @@ NAME SYNOPSIS gcloud alpha run services update-traffic [[SERVICE] --namespace=NAMESPACE] - [--async] [--breakglass=JUSTIFICATION] - [--platform=PLATFORM; default="managed"] + [--async] [--breakglass=JUSTIFICATION] [--region=REGION] [--clear-tags | --set-tags=[TAG=REVISION,...] | --remove-tags=[TAG,...] --update-tags=[TAG=REVISION,...]] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--to-latest | --to-revisions=[REVISION-NAME=PERCENTAGE,...] | --to-tags=[TAG=PERCENTAGE,...]] [GCLOUD_WIDE_FLAG ...] @@ -78,32 +74,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. - --breakglass=JUSTIFICATION - Justification to bypass Binary Authorization policy constraints and - allow the operation. See - https://cloud.google.com/binary-authorization/docs/using-breakglass - for more information. Next update or deploy command will - automatically clear existing breakglass justification. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. Specify traffic tags. Traffic tags can be assigned to a revision by name or to the latest ready revision. Assigning a tag to a revision generates a @@ -136,69 +116,6 @@ FLAGS --update-tags=[TAG=REVISION,...] List of key-value pairs to set as tags. - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - At most one of these can be specified: --to-latest diff --git a/gcloud/alpha/run/workers/delete b/gcloud/alpha/run/workers/delete index 73e155a2c..b7a2f84d3 100644 --- a/gcloud/alpha/run/workers/delete +++ b/gcloud/alpha/run/workers/delete @@ -35,8 +35,7 @@ POSITIONAL ARGUMENTS FLAGS --[no-]async Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async for Cloud Run (fully managed) and - --async for Cloud Run for Anthos. Use --async to enable and --no-async + complete. Defaults to --no-async. Use --async to enable and --no-async to disable. --region=REGION diff --git a/gcloud/alpha/run/workers/deploy b/gcloud/alpha/run/workers/deploy index e8b3794da..87d696fb0 100644 --- a/gcloud/alpha/run/workers/deploy +++ b/gcloud/alpha/run/workers/deploy @@ -144,14 +144,9 @@ FLAGS The number of instances is fixed to a provided config value. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. For the managed platform, - this is the email address of an IAM service account. For the - Kubernetes-based platforms (gke, kubernetes), this is the name of a - Kubernetes service account in the same namespace as the service. If not - provided, the revision will use the default service account of the - project, or default Kubernetes namespace service account respectively. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. --vpc-egress=VPC_EGRESS Specify which of the outbound traffic to send through Direct VPC egress @@ -279,12 +274,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. @@ -351,7 +342,7 @@ FLAGS --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/hello:latest). --source=SOURCE The location of the source to build. If a Dockerfile is present diff --git a/gcloud/alpha/run/workers/update b/gcloud/alpha/run/workers/update index 66b76d3d4..61cce97ee 100644 --- a/gcloud/alpha/run/workers/update +++ b/gcloud/alpha/run/workers/update @@ -145,14 +145,9 @@ FLAGS The number of instances is fixed to a provided config value. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. For the managed platform, - this is the email address of an IAM service account. For the - Kubernetes-based platforms (gke, kubernetes), this is the name of a - Kubernetes service account in the same namespace as the service. If not - provided, the revision will use the default service account of the - project, or default Kubernetes namespace service account respectively. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. --[no-]session-affinity Whether to enable session affinity for connections to the service. Use @@ -302,16 +297,12 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/hello:latest). --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. diff --git a/gcloud/alpha/service-extensions/wasm-plugins/create b/gcloud/alpha/service-extensions/wasm-plugins/create index 6188d223f..2c11b7721 100644 --- a/gcloud/alpha/service-extensions/wasm-plugins/create +++ b/gcloud/alpha/service-extensions/wasm-plugins/create @@ -16,10 +16,6 @@ DESCRIPTION (ALPHA) Create a new WasmPlugin resource. EXAMPLES - To create a WasmPlugin called my-plugin, run: - - $ gcloud alpha service-extensions wasm-plugins create my-plugin - To create a WasmPlugin called my-plugin, together with a new version called v1, and set it as main, run: diff --git a/gcloud/alpha/service-extensions/wasm-plugins/delete b/gcloud/alpha/service-extensions/wasm-plugins/delete index d8b8f934c..6af74864b 100644 --- a/gcloud/alpha/service-extensions/wasm-plugins/delete +++ b/gcloud/alpha/service-extensions/wasm-plugins/delete @@ -9,6 +9,9 @@ SYNOPSIS DESCRIPTION (ALPHA) Delete a WasmPlugin resource. + Please note that all WasmPluginVersions associated with the WasmPlugin will + also be deleted. + EXAMPLES To delete a WasmPlugin called my-plugin, run: diff --git a/gcloud/alpha/spanner/backup-schedules/create b/gcloud/alpha/spanner/backup-schedules/create index 752c77d35..919df78cd 100644 --- a/gcloud/alpha/spanner/backup-schedules/create +++ b/gcloud/alpha/spanner/backup-schedules/create @@ -7,8 +7,8 @@ SYNOPSIS (BACKUP_SCHEDULE : --database=DATABASE --instance=INSTANCE) --backup-type=[BACKUP_TYPE] --cron=CRON --retention-duration=RETENTION_DURATION - [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + [--encryption-type=ENCRYPTION_TYPE --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] @@ -111,6 +111,28 @@ OPTIONAL FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to create the Cloud Spanner + backup. 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 kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner backup. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/alpha/spanner/backup-schedules/update b/gcloud/alpha/spanner/backup-schedules/update index 149ec1f63..11eb75be7 100644 --- a/gcloud/alpha/spanner/backup-schedules/update +++ b/gcloud/alpha/spanner/backup-schedules/update @@ -6,8 +6,8 @@ SYNOPSIS gcloud alpha spanner backup-schedules update (BACKUP_SCHEDULE : --database=DATABASE --instance=INSTANCE) (--cron=CRON --encryption-type=ENCRYPTION_TYPE - --retention-duration=RETENTION_DURATION [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + --retention-duration=RETENTION_DURATION --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]) [GCLOUD_WIDE_FLAG ...] @@ -99,6 +99,28 @@ REQUIRED FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to create the Cloud Spanner + backup. 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 kms-project attribute: + ▫ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▫ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▫ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ◇ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner backup. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/alpha/spanner/backups/copy b/gcloud/alpha/spanner/backups/copy index 475987da1..2e856988a 100644 --- a/gcloud/alpha/spanner/backups/copy +++ b/gcloud/alpha/spanner/backups/copy @@ -10,8 +10,8 @@ SYNOPSIS | --retention-period=RETENTION_PERIOD) (--source-backup=SOURCE_BACKUP : --source-instance=SOURCE_INSTANCE) [--async] - [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + [--encryption-type=ENCRYPTION_TYPE --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] @@ -133,6 +133,28 @@ OPTIONAL FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to copy the Cloud Spanner + backup. 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 kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to copy the Cloud Spanner backup. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/alpha/spanner/backups/create b/gcloud/alpha/spanner/backups/create index 7207c4437..f0c403cda 100644 --- a/gcloud/alpha/spanner/backups/create +++ b/gcloud/alpha/spanner/backups/create @@ -8,8 +8,8 @@ SYNOPSIS (--expiration-date=EXPIRATION_DATE | --retention-period=RETENTION_PERIOD) [--async] [--version-time=TIMESTAMP] - [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + [--encryption-type=ENCRYPTION_TYPE --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] @@ -102,6 +102,28 @@ OPTIONAL FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to create the Cloud Spanner + backup. 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 kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner backup. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/alpha/spanner/databases/create b/gcloud/alpha/spanner/databases/create index b809ddb49..8fc19005a 100644 --- a/gcloud/alpha/spanner/databases/create +++ b/gcloud/alpha/spanner/databases/create @@ -5,8 +5,9 @@ SYNOPSIS gcloud alpha spanner databases create (DATABASE : --instance=INSTANCE) [--async] [--database-dialect=DATABASE_DIALECT] [--ddl=DDL] [--ddl-file=DDL_FILE] [--proto-descriptors-file=PROTO_DESCRIPTORS_FILE] - [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING - --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] + [--kms-keys=[KMS_KEYS,...] | [--kms-key=KMS_KEY + : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -96,6 +97,28 @@ FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to create the Cloud Spanner + database. This represents a Cloud resource. (NOTE) Some attributes are + not given arguments in this group but can be set in other ways. + + To set the kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner database. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/alpha/spanner/databases/restore b/gcloud/alpha/spanner/databases/restore index a939a074d..b1b7546a5 100644 --- a/gcloud/alpha/spanner/databases/restore +++ b/gcloud/alpha/spanner/databases/restore @@ -7,8 +7,8 @@ SYNOPSIS : --destination-instance=DESTINATION_INSTANCE) (--source-backup=SOURCE_BACKUP : --source-instance=SOURCE_INSTANCE) [--async] - [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + [--encryption-type=ENCRYPTION_TYPE --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] @@ -114,6 +114,28 @@ OPTIONAL FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to restore the Cloud Spanner + database. This represents a Cloud resource. (NOTE) Some attributes are + not given arguments in this group but can be set in other ways. + + To set the kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to restore the Cloud Spanner database. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index 34fedc2fc..a93b6c3c9 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -44,6 +44,7 @@ SYNOPSIS [--psc-auto-connections=[network=NETWORK],[project=PROJECT]] [--[no-]recreate-replicas-on-primary-crash] [--replica-type=REPLICA_TYPE] [--replication=REPLICATION] + [--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE] [--require-ssl] [--retained-backups-count=RETAINED_BACKUPS_COUNT] [--retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS] [--root-password=ROOT_PASSWORD] [--server-ca-mode=SERVER_CA_MODE] @@ -427,6 +428,12 @@ FLAGS Type of replication this instance uses. The default is synchronous. REPLICATION must be one of: synchronous, asynchronous. + --replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE + Set a maximum replication lag for a MySQL read replica in seconds. If + the replica lag exceeds the specified value, the readreplica(s) will be + recreated. Min value=300 seconds,Max value=31536000 seconds, default + value=31536000 seconds. + --require-ssl Specified if users connecting over IP must use SSL. diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index a344d2f77..147a5cbb1 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -43,6 +43,7 @@ SYNOPSIS [--pricing-plan=PRICING_PLAN, -p PRICING_PLAN] [--[no-]recreate-replicas-on-primary-crash] [--remove-deny-maintenance-period] [--replication=REPLICATION] + [--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE] [--[no-]require-ssl] [--simulate-maintenance-event] [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] @@ -357,6 +358,12 @@ FLAGS Type of replication this instance uses. The default is synchronous. REPLICATION must be one of: synchronous, asynchronous. + --replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE + Set a maximum replication lag for a MySQL read replica in seconds. If + the replica lag exceeds the specified value, the readreplica(s) will be + recreated. Min value=300 seconds,Max value=31536000 seconds, default + value=31536000 seconds. + --[no-]require-ssl mysqld should default to 'REQUIRE X509' for users connecting over IP. Use --require-ssl to enable and --no-require-ssl to disable. diff --git a/gcloud/alpha/storage/batch-operations/help b/gcloud/alpha/storage/batch-operations/help new file mode 100644 index 000000000..415243b71 --- /dev/null +++ b/gcloud/alpha/storage/batch-operations/help @@ -0,0 +1,27 @@ +NAME + gcloud alpha storage batch-operations - manage Cloud Storage batch + operations + +SYNOPSIS + gcloud alpha storage batch-operations GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud Storage batch operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + jobs + (ALPHA) Manage Cloud Storage batch operations jobs. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/storage/batch-operations/jobs/cancel b/gcloud/alpha/storage/batch-operations/jobs/cancel new file mode 100644 index 000000000..5b86849ee --- /dev/null +++ b/gcloud/alpha/storage/batch-operations/jobs/cancel @@ -0,0 +1,67 @@ +NAME + gcloud alpha storage batch-operations jobs cancel - cancel a + batch-operations job + +SYNOPSIS + gcloud alpha storage batch-operations jobs cancel + (BATCH_JOB : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancel the batch operation job. + +EXAMPLES + To cancel a batch job with the name my-job in location us-central1: + + $ gcloud alpha storage batch-operations jobs cancel my-job \ + --location=us-central1 + + To cancel the same batch job with fully specified name: + + $ gcloud alpha storage batch-operations jobs cancel \ + projects/my-project/locations/us-central1/jobs/my-job + +POSITIONAL ARGUMENTS + Batch job resource - The batch job to cancel. 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 batch_job on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + BATCH_JOB + ID of the batch-job or fully qualified identifier for the batch-job. + + To set the batch-job attribute: + ▸ provide the argument batch_job on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Batch-operations supported Google Cloud location for the batch-job. + + To set the location attribute: + ▸ provide the argument batch_job 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. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/storage/batch-operations/jobs/create b/gcloud/alpha/storage/batch-operations/jobs/create new file mode 100644 index 000000000..7cff47bf0 --- /dev/null +++ b/gcloud/alpha/storage/batch-operations/jobs/create @@ -0,0 +1,166 @@ +NAME + gcloud alpha storage batch-operations jobs create - create a new batch + operation job + +SYNOPSIS + gcloud alpha storage batch-operations jobs create + (BATCH_JOB : --location=LOCATION) + (--manifest-location=MANIFEST_LOCATION + | --prefix-list-file=PREFIX_LIST_FILE) + (--put-kms-key=PUT_KMS_KEY | --put-metadata=KEY=VALUE,[KEY=VALUE,...] + | [--delete-object : --enable-permanent-object-deletion] + | --[no-]put-object-event-based-hold + --[no-]put-object-temporary-hold) [--description=DESCRIPTION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a batch operation job, allowing you to perform operations + such as deletion, updating metadata, and more on objects in a serverless + manner. + +EXAMPLES + To create a batch job with the name my-job in location us-central1 to + perform object deletion where the manifest file gs://my-bucket/manifest.csv + specifies the objects to be transformed: + + $ gcloud alpha storage batch-operations jobs create my-job \ + --location=us-central1 \ + --manifest-location=gs://my-bucket/manifest.csv --delete-object + + To create a batch job with the name my-job in location us-central1 to + update object metadata Content-Disposition to inline and Content-Language + to en where the prefix list file my-path/my-prefix-list.json specifies the + objects to be transformed: + + $ gcloud alpha storage batch-operations jobs create my-job \ + --location=us-central1 \ + --prefix-list-file=my-path/my-prefix-list.json \ + --put-metadata=Content-Disposition=inline,Content-Language=en + +POSITIONAL ARGUMENTS + Batch job resource - The batch job to create. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument batch_job on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + BATCH_JOB + ID of the batch-job or fully qualified identifier for the batch-job. + + To set the batch-job attribute: + ▸ provide the argument batch_job on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Batch-operations supported Google Cloud location for the batch-job. + + To set the location attribute: + ▸ provide the argument batch_job on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Source specifying objects to perform batch operations on. Must be one of + --manifest-location=``MANIFEST_LOCATION or + --prefix-list-file=``PREFIX_LIST_FILE + + Exactly one of these must be specified: + + --manifest-location=MANIFEST_LOCATION + An absolute path to the manifest source file in a Google Cloud + Storage bucket. The file must be a CSV file where each row specifies + the object details i.e. ProjectId, BucketId, and Name. Generation may + optionally be specified. When generation is not specified, the live + object is acted upon. Format: + --manifest-location=gs://bucket_name/path/manifest_name.csv + + --prefix-list-file=PREFIX_LIST_FILE + A path to a local JSON or YAML file containing a list of prefixes. + prefix is specified in the format of {"bucket": BUCKET_NAME, + "objectPrefix": OBJECT_PREFIX} where bucket is the name of the bucket + on which batch operation is being performed and objectPrefix is the + prefix of objects in the bucket that will be acted upon. + + Transformation to be performed on the objects. + + Exactly one of these must be specified: + + --put-kms-key=PUT_KMS_KEY + Sets the resource name of the Cloud KMS key that will be used to + encrypt the object. The Cloud KMS key must be located in same + location as the object. Format: + --put-kms-key=projects/PROJECT_ID/locations/LOCATION/keyRings/KEY_RING/cryptoKeys/CRYPTO_KEY + + --put-metadata=KEY=VALUE,[KEY=VALUE,...] + Sets object metadata. To set how content should be displayed, specify + the the key-value pair Content-Disposition={VALUE}. To set how + content is encoded (e.g. "gzip"), specify the key-value pair + Content-Encoding={VALUE}. To set content's language (e.g. "en" + signifies "English"), specify the key-value pair + Content-Language={VALUE}. To set the type of data contained in the + object (e.g. "text/html"), specify the key-value pair + Content-Type={VALUE}. To set how caches should handle requests and + responses, specify the key-value pair Cache-Control={VALUE}. To set + custom time for Cloud Storage objects in RFC 3339 format, specify the + key-value pair Custom-Time={VALUE}. To set custom metadata on + objects, specify key-value pairs {CUSTOM-KEY}:{VALUE}. Note that all + predefined keys are case-insensitive. Multiple key-value pairs can be + specified by separating them with commas. For example, + --put-metadata=Content-Disposition=inline,Content-Encoding=gzip + + Describes options to delete objects. + + --delete-object + If this flag is set, objects specified in source will be deleted. + When versioning is enabled on the buckets, live objects in + versioned buckets will become noncurrent and objects that were + already noncurrent will be skipped. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --enable-permanent-object-deletion + If this flag is set and versioning is enabled on the buckets, both + live and noncurrent objects will be permanently deleted. + + Describes options to update object hold. + + --[no-]put-object-event-based-hold + Sets or unsets object event based holds state. When object event + based hold is set, object cannot be deleted or replaced. Use + --put-object-event-based-hold to enable and + --no-put-object-event-based-hold to disable. + + --[no-]put-object-temporary-hold + Sets or unsets object temporary holds state. When object temporary + hold is set, object cannot be deleted or replaced. Use + --put-object-temporary-hold to enable and + --no-put-object-temporary-hold to disable. + +OPTIONAL FLAGS + --description=DESCRIPTION + Description for the batch job. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/storage/batch-operations/jobs/delete b/gcloud/alpha/storage/batch-operations/jobs/delete new file mode 100644 index 000000000..1fb123095 --- /dev/null +++ b/gcloud/alpha/storage/batch-operations/jobs/delete @@ -0,0 +1,67 @@ +NAME + gcloud alpha storage batch-operations jobs delete - delete a + batch-operations job + +SYNOPSIS + gcloud alpha storage batch-operations jobs delete + (BATCH_JOB : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete the batch operation job. + +EXAMPLES + To delete a batch job with the name my-job in location us-central1: + + $ gcloud alpha storage batch-operations jobs delete my-job \ + --location=us-central1 + + To delete the same batch job with fully specified name: + + $ gcloud alpha storage batch-operations jobs delete \ + projects/my-project/locations/us-central1/jobs/my-job + +POSITIONAL ARGUMENTS + Batch job resource - The batch job 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 batch_job on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + BATCH_JOB + ID of the batch-job or fully qualified identifier for the batch-job. + + To set the batch-job attribute: + ▸ provide the argument batch_job on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Batch-operations supported Google Cloud location for the batch-job. + + To set the location attribute: + ▸ provide the argument batch_job 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. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/storage/batch-operations/jobs/describe b/gcloud/alpha/storage/batch-operations/jobs/describe new file mode 100644 index 000000000..ed7889667 --- /dev/null +++ b/gcloud/alpha/storage/batch-operations/jobs/describe @@ -0,0 +1,67 @@ +NAME + gcloud alpha storage batch-operations jobs describe - describe a + batch-operations job + +SYNOPSIS + gcloud alpha storage batch-operations jobs describe + (BATCH_JOB : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe the batch operation job. + +EXAMPLES + To describe a batch job with the name my-job in location us-central1: + + $ gcloud alpha storage batch-operations jobs describe my-job \ + --location=us-central1 + + To describe the same batch job with fully specified name: + + $ gcloud alpha storage batch-operations jobs describe \ + projects/my-project/locations/us-central1/jobs/my-job + +POSITIONAL ARGUMENTS + Batch job resource - The batch job 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 batch_job on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + BATCH_JOB + ID of the batch-job or fully qualified identifier for the batch-job. + + To set the batch-job attribute: + ▸ provide the argument batch_job on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Batch-operations supported Google Cloud location for the batch-job. + + To set the location attribute: + ▸ provide the argument batch_job 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. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/storage/batch-operations/jobs/help b/gcloud/alpha/storage/batch-operations/jobs/help new file mode 100644 index 000000000..8725ea184 --- /dev/null +++ b/gcloud/alpha/storage/batch-operations/jobs/help @@ -0,0 +1,39 @@ +NAME + gcloud alpha storage batch-operations jobs - manage Cloud Storage batch + operations jobs + +SYNOPSIS + gcloud alpha storage batch-operations jobs COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Cloud Storage batch operations jobs. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancel a batch-operations job. + + create + (ALPHA) Create a new batch operation job. + + delete + (ALPHA) Delete a batch-operations job. + + describe + (ALPHA) Describe a batch-operations job. + + list + (ALPHA) List batch-operations jobs. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/storage/batch-operations/jobs/list b/gcloud/alpha/storage/batch-operations/jobs/list new file mode 100644 index 000000000..fb8217854 --- /dev/null +++ b/gcloud/alpha/storage/batch-operations/jobs/list @@ -0,0 +1,81 @@ +NAME + gcloud alpha storage batch-operations jobs list - list batch-operations + jobs + +SYNOPSIS + gcloud alpha storage batch-operations jobs list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List batch operation jobs. + +EXAMPLES + To list all batch jobs in all locations: + + $ gcloud alpha storage batch-operations jobs list + + To list all batch jobs for location us-central1: + + $ gcloud alpha storage batch-operations jobs list \ + --location=us-central1 + + To list all batch jobs for location us-central1 with a page size of 10: + + $ gcloud alpha storage batch-operations jobs list \ + --location=us-central1 --page-size=10 + + To list a limit of 20 batch jobs for location us-central1: + + $ gcloud alpha storage batch-operations jobs list \ + --location=us-central1 --limit=20 + + To list all batch jobs for location us-central1 in JSON format: + + $ gcloud alpha storage batch-operations jobs list \ + --location=us-central1 --format=json + +FLAGS + --location=LOCATION + The location of the batch jobs. + +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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/storage/help b/gcloud/alpha/storage/help index ee1dffe9a..758f31b26 100644 --- a/gcloud/alpha/storage/help +++ b/gcloud/alpha/storage/help @@ -20,6 +20,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + batch-operations + (ALPHA) Manage Cloud Storage batch operations. + buckets (ALPHA) Manage Cloud Storage buckets. diff --git a/gcloud/beta/ai/endpoints/create b/gcloud/beta/ai/endpoints/create index 5750b5494..e36e70762 100644 --- a/gcloud/beta/ai/endpoints/create +++ b/gcloud/beta/ai/endpoints/create @@ -5,8 +5,8 @@ SYNOPSIS gcloud beta ai endpoints create --display-name=DISPLAY_NAME [--description=DESCRIPTION] [--encryption-kms-key-name=ENCRYPTION_KMS_KEY_NAME] - [--endpoint-id=ENDPOINT_ID] [--labels=[KEY=VALUE,...]] - [--network=NETWORK] [--region=REGION] + [--endpoint-id=ENDPOINT_ID] [--gdce-zone=GDCE_ZONE] + [--labels=[KEY=VALUE,...]] [--network=NETWORK] [--region=REGION] [--request-response-logging-rate=REQUEST_RESPONSE_LOGGING_RATE --request-response-logging-table=REQUEST_RESPONSE_LOGGING_TABLE] [GCLOUD_WIDE_FLAG ...] @@ -36,6 +36,9 @@ OPTIONAL FLAGS --endpoint-id=ENDPOINT_ID User-specified ID of the endpoint. + --gdce-zone=GDCE_ZONE + The name of the GDCE zone. If set, the endpoint is in GDCE. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/beta/alloydb/clusters/create b/gcloud/beta/alloydb/clusters/create index d6edfa974..53b855952 100644 --- a/gcloud/beta/alloydb/clusters/create +++ b/gcloud/beta/alloydb/clusters/create @@ -7,7 +7,7 @@ SYNOPSIS --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async] [--database-version=DATABASE_VERSION] [--enable-private-service-connect] [--network=NETWORK] - [--subscription-type=SUBSCRIPTION_TYPE] + [--subscription-type=SUBSCRIPTION_TYPE] [--tags=[KEY=VALUE,...]] [--continuous-backup-recovery-window-days=RECOVERY_PERIOD --enable-continuous-backup [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY @@ -76,6 +76,12 @@ OPTIONAL FLAGS Subscription type of the cluster. SUBSCRIPTION_TYPE must be one of: STANDARD, TRIAL. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. + + Example: 123/environment=production,123/costCenter=marketing + Continuous Backup configuration. If unspecified, continuous backups are enabled. diff --git a/gcloud/beta/alloydb/clusters/help b/gcloud/beta/alloydb/clusters/help index 2cb363181..0701e8623 100644 --- a/gcloud/beta/alloydb/clusters/help +++ b/gcloud/beta/alloydb/clusters/help @@ -47,6 +47,9 @@ COMMANDS update (BETA) Update an AlloyDB cluster within a given project and region. + upgrade + (BETA) Upgrade an AlloyDB cluster within a given project and region. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/alloydb/clusters/upgrade b/gcloud/beta/alloydb/clusters/upgrade new file mode 100644 index 000000000..a9636ae85 --- /dev/null +++ b/gcloud/beta/alloydb/clusters/upgrade @@ -0,0 +1,49 @@ +NAME + gcloud beta alloydb clusters upgrade - upgrade an AlloyDB cluster within a + given project and region + +SYNOPSIS + gcloud beta alloydb clusters upgrade CLUSTER --region=REGION + --version=VERSION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Upgrade an AlloyDB cluster within a given project and region. + +EXAMPLES + To upgrade a cluster, run: + + $ gcloud beta alloydb clusters upgrade my-cluster \ + --region=us-central1 --version=POSTGRES_15 + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + + --version=VERSION + Target database version for the upgrade. VERSION must be one of: + POSTGRES_14, POSTGRES_15, POSTGRES_16. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb clusters upgrade + diff --git a/gcloud/beta/colab-enterprise/runtime-templates/add-iam-policy-binding b/gcloud/beta/colab-enterprise/runtime-templates/add-iam-policy-binding index 927293ad0..a35fdcd0c 100644 --- a/gcloud/beta/colab-enterprise/runtime-templates/add-iam-policy-binding +++ b/gcloud/beta/colab-enterprise/runtime-templates/add-iam-policy-binding @@ -51,7 +51,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime_template on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. REQUIRED FLAGS --member=PRINCIPAL diff --git a/gcloud/beta/colab-enterprise/runtime-templates/create b/gcloud/beta/colab-enterprise/runtime-templates/create index 2945fffb2..d15e28472 100644 --- a/gcloud/beta/colab-enterprise/runtime-templates/create +++ b/gcloud/beta/colab-enterprise/runtime-templates/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta colab-enterprise runtime-templates create - --display-name=DISPLAY_NAME --region=REGION [--async] + --display-name=DISPLAY_NAME [--async] [--region=REGION] [--runtime-template-id=RUNTIME_TEMPLATE_ID] [--description=DESCRIPTION --no-enable-euc --enable-secure-boot --idle-shutdown-timeout=IDLE_SHUTDOWN_TIMEOUT; default="3h" @@ -47,6 +47,11 @@ REQUIRED FLAGS --display-name=DISPLAY_NAME The display name of the runtime template. +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + Region resource - Cloud region to create runtime template. Please see https://cloud.google.com/colab/docs/locations for a list of supported regions. This represents a Cloud resource. (NOTE) Some attributes are not @@ -55,21 +60,16 @@ REQUIRED FLAGS To set the project attribute: ◆ provide the argument --region on the command line with a fully specified name; + ◆ set the property colab/region with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - --region=REGION ID of the region or fully qualified identifier for the region. To set the region attribute: - ▸ provide the argument --region on the command line. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. --runtime-template-id=RUNTIME_TEMPLATE_ID The id of the runtime template. If not specified, a random id will be diff --git a/gcloud/beta/colab-enterprise/runtime-templates/delete b/gcloud/beta/colab-enterprise/runtime-templates/delete index 87b25d78e..a50da67fa 100644 --- a/gcloud/beta/colab-enterprise/runtime-templates/delete +++ b/gcloud/beta/colab-enterprise/runtime-templates/delete @@ -48,7 +48,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime_template on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. FLAGS --async diff --git a/gcloud/beta/colab-enterprise/runtime-templates/describe b/gcloud/beta/colab-enterprise/runtime-templates/describe index 9a6dffd2f..a175665a0 100644 --- a/gcloud/beta/colab-enterprise/runtime-templates/describe +++ b/gcloud/beta/colab-enterprise/runtime-templates/describe @@ -48,7 +48,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime_template on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/colab-enterprise/runtime-templates/get-iam-policy b/gcloud/beta/colab-enterprise/runtime-templates/get-iam-policy index 29411e1d3..484e7e0a2 100644 --- a/gcloud/beta/colab-enterprise/runtime-templates/get-iam-policy +++ b/gcloud/beta/colab-enterprise/runtime-templates/get-iam-policy @@ -52,7 +52,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime_template on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/colab-enterprise/runtime-templates/list b/gcloud/beta/colab-enterprise/runtime-templates/list index 8372d220c..dda766996 100644 --- a/gcloud/beta/colab-enterprise/runtime-templates/list +++ b/gcloud/beta/colab-enterprise/runtime-templates/list @@ -3,7 +3,7 @@ NAME templates SYNOPSIS - gcloud beta colab-enterprise runtime-templates list --region=REGION + gcloud beta colab-enterprise runtime-templates list [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -17,7 +17,7 @@ EXAMPLES $ gcloud beta colab-enterprise runtime-templates list \ --region=us-central1 -REQUIRED FLAGS +FLAGS Region resource - Cloud region for which to list all runtime templates. Please see https://cloud.google.com/colab/docs/locations for a list of supported regions. This represents a Cloud resource. (NOTE) Some @@ -27,16 +27,16 @@ REQUIRED FLAGS To set the project attribute: ◆ provide the argument --region on the command line with a fully specified name; + ◆ set the property colab/region with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - --region=REGION ID of the region or fully qualified identifier for the region. To set the region attribute: - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/colab-enterprise/runtime-templates/remove-iam-policy-binding b/gcloud/beta/colab-enterprise/runtime-templates/remove-iam-policy-binding index 8220a783c..25bfcb7a6 100644 --- a/gcloud/beta/colab-enterprise/runtime-templates/remove-iam-policy-binding +++ b/gcloud/beta/colab-enterprise/runtime-templates/remove-iam-policy-binding @@ -52,7 +52,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime_template on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. REQUIRED FLAGS --member=PRINCIPAL diff --git a/gcloud/beta/colab-enterprise/runtime-templates/set-iam-policy b/gcloud/beta/colab-enterprise/runtime-templates/set-iam-policy index cbc991cb2..d2e712b0d 100644 --- a/gcloud/beta/colab-enterprise/runtime-templates/set-iam-policy +++ b/gcloud/beta/colab-enterprise/runtime-templates/set-iam-policy @@ -53,7 +53,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime_template on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. POLICY_FILE Path to a local JSON or YAML formatted file containing a valid policy. diff --git a/gcloud/beta/colab-enterprise/runtimes/assign b/gcloud/beta/colab-enterprise/runtimes/assign index 315db44be..b35c89557 100644 --- a/gcloud/beta/colab-enterprise/runtimes/assign +++ b/gcloud/beta/colab-enterprise/runtimes/assign @@ -3,10 +3,10 @@ NAME SYNOPSIS gcloud beta colab-enterprise runtimes assign --display-name=DISPLAY_NAME - --region=REGION --runtime-template=RUNTIME_TEMPLATE [--async] + --runtime-template=RUNTIME_TEMPLATE [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--runtime-id=RUNTIME_ID] [--runtime-user=RUNTIME_USER] - [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [--runtime-id=RUNTIME_ID] + [--runtime-user=RUNTIME_USER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Assign a notebook runtime to run code from your notebook (IPYNB @@ -30,25 +30,6 @@ REQUIRED FLAGS --display-name=DISPLAY_NAME The display name of the runtime to assign. - Region resource - Cloud region to assign runtime. Please see - https://cloud.google.com/colab/docs/locations for a list of supported - regions. 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 --region on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - --region=REGION - ID of the region or fully qualified identifier for the region. - - To set the region attribute: - ▸ provide the argument --region on the command line. - Runtime template resource - Unique name of the runtime template to configure the runtime with. This was optionally provided by setting --runtime-template-id in the create runtime-template command, or was @@ -65,7 +46,8 @@ REQUIRED FLAGS To set the region attribute: ◆ provide the argument --runtime-template on the command line with a fully specified name; - ◆ provide the argument --region on the command line. + ◆ provide the argument --region on the command line; + ◆ set the property colab/region. This must be specified. @@ -87,6 +69,25 @@ OPTIONAL FLAGS --labels=[KEY=VALUE,...] Add labels to identify and group the runtime template. + Region resource - Cloud region to assign runtime. Please see + https://cloud.google.com/colab/docs/locations for a list of supported + regions. 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 --region on the command line with a fully + specified name; + ◆ set the property colab/region with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. + --runtime-id=RUNTIME_ID The id of the runtime to assign. If not specified, a random id will be generated. diff --git a/gcloud/beta/colab-enterprise/runtimes/delete b/gcloud/beta/colab-enterprise/runtimes/delete index 6d7438e29..20a56a781 100644 --- a/gcloud/beta/colab-enterprise/runtimes/delete +++ b/gcloud/beta/colab-enterprise/runtimes/delete @@ -44,7 +44,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. FLAGS --async diff --git a/gcloud/beta/colab-enterprise/runtimes/describe b/gcloud/beta/colab-enterprise/runtimes/describe index b9ee9ee4f..6fc552d9c 100644 --- a/gcloud/beta/colab-enterprise/runtimes/describe +++ b/gcloud/beta/colab-enterprise/runtimes/describe @@ -44,7 +44,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/colab-enterprise/runtimes/list b/gcloud/beta/colab-enterprise/runtimes/list index 79fd00fd2..fb13ca450 100644 --- a/gcloud/beta/colab-enterprise/runtimes/list +++ b/gcloud/beta/colab-enterprise/runtimes/list @@ -2,7 +2,7 @@ NAME gcloud beta colab-enterprise runtimes list - list your project's runtimes SYNOPSIS - gcloud beta colab-enterprise runtimes list --region=REGION + gcloud beta colab-enterprise runtimes list [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -15,7 +15,7 @@ EXAMPLES $ gcloud beta colab-enterprise runtimes list --region=us-central1 -REQUIRED FLAGS +FLAGS Region resource - Cloud region for which to list all runtimes. Please see https://cloud.google.com/colab/docs/locations for a list of supported regions. This represents a Cloud resource. (NOTE) Some attributes are not @@ -24,16 +24,16 @@ REQUIRED FLAGS To set the project attribute: ◆ provide the argument --region on the command line with a fully specified name; + ◆ set the property colab/region with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - --region=REGION ID of the region or fully qualified identifier for the region. To set the region attribute: - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/colab-enterprise/runtimes/start b/gcloud/beta/colab-enterprise/runtimes/start index 122bb7e30..013024a28 100644 --- a/gcloud/beta/colab-enterprise/runtimes/start +++ b/gcloud/beta/colab-enterprise/runtimes/start @@ -44,7 +44,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. FLAGS --async diff --git a/gcloud/beta/colab-enterprise/runtimes/upgrade b/gcloud/beta/colab-enterprise/runtimes/upgrade index 5b2182d0c..4aed69754 100644 --- a/gcloud/beta/colab-enterprise/runtimes/upgrade +++ b/gcloud/beta/colab-enterprise/runtimes/upgrade @@ -44,7 +44,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. FLAGS --async diff --git a/gcloud/beta/colab/runtime-templates/add-iam-policy-binding b/gcloud/beta/colab/runtime-templates/add-iam-policy-binding index 846dad321..9f9b4d992 100644 --- a/gcloud/beta/colab/runtime-templates/add-iam-policy-binding +++ b/gcloud/beta/colab/runtime-templates/add-iam-policy-binding @@ -52,7 +52,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime_template on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. REQUIRED FLAGS --member=PRINCIPAL diff --git a/gcloud/beta/colab/runtime-templates/create b/gcloud/beta/colab/runtime-templates/create index 1f0f7e72b..a15792ce3 100644 --- a/gcloud/beta/colab/runtime-templates/create +++ b/gcloud/beta/colab/runtime-templates/create @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud beta colab runtime-templates create --display-name=DISPLAY_NAME - --region=REGION [--async] [--runtime-template-id=RUNTIME_TEMPLATE_ID] + [--async] [--region=REGION] [--runtime-template-id=RUNTIME_TEMPLATE_ID] [--description=DESCRIPTION --no-enable-euc --enable-secure-boot --idle-shutdown-timeout=IDLE_SHUTDOWN_TIMEOUT; default="3h" --labels=[KEY=VALUE,...] --network-tags=[TAGS,...] @@ -44,6 +44,11 @@ REQUIRED FLAGS --display-name=DISPLAY_NAME The display name of the runtime template. +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + Region resource - Cloud region to create runtime template. Please see https://cloud.google.com/colab/docs/locations for a list of supported regions. This represents a Cloud resource. (NOTE) Some attributes are not @@ -52,21 +57,16 @@ REQUIRED FLAGS To set the project attribute: ◆ provide the argument --region on the command line with a fully specified name; + ◆ set the property colab/region with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - --region=REGION ID of the region or fully qualified identifier for the region. To set the region attribute: - ▸ provide the argument --region on the command line. - -OPTIONAL FLAGS - --async - Return immediately, without waiting for the operation in progress to - complete. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. --runtime-template-id=RUNTIME_TEMPLATE_ID The id of the runtime template. If not specified, a random id will be diff --git a/gcloud/beta/colab/runtime-templates/delete b/gcloud/beta/colab/runtime-templates/delete index bec060399..89baf4e8f 100644 --- a/gcloud/beta/colab/runtime-templates/delete +++ b/gcloud/beta/colab/runtime-templates/delete @@ -47,7 +47,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime_template on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. FLAGS --async diff --git a/gcloud/beta/colab/runtime-templates/describe b/gcloud/beta/colab/runtime-templates/describe index 1504b543f..8601eec51 100644 --- a/gcloud/beta/colab/runtime-templates/describe +++ b/gcloud/beta/colab/runtime-templates/describe @@ -47,7 +47,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime_template on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/colab/runtime-templates/get-iam-policy b/gcloud/beta/colab/runtime-templates/get-iam-policy index 3acde5604..6b38b0878 100644 --- a/gcloud/beta/colab/runtime-templates/get-iam-policy +++ b/gcloud/beta/colab/runtime-templates/get-iam-policy @@ -52,7 +52,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime_template on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/colab/runtime-templates/list b/gcloud/beta/colab/runtime-templates/list index bc6bc4512..59ea6080d 100644 --- a/gcloud/beta/colab/runtime-templates/list +++ b/gcloud/beta/colab/runtime-templates/list @@ -2,7 +2,7 @@ NAME gcloud beta colab runtime-templates list - list your runtime templates SYNOPSIS - gcloud beta colab runtime-templates list --region=REGION + gcloud beta colab runtime-templates list [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -15,7 +15,7 @@ EXAMPLES $ gcloud beta colab runtime-templates list --region=us-central1 -REQUIRED FLAGS +FLAGS Region resource - Cloud region for which to list all runtime templates. Please see https://cloud.google.com/colab/docs/locations for a list of supported regions. This represents a Cloud resource. (NOTE) Some @@ -25,16 +25,16 @@ REQUIRED FLAGS To set the project attribute: ◆ provide the argument --region on the command line with a fully specified name; + ◆ set the property colab/region with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - --region=REGION ID of the region or fully qualified identifier for the region. To set the region attribute: - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/colab/runtime-templates/remove-iam-policy-binding b/gcloud/beta/colab/runtime-templates/remove-iam-policy-binding index 89edf9f61..bdfb88567 100644 --- a/gcloud/beta/colab/runtime-templates/remove-iam-policy-binding +++ b/gcloud/beta/colab/runtime-templates/remove-iam-policy-binding @@ -53,7 +53,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime_template on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. REQUIRED FLAGS --member=PRINCIPAL diff --git a/gcloud/beta/colab/runtime-templates/set-iam-policy b/gcloud/beta/colab/runtime-templates/set-iam-policy index 6fd059df4..eebcc6f01 100644 --- a/gcloud/beta/colab/runtime-templates/set-iam-policy +++ b/gcloud/beta/colab/runtime-templates/set-iam-policy @@ -52,7 +52,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime_template on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. POLICY_FILE Path to a local JSON or YAML formatted file containing a valid policy. diff --git a/gcloud/beta/colab/runtimes/assign b/gcloud/beta/colab/runtimes/assign index 51783a4b1..a2e001a15 100644 --- a/gcloud/beta/colab/runtimes/assign +++ b/gcloud/beta/colab/runtimes/assign @@ -3,10 +3,10 @@ NAME SYNOPSIS gcloud beta colab runtimes assign --display-name=DISPLAY_NAME - --region=REGION --runtime-template=RUNTIME_TEMPLATE [--async] + --runtime-template=RUNTIME_TEMPLATE [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--runtime-id=RUNTIME_ID] [--runtime-user=RUNTIME_USER] - [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [--runtime-id=RUNTIME_ID] + [--runtime-user=RUNTIME_USER] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Assign a notebook runtime to run code from your notebook (IPYNB @@ -29,25 +29,6 @@ REQUIRED FLAGS --display-name=DISPLAY_NAME The display name of the runtime to assign. - Region resource - Cloud region to assign runtime. Please see - https://cloud.google.com/colab/docs/locations for a list of supported - regions. 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 --region on the command line with a fully - specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. - - This must be specified. - - --region=REGION - ID of the region or fully qualified identifier for the region. - - To set the region attribute: - ▸ provide the argument --region on the command line. - Runtime template resource - Unique name of the runtime template to configure the runtime with. This was optionally provided by setting --runtime-template-id in the create runtime-template command, or was @@ -64,7 +45,8 @@ REQUIRED FLAGS To set the region attribute: ◆ provide the argument --runtime-template on the command line with a fully specified name; - ◆ provide the argument --region on the command line. + ◆ provide the argument --region on the command line; + ◆ set the property colab/region. This must be specified. @@ -86,6 +68,25 @@ OPTIONAL FLAGS --labels=[KEY=VALUE,...] Add labels to identify and group the runtime template. + Region resource - Cloud region to assign runtime. Please see + https://cloud.google.com/colab/docs/locations for a list of supported + regions. 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 --region on the command line with a fully + specified name; + ◆ set the property colab/region with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. + --runtime-id=RUNTIME_ID The id of the runtime to assign. If not specified, a random id will be generated. diff --git a/gcloud/beta/colab/runtimes/delete b/gcloud/beta/colab/runtimes/delete index d89f5e9ca..de7cee976 100644 --- a/gcloud/beta/colab/runtimes/delete +++ b/gcloud/beta/colab/runtimes/delete @@ -43,7 +43,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. FLAGS --async diff --git a/gcloud/beta/colab/runtimes/describe b/gcloud/beta/colab/runtimes/describe index 6c964d9f2..75e6988c7 100644 --- a/gcloud/beta/colab/runtimes/describe +++ b/gcloud/beta/colab/runtimes/describe @@ -43,7 +43,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/colab/runtimes/list b/gcloud/beta/colab/runtimes/list index ce632b8d8..95db3f786 100644 --- a/gcloud/beta/colab/runtimes/list +++ b/gcloud/beta/colab/runtimes/list @@ -2,7 +2,7 @@ NAME gcloud beta colab runtimes list - list your project's runtimes SYNOPSIS - gcloud beta colab runtimes list --region=REGION [--filter=EXPRESSION] + gcloud beta colab runtimes list [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -15,7 +15,7 @@ EXAMPLES $ gcloud beta colab runtimes list --region=us-central1 -REQUIRED FLAGS +FLAGS Region resource - Cloud region for which to list all runtimes. Please see https://cloud.google.com/colab/docs/locations for a list of supported regions. This represents a Cloud resource. (NOTE) Some attributes are not @@ -24,16 +24,16 @@ REQUIRED FLAGS To set the project attribute: ◆ provide the argument --region on the command line with a fully specified name; + ◆ set the property colab/region with a fully specified name; ◆ provide the argument --project on the command line; ◆ set the property core/project. - This must be specified. - --region=REGION ID of the region or fully qualified identifier for the region. To set the region attribute: - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/colab/runtimes/start b/gcloud/beta/colab/runtimes/start index f7b095895..1e2861ae2 100644 --- a/gcloud/beta/colab/runtimes/start +++ b/gcloud/beta/colab/runtimes/start @@ -43,7 +43,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. FLAGS --async diff --git a/gcloud/beta/colab/runtimes/upgrade b/gcloud/beta/colab/runtimes/upgrade index ea526cc36..25cfbe36f 100644 --- a/gcloud/beta/colab/runtimes/upgrade +++ b/gcloud/beta/colab/runtimes/upgrade @@ -43,7 +43,8 @@ POSITIONAL ARGUMENTS To set the region attribute: ▸ provide the argument runtime on the command line with a fully specified name; - ▸ provide the argument --region on the command line. + ▸ provide the argument --region on the command line; + ▸ set the property colab/region. FLAGS --async diff --git a/gcloud/beta/compute/backend-buckets/create b/gcloud/beta/compute/backend-buckets/create index bcc91197d..50100fd97 100644 --- a/gcloud/beta/compute/backend-buckets/create +++ b/gcloud/beta/compute/backend-buckets/create @@ -11,7 +11,8 @@ SYNOPSIS [--compression-mode=COMPRESSION_MODE] [--custom-response-header=CUSTOM_RESPONSE_HEADER] [--default-ttl=DEFAULT_TTL] [--description=DESCRIPTION] - [--[no-]enable-cdn] [--max-ttl=MAX_TTL] [--[no-]negative-caching] + [--[no-]enable-cdn] [--load-balancing-scheme=LOAD_BALANCING_SCHEME] + [--max-ttl=MAX_TTL] [--[no-]negative-caching] [--negative-caching-policy=[[CODE=TTL],...]] [--[no-]request-coalescing] [--serve-while-stale=SERVE_WHILE_STALE] [--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE] @@ -157,6 +158,12 @@ OPTIONAL FLAGS responses from a backend bucket at the edge of the network, close to users. Use --enable-cdn to enable and --no-enable-cdn to disable. + --load-balancing-scheme=LOAD_BALANCING_SCHEME + The load balancing scheme of the backend bucket. If left blank, the + backend bucket will be compatible with Global External Application Load + Balancer or Classic Application Load Balancer. LOAD_BALANCING_SCHEME + must be (only one value is supported): INTERNAL_MANAGED. + --max-ttl=MAX_TTL Specifies the maximum allowed TTL for cached content served by this origin. diff --git a/gcloud/beta/compute/commitments/create b/gcloud/beta/compute/commitments/create index df28c0538..904ee5ebe 100644 --- a/gcloud/beta/compute/commitments/create +++ b/gcloud/beta/compute/commitments/create @@ -5,6 +5,7 @@ SYNOPSIS gcloud beta compute commitments create COMMITMENT --plan=PLAN (--resources=[local-ssd=LOCAL-SSD],[memory=MEMORY],[vcpu=VCPU] --resources-accelerator=[count=COUNT],[type=TYPE]) [--auto-renew] + [--custom-end-time=CUSTOM_END_TIME] [--merge-source-commitments=MERGE_SOURCE_COMMITMENTS] [--region=REGION] [--split-source-commitment=SPLIT_SOURCE_COMMITMENT] [--type=TYPE; default="general-purpose"] @@ -70,6 +71,10 @@ OPTIONAL FLAGS --auto-renew Enable auto renewal for the commitment. + --custom-end-time=CUSTOM_END_TIME + Specifies a custom future end date and extends the commitment's ongoing + term. + --merge-source-commitments=MERGE_SOURCE_COMMITMENTS Creates the new commitment by merging the specified source commitments and combining their resources. diff --git a/gcloud/beta/compute/commitments/update b/gcloud/beta/compute/commitments/update index 03716e988..9df1ae9b5 100644 --- a/gcloud/beta/compute/commitments/update +++ b/gcloud/beta/compute/commitments/update @@ -3,7 +3,8 @@ NAME SYNOPSIS gcloud beta compute commitments update COMMITMENT [--auto-renew] - [--plan=PLAN] [--region=REGION] [GCLOUD_WIDE_FLAG ...] + [--custom-end-time=CUSTOM_END_TIME] [--plan=PLAN] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update Compute Engine commitments. @@ -35,6 +36,10 @@ FLAGS --auto-renew Enable auto renewal for the commitment. + --custom-end-time=CUSTOM_END_TIME + Specifies a custom future end date and extends the commitment's ongoing + term. + --plan=PLAN Duration of the commitment. PLAN must be (only one value is supported): 36-month. diff --git a/gcloud/beta/compute/instance-groups/managed/resize-requests/describe b/gcloud/beta/compute/instance-groups/managed/resize-requests/describe index 9bdcfed0e..26a07bdef 100644 --- a/gcloud/beta/compute/instance-groups/managed/resize-requests/describe +++ b/gcloud/beta/compute/instance-groups/managed/resize-requests/describe @@ -4,9 +4,9 @@ NAME resource SYNOPSIS - gcloud beta compute instance-groups managed resize-requests describe - INSTANCE_GROUP_MANAGER --resize-request=RESIZE_REQUEST_NAME - [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + gcloud beta compute instance-groups managed resize-requests describe NAME + --resize-request=RESIZE_REQUEST_NAME [--region=REGION | --zone=ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute instance-groups managed resize-requests describe @@ -20,7 +20,7 @@ EXAMPLES describe my-mig --resize-request=resize-request-1 POSITIONAL ARGUMENTS - INSTANCE_GROUP_MANAGER + NAME Name of the managed instance group to operate on. REQUIRED FLAGS @@ -28,26 +28,29 @@ REQUIRED FLAGS The name of the resize request to describe. OPTIONAL FLAGS - --zone=ZONE - Zone of the managed instance group to operate on. If not specified and - the compute/zone property isn't set, you might be prompted to select a - zone (interactive mode only). + At most one of these can be specified: - To avoid prompting when this flag is omitted, you can set the - compute/zone property: + --region=REGION + Region of the managed instance group to operate on. If not specified, + you might be prompted to select a region (interactive mode only). - $ gcloud config set compute/zone ZONE + A list of regions can be fetched by running: - A list of zones can be fetched by running: + $ gcloud compute regions list - $ gcloud compute zones list + Overrides the default compute/region property value for this command + invocation. - To unset the property, run: + --zone=ZONE + Zone of the managed instance group to operate on. If not specified, + you might be prompted to select a zone (interactive mode only). - $ gcloud config unset compute/zone + A list of zones can be fetched by running: - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/compute/instance-groups/managed/resize-requests/list b/gcloud/beta/compute/instance-groups/managed/resize-requests/list index 2e3eb707c..e586fb932 100644 --- a/gcloud/beta/compute/instance-groups/managed/resize-requests/list +++ b/gcloud/beta/compute/instance-groups/managed/resize-requests/list @@ -3,9 +3,9 @@ NAME Compute Engine managed instance group resize requests SYNOPSIS - gcloud beta compute instance-groups managed resize-requests list - INSTANCE_GROUP_MANAGER [--zone=ZONE] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud beta compute instance-groups managed resize-requests list NAME + [--region=REGION | --zone=ZONE] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -24,30 +24,33 @@ EXAMPLES example-managed-instance-group --zone=us-central1-a --uri POSITIONAL ARGUMENTS - INSTANCE_GROUP_MANAGER + NAME Name of the managed instance group to operate on. FLAGS - --zone=ZONE - Zone of the managed instance group to operate on. If not specified and - the compute/zone property isn't set, you might be prompted to select a - zone (interactive mode only). + At most one of these can be specified: - To avoid prompting when this flag is omitted, you can set the - compute/zone property: + --region=REGION + Region of the managed instance group to operate on. If not specified, + you might be prompted to select a region (interactive mode only). - $ gcloud config set compute/zone ZONE + A list of regions can be fetched by running: - A list of zones can be fetched by running: + $ gcloud compute regions list - $ gcloud compute zones list + Overrides the default compute/region property value for this command + invocation. - To unset the property, run: + --zone=ZONE + Zone of the managed instance group to operate on. If not specified, + you might be prompted to select a zone (interactive mode only). - $ gcloud config unset compute/zone + A list of zones can be fetched by running: - Alternatively, the zone can be stored in the environment variable - CLOUDSDK_COMPUTE_ZONE. + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/compute/snapshot-settings/describe b/gcloud/beta/compute/snapshot-settings/describe index 0713ce750..35b0888f1 100644 --- a/gcloud/beta/compute/snapshot-settings/describe +++ b/gcloud/beta/compute/snapshot-settings/describe @@ -21,8 +21,9 @@ GCLOUD WIDE FLAGS 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/ + This command uses the compute/alpha or compute/beta or comptue/v1 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. These diff --git a/gcloud/beta/compute/snapshot-settings/update b/gcloud/beta/compute/snapshot-settings/update index 7ae1794a9..6d39f164e 100644 --- a/gcloud/beta/compute/snapshot-settings/update +++ b/gcloud/beta/compute/snapshot-settings/update @@ -15,19 +15,20 @@ EXAMPLES nearest multi-region as the source disk, run: $ gcloud beta compute snapshot-settings update \ - --storage-location-policy=nearest-multi-region + --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 + $ gcloud beta 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 + --storage-location-policy=specific-locations \ + --storage-location-names=us-west1 FLAGS --async @@ -58,8 +59,9 @@ GCLOUD WIDE FLAGS 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/ + This command uses the compute/alpha or compute/beta or compute/v1 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. These diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index c9aac88e7..750d7584a 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -731,6 +731,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 4fa67a691..5214ef9cf 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -763,6 +763,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 8506e1051..52eeba4b5 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -775,6 +775,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 0104a25cc..d00c3d6a8 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -778,6 +778,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 8564ba7d2..3578e6076 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -739,6 +739,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 63f9acb38..0df3f937e 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -18,15 +18,16 @@ SYNOPSIS [--enable-backup-restore] [--enable-cilium-clusterwide-network-policy] [--enable-dns-access] [--enable-fleet] [--enable-google-cloud-access] [--enable-ip-access] [--enable-kubernetes-unstable-apis=API,[API,...]] - [--enable-master-global-access] [--enable-ray-cluster-logging] - [--enable-ray-cluster-monitoring] [--enable-ray-operator] - [--enable-secret-manager] [--fleet-project=PROJECT_ID_OR_NUMBER] - [--labels=[KEY=VALUE,...]] [--logging=[COMPONENT,...]] - [--monitoring=[COMPONENT,...]] [--network=NETWORK] - [--private-endpoint-subnetwork=NAME] [--release-channel=[CHANNEL]] - [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] - [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] - [--subnetwork=SUBNETWORK] [--workload-policies=WORKLOAD_POLICIES] + [--enable-master-global-access] [--enable-multi-networking] + [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] + [--enable-ray-operator] [--enable-secret-manager] + [--fleet-project=PROJECT_ID_OR_NUMBER] [--labels=[KEY=VALUE,...]] + [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] + [--network=NETWORK] [--private-endpoint-subnetwork=NAME] + [--release-channel=[CHANNEL]] [--security-group=SECURITY_GROUP] + [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] + [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] + [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--additive-vpc-scope-dns-domain=ADDITIVE_VPC_SCOPE_DNS_DOMAIN | --disable-additive-vpc-scope] @@ -263,6 +264,10 @@ FLAGS endpoint from any Google Cloud region or on-premises environment regardless of the private cluster's region. + --enable-multi-networking + Enables multi-networking on the cluster. Multi-networking is disabled + by default. + --enable-ray-cluster-logging Enable automatic log processing sidecar for Ray clusters. diff --git a/gcloud/beta/dataproc/clusters/create b/gcloud/beta/dataproc/clusters/create index 2a795fec0..b80d726e1 100644 --- a/gcloud/beta/dataproc/clusters/create +++ b/gcloud/beta/dataproc/clusters/create @@ -46,7 +46,6 @@ SYNOPSIS [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] - [--worker-machine-type=WORKER_MACHINE_TYPE] [--worker-min-cpu-platform=PLATFORM] [--zone=ZONE, -z ZONE] [--expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE] [--gce-pd-kms-key=GCE_PD_KMS_KEY @@ -68,7 +67,9 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] - [GCLOUD_WIDE_FLAG ...] + [--worker-machine-type=WORKER_MACHINE_TYPE + | --worker-machine-types=type=MACHINE_TYPE[, + type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a cluster. @@ -427,9 +428,6 @@ FLAGS --worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE Interface to use to attach local SSDs to each worker in a cluster. - --worker-machine-type=WORKER_MACHINE_TYPE - The type of machine to use for workers. Defaults to server-specified. - --worker-min-cpu-platform=PLATFORM When specified, the VM is scheduled on the host with a specified CPU architecture or a more recent CPU platform that's available in that @@ -862,6 +860,25 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. + At most one of these can be specified: + + --worker-machine-type=WORKER_MACHINE_TYPE + The type of machine to use for primary workers. Defaults to + server-specified. + + --worker-machine-types=type=MACHINE_TYPE[,type=MACHINE_TYPE...][,rank=RANK] + Machine types + (https://cloud.google.com/dataproc/docs/concepts/compute/supported-machine-types) + for primary worker nodes to use with optional rank. A lower rank + number is given higher preference. Based on availablilty, Dataproc + tries to create primary worker VMs using the worker machine type with + the lowest rank, and then tries to use machine types with higher + ranks as necessary. Machine types with the same rank are given the + same preference. Example use: + --worker-machine-types="type=e2-standard-8,type=n2-standard-8,rank=0". + For more information, see Dataproc Flexible VMs + (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/flexible-vms) + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster index c83d191bd..bdeed39ab 100644 --- a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster @@ -39,7 +39,6 @@ SYNOPSIS [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] - [--worker-machine-type=WORKER_MACHINE_TYPE] [--worker-min-cpu-platform=PLATFORM] [--zone=ZONE, -z ZONE] [--image=IMAGE | --image-version=VERSION] [--kerberos-config-file=KERBEROS_CONFIG_FILE | --enable-kerberos @@ -56,7 +55,9 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] - [GCLOUD_WIDE_FLAG ...] + [--worker-machine-type=WORKER_MACHINE_TYPE + | --worker-machine-types=type=MACHINE_TYPE[, + type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Set a managed cluster for the workflow template. @@ -359,9 +360,6 @@ FLAGS --worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE Interface to use to attach local SSDs to each worker in a cluster. - --worker-machine-type=WORKER_MACHINE_TYPE - The type of machine to use for workers. Defaults to server-specified. - --worker-min-cpu-platform=PLATFORM When specified, the VM is scheduled on the host with a specified CPU architecture or a more recent CPU platform that's available in that @@ -738,6 +736,25 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. + At most one of these can be specified: + + --worker-machine-type=WORKER_MACHINE_TYPE + The type of machine to use for primary workers. Defaults to + server-specified. + + --worker-machine-types=type=MACHINE_TYPE[,type=MACHINE_TYPE...][,rank=RANK] + Machine types + (https://cloud.google.com/dataproc/docs/concepts/compute/supported-machine-types) + for primary worker nodes to use with optional rank. A lower rank + number is given higher preference. Based on availablilty, Dataproc + tries to create primary worker VMs using the worker machine type with + the lowest rank, and then tries to use machine types with higher + ranks as necessary. Machine types with the same rank are given the + same preference. Example use: + --worker-machine-types="type=e2-standard-8,type=n2-standard-8,rank=0". + For more information, see Dataproc Flexible VMs + (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/flexible-vms) + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/network-management/connectivity-tests/create b/gcloud/beta/network-management/connectivity-tests/create index b7e27ab15..3863b1c21 100644 --- a/gcloud/beta/network-management/connectivity-tests/create +++ b/gcloud/beta/network-management/connectivity-tests/create @@ -8,7 +8,9 @@ SYNOPSIS --destination-forwarding-rule=DESTINATION_FORWARDING_RULE --destination-gke-master-cluster=DESTINATION_GKE_MASTER_CLUSTER --destination-instance=DESTINATION_INSTANCE - --destination-ip-address=DESTINATION_IP_ADDRESS) + --destination-ip-address=DESTINATION_IP_ADDRESS + --destination-redis-cluster=DESTINATION_REDIS_CLUSTER + --destination-redis-instance=DESTINATION_REDIS_INSTANCE) (--source-app-engine-version=SOURCE_APP_ENGINE_VERSION --source-cloud-function=SOURCE_CLOUD_FUNCTION --source-cloud-run-revision=SOURCE_CLOUD_RUN_REVISION @@ -78,6 +80,12 @@ REQUIRED FLAGS The IP address of the destination which can be an external or internal IP. + --destination-redis-cluster=DESTINATION_REDIS_CLUSTER + A Redis cluster URI as the destination endpoint. + + --destination-redis-instance=DESTINATION_REDIS_INSTANCE + A Redis instance URI as the destination endpoint. + At least one of these must be specified: --source-app-engine-version=SOURCE_APP_ENGINE_VERSION diff --git a/gcloud/beta/network-management/connectivity-tests/update b/gcloud/beta/network-management/connectivity-tests/update index 60c3e1ceb..df3a207c7 100644 --- a/gcloud/beta/network-management/connectivity-tests/update +++ b/gcloud/beta/network-management/connectivity-tests/update @@ -22,6 +22,10 @@ SYNOPSIS | --destination-instance=DESTINATION_INSTANCE] [--clear-destination-ip-address | --destination-ip-address=DESTINATION_IP_ADDRESS] + [--clear-destination-redis-cluster + | --destination-redis-cluster=DESTINATION_REDIS_CLUSTER] + [--clear-destination-redis-instance + | --destination-redis-instance=DESTINATION_REDIS_INSTANCE] [--clear-source-app-engine-version | --source-app-engine-version=SOURCE_APP_ENGINE_VERSION] [--clear-source-cloud-function @@ -153,6 +157,22 @@ FLAGS The IP address of the destination which can be an external or internal IP. + At most one of these can be specified: + + --clear-destination-redis-cluster + Clear existing destination Redis Cluster. + + --destination-redis-cluster=DESTINATION_REDIS_CLUSTER + A Redis cluster URI as the destination endpoint. + + At most one of these can be specified: + + --clear-destination-redis-instance + Clear existing destination Redis Instance. + + --destination-redis-instance=DESTINATION_REDIS_INSTANCE + A Redis instance URI as the destination endpoint. + At most one of these can be specified: --clear-source-app-engine-version diff --git a/gcloud/beta/redis/clusters/create b/gcloud/beta/redis/clusters/create index 4fc48db05..b9d7a3dd6 100644 --- a/gcloud/beta/redis/clusters/create +++ b/gcloud/beta/redis/clusters/create @@ -4,12 +4,11 @@ NAME SYNOPSIS gcloud beta redis clusters create (CLUSTER : --region=REGION) - --network=NETWORK [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] - [--auth-mode=AUTH_MODE] + [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] [--auth-mode=AUTH_MODE] [--cross-cluster-replication-role=CROSS_CLUSTER_REPLICATION_ROLE] [--deletion-protection] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] - [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [--network=NETWORK] [--node-type=NODE_TYPE] [--persistence-mode=PERSISTENCE_MODE] [--primary-cluster=PRIMARY_CLUSTER] [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] @@ -83,14 +82,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property redis/region. -REQUIRED FLAGS - --network=NETWORK - The network used to create your instance. It must use the format: - projects/NETWORK_PROJECT_ID/global/networks/NETWORK_ID. The network ID - used here must match the network ID used by the service connection - policy. Otherwise, the create operation fails - -OPTIONAL FLAGS +FLAGS --aof-append-fsync=AOF_APPEND_FSYNC Fsync configuration. AOF_APPEND_FSYNC must be one of: @@ -137,6 +129,12 @@ OPTIONAL FLAGS Hour of day (0 to 23) for the start of maintenance window, in UTC time zone. + --network=NETWORK + The network used to create your instance. It must use the format: + projects/NETWORK_PROJECT_ID/global/networks/NETWORK_ID. The network ID + used here must match the network ID used by the service connection + policy. Otherwise, the create operation fails + --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 8582b542a..2f0c49953 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -2,13 +2,32 @@ NAME gcloud beta run deploy - create or update a Cloud Run service SYNOPSIS - gcloud beta run deploy [[SERVICE] --namespace=NAMESPACE] [--async] - [--concurrency=CONCURRENCY] [--container=CONTAINER] - [--ingress=INGRESS; default="all"] [--max-instances=MAX_INSTANCES] - [--min-instances=MIN_INSTANCES] - [--platform=PLATFORM; default="managed"] - [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] - [--no-traffic] + gcloud beta run deploy [[SERVICE] --namespace=NAMESPACE] + [--[no-]allow-unauthenticated] [--async] [--breakglass=JUSTIFICATION] + [--clear-vpc-connector] [--concurrency=CONCURRENCY] + [--container=CONTAINER] [--[no-]cpu-boost] [--[no-]cpu-throttling] + [--[no-]default-url] [--[no-]deploy-health-check] + [--description=DESCRIPTION] + [--execution-environment=EXECUTION_ENVIRONMENT] [--gpu-type=GPU_TYPE] + [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] + [--max-instances=MAX_INSTANCES] [--mesh=MESH] + [--min-instances=MIN_INSTANCES] [--region=REGION] + [--remove-containers=[CONTAINER,...]] + [--revision-suffix=REVISION_SUFFIX] [--service-account=SERVICE_ACCOUNT] + [--service-min-instances=SERVICE_MIN_INSTANCES] + [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] + [--no-traffic] [--vpc-connector=VPC_CONNECTOR] + [--vpc-egress=VPC_EGRESS] + [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --clear-cloudsql-instances + | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--add-custom-audiences=[CUSTOM-AUDIENCES,...] + | --clear-custom-audiences + | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + | --set-custom-audiences=[CUSTOM-AUDIENCES,...]] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --[no-]automatic-updates --clear-volume-mounts --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --memory=MEMORY @@ -27,39 +46,21 @@ SYNOPSIS | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...] --command=[COMMAND,...] | --function=FUNCTION --image=IMAGE | --source=SOURCE] + [--binary-authorization=POLICY | --clear-binary-authorization] + [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] + | --remove-config-maps=[KEY,...] + --update-config-maps=[KEY=VALUE,...]] + [--clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] + [--clear-key | --key=KEY] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] - [--connectivity=CONNECTIVITY --clear-config-maps - | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] - [--[no-]allow-unauthenticated --breakglass=JUSTIFICATION - --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling - --[no-]default-url --[no-]deploy-health-check - --description=DESCRIPTION - --execution-environment=EXECUTION_ENVIRONMENT --gpu-type=GPU_TYPE - --[no-]invoker-iam-check --mesh=MESH - --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX - --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity - --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --clear-cloudsql-instances - | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - | --clear-custom-audiences - | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --add-volume=[KEY=VALUE,...] --clear-volumes - --remove-volume=[VOLUME,...] --binary-authorization=POLICY - | --clear-binary-authorization --clear-encryption-key-shutdown-hours - | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - --clear-key | --key=KEY --clear-network + [--clear-network | --network=NETWORK --subnet=SUBNET --clear-network-tags - | --network-tags=[TAG,...] --clear-post-key-revocation-action-type + | --network-tags=[TAG,...]] + [--clear-post-key-revocation-action-type | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates or updates a Cloud Run service. @@ -108,10 +109,25 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS + --[no-]allow-unauthenticated + Whether to enable allowing unauthenticated access to the service. This + may take a few moments to take effect. Use --allow-unauthenticated to + enable and --no-allow-unauthenticated to disable. + --async Return immediately, without waiting for the operation in progress to complete. + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. + + --clear-vpc-connector + Remove the VPC connector for this resource. + --concurrency=CONCURRENCY Set the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified or provide the special value @@ -121,64 +137,112 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + --[no-]cpu-boost + Whether to allocate extra CPU to containers on startup to reduce the + perceived latency of a cold start request. Enabled by default when + unspecified on new services. Use --cpu-boost to enable and + --no-cpu-boost to disable. + + --[no-]cpu-throttling + Whether to throttle the CPU when the container is not actively serving + requests. Use --cpu-throttling to enable and --no-cpu-throttling to + disable. + + --[no-]default-url + Toggles the default url for a run service. This is enabled by default + if not specified. Use --default-url to enable and --no-default-url to + disable. + + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + + --description=DESCRIPTION + Provides an optional, human-readable description of the service. + + --execution-environment=EXECUTION_ENVIRONMENT + Selects the execution environment where the application will run. + EXECUTION_ENVIRONMENT must be one of: + + gen1 + Run the application in a first generation execution environment. + gen2 + Run the application in a second generation execution environment. + + --gpu-type=GPU_TYPE + The GPU type to use. + --ingress=INGRESS; default="all" Set the ingress traffic sources allowed to call the service. For Cloud - Run (fully managed) the --[no-]allow-unauthenticated flag separately - controls the identities allowed to call the service. INGRESS must be - one of: + Run the --[no-]allow-unauthenticated flag separately controls the + identities allowed to call the service. INGRESS must be one of: all Inbound requests from all sources are allowed. internal - For Cloud Run (fully managed), only inbound requests from VPC - networks in the same project or VPC Service Controls perimeter, as - well as Pub/Sub subscriptions and Eventarc events in the same - project or VPC Service Controls perimeter are allowed. All other - requests are rejected. See - https://cloud.google.com/run/docs/securing/ingress for full details - on the definition of internal traffic for Cloud Run (fully - managed). For Cloud Run for Anthos, only inbound requests from the - same cluster are allowed. + For Cloud Run, only inbound requests from VPC networks in the same + project or VPC Service Controls perimeter, as well as Pub/Sub + subscriptions and Eventarc events in the same project or VPC + Service Controls perimeter are allowed. All other requests are + rejected. See https://cloud.google.com/run/docs/securing/ingress + for full details on the definition of internal traffic for Cloud + Run. internal-and-cloud-load-balancing - Only supported for Cloud Run (fully managed). Only inbound requests - from Google Cloud Load Balancing or a traffic source allowed by the - internal option are allowed. + Only inbound requests from Google Cloud Load Balancing or a traffic + source allowed by the internal option are allowed. + + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. --max-instances=MAX_INSTANCES The maximum number of container instances of the Service to run. Use 'default' to unset the limit and use the platform default. + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. Mesh + resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + --min-instances=MIN_INSTANCES The minimum number of container instances for this Revision of the Service to run or 'default' to remove any minimum. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --remove-containers=[CONTAINER,...] + List of containers to remove. + + --revision-suffix=REVISION_SUFFIX + Specify the suffix of the revision name. Revision names always start + with the service name automatically. For example, specifying + [--revision-suffix=v1] for a service named 'helloworld', would lead to + a revision named 'helloworld-v1'. Set empty string to clear the suffix + and resume server-assigned naming. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. For the managed platform, - this is the email address of an IAM service account. For the - Kubernetes-based platforms (gke, kubernetes), this is the name of a - Kubernetes service account in the same namespace as the service. If not - provided, the revision will use the default service account of the - project, or default Kubernetes namespace service account respectively. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. + + --service-min-instances=SERVICE_MIN_INSTANCES + The minimum number of container instances for this Service to run or + 'default' to remove any minimum. These instances will be divided among + all Revisions receiving a percentage of traffic. + + --[no-]session-affinity + Whether to enable session affinity for connections to the service. Use + --session-affinity to enable and --no-session-affinity to disable. --tag=TAG Traffic tag to assign to the newly created revision. @@ -200,6 +264,109 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. + --vpc-connector=VPC_CONNECTOR + Set a VPC connector for this resource. + + --vpc-egress=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 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 Direct VPC egress or the VPC + connector. + private-ranges-only + 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 + region as your Cloud Run service; otherwise specify + :: for the instance. + + At most one of these can be specified: + + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Append the given values to the current Cloud SQL instances. + + --clear-cloudsql-instances + Empty the current Cloud SQL instances. + + --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Remove the given values from the current Cloud SQL instances. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Completely replace the current Cloud SQL instances with the given + values. + + These flags modify the custom audiences that can be used in the audience + field of ID token for authenticated requests. + + At most one of these can be specified: + + --add-custom-audiences=[CUSTOM-AUDIENCES,...] + Append the given values to the current custom audiences. + + --clear-custom-audiences + Empty the current custom audiences. + + --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + Remove the given values from the current custom audiences. + + --set-custom-audiences=[CUSTOM-AUDIENCES,...] + Completely replace the current custom audiences with the given + values. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + in-memory: An ephemeral volume that stores data in the instance's + memory. With this type of volume, data is not shared between instances + and all data will be lost when the instance it is on is terminated. + Additional keys: + ◆ size-limit: (optional) A quantity representing the maximum amount + of memory allocated to this volume, such as "512Mi" or "3G". Data + stored in an in-memory volume consumes the memory allocation of the + container that wrote the data. If size-limit is not specified, the + maximum size will be half the total memory limit of all containers. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + Container Flags The following flags apply to a single container. If the --container flag is specified these flags may only be @@ -229,12 +396,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. @@ -394,7 +557,7 @@ FLAGS --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/hello:latest). --source=SOURCE The location of the source to build. If a Dockerfile is present @@ -412,6 +575,63 @@ FLAGS global .gitignore is not respected. For more information on .gcloudignore, see gcloud topic gcloudignore. + At most one of these can be specified: + + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". + + --clear-binary-authorization + Remove any previously set Binary Authorization policy. + + Specify config map to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. The values associated with each of + these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may + omit the key within the config map to specify a mount of all keys within + the config map. For example: + '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will + create a volume with config map 'myconfig' and mount that volume at + '/my/path'. Because no config map key was specified, all keys in + 'myconfig' will be included. An environment variable named ENV will also + be created whose value is the value of 'key.json' in 'otherconfig. Not + supported on the fully managed version of Cloud Run. + + At most one of these can be specified: + + --clear-config-maps + Remove all config-maps. + + --set-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. All existing + config-maps will be removed first. + + Only --update-config-maps and --remove-config-maps can be used together. + If both are specified, --remove-config-maps will be applied first. + + --remove-config-maps=[KEY,...] + List of config-maps to be removed. + + --update-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. + + At most one of these can be specified: + + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. + + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server after + CMEK key revocation is detected. + + At most one of these can be specified: + + --clear-key + Remove any previously set CMEK key reference. + + --key=KEY + CMEK key reference to encrypt the container with. + At most one of these can be specified: --clear-labels @@ -443,386 +663,53 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - --connectivity=CONNECTIVITY - (DEPRECATED) Defaults to 'external'. If 'external', the service can - be invoked through the internet, in addition to through the cluster - network. - - The --connectivity flag is deprecated but will continue to be - supported. Prefer to use the --ingress flag instead. CONNECTIVITY - must be one of: - - external - Visible from outside the cluster. - internal - Visible only within the cluster. - - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. - - At most one of these can be specified: - - --clear-config-maps - Remove all config-maps. - - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used - together. If both are specified, --remove-config-maps will be applied - first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --[no-]allow-unauthenticated - Whether to enable allowing unauthenticated access to the service. - This may take a few moments to take effect. Use - --allow-unauthenticated to enable and --no-allow-unauthenticated to - disable. - - --breakglass=JUSTIFICATION - Justification to bypass Binary Authorization policy constraints and - allow the operation. See - https://cloud.google.com/binary-authorization/docs/using-breakglass - for more information. Next update or deploy command will - automatically clear existing breakglass justification. - - --clear-vpc-connector - Remove the VPC connector for this resource. - - --[no-]cpu-boost - Whether to allocate extra CPU to containers on startup to reduce the - perceived latency of a cold start request. Enabled by default when - unspecified on new services. Use --cpu-boost to enable and - --no-cpu-boost to disable. - - --[no-]cpu-throttling - Whether to throttle the CPU when the container is not actively - serving requests. Use --cpu-throttling to enable and - --no-cpu-throttling to disable. - - --[no-]default-url - Toggles the default url for a run service. This is enabled by default - if not specified. Use --default-url to enable and --no-default-url to - disable. - - --[no-]deploy-health-check - Schedules a single instance of the Revision and waits for it to pass - its startup probe for the deployment to succeed. If disabled, the - startup probe runs only when the revision is first started via - invocation or by setting min-instances. This check is enabled by - default when unspecified. Use --deploy-health-check to enable and - --no-deploy-health-check to disable. - - --description=DESCRIPTION - Provides an optional, human-readable description of the service. - - --execution-environment=EXECUTION_ENVIRONMENT - Selects the execution environment where the application will run. - EXECUTION_ENVIRONMENT must be one of: - - gen1 - Run the application in a first generation execution environment. - gen2 - Run the application in a second generation execution environment. - - --gpu-type=GPU_TYPE - The GPU type to use. - - --[no-]invoker-iam-check - Optionally disable invoker IAM checks. This feature is available by - invitation only. More info at - https://cloud.google.com/run/docs/securing/managing-access#invoker_check. - Use --invoker-iam-check to enable and --no-invoker-iam-check to - disable. - - --mesh=MESH - Enables Cloud Service Mesh using the specified mesh resource name. - Mesh resource name must be in the format of - projects/PROJECT/locations/global/meshes/MESH_NAME. - - --remove-containers=[CONTAINER,...] - List of containers to remove. - - --revision-suffix=REVISION_SUFFIX - Specify the suffix of the revision name. Revision names always start - with the service name automatically. For example, specifying - [--revision-suffix=v1] for a service named 'helloworld', would lead - to a revision named 'helloworld-v1'. Set empty string to clear the - suffix and resume server-assigned naming. - - --service-min-instances=SERVICE_MIN_INSTANCES - The minimum number of container instances for this Service to run or - 'default' to remove any minimum. These instances will be divided - among all Revisions receiving a percentage of traffic. - - --[no-]session-affinity - Whether to enable session affinity for connections to the service. - Use --session-affinity to enable and --no-session-affinity to - disable. - - --vpc-connector=VPC_CONNECTOR - Set a VPC connector for this resource. - - --vpc-egress=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 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 Direct VPC egress or the VPC - connector. - private-ranges-only - 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 region as your Cloud Run service; otherwise specify - :: for the instance. - - At most one of these can be specified: - - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Append the given values to the current Cloud SQL instances. - - --clear-cloudsql-instances - Empty the current Cloud SQL instances. - - --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Remove the given values from the current Cloud SQL instances. - - --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Completely replace the current Cloud SQL instances with the given - values. - - These flags modify the custom audiences that can be used in the audience - field of ID token for authenticated requests. - - At most one of these can be specified: - - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - Append the given values to the current custom audiences. - - --clear-custom-audiences - Empty the current custom audiences. - - --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - Remove the given values from the current custom audiences. - - --set-custom-audiences=[CUSTOM-AUDIENCES,...] - Completely replace the current custom audiences with the given - values. - - --add-volume=[KEY=VALUE,...] - Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: - - cloud-storage: A volume representing a Cloud Storage bucket. This - volume type is mounted using Cloud Storage FUSE. See - https://cloud.google.com/storage/docs/gcs-fuse for the details and - limitations of this filesystem. Additional keys: - ◆ bucket: (required) the name of the bucket to use as the source of - this volume - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - - in-memory: An ephemeral volume that stores data in the instance's memory. - With this type of volume, data is not shared between instances and all - data will be lost when the instance it is on is terminated. Additional - keys: - ◆ size-limit: (optional) A quantity representing the maximum amount of - memory allocated to this volume, such as "512Mi" or "3G". Data stored - in an in-memory volume consumes the memory allocation of the container - that wrote the data. If size-limit is not specified, the maximum size - will be half the total memory limit of all containers. - - nfs: Represents a volume backed by an NFS server. Additional keys: - ◆ location: (required) The location of the NFS Server, in the form - SERVER:/PATH - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - - --clear-volumes - Remove all existing volumes from the Cloud Run resource, including - volumes mounted as secrets - - --remove-volume=[VOLUME,...] - Removes volumes from the Cloud Run resource. - - At most one of these can be specified: - - --binary-authorization=POLICY - Binary Authorization policy to check against. This must be set to - "default". - - --clear-binary-authorization - Remove any previously set Binary Authorization policy. - - At most one of these can be specified: - - --clear-encryption-key-shutdown-hours - Remove any previously set CMEK key shutdown hours setting. - - --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - The number of hours to wait before an automatic shutdown server - after CMEK key revocation is detected. - - At most one of these can be specified: - - --clear-key - Remove any previously set CMEK key reference. - - --key=KEY - CMEK key reference to encrypt the container with. - - At most one of these can be specified: - - --clear-network - Disconnect this Cloud Run service from the VPC network it is - connected to. - - Direct VPC egress setting flags group. - - --network=NETWORK - The VPC network that the Cloud Run service will be able to send - traffic to. If --subnet is also specified, subnet must be a - subnetwork of the network specified by this --network flag. To - clear existing VPC network settings, use --clear-network. - - --subnet=SUBNET - The VPC subnetwork that the Cloud Run service will get IPs from. - The subnetwork must be /26 or larger. If --network is also - specified, subnet must be a subnetwork of the network specified - by the --network flag. If --network is not specified, network - will be looked up from this subnetwork. To clear existing VPC - network settings, use --clear-network. - - At most one of these can be specified: - - --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. - - --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. - - At most one of these can be specified: - - --clear-post-key-revocation-action-type - Remove any previously set post CMEK key revocation action type. - - --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE - Action type after CMEK key revocation. - POST_KEY_REVOCATION_ACTION_TYPE must be one of: - - prevent-new - No new instances will be started after CMEK key revocation. - shut-down - No new instances will be started and the existing instances - will be shut down after CMEK key revocation. - - Arguments to locate resources, depending on the platform used. + At most one of these can be specified: + + --clear-network + Disconnect this Cloud Run service from the VPC network it is + connected to. + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run service will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. + + --subnet=SUBNET + The VPC subnetwork that the Cloud Run service will get IPs from. + The subnetwork must be /26 or larger. If --network is also + specified, subnet must be a subnetwork of the network specified by + the --network flag. If --network is not specified, network will be + looked up from this subnetwork. To clear existing VPC network + settings, use --clear-network. + + At most one of these can be specified: + + --clear-network-tags + Clears all existing Compute Engine tags from the Cloud Run + service. + + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. To clear existing tags, use + --clear-network-tags. At most one of these can be specified: - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. + --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE + Action type after CMEK key revocation. + POST_KEY_REVOCATION_ACTION_TYPE must be one of: - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▸ set the property run/cluster with a fully specified name; - ▸ specify the cluster from a list of available clusters with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the - cluster. - - To set the cluster attribute: - ▫ provide the argument --cluster on the command line; - ▫ set the property run/cluster; - ▫ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ▫ provide the argument --cluster on the command line with a - fully specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --cluster-location on the command line; - ▫ set the property run/cluster_location; - ▫ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + prevent-new + No new instances will be started after CMEK key revocation. + shut-down + No new instances will be started and the existing instances will + be shut down after CMEK key revocation. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/domain-mappings/create b/gcloud/beta/run/domain-mappings/create index cdd0d2514..1e76a780f 100644 --- a/gcloud/beta/run/domain-mappings/create +++ b/gcloud/beta/run/domain-mappings/create @@ -4,10 +4,7 @@ NAME SYNOPSIS gcloud beta run domain-mappings create --service=SERVICE (--domain=DOMAIN : --namespace=NAMESPACE) [--force-override] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create domain mappings. @@ -56,85 +53,9 @@ OPTIONAL FLAGS --force-override Map this domain even if it is already mapped to another service. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/domain-mappings/delete b/gcloud/beta/run/domain-mappings/delete index 6f439b485..ec9dbecae 100644 --- a/gcloud/beta/run/domain-mappings/delete +++ b/gcloud/beta/run/domain-mappings/delete @@ -4,10 +4,7 @@ NAME SYNOPSIS gcloud beta run domain-mappings delete (--domain=DOMAIN : --namespace=NAMESPACE) [--[no-]async] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Delete domain mappings. @@ -51,89 +48,12 @@ REQUIRED FLAGS OPTIONAL FLAGS --[no-]async Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async for Cloud Run (fully managed) and - --async for Cloud Run for Anthos. Use --async to enable and --no-async + complete. Defaults to --no-async. Use --async to enable and --no-async to disable. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/domain-mappings/describe b/gcloud/beta/run/domain-mappings/describe index e6f690a01..55888b45d 100644 --- a/gcloud/beta/run/domain-mappings/describe +++ b/gcloud/beta/run/domain-mappings/describe @@ -3,11 +3,8 @@ NAME SYNOPSIS gcloud beta run domain-mappings describe - (--domain=DOMAIN : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + (--domain=DOMAIN : --namespace=NAMESPACE) [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Describe domain mappings. @@ -49,85 +46,9 @@ REQUIRED FLAGS ▸ set the property core/project. OPTIONAL FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/domain-mappings/help b/gcloud/beta/run/domain-mappings/help index b4fceeda5..7db162784 100644 --- a/gcloud/beta/run/domain-mappings/help +++ b/gcloud/beta/run/domain-mappings/help @@ -3,11 +3,8 @@ NAME mappings SYNOPSIS - gcloud beta run domain-mappings COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud beta run domain-mappings COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This set of commands can be used to view and manage your service's @@ -19,85 +16,9 @@ EXAMPLES $ gcloud beta run domain-mappings list FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/run/domain-mappings/list b/gcloud/beta/run/domain-mappings/list index d551e4ff4..73822acf2 100644 --- a/gcloud/beta/run/domain-mappings/list +++ b/gcloud/beta/run/domain-mappings/list @@ -3,11 +3,8 @@ NAME SYNOPSIS gcloud beta run domain-mappings list [--namespace=NAMESPACE] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -19,104 +16,23 @@ EXAMPLES $ gcloud beta run domain-mappings list FLAGS - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: + Namespace resource - Namespace to list domain mappings in. This represents + a Cloud resource. - Namespace resource - Namespace to list domain mappings in. This - represents a Cloud resource. + --namespace=NAMESPACE + ID of the namespace or fully qualified identifier for the namespace. - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. + To set the namespace attribute: + ▸ provide the argument --namespace on the command line; + ▸ set the property run/namespace; + ▸ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▸ provide the argument project on the command line; + ▸ set the property core/project. - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/run/jobs/create b/gcloud/beta/run/jobs/create index e35adb4ed..657658dac 100644 --- a/gcloud/beta/run/jobs/create +++ b/gcloud/beta/run/jobs/create @@ -86,9 +86,8 @@ OPTIONAL FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m + Cloud Run supports values fractional values below 1, 1, 2, 4, and 8. + Some CPU values requires a minimum Memory --memory value. --key=KEY CMEK key reference to encrypt the container with. @@ -113,10 +112,9 @@ OPTIONAL FLAGS property [run/region]. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. This is the email address - of an IAM service account. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] You can specify a name of a Cloud SQL instance if it's in the same diff --git a/gcloud/beta/run/jobs/deploy b/gcloud/beta/run/jobs/deploy index db469ccba..8be9428f4 100644 --- a/gcloud/beta/run/jobs/deploy +++ b/gcloud/beta/run/jobs/deploy @@ -85,9 +85,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m + Cloud Run supports values fractional values below 1, 1, 2, 4, and 8. + Some CPU values requires a minimum Memory --memory value. --key=KEY CMEK key reference to encrypt the container with. @@ -112,10 +111,9 @@ FLAGS property [run/region]. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. This is the email address - of an IAM service account. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] You can specify a name of a Cloud SQL instance if it's in the same diff --git a/gcloud/beta/run/jobs/update b/gcloud/beta/run/jobs/update index 6fbdd4a57..6433718b4 100644 --- a/gcloud/beta/run/jobs/update +++ b/gcloud/beta/run/jobs/update @@ -86,9 +86,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m + Cloud Run supports values fractional values below 1, 1, 2, 4, and 8. + Some CPU values requires a minimum Memory --memory value. --image=IMAGE Name of the container image to deploy (e.g. @@ -114,10 +113,9 @@ FLAGS property [run/region]. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. This is the email address - of an IAM service account. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. --task-timeout=TASK_TIMEOUT Set the maximum time (deadline) a job task attempt can run for. In the diff --git a/gcloud/beta/run/multi-region-services/delete b/gcloud/beta/run/multi-region-services/delete index e042d122c..14470c254 100644 --- a/gcloud/beta/run/multi-region-services/delete +++ b/gcloud/beta/run/multi-region-services/delete @@ -4,11 +4,8 @@ NAME SYNOPSIS gcloud beta run multi-region-services delete - (SERVICE : --namespace=NAMESPACE) [--[no-]async] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + (SERVICE : --namespace=NAMESPACE) [--[no-]async] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Deletes a multi-region service. @@ -50,89 +47,12 @@ POSITIONAL ARGUMENTS FLAGS --[no-]async Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async for Cloud Run (fully managed) and - --async for Cloud Run for Anthos. Use --async to enable and --no-async + complete. Defaults to --no-async. Use --async to enable and --no-async to disable. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/multi-region-services/describe b/gcloud/beta/run/multi-region-services/describe index 9067380b1..a5493ba02 100644 --- a/gcloud/beta/run/multi-region-services/describe +++ b/gcloud/beta/run/multi-region-services/describe @@ -4,11 +4,8 @@ NAME SYNOPSIS gcloud beta run multi-region-services describe - (SERVICE : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + (SERVICE : --namespace=NAMESPACE) [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Command to describe a multi-region service. @@ -59,85 +56,9 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/multi-region-services/help b/gcloud/beta/run/multi-region-services/help index eb077b0ba..d44c43895 100644 --- a/gcloud/beta/run/multi-region-services/help +++ b/gcloud/beta/run/multi-region-services/help @@ -3,11 +3,8 @@ NAME services SYNOPSIS - gcloud beta run multi-region-services COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud beta run multi-region-services COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) The gcloud run multi-region-services command group lets you deploy @@ -23,85 +20,9 @@ EXAMPLES $ gcloud run deploy --help FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/run/multi-region-services/list b/gcloud/beta/run/multi-region-services/list index 6adb101d7..d4df2d3c9 100644 --- a/gcloud/beta/run/multi-region-services/list +++ b/gcloud/beta/run/multi-region-services/list @@ -3,13 +3,9 @@ NAME services SYNOPSIS - gcloud beta run multi-region-services list [--namespace=NAMESPACE] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud beta run multi-region-services list [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) List available multi-region services. @@ -20,104 +16,9 @@ EXAMPLES $ gcloud beta run multi-region-services list FLAGS - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to list services in. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/run/multi-region-services/replace b/gcloud/beta/run/multi-region-services/replace index 8ba050cd4..768b92e06 100644 --- a/gcloud/beta/run/multi-region-services/replace +++ b/gcloud/beta/run/multi-region-services/replace @@ -4,10 +4,7 @@ NAME SYNOPSIS gcloud beta run multi-region-services replace FILE [--async] [--dry-run] - [--namespace=NAMESPACE] [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates or replaces a service from a YAML service specification. @@ -31,104 +28,9 @@ FLAGS If set to true, only validates the configuration. The configuration will not be applied. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to replace service. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/multi-region-services/update b/gcloud/beta/run/multi-region-services/update index 8c173cc5c..7f9dde501 100644 --- a/gcloud/beta/run/multi-region-services/update +++ b/gcloud/beta/run/multi-region-services/update @@ -5,12 +5,31 @@ NAME SYNOPSIS gcloud beta run multi-region-services update - [[SERVICE] --namespace=NAMESPACE] [--async] [--concurrency=CONCURRENCY] - [--container=CONTAINER] [--ingress=INGRESS; default="all"] - [--max-instances=MAX_INSTANCES] [--min-instances=MIN_INSTANCES] - [--platform=PLATFORM; default="managed"] - [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] - [--no-traffic] + [[SERVICE] --namespace=NAMESPACE] [--async] + [--breakglass=JUSTIFICATION] [--clear-vpc-connector] + [--concurrency=CONCURRENCY] [--container=CONTAINER] [--[no-]cpu-boost] + [--[no-]cpu-throttling] [--[no-]default-url] + [--[no-]deploy-health-check] + [--execution-environment=EXECUTION_ENVIRONMENT] [--gpu-type=GPU_TYPE] + [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] + [--max-instances=MAX_INSTANCES] [--mesh=MESH] + [--min-instances=MIN_INSTANCES] [--region=REGION] + [--remove-containers=[CONTAINER,...]] + [--revision-suffix=REVISION_SUFFIX] [--service-account=SERVICE_ACCOUNT] + [--service-min-instances=SERVICE_MIN_INSTANCES] + [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] + [--no-traffic] [--vpc-connector=VPC_CONNECTOR] + [--vpc-egress=VPC_EGRESS] + [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --clear-cloudsql-instances + | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--add-custom-audiences=[CUSTOM-AUDIENCES,...] + | --clear-custom-audiences + | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + | --set-custom-audiences=[CUSTOM-AUDIENCES,...]] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE --memory=MEMORY @@ -20,40 +39,21 @@ SYNOPSIS --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] - [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost - --[no-]cpu-throttling --[no-]default-url --[no-]deploy-health-check - --description=DESCRIPTION - --execution-environment=EXECUTION_ENVIRONMENT - --[no-]invoker-iam-check --max-surge=MAX_SURGE - --max-unavailable=MAX_UNAVAILABLE --mesh=MESH - --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX - --scaling=SCALING --service-max-instances=SERVICE_MAX_INSTANCES - --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity - --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --clear-cloudsql-instances - | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - | --clear-custom-audiences - | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --add-volume=[KEY=VALUE,...] --clear-volumes - --remove-volume=[VOLUME,...] --binary-authorization=POLICY - | --clear-binary-authorization --clear-encryption-key-shutdown-hours - | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - --clear-key | --key=KEY --clear-network - | --network=NETWORK --subnet=SUBNET --clear-network-tags - | --network-tags=[TAG,...] --clear-post-key-revocation-action-type - | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [--binary-authorization=POLICY | --clear-binary-authorization] + [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] + | --remove-config-maps=[KEY,...] + --update-config-maps=[KEY=VALUE,...]] + [--clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] + [--clear-key | --key=KEY] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] - [--connectivity=CONNECTIVITY --clear-config-maps - | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAG,...]] + [--clear-post-key-revocation-action-type + | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update environment variables, add/remove regions, and other @@ -97,6 +97,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. + + --clear-vpc-connector + Remove the VPC connector for this resource. + --concurrency=CONCURRENCY Set the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified or provide the special value @@ -106,64 +116,109 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + --[no-]cpu-boost + Whether to allocate extra CPU to containers on startup to reduce the + perceived latency of a cold start request. Enabled by default when + unspecified on new services. Use --cpu-boost to enable and + --no-cpu-boost to disable. + + --[no-]cpu-throttling + Whether to throttle the CPU when the container is not actively serving + requests. Use --cpu-throttling to enable and --no-cpu-throttling to + disable. + + --[no-]default-url + Toggles the default url for a run service. This is enabled by default + if not specified. Use --default-url to enable and --no-default-url to + disable. + + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + + --execution-environment=EXECUTION_ENVIRONMENT + Selects the execution environment where the application will run. + EXECUTION_ENVIRONMENT must be one of: + + gen1 + Run the application in a first generation execution environment. + gen2 + Run the application in a second generation execution environment. + + --gpu-type=GPU_TYPE + The GPU type to use. + --ingress=INGRESS; default="all" Set the ingress traffic sources allowed to call the service. For Cloud - Run (fully managed) the --[no-]allow-unauthenticated flag separately - controls the identities allowed to call the service. INGRESS must be - one of: + Run the --[no-]allow-unauthenticated flag separately controls the + identities allowed to call the service. INGRESS must be one of: all Inbound requests from all sources are allowed. internal - For Cloud Run (fully managed), only inbound requests from VPC - networks in the same project or VPC Service Controls perimeter, as - well as Pub/Sub subscriptions and Eventarc events in the same - project or VPC Service Controls perimeter are allowed. All other - requests are rejected. See - https://cloud.google.com/run/docs/securing/ingress for full details - on the definition of internal traffic for Cloud Run (fully - managed). For Cloud Run for Anthos, only inbound requests from the - same cluster are allowed. + For Cloud Run, only inbound requests from VPC networks in the same + project or VPC Service Controls perimeter, as well as Pub/Sub + subscriptions and Eventarc events in the same project or VPC + Service Controls perimeter are allowed. All other requests are + rejected. See https://cloud.google.com/run/docs/securing/ingress + for full details on the definition of internal traffic for Cloud + Run. internal-and-cloud-load-balancing - Only supported for Cloud Run (fully managed). Only inbound requests - from Google Cloud Load Balancing or a traffic source allowed by the - internal option are allowed. + Only inbound requests from Google Cloud Load Balancing or a traffic + source allowed by the internal option are allowed. + + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. --max-instances=MAX_INSTANCES The maximum number of container instances of the Service to run. Use 'default' to unset the limit and use the platform default. + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. Mesh + resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + --min-instances=MIN_INSTANCES The minimum number of container instances for this Revision of the Service to run or 'default' to remove any minimum. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --remove-containers=[CONTAINER,...] + List of containers to remove. + + --revision-suffix=REVISION_SUFFIX + Specify the suffix of the revision name. Revision names always start + with the service name automatically. For example, specifying + [--revision-suffix=v1] for a service named 'helloworld', would lead to + a revision named 'helloworld-v1'. Set empty string to clear the suffix + and resume server-assigned naming. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. For the managed platform, - this is the email address of an IAM service account. For the - Kubernetes-based platforms (gke, kubernetes), this is the name of a - Kubernetes service account in the same namespace as the service. If not - provided, the revision will use the default service account of the - project, or default Kubernetes namespace service account respectively. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. + + --service-min-instances=SERVICE_MIN_INSTANCES + The minimum number of container instances for this Service to run or + 'default' to remove any minimum. These instances will be divided among + all Revisions receiving a percentage of traffic. + + --[no-]session-affinity + Whether to enable session affinity for connections to the service. Use + --session-affinity to enable and --no-session-affinity to disable. --tag=TAG Traffic tag to assign to the newly created revision. @@ -185,6 +240,84 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. + --vpc-connector=VPC_CONNECTOR + Set a VPC connector for this resource. + + --vpc-egress=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 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 Direct VPC egress or the VPC + connector. + private-ranges-only + 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 + region as your Cloud Run service; otherwise specify + :: for the instance. + + At most one of these can be specified: + + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Append the given values to the current Cloud SQL instances. + + --clear-cloudsql-instances + Empty the current Cloud SQL instances. + + --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Remove the given values from the current Cloud SQL instances. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Completely replace the current Cloud SQL instances with the given + values. + + These flags modify the custom audiences that can be used in the audience + field of ID token for authenticated requests. + + At most one of these can be specified: + + --add-custom-audiences=[CUSTOM-AUDIENCES,...] + Append the given values to the current custom audiences. + + --clear-custom-audiences + Empty the current custom audiences. + + --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + Remove the given values from the current custom audiences. + + --set-custom-audiences=[CUSTOM-AUDIENCES,...] + Completely replace the current custom audiences with the given + values. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + Container Flags If the --container or --remove-containers flag is specified the following @@ -214,19 +347,15 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/hello:latest). --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. @@ -301,263 +430,62 @@ FLAGS --update-secrets=[KEY=VALUE,...] List of key-value pairs to set as secrets. - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + At most one of these can be specified: - --breakglass=JUSTIFICATION - Justification to bypass Binary Authorization policy constraints and - allow the operation. See - https://cloud.google.com/binary-authorization/docs/using-breakglass - for more information. Next update or deploy command will - automatically clear existing breakglass justification. + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". - --clear-vpc-connector - Remove the VPC connector for this resource. + --clear-binary-authorization + Remove any previously set Binary Authorization policy. - --[no-]cpu-boost - Whether to allocate extra CPU to containers on startup to reduce the - perceived latency of a cold start request. Enabled by default when - unspecified on new services. Use --cpu-boost to enable and - --no-cpu-boost to disable. + Specify config map to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. The values associated with each of + these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may + omit the key within the config map to specify a mount of all keys within + the config map. For example: + '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will + create a volume with config map 'myconfig' and mount that volume at + '/my/path'. Because no config map key was specified, all keys in + 'myconfig' will be included. An environment variable named ENV will also + be created whose value is the value of 'key.json' in 'otherconfig. Not + supported on the fully managed version of Cloud Run. - --[no-]cpu-throttling - Whether to throttle the CPU when the container is not actively - serving requests. Use --cpu-throttling to enable and - --no-cpu-throttling to disable. + At most one of these can be specified: - --[no-]default-url - Toggles the default url for a run service. This is enabled by default - if not specified. Use --default-url to enable and --no-default-url to - disable. + --clear-config-maps + Remove all config-maps. - --[no-]deploy-health-check - Schedules a single instance of the Revision and waits for it to pass - its startup probe for the deployment to succeed. If disabled, the - startup probe runs only when the revision is first started via - invocation or by setting min-instances. This check is enabled by - default when unspecified. Use --deploy-health-check to enable and - --no-deploy-health-check to disable. + --set-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. All existing + config-maps will be removed first. - --description=DESCRIPTION - Provides an optional, human-readable description of the service. + Only --update-config-maps and --remove-config-maps can be used together. + If both are specified, --remove-config-maps will be applied first. - --execution-environment=EXECUTION_ENVIRONMENT - Selects the execution environment where the application will run. - EXECUTION_ENVIRONMENT must be one of: + --remove-config-maps=[KEY,...] + List of config-maps to be removed. - gen1 - Run the application in a first generation execution environment. - gen2 - Run the application in a second generation execution environment. + --update-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. - --[no-]invoker-iam-check - Optionally disable invoker IAM checks. This feature is available by - invitation only. More info at - https://cloud.google.com/run/docs/securing/managing-access#invoker_check. - Use --invoker-iam-check to enable and --no-invoker-iam-check to - disable. + At most one of these can be specified: - --max-surge=MAX_SURGE - A maximum percentage of instances that will be moved in each step of - traffic split changes. Use "default" to unset the limit and use the - platform default. + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. - --max-unavailable=MAX_UNAVAILABLE - A maximum percentage of instances that may be unavailable during - traffic split changes. Use "default" to unset the limit and use the - platform default. + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server after + CMEK key revocation is detected. - --mesh=MESH - Enables Cloud Service Mesh using the specified mesh resource name. - Mesh resource name must be in the format of - projects/PROJECT/locations/global/meshes/MESH_NAME. + At most one of these can be specified: - --remove-containers=[CONTAINER,...] - List of containers to remove. + --clear-key + Remove any previously set CMEK key reference. - --revision-suffix=REVISION_SUFFIX - Specify the suffix of the revision name. Revision names always start - with the service name automatically. For example, specifying - [--revision-suffix=v1] for a service named 'helloworld', would lead - to a revision named 'helloworld-v1'. Set empty string to clear the - suffix and resume server-assigned naming. - - --scaling=SCALING - The scaling mode to use for this resource. SCALING must be one of: - - automatic - The number of instances is scaled automatically based on the - usage metrics. - manual - The number of instances is fixed to a provided config value. - - --service-max-instances=SERVICE_MAX_INSTANCES - The maximum number of container instances for this Service to run. - This instance limit will be divided among all Revisions receiving a - percentage of traffic. Once service-max-instances is enabled for a - service, it cannot be disabled. - - --service-min-instances=SERVICE_MIN_INSTANCES - The minimum number of container instances for this Service to run or - 'default' to remove any minimum. These instances will be divided - among all Revisions receiving a percentage of traffic. - - --[no-]session-affinity - Whether to enable session affinity for connections to the service. - Use --session-affinity to enable and --no-session-affinity to - disable. - - --vpc-connector=VPC_CONNECTOR - Set a VPC connector for this resource. - - --vpc-egress=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 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 Direct VPC egress or the VPC - connector. - private-ranges-only - 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 region as your Cloud Run service; otherwise specify - :: for the instance. - - At most one of these can be specified: - - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Append the given values to the current Cloud SQL instances. - - --clear-cloudsql-instances - Empty the current Cloud SQL instances. - - --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Remove the given values from the current Cloud SQL instances. - - --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Completely replace the current Cloud SQL instances with the given - values. - - These flags modify the custom audiences that can be used in the audience - field of ID token for authenticated requests. - - At most one of these can be specified: - - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - Append the given values to the current custom audiences. - - --clear-custom-audiences - Empty the current custom audiences. - - --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - Remove the given values from the current custom audiences. - - --set-custom-audiences=[CUSTOM-AUDIENCES,...] - Completely replace the current custom audiences with the given - values. - - --add-volume=[KEY=VALUE,...] - Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: - - --clear-volumes - Remove all existing volumes from the Cloud Run resource, including - volumes mounted as secrets - - --remove-volume=[VOLUME,...] - Removes volumes from the Cloud Run resource. - - At most one of these can be specified: - - --binary-authorization=POLICY - Binary Authorization policy to check against. This must be set to - "default". - - --clear-binary-authorization - Remove any previously set Binary Authorization policy. - - At most one of these can be specified: - - --clear-encryption-key-shutdown-hours - Remove any previously set CMEK key shutdown hours setting. - - --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - The number of hours to wait before an automatic shutdown server - after CMEK key revocation is detected. - - At most one of these can be specified: - - --clear-key - Remove any previously set CMEK key reference. - - --key=KEY - CMEK key reference to encrypt the container with. - - At most one of these can be specified: - - --clear-network - Disconnect this Cloud Run service from the VPC network it is - connected to. - - Direct VPC egress setting flags group. - - --network=NETWORK - The VPC network that the Cloud Run service will be able to send - traffic to. If --subnet is also specified, subnet must be a - subnetwork of the network specified by this --network flag. To - clear existing VPC network settings, use --clear-network. - - --subnet=SUBNET - The VPC subnetwork that the Cloud Run service will get IPs from. - The subnetwork must be /26 or larger. If --network is also - specified, subnet must be a subnetwork of the network specified - by the --network flag. If --network is not specified, network - will be looked up from this subnetwork. To clear existing VPC - network settings, use --clear-network. - - At most one of these can be specified: - - --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. - - --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. - - At most one of these can be specified: - - --clear-post-key-revocation-action-type - Remove any previously set post CMEK key revocation action type. - - --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE - Action type after CMEK key revocation. - POST_KEY_REVOCATION_ACTION_TYPE must be one of: - - prevent-new - No new instances will be started after CMEK key revocation. - shut-down - No new instances will be started and the existing instances - will be shut down after CMEK key revocation. + --key=KEY + CMEK key reference to encrypt the container with. At most one of these can be specified: @@ -590,119 +518,53 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: + At most one of these can be specified: - --connectivity=CONNECTIVITY - (DEPRECATED) Defaults to 'external'. If 'external', the service can - be invoked through the internet, in addition to through the cluster - network. + --clear-network + Disconnect this Cloud Run service from the VPC network it is + connected to. - The --connectivity flag is deprecated but will continue to be - supported. Prefer to use the --ingress flag instead. CONNECTIVITY - must be one of: + Direct VPC egress setting flags group. - external - Visible from outside the cluster. - internal - Visible only within the cluster. + --network=NETWORK + The VPC network that the Cloud Run service will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. + --subnet=SUBNET + The VPC subnetwork that the Cloud Run service will get IPs from. + The subnetwork must be /26 or larger. If --network is also + specified, subnet must be a subnetwork of the network specified by + the --network flag. If --network is not specified, network will be + looked up from this subnetwork. To clear existing VPC network + settings, use --clear-network. - At most one of these can be specified: + At most one of these can be specified: - --clear-config-maps - Remove all config-maps. + --clear-network-tags + Clears all existing Compute Engine tags from the Cloud Run + service. - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used - together. If both are specified, --remove-config-maps will be applied - first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - - Arguments to locate resources, depending on the platform used. + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. To clear existing tags, use + --clear-network-tags. At most one of these can be specified: - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. + --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE + Action type after CMEK key revocation. + POST_KEY_REVOCATION_ACTION_TYPE must be one of: - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▸ set the property run/cluster with a fully specified name; - ▸ specify the cluster from a list of available clusters with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the - cluster. - - To set the cluster attribute: - ▫ provide the argument --cluster on the command line; - ▫ set the property run/cluster; - ▫ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ▫ provide the argument --cluster on the command line with a - fully specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --cluster-location on the command line; - ▫ set the property run/cluster_location; - ▫ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + prevent-new + No new instances will be started after CMEK key revocation. + shut-down + No new instances will be started and the existing instances will + be shut down after CMEK key revocation. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/regions/help b/gcloud/beta/run/regions/help index 4984add43..6b5f7b355 100644 --- a/gcloud/beta/run/regions/help +++ b/gcloud/beta/run/regions/help @@ -2,27 +2,11 @@ NAME gcloud beta run regions - view available Cloud Run (fully managed) regions SYNOPSIS - gcloud beta run regions COMMAND [--platform=PLATFORM; default="managed"] - [GCLOUD_WIDE_FLAG ...] + gcloud beta run regions COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) View available Cloud Run (fully managed) regions. -FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Not supported by this - command. - kubernetes - Use a Knative-compatible kubernetes cluster. Not supported by this - command. - GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/run/regions/list b/gcloud/beta/run/regions/list index ca8a354e4..25234dda2 100644 --- a/gcloud/beta/run/regions/list +++ b/gcloud/beta/run/regions/list @@ -3,9 +3,9 @@ NAME regions SYNOPSIS - gcloud beta run regions list [--platform=PLATFORM; default="managed"] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + gcloud beta run regions list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) List available Cloud Run (fully managed) regions. @@ -15,21 +15,6 @@ EXAMPLES $ gcloud beta run regions list -FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Not supported by this - command. - kubernetes - Use a Knative-compatible kubernetes cluster. Not supported by this - command. - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/run/revisions/delete b/gcloud/beta/run/revisions/delete index b34d4e51b..108401720 100644 --- a/gcloud/beta/run/revisions/delete +++ b/gcloud/beta/run/revisions/delete @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud beta run revisions delete (REVISION : --namespace=NAMESPACE) - [--[no-]async] [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--[no-]async] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Delete a revision. @@ -48,89 +45,12 @@ POSITIONAL ARGUMENTS FLAGS --[no-]async Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async for Cloud Run (fully managed) and - --async for Cloud Run for Anthos. Use --async to enable and --no-async + complete. Defaults to --no-async. Use --async to enable and --no-async to disable. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/revisions/describe b/gcloud/beta/run/revisions/describe index f47c56269..566f55df3 100644 --- a/gcloud/beta/run/revisions/describe +++ b/gcloud/beta/run/revisions/describe @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud beta run revisions describe (REVISION : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Obtain details about revisions. @@ -46,85 +43,9 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/revisions/help b/gcloud/beta/run/revisions/help index 552e63993..1c3d10aa2 100644 --- a/gcloud/beta/run/revisions/help +++ b/gcloud/beta/run/revisions/help @@ -2,11 +2,8 @@ NAME gcloud beta run revisions - view and manage your Cloud Run revisions SYNOPSIS - gcloud beta run revisions GROUP | COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud beta run revisions GROUP | COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This set of commands can be used to view and manage your existing @@ -18,85 +15,9 @@ EXAMPLES $ gcloud beta run revisions list FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/run/revisions/list b/gcloud/beta/run/revisions/list index b6d6ec3bb..8eceddf9f 100644 --- a/gcloud/beta/run/revisions/list +++ b/gcloud/beta/run/revisions/list @@ -2,13 +2,9 @@ NAME gcloud beta run revisions list - list available revisions SYNOPSIS - gcloud beta run revisions list [--namespace=NAMESPACE] - [--platform=PLATFORM; default="managed"] [--service=SERVICE] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud beta run revisions list [--region=REGION] [--service=SERVICE] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) List available revisions. @@ -19,108 +15,13 @@ EXAMPLES $ gcloud beta run revisions list --service=foo FLAGS - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to list revisions in. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. --service=SERVICE Limit matched revisions to the given service. - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/run/revisions/logs/help b/gcloud/beta/run/revisions/logs/help index 25ca04c4e..2b6fa5be4 100644 --- a/gcloud/beta/run/revisions/logs/help +++ b/gcloud/beta/run/revisions/logs/help @@ -2,95 +2,16 @@ NAME gcloud beta run revisions logs - read logs for Cloud Run revisions SYNOPSIS - gcloud beta run revisions logs COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud beta run revisions logs COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Read logs for Cloud Run revisions. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/run/revisions/logs/read b/gcloud/beta/run/revisions/logs/read index 9af20f297..aaf379824 100644 --- a/gcloud/beta/run/revisions/logs/read +++ b/gcloud/beta/run/revisions/logs/read @@ -4,11 +4,7 @@ NAME SYNOPSIS gcloud beta run revisions logs read REVISION [--freshness=FRESHNESS; default="1d"] [--log-filter=LOG_FILTER] - [--order=ORDER; default="desc"] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--limit=LIMIT] + [--order=ORDER; default="desc"] [--region=REGION] [--limit=LIMIT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -61,85 +57,9 @@ FLAGS Ordering of returned log entries based on timestamp field. ORDER must be one of: desc, asc. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --limit=LIMIT diff --git a/gcloud/beta/run/revisions/logs/tail b/gcloud/beta/run/revisions/logs/tail index 1802461ec..38aaf9a05 100644 --- a/gcloud/beta/run/revisions/logs/tail +++ b/gcloud/beta/run/revisions/logs/tail @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud beta run revisions logs tail REVISION [--log-filter=LOG_FILTER] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta run revisions logs tail tails log-entries for a @@ -36,85 +33,9 @@ FLAGS information about filters can be found at: https://cloud.google.com/logging/docs/view/logging-query-language - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/services/add-iam-policy-binding b/gcloud/beta/run/services/add-iam-policy-binding index cfba56d7b..3d7737339 100644 --- a/gcloud/beta/run/services/add-iam-policy-binding +++ b/gcloud/beta/run/services/add-iam-policy-binding @@ -4,11 +4,9 @@ NAME SYNOPSIS gcloud beta run services add-iam-policy-binding SERVICE --member=PRINCIPAL - --role=ROLE [--platform=PLATFORM; default="managed"] + --role=ROLE [--region=REGION] [--condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Add an IAM policy binding to the IAM policy of a Cloud Run service. @@ -74,22 +72,9 @@ REQUIRED FLAGS organizations/{ORGANIZATION_ID}/roles/logging.viewer. OPTIONAL FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. At most one of these can be specified: @@ -129,69 +114,6 @@ OPTIONAL FLAGS available fields, see the help for --condition. Use a full or relative path to a local file containing the value of condition. - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/run/services/delete b/gcloud/beta/run/services/delete index 4a52ba31f..17f07e45e 100644 --- a/gcloud/beta/run/services/delete +++ b/gcloud/beta/run/services/delete @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud beta run services delete (SERVICE : --namespace=NAMESPACE) - [--[no-]async] [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--[no-]async] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Delete a service. @@ -48,89 +45,12 @@ POSITIONAL ARGUMENTS FLAGS --[no-]async Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async for Cloud Run (fully managed) and - --async for Cloud Run for Anthos. Use --async to enable and --no-async + complete. Defaults to --no-async. Use --async to enable and --no-async to disable. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/services/describe b/gcloud/beta/run/services/describe index 925305951..0e46f6683 100644 --- a/gcloud/beta/run/services/describe +++ b/gcloud/beta/run/services/describe @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud beta run services describe (SERVICE : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Obtain details about a given service. @@ -55,85 +52,9 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/services/get-iam-policy b/gcloud/beta/run/services/get-iam-policy index 4e7d4bfe6..75d87a516 100644 --- a/gcloud/beta/run/services/get-iam-policy +++ b/gcloud/beta/run/services/get-iam-policy @@ -3,13 +3,9 @@ NAME Run service SYNOPSIS - gcloud beta run services get-iam-policy SERVICE - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + gcloud beta run services get-iam-policy SERVICE [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command gets the IAM policy for a service. If formatted as @@ -51,85 +47,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument service on the command line. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/run/services/help b/gcloud/beta/run/services/help index 84f274efe..b62f17219 100644 --- a/gcloud/beta/run/services/help +++ b/gcloud/beta/run/services/help @@ -2,11 +2,8 @@ NAME gcloud beta run services - view and manage your Cloud Run services SYNOPSIS - gcloud beta run services GROUP | COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud beta run services GROUP | COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This set of commands can be used to view and manage your existing @@ -20,85 +17,9 @@ EXAMPLES $ gcloud beta run services list FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/run/services/list b/gcloud/beta/run/services/list index 3908e1c98..cb11383a0 100644 --- a/gcloud/beta/run/services/list +++ b/gcloud/beta/run/services/list @@ -2,11 +2,7 @@ NAME gcloud beta run services list - list available services SYNOPSIS - gcloud beta run services list [--namespace=NAMESPACE] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] + gcloud beta run services list [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -19,104 +15,9 @@ EXAMPLES $ gcloud beta run services list FLAGS - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to list services in. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/run/services/logs/help b/gcloud/beta/run/services/logs/help index 61562ead1..ea4aee44e 100644 --- a/gcloud/beta/run/services/logs/help +++ b/gcloud/beta/run/services/logs/help @@ -2,95 +2,16 @@ NAME gcloud beta run services logs - read logs for Cloud Run services SYNOPSIS - gcloud beta run services logs COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud beta run services logs COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Read logs for Cloud Run services. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/run/services/logs/read b/gcloud/beta/run/services/logs/read index 142279dee..e8dcce508 100644 --- a/gcloud/beta/run/services/logs/read +++ b/gcloud/beta/run/services/logs/read @@ -4,11 +4,7 @@ NAME SYNOPSIS gcloud beta run services logs read SERVICE [--freshness=FRESHNESS; default="1d"] [--log-filter=LOG_FILTER] - [--order=ORDER; default="desc"] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--limit=LIMIT] + [--order=ORDER; default="desc"] [--region=REGION] [--limit=LIMIT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -61,85 +57,9 @@ FLAGS Ordering of returned log entries based on timestamp field. ORDER must be one of: desc, asc. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --limit=LIMIT diff --git a/gcloud/beta/run/services/logs/tail b/gcloud/beta/run/services/logs/tail index eed36a201..b816640ab 100644 --- a/gcloud/beta/run/services/logs/tail +++ b/gcloud/beta/run/services/logs/tail @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud beta run services logs tail SERVICE [--log-filter=LOG_FILTER] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta run services logs tail tails log-entries for a @@ -36,85 +33,9 @@ FLAGS information about filters can be found at: https://cloud.google.com/logging/docs/view/logging-query-language - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/services/proxy b/gcloud/beta/run/services/proxy index 54653a548..4978a289c 100644 --- a/gcloud/beta/run/services/proxy +++ b/gcloud/beta/run/services/proxy @@ -4,11 +4,8 @@ NAME SYNOPSIS gcloud beta run services proxy (SERVICE : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] [--port=PORT] [--tag=TAG] - [--token=TOKEN] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--port=PORT] [--region=REGION] [--tag=TAG] [--token=TOKEN] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Runs a server on localhost that proxies requests to the specified @@ -60,27 +57,14 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - --port=PORT Local port number to expose the proxied service. If not specified, it will be set to 8080. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + --tag=TAG Traffic tag of the service to expose via the proxy. If not specified, the default service URL will be proxied which may serve different @@ -94,69 +78,6 @@ FLAGS authenticated account will be used (e.g. gcloud auth print-identity-token). - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/run/services/remove-iam-policy-binding b/gcloud/beta/run/services/remove-iam-policy-binding index 9f53d899f..1e5e31f6b 100644 --- a/gcloud/beta/run/services/remove-iam-policy-binding +++ b/gcloud/beta/run/services/remove-iam-policy-binding @@ -4,12 +4,9 @@ NAME SYNOPSIS gcloud beta run services remove-iam-policy-binding SERVICE - --member=PRINCIPAL --role=ROLE [--platform=PLATFORM; default="managed"] + --member=PRINCIPAL --role=ROLE [--region=REGION] [--all | --condition=[KEY=VALUE,...] - | --condition-from-file=PATH_TO_FILE] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + | --condition-from-file=PATH_TO_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Remove an IAM policy binding from the IAM policy of a service. One @@ -76,22 +73,9 @@ REQUIRED FLAGS The role to remove the principal from. OPTIONAL FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. At most one of these can be specified: @@ -135,69 +119,6 @@ OPTIONAL FLAGS available fields, see the help for --condition. Use a full or relative path to a local file containing the value of condition. - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/run/services/replace b/gcloud/beta/run/services/replace index fc519c9c2..f944cf196 100644 --- a/gcloud/beta/run/services/replace +++ b/gcloud/beta/run/services/replace @@ -4,10 +4,7 @@ NAME SYNOPSIS gcloud beta run services replace FILE [--async] [--dry-run] - [--namespace=NAMESPACE] [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates or replaces a service from a YAML service specification. @@ -31,104 +28,9 @@ FLAGS If set to true, only validates the configuration. The configuration will not be applied. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to replace service. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/services/set-iam-policy b/gcloud/beta/run/services/set-iam-policy index b94c911e3..a43033d69 100644 --- a/gcloud/beta/run/services/set-iam-policy +++ b/gcloud/beta/run/services/set-iam-policy @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud beta run services set-iam-policy SERVICE POLICY_FILE - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command replaces the existing IAM policy for a service, given a @@ -61,85 +58,9 @@ POSITIONAL ARGUMENTS (https://cloud.google.com/iam/reference/rest/v1/Policy). FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 56a586d64..140647a59 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -4,12 +4,30 @@ NAME SYNOPSIS gcloud beta run services update [[SERVICE] --namespace=NAMESPACE] [--async] - [--concurrency=CONCURRENCY] [--container=CONTAINER] - [--ingress=INGRESS; default="all"] [--max-instances=MAX_INSTANCES] - [--min-instances=MIN_INSTANCES] - [--platform=PLATFORM; default="managed"] - [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] - [--no-traffic] + [--breakglass=JUSTIFICATION] [--clear-vpc-connector] + [--concurrency=CONCURRENCY] [--container=CONTAINER] [--[no-]cpu-boost] + [--[no-]cpu-throttling] [--[no-]default-url] + [--[no-]deploy-health-check] + [--execution-environment=EXECUTION_ENVIRONMENT] [--gpu-type=GPU_TYPE] + [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] + [--max-instances=MAX_INSTANCES] [--mesh=MESH] + [--min-instances=MIN_INSTANCES] [--region=REGION] + [--remove-containers=[CONTAINER,...]] + [--revision-suffix=REVISION_SUFFIX] [--service-account=SERVICE_ACCOUNT] + [--service-min-instances=SERVICE_MIN_INSTANCES] + [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] + [--no-traffic] [--vpc-connector=VPC_CONNECTOR] + [--vpc-egress=VPC_EGRESS] + [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --clear-cloudsql-instances + | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--add-custom-audiences=[CUSTOM-AUDIENCES,...] + | --clear-custom-audiences + | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + | --set-custom-audiences=[CUSTOM-AUDIENCES,...]] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --image=IMAGE @@ -19,37 +37,21 @@ SYNOPSIS --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] - [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost - --[no-]cpu-throttling --[no-]default-url --[no-]deploy-health-check - --execution-environment=EXECUTION_ENVIRONMENT --gpu-type=GPU_TYPE - --[no-]invoker-iam-check --mesh=MESH - --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX - --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity - --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --clear-cloudsql-instances - | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - | --clear-custom-audiences - | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --add-volume=[KEY=VALUE,...] --clear-volumes - --remove-volume=[VOLUME,...] --binary-authorization=POLICY - | --clear-binary-authorization --clear-encryption-key-shutdown-hours - | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - --clear-key | --key=KEY --clear-network - | --network=NETWORK --subnet=SUBNET --clear-network-tags - | --network-tags=[TAG,...] --clear-post-key-revocation-action-type - | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [--binary-authorization=POLICY | --clear-binary-authorization] + [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] + | --remove-config-maps=[KEY,...] + --update-config-maps=[KEY=VALUE,...]] + [--clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] + [--clear-key | --key=KEY] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] - [--connectivity=CONNECTIVITY --clear-config-maps - | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAG,...]] + [--clear-post-key-revocation-action-type + | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update Cloud Run environment variables and other configuration @@ -93,6 +95,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. + + --clear-vpc-connector + Remove the VPC connector for this resource. + --concurrency=CONCURRENCY Set the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified or provide the special value @@ -102,64 +114,109 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + --[no-]cpu-boost + Whether to allocate extra CPU to containers on startup to reduce the + perceived latency of a cold start request. Enabled by default when + unspecified on new services. Use --cpu-boost to enable and + --no-cpu-boost to disable. + + --[no-]cpu-throttling + Whether to throttle the CPU when the container is not actively serving + requests. Use --cpu-throttling to enable and --no-cpu-throttling to + disable. + + --[no-]default-url + Toggles the default url for a run service. This is enabled by default + if not specified. Use --default-url to enable and --no-default-url to + disable. + + --[no-]deploy-health-check + Schedules a single instance of the Revision and waits for it to pass + its startup probe for the deployment to succeed. If disabled, the + startup probe runs only when the revision is first started via + invocation or by setting min-instances. This check is enabled by + default when unspecified. Use --deploy-health-check to enable and + --no-deploy-health-check to disable. + + --execution-environment=EXECUTION_ENVIRONMENT + Selects the execution environment where the application will run. + EXECUTION_ENVIRONMENT must be one of: + + gen1 + Run the application in a first generation execution environment. + gen2 + Run the application in a second generation execution environment. + + --gpu-type=GPU_TYPE + The GPU type to use. + --ingress=INGRESS; default="all" Set the ingress traffic sources allowed to call the service. For Cloud - Run (fully managed) the --[no-]allow-unauthenticated flag separately - controls the identities allowed to call the service. INGRESS must be - one of: + Run the --[no-]allow-unauthenticated flag separately controls the + identities allowed to call the service. INGRESS must be one of: all Inbound requests from all sources are allowed. internal - For Cloud Run (fully managed), only inbound requests from VPC - networks in the same project or VPC Service Controls perimeter, as - well as Pub/Sub subscriptions and Eventarc events in the same - project or VPC Service Controls perimeter are allowed. All other - requests are rejected. See - https://cloud.google.com/run/docs/securing/ingress for full details - on the definition of internal traffic for Cloud Run (fully - managed). For Cloud Run for Anthos, only inbound requests from the - same cluster are allowed. + For Cloud Run, only inbound requests from VPC networks in the same + project or VPC Service Controls perimeter, as well as Pub/Sub + subscriptions and Eventarc events in the same project or VPC + Service Controls perimeter are allowed. All other requests are + rejected. See https://cloud.google.com/run/docs/securing/ingress + for full details on the definition of internal traffic for Cloud + Run. internal-and-cloud-load-balancing - Only supported for Cloud Run (fully managed). Only inbound requests - from Google Cloud Load Balancing or a traffic source allowed by the - internal option are allowed. + Only inbound requests from Google Cloud Load Balancing or a traffic + source allowed by the internal option are allowed. + + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. --max-instances=MAX_INSTANCES The maximum number of container instances of the Service to run. Use 'default' to unset the limit and use the platform default. + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. Mesh + resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + --min-instances=MIN_INSTANCES The minimum number of container instances for this Revision of the Service to run or 'default' to remove any minimum. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --remove-containers=[CONTAINER,...] + List of containers to remove. + + --revision-suffix=REVISION_SUFFIX + Specify the suffix of the revision name. Revision names always start + with the service name automatically. For example, specifying + [--revision-suffix=v1] for a service named 'helloworld', would lead to + a revision named 'helloworld-v1'. Set empty string to clear the suffix + and resume server-assigned naming. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. For the managed platform, - this is the email address of an IAM service account. For the - Kubernetes-based platforms (gke, kubernetes), this is the name of a - Kubernetes service account in the same namespace as the service. If not - provided, the revision will use the default service account of the - project, or default Kubernetes namespace service account respectively. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. + + --service-min-instances=SERVICE_MIN_INSTANCES + The minimum number of container instances for this Service to run or + 'default' to remove any minimum. These instances will be divided among + all Revisions receiving a percentage of traffic. + + --[no-]session-affinity + Whether to enable session affinity for connections to the service. Use + --session-affinity to enable and --no-session-affinity to disable. --tag=TAG Traffic tag to assign to the newly created revision. @@ -181,6 +238,109 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. + --vpc-connector=VPC_CONNECTOR + Set a VPC connector for this resource. + + --vpc-egress=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 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 Direct VPC egress or the VPC + connector. + private-ranges-only + 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 + region as your Cloud Run service; otherwise specify + :: for the instance. + + At most one of these can be specified: + + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Append the given values to the current Cloud SQL instances. + + --clear-cloudsql-instances + Empty the current Cloud SQL instances. + + --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Remove the given values from the current Cloud SQL instances. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Completely replace the current Cloud SQL instances with the given + values. + + These flags modify the custom audiences that can be used in the audience + field of ID token for authenticated requests. + + At most one of these can be specified: + + --add-custom-audiences=[CUSTOM-AUDIENCES,...] + Append the given values to the current custom audiences. + + --clear-custom-audiences + Empty the current custom audiences. + + --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + Remove the given values from the current custom audiences. + + --set-custom-audiences=[CUSTOM-AUDIENCES,...] + Completely replace the current custom audiences with the given + values. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + in-memory: An ephemeral volume that stores data in the instance's + memory. With this type of volume, data is not shared between instances + and all data will be lost when the instance it is on is terminated. + Additional keys: + ◆ size-limit: (optional) A quantity representing the maximum amount + of memory allocated to this volume, such as "512Mi" or "3G". Data + stored in an in-memory volume consumes the memory allocation of the + container that wrote the data. If size-limit is not specified, the + maximum size will be half the total memory limit of all containers. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + Container Flags If the --container or --remove-containers flag is specified the following @@ -210,12 +370,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. @@ -226,7 +382,7 @@ FLAGS --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/hello:latest). --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. @@ -301,263 +457,62 @@ FLAGS --update-secrets=[KEY=VALUE,...] List of key-value pairs to set as secrets. - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + At most one of these can be specified: - --breakglass=JUSTIFICATION - Justification to bypass Binary Authorization policy constraints and - allow the operation. See - https://cloud.google.com/binary-authorization/docs/using-breakglass - for more information. Next update or deploy command will - automatically clear existing breakglass justification. + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". - --clear-vpc-connector - Remove the VPC connector for this resource. + --clear-binary-authorization + Remove any previously set Binary Authorization policy. - --[no-]cpu-boost - Whether to allocate extra CPU to containers on startup to reduce the - perceived latency of a cold start request. Enabled by default when - unspecified on new services. Use --cpu-boost to enable and - --no-cpu-boost to disable. + Specify config map to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. The values associated with each of + these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may + omit the key within the config map to specify a mount of all keys within + the config map. For example: + '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will + create a volume with config map 'myconfig' and mount that volume at + '/my/path'. Because no config map key was specified, all keys in + 'myconfig' will be included. An environment variable named ENV will also + be created whose value is the value of 'key.json' in 'otherconfig. Not + supported on the fully managed version of Cloud Run. - --[no-]cpu-throttling - Whether to throttle the CPU when the container is not actively - serving requests. Use --cpu-throttling to enable and - --no-cpu-throttling to disable. + At most one of these can be specified: - --[no-]default-url - Toggles the default url for a run service. This is enabled by default - if not specified. Use --default-url to enable and --no-default-url to - disable. + --clear-config-maps + Remove all config-maps. - --[no-]deploy-health-check - Schedules a single instance of the Revision and waits for it to pass - its startup probe for the deployment to succeed. If disabled, the - startup probe runs only when the revision is first started via - invocation or by setting min-instances. This check is enabled by - default when unspecified. Use --deploy-health-check to enable and - --no-deploy-health-check to disable. + --set-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. All existing + config-maps will be removed first. - --execution-environment=EXECUTION_ENVIRONMENT - Selects the execution environment where the application will run. - EXECUTION_ENVIRONMENT must be one of: + Only --update-config-maps and --remove-config-maps can be used together. + If both are specified, --remove-config-maps will be applied first. - gen1 - Run the application in a first generation execution environment. - gen2 - Run the application in a second generation execution environment. + --remove-config-maps=[KEY,...] + List of config-maps to be removed. - --gpu-type=GPU_TYPE - The GPU type to use. + --update-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. - --[no-]invoker-iam-check - Optionally disable invoker IAM checks. This feature is available by - invitation only. More info at - https://cloud.google.com/run/docs/securing/managing-access#invoker_check. - Use --invoker-iam-check to enable and --no-invoker-iam-check to - disable. + At most one of these can be specified: - --mesh=MESH - Enables Cloud Service Mesh using the specified mesh resource name. - Mesh resource name must be in the format of - projects/PROJECT/locations/global/meshes/MESH_NAME. + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. - --remove-containers=[CONTAINER,...] - List of containers to remove. + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server after + CMEK key revocation is detected. - --revision-suffix=REVISION_SUFFIX - Specify the suffix of the revision name. Revision names always start - with the service name automatically. For example, specifying - [--revision-suffix=v1] for a service named 'helloworld', would lead - to a revision named 'helloworld-v1'. Set empty string to clear the - suffix and resume server-assigned naming. + At most one of these can be specified: - --service-min-instances=SERVICE_MIN_INSTANCES - The minimum number of container instances for this Service to run or - 'default' to remove any minimum. These instances will be divided - among all Revisions receiving a percentage of traffic. + --clear-key + Remove any previously set CMEK key reference. - --[no-]session-affinity - Whether to enable session affinity for connections to the service. - Use --session-affinity to enable and --no-session-affinity to - disable. - - --vpc-connector=VPC_CONNECTOR - Set a VPC connector for this resource. - - --vpc-egress=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 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 Direct VPC egress or the VPC - connector. - private-ranges-only - 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 region as your Cloud Run service; otherwise specify - :: for the instance. - - At most one of these can be specified: - - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Append the given values to the current Cloud SQL instances. - - --clear-cloudsql-instances - Empty the current Cloud SQL instances. - - --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Remove the given values from the current Cloud SQL instances. - - --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Completely replace the current Cloud SQL instances with the given - values. - - These flags modify the custom audiences that can be used in the audience - field of ID token for authenticated requests. - - At most one of these can be specified: - - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - Append the given values to the current custom audiences. - - --clear-custom-audiences - Empty the current custom audiences. - - --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - Remove the given values from the current custom audiences. - - --set-custom-audiences=[CUSTOM-AUDIENCES,...] - Completely replace the current custom audiences with the given - values. - - --add-volume=[KEY=VALUE,...] - Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: - - cloud-storage: A volume representing a Cloud Storage bucket. This - volume type is mounted using Cloud Storage FUSE. See - https://cloud.google.com/storage/docs/gcs-fuse for the details and - limitations of this filesystem. Additional keys: - ◆ bucket: (required) the name of the bucket to use as the source of - this volume - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - - in-memory: An ephemeral volume that stores data in the instance's memory. - With this type of volume, data is not shared between instances and all - data will be lost when the instance it is on is terminated. Additional - keys: - ◆ size-limit: (optional) A quantity representing the maximum amount of - memory allocated to this volume, such as "512Mi" or "3G". Data stored - in an in-memory volume consumes the memory allocation of the container - that wrote the data. If size-limit is not specified, the maximum size - will be half the total memory limit of all containers. - - nfs: Represents a volume backed by an NFS server. Additional keys: - ◆ location: (required) The location of the NFS Server, in the form - SERVER:/PATH - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - - --clear-volumes - Remove all existing volumes from the Cloud Run resource, including - volumes mounted as secrets - - --remove-volume=[VOLUME,...] - Removes volumes from the Cloud Run resource. - - At most one of these can be specified: - - --binary-authorization=POLICY - Binary Authorization policy to check against. This must be set to - "default". - - --clear-binary-authorization - Remove any previously set Binary Authorization policy. - - At most one of these can be specified: - - --clear-encryption-key-shutdown-hours - Remove any previously set CMEK key shutdown hours setting. - - --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - The number of hours to wait before an automatic shutdown server - after CMEK key revocation is detected. - - At most one of these can be specified: - - --clear-key - Remove any previously set CMEK key reference. - - --key=KEY - CMEK key reference to encrypt the container with. - - At most one of these can be specified: - - --clear-network - Disconnect this Cloud Run service from the VPC network it is - connected to. - - Direct VPC egress setting flags group. - - --network=NETWORK - The VPC network that the Cloud Run service will be able to send - traffic to. If --subnet is also specified, subnet must be a - subnetwork of the network specified by this --network flag. To - clear existing VPC network settings, use --clear-network. - - --subnet=SUBNET - The VPC subnetwork that the Cloud Run service will get IPs from. - The subnetwork must be /26 or larger. If --network is also - specified, subnet must be a subnetwork of the network specified - by the --network flag. If --network is not specified, network - will be looked up from this subnetwork. To clear existing VPC - network settings, use --clear-network. - - At most one of these can be specified: - - --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. - - --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. - - At most one of these can be specified: - - --clear-post-key-revocation-action-type - Remove any previously set post CMEK key revocation action type. - - --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE - Action type after CMEK key revocation. - POST_KEY_REVOCATION_ACTION_TYPE must be one of: - - prevent-new - No new instances will be started after CMEK key revocation. - shut-down - No new instances will be started and the existing instances - will be shut down after CMEK key revocation. + --key=KEY + CMEK key reference to encrypt the container with. At most one of these can be specified: @@ -590,119 +545,53 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: + At most one of these can be specified: - --connectivity=CONNECTIVITY - (DEPRECATED) Defaults to 'external'. If 'external', the service can - be invoked through the internet, in addition to through the cluster - network. + --clear-network + Disconnect this Cloud Run service from the VPC network it is + connected to. - The --connectivity flag is deprecated but will continue to be - supported. Prefer to use the --ingress flag instead. CONNECTIVITY - must be one of: + Direct VPC egress setting flags group. - external - Visible from outside the cluster. - internal - Visible only within the cluster. + --network=NETWORK + The VPC network that the Cloud Run service will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. + --subnet=SUBNET + The VPC subnetwork that the Cloud Run service will get IPs from. + The subnetwork must be /26 or larger. If --network is also + specified, subnet must be a subnetwork of the network specified by + the --network flag. If --network is not specified, network will be + looked up from this subnetwork. To clear existing VPC network + settings, use --clear-network. - At most one of these can be specified: + At most one of these can be specified: - --clear-config-maps - Remove all config-maps. + --clear-network-tags + Clears all existing Compute Engine tags from the Cloud Run + service. - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used - together. If both are specified, --remove-config-maps will be applied - first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - - Arguments to locate resources, depending on the platform used. + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. To clear existing tags, use + --clear-network-tags. At most one of these can be specified: - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. + --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE + Action type after CMEK key revocation. + POST_KEY_REVOCATION_ACTION_TYPE must be one of: - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▸ set the property run/cluster with a fully specified name; - ▸ specify the cluster from a list of available clusters with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the - cluster. - - To set the cluster attribute: - ▫ provide the argument --cluster on the command line; - ▫ set the property run/cluster; - ▫ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ▫ provide the argument --cluster on the command line with a - fully specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --cluster-location on the command line; - ▫ set the property run/cluster_location; - ▫ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + prevent-new + No new instances will be started after CMEK key revocation. + shut-down + No new instances will be started and the existing instances will + be shut down after CMEK key revocation. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/services/update-traffic b/gcloud/beta/run/services/update-traffic index 2e80175e2..f7511787a 100644 --- a/gcloud/beta/run/services/update-traffic +++ b/gcloud/beta/run/services/update-traffic @@ -4,12 +4,9 @@ NAME SYNOPSIS gcloud beta run services update-traffic [[SERVICE] --namespace=NAMESPACE] - [--async] [--platform=PLATFORM; default="managed"] + [--async] [--region=REGION] [--clear-tags | --set-tags=[TAG=REVISION,...] | --remove-tags=[TAG,...] --update-tags=[TAG=REVISION,...]] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--to-latest | --to-revisions=[REVISION-NAME=PERCENTAGE,...] | --to-tags=[TAG=PERCENTAGE,...]] [GCLOUD_WIDE_FLAG ...] @@ -77,22 +74,9 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. Specify traffic tags. Traffic tags can be assigned to a revision by name or to the latest ready revision. Assigning a tag to a revision generates a @@ -125,69 +109,6 @@ FLAGS --update-tags=[TAG=REVISION,...] List of key-value pairs to set as tags. - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - At most one of these can be specified: --to-latest diff --git a/gcloud/beta/service-extensions/wasm-plugins/create b/gcloud/beta/service-extensions/wasm-plugins/create index 0acd20279..4e93cc51d 100644 --- a/gcloud/beta/service-extensions/wasm-plugins/create +++ b/gcloud/beta/service-extensions/wasm-plugins/create @@ -16,10 +16,6 @@ DESCRIPTION (BETA) Create a new WasmPlugin resource. EXAMPLES - To create a WasmPlugin called my-plugin, run: - - $ gcloud beta service-extensions wasm-plugins create my-plugin - To create a WasmPlugin called my-plugin, together with a new version called v1, and set it as main, run: diff --git a/gcloud/beta/service-extensions/wasm-plugins/delete b/gcloud/beta/service-extensions/wasm-plugins/delete index 943726e8c..72a825732 100644 --- a/gcloud/beta/service-extensions/wasm-plugins/delete +++ b/gcloud/beta/service-extensions/wasm-plugins/delete @@ -9,6 +9,9 @@ SYNOPSIS DESCRIPTION (BETA) Delete a WasmPlugin resource. + Please note that all WasmPluginVersions associated with the WasmPlugin will + also be deleted. + EXAMPLES To delete a WasmPlugin called my-plugin, run: diff --git a/gcloud/beta/spanner/backup-schedules/create b/gcloud/beta/spanner/backup-schedules/create index 50a1018ac..acf0d9d27 100644 --- a/gcloud/beta/spanner/backup-schedules/create +++ b/gcloud/beta/spanner/backup-schedules/create @@ -7,8 +7,8 @@ SYNOPSIS (BACKUP_SCHEDULE : --database=DATABASE --instance=INSTANCE) --backup-type=[BACKUP_TYPE] --cron=CRON --retention-duration=RETENTION_DURATION - [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + [--encryption-type=ENCRYPTION_TYPE --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] @@ -111,6 +111,28 @@ OPTIONAL FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to create the Cloud Spanner + backup. 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 kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner backup. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/beta/spanner/backup-schedules/update b/gcloud/beta/spanner/backup-schedules/update index e7f70777c..885ad0b18 100644 --- a/gcloud/beta/spanner/backup-schedules/update +++ b/gcloud/beta/spanner/backup-schedules/update @@ -6,8 +6,8 @@ SYNOPSIS gcloud beta spanner backup-schedules update (BACKUP_SCHEDULE : --database=DATABASE --instance=INSTANCE) (--cron=CRON --encryption-type=ENCRYPTION_TYPE - --retention-duration=RETENTION_DURATION [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + --retention-duration=RETENTION_DURATION --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]) [GCLOUD_WIDE_FLAG ...] @@ -99,6 +99,28 @@ REQUIRED FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to create the Cloud Spanner + backup. 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 kms-project attribute: + ▫ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▫ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▫ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ◇ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner backup. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/beta/spanner/backups/copy b/gcloud/beta/spanner/backups/copy index 8b6ef32f5..93c80eff7 100644 --- a/gcloud/beta/spanner/backups/copy +++ b/gcloud/beta/spanner/backups/copy @@ -10,8 +10,8 @@ SYNOPSIS | --retention-period=RETENTION_PERIOD) (--source-backup=SOURCE_BACKUP : --source-instance=SOURCE_INSTANCE) [--async] - [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + [--encryption-type=ENCRYPTION_TYPE --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] @@ -133,6 +133,28 @@ OPTIONAL FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to copy the Cloud Spanner + backup. 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 kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to copy the Cloud Spanner backup. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/beta/spanner/backups/create b/gcloud/beta/spanner/backups/create index b4f808c4f..e97187c6b 100644 --- a/gcloud/beta/spanner/backups/create +++ b/gcloud/beta/spanner/backups/create @@ -8,8 +8,8 @@ SYNOPSIS (--expiration-date=EXPIRATION_DATE | --retention-period=RETENTION_PERIOD) [--async] [--version-time=TIMESTAMP] - [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + [--encryption-type=ENCRYPTION_TYPE --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] @@ -102,6 +102,28 @@ OPTIONAL FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to create the Cloud Spanner + backup. 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 kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner backup. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/beta/spanner/databases/create b/gcloud/beta/spanner/databases/create index ad535ba18..e943dde43 100644 --- a/gcloud/beta/spanner/databases/create +++ b/gcloud/beta/spanner/databases/create @@ -5,8 +5,9 @@ SYNOPSIS gcloud beta spanner databases create (DATABASE : --instance=INSTANCE) [--async] [--database-dialect=DATABASE_DIALECT] [--ddl=DDL] [--ddl-file=DDL_FILE] [--proto-descriptors-file=PROTO_DESCRIPTORS_FILE] - [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING - --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] + [--kms-keys=[KMS_KEYS,...] | [--kms-key=KMS_KEY + : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -96,6 +97,28 @@ FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to create the Cloud Spanner + database. This represents a Cloud resource. (NOTE) Some attributes are + not given arguments in this group but can be set in other ways. + + To set the kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner database. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/beta/spanner/databases/restore b/gcloud/beta/spanner/databases/restore index c6663c2cc..0653dda95 100644 --- a/gcloud/beta/spanner/databases/restore +++ b/gcloud/beta/spanner/databases/restore @@ -7,8 +7,8 @@ SYNOPSIS : --destination-instance=DESTINATION_INSTANCE) (--source-backup=SOURCE_BACKUP : --source-instance=SOURCE_INSTANCE) [--async] - [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + [--encryption-type=ENCRYPTION_TYPE --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] @@ -114,6 +114,28 @@ OPTIONAL FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to restore the Cloud Spanner + database. This represents a Cloud resource. (NOTE) Some attributes are + not given arguments in this group but can be set in other ways. + + To set the kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to restore the Cloud Spanner database. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index 0f9c6cda8..7437b56d1 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -44,6 +44,7 @@ SYNOPSIS [--psc-auto-connections=[network=NETWORK],[project=PROJECT]] [--[no-]recreate-replicas-on-primary-crash] [--replica-type=REPLICA_TYPE] [--replication=REPLICATION] + [--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE] [--require-ssl] [--retained-backups-count=RETAINED_BACKUPS_COUNT] [--retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS] [--root-password=ROOT_PASSWORD] [--server-ca-mode=SERVER_CA_MODE] @@ -427,6 +428,12 @@ FLAGS Type of replication this instance uses. The default is synchronous. REPLICATION must be one of: synchronous, asynchronous. + --replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE + Set a maximum replication lag for a MySQL read replica in seconds. If + the replica lag exceeds the specified value, the readreplica(s) will be + recreated. Min value=300 seconds,Max value=31536000 seconds, default + value=31536000 seconds. + --require-ssl Specified if users connecting over IP must use SSL. diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 9cc38d11d..31bedf55c 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -43,6 +43,7 @@ SYNOPSIS [--pricing-plan=PRICING_PLAN, -p PRICING_PLAN] [--[no-]recreate-replicas-on-primary-crash] [--remove-deny-maintenance-period] [--replication=REPLICATION] + [--replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE] [--[no-]require-ssl] [--simulate-maintenance-event] [--ssl-mode=SSL_MODE] [--[no-]storage-auto-increase] [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] @@ -357,6 +358,12 @@ FLAGS Type of replication this instance uses. The default is synchronous. REPLICATION must be one of: synchronous, asynchronous. + --replication-lag-max-seconds-for-recreate=REPLICATION_LAG_MAX_SECONDS_FOR_RECREATE + Set a maximum replication lag for a MySQL read replica in seconds. If + the replica lag exceeds the specified value, the readreplica(s) will be + recreated. Min value=300 seconds,Max value=31536000 seconds, default + value=31536000 seconds. + --[no-]require-ssl mysqld should default to 'REQUIRE X509' for users connecting over IP. Use --require-ssl to enable and --no-require-ssl to disable. diff --git a/gcloud/compute/commitments/create b/gcloud/compute/commitments/create index 7bc44bd77..d0374ab41 100644 --- a/gcloud/compute/commitments/create +++ b/gcloud/compute/commitments/create @@ -5,6 +5,7 @@ SYNOPSIS gcloud compute commitments create COMMITMENT --plan=PLAN (--resources=[local-ssd=LOCAL-SSD],[memory=MEMORY],[vcpu=VCPU] --resources-accelerator=[count=COUNT],[type=TYPE]) [--auto-renew] + [--custom-end-time=CUSTOM_END_TIME] [--merge-source-commitments=MERGE_SOURCE_COMMITMENTS] [--region=REGION] [--split-source-commitment=SPLIT_SOURCE_COMMITMENT] [--type=TYPE; default="general-purpose"] @@ -66,6 +67,10 @@ OPTIONAL FLAGS --auto-renew Enable auto renewal for the commitment. + --custom-end-time=CUSTOM_END_TIME + Specifies a custom future end date and extends the commitment's ongoing + term. + --merge-source-commitments=MERGE_SOURCE_COMMITMENTS Creates the new commitment by merging the specified source commitments and combining their resources. diff --git a/gcloud/compute/commitments/update b/gcloud/compute/commitments/update index caafa5510..18671a91e 100644 --- a/gcloud/compute/commitments/update +++ b/gcloud/compute/commitments/update @@ -2,8 +2,9 @@ NAME gcloud compute commitments update - update Compute Engine commitments SYNOPSIS - gcloud compute commitments update COMMITMENT [--auto-renew] [--plan=PLAN] - [--region=REGION] [GCLOUD_WIDE_FLAG ...] + gcloud compute commitments update COMMITMENT [--auto-renew] + [--custom-end-time=CUSTOM_END_TIME] [--plan=PLAN] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update Compute Engine commitments. @@ -35,6 +36,10 @@ FLAGS --auto-renew Enable auto renewal for the commitment. + --custom-end-time=CUSTOM_END_TIME + Specifies a custom future end date and extends the commitment's ongoing + term. + --plan=PLAN Duration of the commitment. PLAN must be (only one value is supported): 36-month. diff --git a/gcloud/compute/service-attachments/create b/gcloud/compute/service-attachments/create index c53a2e55e..4fc9dedd8 100644 --- a/gcloud/compute/service-attachments/create +++ b/gcloud/compute/service-attachments/create @@ -14,6 +14,7 @@ SYNOPSIS [--domain-names=[DOMAIN_NAMES,...]] [--enable-proxy-protocol] [--nat-subnets-region=NAT_SUBNETS_REGION] [--producer-forwarding-rule-region=PRODUCER_FORWARDING_RULE_REGION] + [--propagated-connection-limit=PROPAGATED_CONNECTION_LIMIT] [--reconcile-connections] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -133,6 +134,21 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + --propagated-connection-limit=PROPAGATED_CONNECTION_LIMIT + The number of consumer spokes that connected Private Service Connect + endpoints can be propagated to through Network Connectivity Center. + This limit lets the service producer limit how many propagated Private + Service Connect connections can be established to this service + attachment from a single consumer. + + If the connection preference of the service attachment is + ACCEPT_MANUAL, the limit applies to each project or network that is + listed in the consumer accept list. If the connection preference of the + service attachment is ACCEPT_AUTOMATIC, the limit applies to each + project that contains a connected endpoint. + + If unspecified, the default propagated connection limit is 250. + --reconcile-connections Determines whether to apply changes to consumer accept or reject lists to existing connections or only to new connections. diff --git a/gcloud/compute/service-attachments/update b/gcloud/compute/service-attachments/update index 127cdedf1..72a482e52 100644 --- a/gcloud/compute/service-attachments/update +++ b/gcloud/compute/service-attachments/update @@ -10,6 +10,7 @@ SYNOPSIS [--[no-]enable-proxy-protocol] [--nat-subnets=NAT_SUBNETS,[NAT_SUBNETS,...]] [--nat-subnets-region=NAT_SUBNETS_REGION] + [--propagated-connection-limit=PROPAGATED_CONNECTION_LIMIT] [--[no-]reconcile-connections] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -93,6 +94,21 @@ FLAGS set to the region of the service attachment. Overrides the default compute/region property value for this command invocation. + --propagated-connection-limit=PROPAGATED_CONNECTION_LIMIT + The number of consumer spokes that connected Private Service Connect + endpoints can be propagated to through Network Connectivity Center. + This limit lets the service producer limit how many propagated Private + Service Connect connections can be established to this service + attachment from a single consumer. + + If the connection preference of the service attachment is + ACCEPT_MANUAL, the limit applies to each project or network that is + listed in the consumer accept list. If the connection preference of the + service attachment is ACCEPT_AUTOMATIC, the limit applies to each + project that contains a connected endpoint. + + If unspecified, the default propagated connection limit is 250. + --[no-]reconcile-connections Determines whether to apply changes to consumer accept or reject lists to existing connections or only to new connections. diff --git a/gcloud/compute/snapshot-settings/describe b/gcloud/compute/snapshot-settings/describe index 422997c63..4bf9ab861 100644 --- a/gcloud/compute/snapshot-settings/describe +++ b/gcloud/compute/snapshot-settings/describe @@ -21,8 +21,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the compute/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/compute/ + This command uses the compute/alpha or compute/beta or comptue/v1 API. The + full documentation for this API can be found at: + https://cloud.google.com/compute/ NOTES These variants are also available: diff --git a/gcloud/compute/snapshot-settings/update b/gcloud/compute/snapshot-settings/update index c8268b2fb..77ba60ebe 100644 --- a/gcloud/compute/snapshot-settings/update +++ b/gcloud/compute/snapshot-settings/update @@ -15,19 +15,20 @@ EXAMPLES nearest multi-region as the source disk, run: $ gcloud compute snapshot-settings update \ - --storage-location-policy=nearest-multi-region + --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 + $ gcloud 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 compute snapshot-settings update \ - --storage-location-policy=specific-locations \ - --storage-location-names=us-west1 + --storage-location-policy=specific-locations \ + --storage-location-names=us-west1 FLAGS --async @@ -58,8 +59,9 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the compute/v1 API. The full documentation for this API - can be found at: https://cloud.google.com/compute/ + This command uses the compute/alpha or compute/beta or compute/v1 API. The + full documentation for this API can be found at: + https://cloud.google.com/compute/ NOTES These variants are also available: diff --git a/gcloud/config/get b/gcloud/config/get index a457a6b39..b5dec87c1 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -731,6 +731,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/config/help b/gcloud/config/help index e99dac4b4..487e8e61a 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -763,6 +763,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/config/list b/gcloud/config/list index 783e513c6..94ba4985b 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -775,6 +775,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/config/set b/gcloud/config/set index cdc573dcf..5fd27037b 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -778,6 +778,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/config/unset b/gcloud/config/unset index e4187917f..78a885a74 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -739,6 +739,14 @@ AVAILABLE PROPERTIES If True, kaniko will be used to build images described by a Dockerfile, instead of docker build. + colab + region + Default region to use when working with Colab Enterprise resources. + When a --region flag is required but not provided, the command will + fall back to this value, if set. Please see + https://cloud.google.com/colab/docs/locations for a list of + supported regions. + component_manager additional_repositories Comma separated list of additional repositories to check for diff --git a/gcloud/container/aws/node-pools/create b/gcloud/container/aws/node-pools/create index 226d89843..66e211100 100644 --- a/gcloud/container/aws/node-pools/create +++ b/gcloud/container/aws/node-pools/create @@ -10,7 +10,12 @@ SYNOPSIS --max-pods-per-node=MAX_PODS_PER_NODE --node-version=NODE_VERSION --subnet-id=SUBNET_ID (--max-nodes=MAX_NODES --min-nodes=MIN_NODES) [--annotations=ANNOTATION,[ANNOTATION,...]] [--async] - [--enable-autorepair] [--max-surge-update=MAX_SURGE_UPDATE] + [--enable-autorepair] + [--kubelet-config-cpu-cfs-quota=KUBELET_CONFIG_CPU_CFS_QUOTA] + [--kubelet-config-cpu-cfs-quota-period=KUBELET_CONFIG_CPU_CFS_QUOTA_PERIOD] + [--kubelet-config-cpu-manager-policy=KUBELET_CONFIG_CPU_MANAGER_POLICY] + [--kubelet-config-pod-pids-limit=KUBELET_CONFIG_POD_PIDS_LIMIT] + [--max-surge-update=MAX_SURGE_UPDATE] [--max-unavailable-update=MAX_UNAVAILABLE_UPDATE] [--node-labels=NODE_LABEL,[NODE_LABEL,...]] [--node-taints=NODE_TAINT,[NODE_TAINT,...]] @@ -129,6 +134,20 @@ OPTIONAL FLAGS Node autorepair is disabled by default. + --kubelet-config-cpu-cfs-quota=KUBELET_CONFIG_CPU_CFS_QUOTA + Enforce a Kubelet CPU CFS quota. + + --kubelet-config-cpu-cfs-quota-period=KUBELET_CONFIG_CPU_CFS_QUOTA_PERIOD + Kubelet CPU CFS quota period, within the range "1ms" to "1s". + + --kubelet-config-cpu-manager-policy=KUBELET_CONFIG_CPU_MANAGER_POLICY + Kubelet CPU manager policy. KUBELET_CONFIG_CPU_MANAGER_POLICY must be + one of: none, static. + + --kubelet-config-pod-pids-limit=KUBELET_CONFIG_POD_PIDS_LIMIT + Kubelet maximum number of PIDS in any pod, within the range 1024 to + 4194304. + --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 diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 8cd01709b..facb3e176 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -19,15 +19,16 @@ SYNOPSIS [--enable-backup-restore] [--enable-cilium-clusterwide-network-policy] [--enable-dns-access] [--enable-fleet] [--enable-google-cloud-access] [--enable-ip-access] [--enable-kubernetes-unstable-apis=API,[API,...]] - [--enable-master-global-access] [--enable-ray-cluster-logging] - [--enable-ray-cluster-monitoring] [--enable-ray-operator] - [--enable-secret-manager] [--fleet-project=PROJECT_ID_OR_NUMBER] - [--labels=[KEY=VALUE,...]] [--logging=[COMPONENT,...]] - [--monitoring=[COMPONENT,...]] [--network=NETWORK] - [--private-endpoint-subnetwork=NAME] [--release-channel=[CHANNEL]] - [--security-group=SECURITY_GROUP] [--security-posture=SECURITY_POSTURE] - [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] - [--subnetwork=SUBNETWORK] [--workload-policies=WORKLOAD_POLICIES] + [--enable-master-global-access] [--enable-multi-networking] + [--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring] + [--enable-ray-operator] [--enable-secret-manager] + [--fleet-project=PROJECT_ID_OR_NUMBER] [--labels=[KEY=VALUE,...]] + [--logging=[COMPONENT,...]] [--monitoring=[COMPONENT,...]] + [--network=NETWORK] [--private-endpoint-subnetwork=NAME] + [--release-channel=[CHANNEL]] [--security-group=SECURITY_GROUP] + [--security-posture=SECURITY_POSTURE] [--services-ipv4-cidr=CIDR] + [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] + [--workload-policies=WORKLOAD_POLICIES] [--workload-vulnerability-scanning=WORKLOAD_VULNERABILITY_SCANNING] [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability @@ -267,6 +268,10 @@ FLAGS endpoint from any Google Cloud region or on-premises environment regardless of the private cluster's region. + --enable-multi-networking + Enables multi-networking on the cluster. Multi-networking is disabled + by default. + --enable-ray-cluster-logging Enable automatic log processing sidecar for Ray clusters. diff --git a/gcloud/dataproc/clusters/create b/gcloud/dataproc/clusters/create index 1bf66405d..2dd63be6d 100644 --- a/gcloud/dataproc/clusters/create +++ b/gcloud/dataproc/clusters/create @@ -47,7 +47,6 @@ SYNOPSIS [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] - [--worker-machine-type=WORKER_MACHINE_TYPE] [--worker-min-cpu-platform=PLATFORM] [--zone=ZONE, -z ZONE] [--expiration-time=EXPIRATION_TIME | --max-age=MAX_AGE] [--gce-pd-kms-key=GCE_PD_KMS_KEY @@ -74,7 +73,9 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] - [GCLOUD_WIDE_FLAG ...] + [--worker-machine-type=WORKER_MACHINE_TYPE + | --worker-machine-types=type=MACHINE_TYPE[, + type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a cluster. @@ -451,9 +452,6 @@ FLAGS --worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE Interface to use to attach local SSDs to each worker in a cluster. - --worker-machine-type=WORKER_MACHINE_TYPE - The type of machine to use for workers. Defaults to server-specified. - --worker-min-cpu-platform=PLATFORM When specified, the VM is scheduled on the host with a specified CPU architecture or a more recent CPU platform that's available in that @@ -946,6 +944,25 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. + At most one of these can be specified: + + --worker-machine-type=WORKER_MACHINE_TYPE + The type of machine to use for primary workers. Defaults to + server-specified. + + --worker-machine-types=type=MACHINE_TYPE[,type=MACHINE_TYPE...][,rank=RANK] + Machine types + (https://cloud.google.com/dataproc/docs/concepts/compute/supported-machine-types) + for primary worker nodes to use with optional rank. A lower rank + number is given higher preference. Based on availablilty, Dataproc + tries to create primary worker VMs using the worker machine type with + the lowest rank, and then tries to use machine types with higher + ranks as necessary. Machine types with the same rank are given the + same preference. Example use: + --worker-machine-types="type=e2-standard-8,type=n2-standard-8,rank=0". + For more information, see Dataproc Flexible VMs + (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/flexible-vms) + 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/dataproc/workflow-templates/set-managed-cluster b/gcloud/dataproc/workflow-templates/set-managed-cluster index fa2645044..a93a5319f 100644 --- a/gcloud/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/dataproc/workflow-templates/set-managed-cluster @@ -40,7 +40,6 @@ SYNOPSIS [--worker-boot-disk-size=WORKER_BOOT_DISK_SIZE] [--worker-boot-disk-type=WORKER_BOOT_DISK_TYPE] [--worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE] - [--worker-machine-type=WORKER_MACHINE_TYPE] [--worker-min-cpu-platform=PLATFORM] [--zone=ZONE] [--identity-config-file=IDENTITY_CONFIG_FILE | --secure-multi-tenancy-user-mapping=SECURE_MULTI_TENANCY_USER_MAPPING] @@ -62,7 +61,9 @@ SYNOPSIS --num-secondary-workers=NUM_SECONDARY_WORKERS --num-workers=NUM_WORKERS --secondary-worker-type=TYPE; default="preemptible"] - [GCLOUD_WIDE_FLAG ...] + [--worker-machine-type=WORKER_MACHINE_TYPE + | --worker-machine-types=type=MACHINE_TYPE[, + type=MACHINE_TYPE...][,rank=RANK]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Set a managed cluster for the workflow template. @@ -373,9 +374,6 @@ FLAGS --worker-local-ssd-interface=WORKER_LOCAL_SSD_INTERFACE Interface to use to attach local SSDs to each worker in a cluster. - --worker-machine-type=WORKER_MACHINE_TYPE - The type of machine to use for workers. Defaults to server-specified. - --worker-min-cpu-platform=PLATFORM When specified, the VM is scheduled on the host with a specified CPU architecture or a more recent CPU platform that's available in that @@ -814,6 +812,25 @@ FLAGS The type of the secondary worker group. TYPE must be one of: preemptible, non-preemptible, spot. + At most one of these can be specified: + + --worker-machine-type=WORKER_MACHINE_TYPE + The type of machine to use for primary workers. Defaults to + server-specified. + + --worker-machine-types=type=MACHINE_TYPE[,type=MACHINE_TYPE...][,rank=RANK] + Machine types + (https://cloud.google.com/dataproc/docs/concepts/compute/supported-machine-types) + for primary worker nodes to use with optional rank. A lower rank + number is given higher preference. Based on availablilty, Dataproc + tries to create primary worker VMs using the worker machine type with + the lowest rank, and then tries to use machine types with higher + ranks as necessary. Machine types with the same rank are given the + same preference. Example use: + --worker-machine-types="type=e2-standard-8,type=n2-standard-8,rank=0". + For more information, see Dataproc Flexible VMs + (https://cloud.google.com/dataproc/docs/concepts/configuring-clusters/flexible-vms) + 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/datastore/indexes/cleanup b/gcloud/datastore/indexes/cleanup index 6471895fc..43b3eb24d 100644 --- a/gcloud/datastore/indexes/cleanup +++ b/gcloud/datastore/indexes/cleanup @@ -3,7 +3,8 @@ NAME your local index configuration SYNOPSIS - gcloud datastore indexes cleanup INDEX_FILE [GCLOUD_WIDE_FLAG ...] + gcloud datastore indexes cleanup INDEX_FILE [--database=DATABASE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command removes unused datastore indexes based on your local index @@ -21,6 +22,15 @@ POSITIONAL ARGUMENTS your index.yaml file, refer to this configuration guide: https://cloud.google.com/datastore/docs/tools/indexconfig#Datastore_About_index_yaml +FLAGS + --database=DATABASE + The database to operate on. If not specified, the CLI refers the + (default) database by default. + + For example, to operate on database testdb: + + $ gcloud datastore indexes cleanup --database='testdb' + 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/logging/help b/gcloud/logging/help index e52d0bdf8..c1c3cafc1 100644 --- a/gcloud/logging/help +++ b/gcloud/logging/help @@ -36,6 +36,9 @@ GROUPS resource-descriptors Get information about resource descriptors. + scopes + Manages Cloud Logging log scopes. + settings Manages the org settings for the Cloud Logging Logs Router. diff --git a/gcloud/logging/scopes/create b/gcloud/logging/scopes/create new file mode 100644 index 000000000..8a2e186f2 --- /dev/null +++ b/gcloud/logging/scopes/create @@ -0,0 +1,80 @@ +NAME + gcloud logging scopes create - create a log scope + +SYNOPSIS + gcloud logging scopes create LOG_SCOPE_ID + --resource-names=[RESOURCE_NAMES,...] [--description=DESCRIPTION] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + After creating a log scope, you can use it to view logs in 1 or more + resources. + +EXAMPLES + To create a log scope in a project, run: + + $ gcloud logging scopes create my-scope \ + --resource-names=projects/my-project + + To create a log scope in a project with a description, run: + + $ gcloud logging scopes create my-scope \ + --resource-names=projects/my-project --description="my + custom log scope" + + To create a log scope that contains more than 1 resource, such as projects + and views, run: + + $ gcloud logging scopes create my-scope \ + --resource-names=projects/my-project,projects/my-project2, \ + projects/my-project/locations/global/buckets/my-bucket/views/\ + my-view1, \ + projects/my-project/locations/global/buckets/my-bucket/views/\ + my-view2, + +POSITIONAL ARGUMENTS + LOG_SCOPE_ID + ID of the log scope to create. + +REQUIRED FLAGS + --resource-names=[RESOURCE_NAMES,...] + Comma-separated list of resource names in this log scope. It could be + one or more parent resources or one or more views. A log scope can + include a maximum of 50 projects and a maximum of 100 resources in + total. For example, projects/[PROJECT_ID], + projects/[PROJECT_ID]/locations/[LOCATION_ID]/buckets/[BUCKET_ID]/views/[VIEW_ID] + +OPTIONAL FLAGS + --description=DESCRIPTION + A textual description for the log scope. + + At most one of these can be specified: + + --folder=FOLDER_ID + Folder of the log scope to create. + + --organization=ORGANIZATION_ID + Organization of the log scope to create. + + --project=PROJECT_ID + Project of the log scope to create. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +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. diff --git a/gcloud/logging/scopes/delete b/gcloud/logging/scopes/delete new file mode 100644 index 000000000..1cc2bec50 --- /dev/null +++ b/gcloud/logging/scopes/delete @@ -0,0 +1,47 @@ +NAME + gcloud logging scopes delete - delete a log scope + +SYNOPSIS + gcloud logging scopes delete LOG_SCOPE_ID + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To delete a log scope, run: + + $ gcloud logging scopes delete my-scope + +POSITIONAL ARGUMENTS + LOG_SCOPE_ID + ID of the log scope to delete. + +FLAGS + At most one of these can be specified: + + --folder=FOLDER_ID + Folder of the log scope to delete. + + --organization=ORGANIZATION_ID + Organization of the log scope to delete. + + --project=PROJECT_ID + Project of the log scope to delete. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +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. diff --git a/gcloud/logging/scopes/describe b/gcloud/logging/scopes/describe new file mode 100644 index 000000000..8c7781887 --- /dev/null +++ b/gcloud/logging/scopes/describe @@ -0,0 +1,50 @@ +NAME + gcloud logging scopes describe - display information about a log scope + +SYNOPSIS + gcloud logging scopes describe LOG_SCOPE_ID + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Display information about a log scope. + +EXAMPLES + To describe a log scope in a project, run: + + $ gcloud logging scopes describe my-scope --project=my-project + +POSITIONAL ARGUMENTS + LOG_SCOPE_ID + The ID of the log scope to describe. + +FLAGS + At most one of these can be specified: + + --folder=FOLDER_ID + Folder of the log scope to describe. + + --organization=ORGANIZATION_ID + Organization of the log scope to describe. + + --project=PROJECT_ID + Project of the log scope to describe. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +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. diff --git a/gcloud/logging/scopes/help b/gcloud/logging/scopes/help new file mode 100644 index 000000000..f029f4117 --- /dev/null +++ b/gcloud/logging/scopes/help @@ -0,0 +1,32 @@ +NAME + gcloud logging scopes - manages Cloud Logging log scopes + +SYNOPSIS + gcloud logging scopes COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing Cloud Logging log scopes. A scope is used to describe + a group of resources to read log entries from. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a log scope. + + delete + Delete a log scope. + + describe + Display information about a log scope. + + list + List the defined log scopes. + + update + Update a log scope. diff --git a/gcloud/logging/scopes/list b/gcloud/logging/scopes/list new file mode 100644 index 000000000..301a509f8 --- /dev/null +++ b/gcloud/logging/scopes/list @@ -0,0 +1,80 @@ +NAME + gcloud logging scopes list - list the defined log scopes + +SYNOPSIS + gcloud logging scopes list + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List the log scopes for a project. + +EXAMPLES + To list the log scopes in a project, run: + + $ gcloud logging scopes list --project=my-project + +FLAGS + At most one of these can be specified: + + --folder=FOLDER_ID + Folder of the log scopes to list. + + --organization=ORGANIZATION_ID + Organization of the log scopes to list. + + --project=PROJECT_ID + Project of the log scopes to list. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +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. diff --git a/gcloud/logging/scopes/update b/gcloud/logging/scopes/update new file mode 100644 index 000000000..b31cbbcb5 --- /dev/null +++ b/gcloud/logging/scopes/update @@ -0,0 +1,43 @@ +NAME + gcloud logging scopes update - update a log scope + +SYNOPSIS + gcloud logging scopes update LOG_SCOPE_ID [--description=DESCRIPTION] + [--resource-names=[RESOURCE_NAMES,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update the properties of a log scope. + +EXAMPLES + To update the description of a log scope in a project, run: + + $ gcloud logging scopes update my-scope \ + --description=my-new-description --project=my-project + + To update the resource name of a log scope in a project. Ensure that you + provide all the resource names including the existing ones. For example, if + the log scope has the resource name my-project, and you want to update the + log scope to have the resource name another-project, run the following: + + $ gcloud logging scopes update my-scope \ + --resource-names=projects/my-project,projects/another-project \ + --project=my-project + +POSITIONAL ARGUMENTS + LOG_SCOPE_ID + The ID of the log scope to update. + +FLAGS + --description=DESCRIPTION + A new description for the log scope. + + --resource-names=[RESOURCE_NAMES,...] + A new set of resource names for the log scope. + +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. diff --git a/gcloud/network-management/connectivity-tests/create b/gcloud/network-management/connectivity-tests/create index 69bf57535..c6a80beed 100644 --- a/gcloud/network-management/connectivity-tests/create +++ b/gcloud/network-management/connectivity-tests/create @@ -8,7 +8,9 @@ SYNOPSIS --destination-forwarding-rule=DESTINATION_FORWARDING_RULE --destination-gke-master-cluster=DESTINATION_GKE_MASTER_CLUSTER --destination-instance=DESTINATION_INSTANCE - --destination-ip-address=DESTINATION_IP_ADDRESS) + --destination-ip-address=DESTINATION_IP_ADDRESS + --destination-redis-cluster=DESTINATION_REDIS_CLUSTER + --destination-redis-instance=DESTINATION_REDIS_INSTANCE) (--source-app-engine-version=SOURCE_APP_ENGINE_VERSION --source-cloud-function=SOURCE_CLOUD_FUNCTION --source-cloud-run-revision=SOURCE_CLOUD_RUN_REVISION @@ -78,6 +80,12 @@ REQUIRED FLAGS The IP address of the destination which can be an external or internal IP. + --destination-redis-cluster=DESTINATION_REDIS_CLUSTER + A Redis cluster URI as the destination endpoint. + + --destination-redis-instance=DESTINATION_REDIS_INSTANCE + A Redis instance URI as the destination endpoint. + At least one of these must be specified: --source-app-engine-version=SOURCE_APP_ENGINE_VERSION diff --git a/gcloud/network-management/connectivity-tests/update b/gcloud/network-management/connectivity-tests/update index 2397bfc84..c14080819 100644 --- a/gcloud/network-management/connectivity-tests/update +++ b/gcloud/network-management/connectivity-tests/update @@ -22,6 +22,10 @@ SYNOPSIS | --destination-instance=DESTINATION_INSTANCE] [--clear-destination-ip-address | --destination-ip-address=DESTINATION_IP_ADDRESS] + [--clear-destination-redis-cluster + | --destination-redis-cluster=DESTINATION_REDIS_CLUSTER] + [--clear-destination-redis-instance + | --destination-redis-instance=DESTINATION_REDIS_INSTANCE] [--clear-source-app-engine-version | --source-app-engine-version=SOURCE_APP_ENGINE_VERSION] [--clear-source-cloud-function @@ -153,6 +157,22 @@ FLAGS The IP address of the destination which can be an external or internal IP. + At most one of these can be specified: + + --clear-destination-redis-cluster + Clear existing destination Redis Cluster. + + --destination-redis-cluster=DESTINATION_REDIS_CLUSTER + A Redis cluster URI as the destination endpoint. + + At most one of these can be specified: + + --clear-destination-redis-instance + Clear existing destination Redis Instance. + + --destination-redis-instance=DESTINATION_REDIS_INSTANCE + A Redis instance URI as the destination endpoint. + At most one of these can be specified: --clear-source-app-engine-version diff --git a/gcloud/redis/clusters/create b/gcloud/redis/clusters/create index 2e4c574bd..3fe0cfa59 100644 --- a/gcloud/redis/clusters/create +++ b/gcloud/redis/clusters/create @@ -3,12 +3,12 @@ NAME instance SYNOPSIS - gcloud redis clusters create (CLUSTER : --region=REGION) --network=NETWORK + gcloud redis clusters create (CLUSTER : --region=REGION) [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] [--auth-mode=AUTH_MODE] [--cross-cluster-replication-role=CROSS_CLUSTER_REPLICATION_ROLE] [--deletion-protection] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] - [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [--network=NETWORK] [--node-type=NODE_TYPE] [--persistence-mode=PERSISTENCE_MODE] [--primary-cluster=PRIMARY_CLUSTER] [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] @@ -82,14 +82,7 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property redis/region. -REQUIRED FLAGS - --network=NETWORK - The network used to create your instance. It must use the format: - projects/NETWORK_PROJECT_ID/global/networks/NETWORK_ID. The network ID - used here must match the network ID used by the service connection - policy. Otherwise, the create operation fails - -OPTIONAL FLAGS +FLAGS --aof-append-fsync=AOF_APPEND_FSYNC Fsync configuration. AOF_APPEND_FSYNC must be one of: @@ -136,6 +129,12 @@ OPTIONAL FLAGS Hour of day (0 to 23) for the start of maintenance window, in UTC time zone. + --network=NETWORK + The network used to create your instance. It must use the format: + projects/NETWORK_PROJECT_ID/global/networks/NETWORK_ID. The network ID + used here must match the network ID used by the service connection + policy. Otherwise, the create operation fails + --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, diff --git a/gcloud/run/deploy b/gcloud/run/deploy index cfe96deee..d9c3872f2 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -2,13 +2,30 @@ NAME gcloud run deploy - create or update a Cloud Run service SYNOPSIS - gcloud run deploy [[SERVICE] --namespace=NAMESPACE] [--async] - [--concurrency=CONCURRENCY] [--container=CONTAINER] - [--ingress=INGRESS; default="all"] [--max-instances=MAX_INSTANCES] - [--min-instances=MIN_INSTANCES] - [--platform=PLATFORM; default="managed"] - [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] - [--no-traffic] + gcloud run deploy [[SERVICE] --namespace=NAMESPACE] + [--[no-]allow-unauthenticated] [--async] [--breakglass=JUSTIFICATION] + [--clear-vpc-connector] [--concurrency=CONCURRENCY] + [--container=CONTAINER] [--[no-]cpu-boost] [--[no-]cpu-throttling] + [--description=DESCRIPTION] + [--execution-environment=EXECUTION_ENVIRONMENT] + [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] + [--max-instances=MAX_INSTANCES] [--min-instances=MIN_INSTANCES] + [--region=REGION] [--remove-containers=[CONTAINER,...]] + [--revision-suffix=REVISION_SUFFIX] [--service-account=SERVICE_ACCOUNT] + [--service-min-instances=SERVICE_MIN_INSTANCES] + [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] + [--no-traffic] [--vpc-connector=VPC_CONNECTOR] + [--vpc-egress=VPC_EGRESS] + [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --clear-cloudsql-instances + | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--add-custom-audiences=[CUSTOM-AUDIENCES,...] + | --clear-custom-audiences + | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + | --set-custom-audiences=[CUSTOM-AUDIENCES,...]] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] --cpu=CPU --depends-on=[CONTAINER,...] --memory=MEMORY --port=PORT @@ -18,38 +35,21 @@ SYNOPSIS --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...] --image=IMAGE | --source=SOURCE] + [--binary-authorization=POLICY | --clear-binary-authorization] + [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] + | --remove-config-maps=[KEY,...] + --update-config-maps=[KEY=VALUE,...]] + [--clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] + [--clear-key | --key=KEY] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] - [--connectivity=CONNECTIVITY --clear-config-maps - | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] - [--[no-]allow-unauthenticated --breakglass=JUSTIFICATION - --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling - --description=DESCRIPTION - --execution-environment=EXECUTION_ENVIRONMENT - --[no-]invoker-iam-check --remove-containers=[CONTAINER,...] - --revision-suffix=REVISION_SUFFIX - --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity - --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --clear-cloudsql-instances - | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - | --clear-custom-audiences - | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --add-volume=[KEY=VALUE,...] --clear-volumes - --remove-volume=[VOLUME,...] --binary-authorization=POLICY - | --clear-binary-authorization --clear-encryption-key-shutdown-hours - | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - --clear-key | --key=KEY --clear-network + [--clear-network | --network=NETWORK --subnet=SUBNET --clear-network-tags - | --network-tags=[TAG,...] --clear-post-key-revocation-action-type + | --network-tags=[TAG,...]] + [--clear-post-key-revocation-action-type | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Creates or updates a Cloud Run service. @@ -98,10 +98,25 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS + --[no-]allow-unauthenticated + Whether to enable allowing unauthenticated access to the service. This + may take a few moments to take effect. Use --allow-unauthenticated to + enable and --no-allow-unauthenticated to disable. + --async Return immediately, without waiting for the operation in progress to complete. + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. + + --clear-vpc-connector + Remove the VPC connector for this resource. + --concurrency=CONCURRENCY Set the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified or provide the special value @@ -111,29 +126,55 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + --[no-]cpu-boost + Whether to allocate extra CPU to containers on startup to reduce the + perceived latency of a cold start request. Enabled by default when + unspecified on new services. Use --cpu-boost to enable and + --no-cpu-boost to disable. + + --[no-]cpu-throttling + Whether to throttle the CPU when the container is not actively serving + requests. Use --cpu-throttling to enable and --no-cpu-throttling to + disable. + + --description=DESCRIPTION + Provides an optional, human-readable description of the service. + + --execution-environment=EXECUTION_ENVIRONMENT + Selects the execution environment where the application will run. + EXECUTION_ENVIRONMENT must be one of: + + gen1 + Run the application in a first generation execution environment. + gen2 + Run the application in a second generation execution environment. + --ingress=INGRESS; default="all" Set the ingress traffic sources allowed to call the service. For Cloud - Run (fully managed) the --[no-]allow-unauthenticated flag separately - controls the identities allowed to call the service. INGRESS must be - one of: + Run the --[no-]allow-unauthenticated flag separately controls the + identities allowed to call the service. INGRESS must be one of: all Inbound requests from all sources are allowed. internal - For Cloud Run (fully managed), only inbound requests from VPC - networks in the same project or VPC Service Controls perimeter, as - well as Pub/Sub subscriptions and Eventarc events in the same - project or VPC Service Controls perimeter are allowed. All other - requests are rejected. See - https://cloud.google.com/run/docs/securing/ingress for full details - on the definition of internal traffic for Cloud Run (fully - managed). For Cloud Run for Anthos, only inbound requests from the - same cluster are allowed. + For Cloud Run, only inbound requests from VPC networks in the same + project or VPC Service Controls perimeter, as well as Pub/Sub + subscriptions and Eventarc events in the same project or VPC + Service Controls perimeter are allowed. All other requests are + rejected. See https://cloud.google.com/run/docs/securing/ingress + for full details on the definition of internal traffic for Cloud + Run. internal-and-cloud-load-balancing - Only supported for Cloud Run (fully managed). Only inbound requests - from Google Cloud Load Balancing or a traffic source allowed by the - internal option are allowed. + Only inbound requests from Google Cloud Load Balancing or a traffic + source allowed by the internal option are allowed. + + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. --max-instances=MAX_INSTANCES The maximum number of container instances of the Service to run. Use @@ -143,32 +184,33 @@ FLAGS The minimum number of container instances for this Revision of the Service to run or 'default' to remove any minimum. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --remove-containers=[CONTAINER,...] + List of containers to remove. + + --revision-suffix=REVISION_SUFFIX + Specify the suffix of the revision name. Revision names always start + with the service name automatically. For example, specifying + [--revision-suffix=v1] for a service named 'helloworld', would lead to + a revision named 'helloworld-v1'. Set empty string to clear the suffix + and resume server-assigned naming. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. For the managed platform, - this is the email address of an IAM service account. For the - Kubernetes-based platforms (gke, kubernetes), this is the name of a - Kubernetes service account in the same namespace as the service. If not - provided, the revision will use the default service account of the - project, or default Kubernetes namespace service account respectively. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. + + --service-min-instances=SERVICE_MIN_INSTANCES + The minimum number of container instances for this Service to run or + 'default' to remove any minimum. These instances will be divided among + all Revisions receiving a percentage of traffic. + + --[no-]session-affinity + Whether to enable session affinity for connections to the service. Use + --session-affinity to enable and --no-session-affinity to disable. --tag=TAG Traffic tag to assign to the newly created revision. @@ -190,6 +232,99 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. + --vpc-connector=VPC_CONNECTOR + Set a VPC connector for this resource. + + --vpc-egress=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 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 Direct VPC egress or the VPC + connector. + private-ranges-only + 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 + region as your Cloud Run service; otherwise specify + :: for the instance. + + At most one of these can be specified: + + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Append the given values to the current Cloud SQL instances. + + --clear-cloudsql-instances + Empty the current Cloud SQL instances. + + --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Remove the given values from the current Cloud SQL instances. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Completely replace the current Cloud SQL instances with the given + values. + + These flags modify the custom audiences that can be used in the audience + field of ID token for authenticated requests. + + At most one of these can be specified: + + --add-custom-audiences=[CUSTOM-AUDIENCES,...] + Append the given values to the current custom audiences. + + --clear-custom-audiences + Empty the current custom audiences. + + --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + Remove the given values from the current custom audiences. + + --set-custom-audiences=[CUSTOM-AUDIENCES,...] + Completely replace the current custom audiences with the given + values. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + Container Flags The following flags apply to a single container. If the --container flag is specified these flags may only be @@ -219,12 +354,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. @@ -306,7 +437,7 @@ FLAGS --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/hello:latest). --source=SOURCE The location of the source to build. If a Dockerfile is present @@ -324,6 +455,63 @@ FLAGS global .gitignore is not respected. For more information on .gcloudignore, see gcloud topic gcloudignore. + At most one of these can be specified: + + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". + + --clear-binary-authorization + Remove any previously set Binary Authorization policy. + + Specify config map to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. The values associated with each of + these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may + omit the key within the config map to specify a mount of all keys within + the config map. For example: + '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will + create a volume with config map 'myconfig' and mount that volume at + '/my/path'. Because no config map key was specified, all keys in + 'myconfig' will be included. An environment variable named ENV will also + be created whose value is the value of 'key.json' in 'otherconfig. Not + supported on the fully managed version of Cloud Run. + + At most one of these can be specified: + + --clear-config-maps + Remove all config-maps. + + --set-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. All existing + config-maps will be removed first. + + Only --update-config-maps and --remove-config-maps can be used together. + If both are specified, --remove-config-maps will be applied first. + + --remove-config-maps=[KEY,...] + List of config-maps to be removed. + + --update-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. + + At most one of these can be specified: + + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. + + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server after + CMEK key revocation is detected. + + At most one of these can be specified: + + --clear-key + Remove any previously set CMEK key reference. + + --key=KEY + CMEK key reference to encrypt the container with. + At most one of these can be specified: --clear-labels @@ -354,355 +542,53 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - --connectivity=CONNECTIVITY - (DEPRECATED) Defaults to 'external'. If 'external', the service can - be invoked through the internet, in addition to through the cluster - network. - - The --connectivity flag is deprecated but will continue to be - supported. Prefer to use the --ingress flag instead. CONNECTIVITY - must be one of: - - external - Visible from outside the cluster. - internal - Visible only within the cluster. - - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. - - At most one of these can be specified: - - --clear-config-maps - Remove all config-maps. - - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used - together. If both are specified, --remove-config-maps will be applied - first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --[no-]allow-unauthenticated - Whether to enable allowing unauthenticated access to the service. - This may take a few moments to take effect. Use - --allow-unauthenticated to enable and --no-allow-unauthenticated to - disable. - - --breakglass=JUSTIFICATION - Justification to bypass Binary Authorization policy constraints and - allow the operation. See - https://cloud.google.com/binary-authorization/docs/using-breakglass - for more information. Next update or deploy command will - automatically clear existing breakglass justification. - - --clear-vpc-connector - Remove the VPC connector for this resource. - - --[no-]cpu-boost - Whether to allocate extra CPU to containers on startup to reduce the - perceived latency of a cold start request. Enabled by default when - unspecified on new services. Use --cpu-boost to enable and - --no-cpu-boost to disable. - - --[no-]cpu-throttling - Whether to throttle the CPU when the container is not actively - serving requests. Use --cpu-throttling to enable and - --no-cpu-throttling to disable. - - --description=DESCRIPTION - Provides an optional, human-readable description of the service. - - --execution-environment=EXECUTION_ENVIRONMENT - Selects the execution environment where the application will run. - EXECUTION_ENVIRONMENT must be one of: - - gen1 - Run the application in a first generation execution environment. - gen2 - Run the application in a second generation execution environment. - - --[no-]invoker-iam-check - Optionally disable invoker IAM checks. This feature is available by - invitation only. More info at - https://cloud.google.com/run/docs/securing/managing-access#invoker_check. - Use --invoker-iam-check to enable and --no-invoker-iam-check to - disable. - - --remove-containers=[CONTAINER,...] - List of containers to remove. - - --revision-suffix=REVISION_SUFFIX - Specify the suffix of the revision name. Revision names always start - with the service name automatically. For example, specifying - [--revision-suffix=v1] for a service named 'helloworld', would lead - to a revision named 'helloworld-v1'. Set empty string to clear the - suffix and resume server-assigned naming. - - --service-min-instances=SERVICE_MIN_INSTANCES - The minimum number of container instances for this Service to run or - 'default' to remove any minimum. These instances will be divided - among all Revisions receiving a percentage of traffic. - - --[no-]session-affinity - Whether to enable session affinity for connections to the service. - Use --session-affinity to enable and --no-session-affinity to - disable. - - --vpc-connector=VPC_CONNECTOR - Set a VPC connector for this resource. - - --vpc-egress=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 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 Direct VPC egress or the VPC - connector. - private-ranges-only - 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 region as your Cloud Run service; otherwise specify - :: for the instance. - - At most one of these can be specified: - - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Append the given values to the current Cloud SQL instances. - - --clear-cloudsql-instances - Empty the current Cloud SQL instances. - - --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Remove the given values from the current Cloud SQL instances. - - --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Completely replace the current Cloud SQL instances with the given - values. - - These flags modify the custom audiences that can be used in the audience - field of ID token for authenticated requests. - - At most one of these can be specified: - - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - Append the given values to the current custom audiences. - - --clear-custom-audiences - Empty the current custom audiences. - - --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - Remove the given values from the current custom audiences. - - --set-custom-audiences=[CUSTOM-AUDIENCES,...] - Completely replace the current custom audiences with the given - values. - - --add-volume=[KEY=VALUE,...] - Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: - - cloud-storage: A volume representing a Cloud Storage bucket. This - volume type is mounted using Cloud Storage FUSE. See - https://cloud.google.com/storage/docs/gcs-fuse for the details and - limitations of this filesystem. Additional keys: - ◆ bucket: (required) the name of the bucket to use as the source of - this volume - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - - nfs: Represents a volume backed by an NFS server. Additional keys: - ◆ location: (required) The location of the NFS Server, in the form - SERVER:/PATH - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - - --clear-volumes - Remove all existing volumes from the Cloud Run resource, including - volumes mounted as secrets - - --remove-volume=[VOLUME,...] - Removes volumes from the Cloud Run resource. - - At most one of these can be specified: - - --binary-authorization=POLICY - Binary Authorization policy to check against. This must be set to - "default". - - --clear-binary-authorization - Remove any previously set Binary Authorization policy. - - At most one of these can be specified: - - --clear-encryption-key-shutdown-hours - Remove any previously set CMEK key shutdown hours setting. - - --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - The number of hours to wait before an automatic shutdown server - after CMEK key revocation is detected. - - At most one of these can be specified: - - --clear-key - Remove any previously set CMEK key reference. - - --key=KEY - CMEK key reference to encrypt the container with. - - At most one of these can be specified: - - --clear-network - Disconnect this Cloud Run service from the VPC network it is - connected to. - - Direct VPC egress setting flags group. - - --network=NETWORK - The VPC network that the Cloud Run service will be able to send - traffic to. If --subnet is also specified, subnet must be a - subnetwork of the network specified by this --network flag. To - clear existing VPC network settings, use --clear-network. - - --subnet=SUBNET - The VPC subnetwork that the Cloud Run service will get IPs from. - The subnetwork must be /26 or larger. If --network is also - specified, subnet must be a subnetwork of the network specified - by the --network flag. If --network is not specified, network - will be looked up from this subnetwork. To clear existing VPC - network settings, use --clear-network. - - At most one of these can be specified: - - --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. - - --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. - - At most one of these can be specified: - - --clear-post-key-revocation-action-type - Remove any previously set post CMEK key revocation action type. - - --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE - Action type after CMEK key revocation. - POST_KEY_REVOCATION_ACTION_TYPE must be one of: - - prevent-new - No new instances will be started after CMEK key revocation. - shut-down - No new instances will be started and the existing instances - will be shut down after CMEK key revocation. - - Arguments to locate resources, depending on the platform used. + At most one of these can be specified: + + --clear-network + Disconnect this Cloud Run service from the VPC network it is + connected to. + + Direct VPC egress setting flags group. + + --network=NETWORK + The VPC network that the Cloud Run service will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. + + --subnet=SUBNET + The VPC subnetwork that the Cloud Run service will get IPs from. + The subnetwork must be /26 or larger. If --network is also + specified, subnet must be a subnetwork of the network specified by + the --network flag. If --network is not specified, network will be + looked up from this subnetwork. To clear existing VPC network + settings, use --clear-network. + + At most one of these can be specified: + + --clear-network-tags + Clears all existing Compute Engine tags from the Cloud Run + service. + + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. To clear existing tags, use + --clear-network-tags. At most one of these can be specified: - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. + --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE + Action type after CMEK key revocation. + POST_KEY_REVOCATION_ACTION_TYPE must be one of: - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▸ set the property run/cluster with a fully specified name; - ▸ specify the cluster from a list of available clusters with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the - cluster. - - To set the cluster attribute: - ▫ provide the argument --cluster on the command line; - ▫ set the property run/cluster; - ▫ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ▫ provide the argument --cluster on the command line with a - fully specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --cluster-location on the command line; - ▫ set the property run/cluster_location; - ▫ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + prevent-new + No new instances will be started after CMEK key revocation. + shut-down + No new instances will be started and the existing instances will + be shut down after CMEK key revocation. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/run/domain-mappings/create b/gcloud/run/domain-mappings/create index 05683dab2..1474f0242 100644 --- a/gcloud/run/domain-mappings/create +++ b/gcloud/run/domain-mappings/create @@ -5,9 +5,7 @@ NAME SYNOPSIS gcloud run domain-mappings create --service=SERVICE (--domain=DOMAIN : --namespace=NAMESPACE) [--force-override] - [--platform=PLATFORM; default="managed"] - [--cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create domain mappings for Cloud Run for Anthos. @@ -59,78 +57,6 @@ OPTIONAL FLAGS --force-override Map this domain even if it is already mapped to another service. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Not supported by this command. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - 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/run/domain-mappings/delete b/gcloud/run/domain-mappings/delete index 64f372eda..47333e41d 100644 --- a/gcloud/run/domain-mappings/delete +++ b/gcloud/run/domain-mappings/delete @@ -4,9 +4,7 @@ NAME SYNOPSIS gcloud run domain-mappings delete (--domain=DOMAIN : --namespace=NAMESPACE) - [--[no-]async] [--platform=PLATFORM; default="managed"] - [--cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--[no-]async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Delete domain mappings for Cloud Run for Anthos. @@ -53,82 +51,9 @@ REQUIRED FLAGS OPTIONAL FLAGS --[no-]async Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async for Cloud Run (fully managed) and - --async for Cloud Run for Anthos. Use --async to enable and --no-async + complete. Defaults to --no-async. Use --async to enable and --no-async to disable. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Not supported by this command. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - 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/run/domain-mappings/describe b/gcloud/run/domain-mappings/describe index ccdfc054b..5b3810c1a 100644 --- a/gcloud/run/domain-mappings/describe +++ b/gcloud/run/domain-mappings/describe @@ -4,10 +4,7 @@ NAME SYNOPSIS gcloud run domain-mappings describe - (--domain=DOMAIN : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] - [--cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + (--domain=DOMAIN : --namespace=NAMESPACE) [GCLOUD_WIDE_FLAG ...] DESCRIPTION Describe domain mappings for Cloud Run for Anthos. @@ -51,79 +48,6 @@ REQUIRED FLAGS ▸ provide the argument project on the command line; ▸ set the property core/project. -OPTIONAL FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Not supported by this command. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - 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/run/domain-mappings/help b/gcloud/run/domain-mappings/help index 9b9d0a809..13925b115 100644 --- a/gcloud/run/domain-mappings/help +++ b/gcloud/run/domain-mappings/help @@ -3,9 +3,7 @@ NAME domain mappings SYNOPSIS - gcloud run domain-mappings COMMAND [--platform=PLATFORM; default="managed"] - [--cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud run domain-mappings COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION This set of commands can be used to view and manage your service's domain @@ -19,79 +17,6 @@ EXAMPLES $ gcloud run domain-mappings list -FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Not supported by this command. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/run/domain-mappings/list b/gcloud/run/domain-mappings/list index deb2ad608..26f3778d2 100644 --- a/gcloud/run/domain-mappings/list +++ b/gcloud/run/domain-mappings/list @@ -4,11 +4,8 @@ NAME SYNOPSIS gcloud run domain-mappings list [--namespace=NAMESPACE] - [--platform=PLATFORM; default="managed"] - [--cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Lists domain mappings for Cloud Run for Anthos. @@ -22,96 +19,19 @@ EXAMPLES $ gcloud run domain-mappings list FLAGS - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: + Namespace resource - Namespace to list domain mappings in. This represents + a Cloud resource. - Namespace resource - Namespace to list domain mappings in. This - represents a Cloud resource. + --namespace=NAMESPACE + ID of the namespace or fully qualified identifier for the namespace. - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Not supported by this command. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + To set the namespace attribute: + ▸ provide the argument --namespace on the command line; + ▸ set the property run/namespace; + ▸ For Cloud Run on Kubernetes Engine, defaults to "default". + Otherwise, defaults to project ID.; + ▸ provide the argument project on the command line; + ▸ set the property core/project. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/run/jobs/create b/gcloud/run/jobs/create index 879806aa6..8d0857706 100644 --- a/gcloud/run/jobs/create +++ b/gcloud/run/jobs/create @@ -86,9 +86,8 @@ OPTIONAL FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m + Cloud Run supports values fractional values below 1, 1, 2, 4, and 8. + Some CPU values requires a minimum Memory --memory value. --key=KEY CMEK key reference to encrypt the container with. @@ -113,10 +112,9 @@ OPTIONAL FLAGS property [run/region]. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. This is the email address - of an IAM service account. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] You can specify a name of a Cloud SQL instance if it's in the same diff --git a/gcloud/run/jobs/deploy b/gcloud/run/jobs/deploy index 7021d20c7..77a92eaf9 100644 --- a/gcloud/run/jobs/deploy +++ b/gcloud/run/jobs/deploy @@ -85,9 +85,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m + Cloud Run supports values fractional values below 1, 1, 2, 4, and 8. + Some CPU values requires a minimum Memory --memory value. --key=KEY CMEK key reference to encrypt the container with. @@ -112,10 +111,9 @@ FLAGS property [run/region]. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. This is the email address - of an IAM service account. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] You can specify a name of a Cloud SQL instance if it's in the same diff --git a/gcloud/run/jobs/update b/gcloud/run/jobs/update index 3f3010e3c..1fa8cfed4 100644 --- a/gcloud/run/jobs/update +++ b/gcloud/run/jobs/update @@ -86,9 +86,8 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m + Cloud Run supports values fractional values below 1, 1, 2, 4, and 8. + Some CPU values requires a minimum Memory --memory value. --image=IMAGE Name of the container image to deploy (e.g. @@ -114,10 +113,9 @@ FLAGS property [run/region]. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. This is the email address - of an IAM service account. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. --task-timeout=TASK_TIMEOUT Set the maximum time (deadline) a job task attempt can run for. In the diff --git a/gcloud/run/regions/help b/gcloud/run/regions/help index 169558198..64950578d 100644 --- a/gcloud/run/regions/help +++ b/gcloud/run/regions/help @@ -2,27 +2,11 @@ NAME gcloud run regions - view available Cloud Run (fully managed) regions SYNOPSIS - gcloud run regions COMMAND [--platform=PLATFORM; default="managed"] - [GCLOUD_WIDE_FLAG ...] + gcloud run regions COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION View available Cloud Run (fully managed) regions. -FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Not supported by this - command. - kubernetes - Use a Knative-compatible kubernetes cluster. Not supported by this - command. - GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/run/regions/list b/gcloud/run/regions/list index 4018ac877..2c4956036 100644 --- a/gcloud/run/regions/list +++ b/gcloud/run/regions/list @@ -2,9 +2,9 @@ NAME gcloud run regions list - list available Cloud Run (fully managed) regions SYNOPSIS - gcloud run regions list [--platform=PLATFORM; default="managed"] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + gcloud run regions list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION List available Cloud Run (fully managed) regions. @@ -14,21 +14,6 @@ EXAMPLES $ gcloud run regions list -FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Not supported by this - command. - kubernetes - Use a Knative-compatible kubernetes cluster. Not supported by this - command. - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/run/revisions/delete b/gcloud/run/revisions/delete index 25e22c4b6..d7944e739 100644 --- a/gcloud/run/revisions/delete +++ b/gcloud/run/revisions/delete @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud run revisions delete (REVISION : --namespace=NAMESPACE) - [--[no-]async] [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--[no-]async] [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Delete a revision. @@ -48,89 +45,12 @@ POSITIONAL ARGUMENTS FLAGS --[no-]async Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async for Cloud Run (fully managed) and - --async for Cloud Run for Anthos. Use --async to enable and --no-async + complete. Defaults to --no-async. Use --async to enable and --no-async to disable. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/run/revisions/describe b/gcloud/run/revisions/describe index 534c4463c..b980213f1 100644 --- a/gcloud/run/revisions/describe +++ b/gcloud/run/revisions/describe @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud run revisions describe (REVISION : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Obtain details about revisions. @@ -46,85 +43,9 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/run/revisions/help b/gcloud/run/revisions/help index e951aff70..ed9825e23 100644 --- a/gcloud/run/revisions/help +++ b/gcloud/run/revisions/help @@ -2,10 +2,7 @@ NAME gcloud run revisions - view and manage your Cloud Run revisions SYNOPSIS - gcloud run revisions COMMAND [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud run revisions COMMAND [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This set of commands can be used to view and manage your existing Cloud Run @@ -17,85 +14,9 @@ EXAMPLES $ gcloud run revisions list FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/run/revisions/list b/gcloud/run/revisions/list index ea1480d87..30822f651 100644 --- a/gcloud/run/revisions/list +++ b/gcloud/run/revisions/list @@ -2,13 +2,9 @@ NAME gcloud run revisions list - list available revisions SYNOPSIS - gcloud run revisions list [--namespace=NAMESPACE] - [--platform=PLATFORM; default="managed"] [--service=SERVICE] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud run revisions list [--region=REGION] [--service=SERVICE] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION List available revisions. @@ -19,108 +15,13 @@ EXAMPLES $ gcloud run revisions list --service=foo FLAGS - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to list revisions in. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. --service=SERVICE Limit matched revisions to the given service. - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/run/services/add-iam-policy-binding b/gcloud/run/services/add-iam-policy-binding index b56a3d827..c777fdfcd 100644 --- a/gcloud/run/services/add-iam-policy-binding +++ b/gcloud/run/services/add-iam-policy-binding @@ -4,10 +4,7 @@ NAME SYNOPSIS gcloud run services add-iam-policy-binding SERVICE --member=PRINCIPAL - --role=ROLE [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + --role=ROLE [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Add an IAM policy binding to the IAM policy of a Cloud Run service. One @@ -73,85 +70,9 @@ REQUIRED FLAGS organizations/{ORGANIZATION_ID}/roles/logging.viewer. OPTIONAL FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/run/services/delete b/gcloud/run/services/delete index 2c8897f09..f6d3fa92f 100644 --- a/gcloud/run/services/delete +++ b/gcloud/run/services/delete @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud run services delete (SERVICE : --namespace=NAMESPACE) [--[no-]async] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Delete a service. @@ -48,89 +45,12 @@ POSITIONAL ARGUMENTS FLAGS --[no-]async Return immediately, without waiting for the operation in progress to - complete. Defaults to --no-async for Cloud Run (fully managed) and - --async for Cloud Run for Anthos. Use --async to enable and --no-async + complete. Defaults to --no-async. Use --async to enable and --no-async to disable. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/run/services/describe b/gcloud/run/services/describe index dc8306475..17b705212 100644 --- a/gcloud/run/services/describe +++ b/gcloud/run/services/describe @@ -3,10 +3,7 @@ NAME SYNOPSIS gcloud run services describe (SERVICE : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Obtain details about a given service. @@ -55,85 +52,9 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/run/services/get-iam-policy b/gcloud/run/services/get-iam-policy index 30bdbb794..f27281930 100644 --- a/gcloud/run/services/get-iam-policy +++ b/gcloud/run/services/get-iam-policy @@ -3,13 +3,9 @@ NAME service SYNOPSIS - gcloud run services get-iam-policy SERVICE - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + gcloud run services get-iam-policy SERVICE [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command gets the IAM policy for a service. If formatted as JSON, the @@ -50,85 +46,9 @@ POSITIONAL ARGUMENTS ▸ provide the argument service on the command line. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/run/services/help b/gcloud/run/services/help index a8dd73bd6..351526c60 100644 --- a/gcloud/run/services/help +++ b/gcloud/run/services/help @@ -2,11 +2,8 @@ NAME gcloud run services - view and manage your Cloud Run services SYNOPSIS - gcloud run services GROUP | COMMAND - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud run services GROUP | COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This set of commands can be used to view and manage your existing Cloud Run @@ -20,85 +17,9 @@ EXAMPLES $ gcloud run services list FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/run/services/list b/gcloud/run/services/list index e509351e9..c7c547cd4 100644 --- a/gcloud/run/services/list +++ b/gcloud/run/services/list @@ -2,11 +2,7 @@ NAME gcloud run services list - list available services SYNOPSIS - gcloud run services list [--namespace=NAMESPACE] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION] + gcloud run services list [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -19,104 +15,9 @@ EXAMPLES $ gcloud run services list FLAGS - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to list services in. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/run/services/logs/help b/gcloud/run/services/logs/help index 8429e960f..7f71fd64d 100644 --- a/gcloud/run/services/logs/help +++ b/gcloud/run/services/logs/help @@ -2,94 +2,15 @@ NAME gcloud run services logs - read logs for Cloud Run services SYNOPSIS - gcloud run services logs COMMAND [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud run services logs COMMAND [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Read logs for Cloud Run services. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/run/services/logs/read b/gcloud/run/services/logs/read index 7f45c9f3b..89c75f01f 100644 --- a/gcloud/run/services/logs/read +++ b/gcloud/run/services/logs/read @@ -4,11 +4,7 @@ NAME SYNOPSIS gcloud run services logs read SERVICE [--freshness=FRESHNESS; default="1d"] [--log-filter=LOG_FILTER] [--order=ORDER; default="desc"] - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--limit=LIMIT] - [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [--limit=LIMIT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud run services logs read reads log entries. Log entries matching @@ -60,85 +56,9 @@ FLAGS Ordering of returned log entries based on timestamp field. ORDER must be one of: desc, asc. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. LIST COMMAND FLAGS --limit=LIMIT diff --git a/gcloud/run/services/proxy b/gcloud/run/services/proxy index 69a272695..8656d9a0e 100644 --- a/gcloud/run/services/proxy +++ b/gcloud/run/services/proxy @@ -3,12 +3,8 @@ NAME the active account or with the specified token SYNOPSIS - gcloud run services proxy (SERVICE : --namespace=NAMESPACE) - [--platform=PLATFORM; default="managed"] [--port=PORT] [--tag=TAG] - [--token=TOKEN] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud run services proxy (SERVICE : --namespace=NAMESPACE) [--port=PORT] + [--region=REGION] [--tag=TAG] [--token=TOKEN] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Runs a server on localhost that proxies requests to the specified Cloud Run @@ -60,27 +56,14 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - --port=PORT Local port number to expose the proxied service. If not specified, it will be set to 8080. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + --tag=TAG Traffic tag of the service to expose via the proxy. If not specified, the default service URL will be proxied which may serve different @@ -94,69 +77,6 @@ FLAGS authenticated account will be used (e.g. gcloud auth print-identity-token). - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - 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/run/services/remove-iam-policy-binding b/gcloud/run/services/remove-iam-policy-binding index aba8b5ec2..7c8bafcc8 100644 --- a/gcloud/run/services/remove-iam-policy-binding +++ b/gcloud/run/services/remove-iam-policy-binding @@ -4,10 +4,7 @@ NAME SYNOPSIS gcloud run services remove-iam-policy-binding SERVICE --member=PRINCIPAL - --role=ROLE [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + --role=ROLE [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Remove an IAM policy binding from the IAM policy of a service. One binding @@ -74,85 +71,9 @@ REQUIRED FLAGS The role to remove the principal from. OPTIONAL FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/run/services/replace b/gcloud/run/services/replace index aeb781b7e..ade144431 100644 --- a/gcloud/run/services/replace +++ b/gcloud/run/services/replace @@ -3,11 +3,8 @@ NAME service specification SYNOPSIS - gcloud run services replace FILE [--async] [--dry-run] - [--namespace=NAMESPACE] [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud run services replace FILE [--async] [--dry-run] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Creates or replaces a service from a YAML service specification. @@ -31,104 +28,9 @@ FLAGS If set to true, only validates the configuration. The configuration will not be applied. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: - - Namespace resource - Namespace to replace service. This represents a - Cloud resource. - - --namespace=NAMESPACE - ID of the namespace or fully qualified identifier for the - namespace. - - To set the namespace attribute: - ▫ provide the argument --namespace on the command line; - ▫ set the property run/namespace; - ▫ For Cloud Run on Kubernetes Engine, defaults to "default". - Otherwise, defaults to project ID.; - ▫ provide the argument project on the command line; - ▫ set the property core/project. - - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/run/services/set-iam-policy b/gcloud/run/services/set-iam-policy index 1c81a79d9..e5f42c4e4 100644 --- a/gcloud/run/services/set-iam-policy +++ b/gcloud/run/services/set-iam-policy @@ -2,11 +2,8 @@ NAME gcloud run services set-iam-policy - set the IAM policy for a service SYNOPSIS - gcloud run services set-iam-policy SERVICE POLICY_FILE - [--platform=PLATFORM; default="managed"] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + gcloud run services set-iam-policy SERVICE POLICY_FILE [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command replaces the existing IAM policy for a service, given a @@ -61,85 +58,9 @@ POSITIONAL ARGUMENTS (https://cloud.google.com/iam/reference/rest/v1/Policy). FLAGS - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. - - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/run/services/update b/gcloud/run/services/update index 76a879721..f306d1fae 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -4,12 +4,27 @@ NAME SYNOPSIS gcloud run services update [[SERVICE] --namespace=NAMESPACE] [--async] - [--concurrency=CONCURRENCY] [--container=CONTAINER] - [--ingress=INGRESS; default="all"] [--max-instances=MAX_INSTANCES] - [--min-instances=MIN_INSTANCES] - [--platform=PLATFORM; default="managed"] - [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] - [--no-traffic] + [--breakglass=JUSTIFICATION] [--clear-vpc-connector] + [--concurrency=CONCURRENCY] [--container=CONTAINER] [--[no-]cpu-boost] + [--[no-]cpu-throttling] [--execution-environment=EXECUTION_ENVIRONMENT] + [--ingress=INGRESS; default="all"] [--[no-]invoker-iam-check] + [--max-instances=MAX_INSTANCES] [--min-instances=MIN_INSTANCES] + [--region=REGION] [--remove-containers=[CONTAINER,...]] + [--revision-suffix=REVISION_SUFFIX] [--service-account=SERVICE_ACCOUNT] + [--service-min-instances=SERVICE_MIN_INSTANCES] + [--[no-]session-affinity] [--tag=TAG] [--timeout=TIMEOUT] + [--no-traffic] [--vpc-connector=VPC_CONNECTOR] + [--vpc-egress=VPC_EGRESS] + [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --clear-cloudsql-instances + | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--add-custom-audiences=[CUSTOM-AUDIENCES,...] + | --clear-custom-audiences + | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + | --set-custom-audiences=[CUSTOM-AUDIENCES,...]] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE --memory=MEMORY @@ -19,36 +34,21 @@ SYNOPSIS --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] - [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost - --[no-]cpu-throttling --execution-environment=EXECUTION_ENVIRONMENT - --[no-]invoker-iam-check --remove-containers=[CONTAINER,...] - --revision-suffix=REVISION_SUFFIX - --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity - --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --clear-cloudsql-instances - | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - | --clear-custom-audiences - | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --add-volume=[KEY=VALUE,...] --clear-volumes - --remove-volume=[VOLUME,...] --binary-authorization=POLICY - | --clear-binary-authorization --clear-encryption-key-shutdown-hours - | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - --clear-key | --key=KEY --clear-network - | --network=NETWORK --subnet=SUBNET --clear-network-tags - | --network-tags=[TAG,...] --clear-post-key-revocation-action-type - | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [--binary-authorization=POLICY | --clear-binary-authorization] + [--clear-config-maps | --set-config-maps=[KEY=VALUE,...] + | --remove-config-maps=[KEY,...] + --update-config-maps=[KEY=VALUE,...]] + [--clear-encryption-key-shutdown-hours + | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS] + [--clear-key | --key=KEY] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] - [--connectivity=CONNECTIVITY --clear-config-maps - | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] - --update-config-maps=[KEY=VALUE,...]] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...] + [--clear-network + | --network=NETWORK --subnet=SUBNET --clear-network-tags + | --network-tags=[TAG,...]] + [--clear-post-key-revocation-action-type + | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update Cloud Run environment variables and other configuration settings. @@ -91,6 +91,16 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --breakglass=JUSTIFICATION + Justification to bypass Binary Authorization policy constraints and + allow the operation. See + https://cloud.google.com/binary-authorization/docs/using-breakglass for + more information. Next update or deploy command will automatically + clear existing breakglass justification. + + --clear-vpc-connector + Remove the VPC connector for this resource. + --concurrency=CONCURRENCY Set the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified or provide the special value @@ -100,29 +110,52 @@ FLAGS Specifies a container by name. Flags following --container will apply to the specified container. + --[no-]cpu-boost + Whether to allocate extra CPU to containers on startup to reduce the + perceived latency of a cold start request. Enabled by default when + unspecified on new services. Use --cpu-boost to enable and + --no-cpu-boost to disable. + + --[no-]cpu-throttling + Whether to throttle the CPU when the container is not actively serving + requests. Use --cpu-throttling to enable and --no-cpu-throttling to + disable. + + --execution-environment=EXECUTION_ENVIRONMENT + Selects the execution environment where the application will run. + EXECUTION_ENVIRONMENT must be one of: + + gen1 + Run the application in a first generation execution environment. + gen2 + Run the application in a second generation execution environment. + --ingress=INGRESS; default="all" Set the ingress traffic sources allowed to call the service. For Cloud - Run (fully managed) the --[no-]allow-unauthenticated flag separately - controls the identities allowed to call the service. INGRESS must be - one of: + Run the --[no-]allow-unauthenticated flag separately controls the + identities allowed to call the service. INGRESS must be one of: all Inbound requests from all sources are allowed. internal - For Cloud Run (fully managed), only inbound requests from VPC - networks in the same project or VPC Service Controls perimeter, as - well as Pub/Sub subscriptions and Eventarc events in the same - project or VPC Service Controls perimeter are allowed. All other - requests are rejected. See - https://cloud.google.com/run/docs/securing/ingress for full details - on the definition of internal traffic for Cloud Run (fully - managed). For Cloud Run for Anthos, only inbound requests from the - same cluster are allowed. + For Cloud Run, only inbound requests from VPC networks in the same + project or VPC Service Controls perimeter, as well as Pub/Sub + subscriptions and Eventarc events in the same project or VPC + Service Controls perimeter are allowed. All other requests are + rejected. See https://cloud.google.com/run/docs/securing/ingress + for full details on the definition of internal traffic for Cloud + Run. internal-and-cloud-load-balancing - Only supported for Cloud Run (fully managed). Only inbound requests - from Google Cloud Load Balancing or a traffic source allowed by the - internal option are allowed. + Only inbound requests from Google Cloud Load Balancing or a traffic + source allowed by the internal option are allowed. + + --[no-]invoker-iam-check + Optionally disable invoker IAM checks. This feature is available by + invitation only. More info at + https://cloud.google.com/run/docs/securing/managing-access#invoker_check. + Use --invoker-iam-check to enable and --no-invoker-iam-check to + disable. --max-instances=MAX_INSTANCES The maximum number of container instances of the Service to run. Use @@ -132,32 +165,33 @@ FLAGS The minimum number of container instances for this Revision of the Service to run or 'default' to remove any minimum. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --remove-containers=[CONTAINER,...] + List of containers to remove. + + --revision-suffix=REVISION_SUFFIX + Specify the suffix of the revision name. Revision names always start + with the service name automatically. For example, specifying + [--revision-suffix=v1] for a service named 'helloworld', would lead to + a revision named 'helloworld-v1'. Set empty string to clear the suffix + and resume server-assigned naming. --service-account=SERVICE_ACCOUNT - Service account associated with the revision of the service. The - service account represents the identity of the running revision, and - determines what permissions the revision has. For the managed platform, - this is the email address of an IAM service account. For the - Kubernetes-based platforms (gke, kubernetes), this is the name of a - Kubernetes service account in the same namespace as the service. If not - provided, the revision will use the default service account of the - project, or default Kubernetes namespace service account respectively. + the email address of an IAM service account associated with the + revision of the service. The service account represents the identity of + the running revision, and determines what permissions the revision has. + + --service-min-instances=SERVICE_MIN_INSTANCES + The minimum number of container instances for this Service to run or + 'default' to remove any minimum. These instances will be divided among + all Revisions receiving a percentage of traffic. + + --[no-]session-affinity + Whether to enable session affinity for connections to the service. Use + --session-affinity to enable and --no-session-affinity to disable. --tag=TAG Traffic tag to assign to the newly created revision. @@ -179,6 +213,99 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. + --vpc-connector=VPC_CONNECTOR + Set a VPC connector for this resource. + + --vpc-egress=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 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 Direct VPC egress or the VPC + connector. + private-ranges-only + 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 + region as your Cloud Run service; otherwise specify + :: for the instance. + + At most one of these can be specified: + + --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Append the given values to the current Cloud SQL instances. + + --clear-cloudsql-instances + Empty the current Cloud SQL instances. + + --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Remove the given values from the current Cloud SQL instances. + + --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] + Completely replace the current Cloud SQL instances with the given + values. + + These flags modify the custom audiences that can be used in the audience + field of ID token for authenticated requests. + + At most one of these can be specified: + + --add-custom-audiences=[CUSTOM-AUDIENCES,...] + Append the given values to the current custom audiences. + + --clear-custom-audiences + Empty the current custom audiences. + + --remove-custom-audiences=[CUSTOM-AUDIENCES,...] + Remove the given values from the current custom audiences. + + --set-custom-audiences=[CUSTOM-AUDIENCES,...] + Completely replace the current custom audiences with the given + values. + + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + Container Flags If the --container or --remove-containers flag is specified the following @@ -208,19 +335,15 @@ FLAGS --cpu=CPU Set a CPU limit in Kubernetes cpu units. - Cloud Run (fully managed) supports values 1, 2 and 4. For Cloud Run - (fully managed), 4 cpus also requires a minimum 2Gi --memory value. - Examples 2, 2.0, 2000m - - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Cloud Run supports values fractional values below 1, 1, 2, 4, and + 8. Some CPU values requires a minimum Memory --memory value. --depends-on=[CONTAINER,...] List of container dependencies to add to the current container. --image=IMAGE Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + us-docker.pkg.dev/cloudrun/container/hello:latest). --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. @@ -295,232 +418,62 @@ FLAGS --update-secrets=[KEY=VALUE,...] List of key-value pairs to set as secrets. - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + At most one of these can be specified: - --breakglass=JUSTIFICATION - Justification to bypass Binary Authorization policy constraints and - allow the operation. See - https://cloud.google.com/binary-authorization/docs/using-breakglass - for more information. Next update or deploy command will - automatically clear existing breakglass justification. + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". - --clear-vpc-connector - Remove the VPC connector for this resource. + --clear-binary-authorization + Remove any previously set Binary Authorization policy. - --[no-]cpu-boost - Whether to allocate extra CPU to containers on startup to reduce the - perceived latency of a cold start request. Enabled by default when - unspecified on new services. Use --cpu-boost to enable and - --no-cpu-boost to disable. + Specify config map to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. The values associated with each of + these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may + omit the key within the config map to specify a mount of all keys within + the config map. For example: + '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will + create a volume with config map 'myconfig' and mount that volume at + '/my/path'. Because no config map key was specified, all keys in + 'myconfig' will be included. An environment variable named ENV will also + be created whose value is the value of 'key.json' in 'otherconfig. Not + supported on the fully managed version of Cloud Run. - --[no-]cpu-throttling - Whether to throttle the CPU when the container is not actively - serving requests. Use --cpu-throttling to enable and - --no-cpu-throttling to disable. + At most one of these can be specified: - --execution-environment=EXECUTION_ENVIRONMENT - Selects the execution environment where the application will run. - EXECUTION_ENVIRONMENT must be one of: + --clear-config-maps + Remove all config-maps. - gen1 - Run the application in a first generation execution environment. - gen2 - Run the application in a second generation execution environment. + --set-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. All existing + config-maps will be removed first. - --[no-]invoker-iam-check - Optionally disable invoker IAM checks. This feature is available by - invitation only. More info at - https://cloud.google.com/run/docs/securing/managing-access#invoker_check. - Use --invoker-iam-check to enable and --no-invoker-iam-check to - disable. + Only --update-config-maps and --remove-config-maps can be used together. + If both are specified, --remove-config-maps will be applied first. - --remove-containers=[CONTAINER,...] - List of containers to remove. + --remove-config-maps=[KEY,...] + List of config-maps to be removed. - --revision-suffix=REVISION_SUFFIX - Specify the suffix of the revision name. Revision names always start - with the service name automatically. For example, specifying - [--revision-suffix=v1] for a service named 'helloworld', would lead - to a revision named 'helloworld-v1'. Set empty string to clear the - suffix and resume server-assigned naming. + --update-config-maps=[KEY=VALUE,...] + List of key-value pairs to set as config-maps. - --service-min-instances=SERVICE_MIN_INSTANCES - The minimum number of container instances for this Service to run or - 'default' to remove any minimum. These instances will be divided - among all Revisions receiving a percentage of traffic. + At most one of these can be specified: - --[no-]session-affinity - Whether to enable session affinity for connections to the service. - Use --session-affinity to enable and --no-session-affinity to - disable. + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. - --vpc-connector=VPC_CONNECTOR - Set a VPC connector for this resource. + --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS + The number of hours to wait before an automatic shutdown server after + CMEK key revocation is detected. - --vpc-egress=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: + At most one of these can be specified: - all - (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 Direct VPC egress or the VPC - connector. - private-ranges-only - Default option. Sends outbound traffic to private IP addresses - (RFC 1918 and Private Google Access IPs) through Direct VPC - egress or the VPC connector. + --clear-key + Remove any previously set CMEK key reference. - 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 region as your Cloud Run service; otherwise specify - :: for the instance. - - At most one of these can be specified: - - --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Append the given values to the current Cloud SQL instances. - - --clear-cloudsql-instances - Empty the current Cloud SQL instances. - - --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Remove the given values from the current Cloud SQL instances. - - --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...] - Completely replace the current Cloud SQL instances with the given - values. - - These flags modify the custom audiences that can be used in the audience - field of ID token for authenticated requests. - - At most one of these can be specified: - - --add-custom-audiences=[CUSTOM-AUDIENCES,...] - Append the given values to the current custom audiences. - - --clear-custom-audiences - Empty the current custom audiences. - - --remove-custom-audiences=[CUSTOM-AUDIENCES,...] - Remove the given values from the current custom audiences. - - --set-custom-audiences=[CUSTOM-AUDIENCES,...] - Completely replace the current custom audiences with the given - values. - - --add-volume=[KEY=VALUE,...] - Adds a volume to the Cloud Run resource. To add more than one volume, - specify this flag multiple times. Volumes must have a name and type - key. Only certain values are supported for type. Depending on the - provided type, other keys will be required. The following types are - supported with the specified additional keys: - - cloud-storage: A volume representing a Cloud Storage bucket. This - volume type is mounted using Cloud Storage FUSE. See - https://cloud.google.com/storage/docs/gcs-fuse for the details and - limitations of this filesystem. Additional keys: - ◆ bucket: (required) the name of the bucket to use as the source of - this volume - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - - nfs: Represents a volume backed by an NFS server. Additional keys: - ◆ location: (required) The location of the NFS Server, in the form - SERVER:/PATH - ◆ readonly: (optional) A boolean. If true, this volume will be - read-only from all mounts. - - --clear-volumes - Remove all existing volumes from the Cloud Run resource, including - volumes mounted as secrets - - --remove-volume=[VOLUME,...] - Removes volumes from the Cloud Run resource. - - At most one of these can be specified: - - --binary-authorization=POLICY - Binary Authorization policy to check against. This must be set to - "default". - - --clear-binary-authorization - Remove any previously set Binary Authorization policy. - - At most one of these can be specified: - - --clear-encryption-key-shutdown-hours - Remove any previously set CMEK key shutdown hours setting. - - --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS - The number of hours to wait before an automatic shutdown server - after CMEK key revocation is detected. - - At most one of these can be specified: - - --clear-key - Remove any previously set CMEK key reference. - - --key=KEY - CMEK key reference to encrypt the container with. - - At most one of these can be specified: - - --clear-network - Disconnect this Cloud Run service from the VPC network it is - connected to. - - Direct VPC egress setting flags group. - - --network=NETWORK - The VPC network that the Cloud Run service will be able to send - traffic to. If --subnet is also specified, subnet must be a - subnetwork of the network specified by this --network flag. To - clear existing VPC network settings, use --clear-network. - - --subnet=SUBNET - The VPC subnetwork that the Cloud Run service will get IPs from. - The subnetwork must be /26 or larger. If --network is also - specified, subnet must be a subnetwork of the network specified - by the --network flag. If --network is not specified, network - will be looked up from this subnetwork. To clear existing VPC - network settings, use --clear-network. - - At most one of these can be specified: - - --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. - - --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. - - At most one of these can be specified: - - --clear-post-key-revocation-action-type - Remove any previously set post CMEK key revocation action type. - - --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE - Action type after CMEK key revocation. - POST_KEY_REVOCATION_ACTION_TYPE must be one of: - - prevent-new - No new instances will be started after CMEK key revocation. - shut-down - No new instances will be started and the existing instances - will be shut down after CMEK key revocation. + --key=KEY + CMEK key reference to encrypt the container with. At most one of these can be specified: @@ -553,119 +506,53 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke - or --platform=kubernetes to use: + At most one of these can be specified: - --connectivity=CONNECTIVITY - (DEPRECATED) Defaults to 'external'. If 'external', the service can - be invoked through the internet, in addition to through the cluster - network. + --clear-network + Disconnect this Cloud Run service from the VPC network it is + connected to. - The --connectivity flag is deprecated but will continue to be - supported. Prefer to use the --ingress flag instead. CONNECTIVITY - must be one of: + Direct VPC egress setting flags group. - external - Visible from outside the cluster. - internal - Visible only within the cluster. + --network=NETWORK + The VPC network that the Cloud Run service will be able to send + traffic to. If --subnet is also specified, subnet must be a + subnetwork of the network specified by this --network flag. To + clear existing VPC network settings, use --clear-network. - Specify config map to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. The values associated with each of - these should be in the form CONFIG_MAP_NAME:KEY_IN_CONFIG_MAP; you may - omit the key within the config map to specify a mount of all keys within - the config map. For example: - '--update-config-maps=/my/path=myconfig,ENV=otherconfig:key.json' will - create a volume with config map 'myconfig' and mount that volume at - '/my/path'. Because no config map key was specified, all keys in - 'myconfig' will be included. An environment variable named ENV will also - be created whose value is the value of 'key.json' in 'otherconfig. Not - supported on the fully managed version of Cloud Run. + --subnet=SUBNET + The VPC subnetwork that the Cloud Run service will get IPs from. + The subnetwork must be /26 or larger. If --network is also + specified, subnet must be a subnetwork of the network specified by + the --network flag. If --network is not specified, network will be + looked up from this subnetwork. To clear existing VPC network + settings, use --clear-network. - At most one of these can be specified: + At most one of these can be specified: - --clear-config-maps - Remove all config-maps. + --clear-network-tags + Clears all existing Compute Engine tags from the Cloud Run + service. - --set-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. All existing - config-maps will be removed first. - - Only --update-config-maps and --remove-config-maps can be used - together. If both are specified, --remove-config-maps will be applied - first. - - --remove-config-maps=[KEY,...] - List of config-maps to be removed. - - --update-config-maps=[KEY=VALUE,...] - List of key-value pairs to set as config-maps. - - Arguments to locate resources, depending on the platform used. + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. To clear existing tags, use + --clear-network-tags. At most one of these can be specified: - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. + --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE + Action type after CMEK key revocation. + POST_KEY_REVOCATION_ACTION_TYPE must be one of: - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▸ set the property run/cluster with a fully specified name; - ▸ specify the cluster from a list of available clusters with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the - cluster. - - To set the cluster attribute: - ▫ provide the argument --cluster on the command line; - ▫ set the property run/cluster; - ▫ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ▫ provide the argument --cluster on the command line with a - fully specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --cluster-location on the command line; - ▫ set the property run/cluster_location; - ▫ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. + prevent-new + No new instances will be started after CMEK key revocation. + shut-down + No new instances will be started and the existing instances will + be shut down after CMEK key revocation. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/run/services/update-traffic b/gcloud/run/services/update-traffic index 5a676d94d..fc02cdce7 100644 --- a/gcloud/run/services/update-traffic +++ b/gcloud/run/services/update-traffic @@ -4,12 +4,9 @@ NAME SYNOPSIS gcloud run services update-traffic [[SERVICE] --namespace=NAMESPACE] - [--async] [--platform=PLATFORM; default="managed"] + [--async] [--region=REGION] [--clear-tags | --set-tags=[TAG=REVISION,...] | --remove-tags=[TAG,...] --update-tags=[TAG=REVISION,...]] - [--region=REGION - | --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION - | --context=CONTEXT --kubeconfig=KUBECONFIG] [--to-latest | --to-revisions=[REVISION-NAME=PERCENTAGE,...] | --to-tags=[TAG=PERCENTAGE,...]] [GCLOUD_WIDE_FLAG ...] @@ -77,22 +74,9 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. - --platform=PLATFORM; default="managed" - Target platform for running commands. Alternatively, set the property - [run/platform]. PLATFORM must be one of: - - managed - Fully managed version of Cloud Run. Use with the --region flag or - set the [run/region] property to specify a Cloud Run region. - gke - Cloud Run for Anthos on Google Cloud. Use with the --cluster and - --cluster-location flags or set the [run/cluster] and - [run/cluster_location] properties to specify a cluster in a given - zone. - kubernetes - Use a Knative-compatible kubernetes cluster. Use with the - --kubeconfig and --context flags to specify a kubeconfig file and - the context for connecting. + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. Specify traffic tags. Traffic tags can be assigned to a revision by name or to the latest ready revision. Assigning a tag to a revision generates a @@ -125,69 +109,6 @@ FLAGS --update-tags=[TAG=REVISION,...] List of key-value pairs to set as tags. - Arguments to locate resources, depending on the platform used. - - At most one of these can be specified: - - Only applicable if connecting to Cloud Run (fully managed). Specify - --platform=managed to use: - - --region=REGION - Region in which the resource can be found. Alternatively, set the - property [run/region]. - - Only applicable if connecting to Cloud Run for Anthos deployed on Google - Cloud. Specify --platform=gke to use: - - Cluster resource - Kubernetes Engine cluster to connect to. 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 --cluster on the command line with a fully - specified name; - ▫ set the property run/cluster with a fully specified name; - ▫ specify the cluster from a list of available clusters with a - fully specified name; - ▫ provide the argument --project on the command line; - ▫ set the property core/project. - - --cluster=CLUSTER - ID of the cluster or fully qualified identifier for the cluster. - - To set the cluster attribute: - ◇ provide the argument --cluster on the command line; - ◇ set the property run/cluster; - ◇ specify the cluster from a list of available clusters. - - --cluster-location=CLUSTER_LOCATION - Zone in which the cluster is located. Alternatively, set the - property [run/cluster_location]. - - To set the location attribute: - ◇ provide the argument --cluster on the command line with a - fully specified name; - ◇ set the property run/cluster with a fully specified name; - ◇ specify the cluster from a list of available clusters with a - fully specified name; - ◇ provide the argument --cluster-location on the command line; - ◇ set the property run/cluster_location; - ◇ specify the cluster location from a list of available zones. - - Only applicable if connecting to Cloud Run for Anthos deployed on - VMware. Specify --platform=kubernetes to use: - - --context=CONTEXT - The name of the context in your kubectl config file to use for - connecting. - - --kubeconfig=KUBECONFIG - The absolute path to your kubectl config file. If not specified, - the colon- or semicolon-delimited list of paths specified by - $KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to - ~/.kube/config. - At most one of these can be specified: --to-latest diff --git a/gcloud/spanner/backup-schedules/create b/gcloud/spanner/backup-schedules/create index 42c7ebc88..2a05c122d 100644 --- a/gcloud/spanner/backup-schedules/create +++ b/gcloud/spanner/backup-schedules/create @@ -7,8 +7,8 @@ SYNOPSIS (BACKUP_SCHEDULE : --database=DATABASE --instance=INSTANCE) --backup-type=[BACKUP_TYPE] --cron=CRON --retention-duration=RETENTION_DURATION - [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + [--encryption-type=ENCRYPTION_TYPE --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] @@ -111,6 +111,28 @@ OPTIONAL FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to create the Cloud Spanner + backup. 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 kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner backup. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/spanner/backup-schedules/update b/gcloud/spanner/backup-schedules/update index d75fd6671..70fa6718c 100644 --- a/gcloud/spanner/backup-schedules/update +++ b/gcloud/spanner/backup-schedules/update @@ -6,8 +6,8 @@ SYNOPSIS gcloud spanner backup-schedules update (BACKUP_SCHEDULE : --database=DATABASE --instance=INSTANCE) (--cron=CRON --encryption-type=ENCRYPTION_TYPE - --retention-duration=RETENTION_DURATION [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + --retention-duration=RETENTION_DURATION --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]) [GCLOUD_WIDE_FLAG ...] @@ -99,6 +99,28 @@ REQUIRED FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to create the Cloud Spanner + backup. 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 kms-project attribute: + ▫ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▫ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▫ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ◇ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner backup. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/spanner/backups/copy b/gcloud/spanner/backups/copy index c14062f06..23a715204 100644 --- a/gcloud/spanner/backups/copy +++ b/gcloud/spanner/backups/copy @@ -9,8 +9,8 @@ SYNOPSIS | --retention-period=RETENTION_PERIOD) (--source-backup=SOURCE_BACKUP : --source-instance=SOURCE_INSTANCE) [--async] - [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + [--encryption-type=ENCRYPTION_TYPE --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] @@ -131,6 +131,28 @@ OPTIONAL FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to copy the Cloud Spanner + backup. 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 kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to copy the Cloud Spanner backup. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/spanner/backups/create b/gcloud/spanner/backups/create index 5657a7aef..f7a98152e 100644 --- a/gcloud/spanner/backups/create +++ b/gcloud/spanner/backups/create @@ -8,8 +8,8 @@ SYNOPSIS (--expiration-date=EXPIRATION_DATE | --retention-period=RETENTION_PERIOD) [--async] [--version-time=TIMESTAMP] - [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + [--encryption-type=ENCRYPTION_TYPE --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] @@ -101,6 +101,28 @@ OPTIONAL FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to create the Cloud Spanner + backup. 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 kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner backup. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/spanner/databases/create b/gcloud/spanner/databases/create index 23914cd34..bedbcb75c 100644 --- a/gcloud/spanner/databases/create +++ b/gcloud/spanner/databases/create @@ -5,8 +5,9 @@ SYNOPSIS gcloud spanner databases create (DATABASE : --instance=INSTANCE) [--async] [--database-dialect=DATABASE_DIALECT] [--ddl=DDL] [--ddl-file=DDL_FILE] [--proto-descriptors-file=PROTO_DESCRIPTORS_FILE] - [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING - --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT] + [--kms-keys=[KMS_KEYS,...] | [--kms-key=KMS_KEY + : --kms-keyring=KMS_KEYRING + --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -94,6 +95,28 @@ FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to create the Cloud Spanner + database. This represents a Cloud resource. (NOTE) Some attributes are + not given arguments in this group but can be set in other ways. + + To set the kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to create the Cloud Spanner database. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/spanner/databases/restore b/gcloud/spanner/databases/restore index b49e7b089..dfcf45bee 100644 --- a/gcloud/spanner/databases/restore +++ b/gcloud/spanner/databases/restore @@ -7,8 +7,8 @@ SYNOPSIS : --destination-instance=DESTINATION_INSTANCE) (--source-backup=SOURCE_BACKUP : --source-instance=SOURCE_INSTANCE) [--async] - [--encryption-type=ENCRYPTION_TYPE [--kms-key=KMS_KEY - : --kms-keyring=KMS_KEYRING + [--encryption-type=ENCRYPTION_TYPE --kms-keys=[KMS_KEYS,...] + | [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT]] [GCLOUD_WIDE_FLAG ...] @@ -114,6 +114,28 @@ OPTIONAL FLAGS At most one of these can be specified: + Key resource - Cloud KMS key(s) to be used to restore the Cloud Spanner + database. This represents a Cloud resource. (NOTE) Some attributes are + not given arguments in this group but can be set in other ways. + + To set the kms-project attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-location attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + To set the kms-keyring attribute: + ▸ provide the argument --kms-keys on the command line with a fully + specified name. + + --kms-keys=[KMS_KEYS,...] + IDs of the keys or fully qualified identifiers for the keys. + + To set the kms-key attribute: + ▫ provide the argument --kms-keys on the command line. + Key resource - Cloud KMS key to be used to restore the Cloud Spanner database. The arguments in this group can be used to specify the attributes of this resource.