diff --git a/gcloud/_version b/gcloud/_version index 3d027c77f..eab0c91e6 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 453.0.0 -alpha 2023.10.27 -beta 2023.10.27 +Google Cloud SDK 454.0.0 +alpha 2023.11.03 +beta 2023.11.03 bq 2.0.98 bundled-python3-unix 3.9.17 -core 2023.10.27 +core 2023.11.03 gcloud-crc32c 1.0.0 gsutil 5.27 diff --git a/gcloud/ai/index-endpoints/mutate-deployed-index b/gcloud/ai/index-endpoints/mutate-deployed-index index e69d47197..7c67df15b 100644 --- a/gcloud/ai/index-endpoints/mutate-deployed-index +++ b/gcloud/ai/index-endpoints/mutate-deployed-index @@ -6,6 +6,8 @@ SYNOPSIS gcloud ai index-endpoints mutate-deployed-index (INDEX_ENDPOINT : --region=REGION) --deployed-index-id=DEPLOYED_INDEX_ID + [--allowed-issuers=[ALLOWED_ISSUERS,...]] [--audiences=[AUDIENCES,...]] + [--deployment-group=DEPLOYMENT_GROUP] [--enable-access-logging] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...] @@ -16,14 +18,18 @@ DESCRIPTION EXAMPLES To mutated a deployed index deployed-index-123 from an index endpoint 456 with 2 min replica count and 10 max replica count under project example in - region us-central1, within vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2 - run: + region us-central1, within vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2, + within deployment group test, enabling access logging, with JWT audiences + aud1 and aud2, JWT issuers issuer1 and issuer2 run: $ gcloud ai index-endpoints mutate-deployed-index 456 \ --project=example --region=us-central1 \ --deployed-index-id=deployed-index-123 --min-replica-count=2 \ --max-replica-count=10 \ - --reserved-ip-ranges=vertex-ai-ip-ranges-1,vertex-ai-ip-ranges-2 + --reserved-ip-ranges=vertex-ai-ip-ranges-1,\ + vertex-ai-ip-ranges-2 --enable-access-logging \ + --audiences=aud1,aud2 --allowed-issuers=issuer1,issuer2 \ + --deployment-group=test POSITIONAL ARGUMENTS Index endpoint resource - The index endpoint ID of the index endpoint.. @@ -64,6 +70,34 @@ REQUIRED FLAGS Id of the deployed index. OPTIONAL FLAGS + --allowed-issuers=[ALLOWED_ISSUERS,...] + List of allowed JWT issuers for a deployed index. + + Each entry must be a valid Google service account, in the following + format: service-account-name@project-id.iam.gserviceaccount.com + + --audiences=[AUDIENCES,...] + List of JWT audiences that are allowed to access a deployed index. + + JWT containing any of these audiences + (https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section + -4.1.3) will be accepted. + + --deployment-group=DEPLOYMENT_GROUP + Deployment group can be no longer than 64 characters (eg:test, prod). + If not set, we will use the default deployment group. + + Creating deployment_groups with reserved_ip_ranges is a recommended + practice when the peered network has multiple peering ranges.This + creates your deployments from predictable IP spaces for easier traffic + administration. + + --enable-access-logging + If true, online prediction access logs are sent to Cloud Logging. + + These logs are standard server access logs, containing information like + timestamp and latency for each prediction request. + --max-replica-count=MAX_REPLICA_COUNT Maximum number of machine replicas the deployed index will be always deployed on. diff --git a/gcloud/alpha/ai/index-endpoints/mutate-deployed-index b/gcloud/alpha/ai/index-endpoints/mutate-deployed-index index 92e154a65..5104c97b6 100644 --- a/gcloud/alpha/ai/index-endpoints/mutate-deployed-index +++ b/gcloud/alpha/ai/index-endpoints/mutate-deployed-index @@ -6,6 +6,8 @@ SYNOPSIS gcloud alpha ai index-endpoints mutate-deployed-index (INDEX_ENDPOINT : --region=REGION) --deployed-index-id=DEPLOYED_INDEX_ID + [--allowed-issuers=[ALLOWED_ISSUERS,...]] [--audiences=[AUDIENCES,...]] + [--deployment-group=DEPLOYMENT_GROUP] [--enable-access-logging] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...] @@ -16,14 +18,18 @@ DESCRIPTION EXAMPLES To mutated a deployed index deployed-index-123 from an index endpoint 456 with 2 min replica count and 10 max replica count under project example in - region us-central1, within vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2 - run: + region us-central1, within vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2, + within deployment group test, enabling access logging, with JWT audiences + aud1 and aud2, JWT issuers issuer1 and issuer2 run: $ gcloud alpha ai index-endpoints mutate-deployed-index 456 \ --project=example --region=us-central1 \ --deployed-index-id=deployed-index-123 --min-replica-count=2 \ --max-replica-count=10 \ - --reserved-ip-ranges=vertex-ai-ip-ranges-1,vertex-ai-ip-ranges-2 + --reserved-ip-ranges=vertex-ai-ip-ranges-1,\ + vertex-ai-ip-ranges-2 --enable-access-logging \ + --audiences=aud1,aud2 --allowed-issuers=issuer1,issuer2 \ + --deployment-group=test POSITIONAL ARGUMENTS Index endpoint resource - The index endpoint ID of the index endpoint.. @@ -64,6 +70,34 @@ REQUIRED FLAGS Id of the deployed index. OPTIONAL FLAGS + --allowed-issuers=[ALLOWED_ISSUERS,...] + List of allowed JWT issuers for a deployed index. + + Each entry must be a valid Google service account, in the following + format: service-account-name@project-id.iam.gserviceaccount.com + + --audiences=[AUDIENCES,...] + List of JWT audiences that are allowed to access a deployed index. + + JWT containing any of these audiences + (https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section + -4.1.3) will be accepted. + + --deployment-group=DEPLOYMENT_GROUP + Deployment group can be no longer than 64 characters (eg:test, prod). + If not set, we will use the default deployment group. + + Creating deployment_groups with reserved_ip_ranges is a recommended + practice when the peered network has multiple peering ranges.This + creates your deployments from predictable IP spaces for easier traffic + administration. + + --enable-access-logging + If true, online prediction access logs are sent to Cloud Logging. + + These logs are standard server access logs, containing information like + timestamp and latency for each prediction request. + --max-replica-count=MAX_REPLICA_COUNT Maximum number of machine replicas the deployed index will be always deployed on. diff --git a/gcloud/alpha/builds/triggers/update/pubsub b/gcloud/alpha/builds/triggers/update/pubsub index 5cfa9e37a..e23288024 100644 --- a/gcloud/alpha/builds/triggers/update/pubsub +++ b/gcloud/alpha/builds/triggers/update/pubsub @@ -6,8 +6,8 @@ SYNOPSIS gcloud alpha builds triggers update pubsub (TRIGGER : --region=REGION) (--trigger-config=PATH | --description=DESCRIPTION --[no-]require-approval --service-account=SERVICE_ACCOUNT - --subscription-filter=SUBSCRIPTION_FILTER - --topic=TOPIC --clear-substitutions + --topic=TOPIC --clear-subscription-filter + | --subscription-filter=SUBSCRIPTION_FILTER --clear-substitutions | --remove-substitutions=[KEY,...] | --update-substitutions=[KEY=VALUE,...] --inline-config=PATH | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR @@ -90,14 +90,19 @@ REQUIRED FLAGS used instead. Format: projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - --subscription-filter=SUBSCRIPTION_FILTER - CEL filter expression for the trigger. See - https://cloud.google.com/build/docs/filter-build-events-using-cel - for more details. - --topic=TOPIC The topic to which this trigger should subscribe. + At most one of these can be specified: + + --clear-subscription-filter + Clear existing subscription filter. + + --subscription-filter=SUBSCRIPTION_FILTER + CEL filter expression for the trigger. See + https://cloud.google.com/build/docs/filter-build-events-using-cel + for more details. + At most one of these can be specified: --clear-substitutions diff --git a/gcloud/alpha/certificate-manager/trust-configs/import b/gcloud/alpha/certificate-manager/trust-configs/import index d9589bc3a..323158dcf 100644 --- a/gcloud/alpha/certificate-manager/trust-configs/import +++ b/gcloud/alpha/certificate-manager/trust-configs/import @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha certificate-manager trust-configs import (TRUST_CONFIG : --location=LOCATION) [--async] [--source=SOURCE] - [GCLOUD_WIDE_FLAG ...] + [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Import a TrustConfig. @@ -63,6 +63,13 @@ FLAGS $ gcloud info --format='value(installation.sdk_root)' + --update-mask=UPDATE_MASK + Update mask used to specify fields to be overwritten in the TrustConfig + by import. TrustConfig must already exist. Fields specified in the + update-mask are relative to the TrustConfig. The flag can be a + comma-separated list of updatable non-nested fields, e.g. description + or trust_stores. Valid example: --update-mask=description,trust_stores. + 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/compute/connect-to-serial-port b/gcloud/alpha/compute/connect-to-serial-port index 89f41a76b..3ad62fcfe 100644 --- a/gcloud/alpha/compute/connect-to-serial-port +++ b/gcloud/alpha/compute/connect-to-serial-port @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha compute connect-to-serial-port [USER@]INSTANCE [--dry-run] [--extra-args=KEY=VALUE,[KEY=VALUE,...]] [--force-key-file-overwrite] - [--port=PORT; default=1] [--ssh-key-file=SSH_KEY_FILE] [--zone=ZONE] + [--location=LOCATION] [--port=PORT; default=1] + [--ssh-key-file=SSH_KEY_FILE] [--zone=ZONE] [--ssh-key-expiration=SSH_KEY_EXPIRATION | --ssh-key-expire-after=SSH_KEY_EXPIRE_AFTER] [GCLOUD_WIDE_FLAG ...] @@ -59,6 +60,10 @@ FLAGS regenerated and will fail in both interactive and non-interactive environments. + --location=LOCATION + If provided, the region in which the serial console connection will + occur. Must be the region of the VM to connect to. + --port=PORT; default=1 The number of the requested serial port. Can be 1-4, default is 1. diff --git a/gcloud/alpha/compute/instance-groups/managed/create b/gcloud/alpha/compute/instance-groups/managed/create index fa1008553..5fa564972 100644 --- a/gcloud/alpha/compute/instance-groups/managed/create +++ b/gcloud/alpha/compute/instance-groups/managed/create @@ -144,17 +144,21 @@ OPTIONAL FLAGS method. maxResults and pageToken query parameters are respected. --standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY - Specifies the initialization delay for stopping/suspending instances. + Specifies the number of seconds that the MIG should wait before + suspending or stopping a VM. The initial delay gives the initialization + script the time to prepare your VM for a quick scale out. --standby-policy-mode=STANDBY_POLICY_MODE - Defines behaviour of using instances from standby pool to resize MIG. - STANDBY_POLICY_MODE must be one of: + Defines how a MIG resumes or starts VMs from a standby pool when the + group scales out. The default mode is manual. STANDBY_POLICY_MODE must + be one of: manual - MIG does not automatically stop/start or suspend/resume VMs. + MIG does not automatically resume or start VMs in the standby pool + when the group scales out. scale-out-pool - MIG automatically resumes and starts VMs when it scales out, and - replenishes the standby pool afterwards. + MIG automatically resumes or starts VMs in the standby pool when + the group scales out, and replenishes the standby pool afterwards. --stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME] Disks considered stateful by the instance group. Managed instance @@ -247,10 +251,10 @@ OPTIONAL FLAGS decreased. --stopped-size=STOPPED_SIZE - Specifies the number of stopped instances. + Specifies the target size of stopped VMs in the group. --suspended-size=SUSPENDED_SIZE - Specifies the number of suspended instances. + Specifies the target size of suspended VMs in the group. --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its diff --git a/gcloud/alpha/compute/instance-groups/managed/update b/gcloud/alpha/compute/instance-groups/managed/update index f126c9ee7..63f1cfb0c 100644 --- a/gcloud/alpha/compute/instance-groups/managed/update +++ b/gcloud/alpha/compute/instance-groups/managed/update @@ -134,17 +134,21 @@ FLAGS IPs. --standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY - Specifies the initialization delay for stopping/suspending instances. + Specifies the number of seconds that the MIG should wait before + suspending or stopping a VM. The initial delay gives the initialization + script the time to prepare your VM for a quick scale out. --standby-policy-mode=STANDBY_POLICY_MODE - Defines behaviour of using instances from standby pool to resize MIG. - STANDBY_POLICY_MODE must be one of: + Defines how a MIG resumes or starts VMs from a standby pool when the + group scales out. The default mode is manual. STANDBY_POLICY_MODE must + be one of: manual - MIG does not automatically stop/start or suspend/resume VMs. + MIG does not automatically resume or start VMs in the standby pool + when the group scales out. scale-out-pool - MIG automatically resumes and starts VMs when it scales out, and - replenishes the standby pool afterwards. + MIG automatically resumes or starts VMs in the standby pool when + the group scales out, and replenishes the standby pool afterwards. --stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME] Disks considered stateful by the instance group. Managed instance @@ -250,10 +254,10 @@ FLAGS decreased. --stopped-size=STOPPED_SIZE - Specifies the number of stopped instances. + Specifies the target size of stopped VMs in the group. --suspended-size=SUSPENDED_SIZE - Specifies the number of suspended instances. + Specifies the target size of suspended VMs in the group. --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index fc771b53c..d6d3772a5 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha compute instances create INSTANCE_NAMES [INSTANCE_NAMES ...] [--accelerator=[count=COUNT],[type=TYPE]] [--async] + [--availability-domain=AVAILABILITY_DOMAIN] [--no-boot-disk-auto-delete] [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] @@ -168,6 +169,14 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --availability-domain=AVAILABILITY_DOMAIN + Specifies the availability domain that this VM instance should be + scheduled on. The number of availability domains that a VM can be + scheduled on is specified when you create the spread placement policy. + + Specify a value from 1 to the number of domains that are available in + your placement policy. + --boot-disk-auto-delete Automatically delete boot disks when their instances are deleted. Enabled by default, use --no-boot-disk-auto-delete to disable. @@ -910,6 +919,8 @@ FLAGS The network interface can have both IPv4 and IPv6 addresses IPV4_ONLY The network interface will be assigned IPv4 addresses + IPV6_ONLY + The network interface will be assigned IPv6 addresses --subnet=SUBNET Specifies the subnet that the VM instances are a part of. If --network @@ -1255,8 +1266,8 @@ FLAGS stack-type Specifies whether IPv6 is enabled on the interface. STACK_TYPE - must be one of: IPV4_ONLY, IPV4_IPV6. The default value is - IPV4_ONLY. + must be one of: IPV4_ONLY, IPV4_IPV6, IPV6_ONLY. The default + value is IPV4_ONLY. ipv6-network-tier Specifies the IPv6 network tier that will be used to configure diff --git a/gcloud/alpha/compute/instances/delete b/gcloud/alpha/compute/instances/delete index 525630d3f..af2e1ae5e 100644 --- a/gcloud/alpha/compute/instances/delete +++ b/gcloud/alpha/compute/instances/delete @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha compute instances delete INSTANCE_NAMES [INSTANCE_NAMES ...] - [--zone=ZONE] [--delete-disks=DISK_TYPE | --keep-disks=DISK_TYPE] + [--no-graceful-shutdown] [--zone=ZONE] + [--delete-disks=DISK_TYPE | --keep-disks=DISK_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -25,6 +26,9 @@ POSITIONAL ARGUMENTS https://cloud.google.com/compute/docs/reference/rest/v1/instances FLAGS + --no-graceful-shutdown + If specified, skips graceful shutdown. + --zone=ZONE Zone of the instances to delete. If not specified, you might be prompted to select a zone (interactive mode only). gcloud attempts to diff --git a/gcloud/alpha/compute/instances/stop b/gcloud/alpha/compute/instances/stop index bed729931..c72c9bf46 100644 --- a/gcloud/alpha/compute/instances/stop +++ b/gcloud/alpha/compute/instances/stop @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud alpha compute instances stop INSTANCE_NAMES [INSTANCE_NAMES ...] - [--async] [--discard-local-ssd[=DISCARD_LOCAL_SSD]] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] + [--async] [--discard-local-ssd[=DISCARD_LOCAL_SSD]] + [--no-graceful-shutdown] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute instances stop is used to stop a Compute @@ -40,6 +40,9 @@ FLAGS --discard-local-ssd[=DISCARD_LOCAL_SSD] If set to true, local SSD data is discarded. + --no-graceful-shutdown + If specified, skips graceful shutdown. + --zone=ZONE Zone of the instances to operate on. If not specified, you might be prompted to select a zone (interactive mode only). gcloud attempts to diff --git a/gcloud/alpha/compute/networks/create b/gcloud/alpha/compute/networks/create index 4ed4b9c52..3e22b4156 100644 --- a/gcloud/alpha/compute/networks/create +++ b/gcloud/alpha/compute/networks/create @@ -7,7 +7,11 @@ SYNOPSIS [--description=DESCRIPTION] [--[no-]enable-ula-internal-ipv6] [--internal-ipv6-range=INTERNAL_IPV6_RANGE] [--mtu=MTU] [--network-firewall-policy-enforcement-order=NETWORK_FIREWALL_POLICY_ENFORCEMENT_ORDER] - [--range=RANGE] [--subnet-mode=MODE] [GCLOUD_WIDE_FLAG ...] + [--range=RANGE] [--subnet-mode=MODE] + [--bgp-best-path-selection-mode=BGP_BEST_PATH_SELECTION_MODE + --[no-]bgp-bps-always-compare-med + --bgp-bps-inter-region-cost=BGP_BPS_INTER_REGION_COST] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute networks create is used to create virtual @@ -97,6 +101,39 @@ FLAGS [Deprecated] Create an old style network that has a range and cannot have subnets. This is not recommended for new networks. + BGP Best Path Selection flags + + --bgp-best-path-selection-mode=BGP_BEST_PATH_SELECTION_MODE + The BGP best selection algorithm to be employed. MODE can be LEGACY + or STANDARD. BGP_BEST_PATH_SELECTION_MODE must be one of: + + LEGACY + LEGACY mode (default) + STANDARD + STANDARD mode + + --[no-]bgp-bps-always-compare-med + Enables/disables the comparison of MED across routes with different + NeighborAsn. This value can only be set if the + --bgp-best-path-selection-mode is STANDARD. Use + --bgp-bps-always-compare-med to enable and + --no-bgp-bps-always-compare-med to disable. + + --bgp-bps-inter-region-cost=BGP_BPS_INTER_REGION_COST + Allows to define preferred approach for handling inter-region cost in + the selection process. This value can only be set if the + --bgp-best-path-selection-mode is STANDARD. BGP_BPS_INTER_REGION_COST + must be one of: + + ADD_COST_TO_MED + Adds inter-region cost to the MED before comparing MED value. + When multiple routes have the same value after the + Add-cost-to-med comparison, the route selection continues and + prefers the route with lowest cost. + DEFAULT + MED is compared as originally received from peers. Cost is + evaluated as a next step when MED is the same. + 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/compute/networks/update b/gcloud/alpha/compute/networks/update index 45d449437..da2ef9cd2 100644 --- a/gcloud/alpha/compute/networks/update +++ b/gcloud/alpha/compute/networks/update @@ -6,6 +6,9 @@ SYNOPSIS [--[no-]enable-ula-internal-ipv6] [--internal-ipv6-range=INTERNAL_IPV6_RANGE] [--mtu=MTU] [--network-firewall-policy-enforcement-order=NETWORK_FIREWALL_POLICY_ENFORCEMENT_ORDER] + [--bgp-best-path-selection-mode=BGP_BEST_PATH_SELECTION_MODE + --[no-]bgp-bps-always-compare-med + --bgp-bps-inter-region-cost=BGP_BPS_INTER_REGION_COST] [--bgp-routing-mode=MODE | --switch-to-custom-subnet-mode] [GCLOUD_WIDE_FLAG ...] @@ -54,6 +57,39 @@ FLAGS BEFORE_CLASSIC_FIREWALL Network Firewall Policy is enforced before classic firewall. + BGP Best Path Selection flags + + --bgp-best-path-selection-mode=BGP_BEST_PATH_SELECTION_MODE + The BGP best selection algorithm to be employed. MODE can be LEGACY + or STANDARD. BGP_BEST_PATH_SELECTION_MODE must be one of: + + LEGACY + LEGACY mode (default) + STANDARD + STANDARD mode + + --[no-]bgp-bps-always-compare-med + Enables/disables the comparison of MED across routes with different + NeighborAsn. This value can only be set if the + --bgp-best-path-selection-mode is STANDARD. Use + --bgp-bps-always-compare-med to enable and + --no-bgp-bps-always-compare-med to disable. + + --bgp-bps-inter-region-cost=BGP_BPS_INTER_REGION_COST + Allows to define preferred approach for handling inter-region cost in + the selection process. This value can only be set if the + --bgp-best-path-selection-mode is STANDARD. BGP_BPS_INTER_REGION_COST + must be one of: + + ADD_COST_TO_MED + Adds inter-region cost to the MED before comparing MED value. + When multiple routes have the same value after the + Add-cost-to-med comparison, the route selection continues and + prefers the route with lowest cost. + DEFAULT + MED is compared as originally received from peers. Cost is + evaluated as a next step when MED is the same. + At most one of these can be specified: --bgp-routing-mode=MODE diff --git a/gcloud/alpha/compute/project-info/update b/gcloud/alpha/compute/project-info/update index b2e5ba3a2..6d9b704f1 100644 --- a/gcloud/alpha/compute/project-info/update +++ b/gcloud/alpha/compute/project-info/update @@ -19,7 +19,7 @@ FLAGS --managed-protection-tier=MANAGED_PROTECTION_TIER The maanged protection tier to assign to the project. - MANAGED_PROTECTION_TIER must be one of: CA_STANDARD, CAMP_PLUS_MONTHLY. + MANAGED_PROTECTION_TIER must be one of: CA_STANDARD, CAMP_PLUS_PAYGO. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/queued-resources/list b/gcloud/alpha/compute/queued-resources/list index 70d5e6c48..b9505f0d1 100644 --- a/gcloud/alpha/compute/queued-resources/list +++ b/gcloud/alpha/compute/queued-resources/list @@ -4,31 +4,26 @@ NAME SYNOPSIS gcloud alpha compute queued-resources list [NAME ...] - [--regexp=REGEXP, -r REGEXP] [--zones=ZONE,[ZONE,...]] + --zones=ZONE,[ZONE,...] [--regexp=REGEXP, -r REGEXP] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute queued-resources list displays all Google - Compute Engine queued resources in a project. - - By default, queued resources from all zones are listed. The results can be - narrowed down using a filter: --filter="zone:( ZONE ... )". + Compute Engine queued resources in a project in given zones. EXAMPLES - To list all queued resources in a project in table form, run: - - $ gcloud alpha compute queued-resources list - - To list the URIs of all queued resources in a project, run: - - $ gcloud alpha compute queued-resources list --uri - - To list all queued resources in the us-central1-b and europe-west1-d zones, - run: + To list all queued resources in us-central1-b and europe-west1-d zones in a + project in table form, run: $ gcloud alpha compute queued-resources list \ - --filter="zone:( us-central1-b europe-west1-d )" + --zones=us-central1-b,europe-west1-d + + To list the URIs of all queued resources in us-central1-b zone in a + project, run: + + $ gcloud alpha compute queued-resources list --zones=us-central1-b \ + --uri POSITIONAL ARGUMENTS [NAME ...] @@ -38,6 +33,10 @@ POSITIONAL ARGUMENTS Argument NAME is deprecated. Use --filter="name=( 'NAME' ... )" instead. +REQUIRED FLAGS + --zones=ZONE,[ZONE,...] + Only resources from the given zones are queried. + FLAGS --regexp=REGEXP, -r REGEXP (DEPRECATED) Regular expression to filter the names of the results on. @@ -46,9 +45,6 @@ FLAGS Flag --regexp is deprecated. Use --filter="name~'REGEXP'" instead. - --zones=ZONE,[ZONE,...] - If provided, only resources from the given zones are queried. - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/compute/security-policies/add-user-defined-field b/gcloud/alpha/compute/security-policies/add-user-defined-field index f299d0cb6..29308ef7d 100644 --- a/gcloud/alpha/compute/security-policies/add-user-defined-field +++ b/gcloud/alpha/compute/security-policies/add-user-defined-field @@ -59,7 +59,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute security-policies add-user-defined-field $ gcloud beta compute security-policies add-user-defined-field diff --git a/gcloud/alpha/compute/security-policies/remove-user-defined-field b/gcloud/alpha/compute/security-policies/remove-user-defined-field index 90a184468..9047b0204 100644 --- a/gcloud/alpha/compute/security-policies/remove-user-defined-field +++ b/gcloud/alpha/compute/security-policies/remove-user-defined-field @@ -42,7 +42,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute security-policies remove-user-defined-field $ gcloud beta compute security-policies remove-user-defined-field diff --git a/gcloud/alpha/compute/snapshot-settings/describe b/gcloud/alpha/compute/snapshot-settings/describe index 40baf57d5..06db505c5 100644 --- a/gcloud/alpha/compute/snapshot-settings/describe +++ b/gcloud/alpha/compute/snapshot-settings/describe @@ -30,7 +30,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute snapshot-settings describe $ gcloud beta compute snapshot-settings describe diff --git a/gcloud/alpha/compute/snapshot-settings/help b/gcloud/alpha/compute/snapshot-settings/help index 07fd02868..a7fe0b19f 100644 --- a/gcloud/alpha/compute/snapshot-settings/help +++ b/gcloud/alpha/compute/snapshot-settings/help @@ -26,7 +26,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute snapshot-settings $ gcloud beta compute snapshot-settings diff --git a/gcloud/alpha/compute/snapshot-settings/update b/gcloud/alpha/compute/snapshot-settings/update index f679d3009..4c024dd69 100644 --- a/gcloud/alpha/compute/snapshot-settings/update +++ b/gcloud/alpha/compute/snapshot-settings/update @@ -65,7 +65,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute snapshot-settings update $ gcloud beta compute snapshot-settings update diff --git a/gcloud/alpha/compute/target-instances/update b/gcloud/alpha/compute/target-instances/update index 8bb3d8ec0..1265f7d34 100644 --- a/gcloud/alpha/compute/target-instances/update +++ b/gcloud/alpha/compute/target-instances/update @@ -65,7 +65,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute target-instances update $ gcloud beta compute target-instances update diff --git a/gcloud/alpha/compute/target-pools/update b/gcloud/alpha/compute/target-pools/update index 35bc36e73..e2d51d423 100644 --- a/gcloud/alpha/compute/target-pools/update +++ b/gcloud/alpha/compute/target-pools/update @@ -63,7 +63,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute target-pools update $ gcloud beta compute target-pools update diff --git a/gcloud/alpha/compute/tpus/tpu-vm/update b/gcloud/alpha/compute/tpus/tpu-vm/update index d8766a335..2e0f34fa5 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/update +++ b/gcloud/alpha/compute/tpus/tpu-vm/update @@ -16,6 +16,12 @@ DESCRIPTION (ALPHA) Update a Cloud TPU VM node. EXAMPLES + To modify a TPU VM node with ID my-tpu in the default user project and + compute/zone by updating the description to "A new description", run: + + $ gcloud alpha compute tpus tpu-vm update my-tpu \ + --description="A new description" + To modify a TPU VM node with ID my-tpu in the default user project, network and compute/zone (with other defaults supplied by API) by adding labels k0, with value value0 and label k1 with value value1 and removing labels with diff --git a/gcloud/alpha/container/binauthz/attestations/sign-and-create b/gcloud/alpha/container/binauthz/attestations/sign-and-create index b1bb00f96..f6e2854a8 100644 --- a/gcloud/alpha/container/binauthz/attestations/sign-and-create +++ b/gcloud/alpha/container/binauthz/attestations/sign-and-create @@ -12,9 +12,8 @@ SYNOPSIS --keyversion-project=KEYVERSION_PROJECT) [--dsse-type=DSSE_TYPE; default="application/vnd.dev.cosign.simplesigning.v1+json"] - [--pae-encode-payload] - [--public-key-id-override=PUBLIC_KEY_ID_OVERRIDE] [--validate] - [GCLOUD_WIDE_FLAG ...] + [--public-key-id-override=PUBLIC_KEY_ID_OVERRIDE] + [--pae-encode-payload | --validate] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command signs and creates a Binary Authorization attestation @@ -123,9 +122,6 @@ OPTIONAL FLAGS --dsse-type=DSSE_TYPE; default="application/vnd.dev.cosign.simplesigning.v1+json" DSSE type used for pae encoding. - --pae-encode-payload - Whether to pae-encode the payload before signing. - --public-key-id-override=PUBLIC_KEY_ID_OVERRIDE If provided, the ID of the public key that will be used to verify the Attestation instead of the default generated one. This ID should match @@ -135,9 +131,18 @@ OPTIONAL FLAGS This parameter is only necessary if the --public-key-id-override flag was provided when this KMS key was added to the Attestor. - --validate - Whether to validate that the Attestation can be verified by the - provided Attestor. + exclusive flags + + At most one of these can be specified: + + --pae-encode-payload + Whether to pae-encode the payload before signing. Note: currently + validation is not supported for attestations with pae-encoded + payload. + + --validate + Whether to validate that the Attestation can be verified by the + provided Attestor. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index 8eba83d3b..b61a6965c 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -17,12 +17,12 @@ SYNOPSIS [--enable-google-cloud-access] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--fleet-project=PROJECT_ID_OR_NUMBER] - [--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] + [--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] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...]] @@ -246,6 +246,15 @@ FLAGS Example: $ gcloud alpha container clusters create-auto \ --fleet-project=my-project + --labels=[KEY=VALUE,...] + Labels to apply to the Google Cloud resources in use by the Kubernetes + Engine cluster. These are unrelated to Kubernetes labels. + + Examples: + + $ gcloud alpha container clusters create-auto example-cluster \ + --labels=label_a=value1,label_b=,label_c=value3 + --logging=[COMPONENT,...] Set the components that have logging enabled. Valid component values are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, NONE diff --git a/gcloud/alpha/container/fleet/help b/gcloud/alpha/container/fleet/help index 392667649..650d0b402 100644 --- a/gcloud/alpha/container/fleet/help +++ b/gcloud/alpha/container/fleet/help @@ -76,6 +76,9 @@ GROUPS multi-cluster-services (ALPHA) Manage Multi-cluster Services Feature. + namespaceactuation + (ALPHA) Manage Namespace Actuation Feature. + operations (ALPHA) Manage Anthos fleet long-running operations. diff --git a/gcloud/alpha/container/fleet/namespaceactuation/create b/gcloud/alpha/container/fleet/namespaceactuation/create new file mode 100644 index 000000000..fe141b954 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaceactuation/create @@ -0,0 +1,37 @@ +NAME + gcloud alpha container fleet namespaceactuation create - create Namespace + Actuation Feature + +SYNOPSIS + gcloud alpha container fleet namespaceactuation create + [--actuation-mode=ACTUATION_MODE; default="unspecified"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command creates Namespace Actuation Feature in a fleet. + +EXAMPLES + To create the Namespace Actuation Feature, run: + + $ gcloud alpha container fleet namespaceactuation create + +FLAGS + --actuation-mode=ACTUATION_MODE; default="unspecified" + The actuation mode that can the feature will use. ACTUATION_MODE must + be one of: unspecified, create-and-delete-if-created, + add-and-remove-fleet-labels. + +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/container/fleet/namespaceactuation/delete b/gcloud/alpha/container/fleet/namespaceactuation/delete new file mode 100644 index 000000000..841e4c5f6 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaceactuation/delete @@ -0,0 +1,37 @@ +NAME + gcloud alpha container fleet namespaceactuation delete - delete Namespace + Actuation Feature + +SYNOPSIS + gcloud alpha container fleet namespaceactuation delete [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command deletes Namespace Actuation Feature in a fleet. + Deleting the feature object doesn't delete the Namespace actuation as it is + an opt-out feature, it only removes any configuration. + +EXAMPLES + To delete the Namespace Actuation Feature, run: + + $ gcloud alpha container fleet namespaceactuation delete + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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/container/fleet/namespaceactuation/describe b/gcloud/alpha/container/fleet/namespaceactuation/describe new file mode 100644 index 000000000..ab8f2bcef --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaceactuation/describe @@ -0,0 +1,31 @@ +NAME + gcloud alpha container fleet namespaceactuation describe - describe the + status of Namespace Actuation Feature resource + +SYNOPSIS + gcloud alpha container fleet namespaceactuation describe + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command describes the status of Namespace Actuation Feature + resource in fleet. + +EXAMPLES + To describe the Namespace Actuation Feature, run: + + $ gcloud alpha container fleet namespaceactuation describe + +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/container/fleet/namespaceactuation/help b/gcloud/alpha/container/fleet/namespaceactuation/help new file mode 100644 index 000000000..65436d605 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaceactuation/help @@ -0,0 +1,37 @@ +NAME + gcloud alpha container fleet namespaceactuation - manage Namespace + Actuation Feature + +SYNOPSIS + gcloud alpha container fleet namespaceactuation COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Namespace Actuation Feature. + +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 Namespace Actuation Feature. + + delete + (ALPHA) Delete Namespace Actuation Feature. + + describe + (ALPHA) Describe the status of Namespace Actuation Feature resource. + + update + (ALPHA) Update Namespace Actuation Feature. + +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/container/fleet/namespaceactuation/update b/gcloud/alpha/container/fleet/namespaceactuation/update new file mode 100644 index 000000000..224ad3678 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaceactuation/update @@ -0,0 +1,37 @@ +NAME + gcloud alpha container fleet namespaceactuation update - update Namespace + Actuation Feature + +SYNOPSIS + gcloud alpha container fleet namespaceactuation update + [--actuation-mode=ACTUATION_MODE; default="unspecified"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command updates Namespace Actuation Feature in a fleet. + +EXAMPLES + To update the Namespace Actuation Feature, run: + + $ gcloud alpha container fleet namespaceactuation update + +FLAGS + --actuation-mode=ACTUATION_MODE; default="unspecified" + The actuation mode that can the feature will use. ACTUATION_MODE must + be one of: unspecified, create-and-delete-if-created, + add-and-remove-fleet-labels. + +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/container/fleet/policycontroller/content/bundles/help b/gcloud/alpha/container/fleet/policycontroller/content/bundles/help index 22fa7d2f2..39376eb67 100644 --- a/gcloud/alpha/container/fleet/policycontroller/content/bundles/help +++ b/gcloud/alpha/container/fleet/policycontroller/content/bundles/help @@ -27,7 +27,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller content bundles $ gcloud beta container fleet policycontroller content bundles diff --git a/gcloud/alpha/container/fleet/policycontroller/content/bundles/remove b/gcloud/alpha/container/fleet/policycontroller/content/bundles/remove index 3fbe00c1e..6b31b9b16 100644 --- a/gcloud/alpha/container/fleet/policycontroller/content/bundles/remove +++ b/gcloud/alpha/container/fleet/policycontroller/content/bundles/remove @@ -74,7 +74,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller content bundles remove $ gcloud beta container fleet policycontroller content bundles remove diff --git a/gcloud/alpha/container/fleet/policycontroller/content/bundles/set b/gcloud/alpha/container/fleet/policycontroller/content/bundles/set index 534b2d3d0..4b37458ab 100644 --- a/gcloud/alpha/container/fleet/policycontroller/content/bundles/set +++ b/gcloud/alpha/container/fleet/policycontroller/content/bundles/set @@ -106,7 +106,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller content bundles set $ gcloud beta container fleet policycontroller content bundles set diff --git a/gcloud/alpha/container/fleet/policycontroller/content/help b/gcloud/alpha/container/fleet/policycontroller/content/help index 374fcb4cd..5f6688371 100644 --- a/gcloud/alpha/container/fleet/policycontroller/content/help +++ b/gcloud/alpha/container/fleet/policycontroller/content/help @@ -27,7 +27,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller content $ gcloud beta container fleet policycontroller content diff --git a/gcloud/alpha/container/fleet/policycontroller/content/templates/disable b/gcloud/alpha/container/fleet/policycontroller/content/templates/disable index a7e35351a..af900bde8 100644 --- a/gcloud/alpha/container/fleet/policycontroller/content/templates/disable +++ b/gcloud/alpha/container/fleet/policycontroller/content/templates/disable @@ -69,7 +69,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller content templates disable $ gcloud beta container fleet policycontroller content templates \ disable diff --git a/gcloud/alpha/container/fleet/policycontroller/content/templates/enable b/gcloud/alpha/container/fleet/policycontroller/content/templates/enable index db9bc5714..e90fb8dc3 100644 --- a/gcloud/alpha/container/fleet/policycontroller/content/templates/enable +++ b/gcloud/alpha/container/fleet/policycontroller/content/templates/enable @@ -70,7 +70,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller content templates enable $ gcloud beta container fleet policycontroller content templates \ enable diff --git a/gcloud/alpha/container/fleet/policycontroller/content/templates/help b/gcloud/alpha/container/fleet/policycontroller/content/templates/help index d6eaa4d10..43f36c549 100644 --- a/gcloud/alpha/container/fleet/policycontroller/content/templates/help +++ b/gcloud/alpha/container/fleet/policycontroller/content/templates/help @@ -27,7 +27,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller content templates $ gcloud beta container fleet policycontroller content templates diff --git a/gcloud/alpha/container/fleet/policycontroller/deployment/help b/gcloud/alpha/container/fleet/policycontroller/deployment/help index faa0181d2..247e8ee67 100644 --- a/gcloud/alpha/container/fleet/policycontroller/deployment/help +++ b/gcloud/alpha/container/fleet/policycontroller/deployment/help @@ -28,7 +28,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller deployment $ gcloud beta container fleet policycontroller deployment diff --git a/gcloud/alpha/container/fleet/policycontroller/deployment/remove b/gcloud/alpha/container/fleet/policycontroller/deployment/remove index 84035d919..f918f671b 100644 --- a/gcloud/alpha/container/fleet/policycontroller/deployment/remove +++ b/gcloud/alpha/container/fleet/policycontroller/deployment/remove @@ -132,7 +132,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller deployment remove $ gcloud beta container fleet policycontroller deployment remove diff --git a/gcloud/alpha/container/fleet/policycontroller/deployment/set b/gcloud/alpha/container/fleet/policycontroller/deployment/set index 961102583..126f65546 100644 --- a/gcloud/alpha/container/fleet/policycontroller/deployment/set +++ b/gcloud/alpha/container/fleet/policycontroller/deployment/set @@ -139,7 +139,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller deployment set $ gcloud beta container fleet policycontroller deployment set diff --git a/gcloud/alpha/container/fleet/policycontroller/describe b/gcloud/alpha/container/fleet/policycontroller/describe index 568f7067d..97145203b 100644 --- a/gcloud/alpha/container/fleet/policycontroller/describe +++ b/gcloud/alpha/container/fleet/policycontroller/describe @@ -64,7 +64,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller describe $ gcloud beta container fleet policycontroller describe diff --git a/gcloud/alpha/container/fleet/policycontroller/detach b/gcloud/alpha/container/fleet/policycontroller/detach index 428739c36..c96ec2e61 100644 --- a/gcloud/alpha/container/fleet/policycontroller/detach +++ b/gcloud/alpha/container/fleet/policycontroller/detach @@ -74,7 +74,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller detach $ gcloud beta container fleet policycontroller detach diff --git a/gcloud/alpha/container/fleet/policycontroller/disable b/gcloud/alpha/container/fleet/policycontroller/disable index 3fdf35cbd..2b80a7911 100644 --- a/gcloud/alpha/container/fleet/policycontroller/disable +++ b/gcloud/alpha/container/fleet/policycontroller/disable @@ -77,7 +77,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller disable $ gcloud beta container fleet policycontroller disable diff --git a/gcloud/alpha/container/fleet/policycontroller/enable b/gcloud/alpha/container/fleet/policycontroller/enable index 3a1218a4f..4efc229dc 100644 --- a/gcloud/alpha/container/fleet/policycontroller/enable +++ b/gcloud/alpha/container/fleet/policycontroller/enable @@ -175,7 +175,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller enable $ gcloud beta container fleet policycontroller enable diff --git a/gcloud/alpha/container/fleet/policycontroller/help b/gcloud/alpha/container/fleet/policycontroller/help index c91d4ef06..f3b15e105 100644 --- a/gcloud/alpha/container/fleet/policycontroller/help +++ b/gcloud/alpha/container/fleet/policycontroller/help @@ -48,7 +48,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller $ gcloud beta container fleet policycontroller diff --git a/gcloud/alpha/container/fleet/policycontroller/suspend b/gcloud/alpha/container/fleet/policycontroller/suspend index 23df0f4af..15d9f6864 100644 --- a/gcloud/alpha/container/fleet/policycontroller/suspend +++ b/gcloud/alpha/container/fleet/policycontroller/suspend @@ -73,7 +73,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller suspend $ gcloud beta container fleet policycontroller suspend diff --git a/gcloud/alpha/container/fleet/policycontroller/update b/gcloud/alpha/container/fleet/policycontroller/update index 8e4ea35ac..b28230884 100644 --- a/gcloud/alpha/container/fleet/policycontroller/update +++ b/gcloud/alpha/container/fleet/policycontroller/update @@ -158,7 +158,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet policycontroller update $ gcloud beta container fleet policycontroller update diff --git a/gcloud/alpha/container/hub/help b/gcloud/alpha/container/hub/help index f37e5978c..3ae29b0fa 100644 --- a/gcloud/alpha/container/hub/help +++ b/gcloud/alpha/container/hub/help @@ -76,6 +76,9 @@ GROUPS multi-cluster-services (ALPHA) Manage Multi-cluster Services Feature. + namespaceactuation + (ALPHA) Manage Namespace Actuation Feature. + operations (ALPHA) Manage Anthos fleet long-running operations. diff --git a/gcloud/alpha/container/hub/namespaceactuation/create b/gcloud/alpha/container/hub/namespaceactuation/create new file mode 100644 index 000000000..8f6d31cfb --- /dev/null +++ b/gcloud/alpha/container/hub/namespaceactuation/create @@ -0,0 +1,37 @@ +NAME + gcloud alpha container hub namespaceactuation create - create Namespace + Actuation Feature + +SYNOPSIS + gcloud alpha container hub namespaceactuation create + [--actuation-mode=ACTUATION_MODE; default="unspecified"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command creates Namespace Actuation Feature in a fleet. + +EXAMPLES + To create the Namespace Actuation Feature, run: + + $ gcloud alpha container hub namespaceactuation create + +FLAGS + --actuation-mode=ACTUATION_MODE; default="unspecified" + The actuation mode that can the feature will use. ACTUATION_MODE must + be one of: unspecified, create-and-delete-if-created, + add-and-remove-fleet-labels. + +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/container/hub/namespaceactuation/delete b/gcloud/alpha/container/hub/namespaceactuation/delete new file mode 100644 index 000000000..957493e62 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaceactuation/delete @@ -0,0 +1,37 @@ +NAME + gcloud alpha container hub namespaceactuation delete - delete Namespace + Actuation Feature + +SYNOPSIS + gcloud alpha container hub namespaceactuation delete [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command deletes Namespace Actuation Feature in a fleet. + Deleting the feature object doesn't delete the Namespace actuation as it is + an opt-out feature, it only removes any configuration. + +EXAMPLES + To delete the Namespace Actuation Feature, run: + + $ gcloud alpha container hub namespaceactuation delete + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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/container/hub/namespaceactuation/describe b/gcloud/alpha/container/hub/namespaceactuation/describe new file mode 100644 index 000000000..4b12b8b37 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaceactuation/describe @@ -0,0 +1,31 @@ +NAME + gcloud alpha container hub namespaceactuation describe - describe the + status of Namespace Actuation Feature resource + +SYNOPSIS + gcloud alpha container hub namespaceactuation describe + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command describes the status of Namespace Actuation Feature + resource in fleet. + +EXAMPLES + To describe the Namespace Actuation Feature, run: + + $ gcloud alpha container hub namespaceactuation describe + +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/container/hub/namespaceactuation/help b/gcloud/alpha/container/hub/namespaceactuation/help new file mode 100644 index 000000000..2f0ff8aab --- /dev/null +++ b/gcloud/alpha/container/hub/namespaceactuation/help @@ -0,0 +1,37 @@ +NAME + gcloud alpha container hub namespaceactuation - manage Namespace Actuation + Feature + +SYNOPSIS + gcloud alpha container hub namespaceactuation COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Namespace Actuation Feature. + +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 Namespace Actuation Feature. + + delete + (ALPHA) Delete Namespace Actuation Feature. + + describe + (ALPHA) Describe the status of Namespace Actuation Feature resource. + + update + (ALPHA) Update Namespace Actuation Feature. + +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/container/hub/namespaceactuation/update b/gcloud/alpha/container/hub/namespaceactuation/update new file mode 100644 index 000000000..0090550a5 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaceactuation/update @@ -0,0 +1,37 @@ +NAME + gcloud alpha container hub namespaceactuation update - update Namespace + Actuation Feature + +SYNOPSIS + gcloud alpha container hub namespaceactuation update + [--actuation-mode=ACTUATION_MODE; default="unspecified"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command updates Namespace Actuation Feature in a fleet. + +EXAMPLES + To update the Namespace Actuation Feature, run: + + $ gcloud alpha container hub namespaceactuation update + +FLAGS + --actuation-mode=ACTUATION_MODE; default="unspecified" + The actuation mode that can the feature will use. ACTUATION_MODE must + be one of: unspecified, create-and-delete-if-created, + add-and-remove-fleet-labels. + +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/container/hub/policycontroller/content/bundles/help b/gcloud/alpha/container/hub/policycontroller/content/bundles/help index d28ef27bc..996c686ca 100644 --- a/gcloud/alpha/container/hub/policycontroller/content/bundles/help +++ b/gcloud/alpha/container/hub/policycontroller/content/bundles/help @@ -27,7 +27,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller content bundles $ gcloud beta container hub policycontroller content bundles diff --git a/gcloud/alpha/container/hub/policycontroller/content/bundles/remove b/gcloud/alpha/container/hub/policycontroller/content/bundles/remove index 58b602df8..28c293ce0 100644 --- a/gcloud/alpha/container/hub/policycontroller/content/bundles/remove +++ b/gcloud/alpha/container/hub/policycontroller/content/bundles/remove @@ -74,7 +74,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller content bundles remove $ gcloud beta container hub policycontroller content bundles remove diff --git a/gcloud/alpha/container/hub/policycontroller/content/bundles/set b/gcloud/alpha/container/hub/policycontroller/content/bundles/set index 526dea487..49d670a4f 100644 --- a/gcloud/alpha/container/hub/policycontroller/content/bundles/set +++ b/gcloud/alpha/container/hub/policycontroller/content/bundles/set @@ -105,7 +105,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller content bundles set $ gcloud beta container hub policycontroller content bundles set diff --git a/gcloud/alpha/container/hub/policycontroller/content/help b/gcloud/alpha/container/hub/policycontroller/content/help index c7140a169..9cbf56255 100644 --- a/gcloud/alpha/container/hub/policycontroller/content/help +++ b/gcloud/alpha/container/hub/policycontroller/content/help @@ -27,7 +27,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller content $ gcloud beta container hub policycontroller content diff --git a/gcloud/alpha/container/hub/policycontroller/content/templates/disable b/gcloud/alpha/container/hub/policycontroller/content/templates/disable index 5d6c54104..3997515ae 100644 --- a/gcloud/alpha/container/hub/policycontroller/content/templates/disable +++ b/gcloud/alpha/container/hub/policycontroller/content/templates/disable @@ -69,7 +69,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller content templates disable $ gcloud beta container hub policycontroller content templates \ disable diff --git a/gcloud/alpha/container/hub/policycontroller/content/templates/enable b/gcloud/alpha/container/hub/policycontroller/content/templates/enable index 86f1cd794..f5b457e55 100644 --- a/gcloud/alpha/container/hub/policycontroller/content/templates/enable +++ b/gcloud/alpha/container/hub/policycontroller/content/templates/enable @@ -70,7 +70,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller content templates enable $ gcloud beta container hub policycontroller content templates enable diff --git a/gcloud/alpha/container/hub/policycontroller/content/templates/help b/gcloud/alpha/container/hub/policycontroller/content/templates/help index aa7da4a89..10d9a6dfa 100644 --- a/gcloud/alpha/container/hub/policycontroller/content/templates/help +++ b/gcloud/alpha/container/hub/policycontroller/content/templates/help @@ -27,7 +27,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller content templates $ gcloud beta container hub policycontroller content templates diff --git a/gcloud/alpha/container/hub/policycontroller/deployment/help b/gcloud/alpha/container/hub/policycontroller/deployment/help index 3d96a1826..a5e7d3210 100644 --- a/gcloud/alpha/container/hub/policycontroller/deployment/help +++ b/gcloud/alpha/container/hub/policycontroller/deployment/help @@ -28,7 +28,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller deployment $ gcloud beta container hub policycontroller deployment diff --git a/gcloud/alpha/container/hub/policycontroller/deployment/remove b/gcloud/alpha/container/hub/policycontroller/deployment/remove index 3b8ffe7c7..42ec94162 100644 --- a/gcloud/alpha/container/hub/policycontroller/deployment/remove +++ b/gcloud/alpha/container/hub/policycontroller/deployment/remove @@ -132,7 +132,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller deployment remove $ gcloud beta container hub policycontroller deployment remove diff --git a/gcloud/alpha/container/hub/policycontroller/deployment/set b/gcloud/alpha/container/hub/policycontroller/deployment/set index 0d73ac2e9..098aa600c 100644 --- a/gcloud/alpha/container/hub/policycontroller/deployment/set +++ b/gcloud/alpha/container/hub/policycontroller/deployment/set @@ -139,7 +139,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller deployment set $ gcloud beta container hub policycontroller deployment set diff --git a/gcloud/alpha/container/hub/policycontroller/describe b/gcloud/alpha/container/hub/policycontroller/describe index 7c785237a..a1a42f99f 100644 --- a/gcloud/alpha/container/hub/policycontroller/describe +++ b/gcloud/alpha/container/hub/policycontroller/describe @@ -64,7 +64,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller describe $ gcloud beta container hub policycontroller describe diff --git a/gcloud/alpha/container/hub/policycontroller/detach b/gcloud/alpha/container/hub/policycontroller/detach index 7f7440a9e..2e9366c06 100644 --- a/gcloud/alpha/container/hub/policycontroller/detach +++ b/gcloud/alpha/container/hub/policycontroller/detach @@ -74,7 +74,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller detach $ gcloud beta container hub policycontroller detach diff --git a/gcloud/alpha/container/hub/policycontroller/disable b/gcloud/alpha/container/hub/policycontroller/disable index 041512d79..5d62ca990 100644 --- a/gcloud/alpha/container/hub/policycontroller/disable +++ b/gcloud/alpha/container/hub/policycontroller/disable @@ -77,7 +77,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller disable $ gcloud beta container hub policycontroller disable diff --git a/gcloud/alpha/container/hub/policycontroller/enable b/gcloud/alpha/container/hub/policycontroller/enable index 6902bc1dc..f33031316 100644 --- a/gcloud/alpha/container/hub/policycontroller/enable +++ b/gcloud/alpha/container/hub/policycontroller/enable @@ -175,7 +175,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller enable $ gcloud beta container hub policycontroller enable diff --git a/gcloud/alpha/container/hub/policycontroller/help b/gcloud/alpha/container/hub/policycontroller/help index bf486487a..813afd69e 100644 --- a/gcloud/alpha/container/hub/policycontroller/help +++ b/gcloud/alpha/container/hub/policycontroller/help @@ -48,7 +48,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller $ gcloud beta container hub policycontroller diff --git a/gcloud/alpha/container/hub/policycontroller/suspend b/gcloud/alpha/container/hub/policycontroller/suspend index d0eb478bc..50cda0ea2 100644 --- a/gcloud/alpha/container/hub/policycontroller/suspend +++ b/gcloud/alpha/container/hub/policycontroller/suspend @@ -73,7 +73,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller suspend $ gcloud beta container hub policycontroller suspend diff --git a/gcloud/alpha/container/hub/policycontroller/update b/gcloud/alpha/container/hub/policycontroller/update index 2abc217e5..12a7ea496 100644 --- a/gcloud/alpha/container/hub/policycontroller/update +++ b/gcloud/alpha/container/hub/policycontroller/update @@ -158,7 +158,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub policycontroller update $ gcloud beta container hub policycontroller update diff --git a/gcloud/alpha/dataproc/clusters/create b/gcloud/alpha/dataproc/clusters/create index 4ad3da2f6..eb692c365 100644 --- a/gcloud/alpha/dataproc/clusters/create +++ b/gcloud/alpha/dataproc/clusters/create @@ -22,6 +22,7 @@ SYNOPSIS [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] [--master-machine-type=MASTER_MACHINE_TYPE] [--master-min-cpu-platform=PLATFORM] [--max-idle=MAX_IDLE] + [--min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION] [--node-group=NODE_GROUP] [--num-driver-pool-local-ssds=NUM_DRIVER_POOL_LOCAL_SSDS] [--num-master-local-ssds=NUM_MASTER_LOCAL_SSDS] @@ -258,6 +259,13 @@ FLAGS such as "2h" or "1d". See $ gcloud topic datetimes for information on duration formats. + --min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION + Minimum fraction of secondary worker nodes required to create the + cluster. If it is not met, cluster creation will fail. Must be a + decimal value between 0 and 1. The number of required secondary workers + is calculated by ceil(min-secondary-worker-fraction * + num_secondary_workers). Defaults to 0.0001. + --node-group=NODE_GROUP The name of the sole-tenant node group to create the cluster on. Can be a short name ("node-group-name") or in the format diff --git a/gcloud/alpha/dataproc/clusters/update b/gcloud/alpha/dataproc/clusters/update index ee024ecd4..d1077be02 100644 --- a/gcloud/alpha/dataproc/clusters/update +++ b/gcloud/alpha/dataproc/clusters/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha dataproc clusters update (CLUSTER : --region=REGION) [--async] [--graceful-decommission-timeout=GRACEFUL_DECOMMISSION_TIMEOUT] + [--min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION] [--num-secondary-workers=NUM_SECONDARY_WORKERS] [--num-workers=NUM_WORKERS] [--secondary-worker-standard-capacity-base=SECONDARY_WORKER_STANDARD_CAPACITY_BASE] @@ -93,6 +94,12 @@ FLAGS maximum allowed timeout is 1 day. See $ gcloud topic datetimes for information on duration formats. + --min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION + Minimum fraction of new secondary worker nodes added in a scale up + update operation, required to update the cluster. If it is not met, + cluster updation will rollback the addition of secondary workers. Must + be a decimal value between 0 and 1. Defaults to 0.0001. + --num-secondary-workers=NUM_SECONDARY_WORKERS The new number of secondary worker nodes in the cluster. diff --git a/gcloud/alpha/dataproc/workflow-templates/create b/gcloud/alpha/dataproc/workflow-templates/create index 13bfb93c8..f042df6e7 100644 --- a/gcloud/alpha/dataproc/workflow-templates/create +++ b/gcloud/alpha/dataproc/workflow-templates/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha dataproc workflow-templates create (TEMPLATE : --region=REGION) [--dag-timeout=DAG_TIMEOUT] - [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + [--kms-key=KMS_KEY] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a workflow template. @@ -59,6 +59,9 @@ FLAGS auto-cancelled, such as "10m" or "16h". See $ gcloud topic datetimes for information on duration formats. + --kms-key=KMS_KEY + The KMS key used to encrypt sensitive data in the workflow template. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster index 8b49567f3..5a456fcf9 100644 --- a/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/alpha/dataproc/workflow-templates/set-managed-cluster @@ -16,7 +16,9 @@ SYNOPSIS [--master-boot-disk-type=MASTER_BOOT_DISK_TYPE] [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] [--master-machine-type=MASTER_MACHINE_TYPE] - [--master-min-cpu-platform=PLATFORM] [--node-group=NODE_GROUP] + [--master-min-cpu-platform=PLATFORM] + [--min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION] + [--node-group=NODE_GROUP] [--num-master-local-ssds=NUM_MASTER_LOCAL_SSDS] [--num-masters=NUM_MASTERS] [--num-secondary-worker-local-ssds=NUM_SECONDARY_WORKER_LOCAL_SSDS] @@ -193,6 +195,13 @@ FLAGS which contains the list of available CPU platforms in the zone (see Availability of CPU platforms for more information). + --min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION + Minimum fraction of secondary worker nodes required to create the + cluster. If it is not met, cluster creation will fail. Must be a + decimal value between 0 and 1. The number of required secondary workers + is calculated by ceil(min-secondary-worker-fraction * + num_secondary_workers). Defaults to 0.0001. + --node-group=NODE_GROUP The name of the sole-tenant node group to create the cluster on. Can be a short name ("node-group-name") or in the format diff --git a/gcloud/alpha/deploy/apply b/gcloud/alpha/deploy/apply index 789d189b8..1209be460 100644 --- a/gcloud/alpha/deploy/apply +++ b/gcloud/alpha/deploy/apply @@ -1,14 +1,15 @@ NAME - gcloud alpha deploy apply - applies a yaml configuration containing Deliver - Pipeline(s), Target(s) declarative definitions + gcloud alpha deploy apply - applies a yaml configuration containing + Delivery Pipeline(s), Target(s) and Automation(s) declarative + definitions SYNOPSIS gcloud alpha deploy apply --file=FILE [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Applies a yaml configuration containing Deliver Pipeline(s), - Target(s) declarative definitions. + (ALPHA) Applies a yaml configuration containing Delivery Pipeline(s), + Target(s) and Automation(s) declarative definitions. EXAMPLES To apply a Cloud Deploy YAML file deploy.yaml: diff --git a/gcloud/alpha/deploy/automation-runs/cancel b/gcloud/alpha/deploy/automation-runs/cancel new file mode 100644 index 000000000..a9302b83d --- /dev/null +++ b/gcloud/alpha/deploy/automation-runs/cancel @@ -0,0 +1,82 @@ +NAME + gcloud alpha deploy automation-runs cancel - cancels a Cloud Deploy + Automation Run + +SYNOPSIS + gcloud alpha deploy automation-runs cancel + (AUTOMATION_RUN + : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancels a Cloud Deploy Automation Run. + +EXAMPLES + To cancel an AutomationRun test-run for delivery pipeline test-pipeline in + region us-central1, run: + + $ gcloud alpha deploy automation-runs cancel test-run \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation run resource - The name of the AutomationRun. 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 automation_run 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. + + AUTOMATION_RUN + ID of the automation_run or fully qualified identifier for the + automation_run. + + To set the name attribute: + ▸ provide the argument automation_run on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The delivery pipeline associated with the automation_run. + Alternatively, set the property [deploy/delivery-pipeline]. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation_run on the command line with a + fully specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + The Cloud region for the automation_run. Alternatively, set the + property [deploy/region]. + + To set the region attribute: + ▸ provide the argument automation_run on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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. These variants are also available: + + $ gcloud deploy automation-runs cancel + + $ gcloud beta deploy automation-runs cancel + diff --git a/gcloud/alpha/deploy/automation-runs/describe b/gcloud/alpha/deploy/automation-runs/describe new file mode 100644 index 000000000..d236aae24 --- /dev/null +++ b/gcloud/alpha/deploy/automation-runs/describe @@ -0,0 +1,84 @@ +NAME + gcloud alpha deploy automation-runs describe - show details for an + Automation Run + +SYNOPSIS + gcloud alpha deploy automation-runs describe + (AUTOMATION_RUN + : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show details for a specified automation run. + +EXAMPLES + To show details about a automation run 'test-automationrun', for delivery + pipeline 'test-pipeline', in region 'us-central1', run: + + $ gcloud alpha deploy automation-runs describe test-automationrun \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation run resource - The name of the automation run you want to + describe. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument automation_run 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. + + AUTOMATION_RUN + ID of the automation run or fully qualified identifier for the + automation run. + + To set the automation_run attribute: + ▸ provide the argument automation_run on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The name of the Cloud Deploy delivery pipeline. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation_run on the command line with a + fully specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + Location of the automation run. + + To set the region attribute: + ▸ provide the argument automation_run on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +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. These variants are also available: + + $ gcloud deploy automation-runs describe + + $ gcloud beta deploy automation-runs describe + diff --git a/gcloud/alpha/deploy/automation-runs/help b/gcloud/alpha/deploy/automation-runs/help new file mode 100644 index 000000000..850ec4bcb --- /dev/null +++ b/gcloud/alpha/deploy/automation-runs/help @@ -0,0 +1,37 @@ +NAME + gcloud alpha deploy automation-runs - manages AutomationRuns resources for + Cloud Deploy + +SYNOPSIS + gcloud alpha deploy automation-runs COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manages AutomationRuns resources for Cloud Deploy. + +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) Cancels a Cloud Deploy Automation Run. + + describe + (ALPHA) Show details for an Automation Run. + + list + (ALPHA) List the Automation Runs. + +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. These variants are also available: + + $ gcloud deploy automation-runs + + $ gcloud beta deploy automation-runs + diff --git a/gcloud/alpha/deploy/automation-runs/list b/gcloud/alpha/deploy/automation-runs/list new file mode 100644 index 000000000..4333fc3b0 --- /dev/null +++ b/gcloud/alpha/deploy/automation-runs/list @@ -0,0 +1,106 @@ +NAME + gcloud alpha deploy automation-runs list - list the Automation Runs + +SYNOPSIS + gcloud alpha deploy automation-runs list + [--delivery-pipeline=DELIVERY_PIPELINE --region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List the automation runs for a specified delivery pipeline. + +EXAMPLES + To list the automation runs for delivery pipeline 'test-pipeline' in region + 'us-central1', run: + + $ gcloud alpha deploy automation-runs list \ + --delivery-pipeline=test-pipeline --region=us-central1 + +FLAGS + Delivery pipeline resource - The delivery pipeline for which you want to + list the automation runs. 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 --delivery-pipeline on the command line with a + fully specified name; + ◆ set the property deploy/delivery_pipeline with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --delivery-pipeline=DELIVERY_PIPELINE + ID of the delivery_pipeline or fully qualified identifier for the + delivery_pipeline. + + To set the delivery-pipeline attribute: + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + Location of the delivery_pipeline. + + To set the region attribute: + ▸ provide the argument --delivery-pipeline on the command line with + a fully specified name; + ▸ set the property deploy/delivery_pipeline with a fully specified + name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +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. These variants are also available: + + $ gcloud deploy automation-runs list + + $ gcloud beta deploy automation-runs list + diff --git a/gcloud/alpha/deploy/automations/delete b/gcloud/alpha/deploy/automations/delete new file mode 100644 index 000000000..2158a8473 --- /dev/null +++ b/gcloud/alpha/deploy/automations/delete @@ -0,0 +1,80 @@ +NAME + gcloud alpha deploy automations delete - deletes a Cloud Deploy Automation + +SYNOPSIS + gcloud alpha deploy automations delete + (AUTOMATION : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes a Cloud Deploy Automation. + +EXAMPLES + To delete an automation test-automation for delivery pipeline + test-pipeline, in region us-central1, run: + + $ gcloud alpha deploy automations delete test-automation \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation resource - The name of the Automation. 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 automation 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. + + AUTOMATION + ID of the automation or fully qualified identifier for the + automation. + + To set the name attribute: + ▸ provide the argument automation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The delivery pipeline associated with the automation. Alternatively, + set the property [deploy/delivery-pipeline]. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + The Cloud region for the automation. Alternatively, set the property + [deploy/region]. + + To set the region attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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. These variants are also available: + + $ gcloud deploy automations delete + + $ gcloud beta deploy automations delete + diff --git a/gcloud/alpha/deploy/automations/describe b/gcloud/alpha/deploy/automations/describe new file mode 100644 index 000000000..685e2aaad --- /dev/null +++ b/gcloud/alpha/deploy/automations/describe @@ -0,0 +1,82 @@ +NAME + gcloud alpha deploy automations describe - show details for an Automation + +SYNOPSIS + gcloud alpha deploy automations describe + (AUTOMATION : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show details for a specified automation. + +EXAMPLES + To show details about an automation 'test-automation', for delivery + pipeline 'test-pipeline', in region 'us-central1', run: + + $ gcloud alpha deploy automations describe test-automation \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation resource - The name of the automation you want to describe. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument automation 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. + + AUTOMATION + ID of the automation or fully qualified identifier for the + automation. + + To set the automation attribute: + ▸ provide the argument automation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The name of the Cloud Deploy delivery pipeline. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + Location of the automation. + + To set the region attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +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. These variants are also available: + + $ gcloud deploy automations describe + + $ gcloud beta deploy automations describe + diff --git a/gcloud/alpha/deploy/automations/export b/gcloud/alpha/deploy/automations/export new file mode 100644 index 000000000..50b88d01b --- /dev/null +++ b/gcloud/alpha/deploy/automations/export @@ -0,0 +1,87 @@ +NAME + gcloud alpha deploy automations export - returns the YAML definition of the + specified Automation + +SYNOPSIS + gcloud alpha deploy automations export + (AUTOMATION : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [--destination=DESTINATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The exported yaml definition can be applied by using the deploy + apply command. + +EXAMPLES + To return the YAML definition of the automation test-automation of delivery + pipeline test-pipeline, in region us-central1, run: + + $ gcloud alpha deploy automations export test-automation \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation resource - The name of the Automation. 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 automation 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. + + AUTOMATION + ID of the automation or fully qualified identifier for the + automation. + + To set the name attribute: + ▸ provide the argument automation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The delivery pipeline associated with the automation. Alternatively, + set the property [deploy/delivery-pipeline]. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + The Cloud region for the automation. Alternatively, set the property + [deploy/region]. + + To set the region attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. + +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. These variants are also available: + + $ gcloud deploy automations export + + $ gcloud beta deploy automations export + diff --git a/gcloud/alpha/deploy/automations/help b/gcloud/alpha/deploy/automations/help new file mode 100644 index 000000000..f3d98642d --- /dev/null +++ b/gcloud/alpha/deploy/automations/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha deploy automations - manages Automations resources for Cloud + Deploy + +SYNOPSIS + gcloud alpha deploy automations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manages Automations resources for Cloud Deploy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (ALPHA) Deletes a Cloud Deploy Automation. + + describe + (ALPHA) Show details for an Automation. + + export + (ALPHA) Returns the YAML definition of the specified Automation. + + list + (ALPHA) List the Automations. + +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. These variants are also available: + + $ gcloud deploy automations + + $ gcloud beta deploy automations + diff --git a/gcloud/alpha/deploy/automations/list b/gcloud/alpha/deploy/automations/list new file mode 100644 index 000000000..fabe3f236 --- /dev/null +++ b/gcloud/alpha/deploy/automations/list @@ -0,0 +1,106 @@ +NAME + gcloud alpha deploy automations list - list the Automations + +SYNOPSIS + gcloud alpha deploy automations list + [--delivery-pipeline=DELIVERY_PIPELINE --region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List the automations for a specified delivery pipeline. + +EXAMPLES + To list the automations for delivery pipeline 'test-pipeline' in region + 'us-central1', run: + + $ gcloud alpha deploy automations list \ + --delivery-pipeline=test-pipeline --region=us-central1 + +FLAGS + Delivery pipeline resource - The delivery pipeline for which you want to + list the automations. 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 --delivery-pipeline on the command line with a + fully specified name; + ◆ set the property deploy/delivery_pipeline with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --delivery-pipeline=DELIVERY_PIPELINE + ID of the delivery_pipeline or fully qualified identifier for the + delivery_pipeline. + + To set the delivery-pipeline attribute: + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + Location of the delivery_pipeline. + + To set the region attribute: + ▸ provide the argument --delivery-pipeline on the command line with + a fully specified name; + ▸ set the property deploy/delivery_pipeline with a fully specified + name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +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. These variants are also available: + + $ gcloud deploy automations list + + $ gcloud beta deploy automations list + diff --git a/gcloud/alpha/deploy/help b/gcloud/alpha/deploy/help index d447f0ae6..df64edd03 100644 --- a/gcloud/alpha/deploy/help +++ b/gcloud/alpha/deploy/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + automation-runs + (ALPHA) Manages AutomationRuns resources for Cloud Deploy. + + automations + (ALPHA) Manages Automations resources for Cloud Deploy. + delivery-pipelines (ALPHA) Create and manage Delivery Pipeline resources for Cloud Deploy. @@ -34,8 +40,8 @@ COMMANDS COMMAND is one of the following: apply - (ALPHA) Applies a yaml configuration containing Deliver Pipeline(s), - Target(s) declarative definitions. + (ALPHA) Applies a yaml configuration containing Delivery Pipeline(s), + Target(s) and Automation(s) declarative definitions. delete (ALPHA) Deletes delivery pipeline(s) and target(s) in a yaml diff --git a/gcloud/alpha/edge-cloud/container/clusters/create b/gcloud/alpha/edge-cloud/container/clusters/create index 9b1c03636..a5faa17a7 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/create +++ b/gcloud/alpha/edge-cloud/container/clusters/create @@ -14,6 +14,7 @@ SYNOPSIS [--control-plane-shared-deployment-policy=CONTROL_PLANE_SHARED_DEPLOYMENT_POLICY] [--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE] [--external-lb-ipv4-address-pools=[EXTERNAL_LB_IPV4_ADDRESS,...]] + [--external-lb-ipv6-address-pools=[EXTERNAL_LB_IPV6_ADDRESS,...]] [--fleet-project=FLEET_PROJECT] [--labels=[KEY=VALUE,...]] [--lro-timeout=LRO_TIMEOUT] [--maintenance-window-end=MAINTENANCE_WINDOW_END] @@ -130,6 +131,17 @@ FLAGS address pools, for example: --external-lb-ipv4-address-pools 10.0.0.1-10.0.0.10,10.0.0.1/24 + --external-lb-ipv6-address-pools=[EXTERNAL_LB_IPV6_ADDRESS,...] + IPv6 address pools that are used for data plane load balancing of local + control plane clusters. Existing pools cannot be updated after cluster + creation; only adding new pools is allowed. Each address pool must be + specified as one of the following two types of values: 1. A IPv6 + address range, for example, "2001:db8::1-2001:db8::a". A range that + contains a single IP (e.g. "2001:db8::1-2001:db8::1") is allowed. 2. A + IPv6 CIDR block, for example, "2001:db8::/120" Use comma when + specifying multiple address pools, for example: + --external-lb-ipv6-address-pools 2001:db8::1-2001:db8::a,2001:db8::/120 + --fleet-project=FLEET_PROJECT Name of the Fleet host project where the cluster is registered. diff --git a/gcloud/alpha/edge-cloud/container/clusters/help b/gcloud/alpha/edge-cloud/container/clusters/help index 1831ed48f..ecae4fe97 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/help +++ b/gcloud/alpha/edge-cloud/container/clusters/help @@ -41,6 +41,9 @@ COMMANDS update (ALPHA) Update an Edge Container cluster. + upgrade + (ALPHA) Upgrade an Edge Container cluster. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/edge-cloud/container/clusters/upgrade b/gcloud/alpha/edge-cloud/container/clusters/upgrade new file mode 100644 index 000000000..2af53a461 --- /dev/null +++ b/gcloud/alpha/edge-cloud/container/clusters/upgrade @@ -0,0 +1,77 @@ +NAME + gcloud alpha edge-cloud container clusters upgrade - upgrade an Edge + Container cluster + +SYNOPSIS + gcloud alpha edge-cloud container clusters upgrade + (CLUSTER : --location=LOCATION) --schedule=SCHEDULE --version=VERSION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Upgrade an Edge Container cluster. + +EXAMPLES + To upgrade an Edge Container cluster to 1.5.1 immediately, run: + + $ gcloud alpha edge-cloud container clusters upgrade my-cluster \ + --version=1.5.1 --schedule=IMMEDIATELY + +POSITIONAL ARGUMENTS + Cluster resource - Edge Container cluster to upgrade. 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + 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. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location for the cluster. + + To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --schedule=SCHEDULE + Schedule to upgrade a cluster after the request is acknowledged by + Google. Support values: IMMEDIATELY. + + --version=VERSION + Target cluster version to upgrade to. For example: "1.5.1". + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the edgecontainer/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud edge-cloud container clusters upgrade + diff --git a/gcloud/alpha/iam/workforce-pools/create b/gcloud/alpha/iam/workforce-pools/create index 4fb0bc51f..2dacaaa2e 100644 --- a/gcloud/alpha/iam/workforce-pools/create +++ b/gcloud/alpha/iam/workforce-pools/create @@ -5,9 +5,10 @@ NAME SYNOPSIS gcloud alpha iam workforce-pools create (WORKFORCE_POOL : --location=LOCATION) --organization=ORGANIZATION - [--async] [--description=DESCRIPTION] [--disabled] - [--display-name=DISPLAY_NAME] [--session-duration=SESSION_DURATION] - [GCLOUD_WIDE_FLAG ...] + [--allowed-services=[domain=DOMAIN]] [--async] + [--description=DESCRIPTION] [--disable-programmatic-signin] + [--disabled] [--display-name=DISPLAY_NAME] + [--session-duration=SESSION_DURATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a workforce pool under an organization given a valid @@ -58,6 +59,12 @@ REQUIRED FLAGS The parent organization of the workforce pool to create. OPTIONAL FLAGS + --allowed-services=[domain=DOMAIN] + Services allowed for web sign-in with the workforce pool. The flag + accepts multiple values with the key as domain and value as the domain + of the service allowed for web sign-in. If not set, by default all the + services are allowed. + --async Return immediately, without waiting for the operation in progress to complete. @@ -66,6 +73,9 @@ OPTIONAL FLAGS A description for the workforce pool. Cannot exceed 256 characters in length. + --disable-programmatic-signin + Disable programmatic sign-in for workforce pool users. + --disabled Whether or not the workforce pool is disabled. diff --git a/gcloud/alpha/iam/workforce-pools/update b/gcloud/alpha/iam/workforce-pools/update index ea44f9cd4..4b440893a 100644 --- a/gcloud/alpha/iam/workforce-pools/update +++ b/gcloud/alpha/iam/workforce-pools/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha iam workforce-pools update (WORKFORCE_POOL : --location=LOCATION) [--async] - [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] + [--description=DESCRIPTION] [--disable-programmatic-signin] + [--disabled] [--display-name=DISPLAY_NAME] [--session-duration=SESSION_DURATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -52,6 +53,13 @@ FLAGS A description for the workforce pool. Cannot exceed 256 characters in length. + --disable-programmatic-signin + Disables the programmatic sign-in for workforce pool users. Specify + --no-disable-security-token-exchange to enable programmatic sign-in. + For more information, refer to Obtain short-lived tokens for workforce + identity federation at + https://cloud.google.com/iam/docs/workforce-obtaining-short-lived-credentials + --disabled Disables the workforce pool. You cannot use a disabled workforce pool to perform new token exchanges or sign-ins using any provider in the diff --git a/gcloud/alpha/looker/help b/gcloud/alpha/looker/help index a11a59896..362772f32 100644 --- a/gcloud/alpha/looker/help +++ b/gcloud/alpha/looker/help @@ -21,6 +21,9 @@ GROUPS operations (ALPHA) Manage Looker operations. + regions + (ALPHA) Manage Looker regions. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/looker/regions/help b/gcloud/alpha/looker/regions/help new file mode 100644 index 000000000..45e63836d --- /dev/null +++ b/gcloud/alpha/looker/regions/help @@ -0,0 +1,30 @@ +NAME + gcloud alpha looker regions - manage Looker regions + +SYNOPSIS + gcloud alpha looker regions COMMAND [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all available regions, run: + + $ gcloud alpha looker regions list + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (ALPHA) List Looker regions. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker regions + diff --git a/gcloud/alpha/looker/regions/list b/gcloud/alpha/looker/regions/list new file mode 100644 index 000000000..2953bcd1b --- /dev/null +++ b/gcloud/alpha/looker/regions/list @@ -0,0 +1,68 @@ +NAME + gcloud alpha looker regions list - list Looker regions + +SYNOPSIS + gcloud alpha looker regions list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all available Looker regions. + +EXAMPLES + To list all available Looker regions, run: + + $ gcloud alpha looker regions list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/looker/docs/reference/rest/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker regions list + diff --git a/gcloud/alpha/pubsub/schemas/create b/gcloud/alpha/pubsub/schemas/create index a77f9e971..ba5cc5843 100644 --- a/gcloud/alpha/pubsub/schemas/create +++ b/gcloud/alpha/pubsub/schemas/create @@ -41,8 +41,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --type=TYPE - Type of the schema. TYPE must be one of: avro, protocol-buffer, - type-unspecified. + Type of the schema. TYPE must be one of: avro, protocol-buffer. Schema definition. diff --git a/gcloud/alpha/pubsub/schemas/validate-message b/gcloud/alpha/pubsub/schemas/validate-message index ea73d4ac0..868383d44 100644 --- a/gcloud/alpha/pubsub/schemas/validate-message +++ b/gcloud/alpha/pubsub/schemas/validate-message @@ -33,7 +33,7 @@ REQUIRED FLAGS --message-encoding=MESSAGE_ENCODING The encoding of the message. MESSAGE_ENCODING must be one of: binary, - encoding-unspecified, json. + json. Schema definition. @@ -43,8 +43,7 @@ REQUIRED FLAGS Name or full path of an existing schema. --type=TYPE - Type of inline schema. TYPE must be one of: avro, protocol-buffer, - type-unspecified. + Type of inline schema. TYPE must be one of: avro, protocol-buffer. This flag argument must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/alpha/pubsub/schemas/validate-schema b/gcloud/alpha/pubsub/schemas/validate-schema index af118c1b5..b612896e0 100644 --- a/gcloud/alpha/pubsub/schemas/validate-schema +++ b/gcloud/alpha/pubsub/schemas/validate-schema @@ -25,8 +25,7 @@ EXAMPLES REQUIRED FLAGS --type=TYPE - Type of the schema. TYPE must be one of: avro, protocol-buffer, - type-unspecified. + Type of the schema. TYPE must be one of: avro, protocol-buffer. Schema definition. diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index e293e350f..7f015c004 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -3,11 +3,21 @@ NAME SYNOPSIS gcloud alpha run deploy [[SERVICE] --namespace=NAMESPACE] [--async] - [--concurrency=CONCURRENCY] [--ingress=INGRESS; default="all"] - [--max-instances=MAX_INSTANCES] [--min-instances=MIN_INSTANCES] + [--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] + [--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 + --remove-volume-mount=[MOUNT_PATH,...] + --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] + --update-env-vars=[KEY=VALUE,...] --clear-secrets + | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] + --update-secrets=[KEY=VALUE,...] --image=IMAGE | --source=SOURCE] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] [--connectivity=CONNECTIVITY --clear-config-maps @@ -17,7 +27,7 @@ SYNOPSIS --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling --[no-]default-url --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT - --revision-suffix=REVISION_SUFFIX + --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,...] @@ -29,18 +39,7 @@ SYNOPSIS | --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 - --remove-volume-mount=[MOUNT_PATH,...] - --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH - | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] - --update-env-vars=[KEY=VALUE,...] --clear-secrets - | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] - --update-secrets=[KEY=VALUE,...] --image=IMAGE | --source=SOURCE - | --container=CONTAINER - --remove-containers=[CONTAINER,...] --binary-authorization=POLICY + --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 @@ -107,6 +106,10 @@ FLAGS instance. Leave concurrency unspecified or provide the special value 'default' to receive the server default value. + --container=CONTAINER + Specifies a container by name. Flags following --container will apply + to the specified container. + --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 @@ -186,6 +189,140 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. + Container Flags + + The following flags apply to a single container. If the --container flag is specified these flags may only be + specified after a --container flag. Otherwise they will apply to the primary ingress container. + + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume + on this resource and PATH is the path within the container's + filesystem to mount this volume. + + --args=[ARG,...] + Comma-separated arguments passed to the command run by the + container image. If not specified and no '--command' is provided, + the container image's default Cmd is used. Otherwise, if not + specified, no arguments are passed. To reset this field to its + default, pass an empty string. + + --clear-volume-mounts + Remove all existing mounts from the current container. + + --command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default Entrypoint is run. To reset this field to its + default, pass an empty string. + + --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 + + --depends-on=[CONTAINER,...] + List of container dependencies to add to the current container. + + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. + + --port=PORT + Container port to receive requests at. Also sets the $PORT + environment variable. Must be a number between 1 and 65535, + inclusive. To unset this field, pass the special value "default". + If updating an existing service with a TCP startup probe pointing + to the previous container port, this will also update the probe + port. + + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + + --[no-]use-http2 + Whether to use HTTP/2 for connections to the service. Use + --use-http2 to enable and --no-use-http2 to disable. + + At most one of these can be specified: + + --clear-env-vars + Remove all environment variables. + + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed + before the new environment variables are added. Example YAML + content: + + KEY_1: "value1" + KEY_2: "value 2" + + --set-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. All + existing environment variables will be removed first. + + Only --update-env-vars and --remove-env-vars can be used together. + If both are specified, --remove-env-vars will be applied first. + + --remove-env-vars=[KEY,...] + List of environment variables to be removed. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + Specify secrets to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. Values should be in the form + SECRET_NAME:SECRET_VERSION. For example: + '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' + will mount a volume at '/secrets/api' containing a file 'key' with the + latest version of secret 'mysecret'. An environment variable named ENV + will also be created whose value is version 1 of secret 'othersecret'. + + At most one of these can be specified: + + --clear-secrets + Remove all secrets. + + --set-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. All existing secrets + will be removed first. + + Only --update-secrets and --remove-secrets can be used together. If + both are specified, --remove-secrets will be applied first. + + --remove-secrets=[KEY,...] + List of secrets to be removed. + + --update-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. + + At most one of these can be specified: + + --image=IMAGE + Name of the container image to deploy (e.g. + gcr.io/cloudrun/hello:latest). + + --source=SOURCE + The location of the source to build. If a Dockerfile is present + in the source code directory, it will be built using that + Dockerfile, otherwise it will use Google Cloud buildpacks. See + https://cloud.google.com/run/docs/deploying-source-code for more + details. The location can be a directory on a local disk or a + gzipped archive file (.tar.gz) in Google Cloud Storage. If the + source is a local directory, this command skips the files + specified in the --ignore-file. If --ignore-file is not + specified, use .gcloudignore file. If a .gcloudignore file is + absent and a .gitignore file is present in the local source + directory, gcloud will use a generated Git-compatible + .gcloudignore file that respects your .gitignored files. The + global .gitignore is not respected. For more information on + .gcloudignore, see gcloud topic gcloudignore. + At most one of these can be specified: --clear-labels @@ -312,6 +449,9 @@ FLAGS gen2 Run the application in a second generation execution environment. + --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 @@ -403,35 +543,37 @@ FLAGS 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. + ◆ 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: (required) 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. + 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: - 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. + ◆ 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. - 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. + 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 @@ -440,233 +582,79 @@ FLAGS --remove-volume=[VOLUME,...] Removes volumes from the Cloud Run resource. - Container Flags + At most one of these can be specified: - If the --container flag is not specified, container flags apply to the - primary container. + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". - Multiple containers can specified using --container= followed by the - container flags applying to that container. For example the following - command creates two containers, one using IMAGE-A and one using IMAGE-B: + --clear-binary-authorization + Remove any previously set Binary Authorization policy. - $ gcloud alpha run deploy --container=A --image=IMAGE-A \ - --container=B --image=IMAGE-B + At most one of these can be specified: - If the --container or --remove-containers flag is specified the following - arguments may only be specified after a --container flag. + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. - --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] - Adds a mount to the current container. Must contain the keys - volume=NAME and mount-path=/PATH where NAME is the name of a - volume on this resource and PATH is the path within the - container's filesystem to mount this volume. + --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. - --args=[ARG,...] - Comma-separated arguments passed to the command run by the - container image. If not specified and no '--command' is - provided, the container image's default Cmd is used. Otherwise, - if not specified, no arguments are passed. To reset this field - to its default, pass an empty string. + At most one of these can be specified: - --clear-volume-mounts - Remove all existing mounts from the current container. + --clear-key + Remove any previously set CMEK key reference. - --command=[COMMAND,...] - Entrypoint for the container image. If not specified, the - container image's default Entrypoint is run. To reset this field - to its default, pass an empty string. + --key=KEY + CMEK key reference to encrypt the container with. - --cpu=CPU - Set a CPU limit in Kubernetes cpu units. + At most one of these can be specified: - 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 + --clear-network + Disconnect this Cloud Run service from the VPC network it is + connected to. - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Direct VPC egress setting flags group. - --depends-on=[CONTAINER,...] - List of container dependencies to add to the current container. + --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. - --memory=MEMORY - Set a memory limit. Ex: 1024Mi, 4Gi. + --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. - --port=PORT - Container port to receive requests at. Also sets the $PORT - environment variable. Must be a number between 1 and 65535, - inclusive. To unset this field, pass the special value - "default". If updating an existing service with a TCP startup - probe pointing to the previous container port, this will also - update the probe port. + At most one of these can be specified: - --remove-volume-mount=[MOUNT_PATH,...] - Removes the volume mounted at the specified path from the - current container. + --clear-network-tags + Clears all existing Compute Engine tags from the Cloud Run + service. - --[no-]use-http2 - Whether to use HTTP/2 for connections to the service. Use - --use-http2 to enable and --no-use-http2 to disable. + --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: + At most one of these can be specified: - --clear-env-vars - Remove all environment variables. + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. - --env-vars-file=FILE_PATH - Path to a local YAML file with definitions for all environment - variables. All existing environment variables will be removed - before the new environment variables are added. Example YAML - content: + --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: - KEY_1: "value1" - KEY_2: "value 2" - - --set-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. All - existing environment variables will be removed first. - - Only --update-env-vars and --remove-env-vars can be used - together. If both are specified, --remove-env-vars will be - applied first. - - --remove-env-vars=[KEY,...] - List of environment variables to be removed. - - --update-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. - - Specify secrets to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. Values should be in the form - SECRET_NAME:SECRET_VERSION. For example: - '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' - will mount a volume at '/secrets/api' containing a file 'key' with - the latest version of secret 'mysecret'. An environment variable - named ENV will also be created whose value is version 1 of secret - 'othersecret'. - - At most one of these can be specified: - - --clear-secrets - Remove all secrets. - - --set-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. All existing - secrets will be removed first. - - Only --update-secrets and --remove-secrets can be used together. - If both are specified, --remove-secrets will be applied first. - - --remove-secrets=[KEY,...] - List of secrets to be removed. - - --update-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. - - At most one of these can be specified: - - --image=IMAGE - Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). - - --source=SOURCE - The location of the source to build. If a Dockerfile is - present in the source code directory, it will be built using - that Dockerfile, otherwise it will use Google Cloud - buildpacks. See - https://cloud.google.com/run/docs/deploying-source-code for - more details. The location can be a directory on a local disk - or a gzipped archive file (.tar.gz) in Google Cloud Storage. - If the source is a local directory, this command skips the - files specified in the --ignore-file. If --ignore-file is not - specified, use .gcloudignore file. If a .gcloudignore file is - absent and a .gitignore file is present in the local source - directory, gcloud will use a generated Git-compatible - .gcloudignore file that respects your .gitignored files. The - global .gitignore is not respected. For more information on - .gcloudignore, see gcloud topic gcloudignore. - - --container=CONTAINER - Specifies a container by name. The following container flags apply - to the specified container. - - --remove-containers=[CONTAINER,...] - List of containers to remove. - - 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. + 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. diff --git a/gcloud/alpha/run/jobs/deploy b/gcloud/alpha/run/jobs/deploy index 711e6a357..de0cfd550 100644 --- a/gcloud/alpha/run/jobs/deploy +++ b/gcloud/alpha/run/jobs/deploy @@ -188,10 +188,12 @@ FLAGS 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: (required) A quantity representing the maximum amount + + ◆ 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. + 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 diff --git a/gcloud/alpha/run/jobs/update b/gcloud/alpha/run/jobs/update index 7fd79eb2f..856d34987 100644 --- a/gcloud/alpha/run/jobs/update +++ b/gcloud/alpha/run/jobs/update @@ -197,10 +197,12 @@ FLAGS 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: (required) A quantity representing the maximum amount + + ◆ 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. + 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 diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 24792a0c4..2b76530e2 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -4,16 +4,25 @@ NAME SYNOPSIS gcloud alpha run services update [[SERVICE] --namespace=NAMESPACE] - [--async] [--concurrency=CONCURRENCY] + [--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] + [--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 + --port=PORT --remove-volume-mount=[MOUNT_PATH,...] + --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] + --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 --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT - --revision-suffix=REVISION_SUFFIX + --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,...] @@ -25,18 +34,7 @@ SYNOPSIS | --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 - --port=PORT --remove-volume-mount=[MOUNT_PATH,...] - --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH - | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] - --update-env-vars=[KEY=VALUE,...] --clear-secrets - | --set-secrets=[KEY=VALUE,...] - | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...] - | --container=CONTAINER - --remove-containers=[CONTAINER,...] --binary-authorization=POLICY + --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 @@ -99,6 +97,10 @@ FLAGS instance. Leave concurrency unspecified or provide the special value 'default' to receive the server default value. + --container=CONTAINER + Specifies a container by name. Flags following --container will apply + to the specified container. + --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 @@ -178,6 +180,120 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. + If the --container or --remove-containers flag is specified the following + arguments may only be specified after a --container flag. + + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume + on this resource and PATH is the path within the container's + filesystem to mount this volume. + + --args=[ARG,...] + Comma-separated arguments passed to the command run by the + container image. If not specified and no '--command' is provided, + the container image's default Cmd is used. Otherwise, if not + specified, no arguments are passed. To reset this field to its + default, pass an empty string. + + --clear-volume-mounts + Remove all existing mounts from the current container. + + --command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default Entrypoint is run. To reset this field to its + default, pass an empty string. + + --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 + + --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). + + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. + + --port=PORT + Container port to receive requests at. Also sets the $PORT + environment variable. Must be a number between 1 and 65535, + inclusive. To unset this field, pass the special value "default". + If updating an existing service with a TCP startup probe pointing + to the previous container port, this will also update the probe + port. + + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + + --[no-]use-http2 + Whether to use HTTP/2 for connections to the service. Use + --use-http2 to enable and --no-use-http2 to disable. + + At most one of these can be specified: + + --clear-env-vars + Remove all environment variables. + + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed + before the new environment variables are added. Example YAML + content: + + KEY_1: "value1" + KEY_2: "value 2" + + --set-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. All + existing environment variables will be removed first. + + Only --update-env-vars and --remove-env-vars can be used together. + If both are specified, --remove-env-vars will be applied first. + + --remove-env-vars=[KEY,...] + List of environment variables to be removed. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + Specify secrets to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. Values should be in the form + SECRET_NAME:SECRET_VERSION. For example: + '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' + will mount a volume at '/secrets/api' containing a file 'key' with the + latest version of secret 'mysecret'. An environment variable named ENV + will also be created whose value is version 1 of secret 'othersecret'. + + At most one of these can be specified: + + --clear-secrets + Remove all secrets. + + --set-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. All existing secrets + will be removed first. + + Only --update-secrets and --remove-secrets can be used together. If + both are specified, --remove-secrets will be applied first. + + --remove-secrets=[KEY,...] + List of secrets to be removed. + + --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: @@ -217,6 +333,9 @@ FLAGS gen2 Run the application in a second generation execution environment. + --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 @@ -308,35 +427,37 @@ FLAGS 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. + ◆ 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: (required) 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. + 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: - 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. + ◆ 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. - 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. + 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 @@ -345,214 +466,79 @@ FLAGS --remove-volume=[VOLUME,...] Removes volumes from the Cloud Run resource. - Container Flags + At most one of these can be specified: - If the --container flag is not specified, container flags apply to the - primary container. + --binary-authorization=POLICY + Binary Authorization policy to check against. This must be set to + "default". - Multiple containers can specified using --container= followed by the - container flags applying to that container. For example the following - command creates two containers, one using IMAGE-A and one using IMAGE-B: + --clear-binary-authorization + Remove any previously set Binary Authorization policy. - $ gcloud alpha run services update --container=A --image=IMAGE-A \ - --container=B --image=IMAGE-B + At most one of these can be specified: - If the --container or --remove-containers flag is specified the following - arguments may only be specified after a --container flag. + --clear-encryption-key-shutdown-hours + Remove any previously set CMEK key shutdown hours setting. - --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] - Adds a mount to the current container. Must contain the keys - volume=NAME and mount-path=/PATH where NAME is the name of a - volume on this resource and PATH is the path within the - container's filesystem to mount this volume. + --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. - --args=[ARG,...] - Comma-separated arguments passed to the command run by the - container image. If not specified and no '--command' is - provided, the container image's default Cmd is used. Otherwise, - if not specified, no arguments are passed. To reset this field - to its default, pass an empty string. + At most one of these can be specified: - --clear-volume-mounts - Remove all existing mounts from the current container. + --clear-key + Remove any previously set CMEK key reference. - --command=[COMMAND,...] - Entrypoint for the container image. If not specified, the - container image's default Entrypoint is run. To reset this field - to its default, pass an empty string. + --key=KEY + CMEK key reference to encrypt the container with. - --cpu=CPU - Set a CPU limit in Kubernetes cpu units. + At most one of these can be specified: - 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 + --clear-network + Disconnect this Cloud Run service from the VPC network it is + connected to. - Cloud Run for Anthos and Knative-compatible Kubernetes clusters - support fractional values. Examples .5, 500m, 2 + Direct VPC egress setting flags group. - --depends-on=[CONTAINER,...] - List of container dependencies to add to the current container. + --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. - --image=IMAGE - Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + --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. - --memory=MEMORY - Set a memory limit. Ex: 1024Mi, 4Gi. + At most one of these can be specified: - --port=PORT - Container port to receive requests at. Also sets the $PORT - environment variable. Must be a number between 1 and 65535, - inclusive. To unset this field, pass the special value - "default". If updating an existing service with a TCP startup - probe pointing to the previous container port, this will also - update the probe port. + --clear-network-tags + Clears all existing Compute Engine tags from the Cloud Run + service. - --remove-volume-mount=[MOUNT_PATH,...] - Removes the volume mounted at the specified path from the - current container. + --network-tags=[TAG,...] + Applies the given Compute Engine tags (comma separated) to the + Cloud Run service. To clear existing tags, use + --clear-network-tags. - --[no-]use-http2 - Whether to use HTTP/2 for connections to the service. Use - --use-http2 to enable and --no-use-http2 to disable. + At most one of these can be specified: - At most one of these can be specified: + --clear-post-key-revocation-action-type + Remove any previously set post CMEK key revocation action type. - --clear-env-vars - Remove all environment variables. + --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: - --env-vars-file=FILE_PATH - Path to a local YAML file with definitions for all environment - variables. All existing environment variables will be removed - before the new environment variables are added. Example YAML - content: - - KEY_1: "value1" - KEY_2: "value 2" - - --set-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. All - existing environment variables will be removed first. - - Only --update-env-vars and --remove-env-vars can be used - together. If both are specified, --remove-env-vars will be - applied first. - - --remove-env-vars=[KEY,...] - List of environment variables to be removed. - - --update-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. - - Specify secrets to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. Values should be in the form - SECRET_NAME:SECRET_VERSION. For example: - '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' - will mount a volume at '/secrets/api' containing a file 'key' with - the latest version of secret 'mysecret'. An environment variable - named ENV will also be created whose value is version 1 of secret - 'othersecret'. - - At most one of these can be specified: - - --clear-secrets - Remove all secrets. - - --set-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. All existing - secrets will be removed first. - - Only --update-secrets and --remove-secrets can be used together. - If both are specified, --remove-secrets will be applied first. - - --remove-secrets=[KEY,...] - List of secrets to be removed. - - --update-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. - - --container=CONTAINER - Specifies a container by name. The following container flags apply - to the specified container. - - --remove-containers=[CONTAINER,...] - List of containers to remove. - - 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. + 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. At most one of these can be specified: diff --git a/gcloud/alpha/scc/muteconfigs/update b/gcloud/alpha/scc/muteconfigs/update index 2435ade43..6e88487b9 100644 --- a/gcloud/alpha/scc/muteconfigs/update +++ b/gcloud/alpha/scc/muteconfigs/update @@ -12,7 +12,7 @@ DESCRIPTION (ALPHA) Update a Cloud Security Command Center mute config. EXAMPLES - Update a mute config with id my-test-mute-config under organization 123 + Update a mute config with ID=my-test-mute-config under organization=123 with a filter on category that equals to XSS_SCRIPTING: $ gcloud alpha scc muteconfigs update my-test-mute-config \ @@ -27,7 +27,7 @@ EXAMPLES --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - Update a mute config with id my-test-mute-config under folder 456 with a + Update a mute config with ID=my-test-mute-config under folder=456 with a filter on category that equals to XSS_SCRIPTING: $ gcloud alpha scc muteconfigs update my-test-mute-config \ @@ -42,7 +42,7 @@ EXAMPLES --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - Update a mute config with id my-test-mute-config under project 789 with a + Update a mute config with ID=my-test-mute-config under project=789 with a filter on category that equals to XSS_SCRIPTING: $ gcloud alpha scc muteconfigs update my-test-mute-config \ diff --git a/gcloud/alpha/spanner/instances/create b/gcloud/alpha/spanner/instances/create index 9ba957cce..0ba98d86d 100644 --- a/gcloud/alpha/spanner/instances/create +++ b/gcloud/alpha/spanner/instances/create @@ -68,7 +68,7 @@ OPTIONAL FLAGS --processing-units=PROCESSING_UNITS Number of processing units for the instance. - Autoscaling + Autoscaling (Preview) --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET Specifies the target percentage of high-priority CPU the autoscaled diff --git a/gcloud/alpha/spanner/instances/update b/gcloud/alpha/spanner/instances/update index f4224e844..32082bd01 100644 --- a/gcloud/alpha/spanner/instances/update +++ b/gcloud/alpha/spanner/instances/update @@ -65,7 +65,7 @@ FLAGS --processing-units=PROCESSING_UNITS Number of processing units for the instance. - Autoscaling + Autoscaling (Preview) --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET Specifies the target percentage of high-priority CPU the autoscaled diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index ad6ecec51..d817f9d2d 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -12,9 +12,9 @@ SYNOPSIS [--authorized-networks=NETWORK,[NETWORK,...]] [--availability-type=AVAILABILITY_TYPE] [--no-backup] [--backup-location=BACKUP_LOCATION] - [--backup-start-time=BACKUP_START_TIME] [--collation=COLLATION] - [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] - [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--backup-start-time=BACKUP_START_TIME] [--cascadable-replica] + [--collation=COLLATION] [--connector-enforcement=CONNECTOR_ENFORCEMENT] + [--cpu=CPU] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--database-version=DATABASE_VERSION; default="MYSQL_8_0"] [--[no-]deletion-protection] [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] @@ -169,6 +169,13 @@ FLAGS Start time of daily backups, specified in the HH:MM format, in the UTC timezone. + --cascadable-replica + Specifies whether a SQL Server replica is a cascadable replica. A + cascadable replica is a SQL Server cross-region replica that supports + replica(s) under it. This flag only takes effect when the + --master-instance-name flag is set, and the replica under creation is + in a different region than the primary instance. + --collation=COLLATION Cloud SQL server-level collation setting, which specifies the set of rules for comparing characters in a character set. diff --git a/gcloud/alpha/sql/instances/help b/gcloud/alpha/sql/instances/help index 73863cbcf..37b9154d5 100644 --- a/gcloud/alpha/sql/instances/help +++ b/gcloud/alpha/sql/instances/help @@ -71,6 +71,9 @@ COMMANDS restore-backup (ALPHA) Restores a backup of a Cloud SQL instance. + switchover + (ALPHA) Switches over a Cloud SQL instance to one of its replicas. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/sql/instances/promote-replica b/gcloud/alpha/sql/instances/promote-replica index 00cc50771..7aaf4c4d5 100644 --- a/gcloud/alpha/sql/instances/promote-replica +++ b/gcloud/alpha/sql/instances/promote-replica @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha sql instances promote-replica REPLICA [--async] - [GCLOUD_WIDE_FLAG ...] + [--[no-]failover] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Promotes Cloud SQL read replica to a stand-alone instance. @@ -18,6 +18,10 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --[no-]failover + Whether the promote operation is a failover. Use --failover to enable + and --no-failover to disable. + 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/sql/instances/switchover b/gcloud/alpha/sql/instances/switchover new file mode 100644 index 000000000..004b46585 --- /dev/null +++ b/gcloud/alpha/sql/instances/switchover @@ -0,0 +1,42 @@ +NAME + gcloud alpha sql instances switchover - switches over a Cloud SQL instance + to one of its replicas + +SYNOPSIS + gcloud alpha sql instances switchover REPLICA [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Switches over a Cloud SQL instance to one of its replicas. Only + supported on Cloud SQL for SQL Server and MySQL instances. + +EXAMPLES + To switch over an instance to its replica called replica-instance: + + $ gcloud alpha sql instances switchover replica-instance + +POSITIONAL ARGUMENTS + REPLICA + Cloud SQL replica ID. + +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 alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta sql instances switchover + diff --git a/gcloud/alpha/storage/buckets/create b/gcloud/alpha/storage/buckets/create index e025e7c2f..0c15eca53 100644 --- a/gcloud/alpha/storage/buckets/create +++ b/gcloud/alpha/storage/buckets/create @@ -13,6 +13,7 @@ SYNOPSIS [--placement=REGION,REGION] [--recovery-point-objective=SETTING, --rpo=SETTING] [--retention-period=RETENTION_PERIOD] + [--soft-delete-duration=SOFT_DELETE_DURATION] [--[no-]uniform-bucket-level-access, -b] [--autoclass-terminal-storage-class=AUTOCLASS_TERMINAL_STORAGE_CLASS --[no-]enable-autoclass] [GCLOUD_WIDE_FLAG ...] @@ -95,6 +96,13 @@ FLAGS Default is no retention period. Only available for Cloud Storage using the JSON API. + --soft-delete-duration=SOFT_DELETE_DURATION + Duration to retain soft-deleted objects. For example, "2w1d" is two + weeks and one day. The presence of this flag creates a bucket with a + soft delete policy enabled, meaning deleted objects can be restored if + requested within the inputted duration. See gcloud topic datetimes for + more information on the duration format. + --[no-]uniform-bucket-level-access, -b Turns on uniform bucket-level access setting. Default is False. Use --uniform-bucket-level-access to enable and diff --git a/gcloud/alpha/storage/buckets/update b/gcloud/alpha/storage/buckets/update index ed38748b8..e463c79fd 100644 --- a/gcloud/alpha/storage/buckets/update +++ b/gcloud/alpha/storage/buckets/update @@ -3,13 +3,13 @@ NAME SYNOPSIS gcloud alpha storage buckets update URL [URL ...] - [--additional-headers=HEADER=VALUE] [--continue-on-error, -c] - [--[no-]default-event-based-hold] + [--additional-headers=HEADER=VALUE] [--clear-soft-delete] + [--continue-on-error, -c] [--[no-]default-event-based-hold] [--default-storage-class=DEFAULT_STORAGE_CLASS] [--lock-retention-period] [--recovery-point-objective=SETTING, --rpo=SETTING] - [--[no-]requester-pays] [--[no-]uniform-bucket-level-access] - [--[no-]versioning] + [--[no-]requester-pays] [--soft-delete-duration=SOFT_DELETE_DURATION] + [--[no-]uniform-bucket-level-access] [--[no-]versioning] [--acl-file=ACL_FILE --add-acl-grant=[ACL_GRANT,...] --canned-acl=PREDEFINED_ACL, --predefined-acl=PREDEFINED_ACL, -a PREDEFINED_ACL --remove-acl-grant=REMOVE_ACL_GRANT] @@ -61,6 +61,10 @@ FLAGS Overrides the default storage/additional_headers property value for this command invocation. + --clear-soft-delete + Clears bucket soft delete settings. Does not affect objects already in + soft-deleted state. + --continue-on-error, -c If any operations are unsuccessful, the command will exit with a non-zero exit status after completing the remaining operations. This @@ -100,6 +104,10 @@ FLAGS pays all costs related to accessing the bucket and its objects. Use --requester-pays to enable and --no-requester-pays to disable. + --soft-delete-duration=SOFT_DELETE_DURATION + Duration to retain soft-deleted objects. For example, "2w1d" is two + weeks and one day. + --[no-]uniform-bucket-level-access Enables or disables uniform bucket-level access (https://cloud.google.com/storage/docs/bucket-policy-only) for the diff --git a/gcloud/alpha/storage/cp b/gcloud/alpha/storage/cp index f392d829f..efc64d7b5 100644 --- a/gcloud/alpha/storage/cp +++ b/gcloud/alpha/storage/cp @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha storage cp [SOURCE ...] DESTINATION [--additional-headers=HEADER=VALUE] [--all-versions, -A] - [--no-clobber, -n] [--continue-on-error, -c] [--daisy-chain, -D] - [--do-not-decompress] [--include-managed-folders] + [--no-clobber, -n] [--content-md5=MD5_DIGEST] [--continue-on-error, -c] + [--daisy-chain, -D] [--do-not-decompress] [--include-managed-folders] [--manifest-path=MANIFEST_PATH, -L MANIFEST_PATH] [--preserve-posix, -P] [--print-created-message, -v] [--read-paths-from-stdin, -I] [--recursive, -R, -r] @@ -22,8 +22,7 @@ SYNOPSIS [--cache-control=CACHE_CONTROL --content-disposition=CONTENT_DISPOSITION --content-encoding=CONTENT_ENCODING - --content-language=CONTENT_LANGUAGE --content-md5=MD5_DIGEST - --content-type=CONTENT_TYPE + --content-language=CONTENT_LANGUAGE --content-type=CONTENT_TYPE --custom-time=CUSTOM_TIME --clear-custom-metadata | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] | --remove-custom-metadata=[METADATA_KEYS,...] @@ -96,6 +95,11 @@ FLAGS items will be printed. This option may perform an additional GET request for cloud objects before attempting an upload. + --content-md5=MD5_DIGEST + Manually specified MD5 hash digest for the contents of an uploaded + file. This flag cannot be used when uploading multiple files. The + custom digest is used by the cloud provider for validation. + --continue-on-error, -c If any operations are unsuccessful, the command will exit with a non-zero exit status after completing the remaining operations. This @@ -298,11 +302,6 @@ OBJECT METADATA FLAGS --content-language=CONTENT_LANGUAGE Content's language (e.g. en signifies "English"). - --content-md5=MD5_DIGEST - Manually specified MD5 hash digest for the contents of an uploaded - file. This flag cannot be used when uploading multiple files. The - custom digest is used by the cloud provider for validation. - --content-type=CONTENT_TYPE Type of data contained in the object (e.g. text/html). diff --git a/gcloud/alpha/storage/help b/gcloud/alpha/storage/help index 336050d89..d7ec741c0 100644 --- a/gcloud/alpha/storage/help +++ b/gcloud/alpha/storage/help @@ -60,6 +60,9 @@ COMMANDS mv (ALPHA) Moves or renames objects. + restore + (ALPHA) Restore one or more soft-deleted objects. + rm (ALPHA) Delete objects and buckets. diff --git a/gcloud/alpha/storage/ls b/gcloud/alpha/storage/ls index f93cd80a1..5a360d95a 100644 --- a/gcloud/alpha/storage/ls +++ b/gcloud/alpha/storage/ls @@ -3,9 +3,10 @@ NAME SYNOPSIS gcloud alpha storage ls [PATH ...] [--additional-headers=HEADER=VALUE] - [--all-versions, -a] [--buckets, -b] [--etag, -e] + [--all-versions, -a] [--buckets, -b] [--etag, -e] [--exhaustive] [--fetch-encrypted-object-hashes] [--format=FORMAT] - [--read-paths-from-stdin, -I] [--readable-sizes] [--recursive, -R, -r] + [--next-page-token=NEXT_PAGE_TOKEN] [--read-paths-from-stdin, -I] + [--readable-sizes] [--recursive, -R, -r] [--soft-deleted] [--full, -L | --json, -j | --long, -l] [--decryption-keys=[DECRYPTION_KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -91,6 +92,11 @@ FLAGS --etag, -e Include ETag metadata in listings that use the --long flag. + --exhaustive + For features like soft delete, the API may return an empty list. If + present, continue querying. This may incur costs from repeated LIST + calls and may not return any additional objects. + --fetch-encrypted-object-hashes API requests to the LIST endpoint do not fetch the hashes for encrypted objects by default. If this flag is set, a GET request is sent for each @@ -102,6 +108,9 @@ FLAGS "--format=gsutil"). Other format values (e.g. "json") do not work. See different ls flags and commands for alternative formatting. + --next-page-token=NEXT_PAGE_TOKEN + Page token for resuming LIST calls. + --read-paths-from-stdin, -I Read the list of URLs from stdin. @@ -113,6 +122,10 @@ FLAGS Recursively list the contents of any directories that match the path expression. + --soft-deleted + Displays soft-deleted objects only. Excludes live and noncurrent + objects. + At most one of these can be specified: --full, -L diff --git a/gcloud/alpha/storage/mv b/gcloud/alpha/storage/mv index b11f015ad..1d79868f9 100644 --- a/gcloud/alpha/storage/mv +++ b/gcloud/alpha/storage/mv @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha storage mv [SOURCE ...] DESTINATION [--additional-headers=HEADER=VALUE] [--all-versions, -A] - [--no-clobber, -n] [--continue-on-error, -c] [--daisy-chain, -D] - [--do-not-decompress] [--include-managed-folders] + [--no-clobber, -n] [--content-md5=MD5_DIGEST] [--continue-on-error, -c] + [--daisy-chain, -D] [--do-not-decompress] [--include-managed-folders] [--manifest-path=MANIFEST_PATH, -L MANIFEST_PATH] [--preserve-posix, -P] [--print-created-message, -v] [--read-paths-from-stdin, -I] [--skip-unsupported, -U] @@ -21,8 +21,7 @@ SYNOPSIS [--cache-control=CACHE_CONTROL --content-disposition=CONTENT_DISPOSITION --content-encoding=CONTENT_ENCODING - --content-language=CONTENT_LANGUAGE --content-md5=MD5_DIGEST - --content-type=CONTENT_TYPE + --content-language=CONTENT_LANGUAGE --content-type=CONTENT_TYPE --custom-time=CUSTOM_TIME --clear-custom-metadata | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] | --remove-custom-metadata=[METADATA_KEYS,...] @@ -107,6 +106,11 @@ FLAGS items will be printed. This option may perform an additional GET request for cloud objects before attempting an upload. + --content-md5=MD5_DIGEST + Manually specified MD5 hash digest for the contents of an uploaded + file. This flag cannot be used when uploading multiple files. The + custom digest is used by the cloud provider for validation. + --continue-on-error, -c If any operations are unsuccessful, the command will exit with a non-zero exit status after completing the remaining operations. This @@ -305,11 +309,6 @@ OBJECT METADATA FLAGS --content-language=CONTENT_LANGUAGE Content's language (e.g. en signifies "English"). - --content-md5=MD5_DIGEST - Manually specified MD5 hash digest for the contents of an uploaded - file. This flag cannot be used when uploading multiple files. The - custom digest is used by the cloud provider for validation. - --content-type=CONTENT_TYPE Type of data contained in the object (e.g. text/html). diff --git a/gcloud/alpha/storage/objects/describe b/gcloud/alpha/storage/objects/describe index d4512839b..49dab3d96 100644 --- a/gcloud/alpha/storage/objects/describe +++ b/gcloud/alpha/storage/objects/describe @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha storage objects describe URL [--additional-headers=HEADER=VALUE] [--fetch-encrypted-object-hashes] - [--raw] [--decryption-keys=[DECRYPTION_KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--raw] [--soft-deleted] [--decryption-keys=[DECRYPTION_KEY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Describe a Cloud Storage object. @@ -41,6 +42,10 @@ FLAGS Shows metadata in the format returned by the API instead of standardizing it. + --soft-deleted + Displays soft-deleted objects only. Excludes live and noncurrent + objects. + ENCRYPTION FLAGS --decryption-keys=[DECRYPTION_KEY,...] A comma-separated list of customer-supplied encryption keys (RFC 4648 diff --git a/gcloud/alpha/storage/objects/list b/gcloud/alpha/storage/objects/list index c2aadcf20..874f9eec0 100644 --- a/gcloud/alpha/storage/objects/list +++ b/gcloud/alpha/storage/objects/list @@ -3,10 +3,12 @@ NAME SYNOPSIS gcloud alpha storage objects list URLS [URLS ...] - [--additional-headers=HEADER=VALUE] [--fetch-encrypted-object-hashes] - [--raw] [--stat] [--decryption-keys=[DECRYPTION_KEY,...]] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--additional-headers=HEADER=VALUE] [--exhaustive] + [--fetch-encrypted-object-hashes] [--next-page-token=NEXT_PAGE_TOKEN] + [--raw] [--soft-deleted] [--stat] + [--decryption-keys=[DECRYPTION_KEY,...]] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) List Cloud Storage objects. @@ -40,16 +42,28 @@ FLAGS Overrides the default storage/additional_headers property value for this command invocation. + --exhaustive + For features like soft delete, the API may return an empty list. If + present, continue querying. This may incur costs from repeated LIST + calls and may not return any additional objects. + --fetch-encrypted-object-hashes API requests to the LIST endpoint do not fetch the hashes for encrypted objects by default. If this flag is set, a GET request is sent for each encrypted object in order to fetch hashes. This can significantly increase the cost of the command. + --next-page-token=NEXT_PAGE_TOKEN + Page token for resuming LIST calls. + --raw Shows metadata in the format returned by the API instead of standardizing it. + --soft-deleted + Displays soft-deleted objects only. Excludes live and noncurrent + objects. + --stat Emulates gsutil stat-style behavior. Does not show past object versions and changes output format. diff --git a/gcloud/alpha/storage/objects/update b/gcloud/alpha/storage/objects/update index ac22b9f7d..c69c45037 100644 --- a/gcloud/alpha/storage/objects/update +++ b/gcloud/alpha/storage/objects/update @@ -16,11 +16,10 @@ SYNOPSIS --encryption-key=ENCRYPTION_KEY] [--cache-control=CACHE_CONTROL --clear-cache-control --clear-content-disposition --clear-content-encoding - --clear-content-language --clear-content-md5 --clear-content-type - --clear-custom-time --content-disposition=CONTENT_DISPOSITION + --clear-content-language --clear-content-type --clear-custom-time + --content-disposition=CONTENT_DISPOSITION --content-encoding=CONTENT_ENCODING - --content-language=CONTENT_LANGUAGE --content-md5=MD5_DIGEST - --content-type=CONTENT_TYPE + --content-language=CONTENT_LANGUAGE --content-type=CONTENT_TYPE --custom-time=CUSTOM_TIME --clear-custom-metadata | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] | --remove-custom-metadata=[METADATA_KEYS,...] @@ -161,9 +160,6 @@ OBJECT METADATA FLAGS --clear-content-language Clears object content language. - --clear-content-md5 - Clears object content MD5. - --clear-content-type Clears object content type. @@ -179,11 +175,6 @@ OBJECT METADATA FLAGS --content-language=CONTENT_LANGUAGE Content's language (e.g. en signifies "English"). - --content-md5=MD5_DIGEST - Manually specified MD5 hash digest for the contents of an uploaded - file. This flag cannot be used when uploading multiple files. The - custom digest is used by the cloud provider for validation. - --content-type=CONTENT_TYPE Type of data contained in the object (e.g. text/html). diff --git a/gcloud/alpha/storage/operations/list b/gcloud/alpha/storage/operations/list index 661000ac3..f29d4a718 100644 --- a/gcloud/alpha/storage/operations/list +++ b/gcloud/alpha/storage/operations/list @@ -4,8 +4,7 @@ NAME SYNOPSIS gcloud alpha storage operations list PARENT_RESOURCE_NAME [--server-filter=SERVER_FILTER] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) List storage operations. @@ -50,25 +49,12 @@ LIST COMMAND FLAGS 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, diff --git a/gcloud/alpha/storage/restore b/gcloud/alpha/storage/restore new file mode 100644 index 000000000..40268278a --- /dev/null +++ b/gcloud/alpha/storage/restore @@ -0,0 +1,121 @@ +NAME + gcloud alpha storage restore - restore one or more soft-deleted objects + +SYNOPSIS + gcloud alpha storage restore [URLS ...] [--all-versions, -a] [--async] + [--[no-]preserve-acl, -p] [--read-paths-from-stdin, -I] + [--allow-overwrite --deleted-after-time=DELETED_AFTER_TIME + --deleted-before-time=DELETED_BEFORE_TIME] + [--if-generation-match=GENERATION + --if-metageneration-match=METAGENERATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The restore command restores soft-deleted objects: + + $ gcloud alpha storage restore url... + +EXAMPLES + Restore specific version of object in a bucket. Note: Generation number is + required. + + $ gcloud alpha storage restore gs://bucket/file1.txt#123 + + Restore two objects in a bucket: + + $ gcloud alpha storage restore gs://bucket/file1.txt#123 \ + gs://bucket/file2.txt#456 + + Restore all text objects in a bucket: + + $ gcloud alpha storage restore gs://bucket/**.txt + + Read list of files to restore from stdin: + + $ cat list-of-files.txt | gcloud alpha storage restore \ + --read-paths-from-stdin + + Restore object with its original ACL policy: + + $ gcloud alpha storage restore gs://bucket/file1.txt --preserve-acl + + Restore all objects in a bucket asynchronously: + + $ gcloud alpha storage restore gs://bucket/** --async + + Restore all text files in a bucket asynchronously: + + $ gcloud alpha storage restore gs://bucket/**.txt --async + +POSITIONAL ARGUMENTS + [URLS ...] + The url of objects to list. + +FLAGS + SYNCHRONOUS RESTORE OPTIONS + + --all-versions, -a + Restores all versions of soft-deleted objects. + + This flag is only useful for buckets with [object versioning] + (https://cloud.google.com/storage/docs/object-versioning) enabled. In + this case, the latest soft-deleted version will become live and the + previous generations will become noncurrent. + + If versioning is disabled, the latest soft-deleted version will + become live and previous generations will be soft-deleted again. + + This flag disables parallelism to preserve version order. + + --async + Initiates an asynchronous bulk restore operation on the specified + bucket. + + --[no-]preserve-acl, -p + Preserves ACLs when copying in the cloud. This option is Cloud + Storage-only, and you need OWNER access to all copied objects. If all + objects in the destination bucket should have the same ACL, you can + also set a default object ACL on that bucket instead of using this + flag. Preserving ACLs is the default behavior for updating existing + objects. Use --preserve-acl to enable and --no-preserve-acl to disable. + + --read-paths-from-stdin, -I + Read the list of URLs from stdin. + + BULK RESTORE OPTIONS + + --allow-overwrite + If included, live objects will be overwritten. If versioning is + enabled, this will result in a noncurrent object. If versioning is + not enabled, this will result in a soft-deleted object. + + --deleted-after-time=DELETED_AFTER_TIME + Restores only the objects that were soft-deleted after this time. + + --deleted-before-time=DELETED_BEFORE_TIME + Restores only the objects that were soft-deleted before this time. + +PRECONDITION FLAGS + --if-generation-match=GENERATION + Execute only if the generation matches the generation of the requested + object. + + --if-metageneration-match=METAGENERATION + Execute only if the metageneration matches the metageneration of the + requested object. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud storage restore + diff --git a/gcloud/alpha/storage/rsync b/gcloud/alpha/storage/rsync index 4ae2501de..34ffb9de1 100644 --- a/gcloud/alpha/storage/rsync +++ b/gcloud/alpha/storage/rsync @@ -6,9 +6,9 @@ SYNOPSIS [--additional-headers=HEADER=VALUE] [--canned-acl=PREDEFINED_ACL, --predefined-acl=PREDEFINED_ACL, -a PREDEFINED_ACL] - [--checksums-only] [--no-clobber, -n] [--continue-on-error, -c] - [--delete-unmatched-destination-objects] [--dry-run] - [--exclude=[REGEX,...], -x [REGEX,...]] + [--checksums-only] [--no-clobber, -n] [--content-md5=MD5_DIGEST] + [--continue-on-error, -c] [--delete-unmatched-destination-objects] + [--dry-run] [--exclude=[REGEX,...], -x [REGEX,...]] [--gzip-in-flight=[FILE_EXTENSIONS,...], -j [FILE_EXTENSIONS,...]] [--gzip-in-flight-all, -J] [--no-ignore-symlinks] [--include-managed-folders] [--preserve-posix, -P] @@ -19,8 +19,7 @@ SYNOPSIS [--cache-control=CACHE_CONTROL --content-disposition=CONTENT_DISPOSITION --content-encoding=CONTENT_ENCODING - --content-language=CONTENT_LANGUAGE --content-md5=MD5_DIGEST - --content-type=CONTENT_TYPE + --content-language=CONTENT_LANGUAGE --content-type=CONTENT_TYPE --custom-time=CUSTOM_TIME --clear-custom-metadata | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] | --remove-custom-metadata=[METADATA_KEYS,...] @@ -125,6 +124,11 @@ FLAGS items will be printed. This option may perform an additional GET request for cloud objects before attempting an upload. + --content-md5=MD5_DIGEST + Manually specified MD5 hash digest for the contents of an uploaded + file. This flag cannot be used when uploading multiple files. The + custom digest is used by the cloud provider for validation. + --continue-on-error, -c If any operations are unsuccessful, the command will exit with a non-zero exit status after completing the remaining operations. This @@ -241,11 +245,6 @@ OBJECT METADATA FLAGS --content-language=CONTENT_LANGUAGE Content's language (e.g. en signifies "English"). - --content-md5=MD5_DIGEST - Manually specified MD5 hash digest for the contents of an uploaded - file. This flag cannot be used when uploading multiple files. The - custom digest is used by the cloud provider for validation. - --content-type=CONTENT_TYPE Type of data contained in the object (e.g. text/html). diff --git a/gcloud/artifacts/vulnerabilities/load-vex b/gcloud/artifacts/vulnerabilities/load-vex index eb540f057..16630bc74 100644 --- a/gcloud/artifacts/vulnerabilities/load-vex +++ b/gcloud/artifacts/vulnerabilities/load-vex @@ -31,7 +31,10 @@ REQUIRED FLAGS The path of the VEX file. --uri=URI - The path of the artifact in Artifact Registry. + The path of the artifact in Artifact Registry. A 'gcr.io' image can + also be used if redirection is enabled in Artifact Registry. Make sure + 'artifactregistry.projectsettings.get' permission is granted to the + current gcloud user to verify the redirection status. OPTIONAL FLAGS --project=PROJECT diff --git a/gcloud/beta/ai/index-endpoints/mutate-deployed-index b/gcloud/beta/ai/index-endpoints/mutate-deployed-index index 88b39e267..4f2074136 100644 --- a/gcloud/beta/ai/index-endpoints/mutate-deployed-index +++ b/gcloud/beta/ai/index-endpoints/mutate-deployed-index @@ -6,6 +6,8 @@ SYNOPSIS gcloud beta ai index-endpoints mutate-deployed-index (INDEX_ENDPOINT : --region=REGION) --deployed-index-id=DEPLOYED_INDEX_ID + [--allowed-issuers=[ALLOWED_ISSUERS,...]] [--audiences=[AUDIENCES,...]] + [--deployment-group=DEPLOYMENT_GROUP] [--enable-access-logging] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] [--reserved-ip-ranges=[RESERVED_IP_RANGES,...]] [GCLOUD_WIDE_FLAG ...] @@ -16,14 +18,18 @@ DESCRIPTION EXAMPLES To mutated a deployed index deployed-index-123 from an index endpoint 456 with 2 min replica count and 10 max replica count under project example in - region us-central1, within vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2 - run: + region us-central1, within vertex-ai-ip-ranges-1 and vertex-ai-ip-ranges-2, + within deployment group test, enabling access logging, with JWT audiences + aud1 and aud2, JWT issuers issuer1 and issuer2 run: $ gcloud beta ai index-endpoints mutate-deployed-index 456 \ --project=example --region=us-central1 \ --deployed-index-id=deployed-index-123 --min-replica-count=2 \ --max-replica-count=10 \ - --reserved-ip-ranges=vertex-ai-ip-ranges-1,vertex-ai-ip-ranges-2 + --reserved-ip-ranges=vertex-ai-ip-ranges-1,\ + vertex-ai-ip-ranges-2 --enable-access-logging \ + --audiences=aud1,aud2 --allowed-issuers=issuer1,issuer2 \ + --deployment-group=test POSITIONAL ARGUMENTS Index endpoint resource - The index endpoint ID of the index endpoint.. @@ -64,6 +70,34 @@ REQUIRED FLAGS Id of the deployed index. OPTIONAL FLAGS + --allowed-issuers=[ALLOWED_ISSUERS,...] + List of allowed JWT issuers for a deployed index. + + Each entry must be a valid Google service account, in the following + format: service-account-name@project-id.iam.gserviceaccount.com + + --audiences=[AUDIENCES,...] + List of JWT audiences that are allowed to access a deployed index. + + JWT containing any of these audiences + (https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section + -4.1.3) will be accepted. + + --deployment-group=DEPLOYMENT_GROUP + Deployment group can be no longer than 64 characters (eg:test, prod). + If not set, we will use the default deployment group. + + Creating deployment_groups with reserved_ip_ranges is a recommended + practice when the peered network has multiple peering ranges.This + creates your deployments from predictable IP spaces for easier traffic + administration. + + --enable-access-logging + If true, online prediction access logs are sent to Cloud Logging. + + These logs are standard server access logs, containing information like + timestamp and latency for each prediction request. + --max-replica-count=MAX_REPLICA_COUNT Maximum number of machine replicas the deployed index will be always deployed on. diff --git a/gcloud/beta/builds/triggers/update/pubsub b/gcloud/beta/builds/triggers/update/pubsub index 085a2bc14..51679f972 100644 --- a/gcloud/beta/builds/triggers/update/pubsub +++ b/gcloud/beta/builds/triggers/update/pubsub @@ -6,8 +6,8 @@ SYNOPSIS gcloud beta builds triggers update pubsub (TRIGGER : --region=REGION) (--trigger-config=PATH | --description=DESCRIPTION --[no-]require-approval --service-account=SERVICE_ACCOUNT - --subscription-filter=SUBSCRIPTION_FILTER - --topic=TOPIC --clear-substitutions + --topic=TOPIC --clear-subscription-filter + | --subscription-filter=SUBSCRIPTION_FILTER --clear-substitutions | --remove-substitutions=[KEY,...] | --update-substitutions=[KEY=VALUE,...] --inline-config=PATH | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR @@ -90,14 +90,19 @@ REQUIRED FLAGS used instead. Format: projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - --subscription-filter=SUBSCRIPTION_FILTER - CEL filter expression for the trigger. See - https://cloud.google.com/build/docs/filter-build-events-using-cel - for more details. - --topic=TOPIC The topic to which this trigger should subscribe. + At most one of these can be specified: + + --clear-subscription-filter + Clear existing subscription filter. + + --subscription-filter=SUBSCRIPTION_FILTER + CEL filter expression for the trigger. See + https://cloud.google.com/build/docs/filter-build-events-using-cel + for more details. + At most one of these can be specified: --clear-substitutions diff --git a/gcloud/beta/certificate-manager/trust-configs/import b/gcloud/beta/certificate-manager/trust-configs/import index 2a5b75b92..4ae18a024 100644 --- a/gcloud/beta/certificate-manager/trust-configs/import +++ b/gcloud/beta/certificate-manager/trust-configs/import @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta certificate-manager trust-configs import (TRUST_CONFIG : --location=LOCATION) [--async] [--source=SOURCE] - [GCLOUD_WIDE_FLAG ...] + [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Import a TrustConfig. @@ -63,6 +63,13 @@ FLAGS $ gcloud info --format='value(installation.sdk_root)' + --update-mask=UPDATE_MASK + Update mask used to specify fields to be overwritten in the TrustConfig + by import. TrustConfig must already exist. Fields specified in the + update-mask are relative to the TrustConfig. The flag can be a + comma-separated list of updatable non-nested fields, e.g. description + or trust_stores. Valid example: --update-mask=description,trust_stores. + 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/compute/instance-groups/managed/create b/gcloud/beta/compute/instance-groups/managed/create index 15e41a2e8..b842d10f0 100644 --- a/gcloud/beta/compute/instance-groups/managed/create +++ b/gcloud/beta/compute/instance-groups/managed/create @@ -9,11 +9,14 @@ SYNOPSIS [--description=DESCRIPTION] [--[no-]force-update-on-repair] [--initial-delay=INITIAL_DELAY] [--instance-redistribution-type=TYPE] [--list-managed-instances-results=MODE] + [--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY] + [--standby-policy-mode=STANDBY_POLICY_MODE] [--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]] [--stateful-external-ip=[enabled], [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] [--stateful-internal-ip=[enabled], [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] + [--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE] [--target-distribution-shape=SHAPE] [--target-pool=[TARGET_POOL,...]] [--zones=ZONE,[ZONE,...]] [--health-check=HEALTH_CHECK | --http-health-check=HTTP_HEALTH_CHECK @@ -140,6 +143,23 @@ OPTIONAL FLAGS Pagination is enabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are respected. + --standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY + Specifies the number of seconds that the MIG should wait before + suspending or stopping a VM. The initial delay gives the initialization + script the time to prepare your VM for a quick scale out. + + --standby-policy-mode=STANDBY_POLICY_MODE + Defines how a MIG resumes or starts VMs from a standby pool when the + group scales out. The default mode is manual. STANDBY_POLICY_MODE must + be one of: + + manual + MIG does not automatically resume or start VMs in the standby pool + when the group scales out. + scale-out-pool + MIG automatically resumes or starts VMs in the standby pool when + the group scales out, and replenishes the standby pool afterwards. + --stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME] Disks considered stateful by the instance group. Managed instance groups preserve and reattach stateful disks on VM autohealing, update, @@ -230,6 +250,12 @@ OPTIONAL FLAGS the instance is deleted manually or when the group size is decreased. + --stopped-size=STOPPED_SIZE + Specifies the target size of stopped VMs in the group. + + --suspended-size=SUSPENDED_SIZE + Specifies the target size of suspended VMs in the group. + --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its instances across zones within the region. The default shape is even. diff --git a/gcloud/beta/compute/instance-groups/managed/update b/gcloud/beta/compute/instance-groups/managed/update index 256672d29..29f010754 100644 --- a/gcloud/beta/compute/instance-groups/managed/update +++ b/gcloud/beta/compute/instance-groups/managed/update @@ -11,11 +11,14 @@ SYNOPSIS [--remove-stateful-disks=DEVICE_NAME,[DEVICE_NAME,...]] [--remove-stateful-external-ips=INTERFACE_NAME,[...]] [--remove-stateful-internal-ips=INTERFACE_NAME,[...]] + [--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY] + [--standby-policy-mode=STANDBY_POLICY_MODE] [--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]] [--stateful-external-ip=[enabled], [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] [--stateful-internal-ip=[enabled], [auto-delete=AUTO-DELETE],[interface-name=INTERFACE-NAME]] + [--stopped-size=STOPPED_SIZE] [--suspended-size=SUSPENDED_SIZE] [--target-distribution-shape=SHAPE] [--clear-autohealing | --initial-delay=INITIAL_DELAY --health-check=HEALTH_CHECK @@ -130,6 +133,23 @@ FLAGS Remove stateful configuration for the specified interfaces for internal IPs. + --standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY + Specifies the number of seconds that the MIG should wait before + suspending or stopping a VM. The initial delay gives the initialization + script the time to prepare your VM for a quick scale out. + + --standby-policy-mode=STANDBY_POLICY_MODE + Defines how a MIG resumes or starts VMs from a standby pool when the + group scales out. The default mode is manual. STANDBY_POLICY_MODE must + be one of: + + manual + MIG does not automatically resume or start VMs in the standby pool + when the group scales out. + scale-out-pool + MIG automatically resumes or starts VMs in the standby pool when + the group scales out, and replenishes the standby pool afterwards. + --stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME] Disks considered stateful by the instance group. Managed instance groups preserve and reattach stateful disks on VM autohealing, update, @@ -233,6 +253,12 @@ FLAGS the instance is deleted manually or when the group size is decreased. + --stopped-size=STOPPED_SIZE + Specifies the target size of stopped VMs in the group. + + --suspended-size=SUSPENDED_SIZE + Specifies the target size of suspended VMs in the group. + --target-distribution-shape=SHAPE Specifies how a regional managed instance group distributes its instances across zones within the region. The default shape is even. diff --git a/gcloud/beta/compute/networks/vpc-access/connectors/create b/gcloud/beta/compute/networks/vpc-access/connectors/create index dad9d8b88..7e0d056c5 100644 --- a/gcloud/beta/compute/networks/vpc-access/connectors/create +++ b/gcloud/beta/compute/networks/vpc-access/connectors/create @@ -89,16 +89,22 @@ FLAGS throughput. --max-throughput=MAX_THROUGHPUT - Maximum throughput in Mbps. Value must be a multiple of 100 from - 300 through 1000. Must be higher than the value specified by - --min-throughput; the set value, if applicable, or the default - minimum throughput value. + Maximum throughput of the connector in Mbps. Refers to the expected + throughput when using an e2-micro machine type. Value must be a + multiple of 100 from 300 through 1000. Must be higher than the + value specified by --min-throughput. If both max-throughput and + max-instances are provided, max-instances takes precedence over + max-throughput. The use of max-throughput is discouraged in favor + of max-instances. --min-throughput=MIN_THROUGHPUT - Minimum throughput in Mbps. Value must be a multiple of 100 from - 200 through 900. Must be lower than the value specified by - --max-throughput; the set value, if applicable, or the default - maximum throughput value. + Minimum throughput of the connector in Mbps. Refers to the expected + throughput when using an e2-micro machine type. Value must be a + multiple of 100 from 200 through 900. Must be lower than the value + specified by --max-throughput. If both min-throughput and + min-instances are provided, min-instances takes precedence over + min-throughput. The use of min-throughput is discouraged in favor + of min-instances. At most one of these can be specified: diff --git a/gcloud/beta/compute/project-info/update b/gcloud/beta/compute/project-info/update index 7f6d39db0..c9d2ebcfa 100644 --- a/gcloud/beta/compute/project-info/update +++ b/gcloud/beta/compute/project-info/update @@ -19,7 +19,7 @@ FLAGS --managed-protection-tier=MANAGED_PROTECTION_TIER The maanged protection tier to assign to the project. - MANAGED_PROTECTION_TIER must be one of: CA_STANDARD, CAMP_PLUS_MONTHLY. + MANAGED_PROTECTION_TIER must be one of: CA_STANDARD, CAMP_PLUS_PAYGO. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/compute/security-policies/add-user-defined-field b/gcloud/beta/compute/security-policies/add-user-defined-field index 649e9263c..219b1f6b4 100644 --- a/gcloud/beta/compute/security-policies/add-user-defined-field +++ b/gcloud/beta/compute/security-policies/add-user-defined-field @@ -56,8 +56,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute security-policies add-user-defined-field $ gcloud alpha compute security-policies add-user-defined-field diff --git a/gcloud/beta/compute/security-policies/remove-user-defined-field b/gcloud/beta/compute/security-policies/remove-user-defined-field index 2c45e864f..7da492cb8 100644 --- a/gcloud/beta/compute/security-policies/remove-user-defined-field +++ b/gcloud/beta/compute/security-policies/remove-user-defined-field @@ -39,8 +39,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute security-policies remove-user-defined-field $ gcloud alpha compute security-policies remove-user-defined-field diff --git a/gcloud/beta/compute/snapshot-settings/describe b/gcloud/beta/compute/snapshot-settings/describe index 01af10009..0713ce750 100644 --- a/gcloud/beta/compute/snapshot-settings/describe +++ b/gcloud/beta/compute/snapshot-settings/describe @@ -25,8 +25,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute snapshot-settings describe $ gcloud alpha compute snapshot-settings describe diff --git a/gcloud/beta/compute/snapshot-settings/help b/gcloud/beta/compute/snapshot-settings/help index a0a41e258..5ec28fa26 100644 --- a/gcloud/beta/compute/snapshot-settings/help +++ b/gcloud/beta/compute/snapshot-settings/help @@ -23,8 +23,10 @@ COMMANDS (BETA) Update snapshot settings. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute snapshot-settings $ gcloud alpha compute snapshot-settings diff --git a/gcloud/beta/compute/snapshot-settings/update b/gcloud/beta/compute/snapshot-settings/update index e10a75b57..975d67d54 100644 --- a/gcloud/beta/compute/snapshot-settings/update +++ b/gcloud/beta/compute/snapshot-settings/update @@ -61,8 +61,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute snapshot-settings update $ gcloud alpha compute snapshot-settings update diff --git a/gcloud/beta/compute/target-instances/update b/gcloud/beta/compute/target-instances/update index 2d82760e0..6e5df042a 100644 --- a/gcloud/beta/compute/target-instances/update +++ b/gcloud/beta/compute/target-instances/update @@ -62,8 +62,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute target-instances update $ gcloud alpha compute target-instances update diff --git a/gcloud/beta/compute/target-pools/update b/gcloud/beta/compute/target-pools/update index 0a6b0532b..547aac311 100644 --- a/gcloud/beta/compute/target-pools/update +++ b/gcloud/beta/compute/target-pools/update @@ -60,8 +60,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute target-pools update $ gcloud alpha compute target-pools update diff --git a/gcloud/beta/container/binauthz/attestations/sign-and-create b/gcloud/beta/container/binauthz/attestations/sign-and-create index d71afa708..4a92f865b 100644 --- a/gcloud/beta/container/binauthz/attestations/sign-and-create +++ b/gcloud/beta/container/binauthz/attestations/sign-and-create @@ -12,9 +12,8 @@ SYNOPSIS --keyversion-project=KEYVERSION_PROJECT) [--dsse-type=DSSE_TYPE; default="application/vnd.dev.cosign.simplesigning.v1+json"] - [--pae-encode-payload] - [--public-key-id-override=PUBLIC_KEY_ID_OVERRIDE] [--validate] - [GCLOUD_WIDE_FLAG ...] + [--public-key-id-override=PUBLIC_KEY_ID_OVERRIDE] + [--pae-encode-payload | --validate] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command signs and creates a Binary Authorization attestation @@ -123,9 +122,6 @@ OPTIONAL FLAGS --dsse-type=DSSE_TYPE; default="application/vnd.dev.cosign.simplesigning.v1+json" DSSE type used for pae encoding. - --pae-encode-payload - Whether to pae-encode the payload before signing. - --public-key-id-override=PUBLIC_KEY_ID_OVERRIDE If provided, the ID of the public key that will be used to verify the Attestation instead of the default generated one. This ID should match @@ -135,9 +131,18 @@ OPTIONAL FLAGS This parameter is only necessary if the --public-key-id-override flag was provided when this KMS key was added to the Attestor. - --validate - Whether to validate that the Attestation can be verified by the - provided Attestor. + exclusive flags + + At most one of these can be specified: + + --pae-encode-payload + Whether to pae-encode the payload before signing. Note: currently + validation is not supported for attestations with pae-encoded + payload. + + --validate + Whether to validate that the Attestation can be verified by the + provided Attestor. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 50a61bfc0..5fbad163a 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -17,12 +17,12 @@ SYNOPSIS [--enable-google-cloud-access] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--fleet-project=PROJECT_ID_OR_NUMBER] - [--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] + [--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] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE --binauthz-policy-bindings=[name=BINAUTHZ_POLICY,...]] @@ -246,6 +246,15 @@ FLAGS Example: $ gcloud beta container clusters create-auto \ --fleet-project=my-project + --labels=[KEY=VALUE,...] + Labels to apply to the Google Cloud resources in use by the Kubernetes + Engine cluster. These are unrelated to Kubernetes labels. + + Examples: + + $ gcloud beta container clusters create-auto example-cluster \ + --labels=label_a=value1,label_b=,label_c=value3 + --logging=[COMPONENT,...] Set the components that have logging enabled. Valid component values are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, NONE diff --git a/gcloud/beta/container/fleet/policycontroller/content/bundles/help b/gcloud/beta/container/fleet/policycontroller/content/bundles/help index bcdcfa1a6..eccf97cc4 100644 --- a/gcloud/beta/container/fleet/policycontroller/content/bundles/help +++ b/gcloud/beta/container/fleet/policycontroller/content/bundles/help @@ -24,8 +24,10 @@ COMMANDS (BETA) Sets bundle installation for Policy Controller content. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller content bundles $ gcloud alpha container fleet policycontroller content bundles diff --git a/gcloud/beta/container/fleet/policycontroller/content/bundles/remove b/gcloud/beta/container/fleet/policycontroller/content/bundles/remove index c716972f1..304f61afd 100644 --- a/gcloud/beta/container/fleet/policycontroller/content/bundles/remove +++ b/gcloud/beta/container/fleet/policycontroller/content/bundles/remove @@ -71,8 +71,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller content bundles remove $ gcloud alpha container fleet policycontroller content bundles \ remove diff --git a/gcloud/beta/container/fleet/policycontroller/content/bundles/set b/gcloud/beta/container/fleet/policycontroller/content/bundles/set index ec23d2e63..186dd439f 100644 --- a/gcloud/beta/container/fleet/policycontroller/content/bundles/set +++ b/gcloud/beta/container/fleet/policycontroller/content/bundles/set @@ -103,8 +103,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller content bundles set $ gcloud alpha container fleet policycontroller content bundles set diff --git a/gcloud/beta/container/fleet/policycontroller/content/help b/gcloud/beta/container/fleet/policycontroller/content/help index a8281b898..45fa78b59 100644 --- a/gcloud/beta/container/fleet/policycontroller/content/help +++ b/gcloud/beta/container/fleet/policycontroller/content/help @@ -24,8 +24,10 @@ GROUPS (BETA) Manage Policy Controller content templates. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller content $ gcloud alpha container fleet policycontroller content diff --git a/gcloud/beta/container/fleet/policycontroller/content/templates/disable b/gcloud/beta/container/fleet/policycontroller/content/templates/disable index 19ad37347..a1338dabf 100644 --- a/gcloud/beta/container/fleet/policycontroller/content/templates/disable +++ b/gcloud/beta/container/fleet/policycontroller/content/templates/disable @@ -66,8 +66,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller content templates disable $ gcloud alpha container fleet policycontroller content templates \ disable diff --git a/gcloud/beta/container/fleet/policycontroller/content/templates/enable b/gcloud/beta/container/fleet/policycontroller/content/templates/enable index 878f17ba5..36509b351 100644 --- a/gcloud/beta/container/fleet/policycontroller/content/templates/enable +++ b/gcloud/beta/container/fleet/policycontroller/content/templates/enable @@ -67,8 +67,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller content templates enable $ gcloud alpha container fleet policycontroller content templates \ enable diff --git a/gcloud/beta/container/fleet/policycontroller/content/templates/help b/gcloud/beta/container/fleet/policycontroller/content/templates/help index 105f05cec..7ee9a4443 100644 --- a/gcloud/beta/container/fleet/policycontroller/content/templates/help +++ b/gcloud/beta/container/fleet/policycontroller/content/templates/help @@ -24,8 +24,10 @@ COMMANDS (BETA) Installs the template library for Policy Controller. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller content templates $ gcloud alpha container fleet policycontroller content templates diff --git a/gcloud/beta/container/fleet/policycontroller/deployment/help b/gcloud/beta/container/fleet/policycontroller/deployment/help index 71b13cf45..7039820cd 100644 --- a/gcloud/beta/container/fleet/policycontroller/deployment/help +++ b/gcloud/beta/container/fleet/policycontroller/deployment/help @@ -25,8 +25,10 @@ COMMANDS (BETA) Sets configuration of the Policy Controller components. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller deployment $ gcloud alpha container fleet policycontroller deployment diff --git a/gcloud/beta/container/fleet/policycontroller/deployment/remove b/gcloud/beta/container/fleet/policycontroller/deployment/remove index 682f55893..3f54c8160 100644 --- a/gcloud/beta/container/fleet/policycontroller/deployment/remove +++ b/gcloud/beta/container/fleet/policycontroller/deployment/remove @@ -129,8 +129,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller deployment remove $ gcloud alpha container fleet policycontroller deployment remove diff --git a/gcloud/beta/container/fleet/policycontroller/deployment/set b/gcloud/beta/container/fleet/policycontroller/deployment/set index 502a12103..9761bad74 100644 --- a/gcloud/beta/container/fleet/policycontroller/deployment/set +++ b/gcloud/beta/container/fleet/policycontroller/deployment/set @@ -136,8 +136,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller deployment set $ gcloud alpha container fleet policycontroller deployment set diff --git a/gcloud/beta/container/fleet/policycontroller/describe b/gcloud/beta/container/fleet/policycontroller/describe index cb104dfbe..1cf278506 100644 --- a/gcloud/beta/container/fleet/policycontroller/describe +++ b/gcloud/beta/container/fleet/policycontroller/describe @@ -61,8 +61,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller describe $ gcloud alpha container fleet policycontroller describe diff --git a/gcloud/beta/container/fleet/policycontroller/detach b/gcloud/beta/container/fleet/policycontroller/detach index 176a638d1..46ef2aa00 100644 --- a/gcloud/beta/container/fleet/policycontroller/detach +++ b/gcloud/beta/container/fleet/policycontroller/detach @@ -70,8 +70,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller detach $ gcloud alpha container fleet policycontroller detach diff --git a/gcloud/beta/container/fleet/policycontroller/disable b/gcloud/beta/container/fleet/policycontroller/disable index 27c07a27b..0a3fc9330 100644 --- a/gcloud/beta/container/fleet/policycontroller/disable +++ b/gcloud/beta/container/fleet/policycontroller/disable @@ -74,8 +74,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller disable $ gcloud alpha container fleet policycontroller disable diff --git a/gcloud/beta/container/fleet/policycontroller/enable b/gcloud/beta/container/fleet/policycontroller/enable index 545ff52f9..01ad9fca8 100644 --- a/gcloud/beta/container/fleet/policycontroller/enable +++ b/gcloud/beta/container/fleet/policycontroller/enable @@ -172,8 +172,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller enable $ gcloud alpha container fleet policycontroller enable diff --git a/gcloud/beta/container/fleet/policycontroller/help b/gcloud/beta/container/fleet/policycontroller/help index 9ec917c58..2cfceee68 100644 --- a/gcloud/beta/container/fleet/policycontroller/help +++ b/gcloud/beta/container/fleet/policycontroller/help @@ -45,8 +45,10 @@ COMMANDS (BETA) Updates the configuration of Policy Controller Feature. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller $ gcloud alpha container fleet policycontroller diff --git a/gcloud/beta/container/fleet/policycontroller/suspend b/gcloud/beta/container/fleet/policycontroller/suspend index 04cfaf9ea..479a50559 100644 --- a/gcloud/beta/container/fleet/policycontroller/suspend +++ b/gcloud/beta/container/fleet/policycontroller/suspend @@ -70,8 +70,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller suspend $ gcloud alpha container fleet policycontroller suspend diff --git a/gcloud/beta/container/fleet/policycontroller/update b/gcloud/beta/container/fleet/policycontroller/update index 6456977ff..dcdf7811a 100644 --- a/gcloud/beta/container/fleet/policycontroller/update +++ b/gcloud/beta/container/fleet/policycontroller/update @@ -155,8 +155,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet policycontroller update $ gcloud alpha container fleet policycontroller update diff --git a/gcloud/beta/container/hub/policycontroller/content/bundles/help b/gcloud/beta/container/hub/policycontroller/content/bundles/help index b6cd7d217..8c5d686ec 100644 --- a/gcloud/beta/container/hub/policycontroller/content/bundles/help +++ b/gcloud/beta/container/hub/policycontroller/content/bundles/help @@ -24,8 +24,10 @@ COMMANDS (BETA) Sets bundle installation for Policy Controller content. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller content bundles $ gcloud alpha container hub policycontroller content bundles diff --git a/gcloud/beta/container/hub/policycontroller/content/bundles/remove b/gcloud/beta/container/hub/policycontroller/content/bundles/remove index 5eccfa13a..d4db8f296 100644 --- a/gcloud/beta/container/hub/policycontroller/content/bundles/remove +++ b/gcloud/beta/container/hub/policycontroller/content/bundles/remove @@ -71,8 +71,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller content bundles remove $ gcloud alpha container hub policycontroller content bundles remove diff --git a/gcloud/beta/container/hub/policycontroller/content/bundles/set b/gcloud/beta/container/hub/policycontroller/content/bundles/set index d5ac012c7..d51cc24f3 100644 --- a/gcloud/beta/container/hub/policycontroller/content/bundles/set +++ b/gcloud/beta/container/hub/policycontroller/content/bundles/set @@ -102,8 +102,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller content bundles set $ gcloud alpha container hub policycontroller content bundles set diff --git a/gcloud/beta/container/hub/policycontroller/content/help b/gcloud/beta/container/hub/policycontroller/content/help index fa315b6fa..3d217ba9d 100644 --- a/gcloud/beta/container/hub/policycontroller/content/help +++ b/gcloud/beta/container/hub/policycontroller/content/help @@ -24,8 +24,10 @@ GROUPS (BETA) Manage Policy Controller content templates. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller content $ gcloud alpha container hub policycontroller content diff --git a/gcloud/beta/container/hub/policycontroller/content/templates/disable b/gcloud/beta/container/hub/policycontroller/content/templates/disable index 8d79b7144..4c9923742 100644 --- a/gcloud/beta/container/hub/policycontroller/content/templates/disable +++ b/gcloud/beta/container/hub/policycontroller/content/templates/disable @@ -66,8 +66,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller content templates disable $ gcloud alpha container hub policycontroller content templates \ disable diff --git a/gcloud/beta/container/hub/policycontroller/content/templates/enable b/gcloud/beta/container/hub/policycontroller/content/templates/enable index 40318431e..030f619c6 100644 --- a/gcloud/beta/container/hub/policycontroller/content/templates/enable +++ b/gcloud/beta/container/hub/policycontroller/content/templates/enable @@ -66,8 +66,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller content templates enable $ gcloud alpha container hub policycontroller content templates \ enable diff --git a/gcloud/beta/container/hub/policycontroller/content/templates/help b/gcloud/beta/container/hub/policycontroller/content/templates/help index 33870bd82..78c31b08c 100644 --- a/gcloud/beta/container/hub/policycontroller/content/templates/help +++ b/gcloud/beta/container/hub/policycontroller/content/templates/help @@ -24,8 +24,10 @@ COMMANDS (BETA) Installs the template library for Policy Controller. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller content templates $ gcloud alpha container hub policycontroller content templates diff --git a/gcloud/beta/container/hub/policycontroller/deployment/help b/gcloud/beta/container/hub/policycontroller/deployment/help index dc2355300..5ee3404ae 100644 --- a/gcloud/beta/container/hub/policycontroller/deployment/help +++ b/gcloud/beta/container/hub/policycontroller/deployment/help @@ -25,8 +25,10 @@ COMMANDS (BETA) Sets configuration of the Policy Controller components. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller deployment $ gcloud alpha container hub policycontroller deployment diff --git a/gcloud/beta/container/hub/policycontroller/deployment/remove b/gcloud/beta/container/hub/policycontroller/deployment/remove index e8dc3395a..274276e72 100644 --- a/gcloud/beta/container/hub/policycontroller/deployment/remove +++ b/gcloud/beta/container/hub/policycontroller/deployment/remove @@ -129,8 +129,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller deployment remove $ gcloud alpha container hub policycontroller deployment remove diff --git a/gcloud/beta/container/hub/policycontroller/deployment/set b/gcloud/beta/container/hub/policycontroller/deployment/set index 1085774b1..d4b178907 100644 --- a/gcloud/beta/container/hub/policycontroller/deployment/set +++ b/gcloud/beta/container/hub/policycontroller/deployment/set @@ -136,8 +136,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller deployment set $ gcloud alpha container hub policycontroller deployment set diff --git a/gcloud/beta/container/hub/policycontroller/describe b/gcloud/beta/container/hub/policycontroller/describe index 24318f218..434efc25d 100644 --- a/gcloud/beta/container/hub/policycontroller/describe +++ b/gcloud/beta/container/hub/policycontroller/describe @@ -61,8 +61,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller describe $ gcloud alpha container hub policycontroller describe diff --git a/gcloud/beta/container/hub/policycontroller/detach b/gcloud/beta/container/hub/policycontroller/detach index f7e89ec69..b12a356bc 100644 --- a/gcloud/beta/container/hub/policycontroller/detach +++ b/gcloud/beta/container/hub/policycontroller/detach @@ -70,8 +70,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller detach $ gcloud alpha container hub policycontroller detach diff --git a/gcloud/beta/container/hub/policycontroller/disable b/gcloud/beta/container/hub/policycontroller/disable index c1cf2e3c6..d29780a28 100644 --- a/gcloud/beta/container/hub/policycontroller/disable +++ b/gcloud/beta/container/hub/policycontroller/disable @@ -74,8 +74,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller disable $ gcloud alpha container hub policycontroller disable diff --git a/gcloud/beta/container/hub/policycontroller/enable b/gcloud/beta/container/hub/policycontroller/enable index 148954e00..f9b39fdae 100644 --- a/gcloud/beta/container/hub/policycontroller/enable +++ b/gcloud/beta/container/hub/policycontroller/enable @@ -172,8 +172,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller enable $ gcloud alpha container hub policycontroller enable diff --git a/gcloud/beta/container/hub/policycontroller/help b/gcloud/beta/container/hub/policycontroller/help index 7788a9863..a06944641 100644 --- a/gcloud/beta/container/hub/policycontroller/help +++ b/gcloud/beta/container/hub/policycontroller/help @@ -45,8 +45,10 @@ COMMANDS (BETA) Updates the configuration of Policy Controller Feature. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller $ gcloud alpha container hub policycontroller diff --git a/gcloud/beta/container/hub/policycontroller/suspend b/gcloud/beta/container/hub/policycontroller/suspend index e2a5ef96a..2865c9f0e 100644 --- a/gcloud/beta/container/hub/policycontroller/suspend +++ b/gcloud/beta/container/hub/policycontroller/suspend @@ -70,8 +70,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller suspend $ gcloud alpha container hub policycontroller suspend diff --git a/gcloud/beta/container/hub/policycontroller/update b/gcloud/beta/container/hub/policycontroller/update index 5f1f64054..06b10e851 100644 --- a/gcloud/beta/container/hub/policycontroller/update +++ b/gcloud/beta/container/hub/policycontroller/update @@ -154,8 +154,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub policycontroller update $ gcloud alpha container hub policycontroller update diff --git a/gcloud/beta/dataproc/clusters/create b/gcloud/beta/dataproc/clusters/create index 0b8c220d7..5a28fde29 100644 --- a/gcloud/beta/dataproc/clusters/create +++ b/gcloud/beta/dataproc/clusters/create @@ -22,6 +22,7 @@ SYNOPSIS [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] [--master-machine-type=MASTER_MACHINE_TYPE] [--master-min-cpu-platform=PLATFORM] [--max-idle=MAX_IDLE] + [--min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION] [--node-group=NODE_GROUP] [--num-driver-pool-local-ssds=NUM_DRIVER_POOL_LOCAL_SSDS] [--num-master-local-ssds=NUM_MASTER_LOCAL_SSDS] @@ -256,6 +257,13 @@ FLAGS such as "2h" or "1d". See $ gcloud topic datetimes for information on duration formats. + --min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION + Minimum fraction of secondary worker nodes required to create the + cluster. If it is not met, cluster creation will fail. Must be a + decimal value between 0 and 1. The number of required secondary workers + is calculated by ceil(min-secondary-worker-fraction * + num_secondary_workers). Defaults to 0.0001. + --node-group=NODE_GROUP The name of the sole-tenant node group to create the cluster on. Can be a short name ("node-group-name") or in the format diff --git a/gcloud/beta/dataproc/clusters/update b/gcloud/beta/dataproc/clusters/update index ac6e210cb..85d7d5dd3 100644 --- a/gcloud/beta/dataproc/clusters/update +++ b/gcloud/beta/dataproc/clusters/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud beta dataproc clusters update (CLUSTER : --region=REGION) [--async] [--graceful-decommission-timeout=GRACEFUL_DECOMMISSION_TIMEOUT] + [--min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION] [--num-secondary-workers=NUM_SECONDARY_WORKERS] [--num-workers=NUM_WORKERS] [--update-labels=[KEY=VALUE,...]] [--autoscaling-policy=AUTOSCALING_POLICY | --disable-autoscaling] @@ -91,6 +92,12 @@ FLAGS maximum allowed timeout is 1 day. See $ gcloud topic datetimes for information on duration formats. + --min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION + Minimum fraction of new secondary worker nodes added in a scale up + update operation, required to update the cluster. If it is not met, + cluster updation will rollback the addition of secondary workers. Must + be a decimal value between 0 and 1. Defaults to 0.0001. + --num-secondary-workers=NUM_SECONDARY_WORKERS The new number of secondary worker nodes in the cluster. diff --git a/gcloud/beta/dataproc/workflow-templates/create b/gcloud/beta/dataproc/workflow-templates/create index f0f6bdf1a..36deeddbe 100644 --- a/gcloud/beta/dataproc/workflow-templates/create +++ b/gcloud/beta/dataproc/workflow-templates/create @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud beta dataproc workflow-templates create (TEMPLATE : --region=REGION) - [--dag-timeout=DAG_TIMEOUT] [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + [--dag-timeout=DAG_TIMEOUT] [--kms-key=KMS_KEY] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a workflow template. @@ -58,6 +58,9 @@ FLAGS auto-cancelled, such as "10m" or "16h". See $ gcloud topic datetimes for information on duration formats. + --kms-key=KMS_KEY + The KMS key used to encrypt sensitive data in the workflow template. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster index 83be2cd90..765274921 100644 --- a/gcloud/beta/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/beta/dataproc/workflow-templates/set-managed-cluster @@ -16,7 +16,9 @@ SYNOPSIS [--master-boot-disk-type=MASTER_BOOT_DISK_TYPE] [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] [--master-machine-type=MASTER_MACHINE_TYPE] - [--master-min-cpu-platform=PLATFORM] [--node-group=NODE_GROUP] + [--master-min-cpu-platform=PLATFORM] + [--min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION] + [--node-group=NODE_GROUP] [--num-master-local-ssds=NUM_MASTER_LOCAL_SSDS] [--num-masters=NUM_MASTERS] [--num-secondary-worker-local-ssds=NUM_SECONDARY_WORKER_LOCAL_SSDS] @@ -191,6 +193,13 @@ FLAGS which contains the list of available CPU platforms in the zone (see Availability of CPU platforms for more information). + --min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION + Minimum fraction of secondary worker nodes required to create the + cluster. If it is not met, cluster creation will fail. Must be a + decimal value between 0 and 1. The number of required secondary workers + is calculated by ceil(min-secondary-worker-fraction * + num_secondary_workers). Defaults to 0.0001. + --node-group=NODE_GROUP The name of the sole-tenant node group to create the cluster on. Can be a short name ("node-group-name") or in the format diff --git a/gcloud/beta/deploy/apply b/gcloud/beta/deploy/apply index 70ea3e828..3f1920949 100644 --- a/gcloud/beta/deploy/apply +++ b/gcloud/beta/deploy/apply @@ -1,14 +1,14 @@ NAME - gcloud beta deploy apply - applies a yaml configuration containing Deliver - Pipeline(s), Target(s) declarative definitions + gcloud beta deploy apply - applies a yaml configuration containing Delivery + Pipeline(s), Target(s) and Automation(s) declarative definitions SYNOPSIS gcloud beta deploy apply --file=FILE [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Applies a yaml configuration containing Deliver Pipeline(s), - Target(s) declarative definitions. + (BETA) Applies a yaml configuration containing Delivery Pipeline(s), + Target(s) and Automation(s) declarative definitions. EXAMPLES To apply a Cloud Deploy YAML file deploy.yaml: diff --git a/gcloud/beta/deploy/automation-runs/cancel b/gcloud/beta/deploy/automation-runs/cancel new file mode 100644 index 000000000..746e42458 --- /dev/null +++ b/gcloud/beta/deploy/automation-runs/cancel @@ -0,0 +1,80 @@ +NAME + gcloud beta deploy automation-runs cancel - cancels a Cloud Deploy + Automation Run + +SYNOPSIS + gcloud beta deploy automation-runs cancel + (AUTOMATION_RUN + : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Cancels a Cloud Deploy Automation Run. + +EXAMPLES + To cancel an AutomationRun test-run for delivery pipeline test-pipeline in + region us-central1, run: + + $ gcloud beta deploy automation-runs cancel test-run \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation run resource - The name of the AutomationRun. 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 automation_run 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. + + AUTOMATION_RUN + ID of the automation_run or fully qualified identifier for the + automation_run. + + To set the name attribute: + ▸ provide the argument automation_run on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The delivery pipeline associated with the automation_run. + Alternatively, set the property [deploy/delivery-pipeline]. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation_run on the command line with a + fully specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + The Cloud region for the automation_run. Alternatively, set the + property [deploy/region]. + + To set the region attribute: + ▸ provide the argument automation_run on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy automation-runs cancel + + $ gcloud alpha deploy automation-runs cancel + diff --git a/gcloud/beta/deploy/automation-runs/describe b/gcloud/beta/deploy/automation-runs/describe new file mode 100644 index 000000000..daf31f67f --- /dev/null +++ b/gcloud/beta/deploy/automation-runs/describe @@ -0,0 +1,82 @@ +NAME + gcloud beta deploy automation-runs describe - show details for an + Automation Run + +SYNOPSIS + gcloud beta deploy automation-runs describe + (AUTOMATION_RUN + : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show details for a specified automation run. + +EXAMPLES + To show details about a automation run 'test-automationrun', for delivery + pipeline 'test-pipeline', in region 'us-central1', run: + + $ gcloud beta deploy automation-runs describe test-automationrun \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation run resource - The name of the automation run you want to + describe. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument automation_run 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. + + AUTOMATION_RUN + ID of the automation run or fully qualified identifier for the + automation run. + + To set the automation_run attribute: + ▸ provide the argument automation_run on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The name of the Cloud Deploy delivery pipeline. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation_run on the command line with a + fully specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + Location of the automation run. + + To set the region attribute: + ▸ provide the argument automation_run on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy automation-runs describe + + $ gcloud alpha deploy automation-runs describe + diff --git a/gcloud/beta/deploy/automation-runs/help b/gcloud/beta/deploy/automation-runs/help new file mode 100644 index 000000000..a937caa18 --- /dev/null +++ b/gcloud/beta/deploy/automation-runs/help @@ -0,0 +1,35 @@ +NAME + gcloud beta deploy automation-runs - manages AutomationRuns resources for + Cloud Deploy + +SYNOPSIS + gcloud beta deploy automation-runs COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manages AutomationRuns resources for Cloud Deploy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (BETA) Cancels a Cloud Deploy Automation Run. + + describe + (BETA) Show details for an Automation Run. + + list + (BETA) List the Automation Runs. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy automation-runs + + $ gcloud alpha deploy automation-runs + diff --git a/gcloud/beta/deploy/automation-runs/list b/gcloud/beta/deploy/automation-runs/list new file mode 100644 index 000000000..c9967ae75 --- /dev/null +++ b/gcloud/beta/deploy/automation-runs/list @@ -0,0 +1,104 @@ +NAME + gcloud beta deploy automation-runs list - list the Automation Runs + +SYNOPSIS + gcloud beta deploy automation-runs list + [--delivery-pipeline=DELIVERY_PIPELINE --region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List the automation runs for a specified delivery pipeline. + +EXAMPLES + To list the automation runs for delivery pipeline 'test-pipeline' in region + 'us-central1', run: + + $ gcloud beta deploy automation-runs list \ + --delivery-pipeline=test-pipeline --region=us-central1 + +FLAGS + Delivery pipeline resource - The delivery pipeline for which you want to + list the automation runs. 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 --delivery-pipeline on the command line with a + fully specified name; + ◆ set the property deploy/delivery_pipeline with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --delivery-pipeline=DELIVERY_PIPELINE + ID of the delivery_pipeline or fully qualified identifier for the + delivery_pipeline. + + To set the delivery-pipeline attribute: + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + Location of the delivery_pipeline. + + To set the region attribute: + ▸ provide the argument --delivery-pipeline on the command line with + a fully specified name; + ▸ set the property deploy/delivery_pipeline with a fully specified + name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy automation-runs list + + $ gcloud alpha deploy automation-runs list + diff --git a/gcloud/beta/deploy/automations/delete b/gcloud/beta/deploy/automations/delete new file mode 100644 index 000000000..bbdbc61df --- /dev/null +++ b/gcloud/beta/deploy/automations/delete @@ -0,0 +1,78 @@ +NAME + gcloud beta deploy automations delete - deletes a Cloud Deploy Automation + +SYNOPSIS + gcloud beta deploy automations delete + (AUTOMATION : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes a Cloud Deploy Automation. + +EXAMPLES + To delete an automation test-automation for delivery pipeline + test-pipeline, in region us-central1, run: + + $ gcloud beta deploy automations delete test-automation \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation resource - The name of the Automation. 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 automation 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. + + AUTOMATION + ID of the automation or fully qualified identifier for the + automation. + + To set the name attribute: + ▸ provide the argument automation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The delivery pipeline associated with the automation. Alternatively, + set the property [deploy/delivery-pipeline]. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + The Cloud region for the automation. Alternatively, set the property + [deploy/region]. + + To set the region attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy automations delete + + $ gcloud alpha deploy automations delete + diff --git a/gcloud/beta/deploy/automations/describe b/gcloud/beta/deploy/automations/describe new file mode 100644 index 000000000..41fd63a79 --- /dev/null +++ b/gcloud/beta/deploy/automations/describe @@ -0,0 +1,80 @@ +NAME + gcloud beta deploy automations describe - show details for an Automation + +SYNOPSIS + gcloud beta deploy automations describe + (AUTOMATION : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show details for a specified automation. + +EXAMPLES + To show details about an automation 'test-automation', for delivery + pipeline 'test-pipeline', in region 'us-central1', run: + + $ gcloud beta deploy automations describe test-automation \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation resource - The name of the automation you want to describe. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument automation 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. + + AUTOMATION + ID of the automation or fully qualified identifier for the + automation. + + To set the automation attribute: + ▸ provide the argument automation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The name of the Cloud Deploy delivery pipeline. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + Location of the automation. + + To set the region attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy automations describe + + $ gcloud alpha deploy automations describe + diff --git a/gcloud/beta/deploy/automations/export b/gcloud/beta/deploy/automations/export new file mode 100644 index 000000000..77e22fa4c --- /dev/null +++ b/gcloud/beta/deploy/automations/export @@ -0,0 +1,85 @@ +NAME + gcloud beta deploy automations export - returns the YAML definition of the + specified Automation + +SYNOPSIS + gcloud beta deploy automations export + (AUTOMATION : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [--destination=DESTINATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The exported yaml definition can be applied by using the deploy + apply command. + +EXAMPLES + To return the YAML definition of the automation test-automation of delivery + pipeline test-pipeline, in region us-central1, run: + + $ gcloud beta deploy automations export test-automation \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation resource - The name of the Automation. 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 automation 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. + + AUTOMATION + ID of the automation or fully qualified identifier for the + automation. + + To set the name attribute: + ▸ provide the argument automation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The delivery pipeline associated with the automation. Alternatively, + set the property [deploy/delivery-pipeline]. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + The Cloud region for the automation. Alternatively, set the property + [deploy/region]. + + To set the region attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. + +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. These + variants are also available: + + $ gcloud deploy automations export + + $ gcloud alpha deploy automations export + diff --git a/gcloud/beta/deploy/automations/help b/gcloud/beta/deploy/automations/help new file mode 100644 index 000000000..f4aa2c962 --- /dev/null +++ b/gcloud/beta/deploy/automations/help @@ -0,0 +1,38 @@ +NAME + gcloud beta deploy automations - manages Automations resources for Cloud + Deploy + +SYNOPSIS + gcloud beta deploy automations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manages Automations resources for Cloud Deploy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (BETA) Deletes a Cloud Deploy Automation. + + describe + (BETA) Show details for an Automation. + + export + (BETA) Returns the YAML definition of the specified Automation. + + list + (BETA) List the Automations. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy automations + + $ gcloud alpha deploy automations + diff --git a/gcloud/beta/deploy/automations/list b/gcloud/beta/deploy/automations/list new file mode 100644 index 000000000..90a0ab226 --- /dev/null +++ b/gcloud/beta/deploy/automations/list @@ -0,0 +1,104 @@ +NAME + gcloud beta deploy automations list - list the Automations + +SYNOPSIS + gcloud beta deploy automations list + [--delivery-pipeline=DELIVERY_PIPELINE --region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List the automations for a specified delivery pipeline. + +EXAMPLES + To list the automations for delivery pipeline 'test-pipeline' in region + 'us-central1', run: + + $ gcloud beta deploy automations list \ + --delivery-pipeline=test-pipeline --region=us-central1 + +FLAGS + Delivery pipeline resource - The delivery pipeline for which you want to + list the automations. 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 --delivery-pipeline on the command line with a + fully specified name; + ◆ set the property deploy/delivery_pipeline with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --delivery-pipeline=DELIVERY_PIPELINE + ID of the delivery_pipeline or fully qualified identifier for the + delivery_pipeline. + + To set the delivery-pipeline attribute: + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + Location of the delivery_pipeline. + + To set the region attribute: + ▸ provide the argument --delivery-pipeline on the command line with + a fully specified name; + ▸ set the property deploy/delivery_pipeline with a fully specified + name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud deploy automations list + + $ gcloud alpha deploy automations list + diff --git a/gcloud/beta/deploy/help b/gcloud/beta/deploy/help index d7026c384..0c994c1c0 100644 --- a/gcloud/beta/deploy/help +++ b/gcloud/beta/deploy/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + automation-runs + (BETA) Manages AutomationRuns resources for Cloud Deploy. + + automations + (BETA) Manages Automations resources for Cloud Deploy. + delivery-pipelines (BETA) Create and manage Delivery Pipeline resources for Cloud Deploy. @@ -34,8 +40,8 @@ COMMANDS COMMAND is one of the following: apply - (BETA) Applies a yaml configuration containing Deliver Pipeline(s), - Target(s) declarative definitions. + (BETA) Applies a yaml configuration containing Delivery Pipeline(s), + Target(s) and Automation(s) declarative definitions. delete (BETA) Deletes delivery pipeline(s) and target(s) in a yaml diff --git a/gcloud/beta/iam/workforce-pools/create b/gcloud/beta/iam/workforce-pools/create index e5c3ad9df..c54b6196e 100644 --- a/gcloud/beta/iam/workforce-pools/create +++ b/gcloud/beta/iam/workforce-pools/create @@ -5,9 +5,10 @@ NAME SYNOPSIS gcloud beta iam workforce-pools create (WORKFORCE_POOL : --location=LOCATION) --organization=ORGANIZATION - [--async] [--description=DESCRIPTION] [--disabled] - [--display-name=DISPLAY_NAME] [--session-duration=SESSION_DURATION] - [GCLOUD_WIDE_FLAG ...] + [--allowed-services=[domain=DOMAIN]] [--async] + [--description=DESCRIPTION] [--disable-programmatic-signin] + [--disabled] [--display-name=DISPLAY_NAME] + [--session-duration=SESSION_DURATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates a workforce pool under an organization given a valid @@ -58,6 +59,12 @@ REQUIRED FLAGS The parent organization of the workforce pool to create. OPTIONAL FLAGS + --allowed-services=[domain=DOMAIN] + Services allowed for web sign-in with the workforce pool. The flag + accepts multiple values with the key as domain and value as the domain + of the service allowed for web sign-in. If not set, by default all the + services are allowed. + --async Return immediately, without waiting for the operation in progress to complete. @@ -66,6 +73,9 @@ OPTIONAL FLAGS A description for the workforce pool. Cannot exceed 256 characters in length. + --disable-programmatic-signin + Disable programmatic sign-in for workforce pool users. + --disabled Whether or not the workforce pool is disabled. diff --git a/gcloud/beta/iam/workforce-pools/update b/gcloud/beta/iam/workforce-pools/update index 338f5f0a8..9e93837be 100644 --- a/gcloud/beta/iam/workforce-pools/update +++ b/gcloud/beta/iam/workforce-pools/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta iam workforce-pools update (WORKFORCE_POOL : --location=LOCATION) [--async] - [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] + [--description=DESCRIPTION] [--disable-programmatic-signin] + [--disabled] [--display-name=DISPLAY_NAME] [--session-duration=SESSION_DURATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -52,6 +53,13 @@ FLAGS A description for the workforce pool. Cannot exceed 256 characters in length. + --disable-programmatic-signin + Disables the programmatic sign-in for workforce pool users. Specify + --no-disable-security-token-exchange to enable programmatic sign-in. + For more information, refer to Obtain short-lived tokens for workforce + identity federation at + https://cloud.google.com/iam/docs/workforce-obtaining-short-lived-credentials + --disabled Disables the workforce pool. You cannot use a disabled workforce pool to perform new token exchanges or sign-ins using any provider in the diff --git a/gcloud/beta/pubsub/schemas/create b/gcloud/beta/pubsub/schemas/create index 58f8f0daf..7de82652d 100644 --- a/gcloud/beta/pubsub/schemas/create +++ b/gcloud/beta/pubsub/schemas/create @@ -41,8 +41,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --type=TYPE - Type of the schema. TYPE must be one of: avro, protocol-buffer, - type-unspecified. + Type of the schema. TYPE must be one of: avro, protocol-buffer. Schema definition. diff --git a/gcloud/beta/pubsub/schemas/validate-message b/gcloud/beta/pubsub/schemas/validate-message index b83332da2..90f20e625 100644 --- a/gcloud/beta/pubsub/schemas/validate-message +++ b/gcloud/beta/pubsub/schemas/validate-message @@ -32,7 +32,7 @@ REQUIRED FLAGS --message-encoding=MESSAGE_ENCODING The encoding of the message. MESSAGE_ENCODING must be one of: binary, - encoding-unspecified, json. + json. Schema definition. @@ -42,8 +42,7 @@ REQUIRED FLAGS Name or full path of an existing schema. --type=TYPE - Type of inline schema. TYPE must be one of: avro, protocol-buffer, - type-unspecified. + Type of inline schema. TYPE must be one of: avro, protocol-buffer. This flag argument must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/beta/pubsub/schemas/validate-schema b/gcloud/beta/pubsub/schemas/validate-schema index f34278573..6c2b946dd 100644 --- a/gcloud/beta/pubsub/schemas/validate-schema +++ b/gcloud/beta/pubsub/schemas/validate-schema @@ -25,8 +25,7 @@ EXAMPLES REQUIRED FLAGS --type=TYPE - Type of the schema. TYPE must be one of: avro, protocol-buffer, - type-unspecified. + Type of the schema. TYPE must be one of: avro, protocol-buffer. Schema definition. diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 56f8a88eb..eb8a824df 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -2,31 +2,33 @@ NAME gcloud beta run deploy - create or update a Cloud Run service SYNOPSIS - gcloud beta run deploy [[SERVICE] --namespace=NAMESPACE] [--args=[ARG,...]] - [--async] [--command=[COMMAND,...]] [--concurrency=CONCURRENCY] - [--cpu=CPU] [--ingress=INGRESS; default="all"] - [--max-instances=MAX_INSTANCES] [--memory=MEMORY] + 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"] [--port=PORT] + [--platform=PLATFORM; default="managed"] [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] - [--no-traffic] [--[no-]use-http2] - [--clear-env-vars | --env-vars-file=FILE_PATH - | --set-env-vars=[KEY=VALUE,...] - | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] + [--no-traffic] + [--args=[ARG,...] --command=[COMMAND,...] --cpu=CPU + --depends-on=[CONTAINER,...] + --memory=MEMORY --port=PORT --[no-]use-http2 --clear-env-vars + | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] + | --remove-env-vars=[KEY,...] + --update-env-vars=[KEY=VALUE,...] --clear-secrets + | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] + --update-secrets=[KEY=VALUE,...] --image=IMAGE | --source=SOURCE] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] - [--clear-secrets | --set-secrets=[KEY=VALUE,...] - | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--connectivity=CONNECTIVITY --clear-config-maps | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] --update-config-maps=[KEY=VALUE,...]] - [--image=IMAGE | --source=SOURCE] [--[no-]allow-unauthenticated --breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT - --revision-suffix=REVISION_SUFFIX --[no-]session-affinity - --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS + --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX + --[no-]session-affinity --vpc-connector=VPC_CONNECTOR + --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -93,35 +95,18 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --args=[ARG,...] - Comma-separated arguments passed to the command run by the container - image. If not specified and no '--command' is provided, the container - image's default Cmd is used. Otherwise, if not specified, no arguments - are passed. To reset this field to its default, pass an empty string. - --async Return immediately, without waiting for the operation in progress to complete. - --command=[COMMAND,...] - Entrypoint for the container image. If not specified, the container - image's default Entrypoint is run. To reset this field to its default, - pass an empty string. - --concurrency=CONCURRENCY Set the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified or provide the special value 'default' to receive the server default value. - --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 + --container=CONTAINER + Specifies a container by name. Flags following --container will apply + to the specified container. --ingress=INGRESS; default="all" Set the ingress traffic sources allowed to call the service. For Cloud @@ -151,9 +136,6 @@ FLAGS The maximum number of container instances of the Service to run. Use 'default' to unset the limit and use the platform default. - --memory=MEMORY - Set a memory limit. Ex: 1024Mi, 4Gi. - --min-instances=MIN_INSTANCES The minimum number of container instances for this Revision of the Service to run or 'default' to remove any minimum. @@ -175,13 +157,6 @@ FLAGS --kubeconfig and --context flags to specify a kubeconfig file and the context for connecting. - --port=PORT - Container port to receive requests at. Also sets the $PORT environment - variable. Must be a number between 1 and 65535, inclusive. To unset - this field, pass the special value "default". If updating an existing - service with a TCP startup probe pointing to the previous container - port, this will also update the probe port. - --service-account=SERVICE_ACCOUNT Service account associated with the revision of the service. The service account represents the identity of the running revision, and @@ -212,35 +187,126 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. - --[no-]use-http2 - Whether to use HTTP/2 for connections to the service. Use --use-http2 - to enable and --no-use-http2 to disable. + Container Flags - At most one of these can be specified: + The following flags apply to a single container. If the --container flag is specified these flags may only be + specified after a --container flag. Otherwise they will apply to the primary ingress container. - --clear-env-vars - Remove all environment variables. + --args=[ARG,...] + Comma-separated arguments passed to the command run by the + container image. If not specified and no '--command' is provided, + the container image's default Cmd is used. Otherwise, if not + specified, no arguments are passed. To reset this field to its + default, pass an empty string. - --env-vars-file=FILE_PATH - Path to a local YAML file with definitions for all environment - variables. All existing environment variables will be removed before - the new environment variables are added. Example YAML content: + --command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default Entrypoint is run. To reset this field to its + default, pass an empty string. - KEY_1: "value1" - KEY_2: "value 2" + --cpu=CPU + Set a CPU limit in Kubernetes cpu units. - --set-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. All existing - environment variables will be removed first. + 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 - Only --update-env-vars and --remove-env-vars can be used together. If - both are specified, --remove-env-vars will be applied first. + Cloud Run for Anthos and Knative-compatible Kubernetes clusters + support fractional values. Examples .5, 500m, 2 - --remove-env-vars=[KEY,...] - List of environment variables to be removed. + --depends-on=[CONTAINER,...] + List of container dependencies to add to the current container. - --update-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. + + --port=PORT + Container port to receive requests at. Also sets the $PORT + environment variable. Must be a number between 1 and 65535, + inclusive. To unset this field, pass the special value "default". + If updating an existing service with a TCP startup probe pointing + to the previous container port, this will also update the probe + port. + + --[no-]use-http2 + Whether to use HTTP/2 for connections to the service. Use + --use-http2 to enable and --no-use-http2 to disable. + + At most one of these can be specified: + + --clear-env-vars + Remove all environment variables. + + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed + before the new environment variables are added. Example YAML + content: + + KEY_1: "value1" + KEY_2: "value 2" + + --set-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. All + existing environment variables will be removed first. + + Only --update-env-vars and --remove-env-vars can be used together. + If both are specified, --remove-env-vars will be applied first. + + --remove-env-vars=[KEY,...] + List of environment variables to be removed. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + Specify secrets to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. Values should be in the form + SECRET_NAME:SECRET_VERSION. For example: + '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' + will mount a volume at '/secrets/api' containing a file 'key' with the + latest version of secret 'mysecret'. An environment variable named ENV + will also be created whose value is version 1 of secret 'othersecret'. + + At most one of these can be specified: + + --clear-secrets + Remove all secrets. + + --set-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. All existing secrets + will be removed first. + + Only --update-secrets and --remove-secrets can be used together. If + both are specified, --remove-secrets will be applied first. + + --remove-secrets=[KEY,...] + List of secrets to be removed. + + --update-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. + + At most one of these can be specified: + + --image=IMAGE + Name of the container image to deploy (e.g. + gcr.io/cloudrun/hello:latest). + + --source=SOURCE + The location of the source to build. If a Dockerfile is present + in the source code directory, it will be built using that + Dockerfile, otherwise it will use Google Cloud buildpacks. See + https://cloud.google.com/run/docs/deploying-source-code for more + details. The location can be a directory on a local disk or a + gzipped archive file (.tar.gz) in Google Cloud Storage. If the + source is a local directory, this command skips the files + specified in the --ignore-file. If --ignore-file is not + specified, use .gcloudignore file. If a .gcloudignore file is + absent and a .gitignore file is present in the local source + directory, gcloud will use a generated Git-compatible + .gcloudignore file that respects your .gitignored files. The + global .gitignore is not respected. For more information on + .gcloudignore, see gcloud topic gcloudignore. At most one of these can be specified: @@ -273,33 +339,6 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. - Specify secrets to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. Values should be in the form - SECRET_NAME:SECRET_VERSION. For example: - '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' will - mount a volume at '/secrets/api' containing a file 'key' with the latest - version of secret 'mysecret'. An environment variable named ENV will also - be created whose value is version 1 of secret 'othersecret'. - - At most one of these can be specified: - - --clear-secrets - Remove all secrets. - - --set-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. All existing secrets will - be removed first. - - Only --update-secrets and --remove-secrets can be used together. If both - are specified, --remove-secrets will be applied first. - - --remove-secrets=[KEY,...] - List of secrets to be removed. - - --update-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. - 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: @@ -350,27 +389,6 @@ FLAGS --update-config-maps=[KEY=VALUE,...] List of key-value pairs to set as config-maps. - At most one of these can be specified: - - --image=IMAGE - Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). - - --source=SOURCE - The location of the source to build. If a Dockerfile is present in - the source code directory, it will be built using that Dockerfile, - otherwise it will use Google Cloud buildpacks. See - https://cloud.google.com/run/docs/deploying-source-code for more - details. The location can be a directory on a local disk or a gzipped - archive file (.tar.gz) in Google Cloud Storage. If the source is a - local directory, this command skips the files specified in the - --ignore-file. If --ignore-file is not specified, use .gcloudignore - file. If a .gcloudignore file is absent and a .gitignore file is - present in the local source directory, gcloud will use a generated - Git-compatible .gcloudignore file that respects your .gitignored - files. The global .gitignore is not respected. For more information - on .gcloudignore, see gcloud topic gcloudignore. - Only applicable if connecting to Cloud Run (fully managed). Specify --platform=managed to use: @@ -412,6 +430,9 @@ FLAGS gen2 Run the application in a second generation execution environment. + --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 @@ -581,35 +602,36 @@ FLAGS 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. + ▸ 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. + --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. + 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]. + --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. + 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: diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 87ea0aa1e..1897024b2 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -3,18 +3,26 @@ NAME and other configuration settings SYNOPSIS - gcloud beta run services update [[SERVICE] --namespace=NAMESPACE] - [--args=[ARG,...]] [--async] [--command=[COMMAND,...]] - [--concurrency=CONCURRENCY] [--cpu=CPU] [--image=IMAGE] + gcloud beta run services update [[SERVICE] --namespace=NAMESPACE] [--async] + [--concurrency=CONCURRENCY] [--container=CONTAINER] [--ingress=INGRESS; default="all"] [--max-instances=MAX_INSTANCES] - [--memory=MEMORY] [--min-instances=MIN_INSTANCES] - [--platform=PLATFORM; default="managed"] [--port=PORT] + [--min-instances=MIN_INSTANCES] + [--platform=PLATFORM; default="managed"] [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] - [--no-traffic] [--[no-]use-http2] + [--no-traffic] + [--args=[ARG,...] --command=[COMMAND,...] --cpu=CPU + --depends-on=[CONTAINER,...] --image=IMAGE + --memory=MEMORY --port=PORT --[no-]use-http2 --clear-env-vars + | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] + | --remove-env-vars=[KEY,...] + --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 - --revision-suffix=REVISION_SUFFIX --[no-]session-affinity - --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS + --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX + --[no-]session-affinity --vpc-connector=VPC_CONNECTOR + --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --clear-cloudsql-instances | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -30,13 +38,8 @@ SYNOPSIS | --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] - [--clear-env-vars | --env-vars-file=FILE_PATH - | --set-env-vars=[KEY=VALUE,...] - | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] - [--clear-secrets | --set-secrets=[KEY=VALUE,...] - | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] [--connectivity=CONNECTIVITY --clear-config-maps | --set-config-maps=[KEY=VALUE,...] | --remove-config-maps=[KEY,...] --update-config-maps=[KEY=VALUE,...]] @@ -82,39 +85,18 @@ POSITIONAL ARGUMENTS ▸ set the property core/project. FLAGS - --args=[ARG,...] - Comma-separated arguments passed to the command run by the container - image. If not specified and no '--command' is provided, the container - image's default Cmd is used. Otherwise, if not specified, no arguments - are passed. To reset this field to its default, pass an empty string. - --async Return immediately, without waiting for the operation in progress to complete. - --command=[COMMAND,...] - Entrypoint for the container image. If not specified, the container - image's default Entrypoint is run. To reset this field to its default, - pass an empty string. - --concurrency=CONCURRENCY Set the maximum number of concurrent requests allowed per container instance. Leave concurrency unspecified or provide the special value 'default' to receive the server default value. - --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 - - --image=IMAGE - Name of the container image to deploy (e.g. - gcr.io/cloudrun/hello:latest). + --container=CONTAINER + Specifies a container by name. Flags following --container will apply + to the specified container. --ingress=INGRESS; default="all" Set the ingress traffic sources allowed to call the service. For Cloud @@ -144,9 +126,6 @@ FLAGS The maximum number of container instances of the Service to run. Use 'default' to unset the limit and use the platform default. - --memory=MEMORY - Set a memory limit. Ex: 1024Mi, 4Gi. - --min-instances=MIN_INSTANCES The minimum number of container instances for this Revision of the Service to run or 'default' to remove any minimum. @@ -168,13 +147,6 @@ FLAGS --kubeconfig and --context flags to specify a kubeconfig file and the context for connecting. - --port=PORT - Container port to receive requests at. Also sets the $PORT environment - variable. Must be a number between 1 and 65535, inclusive. To unset - this field, pass the special value "default". If updating an existing - service with a TCP startup probe pointing to the previous container - port, this will also update the probe port. - --service-account=SERVICE_ACCOUNT Service account associated with the revision of the service. The service account represents the identity of the running revision, and @@ -205,9 +177,106 @@ FLAGS revision by default, run the gcloud run services update-traffic command with --to-latest. - --[no-]use-http2 - Whether to use HTTP/2 for connections to the service. Use --use-http2 - to enable and --no-use-http2 to disable. + If the --container or --remove-containers flag is specified the following + arguments may only be specified after a --container flag. + + --args=[ARG,...] + Comma-separated arguments passed to the command run by the + container image. If not specified and no '--command' is provided, + the container image's default Cmd is used. Otherwise, if not + specified, no arguments are passed. To reset this field to its + default, pass an empty string. + + --command=[COMMAND,...] + Entrypoint for the container image. If not specified, the container + image's default Entrypoint is run. To reset this field to its + default, pass an empty string. + + --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 + + --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). + + --memory=MEMORY + Set a memory limit. Ex: 1024Mi, 4Gi. + + --port=PORT + Container port to receive requests at. Also sets the $PORT + environment variable. Must be a number between 1 and 65535, + inclusive. To unset this field, pass the special value "default". + If updating an existing service with a TCP startup probe pointing + to the previous container port, this will also update the probe + port. + + --[no-]use-http2 + Whether to use HTTP/2 for connections to the service. Use + --use-http2 to enable and --no-use-http2 to disable. + + At most one of these can be specified: + + --clear-env-vars + Remove all environment variables. + + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed + before the new environment variables are added. Example YAML + content: + + KEY_1: "value1" + KEY_2: "value 2" + + --set-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. All + existing environment variables will be removed first. + + Only --update-env-vars and --remove-env-vars can be used together. + If both are specified, --remove-env-vars will be applied first. + + --remove-env-vars=[KEY,...] + List of environment variables to be removed. + + --update-env-vars=[KEY=VALUE,...] + List of key-value pairs to set as environment variables. + + Specify secrets to mount or provide as environment variables. Keys + starting with a forward slash '/' are mount paths. All other keys + correspond to environment variables. Values should be in the form + SECRET_NAME:SECRET_VERSION. For example: + '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' + will mount a volume at '/secrets/api' containing a file 'key' with the + latest version of secret 'mysecret'. An environment variable named ENV + will also be created whose value is version 1 of secret 'othersecret'. + + At most one of these can be specified: + + --clear-secrets + Remove all secrets. + + --set-secrets=[KEY=VALUE,...] + List of key-value pairs to set as secrets. All existing secrets + will be removed first. + + Only --update-secrets and --remove-secrets can be used together. If + both are specified, --remove-secrets will be applied first. + + --remove-secrets=[KEY,...] + List of secrets to be removed. + + --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: @@ -241,6 +310,9 @@ FLAGS gen2 Run the application in a second generation execution environment. + --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 @@ -390,32 +462,6 @@ FLAGS No new instances will be started and the existing instances will be shut down after CMEK key revocation. - At most one of these can be specified: - - --clear-env-vars - Remove all environment variables. - - --env-vars-file=FILE_PATH - Path to a local YAML file with definitions for all environment - variables. All existing environment variables will be removed before - the new environment variables are added. Example YAML content: - - KEY_1: "value1" - KEY_2: "value 2" - - --set-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. All existing - environment variables will be removed first. - - Only --update-env-vars and --remove-env-vars can be used together. If - both are specified, --remove-env-vars will be applied first. - - --remove-env-vars=[KEY,...] - List of environment variables to be removed. - - --update-env-vars=[KEY=VALUE,...] - List of key-value pairs to set as environment variables. - At most one of these can be specified: --clear-labels @@ -447,33 +493,6 @@ FLAGS List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. - Specify secrets to mount or provide as environment variables. Keys - starting with a forward slash '/' are mount paths. All other keys - correspond to environment variables. Values should be in the form - SECRET_NAME:SECRET_VERSION. For example: - '--update-secrets=/secrets/api/key=mysecret:latest,ENV=othersecret:1' will - mount a volume at '/secrets/api' containing a file 'key' with the latest - version of secret 'mysecret'. An environment variable named ENV will also - be created whose value is version 1 of secret 'othersecret'. - - At most one of these can be specified: - - --clear-secrets - Remove all secrets. - - --set-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. All existing secrets will - be removed first. - - Only --update-secrets and --remove-secrets can be used together. If both - are specified, --remove-secrets will be applied first. - - --remove-secrets=[KEY,...] - List of secrets to be removed. - - --update-secrets=[KEY=VALUE,...] - List of key-value pairs to set as secrets. - 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: @@ -544,35 +563,36 @@ FLAGS 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. + ▸ 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. + --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. + 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]. + --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. + 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: diff --git a/gcloud/beta/spanner/instances/create b/gcloud/beta/spanner/instances/create index c8cf891e2..010514b06 100644 --- a/gcloud/beta/spanner/instances/create +++ b/gcloud/beta/spanner/instances/create @@ -68,7 +68,7 @@ OPTIONAL FLAGS --processing-units=PROCESSING_UNITS Number of processing units for the instance. - Autoscaling + Autoscaling (Preview) --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET Specifies the target percentage of high-priority CPU the autoscaled diff --git a/gcloud/beta/spanner/instances/update b/gcloud/beta/spanner/instances/update index 4da8d0779..11464e532 100644 --- a/gcloud/beta/spanner/instances/update +++ b/gcloud/beta/spanner/instances/update @@ -65,7 +65,7 @@ FLAGS --processing-units=PROCESSING_UNITS Number of processing units for the instance. - Autoscaling + Autoscaling (Preview) --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET Specifies the target percentage of high-priority CPU the autoscaled diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index 21f1a10dc..bf99f633e 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -12,9 +12,9 @@ SYNOPSIS [--authorized-networks=NETWORK,[NETWORK,...]] [--availability-type=AVAILABILITY_TYPE] [--no-backup] [--backup-location=BACKUP_LOCATION] - [--backup-start-time=BACKUP_START_TIME] [--collation=COLLATION] - [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] - [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--backup-start-time=BACKUP_START_TIME] [--cascadable-replica] + [--collation=COLLATION] [--connector-enforcement=CONNECTOR_ENFORCEMENT] + [--cpu=CPU] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--database-version=DATABASE_VERSION; default="MYSQL_8_0"] [--[no-]deletion-protection] [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] @@ -169,6 +169,13 @@ FLAGS Start time of daily backups, specified in the HH:MM format, in the UTC timezone. + --cascadable-replica + Specifies whether a SQL Server replica is a cascadable replica. A + cascadable replica is a SQL Server cross-region replica that supports + replica(s) under it. This flag only takes effect when the + --master-instance-name flag is set, and the replica under creation is + in a different region than the primary instance. + --collation=COLLATION Cloud SQL server-level collation setting, which specifies the set of rules for comparing characters in a character set. diff --git a/gcloud/beta/sql/instances/help b/gcloud/beta/sql/instances/help index ef914c422..c8832bf9c 100644 --- a/gcloud/beta/sql/instances/help +++ b/gcloud/beta/sql/instances/help @@ -65,6 +65,9 @@ COMMANDS restore-backup (BETA) Restores a backup of a Cloud SQL instance. + switchover + (BETA) Switches over a Cloud SQL instance to one of its replicas. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/sql/instances/promote-replica b/gcloud/beta/sql/instances/promote-replica index 4a9f20919..c5ac42a1c 100644 --- a/gcloud/beta/sql/instances/promote-replica +++ b/gcloud/beta/sql/instances/promote-replica @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta sql instances promote-replica REPLICA [--async] - [GCLOUD_WIDE_FLAG ...] + [--[no-]failover] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Promotes Cloud SQL read replica to a stand-alone instance. @@ -18,6 +18,10 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --[no-]failover + Whether the promote operation is a failover. Use --failover to enable + and --no-failover to disable. + 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/sql/instances/switchover b/gcloud/beta/sql/instances/switchover new file mode 100644 index 000000000..3a3915f15 --- /dev/null +++ b/gcloud/beta/sql/instances/switchover @@ -0,0 +1,40 @@ +NAME + gcloud beta sql instances switchover - switches over a Cloud SQL instance + to one of its replicas + +SYNOPSIS + gcloud beta sql instances switchover REPLICA [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Switches over a Cloud SQL instance to one of its replicas. Currently + only supported on Cloud SQL for SQL Server instances. + +EXAMPLES + To switch over an instance to its replica called replica-instance: + + $ gcloud beta sql instances switchover replica-instance + +POSITIONAL ARGUMENTS + REPLICA + Cloud SQL replica ID. + +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 sql instances switchover + diff --git a/gcloud/builds/triggers/update/pubsub b/gcloud/builds/triggers/update/pubsub index e1972e16a..165ac61ca 100644 --- a/gcloud/builds/triggers/update/pubsub +++ b/gcloud/builds/triggers/update/pubsub @@ -6,8 +6,8 @@ SYNOPSIS gcloud builds triggers update pubsub (TRIGGER : --region=REGION) (--trigger-config=PATH | --description=DESCRIPTION --[no-]require-approval --service-account=SERVICE_ACCOUNT - --subscription-filter=SUBSCRIPTION_FILTER - --topic=TOPIC --clear-substitutions + --topic=TOPIC --clear-subscription-filter + | --subscription-filter=SUBSCRIPTION_FILTER --clear-substitutions | --remove-substitutions=[KEY,...] | --update-substitutions=[KEY=VALUE,...] --inline-config=PATH | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR @@ -90,14 +90,19 @@ REQUIRED FLAGS used instead. Format: projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. - --subscription-filter=SUBSCRIPTION_FILTER - CEL filter expression for the trigger. See - https://cloud.google.com/build/docs/filter-build-events-using-cel - for more details. - --topic=TOPIC The topic to which this trigger should subscribe. + At most one of these can be specified: + + --clear-subscription-filter + Clear existing subscription filter. + + --subscription-filter=SUBSCRIPTION_FILTER + CEL filter expression for the trigger. See + https://cloud.google.com/build/docs/filter-build-events-using-cel + for more details. + At most one of these can be specified: --clear-substitutions diff --git a/gcloud/certificate-manager/trust-configs/import b/gcloud/certificate-manager/trust-configs/import index 3195e07c3..80b5ba16d 100644 --- a/gcloud/certificate-manager/trust-configs/import +++ b/gcloud/certificate-manager/trust-configs/import @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud certificate-manager trust-configs import (TRUST_CONFIG : --location=LOCATION) [--async] [--source=SOURCE] - [GCLOUD_WIDE_FLAG ...] + [--update-mask=UPDATE_MASK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Import a TrustConfig. @@ -63,6 +63,13 @@ FLAGS $ gcloud info --format='value(installation.sdk_root)' + --update-mask=UPDATE_MASK + Update mask used to specify fields to be overwritten in the TrustConfig + by import. TrustConfig must already exist. Fields specified in the + update-mask are relative to the TrustConfig. The flag can be a + comma-separated list of updatable non-nested fields, e.g. description + or trust_stores. Valid example: --update-mask=description,trust_stores. + 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/compute/help b/gcloud/compute/help index 53705a750..660313e05 100644 --- a/gcloud/compute/help +++ b/gcloud/compute/help @@ -150,6 +150,9 @@ GROUPS shared-vpc Configure shared VPC. + snapshot-settings + Describe and update Compute Engine snapshot settings. + snapshots List, describe, and delete Compute Engine snapshots. diff --git a/gcloud/compute/instances/network-interfaces/update b/gcloud/compute/instances/network-interfaces/update index b9f566e5f..f2e9c9049 100644 --- a/gcloud/compute/instances/network-interfaces/update +++ b/gcloud/compute/instances/network-interfaces/update @@ -10,8 +10,11 @@ SYNOPSIS [--internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH] [--ipv6-network-tier=IPV6_NETWORK_TIER] [--network=NETWORK] [--network-interface=NETWORK_INTERFACE; default="nic0"] - [--private-network-ip=PRIVATE_NETWORK_IP] [--stack-type=STACK_TYPE] - [--subnetwork=SUBNETWORK] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--private-network-ip=PRIVATE_NETWORK_IP] + [--security-policy=SECURITY_POLICY] + [--security-policy-region=SECURITY_POLICY_REGION] + [--stack-type=STACK_TYPE] [--subnetwork=SUBNETWORK] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute instances network-interfaces update updates network @@ -91,6 +94,15 @@ FLAGS available in the new subnetwork, then another available IP address will be allocated automatically from the new subnetwork CIDR range. + --security-policy=SECURITY_POLICY + The security policy that will be set for this instance network + interface. To remove the policy from this instance network interface + set the policy to an empty string. + + --security-policy-region=SECURITY_POLICY_REGION + Region of the security policy to operate on. Overrides the default + compute/region property value for this command invocation. + --stack-type=STACK_TYPE The stack type for the default network interface. Determines if IPv6 is enabled on the default network interface. STACK_TYPE must be one of: diff --git a/gcloud/compute/networks/vpc-access/connectors/create b/gcloud/compute/networks/vpc-access/connectors/create index 9806b51eb..a07af946d 100644 --- a/gcloud/compute/networks/vpc-access/connectors/create +++ b/gcloud/compute/networks/vpc-access/connectors/create @@ -89,16 +89,22 @@ FLAGS throughput. --max-throughput=MAX_THROUGHPUT - Maximum throughput in Mbps. Value must be a multiple of 100 from - 300 through 1000. Must be higher than the value specified by - --min-throughput; the set value, if applicable, or the default - minimum throughput value. + Maximum throughput of the connector in Mbps. Refers to the expected + throughput when using an e2-micro machine type. Value must be a + multiple of 100 from 300 through 1000. Must be higher than the + value specified by --min-throughput. If both max-throughput and + max-instances are provided, max-instances takes precedence over + max-throughput. The use of max-throughput is discouraged in favor + of max-instances. --min-throughput=MIN_THROUGHPUT - Minimum throughput in Mbps. Value must be a multiple of 100 from - 200 through 900. Must be lower than the value specified by - --max-throughput; the set value, if applicable, or the default - maximum throughput value. + Minimum throughput of the connector in Mbps. Refers to the expected + throughput when using an e2-micro machine type. Value must be a + multiple of 100 from 200 through 900. Must be lower than the value + specified by --max-throughput. If both min-throughput and + min-instances are provided, min-instances takes precedence over + min-throughput. The use of min-throughput is discouraged in favor + of min-instances. At most one of these can be specified: diff --git a/gcloud/compute/security-policies/add-user-defined-field b/gcloud/compute/security-policies/add-user-defined-field new file mode 100644 index 000000000..88fbe0d2c --- /dev/null +++ b/gcloud/compute/security-policies/add-user-defined-field @@ -0,0 +1,64 @@ +NAME + gcloud compute security-policies add-user-defined-field - add a user + defined field to a Compute Engine security policy + +SYNOPSIS + gcloud compute security-policies add-user-defined-field NAME --base=BASE + --offset=OFFSET --size=SIZE + --user-defined-field-name=USER_DEFINED_FIELD_NAME [--mask=MASK] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute security-policies add-user-defined-field is used to add user + defined fields to security policies. + +EXAMPLES + To add a user defined field run this: + + $ gcloud compute security-policies add-user-defined-field \ + SECURITY_POLICY --user-defined-field-name=my-field --base=ipv6 \ + --offset=10 --size=3 + +POSITIONAL ARGUMENTS + NAME + Name of the security policy to update. + +REQUIRED FLAGS + --base=BASE + The base relative to which offset is measured. BASE must be one of: + ipv4, ipv6, tcp, udp. + + --offset=OFFSET + Offset of the first byte of the field (in network byte order) relative + to base. + + --size=SIZE + Size of the field in bytes. Valid values: 1-4. + + --user-defined-field-name=USER_DEFINED_FIELD_NAME + The name for the user defined field. + +OPTIONAL FLAGS + --mask=MASK + If specified, apply this mask (bitwise AND) to the field to ignore bits + before matching. Encoded as a hexadecimal number (starting with "0x"). + + --region=REGION + Region of the security policy to update. Overrides the default + compute/region property value for this command invocation. + +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 + These variants are also available: + + $ gcloud alpha compute security-policies add-user-defined-field + + $ gcloud beta compute security-policies add-user-defined-field + diff --git a/gcloud/compute/security-policies/help b/gcloud/compute/security-policies/help index b4859747f..e36e9d4c9 100644 --- a/gcloud/compute/security-policies/help +++ b/gcloud/compute/security-policies/help @@ -36,6 +36,9 @@ COMMANDS Add a layer7 ddos defense threshold config to a Compute Engine security policy. + add-user-defined-field + Add a user defined field to a Compute Engine security policy. + create Create a Compute Engine security policy. @@ -61,6 +64,9 @@ COMMANDS Remove a layer7 ddos defense threshold config from a Compute Engine security policy. + remove-user-defined-field + Remove a user defined field from a Compute Engine security policy. + update Update a Compute Engine security policy. diff --git a/gcloud/compute/security-policies/remove-user-defined-field b/gcloud/compute/security-policies/remove-user-defined-field new file mode 100644 index 000000000..32b36c10f --- /dev/null +++ b/gcloud/compute/security-policies/remove-user-defined-field @@ -0,0 +1,47 @@ +NAME + gcloud compute security-policies remove-user-defined-field - remove a user + defined field from a Compute Engine security policy + +SYNOPSIS + gcloud compute security-policies remove-user-defined-field NAME + --user-defined-field-name=USER_DEFINED_FIELD_NAME [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute security-policies remove-user-defined-field is used to + remove user defined fields from security policies. + +EXAMPLES + To remove a user defined field run this: + + $ gcloud compute security-policies remove-user-defined-field \ + SECURITY_POLICY --user-defined-field-name=my-field + +POSITIONAL ARGUMENTS + NAME + Name of the security policy to update. + +REQUIRED FLAGS + --user-defined-field-name=USER_DEFINED_FIELD_NAME + The name of the user defined field to remove. + +OPTIONAL FLAGS + --region=REGION + Region of the security policy to update. Overrides the default + compute/region property value for this command invocation. + +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 + These variants are also available: + + $ gcloud alpha compute security-policies remove-user-defined-field + + $ gcloud beta compute security-policies remove-user-defined-field + diff --git a/gcloud/compute/security-policies/rules/create b/gcloud/compute/security-policies/rules/create index 9ad410316..0ef08eddd 100644 --- a/gcloud/compute/security-policies/rules/create +++ b/gcloud/compute/security-policies/rules/create @@ -4,7 +4,15 @@ NAME SYNOPSIS gcloud compute security-policies rules create PRIORITY --action=ACTION - (--expression=EXPRESSION | --src-ip-ranges=[SRC_IP_RANGE,...]) + (--expression=EXPRESSION --network-dest-ip-ranges=[DEST_IP_RANGE,...] + --network-dest-ports=[DEST_PORT,...] + --network-ip-protocols=[IP_PROTOCOL,...] + --network-src-asns=[SRC_ASN,...] + --network-src-ip-ranges=[SRC_IP_RANGE,...] + --network-src-ports=[SRC_PORT,...] + --network-src-region-codes=[SRC_REGION_CODE,...] + --network-user-defined-fields=[NAME;VALUE:VALUE:...,...] + --src-ip-ranges=[SRC_IP_RANGE,...]) [--ban-duration-sec=BAN_DURATION_SEC] [--ban-threshold-count=BAN_THRESHOLD_COUNT] [--ban-threshold-interval-sec=BAN_THRESHOLD_INTERVAL_SEC] @@ -75,11 +83,48 @@ REQUIRED FLAGS Security policy rule matcher. - Exactly one of these must be specified: + At least one of these must be specified: --expression=EXPRESSION The Cloud Armor rules language expression to match for this rule. + --network-dest-ip-ranges=[DEST_IP_RANGE,...] + The destination IPs/IP ranges to match for this rule. To match all + IPs specify *. + + --network-dest-ports=[DEST_PORT,...] + The destination ports to match for this rule. Each element can be an + 16-bit unsigned decimal number (e.g. "80") or range (e.g."0-1023"), + To match all destination ports specify *. + + --network-ip-protocols=[IP_PROTOCOL,...] + The IP protocols to match for this rule. Each element can be an 8-bit + unsigned decimal number (e.g. "6"), range (e.g."253-254"), or one of + the following protocol names: "tcp", "udp", "icmp", "esp", "ah", + "ipip", or "sctp". To match all protocols specify *. + + --network-src-asns=[SRC_ASN,...] + BGP Autonomous System Number associated with the source IP address to + match for this rule. + + --network-src-ip-ranges=[SRC_IP_RANGE,...] + The source IPs/IP ranges to match for this rule. To match all IPs + specify *. + + --network-src-ports=[SRC_PORT,...] + The source ports to match for this rule. Each element can be an + 16-bit unsigned decimal number (e.g. "80") or range (e.g."0-1023"), + To match all source ports specify *. + + --network-src-region-codes=[SRC_REGION_CODE,...] + The two letter ISO 3166-1 alpha-2 country code associated with the + source IP address to match for this rule. To match all region codes + specify *. + + --network-user-defined-fields=[NAME;VALUE:VALUE:...,...] + Each element names a defined field and lists the matching values for + that field. + --src-ip-ranges=[SRC_IP_RANGE,...] The source IPs/IP ranges to match for this rule. To match all IPs specify *. diff --git a/gcloud/compute/security-policies/rules/update b/gcloud/compute/security-policies/rules/update index 0722b21ba..255c8b762 100644 --- a/gcloud/compute/security-policies/rules/update +++ b/gcloud/compute/security-policies/rules/update @@ -22,8 +22,15 @@ SYNOPSIS [--region=REGION] [--request-headers-to-add=[REQUEST_HEADERS_TO_ADD,...]] [--security-policy=SECURITY_POLICY] - [--expression=EXPRESSION | --src-ip-ranges=[SRC_IP_RANGE,...]] - [GCLOUD_WIDE_FLAG ...] + [--expression=EXPRESSION --network-dest-ip-ranges=[DEST_IP_RANGE,...] + --network-dest-ports=[DEST_PORT,...] + --network-ip-protocols=[IP_PROTOCOL,...] + --network-src-asns=[SRC_ASN,...] + --network-src-ip-ranges=[SRC_IP_RANGE,...] + --network-src-ports=[SRC_PORT,...] + --network-src-region-codes=[SRC_REGION_CODE,...] + --network-user-defined-fields=[NAME;VALUE:VALUE:...,...] + --src-ip-ranges=[SRC_IP_RANGE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute security-policies rules update is used to update security @@ -211,11 +218,46 @@ FLAGS Security policy rule matcher. - At most one of these can be specified: - --expression=EXPRESSION The Cloud Armor rules language expression to match for this rule. + --network-dest-ip-ranges=[DEST_IP_RANGE,...] + The destination IPs/IP ranges to match for this rule. To match all + IPs specify *. + + --network-dest-ports=[DEST_PORT,...] + The destination ports to match for this rule. Each element can be an + 16-bit unsigned decimal number (e.g. "80") or range (e.g."0-1023"), + To match all destination ports specify *. + + --network-ip-protocols=[IP_PROTOCOL,...] + The IP protocols to match for this rule. Each element can be an 8-bit + unsigned decimal number (e.g. "6"), range (e.g."253-254"), or one of + the following protocol names: "tcp", "udp", "icmp", "esp", "ah", + "ipip", or "sctp". To match all protocols specify *. + + --network-src-asns=[SRC_ASN,...] + BGP Autonomous System Number associated with the source IP address to + match for this rule. + + --network-src-ip-ranges=[SRC_IP_RANGE,...] + The source IPs/IP ranges to match for this rule. To match all IPs + specify *. + + --network-src-ports=[SRC_PORT,...] + The source ports to match for this rule. Each element can be an + 16-bit unsigned decimal number (e.g. "80") or range (e.g."0-1023"), + To match all source ports specify *. + + --network-src-region-codes=[SRC_REGION_CODE,...] + The two letter ISO 3166-1 alpha-2 country code associated with the + source IP address to match for this rule. To match all region codes + specify *. + + --network-user-defined-fields=[NAME;VALUE:VALUE:...,...] + Each element names a defined field and lists the matching values for + that field. + --src-ip-ranges=[SRC_IP_RANGE,...] The source IPs/IP ranges to match for this rule. To match all IPs specify *. diff --git a/gcloud/compute/snapshot-settings/describe b/gcloud/compute/snapshot-settings/describe new file mode 100644 index 000000000..422997c63 --- /dev/null +++ b/gcloud/compute/snapshot-settings/describe @@ -0,0 +1,33 @@ +NAME + gcloud compute snapshot-settings describe - describe snapshot settings + +SYNOPSIS + gcloud compute snapshot-settings describe [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe the snapshot settings of a project. + +EXAMPLES + To display the snapshot settings of a project called my-project, run: + + $ gcloud compute snapshot-settings describe --project=my-project + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute snapshot-settings describe + + $ gcloud beta compute snapshot-settings describe + diff --git a/gcloud/compute/snapshot-settings/help b/gcloud/compute/snapshot-settings/help new file mode 100644 index 000000000..1db528aef --- /dev/null +++ b/gcloud/compute/snapshot-settings/help @@ -0,0 +1,31 @@ +NAME + gcloud compute snapshot-settings - describe and update Compute Engine + snapshot settings + +SYNOPSIS + gcloud compute snapshot-settings COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe and update Compute Engine snapshot settings. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe snapshot settings. + + update + Update snapshot settings. + +NOTES + These variants are also available: + + $ gcloud alpha compute snapshot-settings + + $ gcloud beta compute snapshot-settings + diff --git a/gcloud/compute/snapshot-settings/update b/gcloud/compute/snapshot-settings/update new file mode 100644 index 000000000..27c75c1a9 --- /dev/null +++ b/gcloud/compute/snapshot-settings/update @@ -0,0 +1,69 @@ +NAME + gcloud compute snapshot-settings update - update snapshot settings + +SYNOPSIS + gcloud compute snapshot-settings update [--async] + [--storage-location-names=[STORAGE_LOCATION_NAMES,...]] + [--storage-location-policy=STORAGE_LOCATION_POLICY] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update the snapshot settings of a project. + +EXAMPLES + To update the snapshot settings and set the storage location policy to the + nearest multi-region as the source disk, run: + + $ gcloud compute snapshot-settings update \ + --storage-location-policy=nearest-multi-region + + To update the snapshot settings and set the storage location policy to the + same region as the source disk, run: + + $ gcloud alpha compute snapshot-settings update \ --storage-location-policy=local-region + + To update the snapshot settings and set the storage location policy to + store snapshots in a specific location like us-west1, run: + + $ gcloud compute snapshot-settings update \ + --storage-location-policy=specific-locations \ + --storage-location-names=us-west1 + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --storage-location-names=[STORAGE_LOCATION_NAMES,...] + The custom storage locations that you specify for the project's + snapshots. Use this flag only when you use the SPECIFIC_LOCATIONS value + for the --storage-location-policy flag. For more information, refer to + the snapshot settings documentation at + https://cloud.google.com/compute/docs/disks/snapshot-settings. + + --storage-location-policy=STORAGE_LOCATION_POLICY + The storage location policy. For more information, refer to the + snapshot settings documentation at + https://cloud.google.com/compute/docs/disks/snapshot-settings. + STORAGE_LOCATION_POLICY must be one of: local-region, + nearest-multi-region, specific-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute snapshot-settings update + + $ gcloud beta compute snapshot-settings update + diff --git a/gcloud/compute/target-instances/help b/gcloud/compute/target-instances/help index cac74d535..96ec2481c 100644 --- a/gcloud/compute/target-instances/help +++ b/gcloud/compute/target-instances/help @@ -35,6 +35,9 @@ COMMANDS list List Google Compute Engine target instances. + update + Update a Compute Engine target instance. + NOTES These variants are also available: diff --git a/gcloud/compute/target-instances/update b/gcloud/compute/target-instances/update new file mode 100644 index 000000000..2eb65226f --- /dev/null +++ b/gcloud/compute/target-instances/update @@ -0,0 +1,70 @@ +NAME + gcloud compute target-instances update - update a Compute Engine target + instance + +SYNOPSIS + gcloud compute target-instances update NAME + [--security-policy=SECURITY_POLICY] + [--security-policy-region=SECURITY_POLICY_REGION] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute target-instances update updates a Compute Engine target + instance. + +EXAMPLES + To update the security policy run this: + + $ gcloud compute target-instances update TARGET_INSTANCE \ + --security-policy='my-policy' + +POSITIONAL ARGUMENTS + NAME + Name of the target instance to update. + +FLAGS + --security-policy=SECURITY_POLICY + The security policy that will be set for this target instance. To + remove the policy from this target instance set the policy to an empty + string. + + --security-policy-region=SECURITY_POLICY_REGION + Region of the security policy to operate on. Overrides the default + compute/region property value for this command invocation. + + --zone=ZONE + Zone of the target instance to update. If not specified and the + compute/zone property isn't set, you might be prompted to select a zone + (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +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 + These variants are also available: + + $ gcloud alpha compute target-instances update + + $ gcloud beta compute target-instances update + diff --git a/gcloud/compute/target-pools/help b/gcloud/compute/target-pools/help index ed6b32417..89c372ef3 100644 --- a/gcloud/compute/target-pools/help +++ b/gcloud/compute/target-pools/help @@ -53,6 +53,9 @@ COMMANDS set-backup Set a backup pool for a target pool. + update + Update a Compute Engine target pool. + NOTES These variants are also available: diff --git a/gcloud/compute/target-pools/update b/gcloud/compute/target-pools/update new file mode 100644 index 000000000..37ed49391 --- /dev/null +++ b/gcloud/compute/target-pools/update @@ -0,0 +1,66 @@ +NAME + gcloud compute target-pools update - update a Compute Engine target pool + +SYNOPSIS + gcloud compute target-pools update NAME [--region=REGION] + [--security-policy=SECURITY_POLICY] + [--security-policy-region=SECURITY_POLICY_REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute target-pools update updates a Compute Engine target pool. + +EXAMPLES + To update the security policy run this: + + $ gcloud compute target-pools update TARGET_POOL \ + --security-policy='my-policy' + +POSITIONAL ARGUMENTS + NAME + The name of the target pool. + +FLAGS + --region=REGION + Region of the target pool to update. If not specified, you might be + prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --security-policy=SECURITY_POLICY + The security policy that will be set for this target pool. To remove + the policy from this target pool set the policy to an empty string. + + --security-policy-region=SECURITY_POLICY_REGION + Region of the security policy to operate on. Overrides the default + compute/region property value for this command invocation. + +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 + These variants are also available: + + $ gcloud alpha compute target-pools update + + $ gcloud beta compute target-pools update + diff --git a/gcloud/compute/tpus/tpu-vm/update b/gcloud/compute/tpus/tpu-vm/update index c61e6b38a..2cc6b7f49 100644 --- a/gcloud/compute/tpus/tpu-vm/update +++ b/gcloud/compute/tpus/tpu-vm/update @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud compute tpus tpu-vm update (TPU : --zone=ZONE) [--add-tags=[TAGS,...]] [--async] [--description=DESCRIPTION] - [--internal-ips] [--clear-tags | --remove-tags=[TAG,...]] - [GCLOUD_WIDE_FLAG ...] + [--internal-ips] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] + [--clear-tags | --remove-tags=[TAG,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a Cloud TPU VM node. @@ -17,6 +18,25 @@ EXAMPLES $ gcloud compute tpus tpu-vm update my-tpu \ --description="A new description" + To modify a TPU VM node with ID my-tpu in the default user project, network + and compute/zone (with other defaults supplied by API) by adding labels k0, + with value value0 and label k1 with value value1 and removing labels with + key k2, run: + + $ gcloud compute tpus tpu-vm update my-tpu \ + --update-labels=k0=value0,k1=value1 --remove-labels=k2 + + Labels can be used to identify the TPU VM node. To list TPU VM nodes with + the k1:value1 label, run: + + $ gcloud compute tpus tpu-vm list --filter='labels.k1=value1' + + To list only the labels when describing a resource, use --format to filter + the result: + + $ gcloud compute tpus tpu-vm describe my-tpu \ + --format="default(labels)" + POSITIONAL ARGUMENTS Tpu resource - Name of the Cloud TPU VM node to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -70,6 +90,33 @@ FLAGS default is that external IP addresses will be associated with the TPU workers. + --update-labels=[KEY=VALUE,...] + Resource labels to update that represent user-provided metadata. If a + label exists, its value is modified. Otherwise, a new label is created. + See https://cloud.google.com/compute/docs/labeling-resources for + details. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud compute tpus tpu-vm update --clear-labels + + To remove all existing labels and create two new labels, 'foo' and + 'baz': + + $ gcloud compute tpus tpu-vm update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + At most one of these can be specified: --clear-tags diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 046ae229e..693d3a934 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -17,12 +17,12 @@ SYNOPSIS [--enable-google-cloud-access] [--enable-kubernetes-unstable-apis=API,[API,...]] [--enable-master-global-access] [--fleet-project=PROJECT_ID_OR_NUMBER] - [--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] + [--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] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] @@ -226,6 +226,15 @@ FLAGS Example: $ gcloud container clusters create-auto --fleet-project=my-project + --labels=[KEY=VALUE,...] + Labels to apply to the Google Cloud resources in use by the Kubernetes + Engine cluster. These are unrelated to Kubernetes labels. + + Examples: + + $ gcloud container clusters create-auto example-cluster \ + --labels=label_a=value1,label_b=,label_c=value3 + --logging=[COMPONENT,...] Set the components that have logging enabled. Valid component values are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, NONE diff --git a/gcloud/container/fleet/help b/gcloud/container/fleet/help index f55082174..35c11b46b 100644 --- a/gcloud/container/fleet/help +++ b/gcloud/container/fleet/help @@ -70,6 +70,9 @@ GROUPS multi-cluster-services Manage Multi-cluster Services Feature. + policycontroller + Manage Policy Controller Feature. + scopes Manage scopes of all your GKE fleets. diff --git a/gcloud/container/fleet/policycontroller/content/bundles/help b/gcloud/container/fleet/policycontroller/content/bundles/help new file mode 100644 index 000000000..37c483d93 --- /dev/null +++ b/gcloud/container/fleet/policycontroller/content/bundles/help @@ -0,0 +1,32 @@ +NAME + gcloud container fleet policycontroller content bundles - manage Policy + Controller content bundles + +SYNOPSIS + gcloud container fleet policycontroller content bundles COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Policy Controller content bundles. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + remove + Removes a bundle installation for Policy Controller content. + + set + Sets bundle installation for Policy Controller content. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet policycontroller content bundles + + $ gcloud beta container fleet policycontroller content bundles + diff --git a/gcloud/container/fleet/policycontroller/content/bundles/remove b/gcloud/container/fleet/policycontroller/content/bundles/remove new file mode 100644 index 000000000..93c13ea3d --- /dev/null +++ b/gcloud/container/fleet/policycontroller/content/bundles/remove @@ -0,0 +1,79 @@ +NAME + gcloud container fleet policycontroller content bundles remove - removes a + bundle installation for Policy Controller content + +SYNOPSIS + gcloud container fleet policycontroller content bundles remove BUNDLE_NAME + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Google-defined policy bundles of constraints can be installed onto Policy + Controller installations. This command removes those bundles. + +EXAMPLES + To remove a policy bundle: + + $ gcloud container fleet policycontroller content bundles remove \ + cis-k8s-v1.5.1 + +POSITIONAL ARGUMENTS + BUNDLE_NAME + The constraint bundle to remove from Policy Controller. + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container fleet policycontroller content bundles \ + remove + + $ gcloud beta container fleet policycontroller content bundles remove + diff --git a/gcloud/container/fleet/policycontroller/content/bundles/set b/gcloud/container/fleet/policycontroller/content/bundles/set new file mode 100644 index 000000000..2bf736889 --- /dev/null +++ b/gcloud/container/fleet/policycontroller/content/bundles/set @@ -0,0 +1,110 @@ +NAME + gcloud container fleet policycontroller content bundles set - sets bundle + installation for Policy Controller content + +SYNOPSIS + gcloud container fleet policycontroller content bundles set BUNDLE_NAME + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [--exempted-namespaces=EXEMPTED_NAMESPACES | --no-exempted-namespaces] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Google-defined policy bundles of constraints can be installed onto Policy + Controller installations. + + The namespace exclusion flag (--exempted-namespaces) will specify a set of + namespaces that the installed bundle will ignore. Subsequent calls with the + same bundle name and this flag will overwrite what namespaces are being + ignored. Using --no-exempted-namespaces or specifying no namespaces with + --exempted-namespaces will remove all namespaces from the ignore list. + + To uninstall a bundle, use the remove command. + +EXAMPLES + To install a policy bundle: + + $ gcloud container fleet policycontroller content bundles set \ + cis-k8s-v1.5.1 + + To install a policy bundle, while ignoring (exempting) certain namespaces + from being affected by the bundle: + + $ gcloud container fleet policycontroller content bundles set \ + cis-k8s-v1.5.1 \ + --exempted-namespaces=kube-system,gatekeeper-system + + To remove all exempted namespaces from a particular bundles ignore list: + + $ gcloud container fleet policycontroller content bundles set \ + cis-k8s-v1.5.1 --no-exempted-namespaces + +POSITIONAL ARGUMENTS + BUNDLE_NAME + The constraint bundle to install in Policy Controller. + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + + Exempted Namespaces flags. + + At most one of these can be specified: + + --exempted-namespaces=EXEMPTED_NAMESPACES + Exempted namespaces are ignored by Policy Controller when applying + constraints added by this bundle. + + --no-exempted-namespaces + Removes all exempted namespaces from the specified bundle. + +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 + These variants are also available: + + $ gcloud alpha container fleet policycontroller content bundles set + + $ gcloud beta container fleet policycontroller content bundles set + diff --git a/gcloud/container/fleet/policycontroller/content/help b/gcloud/container/fleet/policycontroller/content/help new file mode 100644 index 000000000..0cde676ae --- /dev/null +++ b/gcloud/container/fleet/policycontroller/content/help @@ -0,0 +1,32 @@ +NAME + gcloud container fleet policycontroller content - manage Policy Controller + content + +SYNOPSIS + gcloud container fleet policycontroller content GROUP + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Policy Controller content. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + bundles + Manage Policy Controller content bundles. + + templates + Manage Policy Controller content templates. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet policycontroller content + + $ gcloud beta container fleet policycontroller content + diff --git a/gcloud/container/fleet/policycontroller/content/templates/disable b/gcloud/container/fleet/policycontroller/content/templates/disable new file mode 100644 index 000000000..a53a50461 --- /dev/null +++ b/gcloud/container/fleet/policycontroller/content/templates/disable @@ -0,0 +1,75 @@ +NAME + gcloud container fleet policycontroller content templates disable - disable + template installation for Policy Controller content + +SYNOPSIS + gcloud container fleet policycontroller content templates disable + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The Google-defined template library can be installed onto Policy Controller + installations. This command removes that template library. + +EXAMPLES + To remove the template library: + + $ gcloud container fleet policycontroller content templates disable + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container fleet policycontroller content templates \ + disable + + $ gcloud beta container fleet policycontroller content templates \ + disable + diff --git a/gcloud/container/fleet/policycontroller/content/templates/enable b/gcloud/container/fleet/policycontroller/content/templates/enable new file mode 100644 index 000000000..63e2c1da6 --- /dev/null +++ b/gcloud/container/fleet/policycontroller/content/templates/enable @@ -0,0 +1,75 @@ +NAME + gcloud container fleet policycontroller content templates enable - installs + the template library for Policy Controller + +SYNOPSIS + gcloud container fleet policycontroller content templates enable + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Google-defined template library can be installed onto Policy Controller + installations. To uninstall the template library, use the disable command. + +EXAMPLES + To install a template library: + + $ gcloud container fleet policycontroller content templates enable + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container fleet policycontroller content templates \ + enable + + $ gcloud beta container fleet policycontroller content templates \ + enable + diff --git a/gcloud/container/fleet/policycontroller/content/templates/help b/gcloud/container/fleet/policycontroller/content/templates/help new file mode 100644 index 000000000..0b075687f --- /dev/null +++ b/gcloud/container/fleet/policycontroller/content/templates/help @@ -0,0 +1,32 @@ +NAME + gcloud container fleet policycontroller content templates - manage Policy + Controller content templates + +SYNOPSIS + gcloud container fleet policycontroller content templates COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Policy Controller content templates. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + disable + Disable template installation for Policy Controller content. + + enable + Installs the template library for Policy Controller. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet policycontroller content templates + + $ gcloud beta container fleet policycontroller content templates + diff --git a/gcloud/container/fleet/policycontroller/deployment/help b/gcloud/container/fleet/policycontroller/deployment/help new file mode 100644 index 000000000..81b173569 --- /dev/null +++ b/gcloud/container/fleet/policycontroller/deployment/help @@ -0,0 +1,32 @@ +NAME + gcloud container fleet policycontroller deployment - configure Policy + Controller component deployments + +SYNOPSIS + gcloud container fleet policycontroller deployment COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Configure Policy Controller component deployments. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + remove + Removes configuration properties from Policy Controller components. + + set + Sets configuration of the Policy Controller components. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet policycontroller deployment + + $ gcloud beta container fleet policycontroller deployment + diff --git a/gcloud/container/fleet/policycontroller/deployment/remove b/gcloud/container/fleet/policycontroller/deployment/remove new file mode 100644 index 000000000..8f115c7f1 --- /dev/null +++ b/gcloud/container/fleet/policycontroller/deployment/remove @@ -0,0 +1,137 @@ +NAME + gcloud container fleet policycontroller deployment remove - removes + configuration properties from Policy Controller components + +SYNOPSIS + gcloud container fleet policycontroller deployment remove DEPLOYMENT + PROPERTY [VALUE] [--effect=EFFECT] + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove customizations of on-cluster components in Policy Controller. These + components are managed as individual kubernetes deployments (e.g. + 'admission') in the gatekeeper-system namespace. + + When removing a 'toleration' property, it must match exactly, including the + key, value and effect flag (if originally specified). + +EXAMPLES + To remove the replica count for a component: + + $ gcloud container fleet policycontroller deployment remove \ + admission replica-count + + To remove the replica count for a component across all fleet memberships: + + $ gcloud container fleet policycontroller deployment remove \ + admission replica-count --all-memberships + + To remove a toleration with key 'my-key' on a component: + + $ gcloud container fleet policycontroller deployment remove \ + admission toleration my-key + + To remove a toleration with key 'my-key' and 'my-value' on a component: + + $ gcloud container fleet policycontroller deployment remove \ + admission toleration my-key=my-value + + To remove a toleration with key 'my-key' and 'my-value' on a component, + along with the effect 'NoSchedule': + + $ gcloud container fleet policycontroller deployment remove \ + admission toleration my-key=my-value --effect=NoSchedule + + To remove a memory limit: + + $ gcloud container fleet policycontroller deployment remove audit \ + memory-limit + + To remove a memory request: + + $ gcloud container fleet policycontroller deployment remove \ + mutation memory-request + + To remove a cpu limit: + + $ gcloud container fleet policycontroller deployment remove \ + admission cpu-limit + + To remove a cpu request: + + $ gcloud container fleet policycontroller deployment remove audit \ + cpu-request + +POSITIONAL ARGUMENTS + DEPLOYMENT + The PolicyController deployment component (i.e, "admission", "audit" or + "mutation" from which to remove configuration. + + PROPERTY + Property to be removed. + + [VALUE] + This is only required to remove a toleration. It should not be included + for any other property. + +FLAGS + --effect=EFFECT + Applies only to "toleration" property. To be removed, tolerations must + match exactly, including the effect setting. EFFECT must be one of: + NoSchedule, PreferNoSchedule, NoExecute. + + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container fleet policycontroller deployment remove + + $ gcloud beta container fleet policycontroller deployment remove + diff --git a/gcloud/container/fleet/policycontroller/deployment/set b/gcloud/container/fleet/policycontroller/deployment/set new file mode 100644 index 000000000..5e70ffb1d --- /dev/null +++ b/gcloud/container/fleet/policycontroller/deployment/set @@ -0,0 +1,144 @@ +NAME + gcloud container fleet policycontroller deployment set - sets configuration + of the Policy Controller components + +SYNOPSIS + gcloud container fleet policycontroller deployment set DEPLOYMENT PROPERTY + VALUE [--effect=EFFECT] + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Customizes on-cluster components of Policy Controller. Supported properties + may be set with this command, or removed with 'remove'. These components + are managed as individual kubernetes deployments (e.g. 'admission') in the + gatekeeper-system namespace. + + When setting cpu or memory limits and requests, Kubernetes-standard + resource units are used. + + All properties set using this command will overwrite previous properties, + with the exception of tolerations which can only be added, and any number + may be added. To edit a toleration, use 'remove' to first delete it, and + then 'set' the desired toleration. + +EXAMPLES + To set the replica count for a component: + + $ gcloud container fleet policycontroller deployment set admission \ + replica-count 3 + + To set the replica count for a component across all fleet memberships: + + $ gcloud container fleet policycontroller deployment set admission \ + replica-count 3 --all-memberships + + To set a toleration with key 'my-key' on a component (which is an 'Exists' + operator): + + $ gcloud container fleet policycontroller deployment set admission \ + toleration my-key + + To set a toleration with key 'my-key' and 'my-value' on a component (which + is an 'Equal' operator): + + $ gcloud container fleet policycontroller deployment set admission \ + toleration my-key=my-value + + To set a toleration with key 'my-key' and 'my-value' on a component, along + with the effect 'NoSchedule' (which is an 'Equal' operator): + + $ gcloud container fleet policycontroller deployment set admission \ + toleration my-key=my-value --effect=NoSchedule + + To set a memory limit: + + $ gcloud container fleet policycontroller deployment set audit \ + memory-limit 4Gi + + To set a memory request: + + $ gcloud container fleet policycontroller deployment set mutation \ + memory-request 2Gi + + To set a cpu limit: + + $ gcloud container fleet policycontroller deployment set admission \ + cpu-limit 500m + + To set a cpu request: + + $ gcloud container fleet policycontroller deployment set audit \ + cpu-request 250m + +POSITIONAL ARGUMENTS + DEPLOYMENT + The PolicyController deployment component (e.g. "admission", "audit" or + "mutation") upon which to set configuration. + + PROPERTY + Property to be set. + + VALUE + The value to set the property to. Valid input varies based on the + property being set. + +FLAGS + --effect=EFFECT + Applies only to "toleration" property. EFFECT must be one of: + NoSchedule, PreferNoSchedule, NoExecute. + + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container fleet policycontroller deployment set + + $ gcloud beta container fleet policycontroller deployment set + diff --git a/gcloud/container/fleet/policycontroller/describe b/gcloud/container/fleet/policycontroller/describe new file mode 100644 index 000000000..c157def28 --- /dev/null +++ b/gcloud/container/fleet/policycontroller/describe @@ -0,0 +1,69 @@ +NAME + gcloud container fleet policycontroller describe - describe Policy + Controller feature + +SYNOPSIS + gcloud container fleet policycontroller describe + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To describe the Policy Controller feature: + + $ gcloud container fleet policycontroller describe + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container fleet policycontroller describe + + $ gcloud beta container fleet policycontroller describe + diff --git a/gcloud/container/fleet/policycontroller/detach b/gcloud/container/fleet/policycontroller/detach new file mode 100644 index 000000000..3376544c1 --- /dev/null +++ b/gcloud/container/fleet/policycontroller/detach @@ -0,0 +1,78 @@ +NAME + gcloud container fleet policycontroller detach - detach Policy Controller + Feature + +SYNOPSIS + gcloud container fleet policycontroller detach + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Detaches Policy Controller. This will halt all administration of the Policy + Controller installation by the GKE Fleet. It will not uninstall it from the + cluster. To re-attach Policy Controller, use the enable command. + +EXAMPLES + To detach Policy Controller, run: + + $ gcloud container fleet policycontroller detach + + To re-attach Policy Controller, use the enable command: + + $ gcloud container fleet policycontroller enable + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container fleet policycontroller detach + + $ gcloud beta container fleet policycontroller detach + diff --git a/gcloud/container/fleet/policycontroller/disable b/gcloud/container/fleet/policycontroller/disable new file mode 100644 index 000000000..8c617941c --- /dev/null +++ b/gcloud/container/fleet/policycontroller/disable @@ -0,0 +1,82 @@ +NAME + gcloud container fleet policycontroller disable - disable (Uninstall) + Policy Controller + +SYNOPSIS + gcloud container fleet policycontroller disable + [--fleet-default-member-config | --all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Uninstalls Policy Controller. + +EXAMPLES + To uninstall Policy Controller, run: + + $ gcloud container fleet policycontroller disable + +FLAGS + At most one of these can be specified: + + --fleet-default-member-config + Removes the fleet default configuration for policy controller. + Memberships configured with the fleet default will maintain their + current configuration. + + $ gcloud container fleet policycontroller disable \ + --fleet-default-member-config + + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ◇ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ◇ provide the argument --memberships on the command line with a + fully specified name; + ◇ provide the argument --location on the command line; + ◇ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container fleet policycontroller disable + + $ gcloud beta container fleet policycontroller disable + diff --git a/gcloud/container/fleet/policycontroller/enable b/gcloud/container/fleet/policycontroller/enable new file mode 100644 index 000000000..7512460aa --- /dev/null +++ b/gcloud/container/fleet/policycontroller/enable @@ -0,0 +1,180 @@ +NAME + gcloud container fleet policycontroller enable - enable Policy Controller + Feature + +SYNOPSIS + gcloud container fleet policycontroller enable + [--all-memberships | [--memberships=[MEMBERSHIPS,...] + : --location=LOCATION] --audit-interval=AUDIT_INTERVAL + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + --no-default-bundles --version=VERSION --clear-exemptable-namespaces + | --exemptable-namespaces=EXEMPTABLE_NAMESPACES --log-denies + | --no-log-denies --monitoring=MONITORING + | --no-monitoring --mutation | --no-mutation --referential-rules + | --no-referential-rules + | --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + | --no-fleet-default-member-config] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Enables the Policy Controller Feature in a fleet. + +EXAMPLES + To enable the Policy Controller Feature, run: + + $ gcloud container fleet policycontroller enable + +FLAGS + At most one of these can be specified: + + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ◇ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ◇ provide the argument --memberships on the command line with a + fully specified name; + ◇ provide the argument --location on the command line; + ◇ set the property gkehub/location. + + --audit-interval=AUDIT_INTERVAL + How often Policy Controller will audit resources, in seconds. + + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + The number of violations stored on the constraint resource. Must be + greater than 0. + + --no-default-bundles + If set, skip installing the default bundle of policy-essentials. + + --version=VERSION + The version of Policy Controller to install; defaults to latest + version. + + Exemptable Namespace flags. + + At most one of these can be specified: + + --clear-exemptable-namespaces + Removes any namespace exemptions, enabling Policy Controller on all + namespaces. Setting this flag will overwrite currently exempted + namespaces, not append. + + --exemptable-namespaces=EXEMPTABLE_NAMESPACES + Namespaces that Policy Controller should ignore, separated by + commas if multiple are supplied. + + Log Denies flags. + + At most one of these can be specified: + + --log-denies + If set, log all denies and dry run failures. (To disable, use + --no-log-denies) + + --no-log-denies + If set, disable all log denies. + + Monitoring flags. + + At most one of these can be specified: + + --monitoring=MONITORING + Monitoring backend options Policy Controller should export metrics + to, separated by commas if multiple are supplied. Setting this flag + will overwrite currently enabled backends, not append. Options: + prometheus, cloudmonitoring + + --no-monitoring + Include this flag to disable the monitoring configuration of Policy + Controller. + + Mutation flags. + + At most one of these can be specified: + + --mutation + If set, enable support for mutation. (To disable, use + --no-mutation) + + --no-mutation + Disables mutation support. + + Referential Rules flags. + + At most one of these can be specified: + + --referential-rules + If set, enable support for referential constraints. (To disable, + use --no-referential-rules) + + --no-referential-rules + Disables referential rules support. + + Flags for setting Fleet Default Configuration files. + + At most one of these can be specified: + + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to a policy-controller.yaml configuration file. If + specified, this configuration will become the default Policy + Controller configuration for all memberships in your fleet. It can + be overridden with a membership-specific configuration by using the + the Update command. + + To enable the Policy Controller Feature with a fleet-level default + membership configuration, run: + + $ gcloud container fleet policycontroller enable \ + --fleet-default-member-config=/path/to/policy-controller.yaml + + --no-fleet-default-member-config + Removes the fleet default configuration for policy controller. + Memberships configured with the fleet default will maintain their + current configuration. + + $ gcloud container fleet policycontroller enable \ + --no-fleet-default-member-config + +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 + These variants are also available: + + $ gcloud alpha container fleet policycontroller enable + + $ gcloud beta container fleet policycontroller enable + diff --git a/gcloud/container/fleet/policycontroller/help b/gcloud/container/fleet/policycontroller/help new file mode 100644 index 000000000..23caba5cf --- /dev/null +++ b/gcloud/container/fleet/policycontroller/help @@ -0,0 +1,52 @@ +NAME + gcloud container fleet policycontroller - manage Policy Controller Feature + +SYNOPSIS + gcloud container fleet policycontroller GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Policy Controller Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + content + Manage Policy Controller content. + + deployment + Configure Policy Controller component deployments. + +COMMANDS + COMMAND is one of the following: + + describe + Describe Policy Controller feature. + + detach + Detach Policy Controller Feature. + + disable + Disable (Uninstall) Policy Controller. + + enable + Enable Policy Controller Feature. + + suspend + Suspend Policy Controller Feature. + + update + Updates the configuration of Policy Controller Feature. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet policycontroller + + $ gcloud beta container fleet policycontroller + diff --git a/gcloud/container/fleet/policycontroller/suspend b/gcloud/container/fleet/policycontroller/suspend new file mode 100644 index 000000000..e70d8f86e --- /dev/null +++ b/gcloud/container/fleet/policycontroller/suspend @@ -0,0 +1,78 @@ +NAME + gcloud container fleet policycontroller suspend - suspend Policy Controller + Feature + +SYNOPSIS + gcloud container fleet policycontroller suspend + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Suspends the Policy Controller. This will disable all kubernetes webhooks + on the configured cluster, thereby removing admission and mutation + functionality. Audit functionality will remain in place. + +EXAMPLES + To suspend Policy Controller, run: + + $ gcloud container fleet policycontroller suspend + + To re-enable Policy Controller webhooks, use the enable command: + + $ gcloud container fleet policycontroller enable + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container fleet policycontroller suspend + + $ gcloud beta container fleet policycontroller suspend + diff --git a/gcloud/container/fleet/policycontroller/update b/gcloud/container/fleet/policycontroller/update new file mode 100644 index 000000000..040f4a568 --- /dev/null +++ b/gcloud/container/fleet/policycontroller/update @@ -0,0 +1,161 @@ +NAME + gcloud container fleet policycontroller update - updates the configuration + of Policy Controller Feature + +SYNOPSIS + gcloud container fleet policycontroller update + [--all-memberships | [--memberships=[MEMBERSHIPS,...] + : --location=LOCATION] --origin=ORIGIN + | --audit-interval=AUDIT_INTERVAL + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + --version=VERSION --clear-exemptable-namespaces + | --exemptable-namespaces=EXEMPTABLE_NAMESPACES --log-denies + | --no-log-denies --monitoring=MONITORING + | --no-monitoring --mutation | --no-mutation --referential-rules + | --no-referential-rules] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates the configuration of the Policy Controller installation + +EXAMPLES + To change the installed version, run: + + $ gcloud container fleet policycontroller update --version=VERSION + + To modify the audit interval to 120 seconds, run: + + $ gcloud container fleet policycontroller update --audit-interval=120 + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + + At most one of these can be specified: + + --origin=ORIGIN + If --origin=FLEET will set the configuration of the membership to the + fleet default. + + ORIGIN must be (only one value is supported): FLEET. + + --audit-interval=AUDIT_INTERVAL + How often Policy Controller will audit resources, in seconds. + + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + The number of violations stored on the constraint resource. Must be + greater than 0. + + --version=VERSION + The version of Policy Controller to install; defaults to latest + version. + + Exemptable Namespace flags. + + At most one of these can be specified: + + --clear-exemptable-namespaces + Removes any namespace exemptions, enabling Policy Controller on all + namespaces. Setting this flag will overwrite currently exempted + namespaces, not append. + + --exemptable-namespaces=EXEMPTABLE_NAMESPACES + Namespaces that Policy Controller should ignore, separated by + commas if multiple are supplied. + + Log Denies flags. + + At most one of these can be specified: + + --log-denies + If set, log all denies and dry run failures. (To disable, use + --no-log-denies) + + --no-log-denies + If set, disable all log denies. + + Monitoring flags. + + At most one of these can be specified: + + --monitoring=MONITORING + Monitoring backend options Policy Controller should export metrics + to, separated by commas if multiple are supplied. Setting this flag + will overwrite currently enabled backends, not append. Options: + prometheus, cloudmonitoring + + --no-monitoring + Include this flag to disable the monitoring configuration of Policy + Controller. + + Mutation flags. + + At most one of these can be specified: + + --mutation + If set, enable support for mutation. (To disable, use + --no-mutation) + + --no-mutation + Disables mutation support. + + Referential Rules flags. + + At most one of these can be specified: + + --referential-rules + If set, enable support for referential constraints. (To disable, + use --no-referential-rules) + + --no-referential-rules + Disables referential rules support. + +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 + These variants are also available: + + $ gcloud alpha container fleet policycontroller update + + $ gcloud beta container fleet policycontroller update + diff --git a/gcloud/container/hub/help b/gcloud/container/hub/help index 8d6fe568c..f8ab4d901 100644 --- a/gcloud/container/hub/help +++ b/gcloud/container/hub/help @@ -70,6 +70,9 @@ GROUPS multi-cluster-services Manage Multi-cluster Services Feature. + policycontroller + Manage Policy Controller Feature. + scopes Manage scopes of all your GKE fleets. diff --git a/gcloud/container/hub/policycontroller/content/bundles/help b/gcloud/container/hub/policycontroller/content/bundles/help new file mode 100644 index 000000000..76bf8b5e8 --- /dev/null +++ b/gcloud/container/hub/policycontroller/content/bundles/help @@ -0,0 +1,32 @@ +NAME + gcloud container hub policycontroller content bundles - manage Policy + Controller content bundles + +SYNOPSIS + gcloud container hub policycontroller content bundles COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Policy Controller content bundles. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + remove + Removes a bundle installation for Policy Controller content. + + set + Sets bundle installation for Policy Controller content. + +NOTES + These variants are also available: + + $ gcloud alpha container hub policycontroller content bundles + + $ gcloud beta container hub policycontroller content bundles + diff --git a/gcloud/container/hub/policycontroller/content/bundles/remove b/gcloud/container/hub/policycontroller/content/bundles/remove new file mode 100644 index 000000000..2390e39cb --- /dev/null +++ b/gcloud/container/hub/policycontroller/content/bundles/remove @@ -0,0 +1,78 @@ +NAME + gcloud container hub policycontroller content bundles remove - removes a + bundle installation for Policy Controller content + +SYNOPSIS + gcloud container hub policycontroller content bundles remove BUNDLE_NAME + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Google-defined policy bundles of constraints can be installed onto Policy + Controller installations. This command removes those bundles. + +EXAMPLES + To remove a policy bundle: + + $ gcloud container hub policycontroller content bundles remove \ + cis-k8s-v1.5.1 + +POSITIONAL ARGUMENTS + BUNDLE_NAME + The constraint bundle to remove from Policy Controller. + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container hub policycontroller content bundles remove + + $ gcloud beta container hub policycontroller content bundles remove + diff --git a/gcloud/container/hub/policycontroller/content/bundles/set b/gcloud/container/hub/policycontroller/content/bundles/set new file mode 100644 index 000000000..9831d460e --- /dev/null +++ b/gcloud/container/hub/policycontroller/content/bundles/set @@ -0,0 +1,110 @@ +NAME + gcloud container hub policycontroller content bundles set - sets bundle + installation for Policy Controller content + +SYNOPSIS + gcloud container hub policycontroller content bundles set BUNDLE_NAME + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [--exempted-namespaces=EXEMPTED_NAMESPACES | --no-exempted-namespaces] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Google-defined policy bundles of constraints can be installed onto Policy + Controller installations. + + The namespace exclusion flag (--exempted-namespaces) will specify a set of + namespaces that the installed bundle will ignore. Subsequent calls with the + same bundle name and this flag will overwrite what namespaces are being + ignored. Using --no-exempted-namespaces or specifying no namespaces with + --exempted-namespaces will remove all namespaces from the ignore list. + + To uninstall a bundle, use the remove command. + +EXAMPLES + To install a policy bundle: + + $ gcloud container hub policycontroller content bundles set \ + cis-k8s-v1.5.1 + + To install a policy bundle, while ignoring (exempting) certain namespaces + from being affected by the bundle: + + $ gcloud container hub policycontroller content bundles set \ + cis-k8s-v1.5.1 \ + --exempted-namespaces=kube-system,gatekeeper-system + + To remove all exempted namespaces from a particular bundles ignore list: + + $ gcloud container hub policycontroller content bundles set \ + cis-k8s-v1.5.1 --no-exempted-namespaces + +POSITIONAL ARGUMENTS + BUNDLE_NAME + The constraint bundle to install in Policy Controller. + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + + Exempted Namespaces flags. + + At most one of these can be specified: + + --exempted-namespaces=EXEMPTED_NAMESPACES + Exempted namespaces are ignored by Policy Controller when applying + constraints added by this bundle. + + --no-exempted-namespaces + Removes all exempted namespaces from the specified bundle. + +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 + These variants are also available: + + $ gcloud alpha container hub policycontroller content bundles set + + $ gcloud beta container hub policycontroller content bundles set + diff --git a/gcloud/container/hub/policycontroller/content/help b/gcloud/container/hub/policycontroller/content/help new file mode 100644 index 000000000..7464d88ed --- /dev/null +++ b/gcloud/container/hub/policycontroller/content/help @@ -0,0 +1,31 @@ +NAME + gcloud container hub policycontroller content - manage Policy Controller + content + +SYNOPSIS + gcloud container hub policycontroller content GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Policy Controller content. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + bundles + Manage Policy Controller content bundles. + + templates + Manage Policy Controller content templates. + +NOTES + These variants are also available: + + $ gcloud alpha container hub policycontroller content + + $ gcloud beta container hub policycontroller content + diff --git a/gcloud/container/hub/policycontroller/content/templates/disable b/gcloud/container/hub/policycontroller/content/templates/disable new file mode 100644 index 000000000..91faf0835 --- /dev/null +++ b/gcloud/container/hub/policycontroller/content/templates/disable @@ -0,0 +1,75 @@ +NAME + gcloud container hub policycontroller content templates disable - disable + template installation for Policy Controller content + +SYNOPSIS + gcloud container hub policycontroller content templates disable + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The Google-defined template library can be installed onto Policy Controller + installations. This command removes that template library. + +EXAMPLES + To remove the template library: + + $ gcloud container hub policycontroller content templates disable + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container hub policycontroller content templates \ + disable + + $ gcloud beta container hub policycontroller content templates \ + disable + diff --git a/gcloud/container/hub/policycontroller/content/templates/enable b/gcloud/container/hub/policycontroller/content/templates/enable new file mode 100644 index 000000000..c6c4f187b --- /dev/null +++ b/gcloud/container/hub/policycontroller/content/templates/enable @@ -0,0 +1,74 @@ +NAME + gcloud container hub policycontroller content templates enable - installs + the template library for Policy Controller + +SYNOPSIS + gcloud container hub policycontroller content templates enable + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Google-defined template library can be installed onto Policy Controller + installations. To uninstall the template library, use the disable command. + +EXAMPLES + To install a template library: + + $ gcloud container hub policycontroller content templates enable + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container hub policycontroller content templates \ + enable + + $ gcloud beta container hub policycontroller content templates enable + diff --git a/gcloud/container/hub/policycontroller/content/templates/help b/gcloud/container/hub/policycontroller/content/templates/help new file mode 100644 index 000000000..853d052b5 --- /dev/null +++ b/gcloud/container/hub/policycontroller/content/templates/help @@ -0,0 +1,32 @@ +NAME + gcloud container hub policycontroller content templates - manage Policy + Controller content templates + +SYNOPSIS + gcloud container hub policycontroller content templates COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Policy Controller content templates. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + disable + Disable template installation for Policy Controller content. + + enable + Installs the template library for Policy Controller. + +NOTES + These variants are also available: + + $ gcloud alpha container hub policycontroller content templates + + $ gcloud beta container hub policycontroller content templates + diff --git a/gcloud/container/hub/policycontroller/deployment/help b/gcloud/container/hub/policycontroller/deployment/help new file mode 100644 index 000000000..cd7daba0c --- /dev/null +++ b/gcloud/container/hub/policycontroller/deployment/help @@ -0,0 +1,32 @@ +NAME + gcloud container hub policycontroller deployment - configure Policy + Controller component deployments + +SYNOPSIS + gcloud container hub policycontroller deployment COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Configure Policy Controller component deployments. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + remove + Removes configuration properties from Policy Controller components. + + set + Sets configuration of the Policy Controller components. + +NOTES + These variants are also available: + + $ gcloud alpha container hub policycontroller deployment + + $ gcloud beta container hub policycontroller deployment + diff --git a/gcloud/container/hub/policycontroller/deployment/remove b/gcloud/container/hub/policycontroller/deployment/remove new file mode 100644 index 000000000..96d525d95 --- /dev/null +++ b/gcloud/container/hub/policycontroller/deployment/remove @@ -0,0 +1,137 @@ +NAME + gcloud container hub policycontroller deployment remove - removes + configuration properties from Policy Controller components + +SYNOPSIS + gcloud container hub policycontroller deployment remove DEPLOYMENT PROPERTY + [VALUE] [--effect=EFFECT] + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove customizations of on-cluster components in Policy Controller. These + components are managed as individual kubernetes deployments (e.g. + 'admission') in the gatekeeper-system namespace. + + When removing a 'toleration' property, it must match exactly, including the + key, value and effect flag (if originally specified). + +EXAMPLES + To remove the replica count for a component: + + $ gcloud container hub policycontroller deployment remove \ + admission replica-count + + To remove the replica count for a component across all fleet memberships: + + $ gcloud container hub policycontroller deployment remove \ + admission replica-count --all-memberships + + To remove a toleration with key 'my-key' on a component: + + $ gcloud container hub policycontroller deployment remove \ + admission toleration my-key + + To remove a toleration with key 'my-key' and 'my-value' on a component: + + $ gcloud container hub policycontroller deployment remove \ + admission toleration my-key=my-value + + To remove a toleration with key 'my-key' and 'my-value' on a component, + along with the effect 'NoSchedule': + + $ gcloud container hub policycontroller deployment remove \ + admission toleration my-key=my-value --effect=NoSchedule + + To remove a memory limit: + + $ gcloud container hub policycontroller deployment remove audit \ + memory-limit + + To remove a memory request: + + $ gcloud container hub policycontroller deployment remove mutation \ + memory-request + + To remove a cpu limit: + + $ gcloud container hub policycontroller deployment remove \ + admission cpu-limit + + To remove a cpu request: + + $ gcloud container hub policycontroller deployment remove audit \ + cpu-request + +POSITIONAL ARGUMENTS + DEPLOYMENT + The PolicyController deployment component (i.e, "admission", "audit" or + "mutation" from which to remove configuration. + + PROPERTY + Property to be removed. + + [VALUE] + This is only required to remove a toleration. It should not be included + for any other property. + +FLAGS + --effect=EFFECT + Applies only to "toleration" property. To be removed, tolerations must + match exactly, including the effect setting. EFFECT must be one of: + NoSchedule, PreferNoSchedule, NoExecute. + + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container hub policycontroller deployment remove + + $ gcloud beta container hub policycontroller deployment remove + diff --git a/gcloud/container/hub/policycontroller/deployment/set b/gcloud/container/hub/policycontroller/deployment/set new file mode 100644 index 000000000..a9a850ae9 --- /dev/null +++ b/gcloud/container/hub/policycontroller/deployment/set @@ -0,0 +1,144 @@ +NAME + gcloud container hub policycontroller deployment set - sets configuration + of the Policy Controller components + +SYNOPSIS + gcloud container hub policycontroller deployment set DEPLOYMENT PROPERTY + VALUE [--effect=EFFECT] + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Customizes on-cluster components of Policy Controller. Supported properties + may be set with this command, or removed with 'remove'. These components + are managed as individual kubernetes deployments (e.g. 'admission') in the + gatekeeper-system namespace. + + When setting cpu or memory limits and requests, Kubernetes-standard + resource units are used. + + All properties set using this command will overwrite previous properties, + with the exception of tolerations which can only be added, and any number + may be added. To edit a toleration, use 'remove' to first delete it, and + then 'set' the desired toleration. + +EXAMPLES + To set the replica count for a component: + + $ gcloud container hub policycontroller deployment set admission \ + replica-count 3 + + To set the replica count for a component across all fleet memberships: + + $ gcloud container hub policycontroller deployment set admission \ + replica-count 3 --all-memberships + + To set a toleration with key 'my-key' on a component (which is an 'Exists' + operator): + + $ gcloud container hub policycontroller deployment set admission \ + toleration my-key + + To set a toleration with key 'my-key' and 'my-value' on a component (which + is an 'Equal' operator): + + $ gcloud container hub policycontroller deployment set admission \ + toleration my-key=my-value + + To set a toleration with key 'my-key' and 'my-value' on a component, along + with the effect 'NoSchedule' (which is an 'Equal' operator): + + $ gcloud container hub policycontroller deployment set admission \ + toleration my-key=my-value --effect=NoSchedule + + To set a memory limit: + + $ gcloud container hub policycontroller deployment set audit \ + memory-limit 4Gi + + To set a memory request: + + $ gcloud container hub policycontroller deployment set mutation \ + memory-request 2Gi + + To set a cpu limit: + + $ gcloud container hub policycontroller deployment set admission \ + cpu-limit 500m + + To set a cpu request: + + $ gcloud container hub policycontroller deployment set audit \ + cpu-request 250m + +POSITIONAL ARGUMENTS + DEPLOYMENT + The PolicyController deployment component (e.g. "admission", "audit" or + "mutation") upon which to set configuration. + + PROPERTY + Property to be set. + + VALUE + The value to set the property to. Valid input varies based on the + property being set. + +FLAGS + --effect=EFFECT + Applies only to "toleration" property. EFFECT must be one of: + NoSchedule, PreferNoSchedule, NoExecute. + + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container hub policycontroller deployment set + + $ gcloud beta container hub policycontroller deployment set + diff --git a/gcloud/container/hub/policycontroller/describe b/gcloud/container/hub/policycontroller/describe new file mode 100644 index 000000000..aa40c8d6d --- /dev/null +++ b/gcloud/container/hub/policycontroller/describe @@ -0,0 +1,69 @@ +NAME + gcloud container hub policycontroller describe - describe Policy Controller + feature + +SYNOPSIS + gcloud container hub policycontroller describe + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To describe the Policy Controller feature: + + $ gcloud container hub policycontroller describe + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container hub policycontroller describe + + $ gcloud beta container hub policycontroller describe + diff --git a/gcloud/container/hub/policycontroller/detach b/gcloud/container/hub/policycontroller/detach new file mode 100644 index 000000000..25fcae594 --- /dev/null +++ b/gcloud/container/hub/policycontroller/detach @@ -0,0 +1,78 @@ +NAME + gcloud container hub policycontroller detach - detach Policy Controller + Feature + +SYNOPSIS + gcloud container hub policycontroller detach + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Detaches Policy Controller. This will halt all administration of the Policy + Controller installation by the GKE Fleet. It will not uninstall it from the + cluster. To re-attach Policy Controller, use the enable command. + +EXAMPLES + To detach Policy Controller, run: + + $ gcloud container hub policycontroller detach + + To re-attach Policy Controller, use the enable command: + + $ gcloud container hub policycontroller enable + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container hub policycontroller detach + + $ gcloud beta container hub policycontroller detach + diff --git a/gcloud/container/hub/policycontroller/disable b/gcloud/container/hub/policycontroller/disable new file mode 100644 index 000000000..e9c620ad1 --- /dev/null +++ b/gcloud/container/hub/policycontroller/disable @@ -0,0 +1,82 @@ +NAME + gcloud container hub policycontroller disable - disable (Uninstall) Policy + Controller + +SYNOPSIS + gcloud container hub policycontroller disable + [--fleet-default-member-config | --all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Uninstalls Policy Controller. + +EXAMPLES + To uninstall Policy Controller, run: + + $ gcloud container hub policycontroller disable + +FLAGS + At most one of these can be specified: + + --fleet-default-member-config + Removes the fleet default configuration for policy controller. + Memberships configured with the fleet default will maintain their + current configuration. + + $ gcloud container hub policycontroller disable \ + --fleet-default-member-config + + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ◇ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ◇ provide the argument --memberships on the command line with a + fully specified name; + ◇ provide the argument --location on the command line; + ◇ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container hub policycontroller disable + + $ gcloud beta container hub policycontroller disable + diff --git a/gcloud/container/hub/policycontroller/enable b/gcloud/container/hub/policycontroller/enable new file mode 100644 index 000000000..cd243e56b --- /dev/null +++ b/gcloud/container/hub/policycontroller/enable @@ -0,0 +1,180 @@ +NAME + gcloud container hub policycontroller enable - enable Policy Controller + Feature + +SYNOPSIS + gcloud container hub policycontroller enable + [--all-memberships | [--memberships=[MEMBERSHIPS,...] + : --location=LOCATION] --audit-interval=AUDIT_INTERVAL + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + --no-default-bundles --version=VERSION --clear-exemptable-namespaces + | --exemptable-namespaces=EXEMPTABLE_NAMESPACES --log-denies + | --no-log-denies --monitoring=MONITORING + | --no-monitoring --mutation | --no-mutation --referential-rules + | --no-referential-rules + | --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + | --no-fleet-default-member-config] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Enables the Policy Controller Feature in a fleet. + +EXAMPLES + To enable the Policy Controller Feature, run: + + $ gcloud container hub policycontroller enable + +FLAGS + At most one of these can be specified: + + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a + fully specified name; + ▫ provide the argument --project on the command line; + ▫ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ◇ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ◇ provide the argument --memberships on the command line with a + fully specified name; + ◇ provide the argument --location on the command line; + ◇ set the property gkehub/location. + + --audit-interval=AUDIT_INTERVAL + How often Policy Controller will audit resources, in seconds. + + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + The number of violations stored on the constraint resource. Must be + greater than 0. + + --no-default-bundles + If set, skip installing the default bundle of policy-essentials. + + --version=VERSION + The version of Policy Controller to install; defaults to latest + version. + + Exemptable Namespace flags. + + At most one of these can be specified: + + --clear-exemptable-namespaces + Removes any namespace exemptions, enabling Policy Controller on all + namespaces. Setting this flag will overwrite currently exempted + namespaces, not append. + + --exemptable-namespaces=EXEMPTABLE_NAMESPACES + Namespaces that Policy Controller should ignore, separated by + commas if multiple are supplied. + + Log Denies flags. + + At most one of these can be specified: + + --log-denies + If set, log all denies and dry run failures. (To disable, use + --no-log-denies) + + --no-log-denies + If set, disable all log denies. + + Monitoring flags. + + At most one of these can be specified: + + --monitoring=MONITORING + Monitoring backend options Policy Controller should export metrics + to, separated by commas if multiple are supplied. Setting this flag + will overwrite currently enabled backends, not append. Options: + prometheus, cloudmonitoring + + --no-monitoring + Include this flag to disable the monitoring configuration of Policy + Controller. + + Mutation flags. + + At most one of these can be specified: + + --mutation + If set, enable support for mutation. (To disable, use + --no-mutation) + + --no-mutation + Disables mutation support. + + Referential Rules flags. + + At most one of these can be specified: + + --referential-rules + If set, enable support for referential constraints. (To disable, + use --no-referential-rules) + + --no-referential-rules + Disables referential rules support. + + Flags for setting Fleet Default Configuration files. + + At most one of these can be specified: + + --fleet-default-member-config=FLEET_DEFAULT_MEMBER_CONFIG + The path to a policy-controller.yaml configuration file. If + specified, this configuration will become the default Policy + Controller configuration for all memberships in your fleet. It can + be overridden with a membership-specific configuration by using the + the Update command. + + To enable the Policy Controller Feature with a fleet-level default + membership configuration, run: + + $ gcloud container hub policycontroller enable \ + --fleet-default-member-config=/path/to/policy-controller.yaml + + --no-fleet-default-member-config + Removes the fleet default configuration for policy controller. + Memberships configured with the fleet default will maintain their + current configuration. + + $ gcloud container hub policycontroller enable \ + --no-fleet-default-member-config + +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 + These variants are also available: + + $ gcloud alpha container hub policycontroller enable + + $ gcloud beta container hub policycontroller enable + diff --git a/gcloud/container/hub/policycontroller/help b/gcloud/container/hub/policycontroller/help new file mode 100644 index 000000000..774ac35ba --- /dev/null +++ b/gcloud/container/hub/policycontroller/help @@ -0,0 +1,52 @@ +NAME + gcloud container hub policycontroller - manage Policy Controller Feature + +SYNOPSIS + gcloud container hub policycontroller GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Policy Controller Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + content + Manage Policy Controller content. + + deployment + Configure Policy Controller component deployments. + +COMMANDS + COMMAND is one of the following: + + describe + Describe Policy Controller feature. + + detach + Detach Policy Controller Feature. + + disable + Disable (Uninstall) Policy Controller. + + enable + Enable Policy Controller Feature. + + suspend + Suspend Policy Controller Feature. + + update + Updates the configuration of Policy Controller Feature. + +NOTES + These variants are also available: + + $ gcloud alpha container hub policycontroller + + $ gcloud beta container hub policycontroller + diff --git a/gcloud/container/hub/policycontroller/suspend b/gcloud/container/hub/policycontroller/suspend new file mode 100644 index 000000000..172efaad3 --- /dev/null +++ b/gcloud/container/hub/policycontroller/suspend @@ -0,0 +1,78 @@ +NAME + gcloud container hub policycontroller suspend - suspend Policy Controller + Feature + +SYNOPSIS + gcloud container hub policycontroller suspend + [--all-memberships + | [--memberships=[MEMBERSHIPS,...] : --location=LOCATION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Suspends the Policy Controller. This will disable all kubernetes webhooks + on the configured cluster, thereby removing admission and mutation + functionality. Audit functionality will remain in place. + +EXAMPLES + To suspend Policy Controller, run: + + $ gcloud container hub policycontroller suspend + + To re-enable Policy Controller webhooks, use the enable command: + + $ gcloud container hub policycontroller enable + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + +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 + These variants are also available: + + $ gcloud alpha container hub policycontroller suspend + + $ gcloud beta container hub policycontroller suspend + diff --git a/gcloud/container/hub/policycontroller/update b/gcloud/container/hub/policycontroller/update new file mode 100644 index 000000000..b468fa5c0 --- /dev/null +++ b/gcloud/container/hub/policycontroller/update @@ -0,0 +1,161 @@ +NAME + gcloud container hub policycontroller update - updates the configuration of + Policy Controller Feature + +SYNOPSIS + gcloud container hub policycontroller update + [--all-memberships | [--memberships=[MEMBERSHIPS,...] + : --location=LOCATION] --origin=ORIGIN + | --audit-interval=AUDIT_INTERVAL + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + --version=VERSION --clear-exemptable-namespaces + | --exemptable-namespaces=EXEMPTABLE_NAMESPACES --log-denies + | --no-log-denies --monitoring=MONITORING + | --no-monitoring --mutation | --no-mutation --referential-rules + | --no-referential-rules] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates the configuration of the Policy Controller installation + +EXAMPLES + To change the installed version, run: + + $ gcloud container hub policycontroller update --version=VERSION + + To modify the audit interval to 120 seconds, run: + + $ gcloud container hub policycontroller update --audit-interval=120 + +FLAGS + Membership flags. + + At most one of these can be specified: + + --all-memberships + If supplied, apply to all Policy Controllers memberships in the + fleet. + + Membership resource - The group of arguments defining one or more + memberships. 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 --memberships on the command line with a fully + specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + --memberships=[MEMBERSHIPS,...] + IDs of the memberships or fully qualified identifiers for the + memberships. + + To set the memberships attribute: + ▫ provide the argument --memberships on the command line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --location=LOCATION + Location for the memberships. + + To set the location attribute: + ▫ provide the argument --memberships on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property gkehub/location. + + At most one of these can be specified: + + --origin=ORIGIN + If --origin=FLEET will set the configuration of the membership to the + fleet default. + + ORIGIN must be (only one value is supported): FLEET. + + --audit-interval=AUDIT_INTERVAL + How often Policy Controller will audit resources, in seconds. + + --constraint-violation-limit=CONSTRAINT_VIOLATION_LIMIT + The number of violations stored on the constraint resource. Must be + greater than 0. + + --version=VERSION + The version of Policy Controller to install; defaults to latest + version. + + Exemptable Namespace flags. + + At most one of these can be specified: + + --clear-exemptable-namespaces + Removes any namespace exemptions, enabling Policy Controller on all + namespaces. Setting this flag will overwrite currently exempted + namespaces, not append. + + --exemptable-namespaces=EXEMPTABLE_NAMESPACES + Namespaces that Policy Controller should ignore, separated by + commas if multiple are supplied. + + Log Denies flags. + + At most one of these can be specified: + + --log-denies + If set, log all denies and dry run failures. (To disable, use + --no-log-denies) + + --no-log-denies + If set, disable all log denies. + + Monitoring flags. + + At most one of these can be specified: + + --monitoring=MONITORING + Monitoring backend options Policy Controller should export metrics + to, separated by commas if multiple are supplied. Setting this flag + will overwrite currently enabled backends, not append. Options: + prometheus, cloudmonitoring + + --no-monitoring + Include this flag to disable the monitoring configuration of Policy + Controller. + + Mutation flags. + + At most one of these can be specified: + + --mutation + If set, enable support for mutation. (To disable, use + --no-mutation) + + --no-mutation + Disables mutation support. + + Referential Rules flags. + + At most one of these can be specified: + + --referential-rules + If set, enable support for referential constraints. (To disable, + use --no-referential-rules) + + --no-referential-rules + Disables referential rules support. + +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 + These variants are also available: + + $ gcloud alpha container hub policycontroller update + + $ gcloud beta container hub policycontroller update + diff --git a/gcloud/dataproc/clusters/create b/gcloud/dataproc/clusters/create index 178c47a63..6884cd185 100644 --- a/gcloud/dataproc/clusters/create +++ b/gcloud/dataproc/clusters/create @@ -24,6 +24,7 @@ SYNOPSIS [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] [--master-machine-type=MASTER_MACHINE_TYPE] [--master-min-cpu-platform=PLATFORM] [--max-idle=MAX_IDLE] + [--min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION] [--node-group=NODE_GROUP] [--num-driver-pool-local-ssds=NUM_DRIVER_POOL_LOCAL_SSDS] [--num-master-local-ssds=NUM_MASTER_LOCAL_SSDS] @@ -281,6 +282,13 @@ FLAGS such as "2h" or "1d". See $ gcloud topic datetimes for information on duration formats. + --min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION + Minimum fraction of secondary worker nodes required to create the + cluster. If it is not met, cluster creation will fail. Must be a + decimal value between 0 and 1. The number of required secondary workers + is calculated by ceil(min-secondary-worker-fraction * + num_secondary_workers). Defaults to 0.0001. + --node-group=NODE_GROUP The name of the sole-tenant node group to create the cluster on. Can be a short name ("node-group-name") or in the format diff --git a/gcloud/dataproc/clusters/update b/gcloud/dataproc/clusters/update index a23010d9f..6fb088648 100644 --- a/gcloud/dataproc/clusters/update +++ b/gcloud/dataproc/clusters/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud dataproc clusters update (CLUSTER : --region=REGION) [--async] [--graceful-decommission-timeout=GRACEFUL_DECOMMISSION_TIMEOUT] + [--min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION] [--num-secondary-workers=NUM_SECONDARY_WORKERS] [--num-workers=NUM_WORKERS] [--update-labels=[KEY=VALUE,...]] [--autoscaling-policy=AUTOSCALING_POLICY | --disable-autoscaling] @@ -91,6 +92,12 @@ FLAGS maximum allowed timeout is 1 day. See $ gcloud topic datetimes for information on duration formats. + --min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION + Minimum fraction of new secondary worker nodes added in a scale up + update operation, required to update the cluster. If it is not met, + cluster updation will rollback the addition of secondary workers. Must + be a decimal value between 0 and 1. Defaults to 0.0001. + --num-secondary-workers=NUM_SECONDARY_WORKERS The new number of secondary worker nodes in the cluster. diff --git a/gcloud/dataproc/workflow-templates/create b/gcloud/dataproc/workflow-templates/create index c0936b958..b6411f143 100644 --- a/gcloud/dataproc/workflow-templates/create +++ b/gcloud/dataproc/workflow-templates/create @@ -3,8 +3,8 @@ NAME SYNOPSIS gcloud dataproc workflow-templates create (TEMPLATE : --region=REGION) - [--dag-timeout=DAG_TIMEOUT] [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + [--dag-timeout=DAG_TIMEOUT] [--kms-key=KMS_KEY] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a workflow template. @@ -57,6 +57,9 @@ FLAGS auto-cancelled, such as "10m" or "16h". See $ gcloud topic datetimes for information on duration formats. + --kms-key=KMS_KEY + The KMS key used to encrypt sensitive data in the workflow template. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/dataproc/workflow-templates/set-managed-cluster b/gcloud/dataproc/workflow-templates/set-managed-cluster index 1d56dbdcd..0a1305009 100644 --- a/gcloud/dataproc/workflow-templates/set-managed-cluster +++ b/gcloud/dataproc/workflow-templates/set-managed-cluster @@ -16,7 +16,9 @@ SYNOPSIS [--master-boot-disk-type=MASTER_BOOT_DISK_TYPE] [--master-local-ssd-interface=MASTER_LOCAL_SSD_INTERFACE] [--master-machine-type=MASTER_MACHINE_TYPE] - [--master-min-cpu-platform=PLATFORM] [--node-group=NODE_GROUP] + [--master-min-cpu-platform=PLATFORM] + [--min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION] + [--node-group=NODE_GROUP] [--num-master-local-ssds=NUM_MASTER_LOCAL_SSDS] [--num-masters=NUM_MASTERS] [--num-secondary-worker-local-ssds=NUM_SECONDARY_WORKER_LOCAL_SSDS] @@ -204,6 +206,13 @@ FLAGS which contains the list of available CPU platforms in the zone (see Availability of CPU platforms for more information). + --min-secondary-worker-fraction=MIN_SECONDARY_WORKER_FRACTION + Minimum fraction of secondary worker nodes required to create the + cluster. If it is not met, cluster creation will fail. Must be a + decimal value between 0 and 1. The number of required secondary workers + is calculated by ceil(min-secondary-worker-fraction * + num_secondary_workers). Defaults to 0.0001. + --node-group=NODE_GROUP The name of the sole-tenant node group to create the cluster on. Can be a short name ("node-group-name") or in the format diff --git a/gcloud/deploy/apply b/gcloud/deploy/apply index e7f9df8ae..ffb4bc2c0 100644 --- a/gcloud/deploy/apply +++ b/gcloud/deploy/apply @@ -1,13 +1,13 @@ NAME - gcloud deploy apply - applies a yaml configuration containing Deliver - Pipeline(s), Target(s) declarative definitions + gcloud deploy apply - applies a yaml configuration containing Delivery + Pipeline(s), Target(s) and Automation(s) declarative definitions SYNOPSIS gcloud deploy apply --file=FILE [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Applies a yaml configuration containing Deliver Pipeline(s), Target(s) - declarative definitions. + Applies a yaml configuration containing Delivery Pipeline(s), Target(s) and + Automation(s) declarative definitions. EXAMPLES To apply a Cloud Deploy YAML file deploy.yaml: diff --git a/gcloud/deploy/automation-runs/cancel b/gcloud/deploy/automation-runs/cancel new file mode 100644 index 000000000..1b93991e7 --- /dev/null +++ b/gcloud/deploy/automation-runs/cancel @@ -0,0 +1,79 @@ +NAME + gcloud deploy automation-runs cancel - cancels a Cloud Deploy Automation + Run + +SYNOPSIS + gcloud deploy automation-runs cancel + (AUTOMATION_RUN + : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Cancels a Cloud Deploy Automation Run. + +EXAMPLES + To cancel an AutomationRun test-run for delivery pipeline test-pipeline in + region us-central1, run: + + $ gcloud deploy automation-runs cancel test-run \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation run resource - The name of the AutomationRun. 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 automation_run 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. + + AUTOMATION_RUN + ID of the automation_run or fully qualified identifier for the + automation_run. + + To set the name attribute: + ▸ provide the argument automation_run on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The delivery pipeline associated with the automation_run. + Alternatively, set the property [deploy/delivery-pipeline]. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation_run on the command line with a + fully specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + The Cloud region for the automation_run. Alternatively, set the + property [deploy/region]. + + To set the region attribute: + ▸ provide the argument automation_run on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha deploy automation-runs cancel + + $ gcloud beta deploy automation-runs cancel + diff --git a/gcloud/deploy/automation-runs/describe b/gcloud/deploy/automation-runs/describe new file mode 100644 index 000000000..4d673fd24 --- /dev/null +++ b/gcloud/deploy/automation-runs/describe @@ -0,0 +1,80 @@ +NAME + gcloud deploy automation-runs describe - show details for an Automation Run + +SYNOPSIS + gcloud deploy automation-runs describe + (AUTOMATION_RUN + : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details for a specified automation run. + +EXAMPLES + To show details about a automation run 'test-automationrun', for delivery + pipeline 'test-pipeline', in region 'us-central1', run: + + $ gcloud deploy automation-runs describe test-automationrun \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation run resource - The name of the automation run you want to + describe. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument automation_run 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. + + AUTOMATION_RUN + ID of the automation run or fully qualified identifier for the + automation run. + + To set the automation_run attribute: + ▸ provide the argument automation_run on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The name of the Cloud Deploy delivery pipeline. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation_run on the command line with a + fully specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + Location of the automation run. + + To set the region attribute: + ▸ provide the argument automation_run on the command line with a + fully specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + These variants are also available: + + $ gcloud alpha deploy automation-runs describe + + $ gcloud beta deploy automation-runs describe + diff --git a/gcloud/deploy/automation-runs/help b/gcloud/deploy/automation-runs/help new file mode 100644 index 000000000..5ca542de9 --- /dev/null +++ b/gcloud/deploy/automation-runs/help @@ -0,0 +1,34 @@ +NAME + gcloud deploy automation-runs - manages AutomationRuns resources for Cloud + Deploy + +SYNOPSIS + gcloud deploy automation-runs COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manages AutomationRuns resources for Cloud Deploy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + Cancels a Cloud Deploy Automation Run. + + describe + Show details for an Automation Run. + + list + List the Automation Runs. + +NOTES + These variants are also available: + + $ gcloud alpha deploy automation-runs + + $ gcloud beta deploy automation-runs + diff --git a/gcloud/deploy/automation-runs/list b/gcloud/deploy/automation-runs/list new file mode 100644 index 000000000..9f8eefaf4 --- /dev/null +++ b/gcloud/deploy/automation-runs/list @@ -0,0 +1,103 @@ +NAME + gcloud deploy automation-runs list - list the Automation Runs + +SYNOPSIS + gcloud deploy automation-runs list + [--delivery-pipeline=DELIVERY_PIPELINE --region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List the automation runs for a specified delivery pipeline. + +EXAMPLES + To list the automation runs for delivery pipeline 'test-pipeline' in region + 'us-central1', run: + + $ gcloud deploy automation-runs list \ + --delivery-pipeline=test-pipeline --region=us-central1 + +FLAGS + Delivery pipeline resource - The delivery pipeline for which you want to + list the automation runs. 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 --delivery-pipeline on the command line with a + fully specified name; + ◆ set the property deploy/delivery_pipeline with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --delivery-pipeline=DELIVERY_PIPELINE + ID of the delivery_pipeline or fully qualified identifier for the + delivery_pipeline. + + To set the delivery-pipeline attribute: + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + Location of the delivery_pipeline. + + To set the region attribute: + ▸ provide the argument --delivery-pipeline on the command line with + a fully specified name; + ▸ set the property deploy/delivery_pipeline with a fully specified + name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + These variants are also available: + + $ gcloud alpha deploy automation-runs list + + $ gcloud beta deploy automation-runs list + diff --git a/gcloud/deploy/automations/delete b/gcloud/deploy/automations/delete new file mode 100644 index 000000000..312e01942 --- /dev/null +++ b/gcloud/deploy/automations/delete @@ -0,0 +1,77 @@ +NAME + gcloud deploy automations delete - deletes a Cloud Deploy Automation + +SYNOPSIS + gcloud deploy automations delete + (AUTOMATION : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Deletes a Cloud Deploy Automation. + +EXAMPLES + To delete an automation test-automation for delivery pipeline + test-pipeline, in region us-central1, run: + + $ gcloud deploy automations delete test-automation \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation resource - The name of the Automation. 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 automation 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. + + AUTOMATION + ID of the automation or fully qualified identifier for the + automation. + + To set the name attribute: + ▸ provide the argument automation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The delivery pipeline associated with the automation. Alternatively, + set the property [deploy/delivery-pipeline]. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + The Cloud region for the automation. Alternatively, set the property + [deploy/region]. + + To set the region attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha deploy automations delete + + $ gcloud beta deploy automations delete + diff --git a/gcloud/deploy/automations/describe b/gcloud/deploy/automations/describe new file mode 100644 index 000000000..4ba8aabb8 --- /dev/null +++ b/gcloud/deploy/automations/describe @@ -0,0 +1,79 @@ +NAME + gcloud deploy automations describe - show details for an Automation + +SYNOPSIS + gcloud deploy automations describe + (AUTOMATION : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details for a specified automation. + +EXAMPLES + To show details about an automation 'test-automation', for delivery + pipeline 'test-pipeline', in region 'us-central1', run: + + $ gcloud deploy automations describe test-automation \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation resource - The name of the automation you want to describe. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument automation 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. + + AUTOMATION + ID of the automation or fully qualified identifier for the + automation. + + To set the automation attribute: + ▸ provide the argument automation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The name of the Cloud Deploy delivery pipeline. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + Location of the automation. + + To set the region attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + These variants are also available: + + $ gcloud alpha deploy automations describe + + $ gcloud beta deploy automations describe + diff --git a/gcloud/deploy/automations/export b/gcloud/deploy/automations/export new file mode 100644 index 000000000..d65c31596 --- /dev/null +++ b/gcloud/deploy/automations/export @@ -0,0 +1,84 @@ +NAME + gcloud deploy automations export - returns the YAML definition of the + specified Automation + +SYNOPSIS + gcloud deploy automations export + (AUTOMATION : --delivery-pipeline=DELIVERY_PIPELINE --region=REGION) + [--destination=DESTINATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The exported yaml definition can be applied by using the deploy apply + command. + +EXAMPLES + To return the YAML definition of the automation test-automation of delivery + pipeline test-pipeline, in region us-central1, run: + + $ gcloud deploy automations export test-automation \ + --delivery-pipeline=test-pipeline --region=us-central1 + +POSITIONAL ARGUMENTS + Automation resource - The name of the Automation. 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 automation 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. + + AUTOMATION + ID of the automation or fully qualified identifier for the + automation. + + To set the name attribute: + ▸ provide the argument automation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --delivery-pipeline=DELIVERY_PIPELINE + The delivery pipeline associated with the automation. Alternatively, + set the property [deploy/delivery-pipeline]. + + To set the delivery-pipeline attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + The Cloud region for the automation. Alternatively, set the property + [deploy/region]. + + To set the region attribute: + ▸ provide the argument automation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. + Alternatively, you may omit this flag to write to standard output. + +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 + These variants are also available: + + $ gcloud alpha deploy automations export + + $ gcloud beta deploy automations export + diff --git a/gcloud/deploy/automations/help b/gcloud/deploy/automations/help new file mode 100644 index 000000000..db7aa0271 --- /dev/null +++ b/gcloud/deploy/automations/help @@ -0,0 +1,36 @@ +NAME + gcloud deploy automations - manages Automations resources for Cloud Deploy + +SYNOPSIS + gcloud deploy automations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manages Automations resources for Cloud Deploy. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + Deletes a Cloud Deploy Automation. + + describe + Show details for an Automation. + + export + Returns the YAML definition of the specified Automation. + + list + List the Automations. + +NOTES + These variants are also available: + + $ gcloud alpha deploy automations + + $ gcloud beta deploy automations + diff --git a/gcloud/deploy/automations/list b/gcloud/deploy/automations/list new file mode 100644 index 000000000..deb0ed0cc --- /dev/null +++ b/gcloud/deploy/automations/list @@ -0,0 +1,103 @@ +NAME + gcloud deploy automations list - list the Automations + +SYNOPSIS + gcloud deploy automations list + [--delivery-pipeline=DELIVERY_PIPELINE --region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List the automations for a specified delivery pipeline. + +EXAMPLES + To list the automations for delivery pipeline 'test-pipeline' in region + 'us-central1', run: + + $ gcloud deploy automations list --delivery-pipeline=test-pipeline \ + --region=us-central1 + +FLAGS + Delivery pipeline resource - The delivery pipeline for which you want to + list the automations. 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 --delivery-pipeline on the command line with a + fully specified name; + ◆ set the property deploy/delivery_pipeline with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --delivery-pipeline=DELIVERY_PIPELINE + ID of the delivery_pipeline or fully qualified identifier for the + delivery_pipeline. + + To set the delivery-pipeline attribute: + ▸ provide the argument --delivery-pipeline on the command line; + ▸ set the property deploy/delivery_pipeline. + + --region=REGION + Location of the delivery_pipeline. + + To set the region attribute: + ▸ provide the argument --delivery-pipeline on the command line with + a fully specified name; + ▸ set the property deploy/delivery_pipeline with a fully specified + name; + ▸ provide the argument --region on the command line; + ▸ set the property deploy/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the clouddeploy/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/deploy/ + +NOTES + These variants are also available: + + $ gcloud alpha deploy automations list + + $ gcloud beta deploy automations list + diff --git a/gcloud/deploy/help b/gcloud/deploy/help index 4379bd0dd..1ddffcffb 100644 --- a/gcloud/deploy/help +++ b/gcloud/deploy/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + automation-runs + Manages AutomationRuns resources for Cloud Deploy. + + automations + Manages Automations resources for Cloud Deploy. + delivery-pipelines Create and manage Delivery Pipeline resources for Cloud Deploy. @@ -34,8 +40,8 @@ COMMANDS COMMAND is one of the following: apply - Applies a yaml configuration containing Deliver Pipeline(s), Target(s) - declarative definitions. + Applies a yaml configuration containing Delivery Pipeline(s), Target(s) + and Automation(s) declarative definitions. delete Deletes delivery pipeline(s) and target(s) in a yaml configuration. diff --git a/gcloud/edge-cloud/container/clusters/help b/gcloud/edge-cloud/container/clusters/help index ce3c725a4..5b435845b 100644 --- a/gcloud/edge-cloud/container/clusters/help +++ b/gcloud/edge-cloud/container/clusters/help @@ -39,6 +39,9 @@ COMMANDS update Update an Edge Container cluster. + upgrade + Upgrade an Edge Container cluster. + NOTES This variant is also available: diff --git a/gcloud/edge-cloud/container/clusters/upgrade b/gcloud/edge-cloud/container/clusters/upgrade new file mode 100644 index 000000000..74b3402fa --- /dev/null +++ b/gcloud/edge-cloud/container/clusters/upgrade @@ -0,0 +1,74 @@ +NAME + gcloud edge-cloud container clusters upgrade - upgrade an Edge Container + cluster + +SYNOPSIS + gcloud edge-cloud container clusters upgrade + (CLUSTER : --location=LOCATION) --schedule=SCHEDULE --version=VERSION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Upgrade an Edge Container cluster. + +EXAMPLES + To upgrade an Edge Container cluster to 1.5.1 immediately, run: + + $ gcloud edge-cloud container clusters upgrade my-cluster \ + --version=1.5.1 --schedule=IMMEDIATELY + +POSITIONAL ARGUMENTS + Cluster resource - Edge Container cluster to upgrade. 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + 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. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location for the cluster. + + To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --schedule=SCHEDULE + Schedule to upgrade a cluster after the request is acknowledged by + Google. Support values: IMMEDIATELY. + + --version=VERSION + Target cluster version to upgrade to. For example: "1.5.1". + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the edgecontainer/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/edge-cloud + +NOTES + This variant is also available: + + $ gcloud alpha edge-cloud container clusters upgrade + diff --git a/gcloud/edge-cloud/container/vpn-connections/create b/gcloud/edge-cloud/container/vpn-connections/create index 99565d6ec..43d5bb905 100644 --- a/gcloud/edge-cloud/container/vpn-connections/create +++ b/gcloud/edge-cloud/container/vpn-connections/create @@ -6,8 +6,8 @@ SYNOPSIS gcloud edge-cloud container vpn-connections create VPN_CONNECTION --cluster=CLUSTER --vpc-network=VPC_NETWORK [--async] [--high-availability] [--labels=[KEY=VALUE,...]] [--location=LOCATION] - [--nat-gateway-ip=NAT_GATEWAY_IP] [--vpc-project=VPC_PROJECT] - [GCLOUD_WIDE_FLAG ...] + [--nat-gateway-ip=NAT_GATEWAY_IP] [--router=ROUTER] + [--vpc-project=VPC_PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Creates a new VPN connection. @@ -106,6 +106,12 @@ OPTIONAL FLAGS The NAT gateway IP for the gateway floating IPs. Required if cluster sits behind NAT. + --router=ROUTER + Name of the Cloud Router to use when creating the VPN connection. This + Cloud Router must be in the same region as the cluster and connected to + the provided VPC network. If not provided, a service-managed Cloud + Router will either be created or reused to create the VPN connection. + --vpc-project=VPC_PROJECT The project of the VPC network. Required if the project of VPC network differs from the project of the cluster. diff --git a/gcloud/iam/workforce-pools/create b/gcloud/iam/workforce-pools/create index c62fde816..33d197582 100644 --- a/gcloud/iam/workforce-pools/create +++ b/gcloud/iam/workforce-pools/create @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud iam workforce-pools create (WORKFORCE_POOL : --location=LOCATION) - --organization=ORGANIZATION [--async] [--description=DESCRIPTION] + --organization=ORGANIZATION [--allowed-services=[domain=DOMAIN]] + [--async] [--description=DESCRIPTION] [--disable-programmatic-signin] [--disabled] [--display-name=DISPLAY_NAME] [--session-duration=SESSION_DURATION] [GCLOUD_WIDE_FLAG ...] @@ -57,6 +58,12 @@ REQUIRED FLAGS The parent organization of the workforce pool to create. OPTIONAL FLAGS + --allowed-services=[domain=DOMAIN] + Services allowed for web sign-in with the workforce pool. The flag + accepts multiple values with the key as domain and value as the domain + of the service allowed for web sign-in. If not set, by default all the + services are allowed. + --async Return immediately, without waiting for the operation in progress to complete. @@ -65,6 +72,9 @@ OPTIONAL FLAGS A description for the workforce pool. Cannot exceed 256 characters in length. + --disable-programmatic-signin + Disable programmatic sign-in for workforce pool users. + --disabled Whether or not the workforce pool is disabled. diff --git a/gcloud/iam/workforce-pools/update b/gcloud/iam/workforce-pools/update index 8bb7fbdc1..53ecce9ab 100644 --- a/gcloud/iam/workforce-pools/update +++ b/gcloud/iam/workforce-pools/update @@ -3,9 +3,9 @@ NAME SYNOPSIS gcloud iam workforce-pools update (WORKFORCE_POOL : --location=LOCATION) - [--async] [--description=DESCRIPTION] [--disabled] - [--display-name=DISPLAY_NAME] [--session-duration=SESSION_DURATION] - [GCLOUD_WIDE_FLAG ...] + [--async] [--description=DESCRIPTION] [--disable-programmatic-signin] + [--disabled] [--display-name=DISPLAY_NAME] + [--session-duration=SESSION_DURATION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a workforce pool. @@ -52,6 +52,13 @@ FLAGS A description for the workforce pool. Cannot exceed 256 characters in length. + --disable-programmatic-signin + Disables the programmatic sign-in for workforce pool users. Specify + --no-disable-security-token-exchange to enable programmatic sign-in. + For more information, refer to Obtain short-lived tokens for workforce + identity federation at + https://cloud.google.com/iam/docs/workforce-obtaining-short-lived-credentials + --disabled Disables the workforce pool. You cannot use a disabled workforce pool to perform new token exchanges or sign-ins using any provider in the diff --git a/gcloud/looker/help b/gcloud/looker/help index e494d005b..3e8b4ccd1 100644 --- a/gcloud/looker/help +++ b/gcloud/looker/help @@ -21,6 +21,9 @@ GROUPS operations Manage Looker operations. + regions + Manage Looker regions. + NOTES This variant is also available: diff --git a/gcloud/looker/regions/help b/gcloud/looker/regions/help new file mode 100644 index 000000000..c48a7a4e5 --- /dev/null +++ b/gcloud/looker/regions/help @@ -0,0 +1,27 @@ +NAME + gcloud looker regions - manage Looker regions + +SYNOPSIS + gcloud looker regions COMMAND [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all available regions, run: + + $ gcloud looker regions list + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + List Looker regions. + +NOTES + This variant is also available: + + $ gcloud alpha looker regions + diff --git a/gcloud/looker/regions/list b/gcloud/looker/regions/list new file mode 100644 index 000000000..de770228c --- /dev/null +++ b/gcloud/looker/regions/list @@ -0,0 +1,65 @@ +NAME + gcloud looker regions list - list Looker regions + +SYNOPSIS + gcloud looker regions list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all available Looker regions. + +EXAMPLES + To list all available Looker regions, run: + + $ gcloud looker regions list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/looker/docs/reference/rest/ + +NOTES + This variant is also available: + + $ gcloud alpha looker regions list + diff --git a/gcloud/ml/speech/recognize b/gcloud/ml/speech/recognize index ce32e55b9..d0cb95704 100644 --- a/gcloud/ml/speech/recognize +++ b/gcloud/ml/speech/recognize @@ -50,7 +50,7 @@ OPTIONAL FLAGS --encoding=ENCODING; default="encoding-unspecified" The type of encoding of the file. Required if the file format is not WAV or FLAC. ENCODING must be one of: amr, amr-wb, - encoding-unspecified, flac, linear16, mulaw, ogg-opus, + encoding-unspecified, flac, linear16, mp3, mulaw, ogg-opus, speex-with-header-byte, webm-opus. --filter-profanity diff --git a/gcloud/ml/speech/recognize-long-running b/gcloud/ml/speech/recognize-long-running index 232a54c52..8db329717 100644 --- a/gcloud/ml/speech/recognize-long-running +++ b/gcloud/ml/speech/recognize-long-running @@ -59,7 +59,7 @@ OPTIONAL FLAGS --encoding=ENCODING; default="encoding-unspecified" The type of encoding of the file. Required if the file format is not WAV or FLAC. ENCODING must be one of: amr, amr-wb, - encoding-unspecified, flac, linear16, mulaw, ogg-opus, + encoding-unspecified, flac, linear16, mp3, mulaw, ogg-opus, speex-with-header-byte, webm-opus. --filter-profanity diff --git a/gcloud/privateca/subordinates/create b/gcloud/privateca/subordinates/create index 093d0a3a5..c9f04d040 100644 --- a/gcloud/privateca/subordinates/create +++ b/gcloud/privateca/subordinates/create @@ -6,13 +6,12 @@ SYNOPSIS gcloud privateca subordinates create (CERTIFICATE_AUTHORITY : --location=LOCATION --pool=POOL) (--create-csr --csr-output-file=CSR_OUTPUT_FILE - | --issuer-ca=ISSUER_CA [--issuer-pool=ISSUER_POOL - : --issuer-location=ISSUER_LOCATION]) [--auto-enable] - [--bucket=BUCKET] [--dns-san=[DNS_SAN,...]] + | [--issuer-pool=ISSUER_POOL : --issuer-location=ISSUER_LOCATION]) + [--auto-enable] [--bucket=BUCKET] [--dns-san=[DNS_SAN,...]] [--email-san=[EMAIL_SAN,...]] [--from-ca=FROM_CA] - [--ip-san=[IP_SAN,...]] [--labels=[KEY=VALUE,...]] - [--subject=[SUBJECT,...]] [--uri-san=[URI_SAN,...]] - [--validity=VALIDITY; default="P3Y"] + [--ip-san=[IP_SAN,...]] [--issuer-ca=ISSUER_CA] + [--labels=[KEY=VALUE,...]] [--subject=[SUBJECT,...]] + [--uri-san=[URI_SAN,...]] [--validity=VALIDITY; default="P3Y"] [--key-algorithm=KEY_ALGORITHM; default="rsa-pkcs1-2048-sha256" | [--kms-key-version=KMS_KEY_VERSION : --kms-key=KMS_KEY --kms-keyring=KMS_KEYRING @@ -125,11 +124,6 @@ REQUIRED FLAGS The issuing resource used for this CA certificate. - --issuer-ca=ISSUER_CA - The Certificate Authority ID of the CA to issue the subordinate CA - certificate from. This ID is optional. If ommitted, any available - ENABLED CA in the issuing CA pool will be chosen. - Issuer resource - The issuing CA Pool to use, if it is on Private CA. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this @@ -208,6 +202,11 @@ OPTIONAL FLAGS --ip-san=[IP_SAN,...] One or more comma-separated IP Subject Alternative Names. + --issuer-ca=ISSUER_CA + The Certificate Authority ID of the CA to issue the subordinate CA + certificate from. This ID is optional. If ommitted, any available + ENABLED CA in the issuing CA pool will be chosen. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/pubsub/schemas/create b/gcloud/pubsub/schemas/create index c8ccc7797..7ab5dbd04 100644 --- a/gcloud/pubsub/schemas/create +++ b/gcloud/pubsub/schemas/create @@ -41,8 +41,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --type=TYPE - Type of the schema. TYPE must be one of: avro, protocol-buffer, - type-unspecified. + Type of the schema. TYPE must be one of: avro, protocol-buffer. Schema definition. diff --git a/gcloud/pubsub/schemas/validate-message b/gcloud/pubsub/schemas/validate-message index 01a7ffc1c..a6fadae1f 100644 --- a/gcloud/pubsub/schemas/validate-message +++ b/gcloud/pubsub/schemas/validate-message @@ -32,7 +32,7 @@ REQUIRED FLAGS --message-encoding=MESSAGE_ENCODING The encoding of the message. MESSAGE_ENCODING must be one of: binary, - encoding-unspecified, json. + json. Schema definition. @@ -42,8 +42,7 @@ REQUIRED FLAGS Name or full path of an existing schema. --type=TYPE - Type of inline schema. TYPE must be one of: avro, protocol-buffer, - type-unspecified. + Type of inline schema. TYPE must be one of: avro, protocol-buffer. This flag argument must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/pubsub/schemas/validate-schema b/gcloud/pubsub/schemas/validate-schema index ca76f835e..dde988457 100644 --- a/gcloud/pubsub/schemas/validate-schema +++ b/gcloud/pubsub/schemas/validate-schema @@ -25,8 +25,7 @@ EXAMPLES REQUIRED FLAGS --type=TYPE - Type of the schema. TYPE must be one of: avro, protocol-buffer, - type-unspecified. + Type of the schema. TYPE must be one of: avro, protocol-buffer. Schema definition. diff --git a/gcloud/scc/muteconfigs/update b/gcloud/scc/muteconfigs/update index e003ea609..590310a3f 100644 --- a/gcloud/scc/muteconfigs/update +++ b/gcloud/scc/muteconfigs/update @@ -12,7 +12,7 @@ DESCRIPTION Update a Cloud Security Command Center mute config. EXAMPLES - Update a mute config with id my-test-mute-config under organization 123 + Update a mute config with ID=my-test-mute-config under organization=123 with a filter on category that equals to XSS_SCRIPTING: $ gcloud scc muteconfigs update my-test-mute-config \ @@ -27,7 +27,7 @@ EXAMPLES --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - Update a mute config with id my-test-mute-config under folder 456 with a + Update a mute config with ID=my-test-mute-config under folder=456 with a filter on category that equals to XSS_SCRIPTING: $ gcloud scc muteconfigs update my-test-mute-config \ @@ -42,7 +42,7 @@ EXAMPLES --description="This is a test mute config" \ --filter="category=\"XSS_SCRIPTING\"" - Update a mute config with id my-test-mute-config under project 789 with a + Update a mute config with ID=my-test-mute-config under project=789 with a filter on category that equals to XSS_SCRIPTING: $ gcloud scc muteconfigs update my-test-mute-config \ diff --git a/gcloud/spanner/instances/create b/gcloud/spanner/instances/create index 8cf92e1e1..0e6e38257 100644 --- a/gcloud/spanner/instances/create +++ b/gcloud/spanner/instances/create @@ -5,8 +5,7 @@ SYNOPSIS gcloud spanner instances create INSTANCE --config=CONFIG --description=DESCRIPTION [--async] [--expire-behavior=EXPIRE_BEHAVIOR] [--instance-type=INSTANCE_TYPE] - [--nodes=NODES | --processing-units=PROCESSING_UNITS - | --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET (--autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS)] + [--nodes=NODES | --processing-units=PROCESSING_UNITS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -68,52 +67,6 @@ OPTIONAL FLAGS --processing-units=PROCESSING_UNITS Number of processing units for the instance. - Autoscaling - - --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET - Specifies the target percentage of high-priority CPU the autoscaled - instance can utilize. - - This flag argument must be specified if any of the other arguments - in this group are specified. - - --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET - Specifies the target percentage of storage the autoscaled instance - can utilize. - - This flag argument must be specified if any of the other arguments - in this group are specified. - - Exactly one of these must be specified: - - Autoscaling limits in nodes - - --autoscaling-max-nodes=AUTOSCALING_MAX_NODES - Maximum number of nodes for the autoscaled instance. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --autoscaling-min-nodes=AUTOSCALING_MIN_NODES - Minimum number of nodes for the autoscaled instance. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - Autoscaling limits in processing units - - --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS - Maximum number of processing units for the autoscaled instance. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS - Minimum number of processing units for the autoscaled instance. - - This flag argument must be specified if any of the other - arguments in this group are specified. - 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/spanner/instances/update b/gcloud/spanner/instances/update index 4d0a4d283..b88ec0ff4 100644 --- a/gcloud/spanner/instances/update +++ b/gcloud/spanner/instances/update @@ -5,8 +5,7 @@ SYNOPSIS gcloud spanner instances update INSTANCE [--async] [--description=DESCRIPTION] [--expire-behavior=EXPIRE_BEHAVIOR] [--instance-type=INSTANCE_TYPE] - [--nodes=NODES | --processing-units=PROCESSING_UNITS - | --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET --autoscaling-max-nodes=AUTOSCALING_MAX_NODES --autoscaling-min-nodes=AUTOSCALING_MIN_NODES | --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS] + [--nodes=NODES | --processing-units=PROCESSING_UNITS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -65,34 +64,6 @@ FLAGS --processing-units=PROCESSING_UNITS Number of processing units for the instance. - Autoscaling - - --autoscaling-high-priority-cpu-target=AUTOSCALING_HIGH_PRIORITY_CPU_TARGET - Specifies the target percentage of high-priority CPU the autoscaled - instance can utilize. - - --autoscaling-storage-target=AUTOSCALING_STORAGE_TARGET - Specifies the target percentage of storage the autoscaled instance - can utilize. - - At most one of these can be specified: - - Autoscaling limits in nodes - - --autoscaling-max-nodes=AUTOSCALING_MAX_NODES - Maximum number of nodes for the autoscaled instance. - - --autoscaling-min-nodes=AUTOSCALING_MIN_NODES - Minimum number of nodes for the autoscaled instance. - - Autoscaling limits in processing units - - --autoscaling-max-processing-units=AUTOSCALING_MAX_PROCESSING_UNITS - Maximum number of processing units for the autoscaled instance. - - --autoscaling-min-processing-units=AUTOSCALING_MIN_PROCESSING_UNITS - Minimum number of processing units for the autoscaled instance. - 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/sql/instances/create b/gcloud/sql/instances/create index b92b8ae24..40091105e 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -11,9 +11,9 @@ SYNOPSIS [--authorized-networks=NETWORK,[NETWORK,...]] [--availability-type=AVAILABILITY_TYPE] [--no-backup] [--backup-location=BACKUP_LOCATION] - [--backup-start-time=BACKUP_START_TIME] [--collation=COLLATION] - [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] - [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--backup-start-time=BACKUP_START_TIME] [--cascadable-replica] + [--collation=COLLATION] [--connector-enforcement=CONNECTOR_ENFORCEMENT] + [--cpu=CPU] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--database-version=DATABASE_VERSION; default="MYSQL_8_0"] [--[no-]deletion-protection] [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] @@ -152,6 +152,13 @@ FLAGS Start time of daily backups, specified in the HH:MM format, in the UTC timezone. + --cascadable-replica + Specifies whether a SQL Server replica is a cascadable replica. A + cascadable replica is a SQL Server cross-region replica that supports + replica(s) under it. This flag only takes effect when the + --master-instance-name flag is set, and the replica under creation is + in a different region than the primary instance. + --collation=COLLATION Cloud SQL server-level collation setting, which specifies the set of rules for comparing characters in a character set. diff --git a/gcloud/sql/instances/promote-replica b/gcloud/sql/instances/promote-replica index 2b5413ec7..903f8840e 100644 --- a/gcloud/sql/instances/promote-replica +++ b/gcloud/sql/instances/promote-replica @@ -3,7 +3,7 @@ NAME stand-alone instance SYNOPSIS - gcloud sql instances promote-replica REPLICA [--async] + gcloud sql instances promote-replica REPLICA [--async] [--[no-]failover] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -18,6 +18,10 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --[no-]failover + Whether the promote operation is a failover. Use --failover to enable + and --no-failover to disable. + 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/storage/buckets/create b/gcloud/storage/buckets/create index 7bcc7a4b2..83cf7dbeb 100644 --- a/gcloud/storage/buckets/create +++ b/gcloud/storage/buckets/create @@ -13,6 +13,7 @@ SYNOPSIS [--placement=REGION,REGION] [--recovery-point-objective=SETTING, --rpo=SETTING] [--retention-period=RETENTION_PERIOD] + [--soft-delete-duration=SOFT_DELETE_DURATION] [--[no-]uniform-bucket-level-access, -b] [--autoclass-terminal-storage-class=AUTOCLASS_TERMINAL_STORAGE_CLASS --[no-]enable-autoclass] [GCLOUD_WIDE_FLAG ...] @@ -94,6 +95,13 @@ FLAGS Default is no retention period. Only available for Cloud Storage using the JSON API. + --soft-delete-duration=SOFT_DELETE_DURATION + Duration to retain soft-deleted objects. For example, "2w1d" is two + weeks and one day. The presence of this flag creates a bucket with a + soft delete policy enabled, meaning deleted objects can be restored if + requested within the inputted duration. See gcloud topic datetimes for + more information on the duration format. + --[no-]uniform-bucket-level-access, -b Turns on uniform bucket-level access setting. Default is False. Use --uniform-bucket-level-access to enable and diff --git a/gcloud/storage/buckets/update b/gcloud/storage/buckets/update index 5cc2428ee..7757262a3 100644 --- a/gcloud/storage/buckets/update +++ b/gcloud/storage/buckets/update @@ -3,13 +3,13 @@ NAME SYNOPSIS gcloud storage buckets update URL [URL ...] - [--additional-headers=HEADER=VALUE] [--continue-on-error, -c] - [--[no-]default-event-based-hold] + [--additional-headers=HEADER=VALUE] [--clear-soft-delete] + [--continue-on-error, -c] [--[no-]default-event-based-hold] [--default-storage-class=DEFAULT_STORAGE_CLASS] [--lock-retention-period] [--recovery-point-objective=SETTING, --rpo=SETTING] - [--[no-]requester-pays] [--[no-]uniform-bucket-level-access] - [--[no-]versioning] + [--[no-]requester-pays] [--soft-delete-duration=SOFT_DELETE_DURATION] + [--[no-]uniform-bucket-level-access] [--[no-]versioning] [--acl-file=ACL_FILE --add-acl-grant=[ACL_GRANT,...] --canned-acl=PREDEFINED_ACL, --predefined-acl=PREDEFINED_ACL, -a PREDEFINED_ACL --remove-acl-grant=REMOVE_ACL_GRANT] @@ -67,6 +67,10 @@ FLAGS Overrides the default storage/additional_headers property value for this command invocation. + --clear-soft-delete + Clears bucket soft delete settings. Does not affect objects already in + soft-deleted state. + --continue-on-error, -c If any operations are unsuccessful, the command will exit with a non-zero exit status after completing the remaining operations. This @@ -106,6 +110,10 @@ FLAGS pays all costs related to accessing the bucket and its objects. Use --requester-pays to enable and --no-requester-pays to disable. + --soft-delete-duration=SOFT_DELETE_DURATION + Duration to retain soft-deleted objects. For example, "2w1d" is two + weeks and one day. + --[no-]uniform-bucket-level-access Enables or disables uniform bucket-level access (https://cloud.google.com/storage/docs/bucket-policy-only) for the diff --git a/gcloud/storage/cp b/gcloud/storage/cp index db735ee81..a0043f8c3 100644 --- a/gcloud/storage/cp +++ b/gcloud/storage/cp @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud storage cp [SOURCE ...] DESTINATION [--additional-headers=HEADER=VALUE] [--all-versions, -A] - [--no-clobber, -n] [--continue-on-error, -c] [--daisy-chain, -D] - [--do-not-decompress] [--manifest-path=MANIFEST_PATH, -L MANIFEST_PATH] + [--no-clobber, -n] [--content-md5=MD5_DIGEST] [--continue-on-error, -c] + [--daisy-chain, -D] [--do-not-decompress] + [--manifest-path=MANIFEST_PATH, -L MANIFEST_PATH] [--preserve-posix, -P] [--print-created-message, -v] [--read-paths-from-stdin, -I] [--recursive, -R, -r] [--skip-unsupported, -U] @@ -21,8 +22,7 @@ SYNOPSIS [--cache-control=CACHE_CONTROL --content-disposition=CONTENT_DISPOSITION --content-encoding=CONTENT_ENCODING - --content-language=CONTENT_LANGUAGE --content-md5=MD5_DIGEST - --content-type=CONTENT_TYPE + --content-language=CONTENT_LANGUAGE --content-type=CONTENT_TYPE --custom-time=CUSTOM_TIME --clear-custom-metadata | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] | --remove-custom-metadata=[METADATA_KEYS,...] @@ -95,6 +95,11 @@ FLAGS items will be printed. This option may perform an additional GET request for cloud objects before attempting an upload. + --content-md5=MD5_DIGEST + Manually specified MD5 hash digest for the contents of an uploaded + file. This flag cannot be used when uploading multiple files. The + custom digest is used by the cloud provider for validation. + --continue-on-error, -c If any operations are unsuccessful, the command will exit with a non-zero exit status after completing the remaining operations. This @@ -291,11 +296,6 @@ OBJECT METADATA FLAGS --content-language=CONTENT_LANGUAGE Content's language (e.g. en signifies "English"). - --content-md5=MD5_DIGEST - Manually specified MD5 hash digest for the contents of an uploaded - file. This flag cannot be used when uploading multiple files. The - custom digest is used by the cloud provider for validation. - --content-type=CONTENT_TYPE Type of data contained in the object (e.g. text/html). diff --git a/gcloud/storage/help b/gcloud/storage/help index 9b2c693fc..3907b65f9 100644 --- a/gcloud/storage/help +++ b/gcloud/storage/help @@ -56,6 +56,9 @@ COMMANDS mv Moves or renames objects. + restore + Restore one or more soft-deleted objects. + rm Delete objects and buckets. diff --git a/gcloud/storage/ls b/gcloud/storage/ls index 7f2ada40a..01965bf11 100644 --- a/gcloud/storage/ls +++ b/gcloud/storage/ls @@ -3,9 +3,10 @@ NAME SYNOPSIS gcloud storage ls [PATH ...] [--additional-headers=HEADER=VALUE] - [--all-versions, -a] [--buckets, -b] [--etag, -e] + [--all-versions, -a] [--buckets, -b] [--etag, -e] [--exhaustive] [--fetch-encrypted-object-hashes] [--format=FORMAT] - [--read-paths-from-stdin, -I] [--readable-sizes] [--recursive, -R, -r] + [--next-page-token=NEXT_PAGE_TOKEN] [--read-paths-from-stdin, -I] + [--readable-sizes] [--recursive, -R, -r] [--soft-deleted] [--full, -L | --json, -j | --long, -l] [--decryption-keys=[DECRYPTION_KEY,...]] [GCLOUD_WIDE_FLAG ...] @@ -90,6 +91,11 @@ FLAGS --etag, -e Include ETag metadata in listings that use the --long flag. + --exhaustive + For features like soft delete, the API may return an empty list. If + present, continue querying. This may incur costs from repeated LIST + calls and may not return any additional objects. + --fetch-encrypted-object-hashes API requests to the LIST endpoint do not fetch the hashes for encrypted objects by default. If this flag is set, a GET request is sent for each @@ -101,6 +107,9 @@ FLAGS "--format=gsutil"). Other format values (e.g. "json") do not work. See different ls flags and commands for alternative formatting. + --next-page-token=NEXT_PAGE_TOKEN + Page token for resuming LIST calls. + --read-paths-from-stdin, -I Read the list of URLs from stdin. @@ -112,6 +121,10 @@ FLAGS Recursively list the contents of any directories that match the path expression. + --soft-deleted + Displays soft-deleted objects only. Excludes live and noncurrent + objects. + At most one of these can be specified: --full, -L diff --git a/gcloud/storage/mv b/gcloud/storage/mv index 1984a7b73..276546e5f 100644 --- a/gcloud/storage/mv +++ b/gcloud/storage/mv @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud storage mv [SOURCE ...] DESTINATION [--additional-headers=HEADER=VALUE] [--all-versions, -A] - [--no-clobber, -n] [--continue-on-error, -c] [--daisy-chain, -D] - [--do-not-decompress] [--manifest-path=MANIFEST_PATH, -L MANIFEST_PATH] + [--no-clobber, -n] [--content-md5=MD5_DIGEST] [--continue-on-error, -c] + [--daisy-chain, -D] [--do-not-decompress] + [--manifest-path=MANIFEST_PATH, -L MANIFEST_PATH] [--preserve-posix, -P] [--print-created-message, -v] [--read-paths-from-stdin, -I] [--skip-unsupported, -U] [--storage-class=STORAGE_CLASS, -s STORAGE_CLASS] @@ -20,8 +21,7 @@ SYNOPSIS [--cache-control=CACHE_CONTROL --content-disposition=CONTENT_DISPOSITION --content-encoding=CONTENT_ENCODING - --content-language=CONTENT_LANGUAGE --content-md5=MD5_DIGEST - --content-type=CONTENT_TYPE + --content-language=CONTENT_LANGUAGE --content-type=CONTENT_TYPE --custom-time=CUSTOM_TIME --clear-custom-metadata | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] | --remove-custom-metadata=[METADATA_KEYS,...] @@ -104,6 +104,11 @@ FLAGS items will be printed. This option may perform an additional GET request for cloud objects before attempting an upload. + --content-md5=MD5_DIGEST + Manually specified MD5 hash digest for the contents of an uploaded + file. This flag cannot be used when uploading multiple files. The + custom digest is used by the cloud provider for validation. + --continue-on-error, -c If any operations are unsuccessful, the command will exit with a non-zero exit status after completing the remaining operations. This @@ -296,11 +301,6 @@ OBJECT METADATA FLAGS --content-language=CONTENT_LANGUAGE Content's language (e.g. en signifies "English"). - --content-md5=MD5_DIGEST - Manually specified MD5 hash digest for the contents of an uploaded - file. This flag cannot be used when uploading multiple files. The - custom digest is used by the cloud provider for validation. - --content-type=CONTENT_TYPE Type of data contained in the object (e.g. text/html). diff --git a/gcloud/storage/objects/describe b/gcloud/storage/objects/describe index c773b4c09..f4dbbeca4 100644 --- a/gcloud/storage/objects/describe +++ b/gcloud/storage/objects/describe @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud storage objects describe URL [--additional-headers=HEADER=VALUE] - [--fetch-encrypted-object-hashes] [--raw] + [--fetch-encrypted-object-hashes] [--raw] [--soft-deleted] [--decryption-keys=[DECRYPTION_KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -41,6 +41,10 @@ FLAGS Shows metadata in the format returned by the API instead of standardizing it. + --soft-deleted + Displays soft-deleted objects only. Excludes live and noncurrent + objects. + ENCRYPTION FLAGS --decryption-keys=[DECRYPTION_KEY,...] A comma-separated list of customer-supplied encryption keys (RFC 4648 diff --git a/gcloud/storage/objects/list b/gcloud/storage/objects/list index 6602f6f90..534d03884 100644 --- a/gcloud/storage/objects/list +++ b/gcloud/storage/objects/list @@ -3,10 +3,12 @@ NAME SYNOPSIS gcloud storage objects list URLS [URLS ...] - [--additional-headers=HEADER=VALUE] [--fetch-encrypted-object-hashes] - [--raw] [--stat] [--decryption-keys=[DECRYPTION_KEY,...]] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--additional-headers=HEADER=VALUE] [--exhaustive] + [--fetch-encrypted-object-hashes] [--next-page-token=NEXT_PAGE_TOKEN] + [--raw] [--soft-deleted] [--stat] + [--decryption-keys=[DECRYPTION_KEY,...]] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION List Cloud Storage objects. @@ -39,16 +41,28 @@ FLAGS Overrides the default storage/additional_headers property value for this command invocation. + --exhaustive + For features like soft delete, the API may return an empty list. If + present, continue querying. This may incur costs from repeated LIST + calls and may not return any additional objects. + --fetch-encrypted-object-hashes API requests to the LIST endpoint do not fetch the hashes for encrypted objects by default. If this flag is set, a GET request is sent for each encrypted object in order to fetch hashes. This can significantly increase the cost of the command. + --next-page-token=NEXT_PAGE_TOKEN + Page token for resuming LIST calls. + --raw Shows metadata in the format returned by the API instead of standardizing it. + --soft-deleted + Displays soft-deleted objects only. Excludes live and noncurrent + objects. + --stat Emulates gsutil stat-style behavior. Does not show past object versions and changes output format. diff --git a/gcloud/storage/objects/update b/gcloud/storage/objects/update index 67a0e2d94..2a3f27853 100644 --- a/gcloud/storage/objects/update +++ b/gcloud/storage/objects/update @@ -15,11 +15,10 @@ SYNOPSIS --encryption-key=ENCRYPTION_KEY] [--cache-control=CACHE_CONTROL --clear-cache-control --clear-content-disposition --clear-content-encoding - --clear-content-language --clear-content-md5 --clear-content-type - --clear-custom-time --content-disposition=CONTENT_DISPOSITION + --clear-content-language --clear-content-type --clear-custom-time + --content-disposition=CONTENT_DISPOSITION --content-encoding=CONTENT_ENCODING - --content-language=CONTENT_LANGUAGE --content-md5=MD5_DIGEST - --content-type=CONTENT_TYPE + --content-language=CONTENT_LANGUAGE --content-type=CONTENT_TYPE --custom-time=CUSTOM_TIME --clear-custom-metadata | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] | --remove-custom-metadata=[METADATA_KEYS,...] @@ -160,9 +159,6 @@ OBJECT METADATA FLAGS --clear-content-language Clears object content language. - --clear-content-md5 - Clears object content MD5. - --clear-content-type Clears object content type. @@ -178,11 +174,6 @@ OBJECT METADATA FLAGS --content-language=CONTENT_LANGUAGE Content's language (e.g. en signifies "English"). - --content-md5=MD5_DIGEST - Manually specified MD5 hash digest for the contents of an uploaded - file. This flag cannot be used when uploading multiple files. The - custom digest is used by the cloud provider for validation. - --content-type=CONTENT_TYPE Type of data contained in the object (e.g. text/html). diff --git a/gcloud/storage/operations/list b/gcloud/storage/operations/list index 47abaabe1..11183e333 100644 --- a/gcloud/storage/operations/list +++ b/gcloud/storage/operations/list @@ -4,8 +4,7 @@ NAME SYNOPSIS gcloud storage operations list PARENT_RESOURCE_NAME [--server-filter=SERVER_FILTER] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION List storage operations. @@ -50,25 +49,12 @@ LIST COMMAND FLAGS 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, diff --git a/gcloud/storage/restore b/gcloud/storage/restore new file mode 100644 index 000000000..894963b1d --- /dev/null +++ b/gcloud/storage/restore @@ -0,0 +1,118 @@ +NAME + gcloud storage restore - restore one or more soft-deleted objects + +SYNOPSIS + gcloud storage restore [URLS ...] [--all-versions, -a] [--async] + [--[no-]preserve-acl, -p] [--read-paths-from-stdin, -I] + [--allow-overwrite --deleted-after-time=DELETED_AFTER_TIME + --deleted-before-time=DELETED_BEFORE_TIME] + [--if-generation-match=GENERATION + --if-metageneration-match=METAGENERATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The restore command restores soft-deleted objects: + + $ gcloud storage restore url... + +EXAMPLES + Restore specific version of object in a bucket. Note: Generation number is + required. + + $ gcloud storage restore gs://bucket/file1.txt#123 + + Restore two objects in a bucket: + + $ gcloud storage restore gs://bucket/file1.txt#123 \ + gs://bucket/file2.txt#456 + + Restore all text objects in a bucket: + + $ gcloud storage restore gs://bucket/**.txt + + Read list of files to restore from stdin: + + $ cat list-of-files.txt | gcloud storage restore \ + --read-paths-from-stdin + + Restore object with its original ACL policy: + + $ gcloud storage restore gs://bucket/file1.txt --preserve-acl + + Restore all objects in a bucket asynchronously: + + $ gcloud storage restore gs://bucket/** --async + + Restore all text files in a bucket asynchronously: + + $ gcloud storage restore gs://bucket/**.txt --async + +POSITIONAL ARGUMENTS + [URLS ...] + The url of objects to list. + +FLAGS + SYNCHRONOUS RESTORE OPTIONS + + --all-versions, -a + Restores all versions of soft-deleted objects. + + This flag is only useful for buckets with [object versioning] + (https://cloud.google.com/storage/docs/object-versioning) enabled. In + this case, the latest soft-deleted version will become live and the + previous generations will become noncurrent. + + If versioning is disabled, the latest soft-deleted version will + become live and previous generations will be soft-deleted again. + + This flag disables parallelism to preserve version order. + + --async + Initiates an asynchronous bulk restore operation on the specified + bucket. + + --[no-]preserve-acl, -p + Preserves ACLs when copying in the cloud. This option is Cloud + Storage-only, and you need OWNER access to all copied objects. If all + objects in the destination bucket should have the same ACL, you can + also set a default object ACL on that bucket instead of using this + flag. Preserving ACLs is the default behavior for updating existing + objects. Use --preserve-acl to enable and --no-preserve-acl to disable. + + --read-paths-from-stdin, -I + Read the list of URLs from stdin. + + BULK RESTORE OPTIONS + + --allow-overwrite + If included, live objects will be overwritten. If versioning is + enabled, this will result in a noncurrent object. If versioning is + not enabled, this will result in a soft-deleted object. + + --deleted-after-time=DELETED_AFTER_TIME + Restores only the objects that were soft-deleted after this time. + + --deleted-before-time=DELETED_BEFORE_TIME + Restores only the objects that were soft-deleted before this time. + +PRECONDITION FLAGS + --if-generation-match=GENERATION + Execute only if the generation matches the generation of the requested + object. + + --if-metageneration-match=METAGENERATION + Execute only if the metageneration matches the metageneration of the + requested object. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha storage restore + diff --git a/gcloud/storage/rsync b/gcloud/storage/rsync index 9eece2d3e..5f406ad36 100644 --- a/gcloud/storage/rsync +++ b/gcloud/storage/rsync @@ -5,9 +5,9 @@ SYNOPSIS gcloud storage rsync SOURCE DESTINATION [--additional-headers=HEADER=VALUE] [--canned-acl=PREDEFINED_ACL, --predefined-acl=PREDEFINED_ACL, -a PREDEFINED_ACL] - [--checksums-only] [--no-clobber, -n] [--continue-on-error, -c] - [--delete-unmatched-destination-objects] [--dry-run] - [--exclude=[REGEX,...], -x [REGEX,...]] + [--checksums-only] [--no-clobber, -n] [--content-md5=MD5_DIGEST] + [--continue-on-error, -c] [--delete-unmatched-destination-objects] + [--dry-run] [--exclude=[REGEX,...], -x [REGEX,...]] [--gzip-in-flight=[FILE_EXTENSIONS,...], -j [FILE_EXTENSIONS,...]] [--gzip-in-flight-all, -J] [--no-ignore-symlinks] [--preserve-posix, -P] [--recursive, -R, -r] @@ -17,8 +17,7 @@ SYNOPSIS [--cache-control=CACHE_CONTROL --content-disposition=CONTENT_DISPOSITION --content-encoding=CONTENT_ENCODING - --content-language=CONTENT_LANGUAGE --content-md5=MD5_DIGEST - --content-type=CONTENT_TYPE + --content-language=CONTENT_LANGUAGE --content-type=CONTENT_TYPE --custom-time=CUSTOM_TIME --clear-custom-metadata | --custom-metadata=[CUSTOM_METADATA_KEYS_AND_VALUES,...] | --remove-custom-metadata=[METADATA_KEYS,...] @@ -121,6 +120,11 @@ FLAGS items will be printed. This option may perform an additional GET request for cloud objects before attempting an upload. + --content-md5=MD5_DIGEST + Manually specified MD5 hash digest for the contents of an uploaded + file. This flag cannot be used when uploading multiple files. The + custom digest is used by the cloud provider for validation. + --continue-on-error, -c If any operations are unsuccessful, the command will exit with a non-zero exit status after completing the remaining operations. This @@ -231,11 +235,6 @@ OBJECT METADATA FLAGS --content-language=CONTENT_LANGUAGE Content's language (e.g. en signifies "English"). - --content-md5=MD5_DIGEST - Manually specified MD5 hash digest for the contents of an uploaded - file. This flag cannot be used when uploading multiple files. The - custom digest is used by the cloud provider for validation. - --content-type=CONTENT_TYPE Type of data contained in the object (e.g. text/html).