diff --git a/gcloud/_version b/gcloud/_version index a5217cd17..3bbcfc112 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 540.0.0 -alpha 2025.09.23 -beta 2025.09.23 -bq 2.1.23 +Google Cloud SDK 541.0.0 +alpha 2025.09.29 +beta 2025.09.29 +bq 2.1.24 bundled-python3-unix 3.12.9 -core 2025.09.23 +core 2025.09.29 gcloud-crc32c 1.0.0 gsutil 5.35 diff --git a/gcloud/ai/endpoints/deploy-model b/gcloud/ai/endpoints/deploy-model index 4a083ded9..1a6e4f3ab 100644 --- a/gcloud/ai/endpoints/deploy-model +++ b/gcloud/ai/endpoints/deploy-model @@ -11,6 +11,7 @@ SYNOPSIS [--enable-access-logging] [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] + [--required-replica-count=REQUIRED_REPLICA_COUNT] [--reservation-affinity=[key=KEY], [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], [values=VALUES]] [--service-account=SERVICE_ACCOUNT] [--spot] @@ -138,6 +139,11 @@ OPTIONAL FLAGS NOTE: DeploymentResourcePools (model-cohosting) is currently not supported for scale-to-zero deployments. + --required-replica-count=REQUIRED_REPLICA_COUNT + Required number of machine replicas for the deployment resources the + model will be considered successfully deployed. This value must be + greater than or equal to 1 and less than or equal to min-replica-count. + --reservation-affinity=[key=KEY],[reservation-affinity-type=RESERVATION-AFFINITY-TYPE],[values=VALUES] A ReservationAffinity can be used to configure a Vertex AI resource (e.g., a DeployedModel) to draw its Compute Engine resources from a diff --git a/gcloud/alpha/ai/endpoints/deploy-model b/gcloud/alpha/ai/endpoints/deploy-model index 2d83adff7..dbddf8662 100644 --- a/gcloud/alpha/ai/endpoints/deploy-model +++ b/gcloud/alpha/ai/endpoints/deploy-model @@ -12,6 +12,7 @@ SYNOPSIS [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] [--multihost-gpu-node-count=MULTIHOST_GPU_NODE_COUNT] + [--required-replica-count=REQUIRED_REPLICA_COUNT] [--reservation-affinity=[key=KEY], [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], [values=VALUES]] [--service-account=SERVICE_ACCOUNT] [--spot] @@ -146,6 +147,11 @@ OPTIONAL FLAGS The number of nodes per replica for multihost GPU deployments. Required for multihost GPU deployments. + --required-replica-count=REQUIRED_REPLICA_COUNT + Required number of machine replicas for the deployment resources the + model will be considered successfully deployed. This value must be + greater than or equal to 1 and less than or equal to min-replica-count. + --reservation-affinity=[key=KEY],[reservation-affinity-type=RESERVATION-AFFINITY-TYPE],[values=VALUES] A ReservationAffinity can be used to configure a Vertex AI resource (e.g., a DeployedModel) to draw its Compute Engine resources from a diff --git a/gcloud/alpha/backup-dr/backup-plan-associations/trigger-backup b/gcloud/alpha/backup-dr/backup-plan-associations/trigger-backup index dd2cd35c5..e7604de58 100644 --- a/gcloud/alpha/backup-dr/backup-plan-associations/trigger-backup +++ b/gcloud/alpha/backup-dr/backup-plan-associations/trigger-backup @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud alpha backup-dr backup-plan-associations trigger-backup (BACKUP_PLAN_ASSOCIATION - : --location=LOCATION --workload-project=WORKLOAD_PROJECT) - --backup-rule-id=BACKUP_RULE_ID [--async] [GCLOUD_WIDE_FLAG ...] + : --location=LOCATION --workload-project=WORKLOAD_PROJECT) [--async] + [--backup-rule-id=BACKUP_RULE_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create an on-demand backup for a resource. Trigger an on demand @@ -56,17 +56,16 @@ POSITIONAL ARGUMENTS ▸ provide the argument --project on the command line; ▸ set the property core/project. -REQUIRED FLAGS - --backup-rule-id=BACKUP_RULE_ID - Name of an existing backup rule to use for creating an on-demand - backup. - -OPTIONAL FLAGS +FLAGS --async Return immediately, without waiting for the operation in progress to complete. The default is True. Enabled by default, use --no-async to disable. + --backup-rule-id=BACKUP_RULE_ID + Name of an existing backup rule to use for creating an on-demand + backup. + 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/bigtable/logical-views/update b/gcloud/alpha/bigtable/logical-views/update index a2b8c4e93..b154a57bf 100644 --- a/gcloud/alpha/bigtable/logical-views/update +++ b/gcloud/alpha/bigtable/logical-views/update @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud alpha bigtable logical-views update - (LOGICAL_VIEW : --instance=INSTANCE) --query=QUERY [--async] - [--deletion-protection=DELETION_PROTECTION] [GCLOUD_WIDE_FLAG ...] + (LOGICAL_VIEW : --instance=INSTANCE) + (--deletion-protection=DELETION_PROTECTION --query=QUERY) [--async] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a Bigtable logical view. @@ -16,6 +17,11 @@ EXAMPLES --instance=my-instance-id \ --query="SELECT my-column-family2 FROM my-table" + To enable deletion protection on a logical view, run: + + $ gcloud alpha bigtable logical-views update my-logical-view-id \ + --instance=my-instance-id --deletion-protection + POSITIONAL ARGUMENTS Logical view resource - The logical view to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -49,17 +55,19 @@ POSITIONAL ARGUMENTS ▸ provide the argument --instance on the command line. REQUIRED FLAGS - --query=QUERY - The query of the view. + At least one of these must be specified: + + --deletion-protection=DELETION_PROTECTION + Whether the view is protected from deletion. + + --query=QUERY + The query of the view. OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to complete. - --deletion-protection=DELETION_PROTECTION - Whether the view is protected from deletion. - 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/cluster-director/clusters/update b/gcloud/alpha/cluster-director/clusters/update index 034ee7e09..eda96161d 100644 --- a/gcloud/alpha/cluster-director/clusters/update +++ b/gcloud/alpha/cluster-director/clusters/update @@ -62,8 +62,8 @@ EXAMPLES To update a cluster my-cluster in location us-central1-a with granular flags, run the following example: - Add labels, reserved instances, slurm node sets, slurm partitions and - update description and default partition: + Add labels, compute instances, slurm node sets, slurm partitions and update + description and default partition: $ gcloud alpha cluster-director clusters update my-cluster \ --location us-central1-a \ @@ -97,7 +97,7 @@ EXAMPLES --update-slurm-partitions \ id=partition1,nodesetIds=[nodeset0],exclusive=true - Remove slurm node sets, slurm partitions and reserved instances and update + Remove slurm node sets, slurm partitions and compute instances and update default partition: $ gcloud alpha cluster-director clusters update my-cluster \ diff --git a/gcloud/alpha/compute/backend-services/add-backend b/gcloud/alpha/compute/backend-services/add-backend index dfea4026a..cf4efe4f1 100644 --- a/gcloud/alpha/compute/backend-services/add-backend +++ b/gcloud/alpha/compute/backend-services/add-backend @@ -14,14 +14,15 @@ SYNOPSIS [--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER] [--description=DESCRIPTION] [--failover] [--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE] + [--traffic-duration=TRAFFIC_DURATION] [--custom-metrics=[CUSTOM_METRICS,...] | --custom-metrics-file=[CUSTOM_METRICS,...]] [--global | --region=REGION] [--max-connections=MAX_CONNECTIONS | --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT | --max-connections-per-instance=MAX_CONNECTIONS_PER_INSTANCE - | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT - | --max-rate-per-instance=MAX_RATE_PER_INSTANCE] + | --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS + | --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT | --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT | --max-rate-per-instance=MAX_RATE_PER_INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -188,6 +189,19 @@ OPTIONAL FLAGS CUSTOM_METRICS Spreads load based on custom defined and reported metrics. + IN_FLIGHT + Available if the backend service's load balancing scheme is + INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL_MANAGED. + Available if the backend service's protocol is one of HTTP, HTTPS, + or HTTP/2. + + Spreads load based on how many in-flight requests the backend can + handle. + + You must specify exactly one of these additional parameters: + --max-in-flight-requests, --max-in-flight-requests-per-instance, or + --max-in-flight-requests-per-endpoint, and --traffic-duration=LONG. + RATE Available if the backend service's load balancing scheme is INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL. Available if @@ -256,6 +270,20 @@ OPTIONAL FLAGS Backends with this preference setting are used up to their capacity limits first, while optimizing overall network latency. + --traffic-duration=TRAFFIC_DURATION + The expected traffic duration for this service. TRAFFIC_DURATION must + be one of: + + LONG + Most of the requests are expected to take more than multiple + seconds to finish. + + SHORT + Most requests are expected to finish with a sub-second latency. + + TRAFFIC_DURATION_UNSPECIFIED + Default value. Defaults to SHORT. + At most one of these can be specified: --custom-metrics=[CUSTOM_METRICS,...] @@ -372,6 +400,29 @@ OPTIONAL FLAGS number of instances in the instance group, and then dividing by the number of healthy instances. + --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS + Maximum number of in-flight requests that the backend can handle. + + This cannot be used when the endpoint type of an attached network + endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or + SERVERLESS. + + --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT + Only valid for network endpoint group backends. Defines the maximum + number of in-flight requests per endpoint. + + This cannot be used when the endpoint type of an attached network + endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or + SERVERLESS. + + --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE + Only valid for instance group backends. Defines the maximum number of + in-flight requests per instance. + + This cannot be used when the endpoint type of an attached network + endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or + SERVERLESS. + --max-rate=MAX_RATE Maximum number of HTTP requests per second (RPS) that the backend can handle. Valid for network endpoint group and instance group backends diff --git a/gcloud/alpha/compute/backend-services/update-backend b/gcloud/alpha/compute/backend-services/update-backend index 136d59b30..13b803e47 100644 --- a/gcloud/alpha/compute/backend-services/update-backend +++ b/gcloud/alpha/compute/backend-services/update-backend @@ -12,14 +12,15 @@ SYNOPSIS [--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER] [--description=DESCRIPTION] [--failover] [--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE] + [--traffic-duration=TRAFFIC_DURATION] [--clear-custom-metrics | --custom-metrics=[CUSTOM_METRICS,...] | --custom-metrics-file=[CUSTOM_METRICS,...]] [--global | --region=REGION] [--max-connections=MAX_CONNECTIONS | --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT | --max-connections-per-instance=MAX_CONNECTIONS_PER_INSTANCE - | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT - | --max-rate-per-instance=MAX_RATE_PER_INSTANCE] + | --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS + | --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT | --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE | --max-rate=MAX_RATE | --max-rate-per-endpoint=MAX_RATE_PER_ENDPOINT | --max-rate-per-instance=MAX_RATE_PER_INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -160,6 +161,19 @@ OPTIONAL FLAGS CUSTOM_METRICS Spreads load based on custom defined and reported metrics. + IN_FLIGHT + Available if the backend service's load balancing scheme is + INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL_MANAGED. + Available if the backend service's protocol is one of HTTP, HTTPS, + or HTTP/2. + + Spreads load based on how many in-flight requests the backend can + handle. + + You must specify exactly one of these additional parameters: + --max-in-flight-requests, --max-in-flight-requests-per-instance, or + --max-in-flight-requests-per-endpoint, and --traffic-duration=LONG. + RATE Available if the backend service's load balancing scheme is INTERNAL_MANAGED, INTERNAL_SELF_MANAGED, or EXTERNAL. Available if @@ -225,6 +239,20 @@ OPTIONAL FLAGS Backends with this preference setting are used up to their capacity limits first, while optimizing overall network latency. + --traffic-duration=TRAFFIC_DURATION + The expected traffic duration for this service. TRAFFIC_DURATION must + be one of: + + LONG + Most of the requests are expected to take more than multiple + seconds to finish. + + SHORT + Most requests are expected to finish with a sub-second latency. + + TRAFFIC_DURATION_UNSPECIFIED + Default value. Defaults to SHORT. + At most one of these can be specified: --clear-custom-metrics @@ -336,6 +364,17 @@ OPTIONAL FLAGS number of instances in the instance group, and then dividing by the number of healthy instances. + --max-in-flight-requests=MAX_IN_FLIGHT_REQUESTS + Maximum number of in-flight requests that the backend can handle. + + --max-in-flight-requests-per-endpoint=MAX_IN_FLIGHT_REQUESTS_PER_ENDPOINT + Only valid for network endpoint group backends. Defines the maximum + number of in-flight requests per endpoint. + + --max-in-flight-requests-per-instance=MAX_IN_FLIGHT_REQUESTS_PER_INSTANCE + Only valid for instance group backends. Defines the maximum number of + in-flight requests per instance. + --max-rate=MAX_RATE Maximum number of HTTP requests per second (RPS) that the backend can handle. Valid for network endpoint group and instance group backends diff --git a/gcloud/alpha/compute/disks/help b/gcloud/alpha/compute/disks/help index 998c5859f..724c4cfe5 100644 --- a/gcloud/alpha/compute/disks/help +++ b/gcloud/alpha/compute/disks/help @@ -97,6 +97,9 @@ COMMANDS update (ALPHA) Update a Compute Engine persistent disk. + update-kms-key + (ALPHA) Rotate the KMS key of a persistent disk to the primary version. + wait-for-replication-catchup (ALPHA) Provides the operation id for the asynchronous replication of a Compute Engine persistent disk-pair that can be used to wait for the diff --git a/gcloud/alpha/compute/disks/update-kms-key b/gcloud/alpha/compute/disks/update-kms-key new file mode 100644 index 000000000..c7a6b1839 --- /dev/null +++ b/gcloud/alpha/compute/disks/update-kms-key @@ -0,0 +1,82 @@ +NAME + gcloud alpha compute disks update-kms-key - rotate the KMS key of a + persistent disk to the primary version + +SYNOPSIS + gcloud alpha compute disks update-kms-key DISK_NAME + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) * gcloud alpha compute disks update-kms-key * updates the KMS key + of a Compute Engine persistent disk by rotating it to the primary version + of the key. + +EXAMPLES + To rotate the KMS key of a disk named example-disk-1 to the primary + version, run: + + $ gcloud alpha compute disks update-kms-key example-disk-1 \ + --zone us-central1-a + +POSITIONAL ARGUMENTS + DISK_NAME + Name of the disk to operate on. + +FLAGS + At most one of these can be specified: + + --region=REGION + Region of the disk to operate on. 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. + + --zone=ZONE + Zone of the disk to operate on. If not specified and the compute/zone + property isn't set, you might be prompted to select a zone + (interactive mode only). + + 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 + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index 471851eb2..2fe40e6f1 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -792,7 +792,7 @@ FLAGS enabled over this interface. vlan - VLAN tag of a dynamic network interface, must be an integer in the + VLAN ID of a Dynamic Network Interface, must be an integer in the range from 2 to 255 inclusively. igmp-query diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index e7afb6e8b..a50486efa 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -691,6 +691,10 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + vlan + VLAN ID of a Dynamic Network Interface, must be an integer in the + range from 2 to 255 inclusively. + --network-tier=NETWORK_TIER Specifies the network tier that will be used to configure the instance. NETWORK_TIER must be one of: PREMIUM, STANDARD. The default value is diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 9263a2006..61a6a8c3f 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -42,6 +42,7 @@ SYNOPSIS [--per-instance-hostnames=[INSTANCE_NAME=INSTANCE_HOSTNAME,...]] [--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT] [--post-key-revocation-action-type=POLICY] [--preemptible] + [--preemption-notice-duration=PREEMPTION_NOTICE_DURATION] [--provisioning-model=PROVISIONING_MODEL] [--resource-manager-tags=[KEY=VALUE,...]] [--resource-policies=[RESOURCE_POLICY,...]] [--no-restart-on-failure] @@ -757,6 +758,10 @@ OPTIONAL FLAGS will only be able to run for a limited amount of time. Preemptible instances can not be restarted and will not migrate. + --preemption-notice-duration=PREEMPTION_NOTICE_DURATION + Specifies the metadata preemption notice duration before the ACPI G2 + soft off signal is triggered for Spot VMs. e.g. 120s. + --provisioning-model=PROVISIONING_MODEL Specifies the provisioning model for your VM instances. This choice affects the price, availability, and how long your VM instances can diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 4084bff75..559e626f3 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -1465,8 +1465,8 @@ FLAGS enabled over this interface. vlan - VLAN tag of a dynamic network interface, must be an integer in - the range from 2 to 255 inclusively. + VLAN ID of a Dynamic Network Interface, must be an integer in the + range from 2 to 255 inclusively. igmp-query Determines if the Compute Engine Instance can receive and respond diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index 89e69fb16..347484725 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -795,6 +795,10 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + vlan + VLAN ID of a Dynamic Network Interface, must be an integer in the + range from 2 to 255 inclusively. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/alpha/compute/instances/network-interfaces/add b/gcloud/alpha/compute/instances/network-interfaces/add index 0a28e5404..275824314 100644 --- a/gcloud/alpha/compute/instances/network-interfaces/add +++ b/gcloud/alpha/compute/instances/network-interfaces/add @@ -1,6 +1,6 @@ NAME - gcloud alpha compute instances network-interfaces add - add a dynamic - network interface to a Compute Engine instance + gcloud alpha compute instances network-interfaces add - add a Dynamic + Network Interface to a Compute Engine instance SYNOPSIS gcloud alpha compute instances network-interfaces add INSTANCE_NAME @@ -19,11 +19,12 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha compute instances network-interfaces add adds a - dynamic network interface to a Compute Engine instance. For example: + Dynamic Network Interface to a Compute Engine instance. - $ gcloud alpha compute instances network-interfaces add \ - instance-name --parent-nic-name nic1 --vlan 2 - --network network-1 --subnetwork subnetwork-1 +EXAMPLES + To add a Dynamic Network Interface to a Compute Engine instance, run: $ gcloud alpha compute instances network-interfaces add \ + instance-name --parent-nic-name=nic1 --vlan=2 \ + --network=network-1 --subnetwork=subnetwork-1 POSITIONAL ARGUMENTS INSTANCE_NAME @@ -198,7 +199,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 instances network-interfaces add $ gcloud beta compute instances network-interfaces add diff --git a/gcloud/alpha/compute/instances/network-interfaces/delete b/gcloud/alpha/compute/instances/network-interfaces/delete index 165396c25..bc3e4507a 100644 --- a/gcloud/alpha/compute/instances/network-interfaces/delete +++ b/gcloud/alpha/compute/instances/network-interfaces/delete @@ -1,6 +1,6 @@ NAME - gcloud alpha compute instances network-interfaces delete - delete a dynamic - network interface from a Compute Engine instance + gcloud alpha compute instances network-interfaces delete - delete a Dynamic + Network Interface from a Compute Engine instance SYNOPSIS gcloud alpha compute instances network-interfaces delete INSTANCE_NAME @@ -9,10 +9,11 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha compute instances network-interfaces delete deletes a - dynamic network interface from a Compute Engine instance. For example: + Dynamic Network Interface from a Compute Engine instance. - $ gcloud alpha compute instances network-interfaces delete \ - instance-name --network-interface nic1.2 +EXAMPLES + To delete a Dynamic Network Interface from a Compute Engine instance, run: $ gcloud alpha compute instances network-interfaces delete \ + instance-name --network-interface=nic1.2 POSITIONAL ARGUMENTS INSTANCE_NAME @@ -61,7 +62,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 instances network-interfaces delete $ gcloud beta compute instances network-interfaces delete diff --git a/gcloud/alpha/compute/instances/network-interfaces/help b/gcloud/alpha/compute/instances/network-interfaces/help index 7316891a4..96ff780da 100644 --- a/gcloud/alpha/compute/instances/network-interfaces/help +++ b/gcloud/alpha/compute/instances/network-interfaces/help @@ -25,10 +25,10 @@ COMMANDS COMMAND is one of the following: add - (ALPHA) Add a dynamic network interface to a Compute Engine instance. + (ALPHA) Add a Dynamic Network Interface to a Compute Engine instance. delete - (ALPHA) Delete a dynamic network interface from a Compute Engine + (ALPHA) Delete a Dynamic Network Interface from a Compute Engine instance. get-effective-firewalls diff --git a/gcloud/alpha/compute/networks/subnets/describe b/gcloud/alpha/compute/networks/subnets/describe index b0091378b..0a85cc775 100644 --- a/gcloud/alpha/compute/networks/subnets/describe +++ b/gcloud/alpha/compute/networks/subnets/describe @@ -41,12 +41,13 @@ FLAGS CLOUDSDK_COMPUTE_REGION. --view=VIEW - Specifies the information that the output should contain. VIEW must be - (only one value is supported): + Specifies the information to include in the output. VIEW must be (only + one value is supported): WITH_UTILIZATION - Output includes the IP utilization data of all subnetwork ranges, - showing total allocated and free IPv4 and IPv6 IPs. + Output includes the IP address utilization data of all subnetwork + ranges, showing total allocated and free IPv4 and IPv6 IP + addresses. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/networks/subnets/list b/gcloud/alpha/compute/networks/subnets/list index d1fef64f2..f84415f91 100644 --- a/gcloud/alpha/compute/networks/subnets/list +++ b/gcloud/alpha/compute/networks/subnets/list @@ -53,12 +53,13 @@ FLAGS If provided, only resources from the given regions are queried. --view=VIEW - Specifies the information that the output should contain. VIEW must be - (only one value is supported): + Specifies the information to include in the output. VIEW must be (only + one value is supported): WITH_UTILIZATION - Output includes the IP utilization data of all subnetwork ranges, - showing total allocated and free IPv4 and IPv6 IPs. + Output includes the IP address utilization data of all subnetwork + ranges, showing total allocated and free IPv4 and IPv6 IP + addresses. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index ad2184259..c9d343a3e 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -42,6 +42,7 @@ SYNOPSIS [--per-instance-hostnames=[INSTANCE_NAME=INSTANCE_HOSTNAME,...]] [--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT] [--post-key-revocation-action-type=POLICY] [--preemptible] + [--preemption-notice-duration=PREEMPTION_NOTICE_DURATION] [--provisioning-model=PROVISIONING_MODEL] [--resource-manager-tags=[KEY=VALUE,...]] [--resource-policies=[RESOURCE_POLICY,...]] [--no-restart-on-failure] @@ -730,6 +731,10 @@ OPTIONAL FLAGS will only be able to run for a limited amount of time. Preemptible instances can not be restarted and will not migrate. + --preemption-notice-duration=PREEMPTION_NOTICE_DURATION + Specifies the metadata preemption notice duration before the ACPI G2 + soft off signal is triggered for Spot VMs. e.g. 120s. + --provisioning-model=PROVISIONING_MODEL Specifies the provisioning model for your VM instances. This choice affects the price, availability, and how long your VM instances can diff --git a/gcloud/alpha/compute/reservations/update b/gcloud/alpha/compute/reservations/update index f1a38d76f..a214f5556 100644 --- a/gcloud/alpha/compute/reservations/update +++ b/gcloud/alpha/compute/reservations/update @@ -79,14 +79,14 @@ FLAGS omit this flag during creation, the default value is DISALLOW_ALL. --scheduling-type=SCHEDULING_TYPE - Maintenance for the reserved capacity. SCHEDULING_TYPE must be one of: + How Compute Engine schedules maintenance events for your reserved + hosts. SCHEDULING_TYPE must be one of: GROUPED - In GROUPED mode, maintenance on all reserved instances is - synchronized. + In GROUPED mode, maintenance is synchronized across all your VMs. INDEPENDENT - In INDEPENDENT mode, maintenance is not synchronized for this - reservation, and each instance has its own maintenance window. + In INDEPENDENT mode, your VMs have different, unsynchronized + maintenance schedules. --share-setting=SHARE_SETTING The projects that can use the reservation. SHARE_SETTING must be one diff --git a/gcloud/alpha/compute/snapshots/help b/gcloud/alpha/compute/snapshots/help index 46017685b..1dea23398 100644 --- a/gcloud/alpha/compute/snapshots/help +++ b/gcloud/alpha/compute/snapshots/help @@ -55,6 +55,9 @@ COMMANDS update (ALPHA) Update a Compute Engine snapshot. + update-kms-key + (ALPHA) Update the KMS key of a Compute Engine snapshot. + 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/compute/snapshots/update-kms-key b/gcloud/alpha/compute/snapshots/update-kms-key new file mode 100644 index 000000000..0bfc3b3eb --- /dev/null +++ b/gcloud/alpha/compute/snapshots/update-kms-key @@ -0,0 +1,39 @@ +NAME + gcloud alpha compute snapshots update-kms-key - update the KMS key of a + Compute Engine snapshot + +SYNOPSIS + gcloud alpha compute snapshots update-kms-key SNAPSHOT_NAME + [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) * gcloud alpha compute snapshots update-kms-key updates the KMS key + of a Compute Engine persistent snapshot. + +EXAMPLES + To update the KMS key of a snapshot named example-snapshot-1, run: + + $ gcloud alpha compute snapshots update-kms-key example-snapshot-1 + +POSITIONAL ARGUMENTS + SNAPSHOT_NAME + Name of the snapshot to update the KMS key for. + +FLAGS + --region=REGION + The region of the snapshot to update. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/tpus/execution-groups/create b/gcloud/alpha/compute/tpus/execution-groups/create index f34bb0030..3cc921c72 100644 --- a/gcloud/alpha/compute/tpus/execution-groups/create +++ b/gcloud/alpha/compute/tpus/execution-groups/create @@ -13,6 +13,14 @@ SYNOPSIS [--use-dl-images] [--use-with-notebook] [--vm-only] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (ALPHA) (DEPRECATED) Create Google Compute TPUs along with VMs. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To create both TPU and VM, run: diff --git a/gcloud/alpha/compute/tpus/execution-groups/delete b/gcloud/alpha/compute/tpus/execution-groups/delete index 878ba00c5..864e238f3 100644 --- a/gcloud/alpha/compute/tpus/execution-groups/delete +++ b/gcloud/alpha/compute/tpus/execution-groups/delete @@ -6,6 +6,14 @@ SYNOPSIS gcloud alpha compute tpus execution-groups delete EXECUTION_GROUP_NAME [--tpu-only] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (ALPHA) (DEPRECATED) Delete TPU Node + VM created by execution group. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To delete both, the TPU and the VM, run: diff --git a/gcloud/alpha/compute/tpus/execution-groups/describe b/gcloud/alpha/compute/tpus/execution-groups/describe index 08067102b..16107334f 100644 --- a/gcloud/alpha/compute/tpus/execution-groups/describe +++ b/gcloud/alpha/compute/tpus/execution-groups/describe @@ -6,6 +6,14 @@ SYNOPSIS gcloud alpha compute tpus execution-groups describe EXECUTION_GROUP_NAME [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (ALPHA) (DEPRECATED) Describe Google Compute TPU + VM combination. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To describe the TPU and VM combination, run: diff --git a/gcloud/alpha/compute/tpus/execution-groups/help b/gcloud/alpha/compute/tpus/execution-groups/help index 436aac81b..45cf25d1f 100644 --- a/gcloud/alpha/compute/tpus/execution-groups/help +++ b/gcloud/alpha/compute/tpus/execution-groups/help @@ -6,8 +6,13 @@ SYNOPSIS gcloud alpha compute tpus execution-groups COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Command group that helps create and manage Cloud TPUs and Compute - VMs. + (ALPHA) (DEPRECATED) Command group that helps create and manage Cloud TPUs + and Compute VMs. + + This command group is deprecated and will be removed in a future release. + We recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -18,22 +23,23 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create Google Compute TPUs along with VMs. + (ALPHA) (DEPRECATED) Create Google Compute TPUs along with VMs. delete - (ALPHA) Delete TPU Node + VM created by execution group. + (ALPHA) (DEPRECATED) Delete TPU Node + VM created by execution group. describe - (ALPHA) Describe Google Compute TPU + VM combination. + (ALPHA) (DEPRECATED) Describe Google Compute TPU + VM combination. list - (ALPHA) List TPU Node+VM groups created by execution group. + (ALPHA) (DEPRECATED) List TPU Node+VM groups created by execution + group. resume - (ALPHA) Creates Google Compute TPU and resumes the VM. + (ALPHA) (DEPRECATED) Creates Google Compute TPU and resumes the VM. suspend - (ALPHA) Deletes Google Compute TPU and suspends the VM. + (ALPHA) (DEPRECATED) Deletes Google Compute TPU and suspends the VM. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/compute/tpus/execution-groups/list b/gcloud/alpha/compute/tpus/execution-groups/list index 3bcc5e910..cbe9e9044 100644 --- a/gcloud/alpha/compute/tpus/execution-groups/list +++ b/gcloud/alpha/compute/tpus/execution-groups/list @@ -7,6 +7,14 @@ SYNOPSIS [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (ALPHA) (DEPRECATED) List TPU Node+VM groups created by execution group. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To list all active execution groups, run: diff --git a/gcloud/alpha/compute/tpus/execution-groups/resume b/gcloud/alpha/compute/tpus/execution-groups/resume index 2951a555d..34c31acb5 100644 --- a/gcloud/alpha/compute/tpus/execution-groups/resume +++ b/gcloud/alpha/compute/tpus/execution-groups/resume @@ -9,6 +9,14 @@ SYNOPSIS [--tf-version=TF_VERSION] [--vm-only] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (ALPHA) (DEPRECATED) Creates Google Compute TPU and resumes the VM. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To resume a suspended TPU VM combination, run: diff --git a/gcloud/alpha/compute/tpus/execution-groups/suspend b/gcloud/alpha/compute/tpus/execution-groups/suspend index 990c9f510..f28d4bb80 100644 --- a/gcloud/alpha/compute/tpus/execution-groups/suspend +++ b/gcloud/alpha/compute/tpus/execution-groups/suspend @@ -6,6 +6,14 @@ SYNOPSIS gcloud alpha compute tpus execution-groups suspend EXECUTION_GROUP_NAME [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (ALPHA) (DEPRECATED) Deletes Google Compute TPU and suspends the VM. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To delete the TPU and suspend the VM, run: diff --git a/gcloud/alpha/compute/tpus/help b/gcloud/alpha/compute/tpus/help index 71cb6f211..8277db021 100644 --- a/gcloud/alpha/compute/tpus/help +++ b/gcloud/alpha/compute/tpus/help @@ -25,8 +25,8 @@ GROUPS (ALPHA) List or Describe Available Cloud TPU accelerator types. execution-groups - (ALPHA) Command group that helps create and manage Cloud TPUs and - Compute VMs. + (ALPHA) (DEPRECATED) Command group that helps create and manage Cloud + TPUs and Compute VMs. locations (ALPHA) List or Describe Available Cloud TPU Locations. diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/create b/gcloud/alpha/compute/zone-vm-extension-policies/create index 11e53b510..79a3bd487 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/create +++ b/gcloud/alpha/compute/zone-vm-extension-policies/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha compute zone-vm-extension-policies create NAME --extensions=EXTENSION_NAME,[...] [--config=KEY=VALUE,[KEY=VALUE,...]] - [--description=DESCRIPTION] [--inclusion-labels=INCLUSION_LABELS] + [--config-from-file=KEY=FILE_PATH,[...]] [--description=DESCRIPTION] + [--inclusion-labels=INCLUSION_LABELS] [--priority=PRIORITY; default=1000] [--version=KEY=VALUE,[KEY=VALUE,...]] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] @@ -42,6 +43,14 @@ OPTIONAL FLAGS E.g. --config=filestore=,ops-agent= + --config-from-file=KEY=FILE_PATH,[...] + Same as --config except that the value for the entry will be read from + a local file. The extension name must be one of the extensions + specified in the --extensions flag. + + It is an error to specify the same extension in both --config and + --config-from-file. + --description=DESCRIPTION An optional textual description for the this extension policy. diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/update b/gcloud/alpha/compute/zone-vm-extension-policies/update index 200bc5387..7eb2d71de 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/update +++ b/gcloud/alpha/compute/zone-vm-extension-policies/update @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha compute zone-vm-extension-policies update NAME --extensions=EXTENSION_NAME,[...] [--config=KEY=VALUE,[KEY=VALUE,...]] - [--description=DESCRIPTION] [--inclusion-labels=INCLUSION_LABELS] + [--config-from-file=KEY=FILE_PATH,[...]] [--description=DESCRIPTION] + [--inclusion-labels=INCLUSION_LABELS] [--priority=PRIORITY; default=1000] [--version=KEY=VALUE,[KEY=VALUE,...]] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] @@ -42,6 +43,14 @@ OPTIONAL FLAGS E.g. --config=filestore=,ops-agent= + --config-from-file=KEY=FILE_PATH,[...] + Same as --config except that the value for the entry will be read from + a local file. The extension name must be one of the extensions + specified in the --extensions flag. + + It is an error to specify the same extension in both --config and + --config-from-file. + --description=DESCRIPTION An optional textual description for the this extension policy. diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 63c765a19..5b3be496d 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -112,13 +112,11 @@ SYNOPSIS | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] [--disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics] - [[--enable-autoprovisioning - : --autoprovisioning-config-file=PATH_TO_FILE - | [--max-cpu=MAX_CPU --max-memory=MAX_MEMORY - : --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE + [--enable-autoprovisioning --autoprovisioning-config-file=PATH_TO_FILE + | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE --autoprovisioning-locations=ZONE,[ZONE,...] - --autoprovisioning-min-cpu-platform=PLATFORM --min-cpu=MIN_CPU - --min-memory=MIN_MEMORY + --autoprovisioning-min-cpu-platform=PLATFORM --max-cpu=MAX_CPU + --max-memory=MAX_MEMORY --min-cpu=MIN_CPU --min-memory=MIN_MEMORY --autoprovisioning-max-surge-upgrade=AUTOPROVISIONING_MAX_SURGE_UPGRADE --autoprovisioning-max-unavailable-upgrade=AUTOPROVISIONING_MAX_UNAVAILABLE_UPGRADE --autoprovisioning-node-pool-soak-duration=AUTOPROVISIONING_NODE_POOL_SOAK_DURATION --autoprovisioning-standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, batch-soak-duration=BATCH_SOAK_DURATION,...] @@ -129,7 +127,7 @@ SYNOPSIS --enable-autoprovisioning-autorepair --enable-autoprovisioning-autoupgrade [--max-accelerator=[type=TYPE,count=COUNT,...] - : --min-accelerator=[type=TYPE,count=COUNT,...]]]]] + : --min-accelerator=[type=TYPE,count=COUNT,...]]] [--enable-autoscaling --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES --min-nodes=MIN_NODES --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] @@ -1439,7 +1437,9 @@ FLAGS cpuManagerPolicy either 'static' or 'none' cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') + cpuCFSQuotaPeriod interval (e.g., '100ms'. The + value must be between 1ms and 1 + second, inclusive.) memoryManager specify memory manager policy topologyManager specify topology manager policy and scope @@ -1449,7 +1449,7 @@ FLAGS containerLogMaxSize positive number plus unit suffix (e.g., '100Mi', '0.2Gi'. The value must be between 10Mi and - 500Mi.) + 500Mi, inclusive.) containerLogMaxFiles integer (The value must be between [2, 10].) imageGcLowThresholdPercent integer (The value must be @@ -2075,9 +2075,6 @@ FLAGS Cluster Autoscaler will be able to create new node pools. Requires maximum CPU and memory limits to be specified. - This flag argument must be specified if any of the other arguments in - this group are specified. - At most one of these can be specified: --autoprovisioning-config-file=PATH_TO_FILE @@ -2155,23 +2152,6 @@ FLAGS Flags to configure autoprovisioned nodes - --max-cpu=MAX_CPU - Maximum number of cores in the cluster. - - Maximum number of cores to which the cluster can scale. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --max-memory=MAX_MEMORY - Maximum memory in the cluster. - - Maximum number of gigabytes of memory to which the cluster can - scale. - - This flag argument must be specified if any of the other - arguments in this group are specified. - --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE Node Autoprovisioning will create new nodes with the specified image type @@ -2190,6 +2170,17 @@ FLAGS will be removed in an upcoming release. More info: https://cloud.google.com/kubernetes-engine/docs/release-notes#March_08_2022 + --max-cpu=MAX_CPU + Maximum number of cores in the cluster. + + Maximum number of cores to which the cluster can scale. + + --max-memory=MAX_MEMORY + Maximum memory in the cluster. + + Maximum number of gigabytes of memory to which the cluster can + scale. + --min-cpu=MIN_CPU Minimum number of cores in the cluster. diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index f609cf543..651eb6588 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -96,8 +96,8 @@ SYNOPSIS --enable-master-global-access --enable-private-endpoint --enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...] - | [--enable-autoprovisioning - : --autoprovisioning-config-file=PATH_TO_FILE + | --enable-autoprovisioning + --autoprovisioning-config-file=PATH_TO_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE --autoprovisioning-locations=ZONE,[ZONE,...] --autoprovisioning-min-cpu-platform=PLATFORM --max-cpu=MAX_CPU @@ -112,7 +112,7 @@ SYNOPSIS --enable-autoprovisioning-autorepair --enable-autoprovisioning-autoupgrade [--max-accelerator=[type=TYPE,count=COUNT,...] - : --min-accelerator=[type=TYPE,count=COUNT,...]]] + : --min-accelerator=[type=TYPE,count=COUNT,...]] | --enable-insecure-binding-system-authenticated --enable-insecure-binding-system-unauthenticated | --logging-service=LOGGING_SERVICE @@ -1365,9 +1365,6 @@ REQUIRED FLAGS Cluster Autoscaler will be able to create new node pools. Requires maximum CPU and memory limits to be specified. - This flag argument must be specified if any of the other arguments - in this group are specified. - At most one of these can be specified: --autoprovisioning-config-file=PATH_TO_FILE diff --git a/gcloud/alpha/container/fleet/config-management/describe b/gcloud/alpha/container/fleet/config-management/describe index bbbde309a..10a2a6816 100644 --- a/gcloud/alpha/container/fleet/config-management/describe +++ b/gcloud/alpha/container/fleet/config-management/describe @@ -5,8 +5,12 @@ NAME SYNOPSIS gcloud alpha container fleet config-management describe [--memberships=[MEMBERSHIPS,...] : --location=LOCATION] + [--view=VIEW : --filter=EXPRESSION --sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (ALPHA) Describe the Config Management feature. + EXAMPLES To describe the entire Config Management feature, run: @@ -17,6 +21,15 @@ EXAMPLES $ gcloud alpha container fleet config-management describe \ --memberships=example-membership-1,example-membership-2 + To list the membership configurations, run: + + $ gcloud alpha container fleet config-management describe --view=list + + MEMBERSHIP LOCATION STATUS INSTALL_STATE STOP_STATE SYNC_STATE VERSION SYNCED_TO_FLEET_DEFAULT + example-membership-1 asia-east1 OK CONFIG_SYNC_NOT_INSTALLED NOT_INSTALLED FLEET_DEFAULT_NOT_CONFIGURED + example-membership-2 us-central1 OK CONFIG_SYNC_INSTALLED NOT_STOPPED SYNCED 1.22.0 FLEET_DEFAULT_NOT_CONFIGURED + example-membership-3 us-central1 ERROR CONFIG_SYNC_INSTALLED NOT_STOPPED ERROR 1.21.3 FLEET_DEFAULT_NOT_CONFIGURED + FLAGS Memberships to print configurations for. Errors if a specified membership does not have a configuration for this feature. @@ -51,6 +64,86 @@ FLAGS ▫ provide the argument --location on the command line; ▫ set the property gkehub/location. + --view=VIEW + View of the feature. VIEW must be one of: + + full + Default view. Prints the entire feature. + list + List of membership configurations. Default format is a table + summary. + + The SYNCED_TO_FLEET_DEFAULT column may display UNKNOWN for any + membership whose configuration has not been updated since the + fleet-default membership configuration + (https://cloud.google.com/kubernetes-engine/fleet-management/docs/manage-features) + enablement. + + To view the underlying configurations instead of the table summary + for select memberships, run: + + $ gcloud alpha container fleet config-management describe \ + --view=list --format=yaml \ + --memberships=example-membership-1,example-membership-2 + + List command flags. Only specify when --view=list. Does not include + support for --limit. + + --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. + + To filter for memberships with an overall status of ERROR, use the + COLUMN~VALUE pattern and run: + + $ gcloud alpha container fleet config-management describe \ + --view=list --filter=STATUS~ERROR + + To filter for memberships that are synced to the fleet-default + membership configuration, run: + + $ gcloud alpha container fleet config-management describe \ + --view=list \ + --filter="spec.origin.type.synced_to_fleet_default()~YES" + + SYNCED_TO_FLEET_DEFAULT is the only column that requires filtering on + the underlying configuration field instead of the column name. An + alternative is to --sort-by=SYNCED_TO_FLEET_DEFAULT and filter by + eye. + + To filter on a configuration field not in the table summary, in this + case the Config Sync repo, run: + + $ gcloud alpha container fleet config-management describe \ + --view=list --format=yaml \ + --filter="spec.configmanagement.configSync.git.syncRepo~https://\ + github.com/GoogleCloudPlatform/anthos-config-management-samples.git" + + --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. + + The default table summary sorts by LOCATION then MEMBERSHIP. + + To sort the table by VERSION instead, run: + + $ gcloud alpha container fleet config-management describe \ + --view=list --sort-by=VERSION + + To sort by a configuration field not in the table summary, in this + case the Config Sync repo, and print its values in a table, run: + + $ gcloud alpha container fleet config-management describe \ + --view=list \ + --sort-by="spec.configmanagement.configSync.git.syncRepo" \ + --format="table(MEMBERSHIP,LOCATION,spec.configmanagement.config\ + Sync.git.syncRepo:label=REPO)" + 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/container/hub/config-management/describe b/gcloud/alpha/container/hub/config-management/describe index c7c426c1d..cb2e4b297 100644 --- a/gcloud/alpha/container/hub/config-management/describe +++ b/gcloud/alpha/container/hub/config-management/describe @@ -5,8 +5,12 @@ NAME SYNOPSIS gcloud alpha container hub config-management describe [--memberships=[MEMBERSHIPS,...] : --location=LOCATION] + [--view=VIEW : --filter=EXPRESSION --sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (ALPHA) Describe the Config Management feature. + EXAMPLES To describe the entire Config Management feature, run: @@ -17,6 +21,15 @@ EXAMPLES $ gcloud alpha container hub config-management describe \ --memberships=example-membership-1,example-membership-2 + To list the membership configurations, run: + + $ gcloud alpha container hub config-management describe --view=list + + MEMBERSHIP LOCATION STATUS INSTALL_STATE STOP_STATE SYNC_STATE VERSION SYNCED_TO_FLEET_DEFAULT + example-membership-1 asia-east1 OK CONFIG_SYNC_NOT_INSTALLED NOT_INSTALLED FLEET_DEFAULT_NOT_CONFIGURED + example-membership-2 us-central1 OK CONFIG_SYNC_INSTALLED NOT_STOPPED SYNCED 1.22.0 FLEET_DEFAULT_NOT_CONFIGURED + example-membership-3 us-central1 ERROR CONFIG_SYNC_INSTALLED NOT_STOPPED ERROR 1.21.3 FLEET_DEFAULT_NOT_CONFIGURED + FLAGS Memberships to print configurations for. Errors if a specified membership does not have a configuration for this feature. @@ -51,6 +64,86 @@ FLAGS ▫ provide the argument --location on the command line; ▫ set the property gkehub/location. + --view=VIEW + View of the feature. VIEW must be one of: + + full + Default view. Prints the entire feature. + list + List of membership configurations. Default format is a table + summary. + + The SYNCED_TO_FLEET_DEFAULT column may display UNKNOWN for any + membership whose configuration has not been updated since the + fleet-default membership configuration + (https://cloud.google.com/kubernetes-engine/fleet-management/docs/manage-features) + enablement. + + To view the underlying configurations instead of the table summary + for select memberships, run: + + $ gcloud alpha container hub config-management describe \ + --view=list --format=yaml \ + --memberships=example-membership-1,example-membership-2 + + List command flags. Only specify when --view=list. Does not include + support for --limit. + + --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. + + To filter for memberships with an overall status of ERROR, use the + COLUMN~VALUE pattern and run: + + $ gcloud alpha container hub config-management describe \ + --view=list --filter=STATUS~ERROR + + To filter for memberships that are synced to the fleet-default + membership configuration, run: + + $ gcloud alpha container hub config-management describe \ + --view=list \ + --filter="spec.origin.type.synced_to_fleet_default()~YES" + + SYNCED_TO_FLEET_DEFAULT is the only column that requires filtering on + the underlying configuration field instead of the column name. An + alternative is to --sort-by=SYNCED_TO_FLEET_DEFAULT and filter by + eye. + + To filter on a configuration field not in the table summary, in this + case the Config Sync repo, run: + + $ gcloud alpha container hub config-management describe \ + --view=list --format=yaml \ + --filter="spec.configmanagement.configSync.git.syncRepo~https://\ + github.com/GoogleCloudPlatform/anthos-config-management-samples.git" + + --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. + + The default table summary sorts by LOCATION then MEMBERSHIP. + + To sort the table by VERSION instead, run: + + $ gcloud alpha container hub config-management describe \ + --view=list --sort-by=VERSION + + To sort by a configuration field not in the table summary, in this + case the Config Sync repo, and print its values in a table, run: + + $ gcloud alpha container hub config-management describe \ + --view=list \ + --sort-by="spec.configmanagement.configSync.git.syncRepo" \ + --format="table(MEMBERSHIP,LOCATION,spec.configmanagement.config\ + Sync.git.syncRepo:label=REPO)" + 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/container/node-pools/create b/gcloud/alpha/container/node-pools/create index cc8b6e78b..079970249 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -817,7 +817,9 @@ FLAGS cpuManagerPolicy either 'static' or 'none' cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') + cpuCFSQuotaPeriod interval (e.g., '100ms'. The + value must be between 1ms and 1 + second, inclusive.) memoryManager specify memory manager policy topologyManager specify topology manager policy and scope @@ -827,7 +829,7 @@ FLAGS containerLogMaxSize positive number plus unit suffix (e.g., '100Mi', '0.2Gi'. The value must be between 10Mi and - 500Mi.) + 500Mi, inclusive.) containerLogMaxFiles integer (The value must be between [2, 10].) imageGcLowThresholdPercent integer (The value must be diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index 98d420355..a54e4a8dc 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -318,7 +318,9 @@ REQUIRED FLAGS cpuManagerPolicy either 'static' or 'none' cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') + cpuCFSQuotaPeriod interval (e.g., '100ms'. The + value must be between 1ms and + 1 second, inclusive.) memoryManager specify memory manager policy topologyManager specify topology manager policy and scope @@ -328,7 +330,8 @@ REQUIRED FLAGS containerLogMaxSize positive number plus unit suffix (e.g., '100Mi', '0.2Gi'. The value must be - between 10Mi and 500Mi.) + between 10Mi and 500Mi, + inclusive.) containerLogMaxFiles integer (The value must be between [2, 10].) imageGcLowThresholdPercent integer (The value must be diff --git a/gcloud/alpha/design-center/locations/describe b/gcloud/alpha/design-center/locations/describe index 493f93732..fc5b25156 100644 --- a/gcloud/alpha/design-center/locations/describe +++ b/gcloud/alpha/design-center/locations/describe @@ -14,12 +14,12 @@ EXAMPLES project my-project, run: $ gcloud alpha design-center locations describe my-location \ - --project=my-project + --project=my-project - Or run: + Or run: $ gcloud alpha design-center locations describe \ - projects/my-project/locations/my-location + projects/my-project/locations/my-location POSITIONAL ARGUMENTS Location resource - Location. This represents a Cloud resource. (NOTE) diff --git a/gcloud/alpha/design-center/spaces/application-templates/components/create b/gcloud/alpha/design-center/spaces/application-templates/components/create index 8e71af03f..3fc150c88 100644 --- a/gcloud/alpha/design-center/spaces/application-templates/components/create +++ b/gcloud/alpha/design-center/spaces/application-templates/components/create @@ -18,17 +18,19 @@ EXAMPLES my-app-template, space my-space, project my-project and location us-central1 using a shared template revision, run: - $ gcloud alpha design-center spaces application-templates \ components create my-component \ - --application-template=my-app-template --space=my-space \ - --project=my-project --location=us-central1 \ - --shared-template-revision-uri=projects/my-project/locations/\ + $ gcloud alpha design-center spaces application-templates \ + components create my-component \ + --application-template=my-app-template --space=my-space \ + --project=my-project --location=us-central1 \ + --shared-template-revision-uri=projects/my-project/locations/\ us-central1/spaces/my-space/sharedTemplates/my-shared-template/\ revisions/rev1 Or run: - $ gcloud alpha design-center spaces application-templates \ components create \ - projects/my-project/locations/us-central1/spaces/my-space/\ + $ gcloud alpha design-center spaces application-templates \ + components create \ + projects/my-project/locations/us-central1/spaces/my-space/\ applicationTemplates/my-app-template/components/my-component \ --shared-template-revision-uri=projects/my-project/locations/\ us-central1/spaces/my-space/sharedTemplates/my-shared-template/\ @@ -39,10 +41,11 @@ EXAMPLES us-central1 using a google shared template google-shared-template and revision rev1, run: - $ gcloud alpha design-center spaces application-templates \ components create my-component \ - --application-template=my-app-template --space=my-space \ - --project=my-project --location=us-central1 \ - --shared-template-revision-uri=google/google-shared-template/\ + $ gcloud alpha design-center spaces application-templates \ + components create my-component \ + --application-template=my-app-template --space=my-space \ + --project=my-project --location=us-central1 \ + --shared-template-revision-uri=google/google-shared-template/\ revisions/rev1 To create the component my-component in application template @@ -50,39 +53,43 @@ EXAMPLES us-central1 using a google shared template google-shared-template with its latest revision, run: - $ gcloud alpha design-center spaces application-templates \ components create my-component \ - --application-template=my-app-template --space=my-space \ - --project=my-project --location=us-central1 \ - --shared-template-revision-uri=google/google-shared-template + $ gcloud alpha design-center spaces application-templates \ + components create my-component \ + --application-template=my-app-template --space=my-space \ + --project=my-project --location=us-central1 \ + --shared-template-revision-uri=google/google-shared-template To create the component my-component in application template my-app-template, space my-space, project my-project and location us-central1 using a shared template my-shared-template and revision rev1 present in the same space, run: - $ gcloud alpha design-center spaces application-templates \ components create my-component \ - --application-template=my-app-template --space=my-space \ - --project=my-project --location=us-central1 \ - --shared-template-revision-uri=my-shared-template/revisions/rev1 + $ gcloud alpha design-center spaces application-templates \ + components create my-component \ + --application-template=my-app-template --space=my-space \ + --project=my-project --location=us-central1 \ + --shared-template-revision-uri=my-shared-template/revisions/rev1 To create the component my-component in application template my-app-template, space my-space, project my-project and location us-central1 using a shared template my-shared-template with its latest revision present in the same space, run: - $ gcloud alpha design-center spaces application-templates \ components create my-component \ - --application-template=my-app-template --space=my-space \ - --project=my-project --location=us-central1 \ - --shared-template-revision-uri=my-shared-template + $ gcloud alpha design-center spaces application-templates \ + components create my-component \ + --application-template=my-app-template --space=my-space \ + --project=my-project --location=us-central1 \ + --shared-template-revision-uri=my-shared-template To create the component my-component with a display name My Component in application template my-app-template, space my-space, project my-project and location us-central1 using a shared template revision, run: - $ gcloud alpha design-center spaces application-templates \ components create my-component \ - --application-template=my-app-template --space=my-space \ - --project=my-project --location=us-central1 \ - --shared-template-revision-uri=projects/my-project/locations/\ + $ gcloud alpha design-center spaces application-templates \ + components create my-component \ + --application-template=my-app-template --space=my-space \ + --project=my-project --location=us-central1 \ + --shared-template-revision-uri=projects/my-project/locations/\ us-central1/spaces/my-space/sharedTemplates/my-shared-template/\ revisions/rev1 --display-name="My Component" @@ -91,19 +98,21 @@ EXAMPLES project my-project and location us-central1, run the following shorthand example: - $ gcloud alpha design-center spaces application-templates \ components create my-component \ - --application-template=my-app-template --space=my-space \ - --project=my-project --location=us-central1 \ - --shared-template-revision-uri=projects/my-project/locations/\ + $ gcloud alpha design-center spaces application-templates \ + components create my-component \ + --application-template=my-app-template --space=my-space \ + --project=my-project --location=us-central1 \ + --shared-template-revision-uri=projects/my-project/locations/\ us-central1/spaces/my-space/sharedTemplates/my-shared-template/\ revisions/rev1 --parameters=key=region,value=us-central1 Or run the following JSON example: - $ gcloud alpha design-center spaces application-templates \ components create my-component \ - --application-template=my-app-template --space=my-space \ - --project=my-project --location=us-central1 \ - --shared-template-revision-uri=projects/my-project/locations/\ + $ gcloud alpha design-center spaces application-templates \ + components create my-component \ + --application-template=my-app-template --space=my-space \ + --project=my-project --location=us-central1 \ + --shared-template-revision-uri=projects/my-project/locations/\ us-central1/spaces/my-space/sharedTemplates/my-shared-template/\ revisions/rev1 \ --parameters='[{"key": "region", "value": "us-central1"}]' @@ -111,10 +120,11 @@ EXAMPLES Or create a YAML or JSON file with the parameters and run the following file example: - $ gcloud alpha design-center spaces application-templates \ components create my-component \ - --application-template=my-app-template --space=my-space \ - --project=my-project --location=us-central1 \ - --shared-template-revision-uri=projects/my-project/locations/\ + $ gcloud alpha design-center spaces application-templates \ + components create my-component \ + --application-template=my-app-template --space=my-space \ + --project=my-project --location=us-central1 \ + --shared-template-revision-uri=projects/my-project/locations/\ us-central1/spaces/my-space/sharedTemplates/my-shared-template/\ revisions/rev1 --parameters=my-parameters.yaml diff --git a/gcloud/alpha/design-center/spaces/catalogs/templates/create b/gcloud/alpha/design-center/spaces/catalogs/templates/create index 3baf8d4a5..f3518050a 100644 --- a/gcloud/alpha/design-center/spaces/catalogs/templates/create +++ b/gcloud/alpha/design-center/spaces/catalogs/templates/create @@ -5,36 +5,40 @@ NAME SYNOPSIS gcloud alpha design-center spaces catalogs templates create (TEMPLATE : --catalog=CATALOG --location=LOCATION --space=SPACE) - [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] - [--template-category=TEMPLATE_CATEGORY] [--type=TYPE] - [GCLOUD_WIDE_FLAG ...] + --template-category=TEMPLATE_CATEGORY [--description=DESCRIPTION] + [--display-name=DISPLAY_NAME] [--type=TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a catalog template. EXAMPLES - To create the catalog template my-template in catalog my-catalog, space - my-space, project my-project and location us-central1, run: + To create the catalog template my-template with template category + application-template in catalog my-catalog, space my-space, project + my-project and location us-central1, run: $ gcloud alpha design-center spaces catalogs templates create \ my-template --catalog=my-catalog --space=my-space \ - --project=my-project --location=us-central1 + --project=my-project --location=us-central1 \ + --template-category=application-template Or run: $ gcloud alpha design-center spaces catalogs templates create \ projects/my-project/locations/us-central1/spaces/my-space/\ - catalogs/my-catalog/templates/my-template + catalogs/my-catalog/templates/my-template \ + --template-category=application-template To create the catalog template my-template with a display name of My - Template and description of My template description in catalog my-catalog, - space my-space, project my-project and location us-central1, run: + Template, description of My template description and template category of + application-template in catalog my-catalog, space my-space, project + my-project and location us-central1, run: $ gcloud alpha design-center spaces catalogs templates create \ my-template --catalog=my-catalog --space=my-space \ --project=my-project --location=us-central1 \ --display-name="My Template" \ - --description="My template description" + --description="My template description" \ + --template-category=application-template POSITIONAL ARGUMENTS Template resource - Identifier. The catalog template name in following @@ -85,13 +89,7 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --space on the command line. -FLAGS - --description=DESCRIPTION - The catalog template description. - - --display-name=DISPLAY_NAME - The display name of a catalog template. - +REQUIRED FLAGS --template-category=TEMPLATE_CATEGORY The category of the ADC template. TEMPLATE_CATEGORY must be one of: @@ -103,6 +101,13 @@ FLAGS Imported as a single, complex unit without disassembling into components. +OPTIONAL FLAGS + --description=DESCRIPTION + The catalog template description. + + --display-name=DISPLAY_NAME + The display name of a catalog template. + --type=TYPE The Application Design Center assembly template type. TYPE must be one of: diff --git a/gcloud/alpha/design-center/spaces/shared-templates/describe b/gcloud/alpha/design-center/spaces/shared-templates/describe index 80031b0d7..22db9601c 100644 --- a/gcloud/alpha/design-center/spaces/shared-templates/describe +++ b/gcloud/alpha/design-center/spaces/shared-templates/describe @@ -19,7 +19,7 @@ EXAMPLES my-shared-template --space=my-space --project=my-project \ --location=us-central1 - Or run: + Or run: $ gcloud alpha design-center spaces shared-templates describe \ projects/my-project/locations/us-central1/spaces/my-space/\ diff --git a/gcloud/alpha/design-center/spaces/shared-templates/list b/gcloud/alpha/design-center/spaces/shared-templates/list index 2a09c6795..a16107396 100644 --- a/gcloud/alpha/design-center/spaces/shared-templates/list +++ b/gcloud/alpha/design-center/spaces/shared-templates/list @@ -19,7 +19,7 @@ EXAMPLES $ gcloud alpha design-center spaces shared-templates list \ --space=my-space --project=my-project --location=us-central1 - Or run: + Or run: $ gcloud alpha design-center spaces shared-templates list \ --space=projects/my-project/locations/us-central1/spaces/\ diff --git a/gcloud/alpha/design-center/spaces/shared-templates/revisions/describe b/gcloud/alpha/design-center/spaces/shared-templates/revisions/describe index b8a5e9adc..ddf3e7777 100644 --- a/gcloud/alpha/design-center/spaces/shared-templates/revisions/describe +++ b/gcloud/alpha/design-center/spaces/shared-templates/revisions/describe @@ -20,7 +20,7 @@ EXAMPLES describe my-revision --shared-template=my-shared-template \ --space=my-space --project=my-project --location=us-central1 - Or run: + Or run: $ gcloud alpha design-center spaces shared-templates revisions \ describe \ diff --git a/gcloud/alpha/design-center/spaces/shared-templates/revisions/list b/gcloud/alpha/design-center/spaces/shared-templates/revisions/list index 0b707035e..36a85a749 100644 --- a/gcloud/alpha/design-center/spaces/shared-templates/revisions/list +++ b/gcloud/alpha/design-center/spaces/shared-templates/revisions/list @@ -21,7 +21,7 @@ EXAMPLES list --shared-template=my-shared-template --space=my-space \ --project=my-project --location=us-central1 - Or run: + Or run: $ gcloud alpha design-center spaces shared-templates revisions \ list \ diff --git a/gcloud/alpha/iap/oauth-brands/create b/gcloud/alpha/iap/oauth-brands/create index 07d6413f3..2b2062946 100644 --- a/gcloud/alpha/iap/oauth-brands/create +++ b/gcloud/alpha/iap/oauth-brands/create @@ -7,7 +7,11 @@ SYNOPSIS --support_email=SUPPORT_EMAIL [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) (DEPRECATED) This command is deprecated. + (ALPHA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud alpha iap oauth-brands create is used to create a Cloud OAuth brand for the project. The brand is 'internal only', meaning OAuth clients diff --git a/gcloud/alpha/iap/oauth-brands/describe b/gcloud/alpha/iap/oauth-brands/describe index f911a4721..261a99e20 100644 --- a/gcloud/alpha/iap/oauth-brands/describe +++ b/gcloud/alpha/iap/oauth-brands/describe @@ -5,7 +5,11 @@ SYNOPSIS gcloud alpha iap oauth-brands describe NAME [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) (DEPRECATED) This command is deprecated. + (ALPHA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud alpha iap oauth-brands describe is used to describe a Cloud OAuth brand. diff --git a/gcloud/alpha/iap/oauth-brands/help b/gcloud/alpha/iap/oauth-brands/help index 307beb254..5757be661 100644 --- a/gcloud/alpha/iap/oauth-brands/help +++ b/gcloud/alpha/iap/oauth-brands/help @@ -7,7 +7,11 @@ SYNOPSIS DESCRIPTION (ALPHA) (DEPRECATED) Manage IAP OAuth brands. - This command is deprecated. + This command is deprecated and will be non-functional after the IAP OAuth + Admin APIs are turned down. Jan 19, 2026: Google will discontinue support + for the IAP OAuth Admin APIs. New projects will not be able to use these + APIs. March 19, 2026: The IAP OAuth Admin APIs will be permanently shut + down. Access to this feature will no longer be available. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/alpha/iap/oauth-brands/list b/gcloud/alpha/iap/oauth-brands/list index bf7fdc338..5612b1320 100644 --- a/gcloud/alpha/iap/oauth-brands/list +++ b/gcloud/alpha/iap/oauth-brands/list @@ -6,7 +6,11 @@ SYNOPSIS [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) (DEPRECATED) This command is deprecated. + (ALPHA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud alpha iap oauth-brands list is used to list the Cloud OAuth brand in the project. diff --git a/gcloud/alpha/iap/oauth-clients/create b/gcloud/alpha/iap/oauth-clients/create index 64b8861e9..cecfcdc65 100644 --- a/gcloud/alpha/iap/oauth-clients/create +++ b/gcloud/alpha/iap/oauth-clients/create @@ -7,7 +7,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) (DEPRECATED) This command is deprecated. + (ALPHA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud alpha iap oauth-clients create is used to create an OAuth client in the project to be used by Cloud IAP. To call this command, the Cloud OAuth diff --git a/gcloud/alpha/iap/oauth-clients/delete b/gcloud/alpha/iap/oauth-clients/delete index 93fe0b781..22e532ca6 100644 --- a/gcloud/alpha/iap/oauth-clients/delete +++ b/gcloud/alpha/iap/oauth-clients/delete @@ -6,7 +6,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) (DEPRECATED) This command is deprecated. + (ALPHA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud alpha iap oauth-clients delete is used to delete a Cloud IAP OAuth client. Note this command cannot be used to delete any other type of OAuth diff --git a/gcloud/alpha/iap/oauth-clients/describe b/gcloud/alpha/iap/oauth-clients/describe index cd68394f1..7e265f13d 100644 --- a/gcloud/alpha/iap/oauth-clients/describe +++ b/gcloud/alpha/iap/oauth-clients/describe @@ -6,7 +6,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) (DEPRECATED) This command is deprecated. + (ALPHA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud alpha iap oauth-clients describe is used to describe a Cloud IAP OAuth client. Note this command cannot be used to describe any other type diff --git a/gcloud/alpha/iap/oauth-clients/help b/gcloud/alpha/iap/oauth-clients/help index 7fffa973a..e04a3a778 100644 --- a/gcloud/alpha/iap/oauth-clients/help +++ b/gcloud/alpha/iap/oauth-clients/help @@ -7,7 +7,11 @@ SYNOPSIS DESCRIPTION (ALPHA) (DEPRECATED) Manage IAP OAuth clients. - This command is deprecated. + This command is deprecated and will be non-functional after the IAP OAuth + Admin APIs are turned down. Jan 19, 2026: Google will discontinue support + for the IAP OAuth Admin APIs. New projects will not be able to use these + APIs. March 19, 2026: The IAP OAuth Admin APIs will be permanently shut + down. Access to this feature will no longer be available. Manage OAuth clients that are used by Cloud Identity-Aware Proxy. Note this API cannot be used as a generic management API for all OAuth clients in diff --git a/gcloud/alpha/iap/oauth-clients/list b/gcloud/alpha/iap/oauth-clients/list index 809861bef..40eaeab9a 100644 --- a/gcloud/alpha/iap/oauth-clients/list +++ b/gcloud/alpha/iap/oauth-clients/list @@ -8,7 +8,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) (DEPRECATED) This command is deprecated. + (ALPHA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud alpha iap oauth-clients list is used to list Cloud IAP OAuth clients in a Cloud OAuth brand. Note this command will not list any other type of diff --git a/gcloud/alpha/iap/oauth-clients/reset-secret b/gcloud/alpha/iap/oauth-clients/reset-secret index 4a97dc7be..83530149c 100644 --- a/gcloud/alpha/iap/oauth-clients/reset-secret +++ b/gcloud/alpha/iap/oauth-clients/reset-secret @@ -7,7 +7,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) (DEPRECATED) This command is deprecated. + (ALPHA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud alpha iap oauth-clients reset-secret is used to reset a Cloud IAP OAuth client secret. Note this command cannot be used to reset the secret diff --git a/gcloud/alpha/managed-kafka/connect-clusters/create b/gcloud/alpha/managed-kafka/connect-clusters/create index 384bee6a0..27754c272 100644 --- a/gcloud/alpha/managed-kafka/connect-clusters/create +++ b/gcloud/alpha/managed-kafka/connect-clusters/create @@ -144,5 +144,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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connect-clusters create + + $ gcloud beta managed-kafka connect-clusters create diff --git a/gcloud/alpha/managed-kafka/connect-clusters/delete b/gcloud/alpha/managed-kafka/connect-clusters/delete index 41810a6f3..ccf75dbd2 100644 --- a/gcloud/alpha/managed-kafka/connect-clusters/delete +++ b/gcloud/alpha/managed-kafka/connect-clusters/delete @@ -74,5 +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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connect-clusters delete + + $ gcloud beta managed-kafka connect-clusters delete diff --git a/gcloud/alpha/managed-kafka/connect-clusters/describe b/gcloud/alpha/managed-kafka/connect-clusters/describe index c565eb4e5..c1ec7bda5 100644 --- a/gcloud/alpha/managed-kafka/connect-clusters/describe +++ b/gcloud/alpha/managed-kafka/connect-clusters/describe @@ -69,5 +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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connect-clusters describe + + $ gcloud beta managed-kafka connect-clusters describe diff --git a/gcloud/alpha/managed-kafka/connect-clusters/help b/gcloud/alpha/managed-kafka/connect-clusters/help index 0da29e37a..d471f409a 100644 --- a/gcloud/alpha/managed-kafka/connect-clusters/help +++ b/gcloud/alpha/managed-kafka/connect-clusters/help @@ -37,5 +37,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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connect-clusters + + $ gcloud beta managed-kafka connect-clusters diff --git a/gcloud/alpha/managed-kafka/connect-clusters/list b/gcloud/alpha/managed-kafka/connect-clusters/list index 3daacabd6..145e1018c 100644 --- a/gcloud/alpha/managed-kafka/connect-clusters/list +++ b/gcloud/alpha/managed-kafka/connect-clusters/list @@ -82,5 +82,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connect-clusters list + + $ gcloud beta managed-kafka connect-clusters list diff --git a/gcloud/alpha/managed-kafka/connect-clusters/update b/gcloud/alpha/managed-kafka/connect-clusters/update index 9cc6b57c4..6c1e68504 100644 --- a/gcloud/alpha/managed-kafka/connect-clusters/update +++ b/gcloud/alpha/managed-kafka/connect-clusters/update @@ -171,5 +171,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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connect-clusters update + + $ gcloud beta managed-kafka connect-clusters update diff --git a/gcloud/alpha/managed-kafka/connectors/create b/gcloud/alpha/managed-kafka/connectors/create index 1e54b3c0d..044cd9eba 100644 --- a/gcloud/alpha/managed-kafka/connectors/create +++ b/gcloud/alpha/managed-kafka/connectors/create @@ -121,5 +121,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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connectors create + + $ gcloud beta managed-kafka connectors create diff --git a/gcloud/alpha/managed-kafka/connectors/delete b/gcloud/alpha/managed-kafka/connectors/delete index 27b1ffbfb..4d27dcaab 100644 --- a/gcloud/alpha/managed-kafka/connectors/delete +++ b/gcloud/alpha/managed-kafka/connectors/delete @@ -76,5 +76,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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connectors delete + + $ gcloud beta managed-kafka connectors delete diff --git a/gcloud/alpha/managed-kafka/connectors/describe b/gcloud/alpha/managed-kafka/connectors/describe index 6f0a8ce47..1b12d025e 100644 --- a/gcloud/alpha/managed-kafka/connectors/describe +++ b/gcloud/alpha/managed-kafka/connectors/describe @@ -76,5 +76,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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connectors describe + + $ gcloud beta managed-kafka connectors describe diff --git a/gcloud/alpha/managed-kafka/connectors/help b/gcloud/alpha/managed-kafka/connectors/help index 68ec6a241..69cb6500f 100644 --- a/gcloud/alpha/managed-kafka/connectors/help +++ b/gcloud/alpha/managed-kafka/connectors/help @@ -51,5 +51,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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connectors + + $ gcloud beta managed-kafka connectors diff --git a/gcloud/alpha/managed-kafka/connectors/list b/gcloud/alpha/managed-kafka/connectors/list index 7c00e950e..ccc52e7bd 100644 --- a/gcloud/alpha/managed-kafka/connectors/list +++ b/gcloud/alpha/managed-kafka/connectors/list @@ -98,5 +98,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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connectors list + + $ gcloud beta managed-kafka connectors list diff --git a/gcloud/alpha/managed-kafka/connectors/pause b/gcloud/alpha/managed-kafka/connectors/pause index 606e1ad93..eeb97d37e 100644 --- a/gcloud/alpha/managed-kafka/connectors/pause +++ b/gcloud/alpha/managed-kafka/connectors/pause @@ -76,5 +76,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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connectors pause + + $ gcloud beta managed-kafka connectors pause diff --git a/gcloud/alpha/managed-kafka/connectors/restart b/gcloud/alpha/managed-kafka/connectors/restart index 37d9a2b1d..ba4b31947 100644 --- a/gcloud/alpha/managed-kafka/connectors/restart +++ b/gcloud/alpha/managed-kafka/connectors/restart @@ -76,5 +76,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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connectors restart + + $ gcloud beta managed-kafka connectors restart diff --git a/gcloud/alpha/managed-kafka/connectors/resume b/gcloud/alpha/managed-kafka/connectors/resume index 3eb48eda3..a1ffb800c 100644 --- a/gcloud/alpha/managed-kafka/connectors/resume +++ b/gcloud/alpha/managed-kafka/connectors/resume @@ -77,5 +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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connectors resume + + $ gcloud beta managed-kafka connectors resume diff --git a/gcloud/alpha/managed-kafka/connectors/stop b/gcloud/alpha/managed-kafka/connectors/stop index 64b6a0454..2ce91c9ae 100644 --- a/gcloud/alpha/managed-kafka/connectors/stop +++ b/gcloud/alpha/managed-kafka/connectors/stop @@ -76,5 +76,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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connectors stop + + $ gcloud beta managed-kafka connectors stop diff --git a/gcloud/alpha/managed-kafka/connectors/update b/gcloud/alpha/managed-kafka/connectors/update index 134d688f8..fe1169544 100644 --- a/gcloud/alpha/managed-kafka/connectors/update +++ b/gcloud/alpha/managed-kafka/connectors/update @@ -117,5 +117,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. + access allowlist. These variants are also available: + + $ gcloud managed-kafka connectors update + + $ gcloud beta managed-kafka connectors update diff --git a/gcloud/alpha/pam/grants/withdraw b/gcloud/alpha/pam/grants/withdraw index 091df0820..4f8e3a01e 100644 --- a/gcloud/alpha/pam/grants/withdraw +++ b/gcloud/alpha/pam/grants/withdraw @@ -96,5 +96,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta pam grants withdraw diff --git a/gcloud/alpha/pam/settings/describe b/gcloud/alpha/pam/settings/describe index 94c745e68..eb8aaf47a 100644 --- a/gcloud/alpha/pam/settings/describe +++ b/gcloud/alpha/pam/settings/describe @@ -93,5 +93,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta pam settings describe diff --git a/gcloud/alpha/pam/settings/describe-effective b/gcloud/alpha/pam/settings/describe-effective index 9f7d25eaa..04eb1a5f1 100644 --- a/gcloud/alpha/pam/settings/describe-effective +++ b/gcloud/alpha/pam/settings/describe-effective @@ -97,5 +97,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta pam settings describe-effective diff --git a/gcloud/alpha/pam/settings/export b/gcloud/alpha/pam/settings/export index 2d40fc8b5..6a3682431 100644 --- a/gcloud/alpha/pam/settings/export +++ b/gcloud/alpha/pam/settings/export @@ -104,5 +104,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta pam settings export diff --git a/gcloud/alpha/pam/settings/help b/gcloud/alpha/pam/settings/help index 0b8da86b6..c417989f2 100644 --- a/gcloud/alpha/pam/settings/help +++ b/gcloud/alpha/pam/settings/help @@ -113,5 +113,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta pam settings diff --git a/gcloud/alpha/pam/settings/update b/gcloud/alpha/pam/settings/update index 86cd92d1b..a301a75c2 100644 --- a/gcloud/alpha/pam/settings/update +++ b/gcloud/alpha/pam/settings/update @@ -107,5 +107,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta pam settings update diff --git a/gcloud/alpha/run/worker-pools/deploy b/gcloud/alpha/run/worker-pools/deploy index f06253fa6..cdd4cc0ce 100644 --- a/gcloud/alpha/run/worker-pools/deploy +++ b/gcloud/alpha/run/worker-pools/deploy @@ -6,8 +6,8 @@ SYNOPSIS gcloud alpha run worker-pools deploy [[WORKER_POOL] --region=REGION] [--async] [--breakglass=JUSTIFICATION] [--container=CONTAINER] [--description=DESCRIPTION] [--gpu-type=GPU_TYPE] - [--[no-]gpu-zonal-redundancy] [--max=MAX] [--mesh=MESH] [--min=MIN] - [--no-promote] [--remove-containers=[CONTAINER,...]] + [--[no-]gpu-zonal-redundancy] [--max=MAX] [--min=MIN] [--no-promote] + [--remove-containers=[CONTAINER,...]] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] [--service-account=SERVICE_ACCOUNT] [--vpc-egress=VPC_EGRESS] [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -123,12 +123,6 @@ FLAGS divided among all Revisions receiving a percentage of instance assignments and can be modified without deploying a new Revision. - --mesh=MESH - Enables Cloud Service Mesh using the specified mesh resource name. Mesh - resource name must be in the format of - projects/PROJECT/locations/global/meshes/MESH_NAME or MESH_NAME. Will - default to the current project if only MESH_NAME is provided. - --min=MIN The minimum number of container instances to run for this WorkerPool or 'default' to use system default of 1. These instances will be divided diff --git a/gcloud/alpha/run/worker-pools/update b/gcloud/alpha/run/worker-pools/update index dc8743dec..e69cf99b8 100644 --- a/gcloud/alpha/run/worker-pools/update +++ b/gcloud/alpha/run/worker-pools/update @@ -6,8 +6,8 @@ SYNOPSIS gcloud alpha run worker-pools update [[WORKER_POOL] --region=REGION] [--async] [--breakglass=JUSTIFICATION] [--container=CONTAINER] [--description=DESCRIPTION] [--gpu-type=GPU_TYPE] - [--[no-]gpu-zonal-redundancy] [--max=MAX] [--mesh=MESH] [--min=MIN] - [--no-promote] [--remove-containers=[CONTAINER,...]] + [--[no-]gpu-zonal-redundancy] [--max=MAX] [--min=MIN] [--no-promote] + [--remove-containers=[CONTAINER,...]] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] [--service-account=SERVICE_ACCOUNT] [--vpc-egress=VPC_EGRESS] [--add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -119,12 +119,6 @@ FLAGS divided among all Revisions receiving a percentage of instance assignments and can be modified without deploying a new Revision. - --mesh=MESH - Enables Cloud Service Mesh using the specified mesh resource name. Mesh - resource name must be in the format of - projects/PROJECT/locations/global/meshes/MESH_NAME or MESH_NAME. Will - default to the current project if only MESH_NAME is provided. - --min=MIN The minimum number of container instances to run for this WorkerPool or 'default' to use system default of 1. These instances will be divided diff --git a/gcloud/alpha/spanner/cli b/gcloud/alpha/spanner/cli index 7a1d15b21..dbc29b373 100644 --- a/gcloud/alpha/spanner/cli +++ b/gcloud/alpha/spanner/cli @@ -119,5 +119,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud spanner cli diff --git a/gcloud/alpha/storage/insights/dataset-configs/create b/gcloud/alpha/storage/insights/dataset-configs/create index c856e778d..c84946c31 100644 --- a/gcloud/alpha/storage/insights/dataset-configs/create +++ b/gcloud/alpha/storage/insights/dataset-configs/create @@ -11,6 +11,7 @@ SYNOPSIS | --source-folders-file=SOURCE_FOLDER_NUMBERS_IN_FILE | --source-projects=[SOURCE_PROJECT_NUMBERS,...] | --source-projects-file=SOURCE_PROJECT_NUMBERS_IN_FILE) + [--activity-data-retention-period-days=ACTIVITY_DATA_RETENTION_DAYS] [--auto-add-new-buckets] [--description=DESCRIPTION] [--identity=IDENTITY_TYPE; default="IDENTITY_TYPE_PER_CONFIG"] [--exclude-bucket-names=[BUCKETS_NAMES,...] @@ -86,6 +87,11 @@ REQUIRED FLAGS CSV formatted file containing source project numbers, one per line. OPTIONAL FLAGS + --activity-data-retention-period-days=ACTIVITY_DATA_RETENTION_DAYS + Provide retention period for the activity data in the config. This + overrides the retention period for activity data. Otherwise, the + retention_period_days value is used for activity data as well. + --auto-add-new-buckets Automatically include any new buckets created if they satisfy criteria defined in config settings. diff --git a/gcloud/alpha/storage/insights/dataset-configs/update b/gcloud/alpha/storage/insights/dataset-configs/update index 36fa4b981..78c626f1e 100644 --- a/gcloud/alpha/storage/insights/dataset-configs/update +++ b/gcloud/alpha/storage/insights/dataset-configs/update @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha storage insights dataset-configs update (DATASET_CONFIG : --location=LOCATION) + [--activity-data-retention-period-days=ACTIVITY_DATA_RETENTION_DAYS] [--auto-add-new-buckets=AUTO_ADD_NEW_BUCKETS] [--description=DESCRIPTION] [--retention-period-days=RETENTION_DAYS] [--enable-organization-scope @@ -75,6 +76,11 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line. FLAGS + --activity-data-retention-period-days=ACTIVITY_DATA_RETENTION_DAYS + Provide retention period for the activity data in the config. This + overrides the retention period for activity data. Otherwise, the + retention_period_days value is used for activity data as well. + --auto-add-new-buckets=AUTO_ADD_NEW_BUCKETS Automatically include any new buckets created if they satisfy criteria defined in config settings. AUTO_ADD_NEW_BUCKETS must be one of: true, diff --git a/gcloud/alpha/workstations/ssh b/gcloud/alpha/workstations/ssh index 4fa07bf45..5ce7dc164 100644 --- a/gcloud/alpha/workstations/ssh +++ b/gcloud/alpha/workstations/ssh @@ -12,6 +12,8 @@ SYNOPSIS DESCRIPTION (ALPHA) SSH into a running workstation. + Note that arguments for the NO_PROXY environment variable must be FQDNs. + EXAMPLES To ssh into a running workstation, run: diff --git a/gcloud/alpha/workstations/start-tcp-tunnel b/gcloud/alpha/workstations/start-tcp-tunnel index 81432bb00..d958a4152 100644 --- a/gcloud/alpha/workstations/start-tcp-tunnel +++ b/gcloud/alpha/workstations/start-tcp-tunnel @@ -13,6 +13,8 @@ DESCRIPTION (ALPHA) Start a tunnel through which a local process can forward TCP traffic to the workstation. + Note that arguments for the NO_PROXY environment variable must be FQDNs. + EXAMPLES To start a tunnel to port 22 on a workstation, run: diff --git a/gcloud/backup-dr/backup-plan-associations/trigger-backup b/gcloud/backup-dr/backup-plan-associations/trigger-backup index 38c1592f9..a97519a49 100644 --- a/gcloud/backup-dr/backup-plan-associations/trigger-backup +++ b/gcloud/backup-dr/backup-plan-associations/trigger-backup @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud backup-dr backup-plan-associations trigger-backup (BACKUP_PLAN_ASSOCIATION - : --location=LOCATION --workload-project=WORKLOAD_PROJECT) - --backup-rule-id=BACKUP_RULE_ID [--async] [GCLOUD_WIDE_FLAG ...] + : --location=LOCATION --workload-project=WORKLOAD_PROJECT) [--async] + [--backup-rule-id=BACKUP_RULE_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create an on-demand backup for a resource. Trigger an on demand backup for @@ -56,17 +56,16 @@ POSITIONAL ARGUMENTS ▸ provide the argument --project on the command line; ▸ set the property core/project. -REQUIRED FLAGS - --backup-rule-id=BACKUP_RULE_ID - Name of an existing backup rule to use for creating an on-demand - backup. - -OPTIONAL FLAGS +FLAGS --async Return immediately, without waiting for the operation in progress to complete. The default is True. Enabled by default, use --no-async to disable. + --backup-rule-id=BACKUP_RULE_ID + Name of an existing backup rule to use for creating an on-demand + backup. + 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/ai/endpoints/deploy-model b/gcloud/beta/ai/endpoints/deploy-model index ed09a6cbc..f89c97411 100644 --- a/gcloud/beta/ai/endpoints/deploy-model +++ b/gcloud/beta/ai/endpoints/deploy-model @@ -12,6 +12,7 @@ SYNOPSIS [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] [--multihost-gpu-node-count=MULTIHOST_GPU_NODE_COUNT] + [--required-replica-count=REQUIRED_REPLICA_COUNT] [--reservation-affinity=[key=KEY], [reservation-affinity-type=RESERVATION-AFFINITY-TYPE], [values=VALUES]] [--service-account=SERVICE_ACCOUNT] [--spot] @@ -146,6 +147,11 @@ OPTIONAL FLAGS The number of nodes per replica for multihost GPU deployments. Required for multihost GPU deployments. + --required-replica-count=REQUIRED_REPLICA_COUNT + Required number of machine replicas for the deployment resources the + model will be considered successfully deployed. This value must be + greater than or equal to 1 and less than or equal to min-replica-count. + --reservation-affinity=[key=KEY],[reservation-affinity-type=RESERVATION-AFFINITY-TYPE],[values=VALUES] A ReservationAffinity can be used to configure a Vertex AI resource (e.g., a DeployedModel) to draw its Compute Engine resources from a diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/create b/gcloud/beta/beyondcorp/security-gateways/applications/create index 060c9a664..36e331df8 100644 --- a/gcloud/beta/beyondcorp/security-gateways/applications/create +++ b/gcloud/beta/beyondcorp/security-gateways/applications/create @@ -7,7 +7,9 @@ SYNOPSIS (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) --endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] [--async] [--display-name=DISPLAY_NAME] [--request-id=REQUEST_ID] - [--upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK]] + [--schema=SCHEMA] + [--upstreams=[egressPolicy=EGRESSPOLICY], + [external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -65,11 +67,11 @@ REQUIRED FLAGS combination of hostname and ports as endpoint matchers is used to match the application. Match conditions for OR logic. An array of match conditions to allow for multiple matching criteria. The rule is - considered a match if one of the conditions is met. The conditions can - be one of the following combinations (Hostname), (Hostname & Ports) + considered a match if one of the conditions is met. The conditions + should be the following combination: (Hostname & Ports) - EXAMPLES: Hostname - (".example.com"), ("xyz.example.com") Hostname and - Ports - ("example.com" and "22"), ("example.com" and "22,33") etc. + EXAMPLES: Hostname and Ports - (".example.com", "443"), ("example.com" + and "22"), ("example.com" and "22,33") etc. hostname Hostname of the application. @@ -95,7 +97,7 @@ OPTIONAL FLAGS complete. --display-name=DISPLAY_NAME - An arbitrary user-provided name for the Application resource. Cannot + An arbitrary user-provided name for the application resource. Cannot exceed 64 characters. --request-id=REQUEST_ID @@ -104,7 +106,17 @@ OPTIONAL FLAGS ignore request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request. - --upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK] + --schema=SCHEMA + Type of the external application. SCHEMA must be one of: + + api-gateway + Service Discovery API endpoint when Service Discovery is enabled in + Gateway. + proxy-gateway + Proxy which routes traffic to actual applications, like Netscaler + Gateway. + + --upstreams=[egressPolicy=EGRESSPOLICY],[external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL] Which upstream resources to forward traffic to. egressPolicy @@ -113,6 +125,18 @@ OPTIONAL FLAGS regions List of the regions where the application sends traffic. + external + List of the external endpoints to forward traffic to. + + endpoints + List of the endpoints to forward traffic to. + + hostname + Hostname of the endpoint. + + port + Port of the endpoint. + network Network to forward traffic to. @@ -120,13 +144,63 @@ OPTIONAL FLAGS Network name is of the format: projects/{project}/global/networks/{network}. + proxyProtocol + Enables proxy protocol configuration for the upstream. + + allowedClientHeaders + List of the allowed client header names. + + clientIp + Client IP configuration. The client IP address is included if + true. + + contextualHeaders + Configuration for the contextual headers. + + deviceInfo + Device info configuration. + + outputType + The output type of the delegated device info. + + groupInfo + Group info configuration. + + outputType + The output type of the delegated group info. + + outputType + Default output type for all enabled headers. + + userInfo + User info configuration. + + outputType + The output type of the delegated user info. + + gatewayIdentity + Gateway identity configuration. + + metadataHeaders + Custom resource specific headers along with the values. The + names should conform to RFC 9110: > Field names SHOULD + constrain themselves to alphanumeric characters, "-", and ".", + and SHOULD begin with a letter. Field values SHOULD contain + only ASCII printable characters and tab. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + Shorthand Example: - --upstreams=egressPolicy={regions=[string]},network={name=string} --upstreams=egressPolicy={regions=[string]},network={name=string} + --upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} --upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} JSON Example: - --upstreams='[{"egressPolicy": {"regions": ["string"]}, "network": {"name": "string"}}]' + --upstreams='[{"egressPolicy": {"regions": ["string"]}, "external": {"endpoints": [{"hostname": "string", "port": int}]}, "network": {"name": "string"}, "proxyProtocol": {"allowedClientHeaders": ["string"], "clientIp": boolean, "contextualHeaders": {"deviceInfo": {"outputType": "string"}, "groupInfo": {"outputType": "string"}, "outputType": "string", "userInfo": {"outputType": "string"}}, "gatewayIdentity": "string", "metadataHeaders": {"string": "string"}}}]' File Example: diff --git a/gcloud/beta/beyondcorp/security-gateways/applications/update b/gcloud/beta/beyondcorp/security-gateways/applications/update index d30ec7a54..198307eb5 100644 --- a/gcloud/beta/beyondcorp/security-gateways/applications/update +++ b/gcloud/beta/beyondcorp/security-gateways/applications/update @@ -6,14 +6,18 @@ SYNOPSIS gcloud beta beyondcorp security-gateways applications update (APPLICATION : --location=LOCATION --security-gateway=SECURITY_GATEWAY) [--async] [--display-name=DISPLAY_NAME] [--request-id=REQUEST_ID] + [--schema=SCHEMA] [--endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] | --add-endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS] --clear-endpoint-matchers | --remove-endpoint-matchers=[hostname=HOSTNAME],[ports=PORTS]] - [--upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK] - | --add-upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK] + [--upstreams=[egressPolicy=EGRESSPOLICY], + [external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL] + | --add-upstreams=[egressPolicy=EGRESSPOLICY], + [external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL] --clear-upstreams - | --remove-upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK]] + | --remove-upstreams=[egressPolicy=EGRESSPOLICY], + [external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -71,7 +75,7 @@ FLAGS complete. --display-name=DISPLAY_NAME - An arbitrary user-provided name for the Application resource. Cannot + An arbitrary user-provided name for the application resource. Cannot exceed 64 characters. --request-id=REQUEST_ID @@ -89,6 +93,16 @@ FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). + --schema=SCHEMA + Type of the external application. SCHEMA must be one of: + + api-gateway + Service Discovery API endpoint when Service Discovery is enabled in + Gateway. + proxy-gateway + Proxy which routes traffic to actual applications, like Netscaler + Gateway. + Update endpoint_matchers. At most one of these can be specified: @@ -99,12 +113,11 @@ FLAGS matchers is used to match the application. Match conditions for OR logic. An array of match conditions to allow for multiple matching criteria. The rule is considered a match if one of the conditions is - met. The conditions can be one of the following combinations - (Hostname), (Hostname & Ports) + met. The conditions should be the following combination: (Hostname & + Ports) - EXAMPLES: Hostname - (".example.com"), ("xyz.example.com") Hostname - and Ports - ("example.com" and "22"), ("example.com" and "22,33") - etc. + EXAMPLES: Hostname and Ports - (".example.com", "443"), + ("example.com" and "22"), ("example.com" and "22,33") etc. hostname Hostname of the application. @@ -130,12 +143,11 @@ FLAGS matchers is used to match the application. Match conditions for OR logic. An array of match conditions to allow for multiple matching criteria. The rule is considered a match if one of the conditions is - met. The conditions can be one of the following combinations - (Hostname), (Hostname & Ports) + met. The conditions should be the following combination: (Hostname & + Ports) - EXAMPLES: Hostname - (".example.com"), ("xyz.example.com") Hostname - and Ports - ("example.com" and "22"), ("example.com" and "22,33") - etc. + EXAMPLES: Hostname and Ports - (".example.com", "443"), + ("example.com" and "22"), ("example.com" and "22,33") etc. hostname Hostname of the application. @@ -166,12 +178,11 @@ FLAGS and ports as endpoint matchers is used to match the application. Match conditions for OR logic. An array of match conditions to allow for multiple matching criteria. The rule is considered a - match if one of the conditions is met. The conditions can be one of - the following combinations (Hostname), (Hostname & Ports) + match if one of the conditions is met. The conditions should be the + following combination: (Hostname & Ports) - EXAMPLES: Hostname - (".example.com"), ("xyz.example.com") Hostname - and Ports - ("example.com" and "22"), ("example.com" and "22,33") - etc. + EXAMPLES: Hostname and Ports - (".example.com", "443"), + ("example.com" and "22"), ("example.com" and "22,33") etc. hostname Hostname of the application. @@ -195,7 +206,7 @@ FLAGS At most one of these can be specified: - --upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK] + --upstreams=[egressPolicy=EGRESSPOLICY],[external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL] Set upstreams to new value. Which upstream resources to forward traffic to. @@ -205,6 +216,18 @@ FLAGS regions List of the regions where the application sends traffic. + external + List of the external endpoints to forward traffic to. + + endpoints + List of the endpoints to forward traffic to. + + hostname + Hostname of the endpoint. + + port + Port of the endpoint. + network Network to forward traffic to. @@ -212,19 +235,69 @@ FLAGS Network name is of the format: projects/{project}/global/networks/{network}. + proxyProtocol + Enables proxy protocol configuration for the upstream. + + allowedClientHeaders + List of the allowed client header names. + + clientIp + Client IP configuration. The client IP address is included if + true. + + contextualHeaders + Configuration for the contextual headers. + + deviceInfo + Device info configuration. + + outputType + The output type of the delegated device info. + + groupInfo + Group info configuration. + + outputType + The output type of the delegated group info. + + outputType + Default output type for all enabled headers. + + userInfo + User info configuration. + + outputType + The output type of the delegated user info. + + gatewayIdentity + Gateway identity configuration. + + metadataHeaders + Custom resource specific headers along with the values. The + names should conform to RFC 9110: > Field names SHOULD + constrain themselves to alphanumeric characters, "-", and + ".", and SHOULD begin with a letter. Field values SHOULD + contain only ASCII printable characters and tab. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + Shorthand Example: - --upstreams=egressPolicy={regions=[string]},network={name=string} --upstreams=egressPolicy={regions=[string]},network={name=string} + --upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} --upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} JSON Example: - --upstreams='[{"egressPolicy": {"regions": ["string"]}, "network": {"name": "string"}}]' + --upstreams='[{"egressPolicy": {"regions": ["string"]}, "external": {"endpoints": [{"hostname": "string", "port": int}]}, "network": {"name": "string"}, "proxyProtocol": {"allowedClientHeaders": ["string"], "clientIp": boolean, "contextualHeaders": {"deviceInfo": {"outputType": "string"}, "groupInfo": {"outputType": "string"}, "outputType": "string", "userInfo": {"outputType": "string"}}, "gatewayIdentity": "string", "metadataHeaders": {"string": "string"}}}]' File Example: --upstreams=path_to_file.(yaml|json) - --add-upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK] + --add-upstreams=[egressPolicy=EGRESSPOLICY],[external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL] Add new value to upstreams list. Which upstream resources to forward traffic to. @@ -234,6 +307,18 @@ FLAGS regions List of the regions where the application sends traffic. + external + List of the external endpoints to forward traffic to. + + endpoints + List of the endpoints to forward traffic to. + + hostname + Hostname of the endpoint. + + port + Port of the endpoint. + network Network to forward traffic to. @@ -241,13 +326,63 @@ FLAGS Network name is of the format: projects/{project}/global/networks/{network}. + proxyProtocol + Enables proxy protocol configuration for the upstream. + + allowedClientHeaders + List of the allowed client header names. + + clientIp + Client IP configuration. The client IP address is included if + true. + + contextualHeaders + Configuration for the contextual headers. + + deviceInfo + Device info configuration. + + outputType + The output type of the delegated device info. + + groupInfo + Group info configuration. + + outputType + The output type of the delegated group info. + + outputType + Default output type for all enabled headers. + + userInfo + User info configuration. + + outputType + The output type of the delegated user info. + + gatewayIdentity + Gateway identity configuration. + + metadataHeaders + Custom resource specific headers along with the values. The + names should conform to RFC 9110: > Field names SHOULD + constrain themselves to alphanumeric characters, "-", and + ".", and SHOULD begin with a letter. Field values SHOULD + contain only ASCII printable characters and tab. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + Shorthand Example: - --add-upstreams=egressPolicy={regions=[string]},network={name=string} --add-upstreams=egressPolicy={regions=[string]},network={name=string} + --add-upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} --add-upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} JSON Example: - --add-upstreams='[{"egressPolicy": {"regions": ["string"]}, "network": {"name": "string"}}]' + --add-upstreams='[{"egressPolicy": {"regions": ["string"]}, "external": {"endpoints": [{"hostname": "string", "port": int}]}, "network": {"name": "string"}, "proxyProtocol": {"allowedClientHeaders": ["string"], "clientIp": boolean, "contextualHeaders": {"deviceInfo": {"outputType": "string"}, "groupInfo": {"outputType": "string"}, "outputType": "string", "userInfo": {"outputType": "string"}}, "gatewayIdentity": "string", "metadataHeaders": {"string": "string"}}}]' File Example: @@ -258,7 +393,7 @@ FLAGS --clear-upstreams Clear upstreams value and set to empty list. - --remove-upstreams=[egressPolicy=EGRESSPOLICY],[network=NETWORK] + --remove-upstreams=[egressPolicy=EGRESSPOLICY],[external=EXTERNAL],[network=NETWORK],[proxyProtocol=PROXYPROTOCOL] Remove existing value from upstreams list. Which upstream resources to forward traffic to. @@ -268,6 +403,18 @@ FLAGS regions List of the regions where the application sends traffic. + external + List of the external endpoints to forward traffic to. + + endpoints + List of the endpoints to forward traffic to. + + hostname + Hostname of the endpoint. + + port + Port of the endpoint. + network Network to forward traffic to. @@ -275,13 +422,63 @@ FLAGS Network name is of the format: projects/{project}/global/networks/{network}. + proxyProtocol + Enables proxy protocol configuration for the upstream. + + allowedClientHeaders + List of the allowed client header names. + + clientIp + Client IP configuration. The client IP address is included + if true. + + contextualHeaders + Configuration for the contextual headers. + + deviceInfo + Device info configuration. + + outputType + The output type of the delegated device info. + + groupInfo + Group info configuration. + + outputType + The output type of the delegated group info. + + outputType + Default output type for all enabled headers. + + userInfo + User info configuration. + + outputType + The output type of the delegated user info. + + gatewayIdentity + Gateway identity configuration. + + metadataHeaders + Custom resource specific headers along with the values. The + names should conform to RFC 9110: > Field names SHOULD + constrain themselves to alphanumeric characters, "-", and + ".", and SHOULD begin with a letter. Field values SHOULD + contain only ASCII printable characters and tab. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + Shorthand Example: - --remove-upstreams=egressPolicy={regions=[string]},network={name=string} --remove-upstreams=egressPolicy={regions=[string]},network={name=string} + --remove-upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} --remove-upstreams=egressPolicy={regions=[string]},external={endpoints=[{hostname=string,port=int}]},network={name=string},proxyProtocol={allowedClientHeaders=[string],clientIp=boolean,contextualHeaders={deviceInfo={outputType=string},groupInfo={outputType=string},outputType=string,userInfo={outputType=string}},gatewayIdentity=string,metadataHeaders={string=string}} JSON Example: - --remove-upstreams='[{"egressPolicy": {"regions": ["string"]}, "network": {"name": "string"}}]' + --remove-upstreams='[{"egressPolicy": {"regions": ["string"]}, "external": {"endpoints": [{"hostname": "string", "port": int}]}, "network": {"name": "string"}, "proxyProtocol": {"allowedClientHeaders": ["string"], "clientIp": boolean, "contextualHeaders": {"deviceInfo": {"outputType": "string"}, "groupInfo": {"outputType": "string"}, "outputType": "string", "userInfo": {"outputType": "string"}}, "gatewayIdentity": "string", "metadataHeaders": {"string": "string"}}}]' File Example: diff --git a/gcloud/beta/beyondcorp/security-gateways/create b/gcloud/beta/beyondcorp/security-gateways/create index a2cd3f0e3..f41f17041 100644 --- a/gcloud/beta/beyondcorp/security-gateways/create +++ b/gcloud/beta/beyondcorp/security-gateways/create @@ -5,7 +5,15 @@ SYNOPSIS gcloud beta beyondcorp security-gateways create (SECURITY_GATEWAY : --location=LOCATION) [--async] [--display-name=DISPLAY_NAME] [--hubs=[HUBS,...]] - [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + [--request-id=REQUEST_ID] + [--resource-override-path=RESOURCE_OVERRIDE_PATH] + [--proxy-protocol-config-allowed-client-headers=[PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS, + ...] --proxy-protocol-config-client-ip + --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY --proxy-protocol-config-metadata-headers=[PROXY_PROTOCOL_CONFIG_METADATA_HEADERS, + ...] --contextual-headers-output-type=CONTEXTUAL_HEADERS_OUTPUT_TYPE + --device-info-output-type=DEVICE_INFO_OUTPUT_TYPE + --group-info-output-type=GROUP_INFO_OUTPUT_TYPE + --user-info-output-type=USER_INFO_OUTPUT_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a securityGateway @@ -82,9 +90,116 @@ FLAGS --request-id=REQUEST_ID An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to - ignore request if it has already been completed. The server will + ignore the request if it has already been completed. The server will guarantee that for at least 60 minutes since the first request. + Settings related to the Service Discovery. + + If Service Discovery is done through API, defines its settings. + + This must be specified. + + API operation descriptor. + + This must be specified. + + --resource-override-path=RESOURCE_OVERRIDE_PATH + Contains uri path fragment where HTTP request is sent. + + The configuration for the proxy. + + --proxy-protocol-config-allowed-client-headers=[PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS,...] + List of the allowed client header names. + + --proxy-protocol-config-client-ip + Client IP configuration. The client IP address is included if true. + + --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY + Gateway identity configuration. + PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY must be (only one value is + supported): + + resource-name + Resource name for gateway identity, in the format: + projects/{project_id}/locations/{location_id}/securityGateways/{security_gateway_id} + + --proxy-protocol-config-metadata-headers=[PROXY_PROTOCOL_CONFIG_METADATA_HEADERS,...] + Custom resource specific headers along with the values. The names + should conform to RFC 9110: > Field names SHOULD constrain themselves + to alphanumeric characters, "-", and ".", and SHOULD begin with a + letter. Field values SHOULD contain only ASCII printable characters + and tab. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --proxy-protocol-config-metadata-headers=string=string + + JSON Example: + + --proxy-protocol-config-metadata-headers='{"string": "string"}' + + File Example: + + --proxy-protocol-config-metadata-headers=path_to_file.(yaml|json) + + Contextual headers configuration. + + --contextual-headers-output-type=CONTEXTUAL_HEADERS_OUTPUT_TYPE + Default output type for all enabled headers. + CONTEXTUAL_HEADERS_OUTPUT_TYPE must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + Delegated device info configuration. + + --device-info-output-type=DEVICE_INFO_OUTPUT_TYPE + The output type of the delegated device info. + DEVICE_INFO_OUTPUT_TYPE must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + Delegated group info configuration. + + --group-info-output-type=GROUP_INFO_OUTPUT_TYPE + The output type of the delegated group info. + GROUP_INFO_OUTPUT_TYPE must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + Delegated user info configuration. + + --user-info-output-type=USER_INFO_OUTPUT_TYPE + The output type of the delegated user info. USER_INFO_OUTPUT_TYPE + must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + 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/beyondcorp/security-gateways/update b/gcloud/beta/beyondcorp/security-gateways/update index 4a7039feb..76b2bd7e7 100644 --- a/gcloud/beta/beyondcorp/security-gateways/update +++ b/gcloud/beta/beyondcorp/security-gateways/update @@ -5,6 +5,20 @@ SYNOPSIS gcloud beta beyondcorp security-gateways update (SECURITY_GATEWAY : --location=LOCATION) [--async] [--display-name=DISPLAY_NAME] [--request-id=REQUEST_ID] + [--clear-proxy-protocol-config --[no-]proxy-protocol-config-client-ip + --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY --contextual-headers-output-type=CONTEXTUAL_HEADERS_OUTPUT_TYPE --device-info-output-type=DEVICE_INFO_OUTPUT_TYPE --group-info-output-type=GROUP_INFO_OUTPUT_TYPE --user-info-output-type=USER_INFO_OUTPUT_TYPE --proxy-protocol-config-allowed-client-headers=[PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS, + ...] + | --add-proxy-protocol-config-allowed-client-headers=[ADD_PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS, + ...] --clear-proxy-protocol-config-allowed-client-headers + | --remove-proxy-protocol-config-allowed-client-headers=[REMOVE_PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS, + ...] + --proxy-protocol-config-metadata-headers=[PROXY_PROTOCOL_CONFIG_METADATA_HEADERS, + ...] + | --update-proxy-protocol-config-metadata-headers=[UPDATE_PROXY_PROTOCOL_CONFIG_METADATA_HEADERS, + ...] --clear-proxy-protocol-config-metadata-headers + | --remove-proxy-protocol-config-metadata-headers=REMOVE_PROXY_PROTOCOL_CONFIG_METADATA_HEADERS] + [--clear-service-discovery + --resource-override-path=RESOURCE_OVERRIDE_PATH] [--hubs=[HUBS,...] | --update-hubs=[UPDATE_HUBS,...] --clear-hubs | --remove-hubs=REMOVE_HUBS] [GCLOUD_WIDE_FLAG ...] @@ -73,6 +87,192 @@ FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). + The configuration for the proxy. + + --clear-proxy-protocol-config + Set + googleCloudBeyondcorpSecuritygatewaysV1SecurityGateway.proxyProtocolConfig + back to default value. + + --[no-]proxy-protocol-config-client-ip + Client IP configuration. The client IP address is included if true. + Use --proxy-protocol-config-client-ip to enable and + --no-proxy-protocol-config-client-ip to disable. + + --proxy-protocol-config-gateway-identity=PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY + Gateway identity configuration. + PROXY_PROTOCOL_CONFIG_GATEWAY_IDENTITY must be (only one value is + supported): + + resource-name + Resource name for gateway identity, in the format: + projects/{project_id}/locations/{location_id}/securityGateways/{security_gateway_id} + + Contextual headers configuration. + + --contextual-headers-output-type=CONTEXTUAL_HEADERS_OUTPUT_TYPE + Default output type for all enabled headers. + CONTEXTUAL_HEADERS_OUTPUT_TYPE must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + Delegated device info configuration. + + --device-info-output-type=DEVICE_INFO_OUTPUT_TYPE + The output type of the delegated device info. + DEVICE_INFO_OUTPUT_TYPE must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + Delegated group info configuration. + + --group-info-output-type=GROUP_INFO_OUTPUT_TYPE + The output type of the delegated group info. + GROUP_INFO_OUTPUT_TYPE must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + Delegated user info configuration. + + --user-info-output-type=USER_INFO_OUTPUT_TYPE + The output type of the delegated user info. USER_INFO_OUTPUT_TYPE + must be one of: + + json + JSON output type. + none + Explicitly disable header output. + protobuf + Protobuf output type. + + Update proxy_protocol_config_allowed_client_headers. + + At most one of these can be specified: + + --proxy-protocol-config-allowed-client-headers=[PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS,...] + Set proxy_protocol_config_allowed_client_headers to new value. + + --add-proxy-protocol-config-allowed-client-headers=[ADD_PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS,...] + Add new value to proxy_protocol_config_allowed_client_headers list. + + At most one of these can be specified: + + --clear-proxy-protocol-config-allowed-client-headers + Clear proxy_protocol_config_allowed_client_headers value and set + to empty list. + + --remove-proxy-protocol-config-allowed-client-headers=[REMOVE_PROXY_PROTOCOL_CONFIG_ALLOWED_CLIENT_HEADERS,...] + Remove existing value from + proxy_protocol_config_allowed_client_headers list. + + Update proxy_protocol_config_metadata_headers. + + At most one of these can be specified: + + --proxy-protocol-config-metadata-headers=[PROXY_PROTOCOL_CONFIG_METADATA_HEADERS,...] + Set proxy_protocol_config_metadata_headers to new value. Custom + resource specific headers along with the values. The names should + conform to RFC 9110: > Field names SHOULD constrain themselves to + alphanumeric characters, "-", and ".", and SHOULD begin with a + letter. Field values SHOULD contain only ASCII printable characters + and tab. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --proxy-protocol-config-metadata-headers=string=string + + JSON Example: + + --proxy-protocol-config-metadata-headers='{"string": "string"}' + + File Example: + + --proxy-protocol-config-metadata-headers=path_to_file.(yaml|json) + + --update-proxy-protocol-config-metadata-headers=[UPDATE_PROXY_PROTOCOL_CONFIG_METADATA_HEADERS,...] + Update proxy_protocol_config_metadata_headers value or add key + value pair. Custom resource specific headers along with the values. + The names should conform to RFC 9110: > Field names SHOULD + constrain themselves to alphanumeric characters, "-", and ".", and + SHOULD begin with a letter. Field values SHOULD contain only ASCII + printable characters and tab. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --update-proxy-protocol-config-metadata-headers=string=string + + JSON Example: + + --update-proxy-protocol-config-metadata-headers='{"string": "string"}' + + File Example: + + --update-proxy-protocol-config-metadata-headers=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-proxy-protocol-config-metadata-headers + Clear proxy_protocol_config_metadata_headers value and set to + empty map. + + --remove-proxy-protocol-config-metadata-headers=REMOVE_PROXY_PROTOCOL_CONFIG_METADATA_HEADERS + Remove existing value from map + proxy_protocol_config_metadata_headers. Sets + remove_proxy_protocol_config_metadata_headers value. + + Shorthand Example: + + --remove-proxy-protocol-config-metadata-headers=string,string + + JSON Example: + + --remove-proxy-protocol-config-metadata-headers=["string"] + + File Example: + + --remove-proxy-protocol-config-metadata-headers=path_to_file.(yaml|json) + + Settings related to the Service Discovery. + + --clear-service-discovery + Set + googleCloudBeyondcorpSecuritygatewaysV1SecurityGateway.serviceDiscovery + back to default value. + + If Service Discovery is done through API, defines its settings. + + API operation descriptor. + + --resource-override-path=RESOURCE_OVERRIDE_PATH + Contains uri path fragment where HTTP request is sent. + Update hubs. At most one of these can be specified: diff --git a/gcloud/beta/bigtable/logical-views/update b/gcloud/beta/bigtable/logical-views/update index b2cfc0a1a..b4d197f11 100644 --- a/gcloud/beta/bigtable/logical-views/update +++ b/gcloud/beta/bigtable/logical-views/update @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud beta bigtable logical-views update - (LOGICAL_VIEW : --instance=INSTANCE) --query=QUERY [--async] - [--deletion-protection=DELETION_PROTECTION] [GCLOUD_WIDE_FLAG ...] + (LOGICAL_VIEW : --instance=INSTANCE) + (--deletion-protection=DELETION_PROTECTION --query=QUERY) [--async] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a Bigtable logical view. @@ -16,6 +17,11 @@ EXAMPLES --instance=my-instance-id \ --query="SELECT my-column-family2 FROM my-table" + To enable deletion protection on a logical view, run: + + $ gcloud beta bigtable logical-views update my-logical-view-id \ + --instance=my-instance-id --deletion-protection + POSITIONAL ARGUMENTS Logical view resource - The logical view to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -49,17 +55,19 @@ POSITIONAL ARGUMENTS ▸ provide the argument --instance on the command line. REQUIRED FLAGS - --query=QUERY - The query of the view. + At least one of these must be specified: + + --deletion-protection=DELETION_PROTECTION + Whether the view is protected from deletion. + + --query=QUERY + The query of the view. OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to complete. - --deletion-protection=DELETION_PROTECTION - Whether the view is protected from deletion. - 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-templates/create b/gcloud/beta/compute/instance-templates/create index 0d935731d..757a4ac6d 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -774,7 +774,7 @@ FLAGS to. Mutually exclusive with --network and --subnet flags. vlan - VLAN tag of a dynamic network interface, must be an integer in the + VLAN ID of a Dynamic Network Interface, must be an integer in the range from 2 to 255 inclusively. --network-performance-configs=[PROPERTY=VALUE,...] diff --git a/gcloud/beta/compute/instance-templates/create-with-container b/gcloud/beta/compute/instance-templates/create-with-container index f32063e58..a144c7297 100644 --- a/gcloud/beta/compute/instance-templates/create-with-container +++ b/gcloud/beta/compute/instance-templates/create-with-container @@ -673,6 +673,10 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + vlan + VLAN ID of a Dynamic Network Interface, must be an integer in the + range from 2 to 255 inclusively. + --network-tier=NETWORK_TIER Specifies the network tier that will be used to configure the instance. NETWORK_TIER must be one of: PREMIUM, STANDARD. The default value is diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 907b591bb..6be138672 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -843,7 +843,7 @@ FLAGS to. Mutually exclusive with --network and --subnet flags. vlan - VLAN tag of a dynamic network interface, must be an integer in the + VLAN ID of a Dynamic Network Interface, must be an integer in the range from 2 to 255 inclusively. igmp-query diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index f31aa849c..0ddadbebf 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -776,6 +776,10 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + vlan + VLAN ID of a Dynamic Network Interface, must be an integer in the + range from 2 to 255 inclusively. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/beta/compute/instances/network-interfaces/add b/gcloud/beta/compute/instances/network-interfaces/add index c74a4c99e..76bfa11b1 100644 --- a/gcloud/beta/compute/instances/network-interfaces/add +++ b/gcloud/beta/compute/instances/network-interfaces/add @@ -1,6 +1,6 @@ NAME - gcloud beta compute instances network-interfaces add - add a dynamic - network interface to a Compute Engine instance + gcloud beta compute instances network-interfaces add - add a Dynamic + Network Interface to a Compute Engine instance SYNOPSIS gcloud beta compute instances network-interfaces add INSTANCE_NAME @@ -16,12 +16,13 @@ SYNOPSIS [--address=ADDRESS | --no-address] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) gcloud beta compute instances network-interfaces add adds a dynamic - network interface to a Compute Engine instance. For example: + (BETA) gcloud beta compute instances network-interfaces add adds a Dynamic + Network Interface to a Compute Engine instance. - $ gcloud beta compute instances network-interfaces add \ - instance-name --parent-nic-name nic1 --vlan 2 - --network network-1 --subnetwork subnetwork-1 +EXAMPLES + To add a Dynamic Network Interface to a Compute Engine instance, run: $ gcloud beta compute instances network-interfaces add \ + instance-name --parent-nic-name=nic1 --vlan=2 \ + --network=network-1 --subnetwork=subnetwork-1 POSITIONAL ARGUMENTS INSTANCE_NAME @@ -173,8 +174,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 instances network-interfaces add $ gcloud alpha compute instances network-interfaces add diff --git a/gcloud/beta/compute/instances/network-interfaces/delete b/gcloud/beta/compute/instances/network-interfaces/delete index 18be0c685..e4b1ec097 100644 --- a/gcloud/beta/compute/instances/network-interfaces/delete +++ b/gcloud/beta/compute/instances/network-interfaces/delete @@ -1,6 +1,6 @@ NAME - gcloud beta compute instances network-interfaces delete - delete a dynamic - network interface from a Compute Engine instance + gcloud beta compute instances network-interfaces delete - delete a Dynamic + Network Interface from a Compute Engine instance SYNOPSIS gcloud beta compute instances network-interfaces delete INSTANCE_NAME @@ -9,10 +9,11 @@ SYNOPSIS DESCRIPTION (BETA) gcloud beta compute instances network-interfaces delete deletes a - dynamic network interface from a Compute Engine instance. For example: + Dynamic Network Interface from a Compute Engine instance. - $ gcloud beta compute instances network-interfaces delete \ - instance-name --network-interface nic1.2 +EXAMPLES + To delete a Dynamic Network Interface from a Compute Engine instance, run: $ gcloud beta compute instances network-interfaces delete \ + instance-name --network-interface=nic1.2 POSITIONAL ARGUMENTS INSTANCE_NAME @@ -58,8 +59,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 instances network-interfaces delete $ gcloud alpha compute instances network-interfaces delete diff --git a/gcloud/beta/compute/instances/network-interfaces/help b/gcloud/beta/compute/instances/network-interfaces/help index c88020061..e3070fd56 100644 --- a/gcloud/beta/compute/instances/network-interfaces/help +++ b/gcloud/beta/compute/instances/network-interfaces/help @@ -25,10 +25,10 @@ COMMANDS COMMAND is one of the following: add - (BETA) Add a dynamic network interface to a Compute Engine instance. + (BETA) Add a Dynamic Network Interface to a Compute Engine instance. delete - (BETA) Delete a dynamic network interface from a Compute Engine + (BETA) Delete a Dynamic Network Interface from a Compute Engine instance. get-effective-firewalls diff --git a/gcloud/beta/compute/networks/subnets/describe b/gcloud/beta/compute/networks/subnets/describe index 6860623eb..e2c9043a9 100644 --- a/gcloud/beta/compute/networks/subnets/describe +++ b/gcloud/beta/compute/networks/subnets/describe @@ -41,12 +41,13 @@ FLAGS CLOUDSDK_COMPUTE_REGION. --view=VIEW - Specifies the information that the output should contain. VIEW must be - (only one value is supported): + Specifies the information to include in the output. VIEW must be (only + one value is supported): WITH_UTILIZATION - Output includes the IP utilization data of all subnetwork ranges, - showing total allocated and free IPv4 and IPv6 IPs. + Output includes the IP address utilization data of all subnetwork + ranges, showing total allocated and free IPv4 and IPv6 IP + addresses. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/compute/networks/subnets/list b/gcloud/beta/compute/networks/subnets/list index 102b27f26..ce466015e 100644 --- a/gcloud/beta/compute/networks/subnets/list +++ b/gcloud/beta/compute/networks/subnets/list @@ -53,12 +53,13 @@ FLAGS If provided, only resources from the given regions are queried. --view=VIEW - Specifies the information that the output should contain. VIEW must be - (only one value is supported): + Specifies the information to include in the output. VIEW must be (only + one value is supported): WITH_UTILIZATION - Output includes the IP utilization data of all subnetwork ranges, - showing total allocated and free IPv4 and IPv6 IPs. + Output includes the IP address utilization data of all subnetwork + ranges, showing total allocated and free IPv4 and IPv6 IP + addresses. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/compute/reservations/update b/gcloud/beta/compute/reservations/update index f2b81da02..4b5cac614 100644 --- a/gcloud/beta/compute/reservations/update +++ b/gcloud/beta/compute/reservations/update @@ -8,7 +8,7 @@ SYNOPSIS [--[no-]enable-emergent-maintenance] [--remove-share-with=PROJECT,[PROJECT,...]] [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] - [--share-setting=SHARE_SETTING] + [--scheduling-type=SCHEDULING_TYPE] [--share-setting=SHARE_SETTING] [--share-with=SHARE_WITH,[SHARE_WITH,...]] [--vm-count=VM_COUNT] [--zone=ZONE] [--delete-after-duration=DELETE_AFTER_DURATION @@ -78,6 +78,16 @@ FLAGS The reservation won't be shared with Google Cloud services. If you omit this flag during creation, the default value is DISALLOW_ALL. + --scheduling-type=SCHEDULING_TYPE + How Compute Engine schedules maintenance events for your reserved + hosts. SCHEDULING_TYPE must be one of: + + GROUPED + In GROUPED mode, maintenance is synchronized across all your VMs. + INDEPENDENT + In INDEPENDENT mode, your VMs have different, unsynchronized + maintenance schedules. + --share-setting=SHARE_SETTING The projects that can use the reservation. SHARE_SETTING must be one of: diff --git a/gcloud/beta/compute/tpus/execution-groups/create b/gcloud/beta/compute/tpus/execution-groups/create index 2e3cf8d48..94174a690 100644 --- a/gcloud/beta/compute/tpus/execution-groups/create +++ b/gcloud/beta/compute/tpus/execution-groups/create @@ -13,6 +13,14 @@ SYNOPSIS [--use-dl-images] [--use-with-notebook] [--vm-only] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (BETA) (DEPRECATED) Create Google Compute TPUs along with VMs. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To create both TPU and VM, run: diff --git a/gcloud/beta/compute/tpus/execution-groups/delete b/gcloud/beta/compute/tpus/execution-groups/delete index 9ae3b8424..d56869fb5 100644 --- a/gcloud/beta/compute/tpus/execution-groups/delete +++ b/gcloud/beta/compute/tpus/execution-groups/delete @@ -6,6 +6,14 @@ SYNOPSIS gcloud beta compute tpus execution-groups delete EXECUTION_GROUP_NAME [--tpu-only] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (BETA) (DEPRECATED) Delete TPU Node + VM created by execution group. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To delete both, the TPU and the VM, run: diff --git a/gcloud/beta/compute/tpus/execution-groups/describe b/gcloud/beta/compute/tpus/execution-groups/describe index 9c4328295..758dcb5ae 100644 --- a/gcloud/beta/compute/tpus/execution-groups/describe +++ b/gcloud/beta/compute/tpus/execution-groups/describe @@ -6,6 +6,14 @@ SYNOPSIS gcloud beta compute tpus execution-groups describe EXECUTION_GROUP_NAME [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (BETA) (DEPRECATED) Describe Google Compute TPU + VM combination. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To describe the TPU and VM combination, run: diff --git a/gcloud/beta/compute/tpus/execution-groups/help b/gcloud/beta/compute/tpus/execution-groups/help index 2a2b15ce6..892996e21 100644 --- a/gcloud/beta/compute/tpus/execution-groups/help +++ b/gcloud/beta/compute/tpus/execution-groups/help @@ -6,8 +6,13 @@ SYNOPSIS gcloud beta compute tpus execution-groups COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Command group that helps create and manage Cloud TPUs and Compute - VMs. + (BETA) (DEPRECATED) Command group that helps create and manage Cloud TPUs + and Compute VMs. + + This command group is deprecated and will be removed in a future release. + We recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -18,22 +23,22 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create Google Compute TPUs along with VMs. + (BETA) (DEPRECATED) Create Google Compute TPUs along with VMs. delete - (BETA) Delete TPU Node + VM created by execution group. + (BETA) (DEPRECATED) Delete TPU Node + VM created by execution group. describe - (BETA) Describe Google Compute TPU + VM combination. + (BETA) (DEPRECATED) Describe Google Compute TPU + VM combination. list - (BETA) List TPU Node+VM groups created by execution group. + (BETA) (DEPRECATED) List TPU Node+VM groups created by execution group. resume - (BETA) Creates Google Compute TPU and resumes the VM. + (BETA) (DEPRECATED) Creates Google Compute TPU and resumes the VM. suspend - (BETA) Deletes Google Compute TPU and suspends the VM. + (BETA) (DEPRECATED) Deletes Google Compute TPU and suspends the VM. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/compute/tpus/execution-groups/list b/gcloud/beta/compute/tpus/execution-groups/list index 268bc84bb..2f0e0c3cf 100644 --- a/gcloud/beta/compute/tpus/execution-groups/list +++ b/gcloud/beta/compute/tpus/execution-groups/list @@ -7,6 +7,14 @@ SYNOPSIS [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (BETA) (DEPRECATED) List TPU Node+VM groups created by execution group. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To list all active execution groups, run: diff --git a/gcloud/beta/compute/tpus/execution-groups/resume b/gcloud/beta/compute/tpus/execution-groups/resume index fd07439cf..6086224c1 100644 --- a/gcloud/beta/compute/tpus/execution-groups/resume +++ b/gcloud/beta/compute/tpus/execution-groups/resume @@ -9,6 +9,14 @@ SYNOPSIS [--tf-version=TF_VERSION] [--vm-only] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (BETA) (DEPRECATED) Creates Google Compute TPU and resumes the VM. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To resume a suspended TPU VM combination, run: diff --git a/gcloud/beta/compute/tpus/execution-groups/suspend b/gcloud/beta/compute/tpus/execution-groups/suspend index 847463f4b..df4779c5c 100644 --- a/gcloud/beta/compute/tpus/execution-groups/suspend +++ b/gcloud/beta/compute/tpus/execution-groups/suspend @@ -6,6 +6,14 @@ SYNOPSIS gcloud beta compute tpus execution-groups suspend EXECUTION_GROUP_NAME [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (BETA) (DEPRECATED) Deletes Google Compute TPU and suspends the VM. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To delete the TPU and suspend the VM, run: diff --git a/gcloud/beta/compute/tpus/help b/gcloud/beta/compute/tpus/help index 32fc4ad4c..3d05a12c5 100644 --- a/gcloud/beta/compute/tpus/help +++ b/gcloud/beta/compute/tpus/help @@ -25,8 +25,8 @@ GROUPS (BETA) List or Describe Available Cloud TPU accelerator types. execution-groups - (BETA) Command group that helps create and manage Cloud TPUs and - Compute VMs. + (BETA) (DEPRECATED) Command group that helps create and manage Cloud + TPUs and Compute VMs. locations (BETA) List or Describe Available Cloud TPU Locations. diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 3c6db2e28..d78a3ef20 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -110,13 +110,11 @@ SYNOPSIS | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] [--disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics] - [[--enable-autoprovisioning - : --autoprovisioning-config-file=PATH_TO_FILE - | [--max-cpu=MAX_CPU --max-memory=MAX_MEMORY - : --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE + [--enable-autoprovisioning --autoprovisioning-config-file=PATH_TO_FILE + | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE --autoprovisioning-locations=ZONE,[ZONE,...] - --autoprovisioning-min-cpu-platform=PLATFORM --min-cpu=MIN_CPU - --min-memory=MIN_MEMORY + --autoprovisioning-min-cpu-platform=PLATFORM --max-cpu=MAX_CPU + --max-memory=MAX_MEMORY --min-cpu=MIN_CPU --min-memory=MIN_MEMORY --autoprovisioning-max-surge-upgrade=AUTOPROVISIONING_MAX_SURGE_UPGRADE --autoprovisioning-max-unavailable-upgrade=AUTOPROVISIONING_MAX_UNAVAILABLE_UPGRADE --autoprovisioning-node-pool-soak-duration=AUTOPROVISIONING_NODE_POOL_SOAK_DURATION --autoprovisioning-standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, batch-soak-duration=BATCH_SOAK_DURATION,...] @@ -127,7 +125,7 @@ SYNOPSIS --enable-autoprovisioning-autorepair --enable-autoprovisioning-autoupgrade [--max-accelerator=[type=TYPE,count=COUNT,...] - : --min-accelerator=[type=TYPE,count=COUNT,...]]]]] + : --min-accelerator=[type=TYPE,count=COUNT,...]]] [--enable-autoscaling --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES --min-nodes=MIN_NODES --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] @@ -1405,7 +1403,9 @@ FLAGS cpuManagerPolicy either 'static' or 'none' cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') + cpuCFSQuotaPeriod interval (e.g., '100ms'. The + value must be between 1ms and 1 + second, inclusive.) memoryManager specify memory manager policy topologyManager specify topology manager policy and scope @@ -1415,7 +1415,7 @@ FLAGS containerLogMaxSize positive number plus unit suffix (e.g., '100Mi', '0.2Gi'. The value must be between 10Mi and - 500Mi.) + 500Mi, inclusive.) containerLogMaxFiles integer (The value must be between [2, 10].) imageGcLowThresholdPercent integer (The value must be @@ -2032,9 +2032,6 @@ FLAGS Cluster Autoscaler will be able to create new node pools. Requires maximum CPU and memory limits to be specified. - This flag argument must be specified if any of the other arguments in - this group are specified. - At most one of these can be specified: --autoprovisioning-config-file=PATH_TO_FILE @@ -2112,23 +2109,6 @@ FLAGS Flags to configure autoprovisioned nodes - --max-cpu=MAX_CPU - Maximum number of cores in the cluster. - - Maximum number of cores to which the cluster can scale. - - This flag argument must be specified if any of the other - arguments in this group are specified. - - --max-memory=MAX_MEMORY - Maximum memory in the cluster. - - Maximum number of gigabytes of memory to which the cluster can - scale. - - This flag argument must be specified if any of the other - arguments in this group are specified. - --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE Node Autoprovisioning will create new nodes with the specified image type @@ -2147,6 +2127,17 @@ FLAGS will be removed in an upcoming release. More info: https://cloud.google.com/kubernetes-engine/docs/release-notes#March_08_2022 + --max-cpu=MAX_CPU + Maximum number of cores in the cluster. + + Maximum number of cores to which the cluster can scale. + + --max-memory=MAX_MEMORY + Maximum memory in the cluster. + + Maximum number of gigabytes of memory to which the cluster can + scale. + --min-cpu=MIN_CPU Minimum number of cores in the cluster. diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index d4c125511..6818038f9 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -94,8 +94,8 @@ SYNOPSIS --enable-master-global-access --enable-private-endpoint --enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...] - | [--enable-autoprovisioning - : --autoprovisioning-config-file=PATH_TO_FILE + | --enable-autoprovisioning + --autoprovisioning-config-file=PATH_TO_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE --autoprovisioning-locations=ZONE,[ZONE,...] --autoprovisioning-min-cpu-platform=PLATFORM --max-cpu=MAX_CPU @@ -110,7 +110,7 @@ SYNOPSIS --enable-autoprovisioning-autorepair --enable-autoprovisioning-autoupgrade [--max-accelerator=[type=TYPE,count=COUNT,...] - : --min-accelerator=[type=TYPE,count=COUNT,...]]] + : --min-accelerator=[type=TYPE,count=COUNT,...]] | --enable-insecure-binding-system-authenticated --enable-insecure-binding-system-unauthenticated | --logging-service=LOGGING_SERVICE @@ -1344,9 +1344,6 @@ REQUIRED FLAGS Cluster Autoscaler will be able to create new node pools. Requires maximum CPU and memory limits to be specified. - This flag argument must be specified if any of the other arguments - in this group are specified. - At most one of these can be specified: --autoprovisioning-config-file=PATH_TO_FILE diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 634d76d6d..9e0702e0f 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -788,7 +788,9 @@ FLAGS cpuManagerPolicy either 'static' or 'none' cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') + cpuCFSQuotaPeriod interval (e.g., '100ms'. The + value must be between 1ms and 1 + second, inclusive.) memoryManager specify memory manager policy topologyManager specify topology manager policy and scope @@ -798,7 +800,7 @@ FLAGS containerLogMaxSize positive number plus unit suffix (e.g., '100Mi', '0.2Gi'. The value must be between 10Mi and - 500Mi.) + 500Mi, inclusive.) containerLogMaxFiles integer (The value must be between [2, 10].) imageGcLowThresholdPercent integer (The value must be diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index b90c603fd..26fd868ba 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -318,7 +318,9 @@ REQUIRED FLAGS cpuManagerPolicy either 'static' or 'none' cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') + cpuCFSQuotaPeriod interval (e.g., '100ms'. The + value must be between 1ms and + 1 second, inclusive.) memoryManager specify memory manager policy topologyManager specify topology manager policy and scope @@ -328,7 +330,8 @@ REQUIRED FLAGS containerLogMaxSize positive number plus unit suffix (e.g., '100Mi', '0.2Gi'. The value must be - between 10Mi and 500Mi.) + between 10Mi and 500Mi, + inclusive.) containerLogMaxFiles integer (The value must be between [2, 10].) imageGcLowThresholdPercent integer (The value must be diff --git a/gcloud/beta/iap/oauth-brands/create b/gcloud/beta/iap/oauth-brands/create index 38b14430a..7e10914ce 100644 --- a/gcloud/beta/iap/oauth-brands/create +++ b/gcloud/beta/iap/oauth-brands/create @@ -7,7 +7,11 @@ SYNOPSIS --support_email=SUPPORT_EMAIL [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. + (BETA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud beta iap oauth-brands create is used to create a Cloud OAuth brand for the project. The brand is 'internal only', meaning OAuth clients diff --git a/gcloud/beta/iap/oauth-brands/describe b/gcloud/beta/iap/oauth-brands/describe index c4ca34079..f1bedac81 100644 --- a/gcloud/beta/iap/oauth-brands/describe +++ b/gcloud/beta/iap/oauth-brands/describe @@ -5,7 +5,11 @@ SYNOPSIS gcloud beta iap oauth-brands describe NAME [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. + (BETA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud beta iap oauth-brands describe is used to describe a Cloud OAuth brand. diff --git a/gcloud/beta/iap/oauth-brands/help b/gcloud/beta/iap/oauth-brands/help index b941be7cb..058162a8f 100644 --- a/gcloud/beta/iap/oauth-brands/help +++ b/gcloud/beta/iap/oauth-brands/help @@ -7,7 +7,11 @@ SYNOPSIS DESCRIPTION (BETA) (DEPRECATED) Manage IAP OAuth brands. - This command is deprecated. + This command is deprecated and will be non-functional after the IAP OAuth + Admin APIs are turned down. Jan 19, 2026: Google will discontinue support + for the IAP OAuth Admin APIs. New projects will not be able to use these + APIs. March 19, 2026: The IAP OAuth Admin APIs will be permanently shut + down. Access to this feature will no longer be available. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/iap/oauth-brands/list b/gcloud/beta/iap/oauth-brands/list index b970baadb..42d1d6d1b 100644 --- a/gcloud/beta/iap/oauth-brands/list +++ b/gcloud/beta/iap/oauth-brands/list @@ -6,7 +6,11 @@ SYNOPSIS [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. + (BETA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud beta iap oauth-brands list is used to list the Cloud OAuth brand in the project. diff --git a/gcloud/beta/iap/oauth-clients/create b/gcloud/beta/iap/oauth-clients/create index 0979d58cf..11673ade3 100644 --- a/gcloud/beta/iap/oauth-clients/create +++ b/gcloud/beta/iap/oauth-clients/create @@ -7,7 +7,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. + (BETA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud beta iap oauth-clients create is used to create an OAuth client in the project to be used by Cloud IAP. To call this command, the Cloud OAuth diff --git a/gcloud/beta/iap/oauth-clients/delete b/gcloud/beta/iap/oauth-clients/delete index 3687ebd29..af1c986cf 100644 --- a/gcloud/beta/iap/oauth-clients/delete +++ b/gcloud/beta/iap/oauth-clients/delete @@ -6,7 +6,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. + (BETA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud beta iap oauth-clients delete is used to delete a Cloud IAP OAuth client. Note this command cannot be used to delete any other type of OAuth diff --git a/gcloud/beta/iap/oauth-clients/describe b/gcloud/beta/iap/oauth-clients/describe index 34514faee..6be6b7465 100644 --- a/gcloud/beta/iap/oauth-clients/describe +++ b/gcloud/beta/iap/oauth-clients/describe @@ -6,7 +6,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. + (BETA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud beta iap oauth-clients describe is used to describe a Cloud IAP OAuth client. Note this command cannot be used to describe any other type diff --git a/gcloud/beta/iap/oauth-clients/help b/gcloud/beta/iap/oauth-clients/help index 9848685d1..282d39455 100644 --- a/gcloud/beta/iap/oauth-clients/help +++ b/gcloud/beta/iap/oauth-clients/help @@ -7,7 +7,11 @@ SYNOPSIS DESCRIPTION (BETA) (DEPRECATED) Manage IAP OAuth clients. - This command is deprecated. + This command is deprecated and will be non-functional after the IAP OAuth + Admin APIs are turned down. Jan 19, 2026: Google will discontinue support + for the IAP OAuth Admin APIs. New projects will not be able to use these + APIs. March 19, 2026: The IAP OAuth Admin APIs will be permanently shut + down. Access to this feature will no longer be available. Manage OAuth clients that are used by Cloud Identity-Aware Proxy. Note this API cannot be used as a generic management API for all OAuth clients in diff --git a/gcloud/beta/iap/oauth-clients/list b/gcloud/beta/iap/oauth-clients/list index 1dc46ceee..b447d5298 100644 --- a/gcloud/beta/iap/oauth-clients/list +++ b/gcloud/beta/iap/oauth-clients/list @@ -8,7 +8,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. + (BETA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud beta iap oauth-clients list is used to list Cloud IAP OAuth clients in a Cloud OAuth brand. Note this command will not list any other type of diff --git a/gcloud/beta/iap/oauth-clients/reset-secret b/gcloud/beta/iap/oauth-clients/reset-secret index a585908da..7d18540f6 100644 --- a/gcloud/beta/iap/oauth-clients/reset-secret +++ b/gcloud/beta/iap/oauth-clients/reset-secret @@ -7,7 +7,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) (DEPRECATED) This command is deprecated. + (BETA) (DEPRECATED) This command is deprecated and will be non-functional + after the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud beta iap oauth-clients reset-secret is used to reset a Cloud IAP OAuth client secret. Note this command cannot be used to reset the secret diff --git a/gcloud/beta/managed-kafka/connect-clusters/create b/gcloud/beta/managed-kafka/connect-clusters/create new file mode 100644 index 000000000..f1f2f13df --- /dev/null +++ b/gcloud/beta/managed-kafka/connect-clusters/create @@ -0,0 +1,150 @@ +NAME + gcloud beta managed-kafka connect-clusters create - create a Managed + Service for Apache Kafka connect cluster + +SYNOPSIS + gcloud beta managed-kafka connect-clusters create + (CONNECT_CLUSTER : --location=LOCATION) --cpu=CPU + --kafka-cluster=KAFKA_CLUSTER --memory=MEMORY + --primary-subnet=PRIMARY_SUBNET [--additional-subnet=ADDITIONAL_SUBNET] + [--async] [--dns-name=DNS_NAME] [--labels=[KEY=VALUE,...]] + [--secret=SECRET] + [--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Managed Service for Apache Kafka connect cluster. + +EXAMPLES + To create a connector cluster, run the following: + + $ gcloud beta managed-kafka connect-clusters create \ + myconnectorCluster --location=us-central1 --cpu=3 \ + --memory=3GiB \ + --primary-subnet=projects/PROJECT_ID/regions/us-central1/\ + subnetworks/default --kafka-cluster=my-kafka-cluster OR \ + --kafka-cluster=projects/PROJECT_ID/locations/us-central1/\ + clusters/my-kafka-cluster + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the connect cluster that is created. + 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 connect_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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --cpu=CPU + The number of vCPUs to provision for the cluster. The minimum is 3. + + --kafka-cluster=KAFKA_CLUSTER + The resource path of the Kafka cluster to connect to, or the name of + the Kafka cluster to connect to if the cluster is in the same project + as the Connect cluster. + + --memory=MEMORY + The memory to provision for the cluster in bytes. The value must be + between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. + + --primary-subnet=PRIMARY_SUBNET + VPC subnet to make available to the Kafka Connect cluster. Structured + like: projects/{project}/regions/{region}/subnetworks/{subnet_id}. The + primary subnet is used to create a Private Service Connect (PSC) + interface for the Kafka Connect workers. It must be located in the same + region as the Connect cluster. + +OPTIONAL FLAGS + --additional-subnet=ADDITIONAL_SUBNET + Additional subnet to make available to the Kafka Connect cluster. + Structured like: + projects/{project}/regions/{region}/subnetworks/{subnet_id}. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --dns-name=DNS_NAME + DNS domain name from the subnet's network to be made visible to the + Connect Cluster. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. Keys must start with a lowercase + character and contain only hyphens (-), underscores (_), lowercase + characters, and numbers. Values must contain only hyphens (-), + underscores (_), lowercase characters, and numbers. + + --secret=SECRET + Secrets to load into workers. Exact SecretVersions from Secret Manager + must be provided -- aliases are not supported. Up to 32 secrets may be + loaded into one cluster. Format: + projects//secrets//versions/ + + At most one of these can be specified: + + --config-file=JSON|YAML|FILE + The path to the JSON or YAML file containing the configuration that + are overridden from the cluster or connector defaults. This also + supports inline JSON or YAML. Sets config_file value. + + Input Example: + + --config-file=string + + File Example: + + --config-file=path_to_file.(yaml|json) + + --configs=[KEY=VALUE,...] + Configuration for the connect cluster that are overridden from the + cluster defaults. The key of the map is a Kafka topic property name, + for example: cleanup.policy=compact,compression.type=producer. + +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 managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connect-clusters create + + $ gcloud alpha managed-kafka connect-clusters create + diff --git a/gcloud/beta/managed-kafka/connect-clusters/delete b/gcloud/beta/managed-kafka/connect-clusters/delete new file mode 100644 index 000000000..c74b6f0ee --- /dev/null +++ b/gcloud/beta/managed-kafka/connect-clusters/delete @@ -0,0 +1,80 @@ +NAME + gcloud beta managed-kafka connect-clusters delete - delete a Managed + Service for Apache Kafka connect cluster + +SYNOPSIS + gcloud beta managed-kafka connect-clusters delete + (CONNECT_CLUSTER : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Managed Service for Apache Kafka connect cluster. + +EXAMPLES + To delete a connect cluster named myconnectcluster located in us-central1, + run the following: + + $ gcloud beta managed-kafka connect-clusters delete \ + myconnectcluster --location=us-central1 + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the connect cluster for deletion. + 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 connect_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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connect-clusters delete + + $ gcloud alpha managed-kafka connect-clusters delete + diff --git a/gcloud/beta/managed-kafka/connect-clusters/describe b/gcloud/beta/managed-kafka/connect-clusters/describe new file mode 100644 index 000000000..b2e63d795 --- /dev/null +++ b/gcloud/beta/managed-kafka/connect-clusters/describe @@ -0,0 +1,75 @@ +NAME + gcloud beta managed-kafka connect-clusters describe - describe a Managed + Service for Apache Kafka connect cluster + +SYNOPSIS + gcloud beta managed-kafka connect-clusters describe + (CONNECT_CLUSTER : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Managed Service for Apache Kafka for BigQuery connect + cluster. + +EXAMPLES + To describe a connect cluster named myconnectcluster located in + us-central1, run the following: + + $ gcloud beta managed-kafka connect-clusters describe \ + myconnectcluster --location=us-central1 + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the connect cluster. 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 connect_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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connect-clusters describe + + $ gcloud alpha managed-kafka connect-clusters describe + diff --git a/gcloud/beta/managed-kafka/connect-clusters/help b/gcloud/beta/managed-kafka/connect-clusters/help new file mode 100644 index 000000000..fe3cf6b3c --- /dev/null +++ b/gcloud/beta/managed-kafka/connect-clusters/help @@ -0,0 +1,43 @@ +NAME + gcloud beta managed-kafka connect-clusters - administer Managed Service for + Apache Kafka connect-clusters + +SYNOPSIS + gcloud beta managed-kafka connect-clusters COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Administer Managed Service for Apache Kafka connect-clusters. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a Managed Service for Apache Kafka connect cluster. + + delete + (BETA) Delete a Managed Service for Apache Kafka connect cluster. + + describe + (BETA) Describe a Managed Service for Apache Kafka connect cluster. + + list + (BETA) List all Managed Service for Apache Kafka connect clusters in a + given location. + + update + (BETA) Update a Managed Service for Apache Kafka for BigQuery connect + cluster. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connect-clusters + + $ gcloud alpha managed-kafka connect-clusters + diff --git a/gcloud/beta/managed-kafka/connect-clusters/list b/gcloud/beta/managed-kafka/connect-clusters/list new file mode 100644 index 000000000..627428832 --- /dev/null +++ b/gcloud/beta/managed-kafka/connect-clusters/list @@ -0,0 +1,88 @@ +NAME + gcloud beta managed-kafka connect-clusters list - list all Managed Service + for Apache Kafka connect clusters in a given location + +SYNOPSIS + gcloud beta managed-kafka connect-clusters list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all Managed Service for Apache Kafka connect clusters in a + given location. To specify the maximum number of clusters to list, use the + --limit flag. + +EXAMPLES + To list all connect clusters in a given location, such as us-central1, run + the following: + + $ gcloud beta managed-kafka connect-clusters list \ + --location=us-central1 + +REQUIRED FLAGS + Location resource - Identifies the region which contains all the connector + clusters to be listed. This represents a Cloud resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connect-clusters list + + $ gcloud alpha managed-kafka connect-clusters list + diff --git a/gcloud/beta/managed-kafka/connect-clusters/update b/gcloud/beta/managed-kafka/connect-clusters/update new file mode 100644 index 000000000..0bdbf5ad0 --- /dev/null +++ b/gcloud/beta/managed-kafka/connect-clusters/update @@ -0,0 +1,177 @@ +NAME + gcloud beta managed-kafka connect-clusters update - update a Managed + Service for Apache Kafka for BigQuery connect cluster + +SYNOPSIS + gcloud beta managed-kafka connect-clusters update + (CONNECT_CLUSTER : --location=LOCATION) + (--cpu=CPU --memory=MEMORY --clear-configs + | --config-file=JSON|YAML|FILE + | --configs=[KEY=VALUE,...] --clear-dns-names + | --dns-name=DNS_NAME --clear-labels + | --labels=[KEY=VALUE,...] --clear-secrets + | --secret=SECRET [--primary-subnet=PRIMARY_SUBNET + : --additional-subnet=ADDITIONAL_SUBNET]) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an Managed Service for Apache Kafka for BigQuery connect + cluster. + +EXAMPLES + To update a connect cluster, run the following: + + $ gcloud beta managed-kafka connect-clusters update \ + myconnectorCluster --location=us-central1 \ + --configs=KEY1=VALUE1,KEY2=VALUE2... OR \ + --config-file=my-config-file.yaml --cpu=3 --memory=3GiB \ + --primary-subnet=projects/my-project/regions/us-central1/\ + subnetworks/default/1 \ + --additional-subnet=projects/my-project/regions/us-central1/\ + subnetworks/default/2 \ + --dns-name=bootstrap.myconnectorCluster.us-central1.managedkafka\ + .my-project.cloud.goog:9092 \ + --secret=projects/my-project/secrets/my-secret/versions/1 \ + --labels=KEY1=VALUE1,KEY2=VALUE2... + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the connect cluster for which the + command 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 connect_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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + At least one of these must be specified: + + --cpu=CPU + The number of vCPUs to provision for the cluster. The minimum is 3. + + --memory=MEMORY + The memory to provision for the cluster in bytes. The value must be + between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. + + At most one of these can be specified: + + --clear-configs + Remove all the configurations for the topic. + + --config-file=JSON|YAML|FILE + The path to the JSON or YAML file containing the configuration that + are overridden from the cluster or connector defaults. This also + supports inline JSON or YAML. Sets config_file value. + + Input Example: + + --config-file=string + + File Example: + + --config-file=path_to_file.(yaml|json) + + --configs=[KEY=VALUE,...] + Configuration for the connect cluster that are overridden from the + cluster defaults. The key of the map is a Kafka topic property + name, for example: + cleanup.policy=compact,compression.type=producer. + + At most one of these can be specified: + + --clear-dns-names + Remove all the DNS domain names for the connect cluster. + + --dns-name=DNS_NAME + DNS domain name from the subnet's network to be made visible to the + Connect Cluster. + + At most one of these can be specified: + + --clear-labels + Remove all the labels from the connect cluster. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. Keys must start with a + lowercase character and contain only hyphens (-), underscores (_), + lowercase characters, and numbers. Values must contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + At most one of these can be specified: + + --clear-secrets + Remove all the secrets from the connect cluster. + + --secret=SECRET + Secrets to load into workers. Exact SecretVersions from Secret + Manager must be provided -- aliases are not supported. Up to 32 + secrets may be loaded into one cluster. Format: + projects//secrets//versions/ + + --primary-subnet=PRIMARY_SUBNET + VPC subnet to make available to the Kafka Connect cluster. Structured + like: projects/{project}/regions/{region}/subnetworks/{subnet_id}. + The primary subnet is used to create a Private Service Connect (PSC) + interface for the Kafka Connect workers. It must be located in the + same region as the Connect cluster. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --additional-subnet=ADDITIONAL_SUBNET + Additional subnet to make available to the Kafka Connect cluster. + Structured like: + projects/{project}/regions/{region}/subnetworks/{subnet_id}. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connect-clusters update + + $ gcloud alpha managed-kafka connect-clusters update + diff --git a/gcloud/beta/managed-kafka/connectors/create b/gcloud/beta/managed-kafka/connectors/create new file mode 100644 index 000000000..636ceeb0d --- /dev/null +++ b/gcloud/beta/managed-kafka/connectors/create @@ -0,0 +1,127 @@ +NAME + gcloud beta managed-kafka connectors create - create a Managed Service for + Apache Kafka connector + +SYNOPSIS + gcloud beta managed-kafka connectors create + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + (--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]) + [--task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF + --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Managed Service for Apache Kafka connector. + +EXAMPLES + To create a connector, run the following: + + $ gcloud beta managed-kafka connectors create myconnector \ + --location=us-central1 --connect-cluster=mycluster \ + --configs=connector.class="com.google.pubsub.kafka.source.CloudP\ + ubSubSourceConnector",cps.subscription="my-subscription",... \ + [--task-restart-min-backoff=60s] \ + [--task-restart-max-backoff=30m] OR + $ gcloud beta managed-kafka connectors create myconnector \ + --location=us-central1 --connect-cluster=mycluster \ + --config-file=my-config-file.yaml \ + [--task-restart-min-backoff=60s] \ + [--task-restart-max-backoff=30m] + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector for which the command 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --config-file=JSON|YAML|FILE + The path to the JSON or YAML file containing the configuration that + are overridden from the connector defaults. This also supports inline + JSON or YAML. Sets config_file value. + + Input Example: + + --config-file=string + + File Example: + + --config-file=path_to_file.(yaml|json) + + --configs=[KEY=VALUE,...] + Configuration for the connector that are overridden from the + connector defaults. The key of the map is a Kafka topic property + name, for example: cleanup.policy=compact,compression.type=producer. + +OPTIONAL FLAGS + --task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF + The maximum amount of time to wait before retrying a failed task in + seconds. This sets an upper bound for the backoff delay. The default + value is 1800s (30 minutes). See $ gcloud topic datetimes for + information on duration formats. + + --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF + The minimum amount of time to wait before retrying a failed task in + seconds. This sets a lower bound for the backoff delay. The default + value is 60s. See $ gcloud topic datetimes for information on duration + formats. + +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 managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connectors create + + $ gcloud alpha managed-kafka connectors create + diff --git a/gcloud/beta/managed-kafka/connectors/delete b/gcloud/beta/managed-kafka/connectors/delete new file mode 100644 index 000000000..59d781a2a --- /dev/null +++ b/gcloud/beta/managed-kafka/connectors/delete @@ -0,0 +1,82 @@ +NAME + gcloud beta managed-kafka connectors delete - delete a Managed Service for + Apache Kafka connector + +SYNOPSIS + gcloud beta managed-kafka connectors delete + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Managed Service for Apache Kafka connector. + +EXAMPLES + To delete a connector named myconnector located in us-central1, run the + following: + + $ gcloud beta managed-kafka connectors delete myconnector \ + --location=us-central1 --connect-cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the cluster for deletion. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connectors delete + + $ gcloud alpha managed-kafka connectors delete + diff --git a/gcloud/beta/managed-kafka/connectors/describe b/gcloud/beta/managed-kafka/connectors/describe new file mode 100644 index 000000000..51bd1c9d0 --- /dev/null +++ b/gcloud/beta/managed-kafka/connectors/describe @@ -0,0 +1,82 @@ +NAME + gcloud beta managed-kafka connectors describe - describe a Managed Service + for Apache Kafka connector + +SYNOPSIS + gcloud beta managed-kafka connectors describe + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Managed Service for Apache Kafka connector. + +EXAMPLES + To describe a connector named myconnector located in us-central1, run the + following: + + $ gcloud beta managed-kafka connectors describe myconnector \ + --location=us-central1 --connect-cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector for details to be displayed. + 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connectors describe + + $ gcloud alpha managed-kafka connectors describe + diff --git a/gcloud/beta/managed-kafka/connectors/help b/gcloud/beta/managed-kafka/connectors/help new file mode 100644 index 000000000..bb266679e --- /dev/null +++ b/gcloud/beta/managed-kafka/connectors/help @@ -0,0 +1,56 @@ +NAME + gcloud beta managed-kafka connectors - administer Managed Service for + Apache Kafka connectors + +SYNOPSIS + gcloud beta managed-kafka connectors COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Administer Managed Service for Apache Kafka connectors. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a Managed Service for Apache Kafka connector. + + delete + (BETA) Delete a Managed Service for Apache Kafka connector. + + describe + (BETA) Describe a Managed Service for Apache Kafka connector. + + list + (BETA) List all Managed Service for Apache Kafka connectors for a given + connect cluster. + + pause + (BETA) Pauses operation of a Managed Service for Apache Kafka + connector. + + restart + (BETA) Restarts a Managed Service for Apache Kafka connector. + + resume + (BETA) Resumes operation of a stopped Managed Service for Apache Kafka + connector. + + stop + (BETA) Stops operation of a Managed Service for Apache Kafka connector. + + update + (BETA) Update a Managed Service for Apache Kafka connector. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connectors + + $ gcloud alpha managed-kafka connectors + diff --git a/gcloud/beta/managed-kafka/connectors/list b/gcloud/beta/managed-kafka/connectors/list new file mode 100644 index 000000000..accab6e0e --- /dev/null +++ b/gcloud/beta/managed-kafka/connectors/list @@ -0,0 +1,104 @@ +NAME + gcloud beta managed-kafka connectors list - list all Managed Service for + Apache Kafka connectors for a given connect cluster + +SYNOPSIS + gcloud beta managed-kafka connectors list + (CONNECT_CLUSTER : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all Managed Service for Apache Kafka connectors for a given + connect cluster. To specify the maximum number of connectors to list, use + the --limit flag. + +EXAMPLES + To list all Managed Service for Apache Kafka connectors belonging to the + "mycluster" connect cluster in us-central1, run the following: + + $ gcloud beta managed-kafka connectors list mycluster \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the cluster which contains all the + connectors to be listed. 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 connect_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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connectors list + + $ gcloud alpha managed-kafka connectors list + diff --git a/gcloud/beta/managed-kafka/connectors/pause b/gcloud/beta/managed-kafka/connectors/pause new file mode 100644 index 000000000..4cba8e2ff --- /dev/null +++ b/gcloud/beta/managed-kafka/connectors/pause @@ -0,0 +1,82 @@ +NAME + gcloud beta managed-kafka connectors pause - pauses operation of a Managed + Service for Apache Kafka connector + +SYNOPSIS + gcloud beta managed-kafka connectors pause + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Pauses operation of a Managed Service for Apache Kafka connector. + +EXAMPLES + To pause a connector named myconnector located in us-central1, run the + following: + + $ gcloud beta managed-kafka connectors pause myconnector \ + --location=us-central1 --connect-cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector to pause. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connectors pause + + $ gcloud alpha managed-kafka connectors pause + diff --git a/gcloud/beta/managed-kafka/connectors/restart b/gcloud/beta/managed-kafka/connectors/restart new file mode 100644 index 000000000..7aa806454 --- /dev/null +++ b/gcloud/beta/managed-kafka/connectors/restart @@ -0,0 +1,82 @@ +NAME + gcloud beta managed-kafka connectors restart - restarts a Managed Service + for Apache Kafka connector + +SYNOPSIS + gcloud beta managed-kafka connectors restart + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Restarts a Managed Service for Apache Kafka connector. + +EXAMPLES + To restart a connector named myconnector located in us-central1, run the + following: + + $ gcloud beta managed-kafka connectors restart myconnector \ + --location=us-central1 --connect-cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector to restart. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connectors restart + + $ gcloud alpha managed-kafka connectors restart + diff --git a/gcloud/beta/managed-kafka/connectors/resume b/gcloud/beta/managed-kafka/connectors/resume new file mode 100644 index 000000000..c66b84ec5 --- /dev/null +++ b/gcloud/beta/managed-kafka/connectors/resume @@ -0,0 +1,83 @@ +NAME + gcloud beta managed-kafka connectors resume - resumes operation of a + stopped Managed Service for Apache Kafka connector + +SYNOPSIS + gcloud beta managed-kafka connectors resume + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Resumes operation of a stopped Managed Service for Apache Kafka + connector. + +EXAMPLES + To resume a connector named myconnector located in us-central1, run the + following: + + $ gcloud beta managed-kafka connectors resume myconnector \ + --location=us-central1 --connect-cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector to resume. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connectors resume + + $ gcloud alpha managed-kafka connectors resume + diff --git a/gcloud/beta/managed-kafka/connectors/stop b/gcloud/beta/managed-kafka/connectors/stop new file mode 100644 index 000000000..0a86d2a9a --- /dev/null +++ b/gcloud/beta/managed-kafka/connectors/stop @@ -0,0 +1,82 @@ +NAME + gcloud beta managed-kafka connectors stop - stops operation of a Managed + Service for Apache Kafka connector + +SYNOPSIS + gcloud beta managed-kafka connectors stop + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Stops operation of a Managed Service for Apache Kafka connector. + +EXAMPLES + To stop a connector named myconnector located in us-central1, run the + following: + + $ gcloud beta managed-kafka connectors stop myconnector \ + --location=us-central1 --connect-cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector to resume. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connectors stop + + $ gcloud alpha managed-kafka connectors stop + diff --git a/gcloud/beta/managed-kafka/connectors/update b/gcloud/beta/managed-kafka/connectors/update new file mode 100644 index 000000000..637654f2b --- /dev/null +++ b/gcloud/beta/managed-kafka/connectors/update @@ -0,0 +1,123 @@ +NAME + gcloud beta managed-kafka connectors update - update a Managed Service for + Apache Kafka connector + +SYNOPSIS + gcloud beta managed-kafka connectors update + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]] + [--task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF + --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Managed Service for Apache Kafka connector. + +EXAMPLES + To update a connector name myconnector, run the following: + + $ gcloud beta managed-kafka connectors update myconnector \ + --location=us-central1 --configs=KEY1=VALUE1,KEY2=VALUE2... \ + --connect-cluster=mycluster [--task-restart-min-backoff=60s] \ + [--task-restart-max-backoff=30m] OR + $ gcloud beta managed-kafka connectors update myconnector \ + --location=us-central1 --config-file=my-config-file.yaml \ + --connect-cluster=mycluster [--task-restart-min-backoff=60s] \ + [--task-restart-max-backoff=30m] + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector for which the command 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + At most one of these can be specified: + + --config-file=JSON|YAML|FILE + The path to the JSON or YAML file containing the configuration that + are overridden from the connector defaults. This also supports inline + JSON or YAML. Sets config_file value. + + Input Example: + + --config-file=string + + File Example: + + --config-file=path_to_file.(yaml|json) + + --configs=[KEY=VALUE,...] + Configuration for the connector that are overridden from the + connector defaults. The key of the map is a Kafka topic property + name, for example: cleanup.policy=compact,compression.type=producer. + + --task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF + The maximum amount of time to wait before retrying a failed task in + seconds. This sets an upper bound for the backoff delay. The default + value is 1800s (30 minutes). See $ gcloud topic datetimes for + information on duration formats. + + --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF + The minimum amount of time to wait before retrying a failed task in + seconds. This sets a lower bound for the backoff delay. The default + value is 60s. See $ gcloud topic datetimes for information on duration + formats. + +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 managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud managed-kafka connectors update + + $ gcloud alpha managed-kafka connectors update + diff --git a/gcloud/beta/managed-kafka/help b/gcloud/beta/managed-kafka/help index 2f3d1357f..d758cc620 100644 --- a/gcloud/beta/managed-kafka/help +++ b/gcloud/beta/managed-kafka/help @@ -23,6 +23,12 @@ GROUPS clusters (BETA) Administer Managed Service for Apache Kafka clusters. + connect-clusters + (BETA) Administer Managed Service for Apache Kafka connect-clusters. + + connectors + (BETA) Administer Managed Service for Apache Kafka connectors. + consumer-groups (BETA) Administer Managed Service for Apache Kafka consumer groups. diff --git a/gcloud/beta/network-security/authz-policies/delete b/gcloud/beta/network-security/authz-policies/delete index 3eb69bf1d..32e8464d9 100644 --- a/gcloud/beta/network-security/authz-policies/delete +++ b/gcloud/beta/network-security/authz-policies/delete @@ -66,5 +66,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-security authz-policies delete diff --git a/gcloud/beta/network-security/authz-policies/describe b/gcloud/beta/network-security/authz-policies/describe index 2e92f576e..bc80b13ad 100644 --- a/gcloud/beta/network-security/authz-policies/describe +++ b/gcloud/beta/network-security/authz-policies/describe @@ -61,5 +61,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-security authz-policies describe diff --git a/gcloud/beta/network-security/authz-policies/help b/gcloud/beta/network-security/authz-policies/help index 673413c5a..3413225d9 100644 --- a/gcloud/beta/network-security/authz-policies/help +++ b/gcloud/beta/network-security/authz-policies/help @@ -29,5 +29,8 @@ COMMANDS (BETA) List AuthzPolicy resources. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-security authz-policies diff --git a/gcloud/beta/network-security/authz-policies/import b/gcloud/beta/network-security/authz-policies/import index 5111b8a4f..b12d0c4b8 100644 --- a/gcloud/beta/network-security/authz-policies/import +++ b/gcloud/beta/network-security/authz-policies/import @@ -78,5 +78,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-security authz-policies import diff --git a/gcloud/beta/network-security/authz-policies/list b/gcloud/beta/network-security/authz-policies/list index e1da880bd..83387e154 100644 --- a/gcloud/beta/network-security/authz-policies/list +++ b/gcloud/beta/network-security/authz-policies/list @@ -82,5 +82,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud network-security authz-policies list diff --git a/gcloud/beta/pam/grants/create b/gcloud/beta/pam/grants/create index 6eae81d96..116978503 100644 --- a/gcloud/beta/pam/grants/create +++ b/gcloud/beta/pam/grants/create @@ -7,7 +7,10 @@ SYNOPSIS (--entitlement=ENTITLEMENT : --folder=FOLDER --location=LOCATION --organization=ORGANIZATION) [--additional-email-recipients=[ADDITIONAL_EMAIL_RECIPIENTS,...]] - [--justification=JUSTIFICATION] [GCLOUD_WIDE_FLAG ...] + [--justification=JUSTIFICATION] + [--requested-access-from-file=[REQUESTED_ACCESS_FROM_FILE,...] + | --requested-resources=[REQUESTED_RESOURCES,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a new Privileged Access Manager (PAM) grant under an @@ -91,6 +94,20 @@ OPTIONAL FLAGS --justification=JUSTIFICATION Justification for the grant. + Specify the grant's scope using either high-level resource or a + fine-grained scope configuration. + + At most one of these can be specified: + + --requested-access-from-file=[REQUESTED_ACCESS_FROM_FILE,...] + Path to a YAML file defining the fine-grained scope for the grant. + + --requested-resources=[REQUESTED_RESOURCES,...] + The Google Cloud resources to be granted access to. Format: + {resource-type}/{resource_id}. Example: projects/{project_id} or + folders/{folder_id} or organizations/{organization_id}. This command + currently accepts only one resource. + 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/pam/grants/help b/gcloud/beta/pam/grants/help index e2a3562d7..dd5af7a03 100644 --- a/gcloud/beta/pam/grants/help +++ b/gcloud/beta/pam/grants/help @@ -63,6 +63,10 @@ EXAMPLES $ gcloud beta pam grants search --entitlement=ENTITLEMENT_NAME \ --caller-relationship=can-approve + To withdraw a grant with the full name GRANT_NAME, run: + + $ gcloud beta pam grants withdraw GRANT_NAME + GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -94,6 +98,9 @@ COMMANDS (BETA) Search for and list all Privileged Access Manager (PAM) grants you have created, have approved, or can approve. + withdraw + (BETA) Withdraw a Privileged Access Manager (PAM) grant. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/pam/grants/withdraw b/gcloud/beta/pam/grants/withdraw new file mode 100644 index 000000000..23b1e491e --- /dev/null +++ b/gcloud/beta/pam/grants/withdraw @@ -0,0 +1,100 @@ +NAME + gcloud beta pam grants withdraw - withdraw a Privileged Access Manager + grant + +SYNOPSIS + gcloud beta pam grants withdraw + (GRANT : --entitlement=ENTITLEMENT + --folder=FOLDER --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Withdraw a Privileged Access Manager (PAM) grant. + +EXAMPLES + The following command withdraws a grant with the full name GRANT_NAME: + + $ gcloud beta pam grants withdraw GRANT_NAME + +POSITIONAL ARGUMENTS + Grant resource - Name of the grant to withdraw. 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 grant on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: + [privilegedaccessmanager.projects.locations.entitlements.grants, + privilegedaccessmanager.folders.locations.entitlements.grants, + privilegedaccessmanager.organizations.locations.entitlements.grants]. + + This must be specified. + + GRANT + ID of the grant or fully qualified identifier for the grant. + + To set the grant attribute: + ▸ provide the argument grant on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --entitlement=ENTITLEMENT + The entitlement id + + To set the entitlement attribute: + ▸ provide the argument grant on the command line with a fully + specified name; + ▸ provide the argument --entitlement on the command line. + + --folder=FOLDER + The name of the folder + + To set the folder attribute: + ▸ provide the argument grant on the command line with a fully + specified name; + ▸ provide the argument --folder on the command line. Must be + specified for resource of type + [privilegedaccessmanager.folders.locations.entitlements.grants]. + + --location=LOCATION + The resource location + + To set the location attribute: + ▸ provide the argument grant on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + The name of the organization + + To set the organization attribute: + ▸ provide the argument grant on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [privilegedaccessmanager.organizations.locations.entitlements.grants]. + +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 privilegedaccessmanager/v1beta API. The full + documentation for this API can be found at: + https://cloud.google.com/iam/docs/pam-overview + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha pam grants withdraw + diff --git a/gcloud/beta/pam/help b/gcloud/beta/pam/help index 1205c259e..89c34968f 100644 --- a/gcloud/beta/pam/help +++ b/gcloud/beta/pam/help @@ -44,6 +44,9 @@ GROUPS operations (BETA) Manage Privileged Access Manager (PAM) Long Running Operations. + settings + (BETA) Manage Privileged Access Manager (PAM) Settings. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/beta/pam/settings/describe b/gcloud/beta/pam/settings/describe new file mode 100644 index 000000000..a38240fb2 --- /dev/null +++ b/gcloud/beta/pam/settings/describe @@ -0,0 +1,97 @@ +NAME + gcloud beta pam settings describe - show details of Privileged Access + Manager settings on a resource + +SYNOPSIS + gcloud beta pam settings describe + (--location=LOCATION : --folder=FOLDER --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show details of Privileged Access Manager (PAM) settings on a + resource. + +EXAMPLES + The following command describes settings on a project named sample-project, + and in location global: + + $ gcloud beta pam settings describe --project=sample-project \ + --location=global + + The following command describes settings on a folder with ID FOLDER_ID, and + in location global: + + $ gcloud beta pam settings describe --folder=FOLDER_ID \ + --location=global + + The following command describes settings on an organization with ID + ORGANIZATION_ID, and in location global: + + $ gcloud beta pam settings describe --organization=ORGANIZATION_ID \ + --location=global + +REQUIRED FLAGS + Location resource - The project/organization/folder location for which the + settings are to be described. 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 --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [privilegedaccessmanager.projects.locations, + privilegedaccessmanager.folders.locations, + privilegedaccessmanager.organizations.locations]. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --folder=FOLDER + The name of the folder + + To set the folder attribute: + ▸ provide the argument --location on the command line with a fully + specified name; + ▸ provide the argument --folder on the command line. Must be + specified for resource of type + [privilegedaccessmanager.folders.locations]. + + --organization=ORGANIZATION + The name of the organization + + To set the organization attribute: + ▸ provide the argument --location on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [privilegedaccessmanager.organizations.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 privilegedaccessmanager/v1beta API. The full + documentation for this API can be found at: + https://cloud.google.com/iam/docs/pam-overview + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha pam settings describe + diff --git a/gcloud/beta/pam/settings/describe-effective b/gcloud/beta/pam/settings/describe-effective new file mode 100644 index 000000000..bd5a3237f --- /dev/null +++ b/gcloud/beta/pam/settings/describe-effective @@ -0,0 +1,101 @@ +NAME + gcloud beta pam settings describe-effective - show effective Privileged + Access Manager settings on a resource + +SYNOPSIS + gcloud beta pam settings describe-effective + (--location=LOCATION : --folder=FOLDER --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show effective Privileged Access Manager (PAM) settings on a + resource. The "effective value" of a setting on a given resource refers to + the final or active value of a setting configuration that is applied to a + resource. For each configuration type field in settings resource, a + hierarchy evaluation will happen to calculate effective value on the + resource node. + +EXAMPLES + The following command describes effective settings on a project named + sample-project, and in location global: + + $ gcloud beta pam settings describe-effective \ + --project=sample-project --location=global + + The following command describes effective settings on a folder with ID + FOLDER_ID, and in location global: + + $ gcloud beta pam settings describe-effective --folder=FOLDER_ID \ + --location=global + + The following command describes effective settings on an organization with + ID ORGANIZATION_ID, and in location global: + + $ gcloud beta pam settings describe-effective \ + --organization=ORGANIZATION_ID --location=global + +REQUIRED FLAGS + Location resource - The project/organization/folder location for which the + effective settings are to be described. 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 --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [privilegedaccessmanager.projects.locations, + privilegedaccessmanager.folders.locations, + privilegedaccessmanager.organizations.locations]. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --folder=FOLDER + The name of the folder + + To set the folder attribute: + ▸ provide the argument --location on the command line with a fully + specified name; + ▸ provide the argument --folder on the command line. Must be + specified for resource of type + [privilegedaccessmanager.folders.locations]. + + --organization=ORGANIZATION + The name of the organization + + To set the organization attribute: + ▸ provide the argument --location on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [privilegedaccessmanager.organizations.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 privilegedaccessmanager/v1beta API. The full + documentation for this API can be found at: + https://cloud.google.com/iam/docs/pam-overview + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha pam settings describe-effective + diff --git a/gcloud/beta/pam/settings/export b/gcloud/beta/pam/settings/export new file mode 100644 index 000000000..35a2c7042 --- /dev/null +++ b/gcloud/beta/pam/settings/export @@ -0,0 +1,107 @@ +NAME + gcloud beta pam settings export - export Privileged Access Manager settings + configured on a project, folder, or organization to a local YAML file + +SYNOPSIS + gcloud beta pam settings export + (--location=LOCATION : --folder=FOLDER --organization=ORGANIZATION) + [--destination=DESTINATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Export the Privileged Access Manager (PAM) settings configured for a + specified project, folder, or organization to a local YAML file. + +EXAMPLES + The following command exports PAM settings for the project named + sample-project in location global to a local YAML file named + pam-settings.yaml: + + $ gcloud beta pam settings export --project=sample-project \ + --location=global --destination=pam-settings.yaml + + The following command exports PAM settings for the folder with ID FOLDER_ID + in location global to a local YAML file named pam-settings.yaml: + + $ gcloud beta pam settings export --folder=FOLDER_ID \ + --location=global --destination=pam-settings.yaml + + The following command exports PAM settings for the organization with ID + ORGANIZATION_ID in location global to a local YAML file named + pam-settings.yaml: + + $ gcloud beta pam settings export --organization=ORGANIZATION_ID \ + --location=global --destination=pam-settings.yaml + +REQUIRED FLAGS + Location resource - The project/organization/folder location for which the + settings needs to be exported. 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 --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [privilegedaccessmanager.projects.locations, + privilegedaccessmanager.folders.locations, + privilegedaccessmanager.organizations.locations]. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --folder=FOLDER + The name of the folder + + To set the folder attribute: + ▸ provide the argument --location on the command line with a fully + specified name; + ▸ provide the argument --folder on the command line. Must be + specified for resource of type + [privilegedaccessmanager.folders.locations]. + + --organization=ORGANIZATION + The name of the organization + + To set the organization attribute: + ▸ provide the argument --location on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [privilegedaccessmanager.organizations.locations]. + +OPTIONAL FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. The + exported data will not contain any output-only fields. Alternatively, + you may omit this flag to write to standard output. For a schema + describing the export/import format, see + $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the privilegedaccessmanager/v1beta API. The full + documentation for this API can be found at: + https://cloud.google.com/iam/docs/pam-overview + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha pam settings export + diff --git a/gcloud/beta/pam/settings/help b/gcloud/beta/pam/settings/help new file mode 100644 index 000000000..d6bdcf68c --- /dev/null +++ b/gcloud/beta/pam/settings/help @@ -0,0 +1,117 @@ +NAME + gcloud beta pam settings - manage Privileged Access Manager Settings + +SYNOPSIS + gcloud beta pam settings COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The gcloud pam settings command group lets you manage Privileged + Access Manager (PAM) settings. + +EXAMPLES + To describe the PAM Settings on a project named sample-project and in + location global, run: + + $ gcloud beta pam settings describe --project=sample-project \ + --location=global + + To describe the PAM Settings on a folder with ID FOLDER_ID and in location + global, run: + + $ gcloud beta pam settings describe --folder=FOLDER_ID \ + --location=global + + To describe the PAM Settings on an organization with ID ORGANIZATION_ID and + in location global, run: + + $ gcloud beta pam settings describe --organization=ORGANIZATION_ID \ + --location=global + + To describe the effective PAM Settings on a project named sample-project + and in location global, run: + + $ gcloud beta pam settings describe-effective \ + --project=sample-project --location=global + + To describe the effective PAM Settings on a folder with ID FOLDER_ID and in + location global, run: + + $ gcloud beta pam settings describe-effective --folder=FOLDER_ID \ + --location=global + + To describe the effective PAM Settings on an organization with ID + ORGANIZATION_ID and in location global, run: + + $ gcloud beta pam settings describe-effective \ + --organization=ORGANIZATION_ID --location=global + + To export the PAM Settings configured on a project named sample-project, + and in location global to a local YAML file named pam-settings.yaml, run: + + $ gcloud beta pam settings export --project=sample-project \ + --location=global --destination=pam-settings.yaml + + To export the PAM Settings configured on a folder with ID FOLDER_ID, and in + location global to a local YAML file named pam-settings.yaml, run: + + $ gcloud beta pam settings export --folder=FOLDER_ID \ + --location=global --destination=pam-settings.yaml + + To export the PAM settings configured for an organization with ID + ORGANIZATION_ID in location global to a local YAML file named + pam-settings.yaml, run: + + $ gcloud beta pam settings export --organization=ORGANIZATION_ID \ + --location=global --destination=pam-settings.yaml + + To update the PAM Settings on a project named sample-project and in + location global, and the new updated settings configuration stored in a + file named pam-settings.yaml, run: + + $ gcloud beta pam settings update --project=sample-project \ + --location=global --settings-file=pam-settings.yaml + + To update the PAM Settings on a folder with ID FOLDER_ID and in location + global, and the new updated settings configuration stored in a file named + pam-settings.yaml, run: + + $ gcloud beta pam settings update --folder=FOLDER_ID \ + --location=global --settings-file=pam-settings.yaml + + To update the PAM Settings on an organization with ID ORGANIZATION_ID and + in location global, and the new updated settings configuration stored in a + file named pam-settings.yaml, run: + + $ gcloud beta pam settings update --organization=ORGANIZATION_ID \ + --location=global --settings-file=pam-settings.yaml + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Show details of Privileged Access Manager (PAM) settings on a + resource. + + describe-effective + (BETA) Show effective Privileged Access Manager (PAM) settings on a + resource. + + export + (BETA) Export Privileged Access Manager (PAM) settings configured on a + project, folder, or organization to a local YAML file. + + update + (BETA) Update Privileged Access Manager (PAM) settings configured on a + project, folder, or organization. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha pam settings + diff --git a/gcloud/beta/pam/settings/update b/gcloud/beta/pam/settings/update new file mode 100644 index 000000000..77ced64e6 --- /dev/null +++ b/gcloud/beta/pam/settings/update @@ -0,0 +1,111 @@ +NAME + gcloud beta pam settings update - update Privileged Access Manager settings + configured on a project, folder, or organization + +SYNOPSIS + gcloud beta pam settings update --settings-file=PATH_TO_FILE + (--location=LOCATION : --folder=FOLDER --organization=ORGANIZATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the Privileged Access Manager (PAM) settings configured for a + specified project, folder, or organization. This command allows you to + modify the settings using a YAML file. + +EXAMPLES + The following command updates PAM settings for the project named + sample-project in location global, using the settings defined in a file + named pam_settings.yaml: + + $ gcloud beta pam settings update --project=sample-project \ + --location=global --settings-file=pam_settings.yaml + + The following command updates PAM settings for the folder with ID FOLDER_ID + in location global, using the settings defined in a file named + pam_settings.yaml: + + $ gcloud beta pam settings update --folder=FOLDER_ID \ + --location=global --settings-file=pam_settings.yaml + + The following command updates PAM settings for the organization with ID + ORGANIZATION_ID in location global, using the settings defined in a file + named pam_settings.yaml: + + $ gcloud beta pam settings update --organization=ORGANIZATION_ID \ + --location=global --settings-file=pam_settings.yaml + +REQUIRED FLAGS + --settings-file=PATH_TO_FILE + YAML file containing the new configuration of the PAM settings. Use a + full or relative path to a local file containing the value of + settings_file. + + Location resource - The project/organization/folder location for which the + settings are to be updated. 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 --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [privilegedaccessmanager.projects.locations, + privilegedaccessmanager.folders.locations, + privilegedaccessmanager.organizations.locations]. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --folder=FOLDER + The name of the folder + + To set the folder attribute: + ▸ provide the argument --location on the command line with a fully + specified name; + ▸ provide the argument --folder on the command line. Must be + specified for resource of type + [privilegedaccessmanager.folders.locations]. + + --organization=ORGANIZATION + The name of the organization + + To set the organization attribute: + ▸ provide the argument --location on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [privilegedaccessmanager.organizations.locations]. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the privilegedaccessmanager/v1beta API. The full + documentation for this API can be found at: + https://cloud.google.com/iam/docs/pam-overview + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha pam settings update + diff --git a/gcloud/beta/run/worker-pools/deploy b/gcloud/beta/run/worker-pools/deploy index e69f4fe21..da153caa7 100644 --- a/gcloud/beta/run/worker-pools/deploy +++ b/gcloud/beta/run/worker-pools/deploy @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta run worker-pools deploy [[WORKER_POOL] --region=REGION] [--async] [--breakglass=JUSTIFICATION] [--container=CONTAINER] [--description=DESCRIPTION] [--gpu-type=GPU_TYPE] - [--[no-]gpu-zonal-redundancy] [--mesh=MESH] [--no-promote] + [--[no-]gpu-zonal-redundancy] [--no-promote] [--remove-containers=[CONTAINER,...]] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] [--service-account=SERVICE_ACCOUNT] [--vpc-egress=VPC_EGRESS] @@ -117,12 +117,6 @@ FLAGS Set GPU zonal redundancy. Use --gpu-zonal-redundancy to enable and --no-gpu-zonal-redundancy to disable. - --mesh=MESH - Enables Cloud Service Mesh using the specified mesh resource name. Mesh - resource name must be in the format of - projects/PROJECT/locations/global/meshes/MESH_NAME or MESH_NAME. Will - default to the current project if only MESH_NAME is provided. - --no-promote True to avoid assign instances to the worker revision being deployed. Setting this flag assigns any instances assigned to the LATEST revision diff --git a/gcloud/beta/run/worker-pools/update b/gcloud/beta/run/worker-pools/update index 50982e0e8..760229485 100644 --- a/gcloud/beta/run/worker-pools/update +++ b/gcloud/beta/run/worker-pools/update @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta run worker-pools update [[WORKER_POOL] --region=REGION] [--async] [--breakglass=JUSTIFICATION] [--container=CONTAINER] [--description=DESCRIPTION] [--gpu-type=GPU_TYPE] - [--[no-]gpu-zonal-redundancy] [--mesh=MESH] [--no-promote] + [--[no-]gpu-zonal-redundancy] [--no-promote] [--remove-containers=[CONTAINER,...]] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] [--service-account=SERVICE_ACCOUNT] [--vpc-egress=VPC_EGRESS] @@ -113,12 +113,6 @@ FLAGS Set GPU zonal redundancy. Use --gpu-zonal-redundancy to enable and --no-gpu-zonal-redundancy to disable. - --mesh=MESH - Enables Cloud Service Mesh using the specified mesh resource name. Mesh - resource name must be in the format of - projects/PROJECT/locations/global/meshes/MESH_NAME or MESH_NAME. Will - default to the current project if only MESH_NAME is provided. - --no-promote True to avoid assign instances to the worker revision being deployed. Setting this flag assigns any instances assigned to the LATEST revision diff --git a/gcloud/beta/service-extensions/authz-extensions/delete b/gcloud/beta/service-extensions/authz-extensions/delete index 16818ba8e..ea4ead734 100644 --- a/gcloud/beta/service-extensions/authz-extensions/delete +++ b/gcloud/beta/service-extensions/authz-extensions/delete @@ -67,5 +67,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud service-extensions authz-extensions delete diff --git a/gcloud/beta/service-extensions/authz-extensions/describe b/gcloud/beta/service-extensions/authz-extensions/describe index 5feab33ae..34e3e4011 100644 --- a/gcloud/beta/service-extensions/authz-extensions/describe +++ b/gcloud/beta/service-extensions/authz-extensions/describe @@ -61,5 +61,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud service-extensions authz-extensions describe diff --git a/gcloud/beta/service-extensions/authz-extensions/help b/gcloud/beta/service-extensions/authz-extensions/help index c0ef07804..103f3e4a8 100644 --- a/gcloud/beta/service-extensions/authz-extensions/help +++ b/gcloud/beta/service-extensions/authz-extensions/help @@ -30,5 +30,8 @@ COMMANDS (BETA) List AuthzExtension resources. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud service-extensions authz-extensions diff --git a/gcloud/beta/service-extensions/authz-extensions/import b/gcloud/beta/service-extensions/authz-extensions/import index adb69afb4..2184cd31b 100644 --- a/gcloud/beta/service-extensions/authz-extensions/import +++ b/gcloud/beta/service-extensions/authz-extensions/import @@ -78,5 +78,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud service-extensions authz-extensions import diff --git a/gcloud/beta/service-extensions/authz-extensions/list b/gcloud/beta/service-extensions/authz-extensions/list index 3b2665e0d..843df6603 100644 --- a/gcloud/beta/service-extensions/authz-extensions/list +++ b/gcloud/beta/service-extensions/authz-extensions/list @@ -82,5 +82,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud service-extensions authz-extensions list diff --git a/gcloud/beta/workstations/ssh b/gcloud/beta/workstations/ssh index 075714d44..32ee37731 100644 --- a/gcloud/beta/workstations/ssh +++ b/gcloud/beta/workstations/ssh @@ -12,6 +12,8 @@ SYNOPSIS DESCRIPTION (BETA) SSH into a running workstation. + Note that arguments for the NO_PROXY environment variable must be FQDNs. + EXAMPLES To ssh into a running workstation, run: diff --git a/gcloud/beta/workstations/start-tcp-tunnel b/gcloud/beta/workstations/start-tcp-tunnel index 930b77d28..ff13a4e60 100644 --- a/gcloud/beta/workstations/start-tcp-tunnel +++ b/gcloud/beta/workstations/start-tcp-tunnel @@ -13,6 +13,8 @@ DESCRIPTION (BETA) Start a tunnel through which a local process can forward TCP traffic to the workstation. + Note that arguments for the NO_PROXY environment variable must be FQDNs. + EXAMPLES To start a tunnel to port 22 on a workstation, run: diff --git a/gcloud/bigtable/logical-views/update b/gcloud/bigtable/logical-views/update index b90bc3ed5..df52b1de3 100644 --- a/gcloud/bigtable/logical-views/update +++ b/gcloud/bigtable/logical-views/update @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud bigtable logical-views update (LOGICAL_VIEW : --instance=INSTANCE) - --query=QUERY [--async] [--deletion-protection=DELETION_PROTECTION] + (--deletion-protection=DELETION_PROTECTION --query=QUERY) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -16,6 +16,11 @@ EXAMPLES --instance=my-instance-id \ --query="SELECT my-column-family2 FROM my-table" + To enable deletion protection on a logical view, run: + + $ gcloud bigtable logical-views update my-logical-view-id \ + --instance=my-instance-id --deletion-protection + POSITIONAL ARGUMENTS Logical view resource - The logical view to update. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -49,17 +54,19 @@ POSITIONAL ARGUMENTS ▸ provide the argument --instance on the command line. REQUIRED FLAGS - --query=QUERY - The query of the view. + At least one of these must be specified: + + --deletion-protection=DELETION_PROTECTION + Whether the view is protected from deletion. + + --query=QUERY + The query of the view. OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to complete. - --deletion-protection=DELETION_PROTECTION - Whether the view is protected from deletion. - 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/instance-templates/create b/gcloud/compute/instance-templates/create index 26e1461fa..9a409adf4 100644 --- a/gcloud/compute/instance-templates/create +++ b/gcloud/compute/instance-templates/create @@ -706,6 +706,10 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + vlan + VLAN ID of a Dynamic Network Interface, must be an integer in the + range from 2 to 255 inclusively. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/compute/instance-templates/create-with-container b/gcloud/compute/instance-templates/create-with-container index 2caffeff9..5bb2282dc 100644 --- a/gcloud/compute/instance-templates/create-with-container +++ b/gcloud/compute/instance-templates/create-with-container @@ -626,6 +626,10 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + vlan + VLAN ID of a Dynamic Network Interface, must be an integer in the + range from 2 to 255 inclusively. + --network-tier=NETWORK_TIER Specifies the network tier that will be used to configure the instance. NETWORK_TIER must be one of: PREMIUM, STANDARD. The default value is diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index 1fc3c7e41..af77e600c 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -804,6 +804,10 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + vlan + VLAN ID of a Dynamic Network Interface, must be an integer in the + range from 2 to 255 inclusively. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/compute/instances/create-with-container b/gcloud/compute/instances/create-with-container index 3e6d2afe1..7f8f7a1df 100644 --- a/gcloud/compute/instances/create-with-container +++ b/gcloud/compute/instances/create-with-container @@ -730,6 +730,10 @@ FLAGS Specifies the network attachment that this interface should connect to. Mutually exclusive with --network and --subnet flags. + vlan + VLAN ID of a Dynamic Network Interface, must be an integer in the + range from 2 to 255 inclusively. + --network-performance-configs=[PROPERTY=VALUE,...] Configures network performance settings for the instance. If this flag is not specified, the instance will be created with its default network diff --git a/gcloud/compute/instances/network-interfaces/add b/gcloud/compute/instances/network-interfaces/add new file mode 100644 index 000000000..8dc1875a4 --- /dev/null +++ b/gcloud/compute/instances/network-interfaces/add @@ -0,0 +1,182 @@ +NAME + gcloud compute instances network-interfaces add - add a Dynamic Network + Interface to a Compute Engine instance + +SYNOPSIS + gcloud compute instances network-interfaces add INSTANCE_NAME + [--aliases=ALIASES] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] + [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] + [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] + [--internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH] + [--ipv6-network-tier=IPV6_NETWORK_TIER] [--network=NETWORK] + [--network-attachment=NETWORK_ATTACHMENT] [--network-tier=NETWORK_TIER] + [--parent-nic-name=PARENT_NIC_NAME] + [--private-network-ip=PRIVATE_NETWORK_IP] [--stack-type=STACK_TYPE] + [--subnetwork=SUBNETWORK] [--vlan=VLAN] [--zone=ZONE] + [--address=ADDRESS | --no-address] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instances network-interfaces add adds a Dynamic Network + Interface to a Compute Engine instance. + +EXAMPLES + To add a Dynamic Network Interface to a Compute Engine instance, run: $ gcloud compute instances network-interfaces add instance-name \ + --parent-nic-name=nic1 --vlan=2 --network=network-1 \ + --subnetwork=subnetwork-1 + +POSITIONAL ARGUMENTS + INSTANCE_NAME + Name of the instance to operate on. For details on valid instance + names, refer to the criteria documented under the field 'name' at: + https://cloud.google.com/compute/docs/reference/rest/v1/instances + +FLAGS + --aliases=ALIASES + The IP alias ranges to allocate for this interface. If there are + multiple IP alias ranges, they are separated by semicolons. + + For example: + + --aliases="10.128.1.0/24;range1:/32" + + Each IP alias range consists of a range name and an IP range separated + by a colon, or just the IP range. The range name is the name of the + range within the network interface's subnet from which to allocate an + IP alias range. If unspecified, it defaults to the primary IP range of + the subnet. The IP range can be a CIDR range (e.g. 192.168.100.0/24), a + single IP address (e.g. 192.168.100.1), or a netmask in CIDR format + (e.g. /24). If the IP range is specified by CIDR range or single IP + address, it must belong to the CIDR range specified by the range name + on the subnet. If the IP range is specified by netmask, the IP + allocator will pick an available range with the specified netmask and + allocate it to this network interface. + + --external-ipv6-address=EXTERNAL_IPV6_ADDRESS + Assigns the given external IPv6 address to an instance. The address + must be the first IP in the range. This option is not applicable to + instances with stack-type=IPV4_ONLY. + + --external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH + The prefix length of the external IPv6 address range. This flag should + be used together with --external-ipv6-address. Currently only /96 is + supported and the default value is 96. + + --internal-ipv6-address=INTERNAL_IPV6_ADDRESS + Assigns the given internal IPv6 address or range to an instance. The + address must be the first IP address in the range or a /96 IP address + range. This option can only be used on a dual stack instance network + interface. + + --internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH + Optional field that indicates the prefix length of the internal IPv6 + address range, should be used together with + --internal-ipv6-address=fd20::. Only /96 IP address range is supported + and the default value is 96. If not set, then either the prefix length + from --internal-ipv6-address=fd20::/96 will be used or the default + value of 96 will be assigned. + + --ipv6-network-tier=IPV6_NETWORK_TIER + Specifies the IPv6 network tier that will be used to configure the + instance network interface IPv6 access config. IPV6_NETWORK_TIER must + be (only one value is supported): + + PREMIUM + High quality, Google-grade network tier. + + --network=NETWORK + Specifies the network this network interface belongs to. + + --network-attachment=NETWORK_ATTACHMENT + The network attachment URL this network interface should connect to. + + --network-tier=NETWORK_TIER + Specifies the network tier that will be used to configure the instance + network interface. NETWORK_TIER must be one of: PREMIUM, STANDARD, + FIXED_STANDARD. The default value is PREMIUM. NETWORK_TIER must be one + of: + + FIXED_STANDARD + Public internet quality with fixed bandwidth. + PREMIUM + High quality, Google-grade network tier. + STANDARD + Public internet quality. + + --parent-nic-name=PARENT_NIC_NAME + Name of the parent network interface of a dynamic network interface. + + --private-network-ip=PRIVATE_NETWORK_IP + Specifies the RFC1918 IP to assign to the network interface. The IP + should be in the subnet IP range. + + --stack-type=STACK_TYPE + The stack type for the network interface. Determines if IPv6 is enabled + on the network interface. STACK_TYPE must be one of: + + IPV4_IPV6 + 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. + + --subnetwork=SUBNETWORK + Specifies the subnetwork this network interface belongs to. + + --vlan=VLAN + VLAN tag of a dynamic network interface, must be an integer in the + range from 2 to 255 inclusively. + + --zone=ZONE + Zone of the instance to operate on. If not specified, you might be + prompted to select a zone (interactive mode only). gcloud attempts to + identify the appropriate zone by searching for resources in your + currently active project. If the zone cannot be determined, gcloud + prompts you for a selection with all available Google Cloud Platform + zones. + + To avoid prompting when this flag is omitted, the user 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. + + At most one of these can be specified: + + --address=ADDRESS + Assigns the given external address to the network interface. The + address might be an IP address or the name or URI of an address + resource. Specifying an empty string will assign an ephemeral IP. + Mutually exclusive with no-address. If neither key is present the + network interface will get an ephemeral IP. + + --no-address + If specified the network interface will have no external IP. Mutually + exclusive with address. If neither key is present the network + interfaces will get an ephemeral IP. + +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 instances network-interfaces add + + $ gcloud beta compute instances network-interfaces add + diff --git a/gcloud/compute/instances/network-interfaces/delete b/gcloud/compute/instances/network-interfaces/delete new file mode 100644 index 000000000..f91cbdf38 --- /dev/null +++ b/gcloud/compute/instances/network-interfaces/delete @@ -0,0 +1,67 @@ +NAME + gcloud compute instances network-interfaces delete - delete a Dynamic + Network Interface from a Compute Engine instance + +SYNOPSIS + gcloud compute instances network-interfaces delete INSTANCE_NAME + --network-interface=NETWORK_INTERFACE [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute instances network-interfaces delete deletes a Dynamic + Network Interface from a Compute Engine instance. + +EXAMPLES + To delete a Dynamic Network Interface from a Compute Engine instance, run: $ gcloud compute instances network-interfaces delete instance-name \ + --network-interface=nic1.2 + +POSITIONAL ARGUMENTS + INSTANCE_NAME + Name of the instance to operate on. For details on valid instance + names, refer to the criteria documented under the field 'name' at: + https://cloud.google.com/compute/docs/reference/rest/v1/instances + +REQUIRED FLAGS + --network-interface=NETWORK_INTERFACE + The name of the network interface to delete, e.g. nic1.2 + +OPTIONAL FLAGS + --zone=ZONE + Zone of the instance to operate on. If not specified, you might be + prompted to select a zone (interactive mode only). gcloud attempts to + identify the appropriate zone by searching for resources in your + currently active project. If the zone cannot be determined, gcloud + prompts you for a selection with all available Google Cloud Platform + zones. + + To avoid prompting when this flag is omitted, the user 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 instances network-interfaces delete + + $ gcloud beta compute instances network-interfaces delete + diff --git a/gcloud/compute/instances/network-interfaces/help b/gcloud/compute/instances/network-interfaces/help index b46a5c9c1..132aca231 100644 --- a/gcloud/compute/instances/network-interfaces/help +++ b/gcloud/compute/instances/network-interfaces/help @@ -23,6 +23,12 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add + Add a Dynamic Network Interface to a Compute Engine instance. + + delete + Delete a Dynamic Network Interface from a Compute Engine instance. + get-effective-firewalls Get the effective firewalls for a Compute Engine virtual machine network interface. diff --git a/gcloud/compute/networks/subnets/describe b/gcloud/compute/networks/subnets/describe index f62a9f681..bb60b7f60 100644 --- a/gcloud/compute/networks/subnets/describe +++ b/gcloud/compute/networks/subnets/describe @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud compute networks subnets describe NAME [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--view=VIEW] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute networks subnets describe displays all data associated with @@ -40,6 +40,15 @@ FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + --view=VIEW + Specifies the information to include in the output. VIEW must be (only + one value is supported): + + WITH_UTILIZATION + Output includes the IP address utilization data of all subnetwork + ranges, showing total allocated and free IPv4 and IPv6 IP + addresses. + 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/networks/subnets/list b/gcloud/compute/networks/subnets/list index 67777ac43..84feadc6b 100644 --- a/gcloud/compute/networks/subnets/list +++ b/gcloud/compute/networks/subnets/list @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud compute networks subnets list [NAME ...] [--network=NETWORK] [--regexp=REGEXP, -r REGEXP] [--regions=REGION,[REGION,...]] - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--view=VIEW] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute networks subnets list displays all Google Compute Engine @@ -51,6 +52,15 @@ FLAGS --regions=REGION,[REGION,...] If provided, only resources from the given regions are queried. + --view=VIEW + Specifies the information to include in the output. VIEW must be (only + one value is supported): + + WITH_UTILIZATION + Output includes the IP address utilization data of all subnetwork + ranges, showing total allocated and free IPv4 and IPv6 IP + addresses. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/compute/reservations/update b/gcloud/compute/reservations/update index e7f60828a..e1d730438 100644 --- a/gcloud/compute/reservations/update +++ b/gcloud/compute/reservations/update @@ -7,7 +7,8 @@ SYNOPSIS [--[no-]enable-emergent-maintenance] [--remove-share-with=PROJECT,[PROJECT,...]] [--reservation-sharing-policy=RESERVATION_SHARING_POLICY] - [--vm-count=VM_COUNT] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--scheduling-type=SCHEDULING_TYPE] [--vm-count=VM_COUNT] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update Compute Engine reservations. @@ -66,6 +67,16 @@ FLAGS The reservation won't be shared with Google Cloud services. If you omit this flag during creation, the default value is DISALLOW_ALL. + --scheduling-type=SCHEDULING_TYPE + How Compute Engine schedules maintenance events for your reserved + hosts. SCHEDULING_TYPE must be one of: + + GROUPED + In GROUPED mode, maintenance is synchronized across all your VMs. + INDEPENDENT + In INDEPENDENT mode, your VMs have different, unsynchronized + maintenance schedules. + --vm-count=VM_COUNT The number of VM instances that are allocated to this reservation. The value of this field must be an int in the range [1, 1000]. diff --git a/gcloud/compute/tpus/execution-groups/create b/gcloud/compute/tpus/execution-groups/create index 064046f23..08ac08563 100644 --- a/gcloud/compute/tpus/execution-groups/create +++ b/gcloud/compute/tpus/execution-groups/create @@ -13,6 +13,14 @@ SYNOPSIS [--use-dl-images] [--use-with-notebook] [--vm-only] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (DEPRECATED) Create Google Compute TPUs along with VMs. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To create both TPU and VM, run: diff --git a/gcloud/compute/tpus/execution-groups/delete b/gcloud/compute/tpus/execution-groups/delete index e4e71f14d..7d799bb9c 100644 --- a/gcloud/compute/tpus/execution-groups/delete +++ b/gcloud/compute/tpus/execution-groups/delete @@ -6,6 +6,14 @@ SYNOPSIS gcloud compute tpus execution-groups delete EXECUTION_GROUP_NAME [--tpu-only] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (DEPRECATED) Delete TPU Node + VM created by execution group. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To delete both, the TPU and the VM, run: diff --git a/gcloud/compute/tpus/execution-groups/describe b/gcloud/compute/tpus/execution-groups/describe index a9d229947..2546101be 100644 --- a/gcloud/compute/tpus/execution-groups/describe +++ b/gcloud/compute/tpus/execution-groups/describe @@ -6,6 +6,14 @@ SYNOPSIS gcloud compute tpus execution-groups describe EXECUTION_GROUP_NAME [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (DEPRECATED) Describe Google Compute TPU + VM combination. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To describe the TPU and VM combination, run: diff --git a/gcloud/compute/tpus/execution-groups/help b/gcloud/compute/tpus/execution-groups/help index 61cfaad44..129120e19 100644 --- a/gcloud/compute/tpus/execution-groups/help +++ b/gcloud/compute/tpus/execution-groups/help @@ -6,7 +6,13 @@ SYNOPSIS gcloud compute tpus execution-groups COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Command group that helps create and manage Cloud TPUs and Compute VMs. + (DEPRECATED) Command group that helps create and manage Cloud TPUs and + Compute VMs. + + This command group is deprecated and will be removed in a future release. + We recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,16 +23,16 @@ COMMANDS COMMAND is one of the following: create - Create Google Compute TPUs along with VMs. + (DEPRECATED) Create Google Compute TPUs along with VMs. delete - Delete TPU Node + VM created by execution group. + (DEPRECATED) Delete TPU Node + VM created by execution group. describe - Describe Google Compute TPU + VM combination. + (DEPRECATED) Describe Google Compute TPU + VM combination. list - List TPU Node+VM groups created by execution group. + (DEPRECATED) List TPU Node+VM groups created by execution group. NOTES These variants are also available: diff --git a/gcloud/compute/tpus/execution-groups/list b/gcloud/compute/tpus/execution-groups/list index 5e1299b1a..44b89d610 100644 --- a/gcloud/compute/tpus/execution-groups/list +++ b/gcloud/compute/tpus/execution-groups/list @@ -7,6 +7,14 @@ SYNOPSIS [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] +DESCRIPTION + (DEPRECATED) List TPU Node+VM groups created by execution group. + + This command is deprecated and will be removed in a future release. We + recommend that you use the TPU-VM or Queued Resource API. See + https://cloud.google.com/tpu/docs/managing-tpus-tpu-vm for more + information. + EXAMPLES To list all active execution groups, run: diff --git a/gcloud/compute/tpus/help b/gcloud/compute/tpus/help index a82782a19..38b342ea7 100644 --- a/gcloud/compute/tpus/help +++ b/gcloud/compute/tpus/help @@ -25,7 +25,8 @@ GROUPS List or Describe Available Cloud TPU accelerator types. execution-groups - Command group that helps create and manage Cloud TPUs and Compute VMs. + (DEPRECATED) Command group that helps create and manage Cloud TPUs and + Compute VMs. locations List or Describe Available Cloud TPU Locations. diff --git a/gcloud/compute/vpn-tunnels/create b/gcloud/compute/vpn-tunnels/create index 0136ab195..af9762e02 100644 --- a/gcloud/compute/vpn-tunnels/create +++ b/gcloud/compute/vpn-tunnels/create @@ -14,9 +14,15 @@ SYNOPSIS [--description=DESCRIPTION] [--ike-version=IKE_VERSION] [--interface=INTERFACE] [--local-traffic-selector=CIDR,[CIDR,...]] [--peer-external-gateway-interface=PEER_EXTERNAL_GATEWAY_INTERFACE] - [--region=REGION] [--remote-traffic-selector=CIDR,[CIDR,...]] - [--router=ROUTER] [--router-region=ROUTER_REGION] - [GCLOUD_WIDE_FLAG ...] + [--phase1-dh=GROUPS,[GROUPS,...]] + [--phase1-encryption=ALGORITHMS,[ALGORITHMS,...]] + [--phase1-integrity=ALGORITHMS,[ALGORITHMS,...]] + [--phase1-prf=PSEUDORANDOM FUNCTIONS,[...]] + [--phase2-encryption=ALGORITHMS,[ALGORITHMS,...]] + [--phase2-integrity=ALGORITHMS,[ALGORITHMS,...]] + [--phase2-pfs=ALGORITHMS,[ALGORITHMS,...]] [--region=REGION] + [--remote-traffic-selector=CIDR,[CIDR,...]] [--router=ROUTER] + [--router-region=ROUTER_REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute vpn-tunnels create is used to create a Classic VPN tunnel @@ -110,6 +116,27 @@ OPTIONAL FLAGS a Highly Available VPN gateway to an External Vpn Gateway. PEER_EXTERNAL_GATEWAY_INTERFACE must be one of: 0, 1, 2, 3. + --phase1-dh=GROUPS,[GROUPS,...] + Phase 1 Diffie-Hellman groups. + + --phase1-encryption=ALGORITHMS,[ALGORITHMS,...] + Phase 1 encryption algorithms. + + --phase1-integrity=ALGORITHMS,[ALGORITHMS,...] + Phase 1 integrity algorithms. + + --phase1-prf=PSEUDORANDOM FUNCTIONS,[...] + Phase 1 pseudorandom functions. + + --phase2-encryption=ALGORITHMS,[ALGORITHMS,...] + Phase 2 encryption algorithms. + + --phase2-integrity=ALGORITHMS,[ALGORITHMS,...] + Phase 2 integrity algorithms. + + --phase2-pfs=ALGORITHMS,[ALGORITHMS,...] + Phase 2 perfect forward secerecy algorithms. + --region=REGION Region of the VPN Tunnel to create. If not specified, you might be prompted to select a region (interactive mode only). diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 026a37275..ad2492621 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -1349,7 +1349,9 @@ FLAGS cpuManagerPolicy either 'static' or 'none' cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') + cpuCFSQuotaPeriod interval (e.g., '100ms'. The + value must be between 1ms and 1 + second, inclusive.) memoryManager specify memory manager policy topologyManager specify topology manager policy and scope @@ -1359,7 +1361,7 @@ FLAGS containerLogMaxSize positive number plus unit suffix (e.g., '100Mi', '0.2Gi'. The value must be between 10Mi and - 500Mi.) + 500Mi, inclusive.) containerLogMaxFiles integer (The value must be between [2, 10].) imageGcLowThresholdPercent integer (The value must be diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index e2a722925..49d8f3c6f 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -776,7 +776,9 @@ FLAGS cpuManagerPolicy either 'static' or 'none' cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') + cpuCFSQuotaPeriod interval (e.g., '100ms'. The + value must be between 1ms and 1 + second, inclusive.) memoryManager specify memory manager policy topologyManager specify topology manager policy and scope @@ -786,7 +788,7 @@ FLAGS containerLogMaxSize positive number plus unit suffix (e.g., '100Mi', '0.2Gi'. The value must be between 10Mi and - 500Mi.) + 500Mi, inclusive.) containerLogMaxFiles integer (The value must be between [2, 10].) imageGcLowThresholdPercent integer (The value must be diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index af7e25555..ac465355c 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -318,7 +318,9 @@ REQUIRED FLAGS cpuManagerPolicy either 'static' or 'none' cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') + cpuCFSQuotaPeriod interval (e.g., '100ms'. The + value must be between 1ms and + 1 second, inclusive.) memoryManager specify memory manager policy topologyManager specify topology manager policy and scope @@ -328,7 +330,8 @@ REQUIRED FLAGS containerLogMaxSize positive number plus unit suffix (e.g., '100Mi', '0.2Gi'. The value must be - between 10Mi and 500Mi.) + between 10Mi and 500Mi, + inclusive.) containerLogMaxFiles integer (The value must be between [2, 10].) imageGcLowThresholdPercent integer (The value must be diff --git a/gcloud/iap/oauth-brands/create b/gcloud/iap/oauth-brands/create index 1d9a22d74..22407b84b 100644 --- a/gcloud/iap/oauth-brands/create +++ b/gcloud/iap/oauth-brands/create @@ -6,7 +6,11 @@ SYNOPSIS --support_email=SUPPORT_EMAIL [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) This command is deprecated. + (DEPRECATED) This command is deprecated and will be non-functional after + the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud iap oauth-brands create is used to create a Cloud OAuth brand for the project. The brand is 'internal only', meaning OAuth clients created diff --git a/gcloud/iap/oauth-brands/describe b/gcloud/iap/oauth-brands/describe index 25e006626..207278862 100644 --- a/gcloud/iap/oauth-brands/describe +++ b/gcloud/iap/oauth-brands/describe @@ -5,7 +5,11 @@ SYNOPSIS gcloud iap oauth-brands describe NAME [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) This command is deprecated. + (DEPRECATED) This command is deprecated and will be non-functional after + the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud iap oauth-brands describe is used to describe a Cloud OAuth brand. diff --git a/gcloud/iap/oauth-brands/help b/gcloud/iap/oauth-brands/help index f0e9adb07..75d6026bd 100644 --- a/gcloud/iap/oauth-brands/help +++ b/gcloud/iap/oauth-brands/help @@ -7,7 +7,11 @@ SYNOPSIS DESCRIPTION (DEPRECATED) Manage IAP OAuth brands. - This command is deprecated. + This command is deprecated and will be non-functional after the IAP OAuth + Admin APIs are turned down. Jan 19, 2026: Google will discontinue support + for the IAP OAuth Admin APIs. New projects will not be able to use these + APIs. March 19, 2026: The IAP OAuth Admin APIs will be permanently shut + down. Access to this feature will no longer be available. GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/iap/oauth-brands/list b/gcloud/iap/oauth-brands/list index 17afcc036..a98cd2aee 100644 --- a/gcloud/iap/oauth-brands/list +++ b/gcloud/iap/oauth-brands/list @@ -6,7 +6,11 @@ SYNOPSIS [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) This command is deprecated. + (DEPRECATED) This command is deprecated and will be non-functional after + the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud iap oauth-brands list is used to list the Cloud OAuth brand in the project. diff --git a/gcloud/iap/oauth-clients/create b/gcloud/iap/oauth-clients/create index 5da23f886..5d0399f90 100644 --- a/gcloud/iap/oauth-clients/create +++ b/gcloud/iap/oauth-clients/create @@ -7,7 +7,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) This command is deprecated. + (DEPRECATED) This command is deprecated and will be non-functional after + the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud iap oauth-clients create is used to create an OAuth client in the project to be used by Cloud IAP. To call this command, the Cloud OAuth diff --git a/gcloud/iap/oauth-clients/delete b/gcloud/iap/oauth-clients/delete index df85913e0..932110061 100644 --- a/gcloud/iap/oauth-clients/delete +++ b/gcloud/iap/oauth-clients/delete @@ -6,7 +6,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) This command is deprecated. + (DEPRECATED) This command is deprecated and will be non-functional after + the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud iap oauth-clients delete is used to delete a Cloud IAP OAuth client. Note this command cannot be used to delete any other type of OAuth client diff --git a/gcloud/iap/oauth-clients/describe b/gcloud/iap/oauth-clients/describe index 6bd15812b..51052d7b2 100644 --- a/gcloud/iap/oauth-clients/describe +++ b/gcloud/iap/oauth-clients/describe @@ -6,7 +6,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) This command is deprecated. + (DEPRECATED) This command is deprecated and will be non-functional after + the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud iap oauth-clients describe is used to describe a Cloud IAP OAuth client. Note this command cannot be used to describe any other type of diff --git a/gcloud/iap/oauth-clients/help b/gcloud/iap/oauth-clients/help index 5cac67c6d..42a3c0e2b 100644 --- a/gcloud/iap/oauth-clients/help +++ b/gcloud/iap/oauth-clients/help @@ -7,7 +7,11 @@ SYNOPSIS DESCRIPTION (DEPRECATED) Manage IAP OAuth clients. - This command is deprecated. + This command is deprecated and will be non-functional after the IAP OAuth + Admin APIs are turned down. Jan 19, 2026: Google will discontinue support + for the IAP OAuth Admin APIs. New projects will not be able to use these + APIs. March 19, 2026: The IAP OAuth Admin APIs will be permanently shut + down. Access to this feature will no longer be available. Manage OAuth clients that are used by Cloud Identity-Aware Proxy. Note this API cannot be used as a generic management API for all OAuth clients in diff --git a/gcloud/iap/oauth-clients/list b/gcloud/iap/oauth-clients/list index 8a137f3b9..55b58ad46 100644 --- a/gcloud/iap/oauth-clients/list +++ b/gcloud/iap/oauth-clients/list @@ -7,7 +7,11 @@ SYNOPSIS [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) This command is deprecated. + (DEPRECATED) This command is deprecated and will be non-functional after + the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud iap oauth-clients list is used to list Cloud IAP OAuth clients in a Cloud OAuth brand. Note this command will not list any other type of OAuth diff --git a/gcloud/iap/oauth-clients/reset-secret b/gcloud/iap/oauth-clients/reset-secret index 5ab0f81e7..b678c77f9 100644 --- a/gcloud/iap/oauth-clients/reset-secret +++ b/gcloud/iap/oauth-clients/reset-secret @@ -7,7 +7,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) This command is deprecated. + (DEPRECATED) This command is deprecated and will be non-functional after + the IAP OAuth Admin APIs are turned down. Jan 19, 2026: Google will + discontinue support for the IAP OAuth Admin APIs. New projects will not be + able to use these APIs. March 19, 2026: The IAP OAuth Admin APIs will be + permanently shut down. Access to this feature will no longer be available. gcloud iap oauth-clients reset-secret is used to reset a Cloud IAP OAuth client secret. Note this command cannot be used to reset the secret for any diff --git a/gcloud/managed-kafka/connect-clusters/create b/gcloud/managed-kafka/connect-clusters/create new file mode 100644 index 000000000..a1c9cce0d --- /dev/null +++ b/gcloud/managed-kafka/connect-clusters/create @@ -0,0 +1,148 @@ +NAME + gcloud managed-kafka connect-clusters create - create a Managed Service for + Apache Kafka connect cluster + +SYNOPSIS + gcloud managed-kafka connect-clusters create + (CONNECT_CLUSTER : --location=LOCATION) --cpu=CPU + --kafka-cluster=KAFKA_CLUSTER --memory=MEMORY + --primary-subnet=PRIMARY_SUBNET [--additional-subnet=ADDITIONAL_SUBNET] + [--async] [--dns-name=DNS_NAME] [--labels=[KEY=VALUE,...]] + [--secret=SECRET] + [--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Managed Service for Apache Kafka connect cluster. + +EXAMPLES + To create a connector cluster, run the following: + + $ gcloud managed-kafka connect-clusters create myconnectorCluster \ + --location=us-central1 --cpu=3 --memory=3GiB \ + --primary-subnet=projects/PROJECT_ID/regions/us-central1/\ + subnetworks/default --kafka-cluster=my-kafka-cluster OR \ + --kafka-cluster=projects/PROJECT_ID/locations/us-central1/\ + clusters/my-kafka-cluster + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the connect cluster that is created. + 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 connect_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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --cpu=CPU + The number of vCPUs to provision for the cluster. The minimum is 3. + + --kafka-cluster=KAFKA_CLUSTER + The resource path of the Kafka cluster to connect to, or the name of + the Kafka cluster to connect to if the cluster is in the same project + as the Connect cluster. + + --memory=MEMORY + The memory to provision for the cluster in bytes. The value must be + between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. + + --primary-subnet=PRIMARY_SUBNET + VPC subnet to make available to the Kafka Connect cluster. Structured + like: projects/{project}/regions/{region}/subnetworks/{subnet_id}. The + primary subnet is used to create a Private Service Connect (PSC) + interface for the Kafka Connect workers. It must be located in the same + region as the Connect cluster. + +OPTIONAL FLAGS + --additional-subnet=ADDITIONAL_SUBNET + Additional subnet to make available to the Kafka Connect cluster. + Structured like: + projects/{project}/regions/{region}/subnetworks/{subnet_id}. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --dns-name=DNS_NAME + DNS domain name from the subnet's network to be made visible to the + Connect Cluster. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. Keys must start with a lowercase + character and contain only hyphens (-), underscores (_), lowercase + characters, and numbers. Values must contain only hyphens (-), + underscores (_), lowercase characters, and numbers. + + --secret=SECRET + Secrets to load into workers. Exact SecretVersions from Secret Manager + must be provided -- aliases are not supported. Up to 32 secrets may be + loaded into one cluster. Format: + projects//secrets//versions/ + + At most one of these can be specified: + + --config-file=JSON|YAML|FILE + The path to the JSON or YAML file containing the configuration that + are overridden from the cluster or connector defaults. This also + supports inline JSON or YAML. Sets config_file value. + + Input Example: + + --config-file=string + + File Example: + + --config-file=path_to_file.(yaml|json) + + --configs=[KEY=VALUE,...] + Configuration for the connect cluster that are overridden from the + cluster defaults. The key of the map is a Kafka topic property name, + for example: cleanup.policy=compact,compression.type=producer. + +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 managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connect-clusters create + + $ gcloud beta managed-kafka connect-clusters create + diff --git a/gcloud/managed-kafka/connect-clusters/delete b/gcloud/managed-kafka/connect-clusters/delete new file mode 100644 index 000000000..c5403821d --- /dev/null +++ b/gcloud/managed-kafka/connect-clusters/delete @@ -0,0 +1,79 @@ +NAME + gcloud managed-kafka connect-clusters delete - delete a Managed Service for + Apache Kafka connect cluster + +SYNOPSIS + gcloud managed-kafka connect-clusters delete + (CONNECT_CLUSTER : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Managed Service for Apache Kafka connect cluster. + +EXAMPLES + To delete a connect cluster named myconnectcluster located in us-central1, + run the following: + + $ gcloud managed-kafka connect-clusters delete myconnectcluster \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the connect cluster for deletion. + 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 connect_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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connect-clusters delete + + $ gcloud beta managed-kafka connect-clusters delete + diff --git a/gcloud/managed-kafka/connect-clusters/describe b/gcloud/managed-kafka/connect-clusters/describe new file mode 100644 index 000000000..71d259fc2 --- /dev/null +++ b/gcloud/managed-kafka/connect-clusters/describe @@ -0,0 +1,73 @@ +NAME + gcloud managed-kafka connect-clusters describe - describe a Managed Service + for Apache Kafka connect cluster + +SYNOPSIS + gcloud managed-kafka connect-clusters describe + (CONNECT_CLUSTER : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Managed Service for Apache Kafka for BigQuery connect cluster. + +EXAMPLES + To describe a connect cluster named myconnectcluster located in + us-central1, run the following: + + $ gcloud managed-kafka connect-clusters describe myconnectcluster \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the connect cluster. 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 connect_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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connect-clusters describe + + $ gcloud beta managed-kafka connect-clusters describe + diff --git a/gcloud/managed-kafka/connect-clusters/help b/gcloud/managed-kafka/connect-clusters/help new file mode 100644 index 000000000..2737ee85f --- /dev/null +++ b/gcloud/managed-kafka/connect-clusters/help @@ -0,0 +1,41 @@ +NAME + gcloud managed-kafka connect-clusters - administer Managed Service for + Apache Kafka connect-clusters + +SYNOPSIS + gcloud managed-kafka connect-clusters COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Administer Managed Service for Apache Kafka connect-clusters. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Managed Service for Apache Kafka connect cluster. + + delete + Delete a Managed Service for Apache Kafka connect cluster. + + describe + Describe a Managed Service for Apache Kafka connect cluster. + + list + List all Managed Service for Apache Kafka connect clusters in a given + location. + + update + Update a Managed Service for Apache Kafka for BigQuery connect cluster. + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connect-clusters + + $ gcloud beta managed-kafka connect-clusters + diff --git a/gcloud/managed-kafka/connect-clusters/list b/gcloud/managed-kafka/connect-clusters/list new file mode 100644 index 000000000..bdefa82a3 --- /dev/null +++ b/gcloud/managed-kafka/connect-clusters/list @@ -0,0 +1,86 @@ +NAME + gcloud managed-kafka connect-clusters list - list all Managed Service for + Apache Kafka connect clusters in a given location + +SYNOPSIS + gcloud managed-kafka connect-clusters list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all Managed Service for Apache Kafka connect clusters in a given + location. To specify the maximum number of clusters to list, use the + --limit flag. + +EXAMPLES + To list all connect clusters in a given location, such as us-central1, run + the following: + + $ gcloud managed-kafka connect-clusters list --location=us-central1 + +REQUIRED FLAGS + Location resource - Identifies the region which contains all the connector + clusters to be listed. This represents a Cloud resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connect-clusters list + + $ gcloud beta managed-kafka connect-clusters list + diff --git a/gcloud/managed-kafka/connect-clusters/update b/gcloud/managed-kafka/connect-clusters/update new file mode 100644 index 000000000..b73aeaa26 --- /dev/null +++ b/gcloud/managed-kafka/connect-clusters/update @@ -0,0 +1,174 @@ +NAME + gcloud managed-kafka connect-clusters update - update a Managed Service for + Apache Kafka for BigQuery connect cluster + +SYNOPSIS + gcloud managed-kafka connect-clusters update + (CONNECT_CLUSTER : --location=LOCATION) + (--cpu=CPU --memory=MEMORY --clear-configs + | --config-file=JSON|YAML|FILE + | --configs=[KEY=VALUE,...] --clear-dns-names + | --dns-name=DNS_NAME --clear-labels + | --labels=[KEY=VALUE,...] --clear-secrets + | --secret=SECRET [--primary-subnet=PRIMARY_SUBNET + : --additional-subnet=ADDITIONAL_SUBNET]) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an Managed Service for Apache Kafka for BigQuery connect cluster. + +EXAMPLES + To update a connect cluster, run the following: + + $ gcloud managed-kafka connect-clusters update myconnectorCluster \ + --location=us-central1 --configs=KEY1=VALUE1,KEY2=VALUE2... OR \ + --config-file=my-config-file.yaml --cpu=3 --memory=3GiB \ + --primary-subnet=projects/my-project/regions/us-central1/\ + subnetworks/default/1 \ + --additional-subnet=projects/my-project/regions/us-central1/\ + subnetworks/default/2 \ + --dns-name=bootstrap.myconnectorCluster.us-central1.managedkafka\ + .my-project.cloud.goog:9092 \ + --secret=projects/my-project/secrets/my-secret/versions/1 \ + --labels=KEY1=VALUE1,KEY2=VALUE2... + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the connect cluster for which the + command 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 connect_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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + At least one of these must be specified: + + --cpu=CPU + The number of vCPUs to provision for the cluster. The minimum is 3. + + --memory=MEMORY + The memory to provision for the cluster in bytes. The value must be + between 1 GiB and 8 GiB per vCPU. Ex. 1024Mi, 4Gi. + + At most one of these can be specified: + + --clear-configs + Remove all the configurations for the topic. + + --config-file=JSON|YAML|FILE + The path to the JSON or YAML file containing the configuration that + are overridden from the cluster or connector defaults. This also + supports inline JSON or YAML. Sets config_file value. + + Input Example: + + --config-file=string + + File Example: + + --config-file=path_to_file.(yaml|json) + + --configs=[KEY=VALUE,...] + Configuration for the connect cluster that are overridden from the + cluster defaults. The key of the map is a Kafka topic property + name, for example: + cleanup.policy=compact,compression.type=producer. + + At most one of these can be specified: + + --clear-dns-names + Remove all the DNS domain names for the connect cluster. + + --dns-name=DNS_NAME + DNS domain name from the subnet's network to be made visible to the + Connect Cluster. + + At most one of these can be specified: + + --clear-labels + Remove all the labels from the connect cluster. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. Keys must start with a + lowercase character and contain only hyphens (-), underscores (_), + lowercase characters, and numbers. Values must contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + At most one of these can be specified: + + --clear-secrets + Remove all the secrets from the connect cluster. + + --secret=SECRET + Secrets to load into workers. Exact SecretVersions from Secret + Manager must be provided -- aliases are not supported. Up to 32 + secrets may be loaded into one cluster. Format: + projects//secrets//versions/ + + --primary-subnet=PRIMARY_SUBNET + VPC subnet to make available to the Kafka Connect cluster. Structured + like: projects/{project}/regions/{region}/subnetworks/{subnet_id}. + The primary subnet is used to create a Private Service Connect (PSC) + interface for the Kafka Connect workers. It must be located in the + same region as the Connect cluster. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --additional-subnet=ADDITIONAL_SUBNET + Additional subnet to make available to the Kafka Connect cluster. + Structured like: + projects/{project}/regions/{region}/subnetworks/{subnet_id}. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connect-clusters update + + $ gcloud beta managed-kafka connect-clusters update + diff --git a/gcloud/managed-kafka/connectors/create b/gcloud/managed-kafka/connectors/create new file mode 100644 index 000000000..5bfc08eb2 --- /dev/null +++ b/gcloud/managed-kafka/connectors/create @@ -0,0 +1,126 @@ +NAME + gcloud managed-kafka connectors create - create a Managed Service for + Apache Kafka connector + +SYNOPSIS + gcloud managed-kafka connectors create + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + (--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]) + [--task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF + --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Managed Service for Apache Kafka connector. + +EXAMPLES + To create a connector, run the following: + + $ gcloud managed-kafka connectors create myconnector \ + --location=us-central1 --connect-cluster=mycluster \ + --configs=connector.class="com.google.pubsub.kafka.source.CloudP\ + ubSubSourceConnector",cps.subscription="my-subscription",... \ + [--task-restart-min-backoff=60s] \ + [--task-restart-max-backoff=30m] OR + $ gcloud managed-kafka connectors create myconnector \ + --location=us-central1 --connect-cluster=mycluster \ + --config-file=my-config-file.yaml \ + [--task-restart-min-backoff=60s] \ + [--task-restart-max-backoff=30m] + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector for which the command 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --config-file=JSON|YAML|FILE + The path to the JSON or YAML file containing the configuration that + are overridden from the connector defaults. This also supports inline + JSON or YAML. Sets config_file value. + + Input Example: + + --config-file=string + + File Example: + + --config-file=path_to_file.(yaml|json) + + --configs=[KEY=VALUE,...] + Configuration for the connector that are overridden from the + connector defaults. The key of the map is a Kafka topic property + name, for example: cleanup.policy=compact,compression.type=producer. + +OPTIONAL FLAGS + --task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF + The maximum amount of time to wait before retrying a failed task in + seconds. This sets an upper bound for the backoff delay. The default + value is 1800s (30 minutes). See $ gcloud topic datetimes for + information on duration formats. + + --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF + The minimum amount of time to wait before retrying a failed task in + seconds. This sets a lower bound for the backoff delay. The default + value is 60s. See $ gcloud topic datetimes for information on duration + formats. + +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 managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connectors create + + $ gcloud beta managed-kafka connectors create + diff --git a/gcloud/managed-kafka/connectors/delete b/gcloud/managed-kafka/connectors/delete new file mode 100644 index 000000000..ed5099c8a --- /dev/null +++ b/gcloud/managed-kafka/connectors/delete @@ -0,0 +1,81 @@ +NAME + gcloud managed-kafka connectors delete - delete a Managed Service for + Apache Kafka connector + +SYNOPSIS + gcloud managed-kafka connectors delete + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Managed Service for Apache Kafka connector. + +EXAMPLES + To delete a connector named myconnector located in us-central1, run the + following: + + $ gcloud managed-kafka connectors delete myconnector \ + --location=us-central1 --connect-cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the cluster for deletion. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connectors delete + + $ gcloud beta managed-kafka connectors delete + diff --git a/gcloud/managed-kafka/connectors/describe b/gcloud/managed-kafka/connectors/describe new file mode 100644 index 000000000..3f3df923c --- /dev/null +++ b/gcloud/managed-kafka/connectors/describe @@ -0,0 +1,81 @@ +NAME + gcloud managed-kafka connectors describe - describe a Managed Service for + Apache Kafka connector + +SYNOPSIS + gcloud managed-kafka connectors describe + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Managed Service for Apache Kafka connector. + +EXAMPLES + To describe a connector named myconnector located in us-central1, run the + following: + + $ gcloud managed-kafka connectors describe myconnector \ + --location=us-central1 --connect-cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector for details to be displayed. + 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connectors describe + + $ gcloud beta managed-kafka connectors describe + diff --git a/gcloud/managed-kafka/connectors/help b/gcloud/managed-kafka/connectors/help new file mode 100644 index 000000000..af8c9550d --- /dev/null +++ b/gcloud/managed-kafka/connectors/help @@ -0,0 +1,54 @@ +NAME + gcloud managed-kafka connectors - administer Managed Service for Apache + Kafka connectors + +SYNOPSIS + gcloud managed-kafka connectors COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Administer Managed Service for Apache Kafka connectors. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Managed Service for Apache Kafka connector. + + delete + Delete a Managed Service for Apache Kafka connector. + + describe + Describe a Managed Service for Apache Kafka connector. + + list + List all Managed Service for Apache Kafka connectors for a given + connect cluster. + + pause + Pauses operation of a Managed Service for Apache Kafka connector. + + restart + Restarts a Managed Service for Apache Kafka connector. + + resume + Resumes operation of a stopped Managed Service for Apache Kafka + connector. + + stop + Stops operation of a Managed Service for Apache Kafka connector. + + update + Update a Managed Service for Apache Kafka connector. + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connectors + + $ gcloud beta managed-kafka connectors + diff --git a/gcloud/managed-kafka/connectors/list b/gcloud/managed-kafka/connectors/list new file mode 100644 index 000000000..001c4766d --- /dev/null +++ b/gcloud/managed-kafka/connectors/list @@ -0,0 +1,103 @@ +NAME + gcloud managed-kafka connectors list - list all Managed Service for Apache + Kafka connectors for a given connect cluster + +SYNOPSIS + gcloud managed-kafka connectors list + (CONNECT_CLUSTER : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all Managed Service for Apache Kafka connectors for a given connect + cluster. To specify the maximum number of connectors to list, use the + --limit flag. + +EXAMPLES + To list all Managed Service for Apache Kafka connectors belonging to the + "mycluster" connect cluster in us-central1, run the following: + + $ gcloud managed-kafka connectors list mycluster \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Connect cluster resource - Identifies the cluster which contains all the + connectors to be listed. 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 connect_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. + + CONNECT_CLUSTER + ID of the connect_cluster or fully qualified identifier for the + connect_cluster. + + To set the connect_cluster attribute: + ▸ provide the argument connect_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connect_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connectors list + + $ gcloud beta managed-kafka connectors list + diff --git a/gcloud/managed-kafka/connectors/pause b/gcloud/managed-kafka/connectors/pause new file mode 100644 index 000000000..d677097da --- /dev/null +++ b/gcloud/managed-kafka/connectors/pause @@ -0,0 +1,81 @@ +NAME + gcloud managed-kafka connectors pause - pauses operation of a Managed + Service for Apache Kafka connector + +SYNOPSIS + gcloud managed-kafka connectors pause + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Pauses operation of a Managed Service for Apache Kafka connector. + +EXAMPLES + To pause a connector named myconnector located in us-central1, run the + following: + + $ gcloud managed-kafka connectors pause myconnector \ + --location=us-central1 --connect-cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector to pause. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connectors pause + + $ gcloud beta managed-kafka connectors pause + diff --git a/gcloud/managed-kafka/connectors/restart b/gcloud/managed-kafka/connectors/restart new file mode 100644 index 000000000..ebcde473c --- /dev/null +++ b/gcloud/managed-kafka/connectors/restart @@ -0,0 +1,81 @@ +NAME + gcloud managed-kafka connectors restart - restarts a Managed Service for + Apache Kafka connector + +SYNOPSIS + gcloud managed-kafka connectors restart + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Restarts a Managed Service for Apache Kafka connector. + +EXAMPLES + To restart a connector named myconnector located in us-central1, run the + following: + + $ gcloud managed-kafka connectors restart myconnector \ + --location=us-central1 --connect-cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector to restart. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connectors restart + + $ gcloud beta managed-kafka connectors restart + diff --git a/gcloud/managed-kafka/connectors/resume b/gcloud/managed-kafka/connectors/resume new file mode 100644 index 000000000..59c54de9b --- /dev/null +++ b/gcloud/managed-kafka/connectors/resume @@ -0,0 +1,81 @@ +NAME + gcloud managed-kafka connectors resume - resumes operation of a stopped + Managed Service for Apache Kafka connector + +SYNOPSIS + gcloud managed-kafka connectors resume + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Resumes operation of a stopped Managed Service for Apache Kafka connector. + +EXAMPLES + To resume a connector named myconnector located in us-central1, run the + following: + + $ gcloud managed-kafka connectors resume myconnector \ + --location=us-central1 --connect-cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector to resume. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connectors resume + + $ gcloud beta managed-kafka connectors resume + diff --git a/gcloud/managed-kafka/connectors/stop b/gcloud/managed-kafka/connectors/stop new file mode 100644 index 000000000..68bcd41e7 --- /dev/null +++ b/gcloud/managed-kafka/connectors/stop @@ -0,0 +1,81 @@ +NAME + gcloud managed-kafka connectors stop - stops operation of a Managed Service + for Apache Kafka connector + +SYNOPSIS + gcloud managed-kafka connectors stop + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Stops operation of a Managed Service for Apache Kafka connector. + +EXAMPLES + To stop a connector named myconnector located in us-central1, run the + following: + + $ gcloud managed-kafka connectors stop myconnector \ + --location=us-central1 --connect-cluster=mycluster + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector to resume. 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connectors stop + + $ gcloud beta managed-kafka connectors stop + diff --git a/gcloud/managed-kafka/connectors/update b/gcloud/managed-kafka/connectors/update new file mode 100644 index 000000000..2414e269d --- /dev/null +++ b/gcloud/managed-kafka/connectors/update @@ -0,0 +1,122 @@ +NAME + gcloud managed-kafka connectors update - update a Managed Service for + Apache Kafka connector + +SYNOPSIS + gcloud managed-kafka connectors update + (CONNECTOR : --connect-cluster=CONNECT_CLUSTER --location=LOCATION) + [--config-file=JSON|YAML|FILE | --configs=[KEY=VALUE,...]] + [--task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF + --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Managed Service for Apache Kafka connector. + +EXAMPLES + To update a connector name myconnector, run the following: + + $ gcloud managed-kafka connectors update myconnector \ + --location=us-central1 --configs=KEY1=VALUE1,KEY2=VALUE2... \ + --connect-cluster=mycluster [--task-restart-min-backoff=60s] \ + [--task-restart-max-backoff=30m] OR + $ gcloud managed-kafka connectors update myconnector \ + --location=us-central1 --config-file=my-config-file.yaml \ + --connect-cluster=mycluster [--task-restart-min-backoff=60s] \ + [--task-restart-max-backoff=30m] + +POSITIONAL ARGUMENTS + Connector resource - Identifies the connector for which the command 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 connector 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. + + CONNECTOR + ID of the connector or fully qualified identifier for the connector. + + To set the connector attribute: + ▸ provide the argument connector on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connect-cluster=CONNECT_CLUSTER + The connect cluster name. + + To set the connect-cluster attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --connect-cluster on the command line. + + --location=LOCATION + ID of the location of the Managed Service for Apache Kafka resource. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. + + To set the location attribute: + ▸ provide the argument connector on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + At most one of these can be specified: + + --config-file=JSON|YAML|FILE + The path to the JSON or YAML file containing the configuration that + are overridden from the connector defaults. This also supports inline + JSON or YAML. Sets config_file value. + + Input Example: + + --config-file=string + + File Example: + + --config-file=path_to_file.(yaml|json) + + --configs=[KEY=VALUE,...] + Configuration for the connector that are overridden from the + connector defaults. The key of the map is a Kafka topic property + name, for example: cleanup.policy=compact,compression.type=producer. + + --task-restart-max-backoff=TASK_RESTART_MAX_BACKOFF + The maximum amount of time to wait before retrying a failed task in + seconds. This sets an upper bound for the backoff delay. The default + value is 1800s (30 minutes). See $ gcloud topic datetimes for + information on duration formats. + + --task-restart-min-backoff=TASK_RESTART_MIN_BACKOFF + The minimum amount of time to wait before retrying a failed task in + seconds. This sets a lower bound for the backoff delay. The default + value is 60s. See $ gcloud topic datetimes for information on duration + formats. + +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 managedkafka/v1 API. The full documentation for this + API can be found at: + https://cloud.google.com/managed-service-for-apache-kafka/docs + +NOTES + These variants are also available: + + $ gcloud alpha managed-kafka connectors update + + $ gcloud beta managed-kafka connectors update + diff --git a/gcloud/managed-kafka/help b/gcloud/managed-kafka/help index 9a3edaae4..adfc36679 100644 --- a/gcloud/managed-kafka/help +++ b/gcloud/managed-kafka/help @@ -23,6 +23,12 @@ GROUPS clusters Administer Managed Service for Apache Kafka clusters. + connect-clusters + Administer Managed Service for Apache Kafka connect-clusters. + + connectors + Administer Managed Service for Apache Kafka connectors. + consumer-groups Administer Managed Service for Apache Kafka consumer groups. diff --git a/gcloud/network-security/authz-policies/delete b/gcloud/network-security/authz-policies/delete new file mode 100644 index 000000000..62615bf54 --- /dev/null +++ b/gcloud/network-security/authz-policies/delete @@ -0,0 +1,72 @@ +NAME + gcloud network-security authz-policies delete - delete an AuthzPolicy + resource + +SYNOPSIS + gcloud network-security authz-policies delete + (AUTHZ_POLICY : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete the specified AuthzPolicy resource. + +EXAMPLES + To delete an AuthzPolicy resource named my-authz-policy in us-central1, + run: + + $ gcloud network-security authz-policies delete my-authz-policy \ + --location=us-central1 + +POSITIONAL ARGUMENTS + AuthzPolicy resource - The ID of the deleted AuthzPolicy resource. 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 authz_policy 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. + + AUTHZ_POLICY + ID of the AuthzPolicy or fully qualified identifier for the + AuthzPolicy. + + To set the authz_policy attribute: + ▸ provide the argument authz_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument authz_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networksecurity/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + This variant is also available: + + $ gcloud beta network-security authz-policies delete + diff --git a/gcloud/network-security/authz-policies/describe b/gcloud/network-security/authz-policies/describe new file mode 100644 index 000000000..c717062f9 --- /dev/null +++ b/gcloud/network-security/authz-policies/describe @@ -0,0 +1,67 @@ +NAME + gcloud network-security authz-policies describe - describe an AuthzPolicy + resource + +SYNOPSIS + gcloud network-security authz-policies describe + (AUTHZ_POLICY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details about an AuthzPolicy resource. + +EXAMPLES + To show details about the AuthzPolicy resource named my-authz-policy + located in us-central1. + + $ gcloud network-security authz-policies describe my-authz-policy \ + --location=us-central1 + +POSITIONAL ARGUMENTS + AuthzPolicy resource - The ID of the AuthzPolicy resource. 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 authz_policy 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. + + AUTHZ_POLICY + ID of the AuthzPolicy or fully qualified identifier for the + AuthzPolicy. + + To set the authz_policy attribute: + ▸ provide the argument authz_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument authz_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networksecurity/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + This variant is also available: + + $ gcloud beta network-security authz-policies describe + diff --git a/gcloud/network-security/authz-policies/help b/gcloud/network-security/authz-policies/help new file mode 100644 index 000000000..3c35c81a7 --- /dev/null +++ b/gcloud/network-security/authz-policies/help @@ -0,0 +1,35 @@ +NAME + gcloud network-security authz-policies - manage Network Security + AuthzPolicy resources + +SYNOPSIS + gcloud network-security authz-policies COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Network Security AuthzPolicy resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + Delete an AuthzPolicy resource. + + describe + Describe an AuthzPolicy resource. + + import + Import an AuthzPolicy resource. + + list + List AuthzPolicy resources. + +NOTES + This variant is also available: + + $ gcloud beta network-security authz-policies + diff --git a/gcloud/network-security/authz-policies/import b/gcloud/network-security/authz-policies/import new file mode 100644 index 000000000..468c5edac --- /dev/null +++ b/gcloud/network-security/authz-policies/import @@ -0,0 +1,83 @@ +NAME + gcloud network-security authz-policies import - import an AuthzPolicy + resource + +SYNOPSIS + gcloud network-security authz-policies import + (AUTHZ_POLICY : --location=LOCATION) [--async] [--source=SOURCE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Import an AuthzPolicy resource defined in a YAML file. + +EXAMPLES + To import an AuthzPolicy resource named my-authz-poilcy from a YAML file in + us-central1, run: + + $ gcloud network-security authz-policies import my-authz-policy \ + --source=my-authz-policy.yaml --location=us-central1 + +POSITIONAL ARGUMENTS + AuthzPolicy resource - The ID of the new or updated AuthzPolicy resource. + 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 authz_policy 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. + + AUTHZ_POLICY + ID of the AuthzPolicy or fully qualified identifier for the + AuthzPolicy. + + To set the authz_policy attribute: + ▸ provide the argument authz_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument authz_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --source=SOURCE + Path to a YAML file containing the configuration export data. The YAML + file must not contain any output-only fields. Alternatively, you may + omit this flag to read from standard input. For a schema describing the + export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + + $CLOUDSDKROOT is can be obtained with the following command: + + $ gcloud info --format='value(installation.sdk_root)' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networksecurity/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + This variant is also available: + + $ gcloud beta network-security authz-policies import + diff --git a/gcloud/network-security/authz-policies/list b/gcloud/network-security/authz-policies/list new file mode 100644 index 000000000..84216efd6 --- /dev/null +++ b/gcloud/network-security/authz-policies/list @@ -0,0 +1,86 @@ +NAME + gcloud network-security authz-policies list - list AuthzPolicy resources + +SYNOPSIS + gcloud network-security authz-policies list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all AuthzPolicy resources in the specified location of the current + project. + +EXAMPLES + To list all AuthzPolicy resources in the current project located in + us-central1 region run: + + $ gcloud network-security authz-policies list --location=us-central1 + +REQUIRED FLAGS + Location resource - The parent location. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +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 networksecurity/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + This variant is also available: + + $ gcloud beta network-security authz-policies list + diff --git a/gcloud/network-security/help b/gcloud/network-security/help index de2a82514..b7fcc44ee 100644 --- a/gcloud/network-security/help +++ b/gcloud/network-security/help @@ -21,6 +21,9 @@ GROUPS authorization-policies Manage Network Security AuthorizationPolicies. + authz-policies + Manage Network Security AuthzPolicy resources. + backend-authentication-configs Manage Network Security BackendAuthenticationConfigs. diff --git a/gcloud/oracle-database/exadb-vm-clusters/create b/gcloud/oracle-database/exadb-vm-clusters/create new file mode 100644 index 000000000..5021a66c7 --- /dev/null +++ b/gcloud/oracle-database/exadb-vm-clusters/create @@ -0,0 +1,297 @@ +NAME + gcloud oracle-database exadb-vm-clusters create - create exadbVmClusters + +SYNOPSIS + gcloud oracle-database exadb-vm-clusters create EXADB_VM_CLUSTER + --backup-odb-subnet=BACKUP_ODB_SUBNET --display-name=DISPLAY_NAME + --odb-subnet=ODB_SUBNET + (--properties-enabled-ecpu-count-per-node=PROPERTIES_ENABLED_ECPU_COUNT_PER_NODE --properties-exascale-db-storage-vault=PROPERTIES_EXASCALE_DB_STORAGE_VAULT --properties-grid-image-id=PROPERTIES_GRID_IMAGE_ID --properties-hostname-prefix=PROPERTIES_HOSTNAME_PREFIX --properties-node-count=PROPERTIES_NODE_COUNT --properties-shape-attribute=PROPERTIES_SHAPE_ATTRIBUTE --properties-ssh-public-keys=[PROPERTIES_SSH_PUBLIC_KEYS, + ...] + --vm-file-system-storage-size-in-gbs-per-node=VM_FILE_SYSTEM_STORAGE_SIZE_IN_GBS_PER_NODE : --properties-additional-ecpu-count-per-node=PROPERTIES_ADDITIONAL_ECPU_COUNT_PER_NODE --properties-cluster-name=PROPERTIES_CLUSTER_NAME --properties-license-model=PROPERTIES_LICENSE_MODEL --properties-scan-listener-port-tcp=PROPERTIES_SCAN_LISTENER_PORT_TCP --data-collection-options-is-diagnostics-events-enabled --data-collection-options-is-health-monitoring-enabled --data-collection-options-is-incident-logs-enabled --time-zone-id=TIME_ZONE_ID --time-zone-version=TIME_ZONE_VERSION) + [--async] [--labels=[LABELS,...]] [--location=LOCATION] + [--odb-network=ODB_NETWORK] [--request-id=REQUEST_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create an exadbVmCluster + +EXAMPLES + To create the exadbVmCluster, run: + + $ gcloud oracle-database exadb-vm-clusters create + +POSITIONAL ARGUMENTS + ExadbVmCluster resource - Identifier. The name of the ExadbVmCluster + resource in the following format: + projects/{project}/locations/{region}/exadbVmClusters/{exadb_vm_cluster} + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument exadb_vm_cluster on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument exadb_vm_cluster on the command line with a + fully specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + EXADB_VM_CLUSTER + ID of the exadbVmCluster or fully qualified identifier for the + exadbVmCluster. + + To set the exadb_vm_cluster attribute: + ▸ provide the argument exadb_vm_cluster on the command line. + +REQUIRED FLAGS + OdbSubnet resource - The name of the backup OdbSubnet associated with the + ExadbVmCluster. Format: + projects/{project}/locations/{location}/odbNetworks/{odb_network}/odbSubnets/{odb_subnet} + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --backup-odb-subnet on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument --backup-odb-subnet on the command line with a + fully specified name; + ◆ provide the argument --location on the command line. + + To set the odb-network attribute: + ◆ provide the argument --backup-odb-subnet on the command line with a + fully specified name; + ◆ provide the argument --odb-network on the command line. + + This must be specified. + + --backup-odb-subnet=BACKUP_ODB_SUBNET + ID of the odbSubnet or fully qualified identifier for the odbSubnet. + + To set the odb-subnet attribute: + ▸ provide the argument --backup-odb-subnet on the command line. + + --display-name=DISPLAY_NAME + The display name for the ExadbVmCluster. The name does not have to be + unique within your project. The name must be 1-255 characters long and + can only contain alphanumeric characters. + + OdbSubnet resource - The name of the OdbSubnet associated with the + ExadbVmCluster for IP allocation. Format: + projects/{project}/locations/{location}/odbNetworks/{odb_network}/odbSubnets/{odb_subnet} + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --odb-subnet on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument --odb-subnet on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + To set the odb-network attribute: + ◆ provide the argument --odb-subnet on the command line with a fully + specified name; + ◆ provide the argument --odb-network on the command line. + + This must be specified. + + --odb-subnet=ODB_SUBNET + ID of the odbSubnet or fully qualified identifier for the odbSubnet. + + To set the odb-subnet attribute: + ▸ provide the argument --odb-subnet on the command line. + + The properties of an ExadbVmCluster. + + This must be specified. + + --properties-enabled-ecpu-count-per-node=PROPERTIES_ENABLED_ECPU_COUNT_PER_NODE + The number of ECPUs enabled per node for an exadata vm cluster on + exascale infrastructure. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + ExascaleDbStorageVault resource - The name of ExascaleDbStorageVault + associated with the ExadbVmCluster. It can refer to an existing + ExascaleDbStorageVault. Or a new one can be created during the + ExadbVmCluster creation (requires storage_vault_properties to be set). + Format: + projects/{project}/locations/{location}/exascaleDbStorageVaults/{exascale_db_storage_vault} + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ▸ provide the argument --properties-exascale-db-storage-vault on the + command line with a fully specified name; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + To set the location attribute: + ▸ provide the argument --properties-exascale-db-storage-vault on the + command line with a fully specified name; + ▸ provide the argument --location on the command line. + + This must be specified. + + --properties-exascale-db-storage-vault=PROPERTIES_EXASCALE_DB_STORAGE_VAULT + ID of the exascaleDbStorageVault or fully qualified identifier for + the exascaleDbStorageVault. + + To set the exascale-db-storage-vault attribute: + ▫ provide the argument --properties-exascale-db-storage-vault on + the command line. + + --properties-grid-image-id=PROPERTIES_GRID_IMAGE_ID + Grid Infrastructure Version. + + --properties-hostname-prefix=PROPERTIES_HOSTNAME_PREFIX + Prefix for VM cluster host names. + + --properties-node-count=PROPERTIES_NODE_COUNT + The number of nodes/VMs in the ExadbVmCluster. + + --properties-shape-attribute=PROPERTIES_SHAPE_ATTRIBUTE + The shape attribute of the VM cluster. The type of Exascale storage + used for Exadata VM cluster. The default is SMART_STORAGE which + supports Oracle Database 23ai and later. PROPERTIES_SHAPE_ATTRIBUTE + must be one of: + + block-storage + Indicates that the resource is in block storage. + smart-storage + Indicates that the resource is in smart storage. + + --properties-ssh-public-keys=[PROPERTIES_SSH_PUBLIC_KEYS,...] + The SSH public keys for the ExadbVmCluster. + + The storage allocation for the exadbvmcluster, in gigabytes (GB). + + This must be specified. + + --vm-file-system-storage-size-in-gbs-per-node=VM_FILE_SYSTEM_STORAGE_SIZE_IN_GBS_PER_NODE + The storage allocation for the exadbvmcluster per node, in + gigabytes (GB). This field is used to calculate the total storage + allocation for the exadbvmcluster. + + --properties-additional-ecpu-count-per-node=PROPERTIES_ADDITIONAL_ECPU_COUNT_PER_NODE + The number of additional ECPUs per node for an Exadata VM cluster on + exascale infrastructure. + + --properties-cluster-name=PROPERTIES_CLUSTER_NAME + The cluster name for Exascale vm cluster. The cluster name must begin + with an alphabetic character and may contain hyphens(-) but can not + contain underscores(). It should be not more than 11 characters and + is not case sensitive. OCI Cluster name. + + --properties-license-model=PROPERTIES_LICENSE_MODEL + The license type of the ExadbVmCluster. PROPERTIES_LICENSE_MODEL must + be one of: + + bring-your-own-license + Bring your own license. + license-included + Default is license included. + + --properties-scan-listener-port-tcp=PROPERTIES_SCAN_LISTENER_PORT_TCP + SCAN listener port - TCP + + Data collection options for diagnostics. + https://docs.oracle.com/en-us/iaas/api/#/en/database/20160918/datatypes/DataCollectionOptions + + --data-collection-options-is-diagnostics-events-enabled + Indicates whether to enable data collection for diagnostics. + + --data-collection-options-is-health-monitoring-enabled + Indicates whether to enable health monitoring. + + --data-collection-options-is-incident-logs-enabled + Indicates whether to enable incident logs and trace collection. + + Represents a time zone from the IANA Time Zone Database + (https://www.iana.org/time-zones). + + --time-zone-id=TIME_ZONE_ID + IANA Time Zone Database time zone. For example "America/New_York". + + --time-zone-version=TIME_ZONE_VERSION + IANA Time Zone Database version number. For example "2019a". + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --labels=[LABELS,...] + The labels or tags associated with the ExadbVmCluster. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --location=LOCATION + For resources [backup-odb-subnet, exadb_vm_cluster, odb-network, + odb-subnet, properties-exascale-db-storage-vault], provides fallback + value for resource location attribute. When the resource's full URI + path is not provided, location will fallback to this flag value. + + --odb-network=ODB_NETWORK + For resources [backup-odb-subnet, odb-network, odb-subnet], provides + fallback value for resource odb-network attribute. When the resource's + full URI path is not provided, odb-network will fallback to this flag + value. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/exadb-vm-clusters/delete b/gcloud/oracle-database/exadb-vm-clusters/delete new file mode 100644 index 000000000..504e5a8ed --- /dev/null +++ b/gcloud/oracle-database/exadb-vm-clusters/delete @@ -0,0 +1,76 @@ +NAME + gcloud oracle-database exadb-vm-clusters delete - delete exadbVmClusters + +SYNOPSIS + gcloud oracle-database exadb-vm-clusters delete + (EXADB_VM_CLUSTER : --location=LOCATION) [--async] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an exadbVmCluster + +EXAMPLES + To delete the exadbVmCluster, run: + + $ gcloud oracle-database exadb-vm-clusters delete + +POSITIONAL ARGUMENTS + ExadbVmCluster resource - The name of the ExadbVmCluster in the following + format: + projects/{project}/locations/{location}/exadbVmClusters/{exadb_vm_cluster}. + 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 exadb_vm_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. + + EXADB_VM_CLUSTER + ID of the exadbVmCluster or fully qualified identifier for the + exadbVmCluster. + + To set the exadb_vm_cluster attribute: + ▸ provide the argument exadb_vm_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the exadbVmCluster resource. + + To set the location attribute: + ▸ provide the argument exadb_vm_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --request-id=REQUEST_ID + An optional ID to identify the request. This value is used to identify + duplicate requests. If you make a request with the same request ID and + the original request is still in progress or completed, the server + ignores the second request. This prevents clients from accidentally + creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/exadb-vm-clusters/describe b/gcloud/oracle-database/exadb-vm-clusters/describe new file mode 100644 index 000000000..cc057803c --- /dev/null +++ b/gcloud/oracle-database/exadb-vm-clusters/describe @@ -0,0 +1,61 @@ +NAME + gcloud oracle-database exadb-vm-clusters describe - describe + exadbVmClusters + +SYNOPSIS + gcloud oracle-database exadb-vm-clusters describe + (EXADB_VM_CLUSTER : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an exadbVmCluster + +EXAMPLES + To describe the exadbVmCluster, run: + + $ gcloud oracle-database exadb-vm-clusters describe + +POSITIONAL ARGUMENTS + ExadbVmCluster resource - The name of the ExadbVmCluster in the following + format: + projects/{project}/locations/{location}/exadbVmClusters/{exadb_vm_cluster}. + 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 exadb_vm_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. + + EXADB_VM_CLUSTER + ID of the exadbVmCluster or fully qualified identifier for the + exadbVmCluster. + + To set the exadb_vm_cluster attribute: + ▸ provide the argument exadb_vm_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the exadbVmCluster resource. + + To set the location attribute: + ▸ provide the argument exadb_vm_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/exadb-vm-clusters/help b/gcloud/oracle-database/exadb-vm-clusters/help new file mode 100644 index 000000000..27bfeafb2 --- /dev/null +++ b/gcloud/oracle-database/exadb-vm-clusters/help @@ -0,0 +1,35 @@ +NAME + gcloud oracle-database exadb-vm-clusters - manage Exadb Vm Cluster + resources + +SYNOPSIS + gcloud oracle-database exadb-vm-clusters COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Exadb Vm Cluster resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create exadbVmClusters. + + delete + Delete exadbVmClusters. + + describe + Describe exadbVmClusters. + + list + List exadbVmClusters. + + remove-virtual-machine + remove exadbVmClusters. + + update + Update exadbVmClusters. diff --git a/gcloud/oracle-database/exadb-vm-clusters/list b/gcloud/oracle-database/exadb-vm-clusters/list new file mode 100644 index 000000000..9ed329d5e --- /dev/null +++ b/gcloud/oracle-database/exadb-vm-clusters/list @@ -0,0 +1,79 @@ +NAME + gcloud oracle-database exadb-vm-clusters list - list exadbVmClusters + +SYNOPSIS + gcloud oracle-database exadb-vm-clusters list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List exadbVmClusters + +EXAMPLES + To list all exadbVmClusters, run: + + $ gcloud oracle-database exadb-vm-clusters list + +REQUIRED FLAGS + Location resource - The parent value for ExadbVmClusters in the following + format: projects/{project}/locations/{location}. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +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 oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/exadb-vm-clusters/remove-virtual-machine b/gcloud/oracle-database/exadb-vm-clusters/remove-virtual-machine new file mode 100644 index 000000000..974a22a41 --- /dev/null +++ b/gcloud/oracle-database/exadb-vm-clusters/remove-virtual-machine @@ -0,0 +1,82 @@ +NAME + gcloud oracle-database exadb-vm-clusters remove-virtual-machine - remove + exadbVmClusters + +SYNOPSIS + gcloud oracle-database exadb-vm-clusters remove-virtual-machine + (EXADB_VM_CLUSTER : --location=LOCATION) --hostnames=[HOSTNAMES,...] + [--async] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + remove exadbVmClusters + +EXAMPLES + To remove all exadbVmClusters, run: + + $ gcloud oracle-database exadb-vm-clusters remove-virtual-machine + +POSITIONAL ARGUMENTS + ExadbVmCluster resource - The name of the ExadbVmCluster in the following + format: + projects/{project}/locations/{location}/exadbVmClusters/{exadb_vm_cluster}. + 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 exadb_vm_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. + + EXADB_VM_CLUSTER + ID of the exadbVmCluster or fully qualified identifier for the + exadbVmCluster. + + To set the exadb_vm_cluster attribute: + ▸ provide the argument exadb_vm_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the exadbVmCluster resource. + + To set the location attribute: + ▸ provide the argument exadb_vm_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --hostnames=[HOSTNAMES,...] + The list of host names of db nodes to be removed from the + ExadbVmCluster. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --request-id=REQUEST_ID + An optional ID to identify the request. This value is used to identify + duplicate requests. If you make a request with the same request ID and + the original request is still in progress or completed, the server + ignores the second request. This prevents clients from accidentally + creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/exadb-vm-clusters/update b/gcloud/oracle-database/exadb-vm-clusters/update new file mode 100644 index 000000000..64f7516a0 --- /dev/null +++ b/gcloud/oracle-database/exadb-vm-clusters/update @@ -0,0 +1,160 @@ +NAME + gcloud oracle-database exadb-vm-clusters update - update exadbVmClusters + +SYNOPSIS + gcloud oracle-database exadb-vm-clusters update + (EXADB_VM_CLUSTER : --location=LOCATION) [--async] + [--request-id=REQUEST_ID] + [--clear-properties --properties-node-count=PROPERTIES_NODE_COUNT] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an exadbVmCluster + +EXAMPLES + To update the exadbVmCluster, run: + + $ gcloud oracle-database exadb-vm-clusters update + +POSITIONAL ARGUMENTS + ExadbVmCluster resource - Identifier. The name of the ExadbVmCluster + resource in the following format: + projects/{project}/locations/{region}/exadbVmClusters/{exadb_vm_cluster} + 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 exadb_vm_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. + + EXADB_VM_CLUSTER + ID of the exadbVmCluster or fully qualified identifier for the + exadbVmCluster. + + To set the exadb_vm_cluster attribute: + ▸ provide the argument exadb_vm_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the exadbVmCluster resource. + + To set the location attribute: + ▸ provide the argument exadb_vm_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --request-id=REQUEST_ID + An optional ID to identify the request. This value is used to identify + duplicate requests. If you make a request with the same request ID and + the original request is still in progress or completed, the server + ignores the second request. This prevents clients from accidentally + creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + The properties of an ExadbVmCluster. + + --clear-properties + Set exadbVmCluster.properties back to default value. + + --properties-node-count=PROPERTIES_NODE_COUNT + The number of nodes/VMs in the ExadbVmCluster. + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. The labels or tags associated with the + ExadbVmCluster. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. The labels or tags + associated with the ExadbVmCluster. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=REMOVE_LABELS + Remove existing value from map labels. Sets remove_labels value. + + Shorthand Example: + + --remove-labels=string,string + + JSON Example: + + --remove-labels=["string"] + + File Example: + + --remove-labels=path_to_file.(yaml|json) + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/exascale-db-storage-vaults/create b/gcloud/oracle-database/exascale-db-storage-vaults/create new file mode 100644 index 000000000..9b1ffd1dd --- /dev/null +++ b/gcloud/oracle-database/exascale-db-storage-vaults/create @@ -0,0 +1,141 @@ +NAME + gcloud oracle-database exascale-db-storage-vaults create - create + exascaleDbStorageVaults + +SYNOPSIS + gcloud oracle-database exascale-db-storage-vaults create + (EXASCALE_DB_STORAGE_VAULT : --location=LOCATION) + --display-name=DISPLAY_NAME + (--exascale-db-storage-details-total-size-gbs=EXASCALE_DB_STORAGE_DETAILS_TOTAL_SIZE_GBS : --properties-additional-flash-cache-percent=PROPERTIES_ADDITIONAL_FLASH_CACHE_PERCENT --properties-description=PROPERTIES_DESCRIPTION) + [--async] [--gcp-oracle-zone=GCP_ORACLE_ZONE] [--labels=[LABELS,...]] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create an exascaleDbStorageVault + +EXAMPLES + To create the exascaleDbStorageVault, run: + + $ gcloud oracle-database exascale-db-storage-vaults create + +POSITIONAL ARGUMENTS + ExascaleDbStorageVault resource - Identifier. The resource name of the + ExascaleDbStorageVault. Format: + projects/{project}/locations/{location}/exascaleDbStorageVaults/{exascale_db_storage_vault} + 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 exascale_db_storage_vault 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. + + EXASCALE_DB_STORAGE_VAULT + ID of the exascaleDbStorageVault or fully qualified identifier for + the exascaleDbStorageVault. + + To set the exascale_db_storage_vault attribute: + ▸ provide the argument exascale_db_storage_vault on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the exascaleDbStorageVault resource. + + To set the location attribute: + ▸ provide the argument exascale_db_storage_vault on the command + line with a fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --display-name=DISPLAY_NAME + The display name for the ExascaleDbStorageVault. The name does not have + to be unique within your project. The name must be 1-255 characters + long and can only contain alphanumeric characters. + + The properties of the ExascaleDbStorageVault. + + next ID: 12 + + This must be specified. + + The storage details of the ExascaleDbStorageVault. + + This must be specified. + + --exascale-db-storage-details-total-size-gbs=EXASCALE_DB_STORAGE_DETAILS_TOTAL_SIZE_GBS + The total storage allocation for the ExascaleDbStorageVault, in + gigabytes (GB). + + --properties-additional-flash-cache-percent=PROPERTIES_ADDITIONAL_FLASH_CACHE_PERCENT + The size of additional flash cache in percentage of high capacity + database storage. + + --properties-description=PROPERTIES_DESCRIPTION + The description of the ExascaleDbStorageVault. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --gcp-oracle-zone=GCP_ORACLE_ZONE + The GCP Oracle zone where Oracle ExascaleDbStorageVault is hosted. + Example: us-east4-b-r2. If not specified, the system will pick a zone + based on availability. + + --labels=[LABELS,...] + The labels or tags associated with the ExascaleDbStorageVault. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/exascale-db-storage-vaults/delete b/gcloud/oracle-database/exascale-db-storage-vaults/delete new file mode 100644 index 000000000..34dba53c2 --- /dev/null +++ b/gcloud/oracle-database/exascale-db-storage-vaults/delete @@ -0,0 +1,78 @@ +NAME + gcloud oracle-database exascale-db-storage-vaults delete - delete + exascaleDbStorageVaults + +SYNOPSIS + gcloud oracle-database exascale-db-storage-vaults delete + (EXASCALE_DB_STORAGE_VAULT : --location=LOCATION) [--async] + [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an exascaleDbStorageVault + +EXAMPLES + To delete the exascaleDbStorageVault, run: + + $ gcloud oracle-database exascale-db-storage-vaults delete + +POSITIONAL ARGUMENTS + ExascaleDbStorageVault resource - The name of the ExascaleDbStorageVault + in the following format: + projects/{project}/locations/{location}/exascaleDbStorageVaults/{exascale_db_storage_vault}. + 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 exascale_db_storage_vault 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. + + EXASCALE_DB_STORAGE_VAULT + ID of the exascaleDbStorageVault or fully qualified identifier for + the exascaleDbStorageVault. + + To set the exascale_db_storage_vault attribute: + ▸ provide the argument exascale_db_storage_vault on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the exascaleDbStorageVault resource. + + To set the location attribute: + ▸ provide the argument exascale_db_storage_vault on the command + line with a fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --request-id=REQUEST_ID + An optional ID to identify the request. This value is used to identify + duplicate requests. If you make a request with the same request ID and + the original request is still in progress or completed, the server + ignores the second request. This prevents clients from accidentally + creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/exascale-db-storage-vaults/describe b/gcloud/oracle-database/exascale-db-storage-vaults/describe new file mode 100644 index 000000000..4852cc88c --- /dev/null +++ b/gcloud/oracle-database/exascale-db-storage-vaults/describe @@ -0,0 +1,63 @@ +NAME + gcloud oracle-database exascale-db-storage-vaults describe - describe + exascaleDbStorageVaults + +SYNOPSIS + gcloud oracle-database exascale-db-storage-vaults describe + (EXASCALE_DB_STORAGE_VAULT : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an exascaleDbStorageVault + +EXAMPLES + To describe the exascaleDbStorageVault, run: + + $ gcloud oracle-database exascale-db-storage-vaults describe + +POSITIONAL ARGUMENTS + ExascaleDbStorageVault resource - The name of the ExascaleDbStorageVault + in the following format: + projects/{project}/locations/{location}/exascaleDbStorageVaults/{exascale_db_storage_vault}. + 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 exascale_db_storage_vault 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. + + EXASCALE_DB_STORAGE_VAULT + ID of the exascaleDbStorageVault or fully qualified identifier for + the exascaleDbStorageVault. + + To set the exascale_db_storage_vault attribute: + ▸ provide the argument exascale_db_storage_vault on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the exascaleDbStorageVault resource. + + To set the location attribute: + ▸ provide the argument exascale_db_storage_vault on the command + line with a fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/exascale-db-storage-vaults/help b/gcloud/oracle-database/exascale-db-storage-vaults/help new file mode 100644 index 000000000..4012b78e6 --- /dev/null +++ b/gcloud/oracle-database/exascale-db-storage-vaults/help @@ -0,0 +1,30 @@ +NAME + gcloud oracle-database exascale-db-storage-vaults - manage Exascale Db + Storage Vault resources + +SYNOPSIS + gcloud oracle-database exascale-db-storage-vaults COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Exascale Db Storage Vault resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create exascaleDbStorageVaults. + + delete + Delete exascaleDbStorageVaults. + + describe + Describe exascaleDbStorageVaults. + + list + List exascaleDbStorageVaults. diff --git a/gcloud/oracle-database/exascale-db-storage-vaults/list b/gcloud/oracle-database/exascale-db-storage-vaults/list new file mode 100644 index 000000000..d21cf52ed --- /dev/null +++ b/gcloud/oracle-database/exascale-db-storage-vaults/list @@ -0,0 +1,80 @@ +NAME + gcloud oracle-database exascale-db-storage-vaults list - list + exascaleDbStorageVaults + +SYNOPSIS + gcloud oracle-database exascale-db-storage-vaults list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List exascaleDbStorageVaults + +EXAMPLES + To list all exascaleDbStorageVaults, run: + + $ gcloud oracle-database exascale-db-storage-vaults list + +REQUIRED FLAGS + Location resource - The parent value for ExascaleDbStorageVault in the + following format: projects/{project}/locations/{location}. This represents + a Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +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 oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/gi-versions/help b/gcloud/oracle-database/gi-versions/help index c486f671b..e1e16850f 100644 --- a/gcloud/oracle-database/gi-versions/help +++ b/gcloud/oracle-database/gi-versions/help @@ -2,7 +2,7 @@ NAME gcloud oracle-database gi-versions - manage Gi Version resources SYNOPSIS - gcloud oracle-database gi-versions COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud oracle-database gi-versions GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION Manage Gi Version resources. @@ -12,6 +12,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + minor-versions + Manage Minor Version resources. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/oracle-database/gi-versions/minor-versions/help b/gcloud/oracle-database/gi-versions/minor-versions/help new file mode 100644 index 000000000..9af755e0c --- /dev/null +++ b/gcloud/oracle-database/gi-versions/minor-versions/help @@ -0,0 +1,21 @@ +NAME + gcloud oracle-database gi-versions minor-versions - manage Minor Version + resources + +SYNOPSIS + gcloud oracle-database gi-versions minor-versions COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Minor Version resources. + +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 minorVersions. diff --git a/gcloud/oracle-database/gi-versions/minor-versions/list b/gcloud/oracle-database/gi-versions/minor-versions/list new file mode 100644 index 000000000..db60ebbf2 --- /dev/null +++ b/gcloud/oracle-database/gi-versions/minor-versions/list @@ -0,0 +1,93 @@ +NAME + gcloud oracle-database gi-versions minor-versions list - list minorVersions + +SYNOPSIS + gcloud oracle-database gi-versions minor-versions list + (--gi-version=GI_VERSION : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List minorVersions + +EXAMPLES + To list all minorVersions, run: + + $ gcloud oracle-database gi-versions minor-versions list + +REQUIRED FLAGS + GiVersion resource - The parent value for the MinorVersion resource with + the format: + projects/{project}/locations/{location}/giVersions/{gi_version} 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 --gi-version 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. + + --gi-version=GI_VERSION + ID of the giVersion or fully qualified identifier for the giVersion. + + To set the gi-version attribute: + ▸ provide the argument --gi-version on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location id of the giVersion resource. + + To set the location attribute: + ▸ provide the argument --gi-version on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +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 oracledatabase/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/oracle/database/docs diff --git a/gcloud/oracle-database/help b/gcloud/oracle-database/help index 654d0456f..9135c5746 100644 --- a/gcloud/oracle-database/help +++ b/gcloud/oracle-database/help @@ -54,6 +54,12 @@ GROUPS entitlements Manage Entitlement resources. + exadb-vm-clusters + Manage Exadb Vm Cluster resources. + + exascale-db-storage-vaults + Manage Exascale Db Storage Vault resources. + gi-versions Manage Gi Version resources. diff --git a/gcloud/service-extensions/authz-extensions/delete b/gcloud/service-extensions/authz-extensions/delete new file mode 100644 index 000000000..562ac361c --- /dev/null +++ b/gcloud/service-extensions/authz-extensions/delete @@ -0,0 +1,73 @@ +NAME + gcloud service-extensions authz-extensions delete - delete an + AuthzExtension resource + +SYNOPSIS + gcloud service-extensions authz-extensions delete + (AUTHZ_EXTENSION : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete the specified AuthzExtension resource. + +EXAMPLES + To delete an AuthzExtension resource named my-authz-extension in + us-central1, run: + + $ gcloud service-extensions authz-extensions delete \ + my-authz-extension --location=us-central1 + +POSITIONAL ARGUMENTS + AuthzExtension resource - The ID of the deleted AuthzExtension resource. + 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 authz_extension 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. + + AUTHZ_EXTENSION + ID of the AuthzExtension or fully qualified identifier for the + AuthzExtension. + + To set the authz_extension attribute: + ▸ provide the argument authz_extension on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Cloud region in which the resource is located. + + To set the location attribute: + ▸ provide the argument authz_extension on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + This variant is also available: + + $ gcloud beta service-extensions authz-extensions delete + diff --git a/gcloud/service-extensions/authz-extensions/describe b/gcloud/service-extensions/authz-extensions/describe new file mode 100644 index 000000000..925414803 --- /dev/null +++ b/gcloud/service-extensions/authz-extensions/describe @@ -0,0 +1,67 @@ +NAME + gcloud service-extensions authz-extensions describe - describe an + AuthzExtension resource + +SYNOPSIS + gcloud service-extensions authz-extensions describe + (AUTHZ_EXTENSION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details about an AuthzExtension resource. + +EXAMPLES + To show details about the AuthzExtension resource named my-authz-extension + located in us-central1. + + $ gcloud service-extensions authz-extensions describe \ + my-authz-extension --location=us-central1 + +POSITIONAL ARGUMENTS + AuthzExtension resource - The ID of the AuthzExtension resource. 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 authz_extension 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. + + AUTHZ_EXTENSION + ID of the AuthzExtension or fully qualified identifier for the + AuthzExtension. + + To set the authz_extension attribute: + ▸ provide the argument authz_extension on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Cloud region in which the resource is located. + + To set the location attribute: + ▸ provide the argument authz_extension on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + This variant is also available: + + $ gcloud beta service-extensions authz-extensions describe + diff --git a/gcloud/service-extensions/authz-extensions/help b/gcloud/service-extensions/authz-extensions/help new file mode 100644 index 000000000..ad1e24afe --- /dev/null +++ b/gcloud/service-extensions/authz-extensions/help @@ -0,0 +1,35 @@ +NAME + gcloud service-extensions authz-extensions - manage Service Extensions + AuthzExtension resources + +SYNOPSIS + gcloud service-extensions authz-extensions COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Service Extensions AuthzExtension resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + Delete an AuthzExtension resource. + + describe + Describe an AuthzExtension resource. + + import + Import an AuthzExtension resource. + + list + List AuthzExtension resources. + +NOTES + This variant is also available: + + $ gcloud beta service-extensions authz-extensions + diff --git a/gcloud/service-extensions/authz-extensions/import b/gcloud/service-extensions/authz-extensions/import new file mode 100644 index 000000000..4081d09b9 --- /dev/null +++ b/gcloud/service-extensions/authz-extensions/import @@ -0,0 +1,84 @@ +NAME + gcloud service-extensions authz-extensions import - import an + AuthzExtension resource + +SYNOPSIS + gcloud service-extensions authz-extensions import + (AUTHZ_EXTENSION : --location=LOCATION) [--async] [--source=SOURCE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Import an AuthzExtension resource defined in a YAML file. + +EXAMPLES + To import an AuthzExtension resource named my-authz-extension from a YAML + file in us-central1, run: + + $ gcloud service-extensions authz-extensions import \ + my-authz-extension --source=my-authz-extension.yaml \ + --location=us-central1 + +POSITIONAL ARGUMENTS + AuthzExtension resource - The ID of the new or updated AuthzExtension + resource. 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 authz_extension 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. + + AUTHZ_EXTENSION + ID of the AuthzExtension or fully qualified identifier for the + AuthzExtension. + + To set the authz_extension attribute: + ▸ provide the argument authz_extension on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Cloud region in which the resource is located. + + To set the location attribute: + ▸ provide the argument authz_extension on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --source=SOURCE + Path to a YAML file containing the configuration export data. The YAML + file must not contain any output-only fields. Alternatively, you may + omit this flag to read from standard input. For a schema describing the + export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + + $CLOUDSDKROOT is can be obtained with the following command: + + $ gcloud info --format='value(installation.sdk_root)' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + This variant is also available: + + $ gcloud beta service-extensions authz-extensions import + diff --git a/gcloud/service-extensions/authz-extensions/list b/gcloud/service-extensions/authz-extensions/list new file mode 100644 index 000000000..06331cb39 --- /dev/null +++ b/gcloud/service-extensions/authz-extensions/list @@ -0,0 +1,88 @@ +NAME + gcloud service-extensions authz-extensions list - list AuthzExtension + resources + +SYNOPSIS + gcloud service-extensions authz-extensions list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all AuthzExtension resources in the specified location of the current + project. + +EXAMPLES + To list all AuthzExtension resources in the current project located in + us-central1 region run: + + $ gcloud service-extensions authz-extensions list \ + --location=us-central1 + +REQUIRED FLAGS + Location resource - The parent location. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +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 networkservices/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + This variant is also available: + + $ gcloud beta service-extensions authz-extensions list + diff --git a/gcloud/service-extensions/help b/gcloud/service-extensions/help index 354b221cb..7bbd261f6 100644 --- a/gcloud/service-extensions/help +++ b/gcloud/service-extensions/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + authz-extensions + Manage Service Extensions AuthzExtension resources. + lb-route-extensions Manage Service Extensions LbRouteExtension resources. diff --git a/gcloud/spanner/cli b/gcloud/spanner/cli new file mode 100644 index 000000000..c71091d80 --- /dev/null +++ b/gcloud/spanner/cli @@ -0,0 +1,121 @@ +NAME + gcloud spanner cli - an interactive shell for Spanner + +SYNOPSIS + gcloud spanner cli (DATABASE : --instance=INSTANCE) + [--database-role=DATABASE_ROLE] [--delimiter=DELIMITER; default=";"] + [--execute=EXECUTE] [--host=HOST; default="localhost"] [--html] + [--idle-transaction-timeout=IDLE_TRANSACTION_TIMEOUT; default=60] + [--init-command=INIT_COMMAND] [--init-command-add=INIT_COMMAND_ADD] + [--port=PORT] [--prompt=PROMPT; default="spanner-cli> "] + [--skip-column-names] [--skip-system-command] [--source=SOURCE] + [--system-command=SYSTEM_COMMAND; default="ON"] [--table] [--tee=TEE] + [--xml] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + An interactive shell for Spanner. + +EXAMPLES + To start an interactive shell with your Spanner example database, run the + following command: + + $ gcloud spanner cli example-database --instance=example-instance + +POSITIONAL ARGUMENTS + Database resource - The Cloud Spanner database to use within the + interactive shell. 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 database 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. + + DATABASE + ID of the database or fully qualified identifier for the database. + + To set the database attribute: + ▸ provide the argument database on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + The Cloud Spanner instance for the database. + + To set the instance attribute: + ▸ provide the argument database on the command line with a fully + specified name; + ▸ provide the argument --instance on the command line; + ▸ set the property spanner/instance. + +FLAGS + --database-role=DATABASE_ROLE + Database role user used to access the database. + + --delimiter=DELIMITER; default=";" + Set the statement delimiter. + + --execute=EXECUTE + Execute the statement and then exits. + + --host=HOST; default="localhost" + Host on which Spanner server is located. + + --html + Show output in HTML format. + + --idle-transaction-timeout=IDLE_TRANSACTION_TIMEOUT; default=60 + Set the idle transaction timeout. The default timeout is 60 seconds. + + --init-command=INIT_COMMAND + SQL statement to execute after startup. + + --init-command-add=INIT_COMMAND_ADD + Additional SQL statement to execute after startup. + + --port=PORT + Port number that gcloud uses to connect to Spanner. + + --prompt=PROMPT; default="spanner-cli> " + Set the prompt to the specified format. + + --skip-column-names + Do not show column names in output. + + --skip-system-command + Do not allow system command. + + --source=SOURCE + Execute the statement from a file and then exits. + + --system-command=SYSTEM_COMMAND; default="ON" + Enable or disable system commands. Default: ON. SYSTEM_COMMAND must be + one of: ON, OFF. + + --table + Show output in table format. + + --tee=TEE + Append a copy of the output to a named file. + + --xml + Show output in XML format. + +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 spanner cli + diff --git a/gcloud/spanner/help b/gcloud/spanner/help index 9880dc585..de0eeccf1 100644 --- a/gcloud/spanner/help +++ b/gcloud/spanner/help @@ -2,7 +2,7 @@ NAME gcloud spanner - command groups for Cloud Spanner SYNOPSIS - gcloud spanner GROUP [GCLOUD_WIDE_FLAG ...] + gcloud spanner GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION Command groups for Cloud Spanner. @@ -42,6 +42,12 @@ GROUPS samples Cloud Spanner sample apps. +COMMANDS + COMMAND is one of the following: + + cli + An interactive shell for Spanner. + NOTES These variants are also available: diff --git a/gcloud/sql/instances/help b/gcloud/sql/instances/help index 54b53f231..c4f91ef04 100644 --- a/gcloud/sql/instances/help +++ b/gcloud/sql/instances/help @@ -51,6 +51,10 @@ COMMANDS patch Updates the settings of a Cloud SQL instance. + pre-check-major-version-upgrade + Performs pre-checks for a major version upgrade of a Cloud SQL + instance. + promote-replica Promotes Cloud SQL read replica to a stand-alone instance. diff --git a/gcloud/sql/instances/pre-check-major-version-upgrade b/gcloud/sql/instances/pre-check-major-version-upgrade new file mode 100644 index 000000000..d5617ab97 --- /dev/null +++ b/gcloud/sql/instances/pre-check-major-version-upgrade @@ -0,0 +1,39 @@ +NAME + gcloud sql instances pre-check-major-version-upgrade - performs pre-checks + for a major version upgrade of a Cloud SQL instance + +SYNOPSIS + gcloud sql instances pre-check-major-version-upgrade INSTANCE + --target-database-version=TARGET_DATABASE_VERSION [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud sql instances pre-check-major-version-upgrade performs pre-checks + for a major version upgrade of a Cloud SQL instance. + +EXAMPLES + To perform pre-checks before upgrading to a target version: + + $ gcloud sql instances pre-check-major-version-upgrade \ + test-instance --target-database-version=POSTGRES_15 + +POSITIONAL ARGUMENTS + INSTANCE + Cloud SQL instance ID. + +REQUIRED FLAGS + --target-database-version=TARGET_DATABASE_VERSION + Target database version for the upgrade. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/workstations/ssh b/gcloud/workstations/ssh index dc69db164..f577f7271 100644 --- a/gcloud/workstations/ssh +++ b/gcloud/workstations/ssh @@ -12,6 +12,8 @@ SYNOPSIS DESCRIPTION SSH into a running workstation. + Note that arguments for the NO_PROXY environment variable must be FQDNs. + EXAMPLES To ssh into a running workstation, run: diff --git a/gcloud/workstations/start-tcp-tunnel b/gcloud/workstations/start-tcp-tunnel index ca91ba652..f4b46f9ec 100644 --- a/gcloud/workstations/start-tcp-tunnel +++ b/gcloud/workstations/start-tcp-tunnel @@ -13,6 +13,8 @@ DESCRIPTION Start a tunnel through which a local process can forward TCP traffic to the workstation. + Note that arguments for the NO_PROXY environment variable must be FQDNs. + EXAMPLES To start a tunnel to port 22 on a workstation, run: