diff --git a/gcloud/_version b/gcloud/_version index ea03190b5..8ae6f45a6 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 419.0.0 -alpha 2023.02.17 -beta 2023.02.17 -bq 2.0.85 +Google Cloud SDK 420.0.0 +alpha 2023.02.24 +beta 2023.02.24 +bq 2.0.86 bundled-python3-unix 3.9.16 -core 2023.02.17 +core 2023.02.24 gcloud-crc32c 1.0.0 gsutil 5.20 diff --git a/gcloud/ai-platform/jobs/submit/training b/gcloud/ai-platform/jobs/submit/training index b6420b9a3..95e449d5b 100644 --- a/gcloud/ai-platform/jobs/submit/training +++ b/gcloud/ai-platform/jobs/submit/training @@ -147,7 +147,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. @@ -187,7 +187,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. @@ -305,7 +305,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. diff --git a/gcloud/alpha/ai-platform/jobs/submit/training b/gcloud/alpha/ai-platform/jobs/submit/training index 30526178a..27a1284f9 100644 --- a/gcloud/alpha/ai-platform/jobs/submit/training +++ b/gcloud/alpha/ai-platform/jobs/submit/training @@ -149,7 +149,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. @@ -200,7 +200,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. @@ -322,7 +322,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. diff --git a/gcloud/alpha/auth/application-default/login b/gcloud/alpha/auth/application-default/login index d4dcb8b5e..31dab5b41 100644 --- a/gcloud/alpha/auth/application-default/login +++ b/gcloud/alpha/auth/application-default/login @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud alpha auth application-default login [--no-browser] [--client-id-file=CLIENT_ID_FILE] [--disable-quota-project] - [--no-launch-browser] [--scopes=SCOPE,[SCOPE,...]] - [GCLOUD_WIDE_FLAG ...] + [--no-launch-browser] [--login-config=LOGIN_CONFIG] + [--scopes=SCOPE,[SCOPE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Obtains user access credentials via a web flow and puts them in the @@ -123,6 +123,12 @@ FLAGS Enabled by default, use --no-launch-browser to disable. + --login-config=LOGIN_CONFIG + Path to the login configuration file (workforce pool, generated by the + Cloud Console or gcloud iam workforce-pools create-login-config). + Overrides the default auth/login_config_file property value for this + command invocation. + --scopes=SCOPE,[SCOPE,...] The names of the scopes to authorize for. By default openid, https://www.googleapis.com/auth/userinfo.email, diff --git a/gcloud/alpha/auth/login b/gcloud/alpha/auth/login index 75edb4202..181294f18 100644 --- a/gcloud/alpha/auth/login +++ b/gcloud/alpha/auth/login @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha auth login [ACCOUNT] [--no-activate] [--brief] [--no-browser] [--cred-file=CRED_FILE] [--enable-gdrive-access] [--force] - [--no-launch-browser] [--update-adc] [GCLOUD_WIDE_FLAG ...] + [--no-launch-browser] [--login-config=LOGIN_CONFIG] [--update-adc] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Obtains access credentials for your user account via a web-based @@ -123,6 +124,12 @@ FLAGS Enabled by default, use --no-launch-browser to disable. + --login-config=LOGIN_CONFIG + Path to the login configuration file (workforce pool, generated by the + Cloud Console or gcloud iam workforce-pools create-login-config). + Overrides the default auth/login_config_file property value for this + command invocation. + --update-adc Write the obtained credentials to the well-known location for Application Default Credentials (ADC). Run $ gcloud auth diff --git a/gcloud/alpha/builds/triggers/create/bitbucketserver b/gcloud/alpha/builds/triggers/create/bitbucketserver index c2bb06cc2..ecda7525d 100644 --- a/gcloud/alpha/builds/triggers/create/bitbucketserver +++ b/gcloud/alpha/builds/triggers/create/bitbucketserver @@ -128,9 +128,10 @@ REQUIRED FLAGS --branch-pattern=REGEX A regular expression specifying which git branches to match. - This pattern is used as a regex search for any incoming pushes. - For example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at @@ -139,9 +140,10 @@ REQUIRED FLAGS --tag-pattern=REGEX A regular expression specifying which git tags to match. - This pattern is used as a regex search for any incoming pushes. - For example, --tag-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a tag that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at diff --git a/gcloud/alpha/builds/triggers/create/cloud-source-repositories b/gcloud/alpha/builds/triggers/create/cloud-source-repositories index 330832b23..911ff9a32 100644 --- a/gcloud/alpha/builds/triggers/create/cloud-source-repositories +++ b/gcloud/alpha/builds/triggers/create/cloud-source-repositories @@ -107,9 +107,10 @@ REQUIRED FLAGS --branch-pattern=REGEX A regular expression specifying which git branches to match. - This pattern is used as a regex search for any incoming pushes. - For example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at @@ -118,9 +119,10 @@ REQUIRED FLAGS --tag-pattern=REGEX A regular expression specifying which git tags to match. - This pattern is used as a regex search for any incoming pushes. - For example, --tag-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a tag that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at diff --git a/gcloud/alpha/builds/triggers/create/github b/gcloud/alpha/builds/triggers/create/github index 23686859a..376c8b9d4 100644 --- a/gcloud/alpha/builds/triggers/create/github +++ b/gcloud/alpha/builds/triggers/create/github @@ -119,9 +119,10 @@ REQUIRED FLAGS --branch-pattern=REGEX A regular expression specifying which git branches to match. - This pattern is used as a regex search for any incoming pushes. - For example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at @@ -130,9 +131,10 @@ REQUIRED FLAGS --tag-pattern=REGEX A regular expression specifying which git tags to match. - This pattern is used as a regex search for any incoming pushes. - For example, --tag-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a tag that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at diff --git a/gcloud/alpha/builds/triggers/create/gitlab-enterprise b/gcloud/alpha/builds/triggers/create/gitlab-enterprise index 5d3c24101..1af5f2899 100644 --- a/gcloud/alpha/builds/triggers/create/gitlab-enterprise +++ b/gcloud/alpha/builds/triggers/create/gitlab-enterprise @@ -109,9 +109,10 @@ REQUIRED FLAGS --branch-pattern=REGEX A regular expression specifying which git branches to match. - This pattern is used as a regex search for any incoming pushes. - For example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at @@ -120,9 +121,10 @@ REQUIRED FLAGS --tag-pattern=REGEX A regular expression specifying which git tags to match. - This pattern is used as a regex search for any incoming pushes. - For example, --tag-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a tag that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at diff --git a/gcloud/alpha/compute/disks/create b/gcloud/alpha/compute/disks/create index e653e2547..6876f67e1 100644 --- a/gcloud/alpha/compute/disks/create +++ b/gcloud/alpha/compute/disks/create @@ -121,9 +121,8 @@ FLAGS 16384. --provisioned-iops=PROVISIONED_IOPS - Provisioned IOPS of pd-extreme disk to create. Only for use with disks - of type pd-extreme. If specified, the value must be in the range - between 2500 and 120000. If not specified, the default value is 100000. + Provisioned IOPS of disk to create. Only for use with disks of type + pd-extreme and hyperdisk-extreme. --provisioned-throughput=PROVISIONED_THROUGHPUT Provisioned throughput of disk to create. The throughput unit is MB per diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index 12aa40037..edc51d101 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -320,6 +320,13 @@ FLAGS among other restrictions. For more information, see https://cloud.google.com/compute/docs/disks/sharing-disks-between-vms. + replica-zones + Required for each regional disk associated with the instance. + Specify the URLs of the zones where the disk should be replicated + to. You must provide exactly two replica zones, and one zone must + be the same as the instance zone. You can't use this option with + boot disks. + provisioned-throughput Indicates how much throughput to provision for the disk. This sets the number of throughput mb per second that the disk can handle. diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 3b729312e..84b61bacf 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -112,20 +112,20 @@ EXAMPLES example-instance-2 example-instance-3 --zone=us-central1-a To create an instance called 'instance-1' from a source snapshot called - 'instance-snapshot' in zone 'us-central2-a' and attached regional disk + 'instance-snapshot' in zone 'us-central1-a' and attached regional disk 'disk-1', run: $ gcloud alpha compute instances create instance-1 \ --source-snapshot=https://compute.googleapis.com/compute/v1/\ projects/myproject/global/snapshots/instance-snapshot \ - --zone=central2-a --disk=name=disk1,scope=regional + --zone=us-central1-a --disk=name=disk1,scope=regional To create an instance called instance-1 as a Shielded VM instance with Secure Boot, virtual trusted platform module (vTPM) enabled and integrity monitoring, run: $ gcloud alpha compute instances create instance-1 \ - --zone=central2-a --shielded-secure-boot --shielded-vtpm \ + --zone=us-central1-a --shielded-secure-boot --shielded-vtpm \ --shielded-integrity-monitoring To create a preemptible instance called 'instance-1', run: diff --git a/gcloud/alpha/compute/routers/add-bgp-peer b/gcloud/alpha/compute/routers/add-bgp-peer index 3626856ae..8e69b7385 100644 --- a/gcloud/alpha/compute/routers/add-bgp-peer +++ b/gcloud/alpha/compute/routers/add-bgp-peer @@ -144,7 +144,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --set-advertisement-ranges=[CIDR_RANGE=DESC,...] The list of individual IP ranges, in CIDR format, to dynamically diff --git a/gcloud/alpha/compute/routers/create b/gcloud/alpha/compute/routers/create index dd42aabfb..dbb662a5c 100644 --- a/gcloud/alpha/compute/routers/create +++ b/gcloud/alpha/compute/routers/create @@ -88,7 +88,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --set-advertisement-ranges=[CIDR_RANGE=DESC,...] The list of individual IP ranges, in CIDR format, to dynamically diff --git a/gcloud/alpha/compute/routers/nats/create b/gcloud/alpha/compute/routers/nats/create index 4bc1ad7d6..17be07b6f 100644 --- a/gcloud/alpha/compute/routers/nats/create +++ b/gcloud/alpha/compute/routers/nats/create @@ -9,6 +9,7 @@ SYNOPSIS | --nat-primary-subnet-ip-ranges) [--async] [--[no-]enable-dynamic-port-allocation] [--enable-endpoint-independent-mapping] [--enable-logging] + [--endpoint-types=[ENDPOINT_TYPE,...]] [--icmp-idle-timeout=ICMP_IDLE_TIMEOUT] [--log-filter=LOG_FILTER] [--max-ports-per-vm=MAX_PORTS_PER_VM] [--min-ports-per-vm=MIN_PORTS_PER_VM] [--region=REGION] [--rules=RULES] @@ -106,6 +107,12 @@ OPTIONAL FLAGS gcloud alpha compute routers nats update MY-NAT \ --no-enable-logging --router ROUTER --region REGION + --endpoint-types=[ENDPOINT_TYPE,...] + Endpoint Types supported by the NAT Gateway. Choices are + ENDPOINT_TYPE_VM for VM Endpoints and ENDPOINT_TYPE_SWG for Secure Web + Gateway Endpoints. Defaults to ENDPOINT_TYPE_VM if not specified. + ENDPOINT_TYPE must be one of: ENDPOINT_TYPE_VM, ENDPOINT_TYPE_SWG. + --icmp-idle-timeout=ICMP_IDLE_TIMEOUT Timeout for ICMP connections. See https://cloud.google.com/sdk/gcloud/reference/topic/datetimes for @@ -192,7 +199,7 @@ OPTIONAL FLAGS be one of: PRIVATE - Used for priate-to-private NAT translations. Allows communication + Used for private-to-private NAT translations. Allows communication between VPC Networks. PUBLIC Used for private-to-public NAT translations. Allows VMs to diff --git a/gcloud/alpha/compute/routers/update b/gcloud/alpha/compute/routers/update index ebf4d769c..f3b35e51f 100644 --- a/gcloud/alpha/compute/routers/update +++ b/gcloud/alpha/compute/routers/update @@ -84,7 +84,8 @@ FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --set-advertisement-ranges=[CIDR_RANGE=DESC,...] The list of individual IP ranges, in CIDR format, to dynamically @@ -104,7 +105,8 @@ FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --add-advertisement-ranges=[CIDR_RANGE=DESC,...] A list of individual IP ranges, in CIDR format, to dynamically @@ -124,7 +126,8 @@ FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --remove-advertisement-ranges=[CIDR_RANGE,...] A list of individual IP ranges, in CIDR format, to remove from diff --git a/gcloud/alpha/compute/routers/update-bgp-peer b/gcloud/alpha/compute/routers/update-bgp-peer index dd41660d4..77ab82dff 100644 --- a/gcloud/alpha/compute/routers/update-bgp-peer +++ b/gcloud/alpha/compute/routers/update-bgp-peer @@ -130,7 +130,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --set-advertisement-ranges=[CIDR_RANGE=DESC,...] The list of individual IP ranges, in CIDR format, to dynamically @@ -150,7 +151,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --add-advertisement-ranges=[CIDR_RANGE=DESC,...] A list of individual IP ranges, in CIDR format, to dynamically @@ -170,7 +172,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --remove-advertisement-ranges=[CIDR_RANGE,...] A list of individual IP ranges, in CIDR format, to remove from diff --git a/gcloud/alpha/compute/tpus/locations/describe b/gcloud/alpha/compute/tpus/locations/describe index b038c64e0..a9ccd4b3a 100644 --- a/gcloud/alpha/compute/tpus/locations/describe +++ b/gcloud/alpha/compute/tpus/locations/describe @@ -15,7 +15,7 @@ DESCRIPTION EXAMPLES The following command describes the TPUs running in zone us-central1-b: - $ gcloud alpha compute tpus locations describe zone=us-central1-b + $ gcloud alpha compute tpus locations describe us-central1-b POSITIONAL ARGUMENTS Location resource - The Cloud TPU Location you want to describe. This diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index dffde274e..956c12b9c 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -648,6 +648,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index 08a4a21c4..510c2d962 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -680,6 +680,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index 55de6b459..35ae7b318 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -692,6 +692,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index e6775b935..a7437f0ab 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -695,6 +695,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index ff0ec8560..a0682ec37 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -656,6 +656,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/alpha/container/bare-metal/admin-clusters/query-version-config b/gcloud/alpha/container/bare-metal/admin-clusters/query-version-config index ccc689a84..cd60706c2 100644 --- a/gcloud/alpha/container/bare-metal/admin-clusters/query-version-config +++ b/gcloud/alpha/container/bare-metal/admin-clusters/query-version-config @@ -26,7 +26,7 @@ EXAMPLES FLAGS Use cases for querying versions. - Upgrade an Anthos on bare metal user cluster use case. + Upgrade an Anthos on bare metal admin cluster use case. Admin cluster resource - Admin cluster to query versions for upgrade. This represents a Cloud resource. (NOTE) Some attributes are not given diff --git a/gcloud/alpha/container/bare-metal/admin-clusters/update b/gcloud/alpha/container/bare-metal/admin-clusters/update index 5779f6c72..f4899c01b 100644 --- a/gcloud/alpha/container/bare-metal/admin-clusters/update +++ b/gcloud/alpha/container/bare-metal/admin-clusters/update @@ -4,8 +4,17 @@ NAME SYNOPSIS gcloud alpha container bare-metal admin-clusters update - (ADMIN_CLUSTER : --location=LOCATION) [--async] [--version=VERSION] - [GCLOUD_WIDE_FLAG ...] + (ADMIN_CLUSTER : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--enable-application-logs] + [--login-user=LOGIN_USER] + [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS, + ...]] [--max-pods-per-node=MAX_PODS_PER_NODE] [--validate-only] + [--version=VERSION] + [--api-server-args=[KEY=VALUE,...] + --control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] + --control-plane-node-labels=[KEY=VALUE,...] + --control-plane-node-taints=[KEY=VALUE:EFFECT,...]] + [--no-proxy=[NO_PROXY,...] --uri=URI] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update an Anthos on bare metal admin cluster. @@ -49,8 +58,68 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --description=DESCRIPTION + Description for the resource. + + Anthos on bare metal cluster operations configuration. + + --enable-application-logs + Whether collection of application logs/metrics should be enabled (in + addition to system logs/metrics). + + Anthos on bare metal node access related settings for the admin cluster. + + --login-user=LOGIN_USER + User name used to access node machines. + + Anthos on bare metal cluster maintenance configuration. + + --maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,...] + IPv4 addresses to be placed into maintenance mode. + + Anthos on bare metal admin cluster workload node configuration. + + --max-pods-per-node=MAX_PODS_PER_NODE + Maximum number of pods a node can run. + + --validate-only + If set, only validate the request, but do not actually perform the + operation. + --version=VERSION - Anthos cluster on bare metal version for the user cluster resource. + Anthos cluster on bare metal version for the admin cluster resource. + + Anthos on bare metal cluster control plane configuration. + + --api-server-args=[KEY=VALUE,...] + API Server argument configuration. + + Anthos on bare metal cluster control plane node pool configuration. + + Anthos on bare metal node pool configuration for control plane nodes. + + Anthos on bare metal node configuration for control plane nodes. + + Populate control plane node config. + + At most one of these can be specified: + + --control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] + Control plane node configuration. + + --control-plane-node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a node pool. + + --control-plane-node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every Kubernetes node in a node pool. + + Anthos on bare metal cluster proxy configuration. + + --no-proxy=[NO_PROXY,...] + List of IPs, hostnames, and domains that should skip the proxy. + + --uri=URI + Address of the proxy server. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/fleet/help b/gcloud/alpha/container/fleet/help index 97511f8e4..f0dc0cf60 100644 --- a/gcloud/alpha/container/fleet/help +++ b/gcloud/alpha/container/fleet/help @@ -70,9 +70,16 @@ GROUPS multi-cluster-services (ALPHA) Manage Multi-cluster Services Feature. + namespaces + (ALPHA) Fleet namespaces are the fleet equivalent of k8s cluster + namespaces. + policycontroller (ALPHA) Manage Policy Controller Feature. + scopes + (ALPHA) Manage scopes of all your GKE fleets. + service-directory (ALPHA) Manage the Service Directory Feature. diff --git a/gcloud/alpha/container/fleet/memberships/bindings/create b/gcloud/alpha/container/fleet/memberships/bindings/create new file mode 100644 index 000000000..fb4b2c1d2 --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/bindings/create @@ -0,0 +1,106 @@ +NAME + gcloud alpha container fleet memberships bindings create - create a + Membership Binding + +SYNOPSIS + gcloud alpha container fleet memberships bindings create + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The Membership Binding already exists. + ▪ The caller does not have permission to access the given Membership. + ▪ The Scope or the Membership does not exist. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To create a membership binding BINDING_NAME in global membership + MEMBERSHIP_NAME for scope SCOPE_NAME, run: + + $ gcloud alpha container fleet memberships bindings create \ + BINDING_NAME --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME + + To create a Binding BINDING_NAME associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with membership name and associated Scope + SCOPE_NAME. + + $ gcloud alpha container fleet memberships bindings create \ + BINDING_NAME --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --fleet=FLEET + Membership Binding is created for all the Scopes in the Fleet for + given Membership. + + Scope resource - The group of arguments defining the Fleet Scope. 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 --scope 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 --scope on the command line with a fully + specified name; + ▸ global is the only supported location. + + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▫ provide the argument --scope on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet memberships bindings create + diff --git a/gcloud/alpha/container/fleet/memberships/bindings/delete b/gcloud/alpha/container/fleet/memberships/bindings/delete new file mode 100644 index 000000000..4f11236b6 --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/bindings/delete @@ -0,0 +1,81 @@ +NAME + gcloud alpha container fleet memberships bindings delete - delete a + Membership Binding + +SYNOPSIS + gcloud alpha container fleet memberships bindings delete + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The Membership Binding specified does not exist. + ▪ The caller does not have permission to access the given Membership. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To delete Membership Binding BINDING_NAME in global Membership + MEMBERSHIP_NAME for a global membership: + + $ gcloud alpha container fleet memberships bindings delete \ + BINDING_NAME --membership=MEMBERSHIP_NAME + + To delete a Binding BINDING_NAME associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with the membership name. + + $ gcloud alpha container fleet memberships bindings delete \ + BINDING_NAME --membership=MEMBERSHIP_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet memberships bindings delete + diff --git a/gcloud/alpha/container/fleet/memberships/bindings/describe b/gcloud/alpha/container/fleet/memberships/bindings/describe new file mode 100644 index 000000000..6a6e51ab4 --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/bindings/describe @@ -0,0 +1,81 @@ +NAME + gcloud alpha container fleet memberships bindings describe - show + Membership-Binding info + +SYNOPSIS + gcloud alpha container fleet memberships bindings describe + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The Membership Binding specified does not exist in the project. + ▪ The caller does not have permission to access the Membership Binding. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To print metadata for the membership Binding BINDING_NAME in a global + membership MEMBERSHIP_NAME, run: + + $ gcloud alpha container fleet memberships bindings describe \ + BINDING_NAME --membership=MEMBERSHIP_NAME + + To print metadata for the Binding BINDING_NAME associated with regional + membership MEMBERSHIP_NAME, provide the location LOCATION_NAME for the + Membership where the Binding belongs along with membership name. + + $ gcloud alpha container fleet memberships bindings describe \ + BINDING_NAME --membership=MEMBERSHIP_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet memberships bindings describe + diff --git a/gcloud/alpha/container/fleet/memberships/bindings/help b/gcloud/alpha/container/fleet/memberships/bindings/help new file mode 100644 index 000000000..7704da74f --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/bindings/help @@ -0,0 +1,48 @@ +NAME + gcloud alpha container fleet memberships bindings - membership Bindings for + permissions + +SYNOPSIS + gcloud alpha container fleet memberships bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command group allows for manipulation of bindings associated + with membership-scope. + +EXAMPLES + Manage Bindings: + + $ gcloud alpha container fleet memberships bindings --help + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a Membership Binding. + + delete + (ALPHA) Delete a Membership Binding. + + describe + (ALPHA) Show Membership-Binding info. + + list + (ALPHA) List Bindings in a Membership. + + update + (ALPHA) Update the Binding in a Membership. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet memberships bindings + diff --git a/gcloud/alpha/container/fleet/memberships/bindings/list b/gcloud/alpha/container/fleet/memberships/bindings/list new file mode 100644 index 000000000..90934cfaf --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/bindings/list @@ -0,0 +1,87 @@ +NAME + gcloud alpha container fleet memberships bindings list - list Bindings in a + Membership + +SYNOPSIS + gcloud alpha container fleet memberships bindings list + --membership=MEMBERSHIP [--location=LOCATION; default="global"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The user does not have access to the Membership specified. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + The following command lists Bindings in global Membership MEMBERSHIP_NAME: + + $ gcloud alpha container fleet memberships bindings list \ + --membership=MEMBERSHIP_NAME + + To list all the bindings associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with membership name. + + $ gcloud alpha container fleet memberships bindings list \ + BINDING_NAME --membership=MEMBERSHIP_NAME \ + --location=LOCATION_NAME + +REQUIRED FLAGS + --membership=MEMBERSHIP + Name of the Membership to list Bindings from. + +FLAGS + --location=LOCATION; default="global" + Name of the Membership location to list Bindings from. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet memberships bindings list + diff --git a/gcloud/alpha/container/fleet/memberships/bindings/update b/gcloud/alpha/container/fleet/memberships/bindings/update new file mode 100644 index 000000000..330f3a050 --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/bindings/update @@ -0,0 +1,93 @@ +NAME + gcloud alpha container fleet memberships bindings update - update the + Binding in a Membership + +SYNOPSIS + gcloud alpha container fleet memberships bindings update + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The Binding does not exist in the Membership. + ▪ The caller does not have permission to access the Membership/Binding. + ▪ The Scope specified does not exist. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To update the binding BINDING_NAME in global membership MEMBERSHIP_NAME in + the active project: + + $ gcloud alpha container fleet memberships bindings update \ + BINDING_NAME --membership=MEMBERSHIP_NAME + + To update a Binding BINDING_NAME associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with membership name and associated Scope + SCOPE_NAME. + + $ gcloud alpha container fleet memberships bindings update \ + BINDING_NAME --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --fleet=FLEET + Bindings for all the membership related scopes in the fleet would be + updated. + + --scope=SCOPE + Scope related to the Binding. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet memberships bindings update + diff --git a/gcloud/alpha/container/fleet/memberships/help b/gcloud/alpha/container/fleet/memberships/help index 436c49f6c..8f8ef9fba 100644 --- a/gcloud/alpha/container/fleet/memberships/help +++ b/gcloud/alpha/container/fleet/memberships/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + bindings + (ALPHA) Membership Bindings for permissions. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/alpha/container/fleet/namespaces/create b/gcloud/alpha/container/fleet/namespaces/create new file mode 100644 index 000000000..754002d1d --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/create @@ -0,0 +1,63 @@ +NAME + gcloud alpha container fleet namespaces create - create a fleet namespace + +SYNOPSIS + gcloud alpha container fleet namespaces create NAME [--scope=SCOPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The project has a fleet namespace with the same name. + ▪ The caller does not have permission to access the given project. + +EXAMPLES + To create a fleet namespace with name NAMESPACE in the active project, run: + + $ gcloud alpha container fleet namespaces create NAMESPACE + + To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with + name NAMESPACE, run: + + $ gcloud alpha container fleet namespaces create NAMESPACE \ + --scope=SCOPE --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the fleet namespace to be created. Must comply with RFC 1123 + (up to 63 characters, alphanumeric and '-') + +FLAGS + Scope resource - The group of arguments defining the Fleet Scope. 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 --scope 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 --scope on the command line with a fully + specified name; + ◆ global is the only supported location. + + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument --scope on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces create + diff --git a/gcloud/alpha/container/fleet/namespaces/delete b/gcloud/alpha/container/fleet/namespaces/delete new file mode 100644 index 000000000..adc391048 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/delete @@ -0,0 +1,43 @@ +NAME + gcloud alpha container fleet namespaces delete - delete a fleet namespace + +SYNOPSIS + gcloud alpha container fleet namespaces delete NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The namespace specified does not exist. + ▪ The caller does not have permission to access the given project or + namespace. + +EXAMPLES + To delete fleet namespace NAMESPACE in the active project: + + $ gcloud alpha container fleet namespaces delete NAMESPACE + + To delete fleet namespace NAMESPACE in project PROJECT_ID: + + $ gcloud alpha container fleet namespaces delete NAMESPACE \ + --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the fleet namespace to be deleted. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces delete + diff --git a/gcloud/alpha/container/fleet/namespaces/describe b/gcloud/alpha/container/fleet/namespaces/describe new file mode 100644 index 000000000..f61916da7 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/describe @@ -0,0 +1,45 @@ +NAME + gcloud alpha container fleet namespaces describe - show fleet namespace + info + +SYNOPSIS + gcloud alpha container fleet namespaces describe NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The namespace specified does not exist in the project. + ▪ The caller does not have permission to access the project or + namespace. + +EXAMPLES + To print metadata for the namespace NAMESPACE in the active project, run: + + $ gcloud alpha container fleet namespaces describe NAMESPACE + + To print metadata for the namespace NAMESPACE in project PROJECT_ID, run: + + $ gcloud alpha container fleet namespaces describe NAMESPACE \ + --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the fleet namespace to be described. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces describe + diff --git a/gcloud/alpha/container/fleet/namespaces/get-credentials b/gcloud/alpha/container/fleet/namespaces/get-credentials new file mode 100644 index 000000000..989d7b764 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/get-credentials @@ -0,0 +1,60 @@ +NAME + gcloud alpha container fleet namespaces get-credentials - fetch credentials + for a membership with a particular namespace + +SYNOPSIS + gcloud alpha container fleet namespaces get-credentials NAMESPACE + [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION] + [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using + namespace NAMESPACE in the config: + + $ gcloud alpha container fleet namespaces get-credentials \ + NAMESPACE --membership=MEMBERSHIP --membership-location=global \ + --set-namespace-in-config=true + + Get the Connect Gateway kubeconfig for global membership MEMBERSHIP: + + $ gcloud alpha container fleet namespaces get-credentials \ + NAMESPACE --membership=MEMBERSHIP --membership-location=global + +POSITIONAL ARGUMENTS + NAMESPACE + Name of the namespace for which to get access to memberships. + +FLAGS + --membership=MEMBERSHIP + Membership ID to get credentials from. If not provided, a prompt will + offer a list of memberships in the fleet. + + --membership-location=MEMBERSHIP_LOCATION + The location of the membership resource, e.g. us-central1. If not + specified, defaults to global. + + --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG + If true, the default namespace for the context in the generated + kubeconfig will be set to the Fleet namespace (i.e. the name given as + the positional argument in this command). + + Otherwise, no default namespace will be set, functioning the same as + gcloud container fleet memberships get-credentials. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces get-credentials + diff --git a/gcloud/alpha/container/fleet/namespaces/help b/gcloud/alpha/container/fleet/namespaces/help new file mode 100644 index 000000000..893d3e083 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/help @@ -0,0 +1,60 @@ +NAME + gcloud alpha container fleet namespaces - fleet namespaces are the fleet + equivalent of k8s cluster namespaces + +SYNOPSIS + gcloud alpha container fleet namespaces GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command group allows for manipulation of fleet namespaces. + +EXAMPLES + Manage fleet namespaces: + + $ gcloud alpha container fleet namespaces --help + + Manage RBAC RoleBindings in a fleet namespace: + + $ gcloud alpha container fleet namespaces rbacrolebindings --help + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + rbacrolebindings + (ALPHA) Fleet namespace RBAC RoleBindings for permissions. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a fleet namespace. + + delete + (ALPHA) Delete a fleet namespace. + + describe + (ALPHA) Show fleet namespace info. + + get-credentials + (ALPHA) Fetch credentials for a membership with a particular namespace. + + list + (ALPHA) List fleet namespaces in a project. + + update + (ALPHA) Update a fleet namespace. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces + diff --git a/gcloud/alpha/container/fleet/namespaces/list b/gcloud/alpha/container/fleet/namespaces/list new file mode 100644 index 000000000..f18c8aab7 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/list @@ -0,0 +1,71 @@ +NAME + gcloud alpha container fleet namespaces list - list fleet namespaces in a + project + +SYNOPSIS + gcloud alpha container fleet namespaces list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The user does not have access to the project specified. + +EXAMPLES + The following command lists namespaces in the active project: + + $ gcloud alpha container fleet namespaces list + + The following command lists namespaces in project PROJECT_ID: + + $ gcloud alpha container fleet namespaces list --project=PROJECT_ID + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces list + diff --git a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/create b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/create new file mode 100644 index 000000000..5ab7b057b --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/create @@ -0,0 +1,90 @@ +NAME + gcloud alpha container fleet namespaces rbacrolebindings create - create an + RBAC RoleBinding + +SYNOPSIS + gcloud alpha container fleet namespaces rbacrolebindings create + (NAME : --location=LOCATION --namespace=NAMESPACE) --role=ROLE + (--group=GROUP | --user=USER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The RBAC RoleBinding already exists. + ▪ The caller does not have permission to access the given namespace. + +EXAMPLES + To create an admin RBAC RoleBinding RBRB in namespace NAMESPACE for user + person@google.com, run: + + $ gcloud alpha container fleet namespaces rbacrolebindings create \ + RBRB --namespace=NAMESPACE --role=admin --user=person@google.com + + To create a viewer RBAC RoleBinding RBRB in namespace NAMESPACE for group + people@google.com, run: + + $ gcloud alpha container fleet namespaces rbacrolebindings create \ + RBRB --namespace=NAMESPACE --role=viewer \ + --group=people@google.com + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +REQUIRED FLAGS + --role=ROLE + Role to assign. ROLE must be one of: admin, edit, view. + + Exactly one of these must be specified: + + --group=GROUP + Group for the RoleBinding. + + --user=USER + User for the RoleBinding. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces rbacrolebindings create + diff --git a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/delete b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/delete new file mode 100644 index 000000000..376ef0f37 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/delete @@ -0,0 +1,71 @@ +NAME + gcloud alpha container fleet namespaces rbacrolebindings delete - delete a + fleet namespace RBAC RoleBinding + +SYNOPSIS + gcloud alpha container fleet namespaces rbacrolebindings delete + (NAME : --location=LOCATION --namespace=NAMESPACE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The RoleBinding specified does not exist. + ▪ The caller does not have permission to access the given RoleBinding. + +EXAMPLES + To delete RBAC RoleBinding RBRB in namespace NAMESPACE in the active + project: + + $ gcloud alpha container fleet namespaces rbacrolebindings delete \ + RBRB --namespace=NAMESPACE + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces rbacrolebindings delete + diff --git a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/describe b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/describe new file mode 100644 index 000000000..96ae94813 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/describe @@ -0,0 +1,71 @@ +NAME + gcloud alpha container fleet namespaces rbacrolebindings describe - show + fleet namespace RBAC RoleBinding information + +SYNOPSIS + gcloud alpha container fleet namespaces rbacrolebindings describe + (NAME : --location=LOCATION --namespace=NAMESPACE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The RoleBinding specified does not exist in the project. + ▪ The caller does not have permission to access the RoleBinding. + +EXAMPLES + To print metadata for RBAC RoleBinding RBRB in the namespace NAMESPACE, + run: + + $ gcloud alpha container fleet namespaces rbacrolebindings \ + describe RBRB --namespace=NAMESPACE + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces rbacrolebindings describe + diff --git a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/help b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/help new file mode 100644 index 000000000..24731691a --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/help @@ -0,0 +1,48 @@ +NAME + gcloud alpha container fleet namespaces rbacrolebindings - fleet namespace + RBAC RoleBindings for permissions + +SYNOPSIS + gcloud alpha container fleet namespaces rbacrolebindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command group allows for manipulation of fleet namespace RBAC + RoleBindings. + +EXAMPLES + Manage RBAC RoleBindings: + + $ gcloud alpha container fleet namespaces rbacrolebindings --help + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create an RBAC RoleBinding. + + delete + (ALPHA) Delete a fleet namespace RBAC RoleBinding. + + describe + (ALPHA) Show fleet namespace RBAC RoleBinding information. + + list + (ALPHA) List RBAC RoleBindings in a fleet namespace. + + update + (ALPHA) Update a fleet namespace RBAC RoleBinding. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces rbacrolebindings + diff --git a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/list b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/list new file mode 100644 index 000000000..66f9f0be5 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/list @@ -0,0 +1,74 @@ +NAME + gcloud alpha container fleet namespaces rbacrolebindings list - list RBAC + RoleBindings in a fleet namespace + +SYNOPSIS + gcloud alpha container fleet namespaces rbacrolebindings list + --namespace=NAMESPACE [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The namespace specified does not exist. + ▪ The user does not have access to the specified namespace. + +EXAMPLES + The following command lists RBAC RoleBindings in namespace NAMESPACE in + project PROJECT_ID: + + $ gcloud alpha container fleet namespaces rbacrolebindings list \ + --namespace=NAMESPACE --project=PROJECT_ID + +REQUIRED FLAGS + --namespace=NAMESPACE + Name of the fleet namespace to list RBAC RoleBindings from. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces rbacrolebindings list + diff --git a/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/update b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/update new file mode 100644 index 000000000..419810809 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/rbacrolebindings/update @@ -0,0 +1,90 @@ +NAME + gcloud alpha container fleet namespaces rbacrolebindings update - update a + fleet namespace RBAC RoleBinding + +SYNOPSIS + gcloud alpha container fleet namespaces rbacrolebindings update + (NAME : --location=LOCATION --namespace=NAMESPACE) [--role=ROLE] + [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The RoleBinding does not exist in the project. + ▪ The caller does not have permission to access the RoleBinding. + +EXAMPLES + To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active + project to the viewer role: + + $ gcloud alpha container fleet namespaces rbacrolebindings update \ + RBRB --namespace=NAMESPACE --role=viewer + + To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active + project to the user someone@google.com: + + $ gcloud alpha container fleet namespaces rbacrolebindings update \ + RBRB --namespace=NAMESPACE --user=someone@google.com + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +FLAGS + --role=ROLE + Role for the RBACRoleBinding to update to. ROLE must be one of: admin, + edit, view. + + At most one of these can be specified: + + --group=GROUP + Group for the RBACRoleBinding to update to. + + --user=USER + User for the RBACRoleBinding to update to. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces rbacrolebindings update + diff --git a/gcloud/alpha/container/fleet/namespaces/update b/gcloud/alpha/container/fleet/namespaces/update new file mode 100644 index 000000000..0db8b2169 --- /dev/null +++ b/gcloud/alpha/container/fleet/namespaces/update @@ -0,0 +1,62 @@ +NAME + gcloud alpha container fleet namespaces update - update a fleet namespace + +SYNOPSIS + gcloud alpha container fleet namespaces update NAME [--scope=SCOPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The fleet namespace does not exist in the project. + ▪ The caller does not have permission to access the project or + namespace. + +EXAMPLES + To update the namespace NAMESPACE in the active project: + + $ gcloud alpha container fleet namespaces update NAMESPACE + + To update the namespace NAMESPACE in project PROJECT_ID: + + $ gcloud alpha container fleet namespaces update NAMESPACE \ + --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the namespace to be updated. + +FLAGS + Scope resource - The group of arguments defining the Fleet Scope. 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 --scope 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 --scope on the command line with a fully + specified name; + ◆ global is the only supported location. + + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument --scope on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet namespaces update + diff --git a/gcloud/alpha/container/fleet/scopes/create b/gcloud/alpha/container/fleet/scopes/create new file mode 100644 index 000000000..d8020129e --- /dev/null +++ b/gcloud/alpha/container/fleet/scopes/create @@ -0,0 +1,61 @@ +NAME + gcloud alpha container fleet scopes create - create a new fleet scope + +SYNOPSIS + gcloud alpha container fleet scopes create SCOPE [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Fleet Scope resource. + +EXAMPLES + Create a new scope SCOPE_NAME in the active project's fleet: + + $ gcloud alpha container fleet scopes create SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - The fleet scope resourse to be created. 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 scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. To set the + location attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ global is the only supported location. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument scope 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 gkehub/v1alpha API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet scopes create + diff --git a/gcloud/alpha/container/fleet/scopes/delete b/gcloud/alpha/container/fleet/scopes/delete new file mode 100644 index 000000000..45df7c394 --- /dev/null +++ b/gcloud/alpha/container/fleet/scopes/delete @@ -0,0 +1,74 @@ +NAME + gcloud alpha container fleet scopes delete - delete a fleet scope + +SYNOPSIS + gcloud alpha container fleet scopes delete (SCOPE : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command deletes a Fleet Scope resource . + +EXAMPLES + First retrieve the ID of the scope using the command below. The output of + this command lists all the fleet's scopes, with their unique IDs in the + Names column: + + $ gcloud alpha container fleet scopes list + + Delete a scope from the active project's fleet: + + $ gcloud alpha container fleet scopes delete SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - The fleet scope to delete. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument scope 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 name. To set the location attribute: + ▸ provide the argument scope on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +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 gkehub/v1alpha API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet scopes delete + diff --git a/gcloud/alpha/container/fleet/scopes/describe b/gcloud/alpha/container/fleet/scopes/describe new file mode 100644 index 000000000..5c74c2bfb --- /dev/null +++ b/gcloud/alpha/container/fleet/scopes/describe @@ -0,0 +1,69 @@ +NAME + gcloud alpha container fleet scopes describe - describe a fleet scope + +SYNOPSIS + gcloud alpha container fleet scopes describe (SCOPE : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Fleet Scope. + +EXAMPLES + First retrieve the ID of the scope using the command below. The output of + this command lists all the fleet's members, with their unique IDs in the + Names column: + + $ gcloud alpha container fleet scopes list + + Then describe it: + + $ gcloud alpha container fleet scopes describe SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - The scope to describe. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. To set + the project attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument scope 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 name. To set the location attribute: + ▸ provide the argument scope on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkehub/v1alpha API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet scopes describe + diff --git a/gcloud/alpha/container/fleet/scopes/help b/gcloud/alpha/container/fleet/scopes/help new file mode 100644 index 000000000..6efd09985 --- /dev/null +++ b/gcloud/alpha/container/fleet/scopes/help @@ -0,0 +1,37 @@ +NAME + gcloud alpha container fleet scopes - manage scopes of all your GKE fleets + +SYNOPSIS + gcloud alpha container fleet scopes COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage scopes of all your GKE fleets. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a new fleet scope. + + delete + (ALPHA) Delete a fleet scope. + + describe + (ALPHA) Describe a fleet scope. + + list + (ALPHA) List fleet scopes. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet scopes + diff --git a/gcloud/alpha/container/fleet/scopes/list b/gcloud/alpha/container/fleet/scopes/list new file mode 100644 index 000000000..b8e269edc --- /dev/null +++ b/gcloud/alpha/container/fleet/scopes/list @@ -0,0 +1,69 @@ +NAME + gcloud alpha container fleet scopes list - list fleet scopes + +SYNOPSIS + gcloud alpha container fleet scopes list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List scopes in a fleet. + +EXAMPLES + List scopes in the active project's fleet: + + $ gcloud alpha container fleet scopes list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkehub/v1alpha API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet scopes list + diff --git a/gcloud/alpha/container/hub/help b/gcloud/alpha/container/hub/help index 0049441b9..f1b42baef 100644 --- a/gcloud/alpha/container/hub/help +++ b/gcloud/alpha/container/hub/help @@ -70,9 +70,16 @@ GROUPS multi-cluster-services (ALPHA) Manage Multi-cluster Services Feature. + namespaces + (ALPHA) Fleet namespaces are the fleet equivalent of k8s cluster + namespaces. + policycontroller (ALPHA) Manage Policy Controller Feature. + scopes + (ALPHA) Manage scopes of all your GKE fleets. + service-directory (ALPHA) Manage the Service Directory Feature. diff --git a/gcloud/alpha/container/hub/memberships/bindings/create b/gcloud/alpha/container/hub/memberships/bindings/create new file mode 100644 index 000000000..3e6413e59 --- /dev/null +++ b/gcloud/alpha/container/hub/memberships/bindings/create @@ -0,0 +1,106 @@ +NAME + gcloud alpha container hub memberships bindings create - create a + Membership Binding + +SYNOPSIS + gcloud alpha container hub memberships bindings create + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The Membership Binding already exists. + ▪ The caller does not have permission to access the given Membership. + ▪ The Scope or the Membership does not exist. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To create a membership binding BINDING_NAME in global membership + MEMBERSHIP_NAME for scope SCOPE_NAME, run: + + $ gcloud alpha container hub memberships bindings create \ + BINDING_NAME --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME + + To create a Binding BINDING_NAME associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with membership name and associated Scope + SCOPE_NAME. + + $ gcloud alpha container hub memberships bindings create \ + BINDING_NAME --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --fleet=FLEET + Membership Binding is created for all the Scopes in the Fleet for + given Membership. + + Scope resource - The group of arguments defining the Fleet Scope. 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 --scope 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 --scope on the command line with a fully + specified name; + ▸ global is the only supported location. + + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▫ provide the argument --scope on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub memberships bindings create + diff --git a/gcloud/alpha/container/hub/memberships/bindings/delete b/gcloud/alpha/container/hub/memberships/bindings/delete new file mode 100644 index 000000000..1dc21c298 --- /dev/null +++ b/gcloud/alpha/container/hub/memberships/bindings/delete @@ -0,0 +1,81 @@ +NAME + gcloud alpha container hub memberships bindings delete - delete a + Membership Binding + +SYNOPSIS + gcloud alpha container hub memberships bindings delete + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The Membership Binding specified does not exist. + ▪ The caller does not have permission to access the given Membership. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To delete Membership Binding BINDING_NAME in global Membership + MEMBERSHIP_NAME for a global membership: + + $ gcloud alpha container hub memberships bindings delete \ + BINDING_NAME --membership=MEMBERSHIP_NAME + + To delete a Binding BINDING_NAME associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with the membership name. + + $ gcloud alpha container hub memberships bindings delete \ + BINDING_NAME --membership=MEMBERSHIP_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub memberships bindings delete + diff --git a/gcloud/alpha/container/hub/memberships/bindings/describe b/gcloud/alpha/container/hub/memberships/bindings/describe new file mode 100644 index 000000000..3108dd677 --- /dev/null +++ b/gcloud/alpha/container/hub/memberships/bindings/describe @@ -0,0 +1,81 @@ +NAME + gcloud alpha container hub memberships bindings describe - show + Membership-Binding info + +SYNOPSIS + gcloud alpha container hub memberships bindings describe + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The Membership Binding specified does not exist in the project. + ▪ The caller does not have permission to access the Membership Binding. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To print metadata for the membership Binding BINDING_NAME in a global + membership MEMBERSHIP_NAME, run: + + $ gcloud alpha container hub memberships bindings describe \ + BINDING_NAME --membership=MEMBERSHIP_NAME + + To print metadata for the Binding BINDING_NAME associated with regional + membership MEMBERSHIP_NAME, provide the location LOCATION_NAME for the + Membership where the Binding belongs along with membership name. + + $ gcloud alpha container hub memberships bindings describe \ + BINDING_NAME --membership=MEMBERSHIP_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub memberships bindings describe + diff --git a/gcloud/alpha/container/hub/memberships/bindings/help b/gcloud/alpha/container/hub/memberships/bindings/help new file mode 100644 index 000000000..0e0d312c8 --- /dev/null +++ b/gcloud/alpha/container/hub/memberships/bindings/help @@ -0,0 +1,48 @@ +NAME + gcloud alpha container hub memberships bindings - membership Bindings for + permissions + +SYNOPSIS + gcloud alpha container hub memberships bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command group allows for manipulation of bindings associated + with membership-scope. + +EXAMPLES + Manage Bindings: + + $ gcloud alpha container hub memberships bindings --help + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a Membership Binding. + + delete + (ALPHA) Delete a Membership Binding. + + describe + (ALPHA) Show Membership-Binding info. + + list + (ALPHA) List Bindings in a Membership. + + update + (ALPHA) Update the Binding in a Membership. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub memberships bindings + diff --git a/gcloud/alpha/container/hub/memberships/bindings/list b/gcloud/alpha/container/hub/memberships/bindings/list new file mode 100644 index 000000000..9017aa69d --- /dev/null +++ b/gcloud/alpha/container/hub/memberships/bindings/list @@ -0,0 +1,87 @@ +NAME + gcloud alpha container hub memberships bindings list - list Bindings in a + Membership + +SYNOPSIS + gcloud alpha container hub memberships bindings list + --membership=MEMBERSHIP [--location=LOCATION; default="global"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The user does not have access to the Membership specified. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + The following command lists Bindings in global Membership MEMBERSHIP_NAME: + + $ gcloud alpha container hub memberships bindings list \ + --membership=MEMBERSHIP_NAME + + To list all the bindings associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with membership name. + + $ gcloud alpha container hub memberships bindings list \ + BINDING_NAME --membership=MEMBERSHIP_NAME \ + --location=LOCATION_NAME + +REQUIRED FLAGS + --membership=MEMBERSHIP + Name of the Membership to list Bindings from. + +FLAGS + --location=LOCATION; default="global" + Name of the Membership location to list Bindings from. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub memberships bindings list + diff --git a/gcloud/alpha/container/hub/memberships/bindings/update b/gcloud/alpha/container/hub/memberships/bindings/update new file mode 100644 index 000000000..dd1ad6553 --- /dev/null +++ b/gcloud/alpha/container/hub/memberships/bindings/update @@ -0,0 +1,93 @@ +NAME + gcloud alpha container hub memberships bindings update - update the Binding + in a Membership + +SYNOPSIS + gcloud alpha container hub memberships bindings update + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The Binding does not exist in the Membership. + ▪ The caller does not have permission to access the Membership/Binding. + ▪ The Scope specified does not exist. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To update the binding BINDING_NAME in global membership MEMBERSHIP_NAME in + the active project: + + $ gcloud alpha container hub memberships bindings update \ + BINDING_NAME --membership=MEMBERSHIP_NAME + + To update a Binding BINDING_NAME associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with membership name and associated Scope + SCOPE_NAME. + + $ gcloud alpha container hub memberships bindings update \ + BINDING_NAME --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --fleet=FLEET + Bindings for all the membership related scopes in the fleet would be + updated. + + --scope=SCOPE + Scope related to the Binding. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub memberships bindings update + diff --git a/gcloud/alpha/container/hub/memberships/help b/gcloud/alpha/container/hub/memberships/help index 1ff6189c7..1aaec5253 100644 --- a/gcloud/alpha/container/hub/memberships/help +++ b/gcloud/alpha/container/hub/memberships/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + bindings + (ALPHA) Membership Bindings for permissions. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/alpha/container/hub/namespaces/create b/gcloud/alpha/container/hub/namespaces/create new file mode 100644 index 000000000..a80eb6636 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/create @@ -0,0 +1,63 @@ +NAME + gcloud alpha container hub namespaces create - create a fleet namespace + +SYNOPSIS + gcloud alpha container hub namespaces create NAME [--scope=SCOPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The project has a fleet namespace with the same name. + ▪ The caller does not have permission to access the given project. + +EXAMPLES + To create a fleet namespace with name NAMESPACE in the active project, run: + + $ gcloud alpha container hub namespaces create NAMESPACE + + To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with + name NAMESPACE, run: + + $ gcloud alpha container hub namespaces create NAMESPACE \ + --scope=SCOPE --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the fleet namespace to be created. Must comply with RFC 1123 + (up to 63 characters, alphanumeric and '-') + +FLAGS + Scope resource - The group of arguments defining the Fleet Scope. 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 --scope 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 --scope on the command line with a fully + specified name; + ◆ global is the only supported location. + + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument --scope on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces create + diff --git a/gcloud/alpha/container/hub/namespaces/delete b/gcloud/alpha/container/hub/namespaces/delete new file mode 100644 index 000000000..9e60f6485 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/delete @@ -0,0 +1,43 @@ +NAME + gcloud alpha container hub namespaces delete - delete a fleet namespace + +SYNOPSIS + gcloud alpha container hub namespaces delete NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The namespace specified does not exist. + ▪ The caller does not have permission to access the given project or + namespace. + +EXAMPLES + To delete fleet namespace NAMESPACE in the active project: + + $ gcloud alpha container hub namespaces delete NAMESPACE + + To delete fleet namespace NAMESPACE in project PROJECT_ID: + + $ gcloud alpha container hub namespaces delete NAMESPACE \ + --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the fleet namespace to be deleted. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces delete + diff --git a/gcloud/alpha/container/hub/namespaces/describe b/gcloud/alpha/container/hub/namespaces/describe new file mode 100644 index 000000000..d085301eb --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/describe @@ -0,0 +1,43 @@ +NAME + gcloud alpha container hub namespaces describe - show fleet namespace info + +SYNOPSIS + gcloud alpha container hub namespaces describe NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The namespace specified does not exist in the project. + ▪ The caller does not have permission to access the project or + namespace. + +EXAMPLES + To print metadata for the namespace NAMESPACE in the active project, run: + + $ gcloud alpha container hub namespaces describe NAMESPACE + + To print metadata for the namespace NAMESPACE in project PROJECT_ID, run: + + $ gcloud alpha container hub namespaces describe NAMESPACE \ + --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the fleet namespace to be described. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces describe + diff --git a/gcloud/alpha/container/hub/namespaces/get-credentials b/gcloud/alpha/container/hub/namespaces/get-credentials new file mode 100644 index 000000000..abf049181 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/get-credentials @@ -0,0 +1,60 @@ +NAME + gcloud alpha container hub namespaces get-credentials - fetch credentials + for a membership with a particular namespace + +SYNOPSIS + gcloud alpha container hub namespaces get-credentials NAMESPACE + [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION] + [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using + namespace NAMESPACE in the config: + + $ gcloud alpha container hub namespaces get-credentials NAMESPACE \ + --membership=MEMBERSHIP --membership-location=global \ + --set-namespace-in-config=true + + Get the Connect Gateway kubeconfig for global membership MEMBERSHIP: + + $ gcloud alpha container hub namespaces get-credentials NAMESPACE \ + --membership=MEMBERSHIP --membership-location=global + +POSITIONAL ARGUMENTS + NAMESPACE + Name of the namespace for which to get access to memberships. + +FLAGS + --membership=MEMBERSHIP + Membership ID to get credentials from. If not provided, a prompt will + offer a list of memberships in the fleet. + + --membership-location=MEMBERSHIP_LOCATION + The location of the membership resource, e.g. us-central1. If not + specified, defaults to global. + + --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG + If true, the default namespace for the context in the generated + kubeconfig will be set to the Fleet namespace (i.e. the name given as + the positional argument in this command). + + Otherwise, no default namespace will be set, functioning the same as + gcloud container fleet memberships get-credentials. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces get-credentials + diff --git a/gcloud/alpha/container/hub/namespaces/help b/gcloud/alpha/container/hub/namespaces/help new file mode 100644 index 000000000..bb143e807 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/help @@ -0,0 +1,60 @@ +NAME + gcloud alpha container hub namespaces - fleet namespaces are the fleet + equivalent of k8s cluster namespaces + +SYNOPSIS + gcloud alpha container hub namespaces GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command group allows for manipulation of fleet namespaces. + +EXAMPLES + Manage fleet namespaces: + + $ gcloud alpha container hub namespaces --help + + Manage RBAC RoleBindings in a fleet namespace: + + $ gcloud alpha container hub namespaces rbacrolebindings --help + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + rbacrolebindings + (ALPHA) Fleet namespace RBAC RoleBindings for permissions. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a fleet namespace. + + delete + (ALPHA) Delete a fleet namespace. + + describe + (ALPHA) Show fleet namespace info. + + get-credentials + (ALPHA) Fetch credentials for a membership with a particular namespace. + + list + (ALPHA) List fleet namespaces in a project. + + update + (ALPHA) Update a fleet namespace. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces + diff --git a/gcloud/alpha/container/hub/namespaces/list b/gcloud/alpha/container/hub/namespaces/list new file mode 100644 index 000000000..0306abc95 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/list @@ -0,0 +1,71 @@ +NAME + gcloud alpha container hub namespaces list - list fleet namespaces in a + project + +SYNOPSIS + gcloud alpha container hub namespaces list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The user does not have access to the project specified. + +EXAMPLES + The following command lists namespaces in the active project: + + $ gcloud alpha container hub namespaces list + + The following command lists namespaces in project PROJECT_ID: + + $ gcloud alpha container hub namespaces list --project=PROJECT_ID + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces list + diff --git a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/create b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/create new file mode 100644 index 000000000..b84c95439 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/create @@ -0,0 +1,90 @@ +NAME + gcloud alpha container hub namespaces rbacrolebindings create - create an + RBAC RoleBinding + +SYNOPSIS + gcloud alpha container hub namespaces rbacrolebindings create + (NAME : --location=LOCATION --namespace=NAMESPACE) --role=ROLE + (--group=GROUP | --user=USER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The RBAC RoleBinding already exists. + ▪ The caller does not have permission to access the given namespace. + +EXAMPLES + To create an admin RBAC RoleBinding RBRB in namespace NAMESPACE for user + person@google.com, run: + + $ gcloud alpha container hub namespaces rbacrolebindings create \ + RBRB --namespace=NAMESPACE --role=admin --user=person@google.com + + To create a viewer RBAC RoleBinding RBRB in namespace NAMESPACE for group + people@google.com, run: + + $ gcloud alpha container hub namespaces rbacrolebindings create \ + RBRB --namespace=NAMESPACE --role=viewer \ + --group=people@google.com + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +REQUIRED FLAGS + --role=ROLE + Role to assign. ROLE must be one of: admin, edit, view. + + Exactly one of these must be specified: + + --group=GROUP + Group for the RoleBinding. + + --user=USER + User for the RoleBinding. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces rbacrolebindings create + diff --git a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/delete b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/delete new file mode 100644 index 000000000..099544207 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/delete @@ -0,0 +1,71 @@ +NAME + gcloud alpha container hub namespaces rbacrolebindings delete - delete a + fleet namespace RBAC RoleBinding + +SYNOPSIS + gcloud alpha container hub namespaces rbacrolebindings delete + (NAME : --location=LOCATION --namespace=NAMESPACE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The RoleBinding specified does not exist. + ▪ The caller does not have permission to access the given RoleBinding. + +EXAMPLES + To delete RBAC RoleBinding RBRB in namespace NAMESPACE in the active + project: + + $ gcloud alpha container hub namespaces rbacrolebindings delete \ + RBRB --namespace=NAMESPACE + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces rbacrolebindings delete + diff --git a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/describe b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/describe new file mode 100644 index 000000000..806885b48 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/describe @@ -0,0 +1,71 @@ +NAME + gcloud alpha container hub namespaces rbacrolebindings describe - show + fleet namespace RBAC RoleBinding information + +SYNOPSIS + gcloud alpha container hub namespaces rbacrolebindings describe + (NAME : --location=LOCATION --namespace=NAMESPACE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The RoleBinding specified does not exist in the project. + ▪ The caller does not have permission to access the RoleBinding. + +EXAMPLES + To print metadata for RBAC RoleBinding RBRB in the namespace NAMESPACE, + run: + + $ gcloud alpha container hub namespaces rbacrolebindings describe \ + RBRB --namespace=NAMESPACE + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces rbacrolebindings describe + diff --git a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/help b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/help new file mode 100644 index 000000000..a604dd124 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/help @@ -0,0 +1,48 @@ +NAME + gcloud alpha container hub namespaces rbacrolebindings - fleet namespace + RBAC RoleBindings for permissions + +SYNOPSIS + gcloud alpha container hub namespaces rbacrolebindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command group allows for manipulation of fleet namespace RBAC + RoleBindings. + +EXAMPLES + Manage RBAC RoleBindings: + + $ gcloud alpha container hub namespaces rbacrolebindings --help + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create an RBAC RoleBinding. + + delete + (ALPHA) Delete a fleet namespace RBAC RoleBinding. + + describe + (ALPHA) Show fleet namespace RBAC RoleBinding information. + + list + (ALPHA) List RBAC RoleBindings in a fleet namespace. + + update + (ALPHA) Update a fleet namespace RBAC RoleBinding. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces rbacrolebindings + diff --git a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/list b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/list new file mode 100644 index 000000000..c3a898b16 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/list @@ -0,0 +1,74 @@ +NAME + gcloud alpha container hub namespaces rbacrolebindings list - list RBAC + RoleBindings in a fleet namespace + +SYNOPSIS + gcloud alpha container hub namespaces rbacrolebindings list + --namespace=NAMESPACE [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The namespace specified does not exist. + ▪ The user does not have access to the specified namespace. + +EXAMPLES + The following command lists RBAC RoleBindings in namespace NAMESPACE in + project PROJECT_ID: + + $ gcloud alpha container hub namespaces rbacrolebindings list \ + --namespace=NAMESPACE --project=PROJECT_ID + +REQUIRED FLAGS + --namespace=NAMESPACE + Name of the fleet namespace to list RBAC RoleBindings from. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces rbacrolebindings list + diff --git a/gcloud/alpha/container/hub/namespaces/rbacrolebindings/update b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/update new file mode 100644 index 000000000..74a28fb40 --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/rbacrolebindings/update @@ -0,0 +1,90 @@ +NAME + gcloud alpha container hub namespaces rbacrolebindings update - update a + fleet namespace RBAC RoleBinding + +SYNOPSIS + gcloud alpha container hub namespaces rbacrolebindings update + (NAME : --location=LOCATION --namespace=NAMESPACE) [--role=ROLE] + [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The RoleBinding does not exist in the project. + ▪ The caller does not have permission to access the RoleBinding. + +EXAMPLES + To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active + project to the viewer role: + + $ gcloud alpha container hub namespaces rbacrolebindings update \ + RBRB --namespace=NAMESPACE --role=viewer + + To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active + project to the user someone@google.com: + + $ gcloud alpha container hub namespaces rbacrolebindings update \ + RBRB --namespace=NAMESPACE --user=someone@google.com + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +FLAGS + --role=ROLE + Role for the RBACRoleBinding to update to. ROLE must be one of: admin, + edit, view. + + At most one of these can be specified: + + --group=GROUP + Group for the RBACRoleBinding to update to. + + --user=USER + User for the RBACRoleBinding to update to. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces rbacrolebindings update + diff --git a/gcloud/alpha/container/hub/namespaces/update b/gcloud/alpha/container/hub/namespaces/update new file mode 100644 index 000000000..d98e3004a --- /dev/null +++ b/gcloud/alpha/container/hub/namespaces/update @@ -0,0 +1,62 @@ +NAME + gcloud alpha container hub namespaces update - update a fleet namespace + +SYNOPSIS + gcloud alpha container hub namespaces update NAME [--scope=SCOPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The fleet namespace does not exist in the project. + ▪ The caller does not have permission to access the project or + namespace. + +EXAMPLES + To update the namespace NAMESPACE in the active project: + + $ gcloud alpha container hub namespaces update NAMESPACE + + To update the namespace NAMESPACE in project PROJECT_ID: + + $ gcloud alpha container hub namespaces update NAMESPACE \ + --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the namespace to be updated. + +FLAGS + Scope resource - The group of arguments defining the Fleet Scope. 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 --scope 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 --scope on the command line with a fully + specified name; + ◆ global is the only supported location. + + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument --scope on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub namespaces update + diff --git a/gcloud/alpha/container/hub/scopes/create b/gcloud/alpha/container/hub/scopes/create new file mode 100644 index 000000000..d323d5f96 --- /dev/null +++ b/gcloud/alpha/container/hub/scopes/create @@ -0,0 +1,61 @@ +NAME + gcloud alpha container hub scopes create - create a new fleet scope + +SYNOPSIS + gcloud alpha container hub scopes create SCOPE [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Fleet Scope resource. + +EXAMPLES + Create a new scope SCOPE_NAME in the active project's fleet: + + $ gcloud alpha container hub scopes create SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - The fleet scope resourse to be created. 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 scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. To set the + location attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ global is the only supported location. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument scope 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 gkehub/v1alpha API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub scopes create + diff --git a/gcloud/alpha/container/hub/scopes/delete b/gcloud/alpha/container/hub/scopes/delete new file mode 100644 index 000000000..a89bb20be --- /dev/null +++ b/gcloud/alpha/container/hub/scopes/delete @@ -0,0 +1,74 @@ +NAME + gcloud alpha container hub scopes delete - delete a fleet scope + +SYNOPSIS + gcloud alpha container hub scopes delete (SCOPE : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command deletes a Fleet Scope resource . + +EXAMPLES + First retrieve the ID of the scope using the command below. The output of + this command lists all the fleet's scopes, with their unique IDs in the + Names column: + + $ gcloud alpha container hub scopes list + + Delete a scope from the active project's fleet: + + $ gcloud alpha container hub scopes delete SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - The fleet scope to delete. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument scope 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 name. To set the location attribute: + ▸ provide the argument scope on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +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 gkehub/v1alpha API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub scopes delete + diff --git a/gcloud/alpha/container/hub/scopes/describe b/gcloud/alpha/container/hub/scopes/describe new file mode 100644 index 000000000..62e462985 --- /dev/null +++ b/gcloud/alpha/container/hub/scopes/describe @@ -0,0 +1,69 @@ +NAME + gcloud alpha container hub scopes describe - describe a fleet scope + +SYNOPSIS + gcloud alpha container hub scopes describe (SCOPE : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Fleet Scope. + +EXAMPLES + First retrieve the ID of the scope using the command below. The output of + this command lists all the fleet's members, with their unique IDs in the + Names column: + + $ gcloud alpha container hub scopes list + + Then describe it: + + $ gcloud alpha container hub scopes describe SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - The scope to describe. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. To set + the project attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument scope 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 name. To set the location attribute: + ▸ provide the argument scope on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkehub/v1alpha API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub scopes describe + diff --git a/gcloud/alpha/container/hub/scopes/help b/gcloud/alpha/container/hub/scopes/help new file mode 100644 index 000000000..b86c53d8c --- /dev/null +++ b/gcloud/alpha/container/hub/scopes/help @@ -0,0 +1,37 @@ +NAME + gcloud alpha container hub scopes - manage scopes of all your GKE fleets + +SYNOPSIS + gcloud alpha container hub scopes COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage scopes of all your GKE fleets. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a new fleet scope. + + delete + (ALPHA) Delete a fleet scope. + + describe + (ALPHA) Describe a fleet scope. + + list + (ALPHA) List fleet scopes. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub scopes + diff --git a/gcloud/alpha/container/hub/scopes/list b/gcloud/alpha/container/hub/scopes/list new file mode 100644 index 000000000..9be85c93f --- /dev/null +++ b/gcloud/alpha/container/hub/scopes/list @@ -0,0 +1,69 @@ +NAME + gcloud alpha container hub scopes list - list fleet scopes + +SYNOPSIS + gcloud alpha container hub scopes list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List scopes in a fleet. + +EXAMPLES + List scopes in the active project's fleet: + + $ gcloud alpha container hub scopes list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkehub/v1alpha API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container hub scopes list + diff --git a/gcloud/alpha/container/vmware/clusters/delete b/gcloud/alpha/container/vmware/clusters/delete index fcb113ab5..5418b2e2e 100644 --- a/gcloud/alpha/container/vmware/clusters/delete +++ b/gcloud/alpha/container/vmware/clusters/delete @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha container vmware clusters delete (CLUSTER : --location=LOCATION) [--allow-missing] [--async] [--force] - [GCLOUD_WIDE_FLAG ...] + [--ignore-errors] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Delete an Anthos cluster on VMware. @@ -56,6 +56,10 @@ FLAGS If set, any node pools from the cluster will also be deleted. This flag is required if the cluster has any associated node pools. + --ignore-errors + If set, the deletion of a VMware user cluster resource will succeed + even if errors occur during 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/firebase/test/android/run b/gcloud/alpha/firebase/test/android/run index d0ef92383..06754ce91 100644 --- a/gcloud/alpha/firebase/test/android/run +++ b/gcloud/alpha/firebase/test/android/run @@ -111,6 +111,12 @@ EXAMPLES executions, but only the subset of executions with valid dimension combinations will actually run your tests. + To help you identify and locate your test matrix in the Firebase console, + run: + + $ gcloud alpha firebase test android run --app=APP_APK \ + --client-details=matrixLabel="Example matrix label" + Controlling Results Storage By default, Firebase Test Lab stores detailed test results for a limited diff --git a/gcloud/alpha/firebase/test/ios/run b/gcloud/alpha/firebase/test/ios/run index d873fe39e..59ad4b678 100644 --- a/gcloud/alpha/firebase/test/ios/run +++ b/gcloud/alpha/firebase/test/ios/run @@ -69,6 +69,12 @@ EXAMPLES $ gcloud alpha firebase test ios run --test=XCTEST_ZIP \ --xcode-version=9.4.1 + To help you identify and locate your test matrix in the Firebase console, + run: + + $ gcloud alpha firebase test ios run --test=XCTEST_ZIP \ + --client-details=matrixLabel="Example matrix label" + To run an iOS game loop, specify the --type and --app flags: $ gcloud alpha firebase test ios run --type=game-loop --app=app.ipa diff --git a/gcloud/alpha/firestore/databases/create b/gcloud/alpha/firestore/databases/create index f24dad352..0f45a2e5d 100644 --- a/gcloud/alpha/firestore/databases/create +++ b/gcloud/alpha/firestore/databases/create @@ -1,26 +1,26 @@ NAME gcloud alpha firestore databases create - create a Google Cloud Firestore - Native database via Firestore API + database via Firestore API SYNOPSIS gcloud alpha firestore databases create --location=LOCATION [--database=DATABASE; default="(default)"] [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] -DESCRIPTION - (ALPHA) 'EXAMPLES': To create Cloud Firestore Native database in nam5. +EXAMPLES + To create Firestore Native database in nam5. $ gcloud alpha firestore databases create --location=nam5 - To create Cloud Datastore Mode database in us-east1. + To create Datastore Mode database in us-east1. $ gcloud alpha firestore databases create --location=us-east1 \ --type=datastore-mode - To create Cloud Datastore Mode database in us-east1 with a databaseId foo. + To create Datastore Mode database in us-east1 with a databaseId foo. - $ gcloud alpha firestore databases create foo --location=us-east1 \ - --type=datastore-mode + $ gcloud alpha firestore databases create --database=mytest \ + --location=us-east1 --type=datastore-mode REQUIRED FLAGS --location=LOCATION diff --git a/gcloud/alpha/firestore/databases/help b/gcloud/alpha/firestore/databases/help index 66cdfe79e..b1f51183d 100644 --- a/gcloud/alpha/firestore/databases/help +++ b/gcloud/alpha/firestore/databases/help @@ -17,8 +17,7 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create a Google Cloud Firestore Native database via Firestore - API. + (ALPHA) Create a Google Cloud Firestore database via Firestore API. describe (ALPHA) Describe a Google Cloud Firestore database. diff --git a/gcloud/alpha/iam/workforce-pools/create-login-config b/gcloud/alpha/iam/workforce-pools/create-login-config index bef3124ed..e94bf21cd 100644 --- a/gcloud/alpha/iam/workforce-pools/create-login-config +++ b/gcloud/alpha/iam/workforce-pools/create-login-config @@ -45,5 +45,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 iam workforce-pools create-login-config + + $ gcloud beta iam workforce-pools create-login-config diff --git a/gcloud/alpha/kms/inventory/get-protected-resources-summary b/gcloud/alpha/kms/inventory/get-protected-resources-summary index 5e3be40ba..c7d0c8213 100644 --- a/gcloud/alpha/kms/inventory/get-protected-resources-summary +++ b/gcloud/alpha/kms/inventory/get-protected-resources-summary @@ -8,7 +8,18 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Gets the protected resources summary. + (ALPHA) gcloud alpha kms inventory get-protected-resources-summary returns + a summary of the resources a key is protecting. + + The summary includes: How many projects contain protected resources How + many protected resources there are What types of protected resources The + count for each type of protected resource + +EXAMPLES + To view the summary of protected resources for the key puppy, run: + + $ gcloud alpha kms inventory get-protected-resources-summary \ + --keyname=puppy REQUIRED FLAGS Key resource - The KMS key resource. The arguments in this group can be @@ -53,5 +64,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 kms inventory get-protected-resources-summary diff --git a/gcloud/alpha/kms/inventory/help b/gcloud/alpha/kms/inventory/help index f4846633a..8f3d5220a 100644 --- a/gcloud/alpha/kms/inventory/help +++ b/gcloud/alpha/kms/inventory/help @@ -29,5 +29,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 kms inventory diff --git a/gcloud/alpha/kms/inventory/list-keys b/gcloud/alpha/kms/inventory/list-keys index 5a6d75605..3efa5d091 100644 --- a/gcloud/alpha/kms/inventory/list-keys +++ b/gcloud/alpha/kms/inventory/list-keys @@ -7,7 +7,17 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Lists the keys in a project. + (ALPHA) gcloud alpha kms inventory list-keys lists the keys in the + specified project. + +EXAMPLES + To view the keys in the default project, run: + + $ gcloud alpha kms inventory list-keys + + To view the keys in project jellyfish, run: + + $ gcloud alpha kms inventory list-keys --project=jellyfish LIST COMMAND FLAGS --filter=EXPRESSION @@ -53,5 +63,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 kms inventory list-keys diff --git a/gcloud/alpha/kms/inventory/search-protected-resources b/gcloud/alpha/kms/inventory/search-protected-resources index 4e0def2e7..7f65cc416 100644 --- a/gcloud/alpha/kms/inventory/search-protected-resources +++ b/gcloud/alpha/kms/inventory/search-protected-resources @@ -10,7 +10,16 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Searches the resources protected by a key. + (ALPHA) gcloud alpha kms inventory search-protected-resources returns a + list of the resources a key is protecting within the specified + organization. + +EXAMPLES + To view the protected resources for the key puppy and organization number + 1234 run: + + $ gcloud alpha kms inventory search-protected-resources \ + --keyname=puppy --scope=1234 REQUIRED FLAGS --scope=ORGANIZATION_ID @@ -90,5 +99,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 kms inventory search-protected-resources diff --git a/gcloud/alpha/logging/buckets/create b/gcloud/alpha/logging/buckets/create index 437d80a75..b25f4838c 100644 --- a/gcloud/alpha/logging/buckets/create +++ b/gcloud/alpha/logging/buckets/create @@ -2,7 +2,7 @@ NAME gcloud alpha logging buckets create - create a bucket SYNOPSIS - gcloud alpha logging buckets create BUCKET_ID --location=LOCATION + gcloud alpha logging buckets create BUCKET_ID --location=LOCATION [--async] [--cmek-kms-key-name=CMEK_KMS_KEY_NAME] [--description=DESCRIPTION] [--enable-analytics] [--index=[KEY=VALUE, ...,...]] [--restricted-fields=[RESTRICTED_FIELD,...]] @@ -38,6 +38,11 @@ EXAMPLES $ gcloud alpha logging buckets create my-bucket \ --location=us-central1 --cmek-kms-key-name=CMEK_KMS_KEY_NAME + To asynchronously create a bucket enrolled into Log Analytics, run: + + $ gcloud alpha logging buckets create my-bucket --location=global \ + --async --enable-analytics + POSITIONAL ARGUMENTS BUCKET_ID ID of the bucket to create. @@ -48,6 +53,10 @@ REQUIRED FLAGS location cannot be changed. OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + --cmek-kms-key-name=CMEK_KMS_KEY_NAME A valid kms_key_name will enable CMEK for the bucket. @@ -55,8 +64,8 @@ OPTIONAL FLAGS A textual description for the bucket. --enable-analytics - Whether to opt the bucket into advanced log analytics. This field may - only be set at bucket creation and cannot be changed later. + Whether to opt the bucket into Log Analytics. Once opted in, the bucket + cannot be opted out of Log Analytics. --index=[KEY=VALUE, ...,...] Specify an index to be added to the log bucket. This flag can be diff --git a/gcloud/alpha/logging/buckets/update b/gcloud/alpha/logging/buckets/update index 2024d51d1..9285fe5d0 100644 --- a/gcloud/alpha/logging/buckets/update +++ b/gcloud/alpha/logging/buckets/update @@ -3,9 +3,9 @@ NAME SYNOPSIS gcloud alpha logging buckets update BUCKET_ID --location=LOCATION - [--add-index=[KEY=VALUE, ...,...]] [--clear-indexes] + [--add-index=[KEY=VALUE, ...,...]] [--async] [--clear-indexes] [--cmek-kms-key-name=CMEK_KMS_KEY_NAME] [--description=DESCRIPTION] - [--enable-loglink] [--locked] [--remove-indexes=[FIELD PATH,...]] + [--enable-analytics] [--locked] [--remove-indexes=[FIELD PATH,...]] [--restricted-fields=[RESTRICTED_FIELD,...]] [--retention-days=RETENTION_DAYS] [--update-index=[KEY=VALUE, ...,...]] [GCLOUD_WIDE_FLAG ...] @@ -44,6 +44,11 @@ EXAMPLES $ gcloud alpha logging buckets update my-bucket --location=global \ --cmek-kms-key-name=CMEK_KEY_NAME + To asynchronously enroll a bucket in your project into Log Analytics, run: + + $ gcloud alpha logging buckets update my-bucket --location=global \ + --async --enable-analytics + POSITIONAL ARGUMENTS BUCKET_ID The id of the bucket to update. @@ -69,6 +74,10 @@ OPTIONAL FLAGS The type of data in this index. For example: INDEX_TYPE_STRING Supported types are strings and integers. + --async + Return immediately, without waiting for the operation in progress to + complete. + --clear-indexes Remove all logging indexes from the bucket. @@ -78,12 +87,9 @@ OPTIONAL FLAGS --description=DESCRIPTION A new description for the bucket. - --enable-loglink - Enables a linked dataset in BigQuery corresponding to this log bucket. - The linked dataset contains authorized views which give a ready-only - access to logs in BigQuery. This option can only be enabled in a log - bucket with advanced log analytics enabled. Use --no-enable-loglink to - disable the linked dataset. + --enable-analytics + Whether to opt the bucket into Log Analytics. Once opted in, the bucket + cannot be opted out of Log Analytics. --locked Lock the bucket and prevent it from being modified or deleted (unless diff --git a/gcloud/alpha/logging/help b/gcloud/alpha/logging/help index 3e32bddfd..d96c3308f 100644 --- a/gcloud/alpha/logging/help +++ b/gcloud/alpha/logging/help @@ -18,6 +18,9 @@ GROUPS buckets (ALPHA) Manage Cloud Logging buckets. + links + (ALPHA) Manage log links. + locations (ALPHA) Query Cloud Logging locations. diff --git a/gcloud/alpha/logging/links/create b/gcloud/alpha/logging/links/create new file mode 100644 index 000000000..dd6bd50ce --- /dev/null +++ b/gcloud/alpha/logging/links/create @@ -0,0 +1,82 @@ +NAME + gcloud alpha logging links create - create a link on an analytics log + bucket + +SYNOPSIS + gcloud alpha logging links create LINK_ID --bucket=BUCKET + --location=LOCATION [--async] [--description=DESCRIPTION] + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a link for a log bucket. + +EXAMPLES + To create a link in a project, run: + + $ gcloud alpha logging links create my-link --bucket=my-bucket \ + --location=global + +POSITIONAL ARGUMENTS + LINK_ID + ID of the link to create. + +REQUIRED FLAGS + --bucket=BUCKET + ID of the bucket that will hold the link + + --location=LOCATION + Location of the bucket that will hold the link. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A textual description for the link. + + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the link to create. + + --folder=FOLDER_ID + Folder of the link to create. + + --organization=ORGANIZATION_ID + Organization of the link to create. + + --project=PROJECT_ID + Project of the link to create. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud logging links create + + $ gcloud beta logging links create + diff --git a/gcloud/alpha/logging/links/delete b/gcloud/alpha/logging/links/delete new file mode 100644 index 000000000..083acbd1a --- /dev/null +++ b/gcloud/alpha/logging/links/delete @@ -0,0 +1,78 @@ +NAME + gcloud alpha logging links delete - delete a link + +SYNOPSIS + gcloud alpha logging links delete LINK_ID --bucket=BUCKET + --location=LOCATION [--async] + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes a bucket's link. + +EXAMPLES + To delete a bucket's link, run: + + $ gcloud alpha logging links delete my-link --bucket=my-bucket \ + --location=global + +POSITIONAL ARGUMENTS + LINK_ID + ID of the link to delete. + +REQUIRED FLAGS + --bucket=BUCKET + ID of bucket + + --location=LOCATION + Location of the bucket. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the link to delete. + + --folder=FOLDER_ID + Folder of the link to delete. + + --organization=ORGANIZATION_ID + Organization of the link to delete. + + --project=PROJECT_ID + Project of the link to delete. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud logging links delete + + $ gcloud beta logging links delete + diff --git a/gcloud/alpha/logging/links/describe b/gcloud/alpha/logging/links/describe new file mode 100644 index 000000000..0b6d3e763 --- /dev/null +++ b/gcloud/alpha/logging/links/describe @@ -0,0 +1,74 @@ +NAME + gcloud alpha logging links describe - display information about a link + +SYNOPSIS + gcloud alpha logging links describe LINK_ID --bucket=BUCKET + --location=LOCATION + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Displays information about a link. + +EXAMPLES + To describe a link in a project, run: + + $ gcloud alpha logging links describe my-link --bucket=my-bucket \ + --location=global + +POSITIONAL ARGUMENTS + LINK_ID + Id of the link to describe. + +REQUIRED FLAGS + --bucket=BUCKET + ID of bucket + + --location=LOCATION + Location of the bucket. + +OPTIONAL FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the link to describe. + + --folder=FOLDER_ID + Folder of the link to describe. + + --organization=ORGANIZATION_ID + Organization of the link to describe. + + --project=PROJECT_ID + Project of the link to describe. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud logging links describe + + $ gcloud beta logging links describe + diff --git a/gcloud/alpha/logging/links/help b/gcloud/alpha/logging/links/help new file mode 100644 index 000000000..a29da536c --- /dev/null +++ b/gcloud/alpha/logging/links/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha logging links - manage log links + +SYNOPSIS + gcloud alpha logging links COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Commands for managing links. A log link represents a linked + BigQuery dataset that contains log data for the link's parent log bucket. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a link on an analytics log bucket. + + delete + (ALPHA) Delete a link. + + describe + (ALPHA) Display information about a link. + + list + (ALPHA) List created links on the specified bucket. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud logging links + + $ gcloud beta logging links + diff --git a/gcloud/alpha/logging/links/list b/gcloud/alpha/logging/links/list new file mode 100644 index 000000000..9c08fe956 --- /dev/null +++ b/gcloud/alpha/logging/links/list @@ -0,0 +1,102 @@ +NAME + gcloud alpha logging links list - list created links on the specified + bucket + +SYNOPSIS + gcloud alpha logging links list --bucket=BUCKET --location=LOCATION + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists the links created for a bucket. + +EXAMPLES + To list the links created for a bucket, run: + + $ gcloud alpha logging links list + +REQUIRED FLAGS + --bucket=BUCKET + ID of bucket + + --location=LOCATION + Location of the specified bucket + +FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the links to list. + + --folder=FOLDER_ID + Folder of the links to list. + + --organization=ORGANIZATION_ID + Organization of the links to list. + + --project=PROJECT_ID + Project of the links to list. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud logging links list + + $ gcloud beta logging links list + diff --git a/gcloud/alpha/ml-engine/jobs/submit/training b/gcloud/alpha/ml-engine/jobs/submit/training index 2b8aea490..82223575b 100644 --- a/gcloud/alpha/ml-engine/jobs/submit/training +++ b/gcloud/alpha/ml-engine/jobs/submit/training @@ -149,7 +149,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. @@ -200,7 +200,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. @@ -322,7 +322,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. diff --git a/gcloud/alpha/recaptcha/keys/create b/gcloud/alpha/recaptcha/keys/create index a5cbd3d90..08efc1add 100644 --- a/gcloud/alpha/recaptcha/keys/create +++ b/gcloud/alpha/recaptcha/keys/create @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud alpha recaptcha keys create --display-name=DISPLAY_NAME - (--android (--allow-all-package-names + ([--android (--allow-all-package-names | --package-names=[PACKAGE_NAMES,...]) + : --support-non-google-app-store-distribution] | --ios (--allow-all-bundle-ids | --bundle-ids=[BUNDLE_IDS,...]) | [--web (--allow-all-domains | --domains=[DOMAINS,...]) : --allow-amp-traffic --integration-type=INTEGRATION_TYPE @@ -38,6 +39,14 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --support-non-google-app-store-distribution + If set, this key can be used in an Android application that is + available for download in app stores other than the Google Play + Store. + + This setting allows your key to accept traffic from devices without + Google Mobility Services (GMS) installed. + Exactly one of these must be specified: --allow-all-package-names diff --git a/gcloud/alpha/services/api-keys/update b/gcloud/alpha/services/api-keys/update index 8dd12182c..6516a6919 100644 --- a/gcloud/alpha/services/api-keys/update +++ b/gcloud/alpha/services/api-keys/update @@ -2,10 +2,10 @@ NAME gcloud alpha services api-keys update - update an API key's metadata SYNOPSIS - gcloud alpha services api-keys update (KEY : --location=LOCATION) - [--annotations=[KEY=VALUE,...]] [--async] [--display-name=DISPLAY_NAME] - [--clear-annotations | --clear-restrictions - | --api-target=service=SERVICE,[...] + gcloud alpha services api-keys update (KEY : --location=LOCATION) [--async] + [--display-name=DISPLAY_NAME] + [--annotations=[KEY=VALUE,...] | --clear-annotations] + [--clear-restrictions | --api-target=service=SERVICE,[...] --allowed-application=[sha1_fingerprint=SHA1_FINGERPRINT, package_name=PACKAGE_NAME,...] | --allowed-bundle-ids=[ALLOWED_BUNDLE_IDS,...] @@ -103,10 +103,6 @@ POSITIONAL ARGUMENTS ▸ location will default to global. FLAGS - --annotations=[KEY=VALUE,...] - Annotations are key resource. Specify annotations as a key-value - dictionary for small amounts of arbitrary client data. - --async Return immediately, without waiting for the operation in progress to complete. @@ -116,9 +112,15 @@ FLAGS At most one of these can be specified: + --annotations=[KEY=VALUE,...] + Annotations are key resource. Specify annotations as a key-value + dictionary for small amounts of arbitrary client data. + --clear-annotations If set, clear all annotations on the key. + At most one of these can be specified: + --clear-restrictions If set, clear all restrictions on the key. diff --git a/gcloud/alpha/storage/mv b/gcloud/alpha/storage/mv index 0e7c5d3e1..7a7b61934 100644 --- a/gcloud/alpha/storage/mv +++ b/gcloud/alpha/storage/mv @@ -42,7 +42,7 @@ DESCRIPTION under gs://my_bucket/oldprefix to be under gs://my_bucket/newprefix, otherwise preserving the naming structure: - $ gcloud alpha storage mv mv gs://my_bucket/oldprefix \ + $ gcloud alpha storage mv gs://my_bucket/oldprefix \ gs://my_bucket/newprefix Note that when using mv to rename groups of objects with a common prefix, diff --git a/gcloud/auth/application-default/login b/gcloud/auth/application-default/login index f9ba7f887..ef5c75c95 100644 --- a/gcloud/auth/application-default/login +++ b/gcloud/auth/application-default/login @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud auth application-default login [--no-browser] [--client-id-file=CLIENT_ID_FILE] [--disable-quota-project] - [--no-launch-browser] [--scopes=SCOPE,[SCOPE,...]] - [GCLOUD_WIDE_FLAG ...] + [--no-launch-browser] [--login-config=LOGIN_CONFIG] + [--scopes=SCOPE,[SCOPE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Obtains user access credentials via a web flow and puts them in the @@ -123,6 +123,12 @@ FLAGS Enabled by default, use --no-launch-browser to disable. + --login-config=LOGIN_CONFIG + Path to the login configuration file (workforce pool, generated by the + Cloud Console or gcloud iam workforce-pools create-login-config). + Overrides the default auth/login_config_file property value for this + command invocation. + --scopes=SCOPE,[SCOPE,...] The names of the scopes to authorize for. By default openid, https://www.googleapis.com/auth/userinfo.email, diff --git a/gcloud/auth/login b/gcloud/auth/login index d665a31d8..effe1d6e3 100644 --- a/gcloud/auth/login +++ b/gcloud/auth/login @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud auth login [ACCOUNT] [--no-activate] [--brief] [--no-browser] [--cred-file=CRED_FILE] [--enable-gdrive-access] [--force] - [--no-launch-browser] [--update-adc] [GCLOUD_WIDE_FLAG ...] + [--no-launch-browser] [--login-config=LOGIN_CONFIG] [--update-adc] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Obtains access credentials for your user account via a web-based @@ -122,6 +123,12 @@ FLAGS Enabled by default, use --no-launch-browser to disable. + --login-config=LOGIN_CONFIG + Path to the login configuration file (workforce pool, generated by the + Cloud Console or gcloud iam workforce-pools create-login-config). + Overrides the default auth/login_config_file property value for this + command invocation. + --update-adc Write the obtained credentials to the well-known location for Application Default Credentials (ADC). Run $ gcloud auth diff --git a/gcloud/beta/ai-platform/jobs/submit/training b/gcloud/beta/ai-platform/jobs/submit/training index 64f1f0a2a..7c09018f6 100644 --- a/gcloud/beta/ai-platform/jobs/submit/training +++ b/gcloud/beta/ai-platform/jobs/submit/training @@ -149,7 +149,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. @@ -200,7 +200,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. @@ -322,7 +322,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. diff --git a/gcloud/beta/auth/application-default/login b/gcloud/beta/auth/application-default/login index a118859c4..4fa62263a 100644 --- a/gcloud/beta/auth/application-default/login +++ b/gcloud/beta/auth/application-default/login @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud beta auth application-default login [--no-browser] [--client-id-file=CLIENT_ID_FILE] [--disable-quota-project] - [--no-launch-browser] [--scopes=SCOPE,[SCOPE,...]] - [GCLOUD_WIDE_FLAG ...] + [--no-launch-browser] [--login-config=LOGIN_CONFIG] + [--scopes=SCOPE,[SCOPE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Obtains user access credentials via a web flow and puts them in the @@ -123,6 +123,12 @@ FLAGS Enabled by default, use --no-launch-browser to disable. + --login-config=LOGIN_CONFIG + Path to the login configuration file (workforce pool, generated by the + Cloud Console or gcloud iam workforce-pools create-login-config). + Overrides the default auth/login_config_file property value for this + command invocation. + --scopes=SCOPE,[SCOPE,...] The names of the scopes to authorize for. By default openid, https://www.googleapis.com/auth/userinfo.email, diff --git a/gcloud/beta/auth/login b/gcloud/beta/auth/login index b6eea1907..49b4aafbb 100644 --- a/gcloud/beta/auth/login +++ b/gcloud/beta/auth/login @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta auth login [ACCOUNT] [--no-activate] [--brief] [--no-browser] [--cred-file=CRED_FILE] [--enable-gdrive-access] [--force] - [--no-launch-browser] [--update-adc] [GCLOUD_WIDE_FLAG ...] + [--no-launch-browser] [--login-config=LOGIN_CONFIG] [--update-adc] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Obtains access credentials for your user account via a web-based @@ -123,6 +124,12 @@ FLAGS Enabled by default, use --no-launch-browser to disable. + --login-config=LOGIN_CONFIG + Path to the login configuration file (workforce pool, generated by the + Cloud Console or gcloud iam workforce-pools create-login-config). + Overrides the default auth/login_config_file property value for this + command invocation. + --update-adc Write the obtained credentials to the well-known location for Application Default Credentials (ADC). Run $ gcloud auth diff --git a/gcloud/beta/builds/triggers/create/bitbucketserver b/gcloud/beta/builds/triggers/create/bitbucketserver index ae8a02d0e..f6251968a 100644 --- a/gcloud/beta/builds/triggers/create/bitbucketserver +++ b/gcloud/beta/builds/triggers/create/bitbucketserver @@ -128,9 +128,10 @@ REQUIRED FLAGS --branch-pattern=REGEX A regular expression specifying which git branches to match. - This pattern is used as a regex search for any incoming pushes. - For example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at @@ -139,9 +140,10 @@ REQUIRED FLAGS --tag-pattern=REGEX A regular expression specifying which git tags to match. - This pattern is used as a regex search for any incoming pushes. - For example, --tag-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a tag that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at diff --git a/gcloud/beta/builds/triggers/create/cloud-source-repositories b/gcloud/beta/builds/triggers/create/cloud-source-repositories index 768499208..729fd1a3c 100644 --- a/gcloud/beta/builds/triggers/create/cloud-source-repositories +++ b/gcloud/beta/builds/triggers/create/cloud-source-repositories @@ -107,9 +107,10 @@ REQUIRED FLAGS --branch-pattern=REGEX A regular expression specifying which git branches to match. - This pattern is used as a regex search for any incoming pushes. - For example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at @@ -118,9 +119,10 @@ REQUIRED FLAGS --tag-pattern=REGEX A regular expression specifying which git tags to match. - This pattern is used as a regex search for any incoming pushes. - For example, --tag-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a tag that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at diff --git a/gcloud/beta/builds/triggers/create/github b/gcloud/beta/builds/triggers/create/github index 45326b860..b7fae51ac 100644 --- a/gcloud/beta/builds/triggers/create/github +++ b/gcloud/beta/builds/triggers/create/github @@ -119,9 +119,10 @@ REQUIRED FLAGS --branch-pattern=REGEX A regular expression specifying which git branches to match. - This pattern is used as a regex search for any incoming pushes. - For example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at @@ -130,9 +131,10 @@ REQUIRED FLAGS --tag-pattern=REGEX A regular expression specifying which git tags to match. - This pattern is used as a regex search for any incoming pushes. - For example, --tag-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a tag that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at diff --git a/gcloud/beta/builds/triggers/create/gitlab-enterprise b/gcloud/beta/builds/triggers/create/gitlab-enterprise index 694b8c806..1c72a9750 100644 --- a/gcloud/beta/builds/triggers/create/gitlab-enterprise +++ b/gcloud/beta/builds/triggers/create/gitlab-enterprise @@ -109,9 +109,10 @@ REQUIRED FLAGS --branch-pattern=REGEX A regular expression specifying which git branches to match. - This pattern is used as a regex search for any incoming pushes. - For example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at @@ -120,9 +121,10 @@ REQUIRED FLAGS --tag-pattern=REGEX A regular expression specifying which git tags to match. - This pattern is used as a regex search for any incoming pushes. - For example, --tag-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a tag that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at diff --git a/gcloud/beta/compute/disks/create b/gcloud/beta/compute/disks/create index 2bdd06b56..3deccbb68 100644 --- a/gcloud/beta/compute/disks/create +++ b/gcloud/beta/compute/disks/create @@ -113,9 +113,8 @@ FLAGS 16384. --provisioned-iops=PROVISIONED_IOPS - Provisioned IOPS of pd-extreme disk to create. Only for use with disks - of type pd-extreme. If specified, the value must be in the range - between 2500 and 120000. If not specified, the default value is 100000. + Provisioned IOPS of disk to create. Only for use with disks of type + pd-extreme and hyperdisk-extreme. --replica-zones=ZONE,ZONE A comma-separated list of exactly 2 zones that a regional disk will be diff --git a/gcloud/beta/compute/disks/update b/gcloud/beta/compute/disks/update index a9031ef13..98c6cb497 100644 --- a/gcloud/beta/compute/disks/update +++ b/gcloud/beta/compute/disks/update @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud beta compute disks update DISK_NAME - [--update-labels=[KEY=VALUE,...]] + [--provisioned-iops=PROVISIONED_IOPS] [--update-labels=[KEY=VALUE,...]] [--clear-architecture | --update-architecture=UPDATE_ARCHITECTURE] [--clear-labels | --remove-labels=[KEY,...]] [--clear-user-licenses | --update-user-licenses=[LICENSE,...]] @@ -38,6 +38,10 @@ POSITIONAL ARGUMENTS Name of the disk to update. FLAGS + --provisioned-iops=PROVISIONED_IOPS + Provisioned IOPS of disk to update. Only for use with disks of type + hyperdisk-extreme. + --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index f09f05bc9..48e6cb608 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -36,7 +36,7 @@ SYNOPSIS [--resource-policies=[RESOURCE_POLICY,...]] [--no-restart-on-failure] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--source-instance-template=SOURCE_INSTANCE_TEMPLATE] - [--subnet=SUBNET] [--tags=TAG,[TAG,...]] + [--stack-type=STACK_TYPE] [--subnet=SUBNET] [--tags=TAG,[TAG,...]] [--target-distribution-shape=SHAPE] [--termination-time=TERMINATION_TIME] [--threads-per-core=THREADS_PER_CORE] @@ -657,6 +657,15 @@ OPTIONAL FLAGS The name of the instance template that the instance will be created from. Users can override fields by specifying other flags. + --stack-type=STACK_TYPE + Specifies whether IPv6 is enabled on the default network interface. If + not specified, IPV4_ONLY will be used. 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 + --subnet=SUBNET Specifies the subnet that the VM instances are a part of. If --network is also specified, subnet must be a subnetwork of the network specified diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 97253c5d7..32f95993b 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -94,20 +94,20 @@ EXAMPLES example-instance-2 example-instance-3 --zone=us-central1-a To create an instance called 'instance-1' from a source snapshot called - 'instance-snapshot' in zone 'us-central2-a' and attached regional disk + 'instance-snapshot' in zone 'us-central1-a' and attached regional disk 'disk-1', run: $ gcloud beta compute instances create instance-1 \ --source-snapshot=https://compute.googleapis.com/compute/v1/\ projects/myproject/global/snapshots/instance-snapshot \ - --zone=central2-a --disk=name=disk1,scope=regional + --zone=us-central1-a --disk=name=disk1,scope=regional To create an instance called instance-1 as a Shielded VM instance with Secure Boot, virtual trusted platform module (vTPM) enabled and integrity monitoring, run: $ gcloud beta compute instances create instance-1 \ - --zone=central2-a --shielded-secure-boot --shielded-vtpm \ + --zone=us-central1-a --shielded-secure-boot --shielded-vtpm \ --shielded-integrity-monitoring To create a preemptible instance called 'instance-1', run: @@ -632,6 +632,13 @@ FLAGS Specifies the Network Interface Controller (NIC) type for the interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + queue-count + Specifies the networking queue count for this interface. Both Rx + and Tx queues will be set to this number. If it's not specified, a + default queue count will be assigned. For Virtio-net, each + interface will get min(floor(#vCPU / #vNIC), 32) queues. For gVNIC, + each interface will get min(floor(#vCPU / #vNIC / 2), 16) qeueus. + stack-type Specifies whether IPv6 is enabled on the interface. STACK_TYPE must be one of: IPV4_ONLY, IPV4_IPV6. The default value is IPV4_ONLY. diff --git a/gcloud/beta/compute/routers/add-bgp-peer b/gcloud/beta/compute/routers/add-bgp-peer index ed5b8f043..c1ac1d325 100644 --- a/gcloud/beta/compute/routers/add-bgp-peer +++ b/gcloud/beta/compute/routers/add-bgp-peer @@ -144,7 +144,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --set-advertisement-ranges=[CIDR_RANGE=DESC,...] The list of individual IP ranges, in CIDR format, to dynamically diff --git a/gcloud/beta/compute/routers/create b/gcloud/beta/compute/routers/create index 348eb16b3..c4c54ec2b 100644 --- a/gcloud/beta/compute/routers/create +++ b/gcloud/beta/compute/routers/create @@ -88,7 +88,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --set-advertisement-ranges=[CIDR_RANGE=DESC,...] The list of individual IP ranges, in CIDR format, to dynamically diff --git a/gcloud/beta/compute/routers/update b/gcloud/beta/compute/routers/update index 844df6156..1bd45fae1 100644 --- a/gcloud/beta/compute/routers/update +++ b/gcloud/beta/compute/routers/update @@ -84,7 +84,8 @@ FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --set-advertisement-ranges=[CIDR_RANGE=DESC,...] The list of individual IP ranges, in CIDR format, to dynamically @@ -104,7 +105,8 @@ FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --add-advertisement-ranges=[CIDR_RANGE=DESC,...] A list of individual IP ranges, in CIDR format, to dynamically @@ -124,7 +126,8 @@ FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --remove-advertisement-ranges=[CIDR_RANGE,...] A list of individual IP ranges, in CIDR format, to remove from diff --git a/gcloud/beta/compute/routers/update-bgp-peer b/gcloud/beta/compute/routers/update-bgp-peer index 8464a76dc..0877862c5 100644 --- a/gcloud/beta/compute/routers/update-bgp-peer +++ b/gcloud/beta/compute/routers/update-bgp-peer @@ -130,7 +130,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --set-advertisement-ranges=[CIDR_RANGE=DESC,...] The list of individual IP ranges, in CIDR format, to dynamically @@ -150,7 +151,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --add-advertisement-ranges=[CIDR_RANGE=DESC,...] A list of individual IP ranges, in CIDR format, to dynamically @@ -170,7 +172,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --remove-advertisement-ranges=[CIDR_RANGE,...] A list of individual IP ranges, in CIDR format, to remove from diff --git a/gcloud/beta/compute/tpus/locations/describe b/gcloud/beta/compute/tpus/locations/describe index 574f5028d..2a293c686 100644 --- a/gcloud/beta/compute/tpus/locations/describe +++ b/gcloud/beta/compute/tpus/locations/describe @@ -14,7 +14,7 @@ DESCRIPTION EXAMPLES The following command describes the TPUs running in zone us-central1-b: - $ gcloud beta compute tpus locations describe zone=us-central1-b + $ gcloud beta compute tpus locations describe us-central1-b POSITIONAL ARGUMENTS Location resource - The Cloud TPU Location you want to describe. This diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index 5fbf0f035..4d60e9ff1 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -648,6 +648,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index ff743a901..6ba02e885 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -680,6 +680,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 0742e619f..d04fa608a 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -692,6 +692,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 9fa02bda1..2a253c3bb 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -695,6 +695,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 416973e88..d74b04068 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -656,6 +656,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/beta/container/fleet/help b/gcloud/beta/container/fleet/help index aa6af210a..1c53e7bc8 100644 --- a/gcloud/beta/container/fleet/help +++ b/gcloud/beta/container/fleet/help @@ -70,6 +70,13 @@ GROUPS multi-cluster-services (BETA) Manage Multi-cluster Services Feature. + namespaces + (BETA) Fleet namespaces are the fleet equivalent of k8s cluster + namespaces. + + scopes + (BETA) Manage scopes of all your GKE fleets. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/container/fleet/memberships/bindings/create b/gcloud/beta/container/fleet/memberships/bindings/create new file mode 100644 index 000000000..fef85649b --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/bindings/create @@ -0,0 +1,104 @@ +NAME + gcloud beta container fleet memberships bindings create - create a + Membership Binding + +SYNOPSIS + gcloud beta container fleet memberships bindings create + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The Membership Binding already exists. + ▪ The caller does not have permission to access the given Membership. + ▪ The Scope or the Membership does not exist. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To create a membership binding BINDING_NAME in global membership + MEMBERSHIP_NAME for scope SCOPE_NAME, run: + + $ gcloud beta container fleet memberships bindings create \ + BINDING_NAME --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME + + To create a Binding BINDING_NAME associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with membership name and associated Scope + SCOPE_NAME. + + $ gcloud beta container fleet memberships bindings create \ + BINDING_NAME --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --fleet=FLEET + Membership Binding is created for all the Scopes in the Fleet for + given Membership. + + Scope resource - The group of arguments defining the Fleet Scope. 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 --scope 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 --scope on the command line with a fully + specified name; + ▸ global is the only supported location. + + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▫ provide the argument --scope on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet memberships bindings create + diff --git a/gcloud/beta/container/fleet/memberships/bindings/delete b/gcloud/beta/container/fleet/memberships/bindings/delete new file mode 100644 index 000000000..02e909fa5 --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/bindings/delete @@ -0,0 +1,79 @@ +NAME + gcloud beta container fleet memberships bindings delete - delete a + Membership Binding + +SYNOPSIS + gcloud beta container fleet memberships bindings delete + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The Membership Binding specified does not exist. + ▪ The caller does not have permission to access the given Membership. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To delete Membership Binding BINDING_NAME in global Membership + MEMBERSHIP_NAME for a global membership: + + $ gcloud beta container fleet memberships bindings delete \ + BINDING_NAME --membership=MEMBERSHIP_NAME + + To delete a Binding BINDING_NAME associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with the membership name. + + $ gcloud beta container fleet memberships bindings delete \ + BINDING_NAME --membership=MEMBERSHIP_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet memberships bindings delete + diff --git a/gcloud/beta/container/fleet/memberships/bindings/describe b/gcloud/beta/container/fleet/memberships/bindings/describe new file mode 100644 index 000000000..6c9272e0e --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/bindings/describe @@ -0,0 +1,79 @@ +NAME + gcloud beta container fleet memberships bindings describe - show + Membership-Binding info + +SYNOPSIS + gcloud beta container fleet memberships bindings describe + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The Membership Binding specified does not exist in the project. + ▪ The caller does not have permission to access the Membership Binding. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To print metadata for the membership Binding BINDING_NAME in a global + membership MEMBERSHIP_NAME, run: + + $ gcloud beta container fleet memberships bindings describe \ + BINDING_NAME --membership=MEMBERSHIP_NAME + + To print metadata for the Binding BINDING_NAME associated with regional + membership MEMBERSHIP_NAME, provide the location LOCATION_NAME for the + Membership where the Binding belongs along with membership name. + + $ gcloud beta container fleet memberships bindings describe \ + BINDING_NAME --membership=MEMBERSHIP_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet memberships bindings describe + diff --git a/gcloud/beta/container/fleet/memberships/bindings/help b/gcloud/beta/container/fleet/memberships/bindings/help new file mode 100644 index 000000000..d84d8fa6b --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/bindings/help @@ -0,0 +1,46 @@ +NAME + gcloud beta container fleet memberships bindings - membership Bindings for + permissions + +SYNOPSIS + gcloud beta container fleet memberships bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command group allows for manipulation of bindings associated + with membership-scope. + +EXAMPLES + Manage Bindings: + + $ gcloud beta container fleet memberships bindings --help + +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 Membership Binding. + + delete + (BETA) Delete a Membership Binding. + + describe + (BETA) Show Membership-Binding info. + + list + (BETA) List Bindings in a Membership. + + update + (BETA) Update the Binding in a Membership. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet memberships bindings + diff --git a/gcloud/beta/container/fleet/memberships/bindings/list b/gcloud/beta/container/fleet/memberships/bindings/list new file mode 100644 index 000000000..2008865fd --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/bindings/list @@ -0,0 +1,85 @@ +NAME + gcloud beta container fleet memberships bindings list - list Bindings in a + Membership + +SYNOPSIS + gcloud beta container fleet memberships bindings list + --membership=MEMBERSHIP [--location=LOCATION; default="global"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The user does not have access to the Membership specified. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + The following command lists Bindings in global Membership MEMBERSHIP_NAME: + + $ gcloud beta container fleet memberships bindings list \ + --membership=MEMBERSHIP_NAME + + To list all the bindings associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with membership name. + + $ gcloud beta container fleet memberships bindings list \ + BINDING_NAME --membership=MEMBERSHIP_NAME \ + --location=LOCATION_NAME + +REQUIRED FLAGS + --membership=MEMBERSHIP + Name of the Membership to list Bindings from. + +FLAGS + --location=LOCATION; default="global" + Name of the Membership location to list Bindings from. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet memberships bindings list + diff --git a/gcloud/beta/container/fleet/memberships/bindings/update b/gcloud/beta/container/fleet/memberships/bindings/update new file mode 100644 index 000000000..281e1e04a --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/bindings/update @@ -0,0 +1,91 @@ +NAME + gcloud beta container fleet memberships bindings update - update the + Binding in a Membership + +SYNOPSIS + gcloud beta container fleet memberships bindings update + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The Binding does not exist in the Membership. + ▪ The caller does not have permission to access the Membership/Binding. + ▪ The Scope specified does not exist. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To update the binding BINDING_NAME in global membership MEMBERSHIP_NAME in + the active project: + + $ gcloud beta container fleet memberships bindings update \ + BINDING_NAME --membership=MEMBERSHIP_NAME + + To update a Binding BINDING_NAME associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with membership name and associated Scope + SCOPE_NAME. + + $ gcloud beta container fleet memberships bindings update \ + BINDING_NAME --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --fleet=FLEET + Bindings for all the membership related scopes in the fleet would be + updated. + + --scope=SCOPE + Scope related to the Binding. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet memberships bindings update + diff --git a/gcloud/beta/container/fleet/memberships/help b/gcloud/beta/container/fleet/memberships/help index ed05c7572..bd6036197 100644 --- a/gcloud/beta/container/fleet/memberships/help +++ b/gcloud/beta/container/fleet/memberships/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + bindings + (BETA) Membership Bindings for permissions. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/beta/container/fleet/namespaces/create b/gcloud/beta/container/fleet/namespaces/create new file mode 100644 index 000000000..2e16cf6bd --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/create @@ -0,0 +1,61 @@ +NAME + gcloud beta container fleet namespaces create - create a fleet namespace + +SYNOPSIS + gcloud beta container fleet namespaces create NAME [--scope=SCOPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The project has a fleet namespace with the same name. + ▪ The caller does not have permission to access the given project. + +EXAMPLES + To create a fleet namespace with name NAMESPACE in the active project, run: + + $ gcloud beta container fleet namespaces create NAMESPACE + + To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with + name NAMESPACE, run: + + $ gcloud beta container fleet namespaces create NAMESPACE \ + --scope=SCOPE --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the fleet namespace to be created. Must comply with RFC 1123 + (up to 63 characters, alphanumeric and '-') + +FLAGS + Scope resource - The group of arguments defining the Fleet Scope. 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 --scope 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 --scope on the command line with a fully + specified name; + ◆ global is the only supported location. + + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument --scope on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces create + diff --git a/gcloud/beta/container/fleet/namespaces/delete b/gcloud/beta/container/fleet/namespaces/delete new file mode 100644 index 000000000..f4298cde0 --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/delete @@ -0,0 +1,41 @@ +NAME + gcloud beta container fleet namespaces delete - delete a fleet namespace + +SYNOPSIS + gcloud beta container fleet namespaces delete NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The namespace specified does not exist. + ▪ The caller does not have permission to access the given project or + namespace. + +EXAMPLES + To delete fleet namespace NAMESPACE in the active project: + + $ gcloud beta container fleet namespaces delete NAMESPACE + + To delete fleet namespace NAMESPACE in project PROJECT_ID: + + $ gcloud beta container fleet namespaces delete NAMESPACE \ + --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the fleet namespace to be deleted. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces delete + diff --git a/gcloud/beta/container/fleet/namespaces/describe b/gcloud/beta/container/fleet/namespaces/describe new file mode 100644 index 000000000..bff13d62c --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/describe @@ -0,0 +1,41 @@ +NAME + gcloud beta container fleet namespaces describe - show fleet namespace info + +SYNOPSIS + gcloud beta container fleet namespaces describe NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The namespace specified does not exist in the project. + ▪ The caller does not have permission to access the project or + namespace. + +EXAMPLES + To print metadata for the namespace NAMESPACE in the active project, run: + + $ gcloud beta container fleet namespaces describe NAMESPACE + + To print metadata for the namespace NAMESPACE in project PROJECT_ID, run: + + $ gcloud beta container fleet namespaces describe NAMESPACE \ + --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the fleet namespace to be described. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces describe + diff --git a/gcloud/beta/container/fleet/namespaces/get-credentials b/gcloud/beta/container/fleet/namespaces/get-credentials new file mode 100644 index 000000000..5c23d6740 --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/get-credentials @@ -0,0 +1,58 @@ +NAME + gcloud beta container fleet namespaces get-credentials - fetch credentials + for a membership with a particular namespace + +SYNOPSIS + gcloud beta container fleet namespaces get-credentials NAMESPACE + [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION] + [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using + namespace NAMESPACE in the config: + + $ gcloud beta container fleet namespaces get-credentials NAMESPACE \ + --membership=MEMBERSHIP --membership-location=global \ + --set-namespace-in-config=true + + Get the Connect Gateway kubeconfig for global membership MEMBERSHIP: + + $ gcloud beta container fleet namespaces get-credentials NAMESPACE \ + --membership=MEMBERSHIP --membership-location=global + +POSITIONAL ARGUMENTS + NAMESPACE + Name of the namespace for which to get access to memberships. + +FLAGS + --membership=MEMBERSHIP + Membership ID to get credentials from. If not provided, a prompt will + offer a list of memberships in the fleet. + + --membership-location=MEMBERSHIP_LOCATION + The location of the membership resource, e.g. us-central1. If not + specified, defaults to global. + + --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG + If true, the default namespace for the context in the generated + kubeconfig will be set to the Fleet namespace (i.e. the name given as + the positional argument in this command). + + Otherwise, no default namespace will be set, functioning the same as + gcloud container fleet memberships get-credentials. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces get-credentials + diff --git a/gcloud/beta/container/fleet/namespaces/help b/gcloud/beta/container/fleet/namespaces/help new file mode 100644 index 000000000..83ff7f125 --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/help @@ -0,0 +1,58 @@ +NAME + gcloud beta container fleet namespaces - fleet namespaces are the fleet + equivalent of k8s cluster namespaces + +SYNOPSIS + gcloud beta container fleet namespaces GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command group allows for manipulation of fleet namespaces. + +EXAMPLES + Manage fleet namespaces: + + $ gcloud beta container fleet namespaces --help + + Manage RBAC RoleBindings in a fleet namespace: + + $ gcloud beta container fleet namespaces rbacrolebindings --help + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + rbacrolebindings + (BETA) Fleet namespace RBAC RoleBindings for permissions. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a fleet namespace. + + delete + (BETA) Delete a fleet namespace. + + describe + (BETA) Show fleet namespace info. + + get-credentials + (BETA) Fetch credentials for a membership with a particular namespace. + + list + (BETA) List fleet namespaces in a project. + + update + (BETA) Update a fleet namespace. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces + diff --git a/gcloud/beta/container/fleet/namespaces/list b/gcloud/beta/container/fleet/namespaces/list new file mode 100644 index 000000000..8204e8f47 --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/list @@ -0,0 +1,69 @@ +NAME + gcloud beta container fleet namespaces list - list fleet namespaces in a + project + +SYNOPSIS + gcloud beta container fleet namespaces list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The user does not have access to the project specified. + +EXAMPLES + The following command lists namespaces in the active project: + + $ gcloud beta container fleet namespaces list + + The following command lists namespaces in project PROJECT_ID: + + $ gcloud beta container fleet namespaces list --project=PROJECT_ID + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces list + diff --git a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/create b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/create new file mode 100644 index 000000000..7febb3dec --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/create @@ -0,0 +1,88 @@ +NAME + gcloud beta container fleet namespaces rbacrolebindings create - create an + RBAC RoleBinding + +SYNOPSIS + gcloud beta container fleet namespaces rbacrolebindings create + (NAME : --location=LOCATION --namespace=NAMESPACE) --role=ROLE + (--group=GROUP | --user=USER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The RBAC RoleBinding already exists. + ▪ The caller does not have permission to access the given namespace. + +EXAMPLES + To create an admin RBAC RoleBinding RBRB in namespace NAMESPACE for user + person@google.com, run: + + $ gcloud beta container fleet namespaces rbacrolebindings create \ + RBRB --namespace=NAMESPACE --role=admin --user=person@google.com + + To create a viewer RBAC RoleBinding RBRB in namespace NAMESPACE for group + people@google.com, run: + + $ gcloud beta container fleet namespaces rbacrolebindings create \ + RBRB --namespace=NAMESPACE --role=viewer \ + --group=people@google.com + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +REQUIRED FLAGS + --role=ROLE + Role to assign. ROLE must be one of: admin, edit, view. + + Exactly one of these must be specified: + + --group=GROUP + Group for the RoleBinding. + + --user=USER + User for the RoleBinding. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces rbacrolebindings create + diff --git a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/delete b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/delete new file mode 100644 index 000000000..664331aea --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/delete @@ -0,0 +1,69 @@ +NAME + gcloud beta container fleet namespaces rbacrolebindings delete - delete a + fleet namespace RBAC RoleBinding + +SYNOPSIS + gcloud beta container fleet namespaces rbacrolebindings delete + (NAME : --location=LOCATION --namespace=NAMESPACE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The RoleBinding specified does not exist. + ▪ The caller does not have permission to access the given RoleBinding. + +EXAMPLES + To delete RBAC RoleBinding RBRB in namespace NAMESPACE in the active + project: + + $ gcloud beta container fleet namespaces rbacrolebindings delete \ + RBRB --namespace=NAMESPACE + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces rbacrolebindings delete + diff --git a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/describe b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/describe new file mode 100644 index 000000000..c8982b279 --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/describe @@ -0,0 +1,69 @@ +NAME + gcloud beta container fleet namespaces rbacrolebindings describe - show + fleet namespace RBAC RoleBinding information + +SYNOPSIS + gcloud beta container fleet namespaces rbacrolebindings describe + (NAME : --location=LOCATION --namespace=NAMESPACE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The RoleBinding specified does not exist in the project. + ▪ The caller does not have permission to access the RoleBinding. + +EXAMPLES + To print metadata for RBAC RoleBinding RBRB in the namespace NAMESPACE, + run: + + $ gcloud beta container fleet namespaces rbacrolebindings describe \ + RBRB --namespace=NAMESPACE + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces rbacrolebindings describe + diff --git a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/help b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/help new file mode 100644 index 000000000..1548af286 --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/help @@ -0,0 +1,46 @@ +NAME + gcloud beta container fleet namespaces rbacrolebindings - fleet namespace + RBAC RoleBindings for permissions + +SYNOPSIS + gcloud beta container fleet namespaces rbacrolebindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command group allows for manipulation of fleet namespace RBAC + RoleBindings. + +EXAMPLES + Manage RBAC RoleBindings: + + $ gcloud beta container fleet namespaces rbacrolebindings --help + +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 an RBAC RoleBinding. + + delete + (BETA) Delete a fleet namespace RBAC RoleBinding. + + describe + (BETA) Show fleet namespace RBAC RoleBinding information. + + list + (BETA) List RBAC RoleBindings in a fleet namespace. + + update + (BETA) Update a fleet namespace RBAC RoleBinding. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces rbacrolebindings + diff --git a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/list b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/list new file mode 100644 index 000000000..68142ebe8 --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/list @@ -0,0 +1,72 @@ +NAME + gcloud beta container fleet namespaces rbacrolebindings list - list RBAC + RoleBindings in a fleet namespace + +SYNOPSIS + gcloud beta container fleet namespaces rbacrolebindings list + --namespace=NAMESPACE [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The namespace specified does not exist. + ▪ The user does not have access to the specified namespace. + +EXAMPLES + The following command lists RBAC RoleBindings in namespace NAMESPACE in + project PROJECT_ID: + + $ gcloud beta container fleet namespaces rbacrolebindings list \ + --namespace=NAMESPACE --project=PROJECT_ID + +REQUIRED FLAGS + --namespace=NAMESPACE + Name of the fleet namespace to list RBAC RoleBindings from. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces rbacrolebindings list + diff --git a/gcloud/beta/container/fleet/namespaces/rbacrolebindings/update b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/update new file mode 100644 index 000000000..2a3dec8c0 --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/rbacrolebindings/update @@ -0,0 +1,88 @@ +NAME + gcloud beta container fleet namespaces rbacrolebindings update - update a + fleet namespace RBAC RoleBinding + +SYNOPSIS + gcloud beta container fleet namespaces rbacrolebindings update + (NAME : --location=LOCATION --namespace=NAMESPACE) [--role=ROLE] + [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The RoleBinding does not exist in the project. + ▪ The caller does not have permission to access the RoleBinding. + +EXAMPLES + To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active + project to the viewer role: + + $ gcloud beta container fleet namespaces rbacrolebindings update \ + RBRB --namespace=NAMESPACE --role=viewer + + To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active + project to the user someone@google.com: + + $ gcloud beta container fleet namespaces rbacrolebindings update \ + RBRB --namespace=NAMESPACE --user=someone@google.com + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +FLAGS + --role=ROLE + Role for the RBACRoleBinding to update to. ROLE must be one of: admin, + edit, view. + + At most one of these can be specified: + + --group=GROUP + Group for the RBACRoleBinding to update to. + + --user=USER + User for the RBACRoleBinding to update to. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces rbacrolebindings update + diff --git a/gcloud/beta/container/fleet/namespaces/update b/gcloud/beta/container/fleet/namespaces/update new file mode 100644 index 000000000..544931485 --- /dev/null +++ b/gcloud/beta/container/fleet/namespaces/update @@ -0,0 +1,60 @@ +NAME + gcloud beta container fleet namespaces update - update a fleet namespace + +SYNOPSIS + gcloud beta container fleet namespaces update NAME [--scope=SCOPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The fleet namespace does not exist in the project. + ▪ The caller does not have permission to access the project or + namespace. + +EXAMPLES + To update the namespace NAMESPACE in the active project: + + $ gcloud beta container fleet namespaces update NAMESPACE + + To update the namespace NAMESPACE in project PROJECT_ID: + + $ gcloud beta container fleet namespaces update NAMESPACE \ + --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the namespace to be updated. + +FLAGS + Scope resource - The group of arguments defining the Fleet Scope. 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 --scope 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 --scope on the command line with a fully + specified name; + ◆ global is the only supported location. + + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument --scope on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet namespaces update + diff --git a/gcloud/beta/container/fleet/scopes/create b/gcloud/beta/container/fleet/scopes/create new file mode 100644 index 000000000..4e74a4b07 --- /dev/null +++ b/gcloud/beta/container/fleet/scopes/create @@ -0,0 +1,59 @@ +NAME + gcloud beta container fleet scopes create - create a new fleet scope + +SYNOPSIS + gcloud beta container fleet scopes create SCOPE [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Fleet Scope resource. + +EXAMPLES + Create a new scope SCOPE_NAME in the active project's fleet: + + $ gcloud beta container fleet scopes create SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - The fleet scope resourse to be created. 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 scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. To set the + location attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ global is the only supported location. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument scope 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 gkehub/v1beta API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet scopes create + diff --git a/gcloud/beta/container/fleet/scopes/delete b/gcloud/beta/container/fleet/scopes/delete new file mode 100644 index 000000000..dcbb86aae --- /dev/null +++ b/gcloud/beta/container/fleet/scopes/delete @@ -0,0 +1,72 @@ +NAME + gcloud beta container fleet scopes delete - delete a fleet scope + +SYNOPSIS + gcloud beta container fleet scopes delete (SCOPE : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command deletes a Fleet Scope resource . + +EXAMPLES + First retrieve the ID of the scope using the command below. The output of + this command lists all the fleet's scopes, with their unique IDs in the + Names column: + + $ gcloud beta container fleet scopes list + + Delete a scope from the active project's fleet: + + $ gcloud beta container fleet scopes delete SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - The fleet scope to delete. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument scope 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 name. To set the location attribute: + ▸ provide the argument scope on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +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 gkehub/v1beta API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet scopes delete + diff --git a/gcloud/beta/container/fleet/scopes/describe b/gcloud/beta/container/fleet/scopes/describe new file mode 100644 index 000000000..e532728fc --- /dev/null +++ b/gcloud/beta/container/fleet/scopes/describe @@ -0,0 +1,67 @@ +NAME + gcloud beta container fleet scopes describe - describe a fleet scope + +SYNOPSIS + gcloud beta container fleet scopes describe (SCOPE : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Fleet Scope. + +EXAMPLES + First retrieve the ID of the scope using the command below. The output of + this command lists all the fleet's members, with their unique IDs in the + Names column: + + $ gcloud beta container fleet scopes list + + Then describe it: + + $ gcloud beta container fleet scopes describe SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - The scope to describe. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. To set + the project attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument scope 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 name. To set the location attribute: + ▸ provide the argument scope on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkehub/v1beta API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet scopes describe + diff --git a/gcloud/beta/container/fleet/scopes/help b/gcloud/beta/container/fleet/scopes/help new file mode 100644 index 000000000..c0b4a3433 --- /dev/null +++ b/gcloud/beta/container/fleet/scopes/help @@ -0,0 +1,35 @@ +NAME + gcloud beta container fleet scopes - manage scopes of all your GKE fleets + +SYNOPSIS + gcloud beta container fleet scopes COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage scopes of all your GKE fleets. + +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 new fleet scope. + + delete + (BETA) Delete a fleet scope. + + describe + (BETA) Describe a fleet scope. + + list + (BETA) List fleet scopes. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet scopes + diff --git a/gcloud/beta/container/fleet/scopes/list b/gcloud/beta/container/fleet/scopes/list new file mode 100644 index 000000000..4496b4ae9 --- /dev/null +++ b/gcloud/beta/container/fleet/scopes/list @@ -0,0 +1,67 @@ +NAME + gcloud beta container fleet scopes list - list fleet scopes + +SYNOPSIS + gcloud beta container fleet scopes list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List scopes in a fleet. + +EXAMPLES + List scopes in the active project's fleet: + + $ gcloud beta container fleet scopes list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkehub/v1beta API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet scopes list + diff --git a/gcloud/beta/container/hub/help b/gcloud/beta/container/hub/help index 9fed0cc50..6523718f9 100644 --- a/gcloud/beta/container/hub/help +++ b/gcloud/beta/container/hub/help @@ -70,6 +70,13 @@ GROUPS multi-cluster-services (BETA) Manage Multi-cluster Services Feature. + namespaces + (BETA) Fleet namespaces are the fleet equivalent of k8s cluster + namespaces. + + scopes + (BETA) Manage scopes of all your GKE fleets. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/container/hub/memberships/bindings/create b/gcloud/beta/container/hub/memberships/bindings/create new file mode 100644 index 000000000..418948aea --- /dev/null +++ b/gcloud/beta/container/hub/memberships/bindings/create @@ -0,0 +1,104 @@ +NAME + gcloud beta container hub memberships bindings create - create a Membership + Binding + +SYNOPSIS + gcloud beta container hub memberships bindings create + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The Membership Binding already exists. + ▪ The caller does not have permission to access the given Membership. + ▪ The Scope or the Membership does not exist. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To create a membership binding BINDING_NAME in global membership + MEMBERSHIP_NAME for scope SCOPE_NAME, run: + + $ gcloud beta container hub memberships bindings create \ + BINDING_NAME --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME + + To create a Binding BINDING_NAME associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with membership name and associated Scope + SCOPE_NAME. + + $ gcloud beta container hub memberships bindings create \ + BINDING_NAME --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --fleet=FLEET + Membership Binding is created for all the Scopes in the Fleet for + given Membership. + + Scope resource - The group of arguments defining the Fleet Scope. 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 --scope 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 --scope on the command line with a fully + specified name; + ▸ global is the only supported location. + + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▫ provide the argument --scope on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub memberships bindings create + diff --git a/gcloud/beta/container/hub/memberships/bindings/delete b/gcloud/beta/container/hub/memberships/bindings/delete new file mode 100644 index 000000000..56ddece0a --- /dev/null +++ b/gcloud/beta/container/hub/memberships/bindings/delete @@ -0,0 +1,79 @@ +NAME + gcloud beta container hub memberships bindings delete - delete a Membership + Binding + +SYNOPSIS + gcloud beta container hub memberships bindings delete + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The Membership Binding specified does not exist. + ▪ The caller does not have permission to access the given Membership. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To delete Membership Binding BINDING_NAME in global Membership + MEMBERSHIP_NAME for a global membership: + + $ gcloud beta container hub memberships bindings delete \ + BINDING_NAME --membership=MEMBERSHIP_NAME + + To delete a Binding BINDING_NAME associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with the membership name. + + $ gcloud beta container hub memberships bindings delete \ + BINDING_NAME --membership=MEMBERSHIP_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub memberships bindings delete + diff --git a/gcloud/beta/container/hub/memberships/bindings/describe b/gcloud/beta/container/hub/memberships/bindings/describe new file mode 100644 index 000000000..5a6e4b957 --- /dev/null +++ b/gcloud/beta/container/hub/memberships/bindings/describe @@ -0,0 +1,79 @@ +NAME + gcloud beta container hub memberships bindings describe - show + Membership-Binding info + +SYNOPSIS + gcloud beta container hub memberships bindings describe + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The Membership Binding specified does not exist in the project. + ▪ The caller does not have permission to access the Membership Binding. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To print metadata for the membership Binding BINDING_NAME in a global + membership MEMBERSHIP_NAME, run: + + $ gcloud beta container hub memberships bindings describe \ + BINDING_NAME --membership=MEMBERSHIP_NAME + + To print metadata for the Binding BINDING_NAME associated with regional + membership MEMBERSHIP_NAME, provide the location LOCATION_NAME for the + Membership where the Binding belongs along with membership name. + + $ gcloud beta container hub memberships bindings describe \ + BINDING_NAME --membership=MEMBERSHIP_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub memberships bindings describe + diff --git a/gcloud/beta/container/hub/memberships/bindings/help b/gcloud/beta/container/hub/memberships/bindings/help new file mode 100644 index 000000000..22493a25e --- /dev/null +++ b/gcloud/beta/container/hub/memberships/bindings/help @@ -0,0 +1,46 @@ +NAME + gcloud beta container hub memberships bindings - membership Bindings for + permissions + +SYNOPSIS + gcloud beta container hub memberships bindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command group allows for manipulation of bindings associated + with membership-scope. + +EXAMPLES + Manage Bindings: + + $ gcloud beta container hub memberships bindings --help + +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 Membership Binding. + + delete + (BETA) Delete a Membership Binding. + + describe + (BETA) Show Membership-Binding info. + + list + (BETA) List Bindings in a Membership. + + update + (BETA) Update the Binding in a Membership. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub memberships bindings + diff --git a/gcloud/beta/container/hub/memberships/bindings/list b/gcloud/beta/container/hub/memberships/bindings/list new file mode 100644 index 000000000..b0e5e197d --- /dev/null +++ b/gcloud/beta/container/hub/memberships/bindings/list @@ -0,0 +1,84 @@ +NAME + gcloud beta container hub memberships bindings list - list Bindings in a + Membership + +SYNOPSIS + gcloud beta container hub memberships bindings list --membership=MEMBERSHIP + [--location=LOCATION; default="global"] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The user does not have access to the Membership specified. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + The following command lists Bindings in global Membership MEMBERSHIP_NAME: + + $ gcloud beta container hub memberships bindings list \ + --membership=MEMBERSHIP_NAME + + To list all the bindings associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with membership name. + + $ gcloud beta container hub memberships bindings list BINDING_NAME \ + --membership=MEMBERSHIP_NAME --location=LOCATION_NAME + +REQUIRED FLAGS + --membership=MEMBERSHIP + Name of the Membership to list Bindings from. + +FLAGS + --location=LOCATION; default="global" + Name of the Membership location to list Bindings from. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub memberships bindings list + diff --git a/gcloud/beta/container/hub/memberships/bindings/update b/gcloud/beta/container/hub/memberships/bindings/update new file mode 100644 index 000000000..a7380f89c --- /dev/null +++ b/gcloud/beta/container/hub/memberships/bindings/update @@ -0,0 +1,91 @@ +NAME + gcloud beta container hub memberships bindings update - update the Binding + in a Membership + +SYNOPSIS + gcloud beta container hub memberships bindings update + (BINDING : --location=LOCATION --membership=MEMBERSHIP) + (--fleet=FLEET | --scope=SCOPE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The Membership specified does not exist. + ▪ The Binding does not exist in the Membership. + ▪ The caller does not have permission to access the Membership/Binding. + ▪ The Scope specified does not exist. + ▪ The caller did not specify the location (--location) if referring to + location other than global. + +EXAMPLES + To update the binding BINDING_NAME in global membership MEMBERSHIP_NAME in + the active project: + + $ gcloud beta container hub memberships bindings update \ + BINDING_NAME --membership=MEMBERSHIP_NAME + + To update a Binding BINDING_NAME associated with regional membership + MEMBERSHIP_NAME, provide the location LOCATION_NAME for the Membership + where the Binding belongs along with membership name and associated Scope + SCOPE_NAME. + + $ gcloud beta container hub memberships bindings update \ + BINDING_NAME --membership=MEMBERSHIP_NAME --scope=SCOPE_NAME \ + --location=LOCATION_NAME + +POSITIONAL ARGUMENTS + Binding resource - The group of arguments defining a Membership Binding. + 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 BINDING 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. + + BINDING + ID of the binding or fully qualified identifier for the binding. To + set the binding attribute: + ▸ provide the argument BINDING on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the binding. To set the location attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --membership=MEMBERSHIP + Name of the binding. To set the membership attribute: + ▸ provide the argument BINDING on the command line with a fully + specified name; + ▸ provide the argument --membership on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --fleet=FLEET + Bindings for all the membership related scopes in the fleet would be + updated. + + --scope=SCOPE + Scope related to the Binding. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub memberships bindings update + diff --git a/gcloud/beta/container/hub/memberships/help b/gcloud/beta/container/hub/memberships/help index ed960e4cf..bf62d2e0d 100644 --- a/gcloud/beta/container/hub/memberships/help +++ b/gcloud/beta/container/hub/memberships/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + bindings + (BETA) Membership Bindings for permissions. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/beta/container/hub/namespaces/create b/gcloud/beta/container/hub/namespaces/create new file mode 100644 index 000000000..8eccdfb2d --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/create @@ -0,0 +1,61 @@ +NAME + gcloud beta container hub namespaces create - create a fleet namespace + +SYNOPSIS + gcloud beta container hub namespaces create NAME [--scope=SCOPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The project has a fleet namespace with the same name. + ▪ The caller does not have permission to access the given project. + +EXAMPLES + To create a fleet namespace with name NAMESPACE in the active project, run: + + $ gcloud beta container hub namespaces create NAMESPACE + + To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with + name NAMESPACE, run: + + $ gcloud beta container hub namespaces create NAMESPACE \ + --scope=SCOPE --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the fleet namespace to be created. Must comply with RFC 1123 + (up to 63 characters, alphanumeric and '-') + +FLAGS + Scope resource - The group of arguments defining the Fleet Scope. 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 --scope 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 --scope on the command line with a fully + specified name; + ◆ global is the only supported location. + + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument --scope on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces create + diff --git a/gcloud/beta/container/hub/namespaces/delete b/gcloud/beta/container/hub/namespaces/delete new file mode 100644 index 000000000..f17b38036 --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/delete @@ -0,0 +1,41 @@ +NAME + gcloud beta container hub namespaces delete - delete a fleet namespace + +SYNOPSIS + gcloud beta container hub namespaces delete NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The namespace specified does not exist. + ▪ The caller does not have permission to access the given project or + namespace. + +EXAMPLES + To delete fleet namespace NAMESPACE in the active project: + + $ gcloud beta container hub namespaces delete NAMESPACE + + To delete fleet namespace NAMESPACE in project PROJECT_ID: + + $ gcloud beta container hub namespaces delete NAMESPACE \ + --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the fleet namespace to be deleted. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces delete + diff --git a/gcloud/beta/container/hub/namespaces/describe b/gcloud/beta/container/hub/namespaces/describe new file mode 100644 index 000000000..1cf55fab7 --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/describe @@ -0,0 +1,41 @@ +NAME + gcloud beta container hub namespaces describe - show fleet namespace info + +SYNOPSIS + gcloud beta container hub namespaces describe NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The namespace specified does not exist in the project. + ▪ The caller does not have permission to access the project or + namespace. + +EXAMPLES + To print metadata for the namespace NAMESPACE in the active project, run: + + $ gcloud beta container hub namespaces describe NAMESPACE + + To print metadata for the namespace NAMESPACE in project PROJECT_ID, run: + + $ gcloud beta container hub namespaces describe NAMESPACE \ + --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the fleet namespace to be described. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces describe + diff --git a/gcloud/beta/container/hub/namespaces/get-credentials b/gcloud/beta/container/hub/namespaces/get-credentials new file mode 100644 index 000000000..155f55b7a --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/get-credentials @@ -0,0 +1,58 @@ +NAME + gcloud beta container hub namespaces get-credentials - fetch credentials + for a membership with a particular namespace + +SYNOPSIS + gcloud beta container hub namespaces get-credentials NAMESPACE + [--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION] + [--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using + namespace NAMESPACE in the config: + + $ gcloud beta container hub namespaces get-credentials NAMESPACE \ + --membership=MEMBERSHIP --membership-location=global \ + --set-namespace-in-config=true + + Get the Connect Gateway kubeconfig for global membership MEMBERSHIP: + + $ gcloud beta container hub namespaces get-credentials NAMESPACE \ + --membership=MEMBERSHIP --membership-location=global + +POSITIONAL ARGUMENTS + NAMESPACE + Name of the namespace for which to get access to memberships. + +FLAGS + --membership=MEMBERSHIP + Membership ID to get credentials from. If not provided, a prompt will + offer a list of memberships in the fleet. + + --membership-location=MEMBERSHIP_LOCATION + The location of the membership resource, e.g. us-central1. If not + specified, defaults to global. + + --set-namespace-in-config=SET_NAMESPACE_IN_CONFIG + If true, the default namespace for the context in the generated + kubeconfig will be set to the Fleet namespace (i.e. the name given as + the positional argument in this command). + + Otherwise, no default namespace will be set, functioning the same as + gcloud container fleet memberships get-credentials. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces get-credentials + diff --git a/gcloud/beta/container/hub/namespaces/help b/gcloud/beta/container/hub/namespaces/help new file mode 100644 index 000000000..6d823cc86 --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/help @@ -0,0 +1,57 @@ +NAME + gcloud beta container hub namespaces - fleet namespaces are the fleet + equivalent of k8s cluster namespaces + +SYNOPSIS + gcloud beta container hub namespaces GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command group allows for manipulation of fleet namespaces. + +EXAMPLES + Manage fleet namespaces: + + $ gcloud beta container hub namespaces --help + + Manage RBAC RoleBindings in a fleet namespace: + + $ gcloud beta container hub namespaces rbacrolebindings --help + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + rbacrolebindings + (BETA) Fleet namespace RBAC RoleBindings for permissions. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a fleet namespace. + + delete + (BETA) Delete a fleet namespace. + + describe + (BETA) Show fleet namespace info. + + get-credentials + (BETA) Fetch credentials for a membership with a particular namespace. + + list + (BETA) List fleet namespaces in a project. + + update + (BETA) Update a fleet namespace. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces + diff --git a/gcloud/beta/container/hub/namespaces/list b/gcloud/beta/container/hub/namespaces/list new file mode 100644 index 000000000..272100050 --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/list @@ -0,0 +1,69 @@ +NAME + gcloud beta container hub namespaces list - list fleet namespaces in a + project + +SYNOPSIS + gcloud beta container hub namespaces list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The user does not have access to the project specified. + +EXAMPLES + The following command lists namespaces in the active project: + + $ gcloud beta container hub namespaces list + + The following command lists namespaces in project PROJECT_ID: + + $ gcloud beta container hub namespaces list --project=PROJECT_ID + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces list + diff --git a/gcloud/beta/container/hub/namespaces/rbacrolebindings/create b/gcloud/beta/container/hub/namespaces/rbacrolebindings/create new file mode 100644 index 000000000..397f3edfa --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/rbacrolebindings/create @@ -0,0 +1,88 @@ +NAME + gcloud beta container hub namespaces rbacrolebindings create - create an + RBAC RoleBinding + +SYNOPSIS + gcloud beta container hub namespaces rbacrolebindings create + (NAME : --location=LOCATION --namespace=NAMESPACE) --role=ROLE + (--group=GROUP | --user=USER) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The RBAC RoleBinding already exists. + ▪ The caller does not have permission to access the given namespace. + +EXAMPLES + To create an admin RBAC RoleBinding RBRB in namespace NAMESPACE for user + person@google.com, run: + + $ gcloud beta container hub namespaces rbacrolebindings create \ + RBRB --namespace=NAMESPACE --role=admin --user=person@google.com + + To create a viewer RBAC RoleBinding RBRB in namespace NAMESPACE for group + people@google.com, run: + + $ gcloud beta container hub namespaces rbacrolebindings create \ + RBRB --namespace=NAMESPACE --role=viewer \ + --group=people@google.com + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +REQUIRED FLAGS + --role=ROLE + Role to assign. ROLE must be one of: admin, edit, view. + + Exactly one of these must be specified: + + --group=GROUP + Group for the RoleBinding. + + --user=USER + User for the RoleBinding. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces rbacrolebindings create + diff --git a/gcloud/beta/container/hub/namespaces/rbacrolebindings/delete b/gcloud/beta/container/hub/namespaces/rbacrolebindings/delete new file mode 100644 index 000000000..e5abc6437 --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/rbacrolebindings/delete @@ -0,0 +1,69 @@ +NAME + gcloud beta container hub namespaces rbacrolebindings delete - delete a + fleet namespace RBAC RoleBinding + +SYNOPSIS + gcloud beta container hub namespaces rbacrolebindings delete + (NAME : --location=LOCATION --namespace=NAMESPACE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The RoleBinding specified does not exist. + ▪ The caller does not have permission to access the given RoleBinding. + +EXAMPLES + To delete RBAC RoleBinding RBRB in namespace NAMESPACE in the active + project: + + $ gcloud beta container hub namespaces rbacrolebindings delete \ + RBRB --namespace=NAMESPACE + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces rbacrolebindings delete + diff --git a/gcloud/beta/container/hub/namespaces/rbacrolebindings/describe b/gcloud/beta/container/hub/namespaces/rbacrolebindings/describe new file mode 100644 index 000000000..084408c69 --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/rbacrolebindings/describe @@ -0,0 +1,69 @@ +NAME + gcloud beta container hub namespaces rbacrolebindings describe - show fleet + namespace RBAC RoleBinding information + +SYNOPSIS + gcloud beta container hub namespaces rbacrolebindings describe + (NAME : --location=LOCATION --namespace=NAMESPACE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The RoleBinding specified does not exist in the project. + ▪ The caller does not have permission to access the RoleBinding. + +EXAMPLES + To print metadata for RBAC RoleBinding RBRB in the namespace NAMESPACE, + run: + + $ gcloud beta container hub namespaces rbacrolebindings describe \ + RBRB --namespace=NAMESPACE + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces rbacrolebindings describe + diff --git a/gcloud/beta/container/hub/namespaces/rbacrolebindings/help b/gcloud/beta/container/hub/namespaces/rbacrolebindings/help new file mode 100644 index 000000000..b60a25f30 --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/rbacrolebindings/help @@ -0,0 +1,46 @@ +NAME + gcloud beta container hub namespaces rbacrolebindings - fleet namespace + RBAC RoleBindings for permissions + +SYNOPSIS + gcloud beta container hub namespaces rbacrolebindings COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command group allows for manipulation of fleet namespace RBAC + RoleBindings. + +EXAMPLES + Manage RBAC RoleBindings: + + $ gcloud beta container hub namespaces rbacrolebindings --help + +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 an RBAC RoleBinding. + + delete + (BETA) Delete a fleet namespace RBAC RoleBinding. + + describe + (BETA) Show fleet namespace RBAC RoleBinding information. + + list + (BETA) List RBAC RoleBindings in a fleet namespace. + + update + (BETA) Update a fleet namespace RBAC RoleBinding. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces rbacrolebindings + diff --git a/gcloud/beta/container/hub/namespaces/rbacrolebindings/list b/gcloud/beta/container/hub/namespaces/rbacrolebindings/list new file mode 100644 index 000000000..6381384ae --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/rbacrolebindings/list @@ -0,0 +1,72 @@ +NAME + gcloud beta container hub namespaces rbacrolebindings list - list RBAC + RoleBindings in a fleet namespace + +SYNOPSIS + gcloud beta container hub namespaces rbacrolebindings list + --namespace=NAMESPACE [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The namespace specified does not exist. + ▪ The user does not have access to the specified namespace. + +EXAMPLES + The following command lists RBAC RoleBindings in namespace NAMESPACE in + project PROJECT_ID: + + $ gcloud beta container hub namespaces rbacrolebindings list \ + --namespace=NAMESPACE --project=PROJECT_ID + +REQUIRED FLAGS + --namespace=NAMESPACE + Name of the fleet namespace to list RBAC RoleBindings from. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces rbacrolebindings list + diff --git a/gcloud/beta/container/hub/namespaces/rbacrolebindings/update b/gcloud/beta/container/hub/namespaces/rbacrolebindings/update new file mode 100644 index 000000000..0b885bd48 --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/rbacrolebindings/update @@ -0,0 +1,88 @@ +NAME + gcloud beta container hub namespaces rbacrolebindings update - update a + fleet namespace RBAC RoleBinding + +SYNOPSIS + gcloud beta container hub namespaces rbacrolebindings update + (NAME : --location=LOCATION --namespace=NAMESPACE) [--role=ROLE] + [--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The RoleBinding does not exist in the project. + ▪ The caller does not have permission to access the RoleBinding. + +EXAMPLES + To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active + project to the viewer role: + + $ gcloud beta container hub namespaces rbacrolebindings update \ + RBRB --namespace=NAMESPACE --role=viewer + + To update the RBAC RoleBinding RBRB in namespace NAMESPACE in the active + project to the user someone@google.com: + + $ gcloud beta container hub namespaces rbacrolebindings update \ + RBRB --namespace=NAMESPACE --user=someone@google.com + +POSITIONAL ARGUMENTS + Rbacrolebinding resource - The group of arguments defining an + RBACRoleBinding. 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 NAME 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. + + NAME + ID of the rbacrolebinding or fully qualified identifier for the + rbacrolebinding. To set the rbacrolebinding attribute: + ▸ provide the argument NAME on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location for the rbacrolebinding. To set the location attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property gkehub/location. + + --namespace=NAMESPACE + Name of the rbacrolebinding. To set the namespace attribute: + ▸ provide the argument NAME on the command line with a fully + specified name; + ▸ provide the argument --namespace on the command line. + +FLAGS + --role=ROLE + Role for the RBACRoleBinding to update to. ROLE must be one of: admin, + edit, view. + + At most one of these can be specified: + + --group=GROUP + Group for the RBACRoleBinding to update to. + + --user=USER + User for the RBACRoleBinding to update to. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces rbacrolebindings update + diff --git a/gcloud/beta/container/hub/namespaces/update b/gcloud/beta/container/hub/namespaces/update new file mode 100644 index 000000000..1250e1fde --- /dev/null +++ b/gcloud/beta/container/hub/namespaces/update @@ -0,0 +1,60 @@ +NAME + gcloud beta container hub namespaces update - update a fleet namespace + +SYNOPSIS + gcloud beta container hub namespaces update NAME [--scope=SCOPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command can fail for the following reasons: + ▪ The project specified does not exist. + ▪ The fleet namespace does not exist in the project. + ▪ The caller does not have permission to access the project or + namespace. + +EXAMPLES + To update the namespace NAMESPACE in the active project: + + $ gcloud beta container hub namespaces update NAMESPACE + + To update the namespace NAMESPACE in project PROJECT_ID: + + $ gcloud beta container hub namespaces update NAMESPACE \ + --project=PROJECT_ID + +POSITIONAL ARGUMENTS + NAME + Name of the namespace to be updated. + +FLAGS + Scope resource - The group of arguments defining the Fleet Scope. 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 --scope 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 --scope on the command line with a fully + specified name; + ◆ global is the only supported location. + + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument --scope on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub namespaces update + diff --git a/gcloud/beta/container/hub/scopes/create b/gcloud/beta/container/hub/scopes/create new file mode 100644 index 000000000..0a024102e --- /dev/null +++ b/gcloud/beta/container/hub/scopes/create @@ -0,0 +1,59 @@ +NAME + gcloud beta container hub scopes create - create a new fleet scope + +SYNOPSIS + gcloud beta container hub scopes create SCOPE [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Fleet Scope resource. + +EXAMPLES + Create a new scope SCOPE_NAME in the active project's fleet: + + $ gcloud beta container hub scopes create SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - The fleet scope resourse to be created. 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 scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. To set the + location attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ global is the only supported location. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument scope 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 gkehub/v1beta API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub scopes create + diff --git a/gcloud/beta/container/hub/scopes/delete b/gcloud/beta/container/hub/scopes/delete new file mode 100644 index 000000000..c9620a600 --- /dev/null +++ b/gcloud/beta/container/hub/scopes/delete @@ -0,0 +1,72 @@ +NAME + gcloud beta container hub scopes delete - delete a fleet scope + +SYNOPSIS + gcloud beta container hub scopes delete (SCOPE : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command deletes a Fleet Scope resource . + +EXAMPLES + First retrieve the ID of the scope using the command below. The output of + this command lists all the fleet's scopes, with their unique IDs in the + Names column: + + $ gcloud beta container hub scopes list + + Delete a scope from the active project's fleet: + + $ gcloud beta container hub scopes delete SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - The fleet scope to delete. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. To set the project attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument scope 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 name. To set the location attribute: + ▸ provide the argument scope on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +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 gkehub/v1beta API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub scopes delete + diff --git a/gcloud/beta/container/hub/scopes/describe b/gcloud/beta/container/hub/scopes/describe new file mode 100644 index 000000000..bd23cae83 --- /dev/null +++ b/gcloud/beta/container/hub/scopes/describe @@ -0,0 +1,67 @@ +NAME + gcloud beta container hub scopes describe - describe a fleet scope + +SYNOPSIS + gcloud beta container hub scopes describe (SCOPE : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Fleet Scope. + +EXAMPLES + First retrieve the ID of the scope using the command below. The output of + this command lists all the fleet's members, with their unique IDs in the + Names column: + + $ gcloud beta container hub scopes list + + Then describe it: + + $ gcloud beta container hub scopes describe SCOPE_NAME + +POSITIONAL ARGUMENTS + Scope resource - The scope to describe. The arguments in this group can be + used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. To set + the project attribute: + ◆ provide the argument scope on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SCOPE + ID of the scope or fully qualified identifier for the scope. To set + the scope attribute: + ▸ provide the argument scope 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 name. To set the location attribute: + ▸ provide the argument scope on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkehub/v1beta API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub scopes describe + diff --git a/gcloud/beta/container/hub/scopes/help b/gcloud/beta/container/hub/scopes/help new file mode 100644 index 000000000..c278fb660 --- /dev/null +++ b/gcloud/beta/container/hub/scopes/help @@ -0,0 +1,35 @@ +NAME + gcloud beta container hub scopes - manage scopes of all your GKE fleets + +SYNOPSIS + gcloud beta container hub scopes COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage scopes of all your GKE fleets. + +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 new fleet scope. + + delete + (BETA) Delete a fleet scope. + + describe + (BETA) Describe a fleet scope. + + list + (BETA) List fleet scopes. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub scopes + diff --git a/gcloud/beta/container/hub/scopes/list b/gcloud/beta/container/hub/scopes/list new file mode 100644 index 000000000..e6d74c1ef --- /dev/null +++ b/gcloud/beta/container/hub/scopes/list @@ -0,0 +1,67 @@ +NAME + gcloud beta container hub scopes list - list fleet scopes + +SYNOPSIS + gcloud beta container hub scopes list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List scopes in a fleet. + +EXAMPLES + List scopes in the active project's fleet: + + $ gcloud beta container hub scopes list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkehub/v1beta API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container hub scopes list + diff --git a/gcloud/beta/firebase/test/android/run b/gcloud/beta/firebase/test/android/run index 56086fdb8..17dfcef35 100644 --- a/gcloud/beta/firebase/test/android/run +++ b/gcloud/beta/firebase/test/android/run @@ -111,6 +111,12 @@ EXAMPLES executions, but only the subset of executions with valid dimension combinations will actually run your tests. + To help you identify and locate your test matrix in the Firebase console, + run: + + $ gcloud beta firebase test android run --app=APP_APK \ + --client-details=matrixLabel="Example matrix label" + Controlling Results Storage By default, Firebase Test Lab stores detailed test results for a limited diff --git a/gcloud/beta/firebase/test/ios/run b/gcloud/beta/firebase/test/ios/run index 5cc26a5f9..b4905aba4 100644 --- a/gcloud/beta/firebase/test/ios/run +++ b/gcloud/beta/firebase/test/ios/run @@ -69,6 +69,12 @@ EXAMPLES $ gcloud beta firebase test ios run --test=XCTEST_ZIP \ --xcode-version=9.4.1 + To help you identify and locate your test matrix in the Firebase console, + run: + + $ gcloud beta firebase test ios run --test=XCTEST_ZIP \ + --client-details=matrixLabel="Example matrix label" + To run an iOS game loop, specify the --type and --app flags: $ gcloud beta firebase test ios run --type=game-loop --app=app.ipa diff --git a/gcloud/beta/firestore/databases/create b/gcloud/beta/firestore/databases/create index 530e08b83..ddcd30c95 100644 --- a/gcloud/beta/firestore/databases/create +++ b/gcloud/beta/firestore/databases/create @@ -1,31 +1,48 @@ NAME gcloud beta firestore databases create - create a Google Cloud Firestore - Native database + database via Firestore API SYNOPSIS - gcloud beta firestore databases create [--region=REGION] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) Create a Google Cloud Firestore Native database. + gcloud beta firestore databases create --location=LOCATION + [--database=DATABASE; default="(default)"] + [--type=TYPE; default="firestore-native"] [GCLOUD_WIDE_FLAG ...] EXAMPLES - To create Google Cloud Firestore Native database + To create Firestore Native database in nam5. - $ gcloud beta firestore databases create + $ gcloud beta firestore databases create --location=nam5 - To create an app in the nam5 region (multi-region), run: + To create Datastore Mode database in us-east1. - $ gcloud beta firestore databases create --region=nam5 + $ gcloud beta firestore databases create --location=us-east1 \ + --type=datastore-mode - To create an app in the us-east1 region, run: + To create Datastore Mode database in us-east1 with a databaseId foo. - $ gcloud beta firestore databases create --region=us-east1 + $ gcloud beta firestore databases create --database=mytest \ + --location=us-east1 --type=datastore-mode -FLAGS - --region=REGION - The region to create the Google Cloud Firestore Native database within. - Use gcloud app regions list to list available regions. +REQUIRED FLAGS + --location=LOCATION + The location to create the Google Cloud Firestore Native database + within. Available locations are listed at + https://cloud.google.com/firestore/docs/locations. + +OPTIONAL FLAGS + --database=DATABASE; default="(default)" + The ID to use for the database, which will become the final component + of the database's resource name. If database ID is not provided, + (default) will be used as database ID. + + This value should be 4-63 characters. Valid characters are /[a-z][0-9]-/ + with first character a letter and the last a letter or a number. Must + not be UUID-like /[0-9a-f]{8}(-[0-9a-f]{4}){3}-[0-9a-f]{12}/. + + Using "(default)" database ID is also allowed. + + --type=TYPE; default="firestore-native" + The type of the database. TYPE must be one of: firestore-native, + datastore-mode. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/firestore/databases/help b/gcloud/beta/firestore/databases/help index 8a9b13213..01dc9490f 100644 --- a/gcloud/beta/firestore/databases/help +++ b/gcloud/beta/firestore/databases/help @@ -17,7 +17,7 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create a Google Cloud Firestore Native database. + (BETA) Create a Google Cloud Firestore database via Firestore API. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/iam/workforce-pools/create-login-config b/gcloud/beta/iam/workforce-pools/create-login-config new file mode 100644 index 000000000..6a71d6e4d --- /dev/null +++ b/gcloud/beta/iam/workforce-pools/create-login-config @@ -0,0 +1,51 @@ +NAME + gcloud beta iam workforce-pools create-login-config - create a login + configuration file to enable sign-in via a web-based authorization flow + using Workforce Identity Federation + +SYNOPSIS + gcloud beta iam workforce-pools create-login-config AUDIENCE + --output-file=OUTPUT_FILE [--activate] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command creates a configuration file to enable browser based + third-party sign in with Workforce Identity Federation through gcloud auth + login --login-config=/path/to/config.json. + +EXAMPLES + To create a login configuration for your project, run: + + $ gcloud beta iam workforce-pools create-login-config \ + locations/global/workforcePools/$WORKFORCE_POOL_ID/providers/\ + $PROVIDER_ID --output-file=login-config.json + +POSITIONAL ARGUMENTS + AUDIENCE + Workforce pool provider resource name. + +REQUIRED FLAGS + --output-file=OUTPUT_FILE + Location to store the generated login configuration file. + +OPTIONAL FLAGS + --activate + Sets the property auth/login_config_file to the created login + configuration file. Calling gcloud auth login will automatically use + this login configuration unless it is explicitly unset. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud iam workforce-pools create-login-config + + $ gcloud alpha iam workforce-pools create-login-config + diff --git a/gcloud/beta/iam/workforce-pools/help b/gcloud/beta/iam/workforce-pools/help index 8c394977d..b4ee464f0 100644 --- a/gcloud/beta/iam/workforce-pools/help +++ b/gcloud/beta/iam/workforce-pools/help @@ -31,6 +31,10 @@ COMMANDS create-cred-config (BETA) Create a configuration file for generated credentials. + create-login-config + (BETA) Create a login configuration file to enable sign-in via a + web-based authorization flow using Workforce Identity Federation. + delete (BETA) Delete a workforce pool. diff --git a/gcloud/beta/kms/help b/gcloud/beta/kms/help index e2aae16b3..d3b0a5616 100644 --- a/gcloud/beta/kms/help +++ b/gcloud/beta/kms/help @@ -34,6 +34,9 @@ GROUPS import-jobs (BETA) Create and manage import jobs. + inventory + (BETA) Manages the KMS Inventory and Key Tracking commands. + keyrings (BETA) Create and manage keyrings. diff --git a/gcloud/beta/kms/inventory/get-protected-resources-summary b/gcloud/beta/kms/inventory/get-protected-resources-summary new file mode 100644 index 000000000..cf647a3c3 --- /dev/null +++ b/gcloud/beta/kms/inventory/get-protected-resources-summary @@ -0,0 +1,68 @@ +NAME + gcloud beta kms inventory get-protected-resources-summary - gets the + protected resources summary + +SYNOPSIS + gcloud beta kms inventory get-protected-resources-summary + (--keyname=KEYNAME : --keyring=KEYRING --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta kms inventory get-protected-resources-summary returns a + summary of the resources a key is protecting. + + The summary includes: How many projects contain protected resources How + many protected resources there are What types of protected resources The + count for each type of protected resource + +EXAMPLES + To view the summary of protected resources for the key puppy, run: + + $ gcloud beta kms inventory get-protected-resources-summary \ + --keyname=puppy + +REQUIRED FLAGS + Key resource - The KMS key 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 --keyname on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + --keyname=KEYNAME + ID of the key or fully qualified identifier for the key. To set the + key attribute: + ▸ provide the argument --keyname on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --keyring=KEYRING + The KMS keyring of the key. To set the keyring attribute: + ▸ provide the argument --keyname on the command line with a fully + specified name; + ▸ provide the argument --keyring on the command line. + + --location=LOCATION + The Google Cloud location for the key. To set the location attribute: + ▸ provide the argument --keyname on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha kms inventory get-protected-resources-summary + diff --git a/gcloud/beta/kms/inventory/help b/gcloud/beta/kms/inventory/help new file mode 100644 index 000000000..e31071c83 --- /dev/null +++ b/gcloud/beta/kms/inventory/help @@ -0,0 +1,33 @@ +NAME + gcloud beta kms inventory - manages the KMS Inventory and Key Tracking + commands + +SYNOPSIS + gcloud beta kms inventory COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manages the KMS Inventory and Key Tracking commands. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + get-protected-resources-summary + (BETA) Gets the protected resources summary. + + list-keys + (BETA) Lists the keys in a project. + + search-protected-resources + (BETA) Searches the resources protected by a key. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha kms inventory + diff --git a/gcloud/beta/kms/inventory/list-keys b/gcloud/beta/kms/inventory/list-keys new file mode 100644 index 000000000..206857897 --- /dev/null +++ b/gcloud/beta/kms/inventory/list-keys @@ -0,0 +1,67 @@ +NAME + gcloud beta kms inventory list-keys - lists the keys in a project + +SYNOPSIS + gcloud beta kms inventory list-keys [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta kms inventory list-keys lists the keys in the specified + project. + +EXAMPLES + To view the keys in the default project, run: + + $ gcloud beta kms inventory list-keys + + To view the keys in project jellyfish, run: + + $ gcloud beta kms inventory list-keys --project=jellyfish + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha kms inventory list-keys + diff --git a/gcloud/beta/kms/inventory/search-protected-resources b/gcloud/beta/kms/inventory/search-protected-resources new file mode 100644 index 000000000..a3a672b1a --- /dev/null +++ b/gcloud/beta/kms/inventory/search-protected-resources @@ -0,0 +1,102 @@ +NAME + gcloud beta kms inventory search-protected-resources - searches the + resources protected by a key + +SYNOPSIS + gcloud beta kms inventory search-protected-resources + --scope=ORGANIZATION_ID + (--keyname=KEYNAME : --keyring=KEYRING --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta kms inventory search-protected-resources returns a list + of the resources a key is protecting within the specified organization. + +EXAMPLES + To view the protected resources for the key puppy and organization number + 1234 run: + + $ gcloud beta kms inventory search-protected-resources \ + --keyname=puppy --scope=1234 + +REQUIRED FLAGS + --scope=ORGANIZATION_ID + Organization ID. + + Key resource - The KMS key 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 --keyname on the command line with a fully + specified name; + ◆ set the property core/project. + + This must be specified. + + --keyname=KEYNAME + ID of the key or fully qualified identifier for the key. To set the + key attribute: + ▸ provide the argument --keyname on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --keyring=KEYRING + The KMS keyring of the key. To set the keyring attribute: + ▸ provide the argument --keyname on the command line with a fully + specified name; + ▸ provide the argument --keyring on the command line. + + --location=LOCATION + The Google Cloud location for the key. To set the location attribute: + ▸ provide the argument --keyname 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. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha kms inventory search-protected-resources + diff --git a/gcloud/beta/logging/buckets/create b/gcloud/beta/logging/buckets/create index 76863f3f6..e2e1c2e2c 100644 --- a/gcloud/beta/logging/buckets/create +++ b/gcloud/beta/logging/buckets/create @@ -2,9 +2,9 @@ NAME gcloud beta logging buckets create - create a bucket SYNOPSIS - gcloud beta logging buckets create BUCKET_ID --location=LOCATION + gcloud beta logging buckets create BUCKET_ID --location=LOCATION [--async] [--cmek-kms-key-name=CMEK_KMS_KEY_NAME] [--description=DESCRIPTION] - [--index=[KEY=VALUE, ...,...]] + [--enable-analytics] [--index=[KEY=VALUE, ...,...]] [--restricted-fields=[RESTRICTED_FIELD,...]] [--retention-days=RETENTION_DAYS] [GCLOUD_WIDE_FLAG ...] @@ -37,6 +37,11 @@ EXAMPLES $ gcloud beta logging buckets create my-bucket \ --location=us-central1 --cmek-kms-key-name=CMEK_KMS_KEY_NAME + To asynchronously create a bucket enrolled into Log Analytics, run: + + $ gcloud beta logging buckets create my-bucket --location=global \ + --async --enable-analytics + POSITIONAL ARGUMENTS BUCKET_ID ID of the bucket to create. @@ -47,12 +52,20 @@ REQUIRED FLAGS location cannot be changed. OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + --cmek-kms-key-name=CMEK_KMS_KEY_NAME A valid kms_key_name will enable CMEK for the bucket. --description=DESCRIPTION A textual description for the bucket. + --enable-analytics + Whether to opt the bucket into Log Analytics. Once opted in, the bucket + cannot be opted out of Log Analytics. + --index=[KEY=VALUE, ...,...] Specify an index to be added to the log bucket. This flag can be repeated. The fieldPath and type attributes are required. For example: diff --git a/gcloud/beta/logging/buckets/update b/gcloud/beta/logging/buckets/update index 8c04400fd..447be5059 100644 --- a/gcloud/beta/logging/buckets/update +++ b/gcloud/beta/logging/buckets/update @@ -3,9 +3,9 @@ NAME SYNOPSIS gcloud beta logging buckets update BUCKET_ID --location=LOCATION - [--add-index=[KEY=VALUE, ...,...]] [--clear-indexes] + [--add-index=[KEY=VALUE, ...,...]] [--async] [--clear-indexes] [--cmek-kms-key-name=CMEK_KMS_KEY_NAME] [--description=DESCRIPTION] - [--locked] [--remove-indexes=[FIELD PATH,...]] + [--enable-analytics] [--locked] [--remove-indexes=[FIELD PATH,...]] [--restricted-fields=[RESTRICTED_FIELD,...]] [--retention-days=RETENTION_DAYS] [--update-index=[KEY=VALUE, ...,...]] [GCLOUD_WIDE_FLAG ...] @@ -44,6 +44,11 @@ EXAMPLES $ gcloud beta logging buckets update my-bucket --location=global \ --cmek-kms-key-name=CMEK_KEY_NAME + To asynchronously enroll a bucket in your project into Log Analytics, run: + + $ gcloud beta logging buckets update my-bucket --location=global \ + --async --enable-analytics + POSITIONAL ARGUMENTS BUCKET_ID The id of the bucket to update. @@ -69,6 +74,10 @@ OPTIONAL FLAGS The type of data in this index. For example: INDEX_TYPE_STRING Supported types are strings and integers. + --async + Return immediately, without waiting for the operation in progress to + complete. + --clear-indexes Remove all logging indexes from the bucket. @@ -78,6 +87,10 @@ OPTIONAL FLAGS --description=DESCRIPTION A new description for the bucket. + --enable-analytics + Whether to opt the bucket into Log Analytics. Once opted in, the bucket + cannot be opted out of Log Analytics. + --locked Lock the bucket and prevent it from being modified or deleted (unless it is empty). diff --git a/gcloud/beta/logging/help b/gcloud/beta/logging/help index 4c8df9c4e..39862295c 100644 --- a/gcloud/beta/logging/help +++ b/gcloud/beta/logging/help @@ -18,6 +18,9 @@ GROUPS buckets (BETA) Manage Cloud Logging buckets. + links + (BETA) Manage log links. + locations (BETA) Query Cloud Logging locations. diff --git a/gcloud/beta/logging/links/create b/gcloud/beta/logging/links/create new file mode 100644 index 000000000..5feb25496 --- /dev/null +++ b/gcloud/beta/logging/links/create @@ -0,0 +1,79 @@ +NAME + gcloud beta logging links create - create a link on an analytics log bucket + +SYNOPSIS + gcloud beta logging links create LINK_ID --bucket=BUCKET + --location=LOCATION [--async] [--description=DESCRIPTION] + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a link for a log bucket. + +EXAMPLES + To create a link in a project, run: + + $ gcloud beta logging links create my-link --bucket=my-bucket \ + --location=global + +POSITIONAL ARGUMENTS + LINK_ID + ID of the link to create. + +REQUIRED FLAGS + --bucket=BUCKET + ID of the bucket that will hold the link + + --location=LOCATION + Location of the bucket that will hold the link. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A textual description for the link. + + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the link to create. + + --folder=FOLDER_ID + Folder of the link to create. + + --organization=ORGANIZATION_ID + Organization of the link to create. + + --project=PROJECT_ID + Project of the link to create. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud logging links create + + $ gcloud alpha logging links create + diff --git a/gcloud/beta/logging/links/delete b/gcloud/beta/logging/links/delete new file mode 100644 index 000000000..8fd45e1ed --- /dev/null +++ b/gcloud/beta/logging/links/delete @@ -0,0 +1,76 @@ +NAME + gcloud beta logging links delete - delete a link + +SYNOPSIS + gcloud beta logging links delete LINK_ID --bucket=BUCKET + --location=LOCATION [--async] + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes a bucket's link. + +EXAMPLES + To delete a bucket's link, run: + + $ gcloud beta logging links delete my-link --bucket=my-bucket \ + --location=global + +POSITIONAL ARGUMENTS + LINK_ID + ID of the link to delete. + +REQUIRED FLAGS + --bucket=BUCKET + ID of bucket + + --location=LOCATION + Location of the bucket. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the link to delete. + + --folder=FOLDER_ID + Folder of the link to delete. + + --organization=ORGANIZATION_ID + Organization of the link to delete. + + --project=PROJECT_ID + Project of the link to delete. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud logging links delete + + $ gcloud alpha logging links delete + diff --git a/gcloud/beta/logging/links/describe b/gcloud/beta/logging/links/describe new file mode 100644 index 000000000..68e5b6495 --- /dev/null +++ b/gcloud/beta/logging/links/describe @@ -0,0 +1,72 @@ +NAME + gcloud beta logging links describe - display information about a link + +SYNOPSIS + gcloud beta logging links describe LINK_ID --bucket=BUCKET + --location=LOCATION + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Displays information about a link. + +EXAMPLES + To describe a link in a project, run: + + $ gcloud beta logging links describe my-link --bucket=my-bucket \ + --location=global + +POSITIONAL ARGUMENTS + LINK_ID + Id of the link to describe. + +REQUIRED FLAGS + --bucket=BUCKET + ID of bucket + + --location=LOCATION + Location of the bucket. + +OPTIONAL FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the link to describe. + + --folder=FOLDER_ID + Folder of the link to describe. + + --organization=ORGANIZATION_ID + Organization of the link to describe. + + --project=PROJECT_ID + Project of the link to describe. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud logging links describe + + $ gcloud alpha logging links describe + diff --git a/gcloud/beta/logging/links/help b/gcloud/beta/logging/links/help new file mode 100644 index 000000000..320d123a9 --- /dev/null +++ b/gcloud/beta/logging/links/help @@ -0,0 +1,38 @@ +NAME + gcloud beta logging links - manage log links + +SYNOPSIS + gcloud beta logging links COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Commands for managing links. A log link represents a linked BigQuery + dataset that contains log data for the link's parent log bucket. + +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 link on an analytics log bucket. + + delete + (BETA) Delete a link. + + describe + (BETA) Display information about a link. + + list + (BETA) List created links on the specified bucket. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud logging links + + $ gcloud alpha logging links + diff --git a/gcloud/beta/logging/links/list b/gcloud/beta/logging/links/list new file mode 100644 index 000000000..f2c033684 --- /dev/null +++ b/gcloud/beta/logging/links/list @@ -0,0 +1,99 @@ +NAME + gcloud beta logging links list - list created links on the specified bucket + +SYNOPSIS + gcloud beta logging links list --bucket=BUCKET --location=LOCATION + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Lists the links created for a bucket. + +EXAMPLES + To list the links created for a bucket, run: + + $ gcloud beta logging links list + +REQUIRED FLAGS + --bucket=BUCKET + ID of bucket + + --location=LOCATION + Location of the specified bucket + +FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the links to list. + + --folder=FOLDER_ID + Folder of the links to list. + + --organization=ORGANIZATION_ID + Organization of the links to list. + + --project=PROJECT_ID + Project of the links to list. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud logging links list + + $ gcloud alpha logging links list + diff --git a/gcloud/beta/ml-engine/jobs/submit/training b/gcloud/beta/ml-engine/jobs/submit/training index 241db7f8a..e467bd809 100644 --- a/gcloud/beta/ml-engine/jobs/submit/training +++ b/gcloud/beta/ml-engine/jobs/submit/training @@ -149,7 +149,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. @@ -200,7 +200,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. @@ -322,7 +322,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. diff --git a/gcloud/beta/services/api-keys/update b/gcloud/beta/services/api-keys/update index 6752fcacc..843444d11 100644 --- a/gcloud/beta/services/api-keys/update +++ b/gcloud/beta/services/api-keys/update @@ -2,10 +2,10 @@ NAME gcloud beta services api-keys update - update an API key's metadata SYNOPSIS - gcloud beta services api-keys update (KEY : --location=LOCATION) - [--annotations=[KEY=VALUE,...]] [--async] [--display-name=DISPLAY_NAME] - [--clear-annotations | --clear-restrictions - | --api-target=service=SERVICE,[...] + gcloud beta services api-keys update (KEY : --location=LOCATION) [--async] + [--display-name=DISPLAY_NAME] + [--annotations=[KEY=VALUE,...] | --clear-annotations] + [--clear-restrictions | --api-target=service=SERVICE,[...] --allowed-application=[sha1_fingerprint=SHA1_FINGERPRINT, package_name=PACKAGE_NAME,...] | --allowed-bundle-ids=[ALLOWED_BUNDLE_IDS,...] @@ -103,10 +103,6 @@ POSITIONAL ARGUMENTS ▸ location will default to global. FLAGS - --annotations=[KEY=VALUE,...] - Annotations are key resource. Specify annotations as a key-value - dictionary for small amounts of arbitrary client data. - --async Return immediately, without waiting for the operation in progress to complete. @@ -116,9 +112,15 @@ FLAGS At most one of these can be specified: + --annotations=[KEY=VALUE,...] + Annotations are key resource. Specify annotations as a key-value + dictionary for small amounts of arbitrary client data. + --clear-annotations If set, clear all annotations on the key. + At most one of these can be specified: + --clear-restrictions If set, clear all restrictions on the key. diff --git a/gcloud/builds/triggers/create/bitbucketserver b/gcloud/builds/triggers/create/bitbucketserver index 74a25eaa9..371b75ab7 100644 --- a/gcloud/builds/triggers/create/bitbucketserver +++ b/gcloud/builds/triggers/create/bitbucketserver @@ -128,9 +128,10 @@ REQUIRED FLAGS --branch-pattern=REGEX A regular expression specifying which git branches to match. - This pattern is used as a regex search for any incoming pushes. - For example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at @@ -139,9 +140,10 @@ REQUIRED FLAGS --tag-pattern=REGEX A regular expression specifying which git tags to match. - This pattern is used as a regex search for any incoming pushes. - For example, --tag-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a tag that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at diff --git a/gcloud/builds/triggers/create/cloud-source-repositories b/gcloud/builds/triggers/create/cloud-source-repositories index 26da31544..c5c76dc92 100644 --- a/gcloud/builds/triggers/create/cloud-source-repositories +++ b/gcloud/builds/triggers/create/cloud-source-repositories @@ -107,9 +107,10 @@ REQUIRED FLAGS --branch-pattern=REGEX A regular expression specifying which git branches to match. - This pattern is used as a regex search for any incoming pushes. - For example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at @@ -118,9 +119,10 @@ REQUIRED FLAGS --tag-pattern=REGEX A regular expression specifying which git tags to match. - This pattern is used as a regex search for any incoming pushes. - For example, --tag-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a tag that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at diff --git a/gcloud/builds/triggers/create/github b/gcloud/builds/triggers/create/github index 83dbd2aad..3c99be2ee 100644 --- a/gcloud/builds/triggers/create/github +++ b/gcloud/builds/triggers/create/github @@ -119,9 +119,10 @@ REQUIRED FLAGS --branch-pattern=REGEX A regular expression specifying which git branches to match. - This pattern is used as a regex search for any incoming pushes. - For example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at @@ -130,9 +131,10 @@ REQUIRED FLAGS --tag-pattern=REGEX A regular expression specifying which git tags to match. - This pattern is used as a regex search for any incoming pushes. - For example, --tag-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a tag that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at diff --git a/gcloud/builds/triggers/create/gitlab-enterprise b/gcloud/builds/triggers/create/gitlab-enterprise index 96471b265..24c87d6c3 100644 --- a/gcloud/builds/triggers/create/gitlab-enterprise +++ b/gcloud/builds/triggers/create/gitlab-enterprise @@ -109,9 +109,10 @@ REQUIRED FLAGS --branch-pattern=REGEX A regular expression specifying which git branches to match. - This pattern is used as a regex search for any incoming pushes. - For example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --branch-pattern=foo will match + "foo", "foobar", and "barfoo". Events on a branch that does not + match will be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at @@ -120,9 +121,10 @@ REQUIRED FLAGS --tag-pattern=REGEX A regular expression specifying which git tags to match. - This pattern is used as a regex search for any incoming pushes. - For example, --tag-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a tag that does not match will be ignored. + This pattern is used as a regular expression search for any + incoming pushes. For example, --tag-pattern=foo will match "foo", + "foobar", and "barfoo". Events on a tag that does not match will + be ignored. The syntax of the regular expressions accepted is the syntax accepted by RE2 and described at diff --git a/gcloud/compute/disks/create b/gcloud/compute/disks/create index d7c5631fa..690f09efd 100644 --- a/gcloud/compute/disks/create +++ b/gcloud/compute/disks/create @@ -89,9 +89,8 @@ FLAGS policies. --provisioned-iops=PROVISIONED_IOPS - Provisioned IOPS of pd-extreme disk to create. Only for use with disks - of type pd-extreme. If specified, the value must be in the range - between 2500 and 120000. If not specified, the default value is 100000. + Provisioned IOPS of disk to create. Only for use with disks of type + pd-extreme and hyperdisk-extreme. --replica-zones=ZONE,ZONE A comma-separated list of exactly 2 zones that a regional disk will be diff --git a/gcloud/compute/disks/update b/gcloud/compute/disks/update index c57c3bf97..eab46f66c 100644 --- a/gcloud/compute/disks/update +++ b/gcloud/compute/disks/update @@ -2,7 +2,8 @@ NAME gcloud compute disks update - update a Compute Engine persistent disk SYNOPSIS - gcloud compute disks update DISK_NAME [--update-labels=[KEY=VALUE,...]] + gcloud compute disks update DISK_NAME [--provisioned-iops=PROVISIONED_IOPS] + [--update-labels=[KEY=VALUE,...]] [--clear-architecture | --update-architecture=UPDATE_ARCHITECTURE] [--clear-labels | --remove-labels=[KEY,...]] [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] @@ -34,6 +35,10 @@ POSITIONAL ARGUMENTS Name of the disk to update. FLAGS + --provisioned-iops=PROVISIONED_IOPS + Provisioned IOPS of disk to update. Only for use with disks of type + hyperdisk-extreme. + --update-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its value is modified. Otherwise, a new label is created. diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index 92cd676bd..bfad6283e 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -34,7 +34,7 @@ SYNOPSIS [--resource-policies=[RESOURCE_POLICY,...]] [--no-restart-on-failure] [--shielded-integrity-monitoring] [--shielded-secure-boot] [--shielded-vtpm] [--source-instance-template=SOURCE_INSTANCE_TEMPLATE] - [--subnet=SUBNET] [--tags=TAG,[TAG,...]] + [--stack-type=STACK_TYPE] [--subnet=SUBNET] [--tags=TAG,[TAG,...]] [--target-distribution-shape=SHAPE] [--threads-per-core=THREADS_PER_CORE] [--visible-core-count=VISIBLE_CORE_COUNT] @@ -625,6 +625,15 @@ OPTIONAL FLAGS The name of the instance template that the instance will be created from. Users can override fields by specifying other flags. + --stack-type=STACK_TYPE + Specifies whether IPv6 is enabled on the default network interface. If + not specified, IPV4_ONLY will be used. 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 + --subnet=SUBNET Specifies the subnet that the VM instances are a part of. If --network is also specified, subnet must be a subnetwork of the network specified diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index db3c708fc..aa995374b 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -91,19 +91,19 @@ EXAMPLES example-instance-2 example-instance-3 --zone=us-central1-a To create an instance called 'instance-1' from a source snapshot called - 'instance-snapshot' in zone 'us-central2-a' and attached regional disk + 'instance-snapshot' in zone 'us-central1-a' and attached regional disk 'disk-1', run: $ gcloud compute instances create instance-1 \ --source-snapshot=https://compute.googleapis.com/compute/v1/\ projects/myproject/global/snapshots/instance-snapshot \ - --zone=central2-a --disk=name=disk1,scope=regional + --zone=us-central1-a --disk=name=disk1,scope=regional To create an instance called instance-1 as a Shielded VM instance with Secure Boot, virtual trusted platform module (vTPM) enabled and integrity monitoring, run: - $ gcloud compute instances create instance-1 --zone=central2-a \ + $ gcloud compute instances create instance-1 --zone=us-central1-a \ --shielded-secure-boot --shielded-vtpm \ --shielded-integrity-monitoring diff --git a/gcloud/compute/routers/add-bgp-peer b/gcloud/compute/routers/add-bgp-peer index 8f362c82a..edf16797d 100644 --- a/gcloud/compute/routers/add-bgp-peer +++ b/gcloud/compute/routers/add-bgp-peer @@ -144,7 +144,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --set-advertisement-ranges=[CIDR_RANGE=DESC,...] The list of individual IP ranges, in CIDR format, to dynamically diff --git a/gcloud/compute/routers/create b/gcloud/compute/routers/create index b2e87dba2..e2de7e309 100644 --- a/gcloud/compute/routers/create +++ b/gcloud/compute/routers/create @@ -88,7 +88,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --set-advertisement-ranges=[CIDR_RANGE=DESC,...] The list of individual IP ranges, in CIDR format, to dynamically diff --git a/gcloud/compute/routers/update b/gcloud/compute/routers/update index 7a700845e..8af0ed703 100644 --- a/gcloud/compute/routers/update +++ b/gcloud/compute/routers/update @@ -83,7 +83,8 @@ FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --set-advertisement-ranges=[CIDR_RANGE=DESC,...] The list of individual IP ranges, in CIDR format, to dynamically @@ -103,7 +104,8 @@ FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --add-advertisement-ranges=[CIDR_RANGE=DESC,...] A list of individual IP ranges, in CIDR format, to dynamically @@ -123,7 +125,8 @@ FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --remove-advertisement-ranges=[CIDR_RANGE,...] A list of individual IP ranges, in CIDR format, to remove from diff --git a/gcloud/compute/routers/update-bgp-peer b/gcloud/compute/routers/update-bgp-peer index d5988e8f0..2edeb25ef 100644 --- a/gcloud/compute/routers/update-bgp-peer +++ b/gcloud/compute/routers/update-bgp-peer @@ -130,7 +130,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --set-advertisement-ranges=[CIDR_RANGE=DESC,...] The list of individual IP ranges, in CIDR format, to dynamically @@ -150,7 +151,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --add-advertisement-ranges=[CIDR_RANGE=DESC,...] A list of individual IP ranges, in CIDR format, to dynamically @@ -170,7 +172,8 @@ OPTIONAL FLAGS GROUP must be (currently only one value is supported): ALL_SUBNETS - Automatically advertise all available subnets. + Automatically advertise all available subnets. This excludes any + routes learned for subnets that use VPC Network Peering. --remove-advertisement-ranges=[CIDR_RANGE,...] A list of individual IP ranges, in CIDR format, to remove from diff --git a/gcloud/compute/tpus/locations/describe b/gcloud/compute/tpus/locations/describe index 888872f5a..59f97fcb4 100644 --- a/gcloud/compute/tpus/locations/describe +++ b/gcloud/compute/tpus/locations/describe @@ -14,7 +14,7 @@ DESCRIPTION EXAMPLES The following command describes the TPUs running in zone us-central1-b: - $ gcloud compute tpus locations describe zone=us-central1-b + $ gcloud compute tpus locations describe us-central1-b POSITIONAL ARGUMENTS Location resource - The Cloud TPU Location you want to describe. This diff --git a/gcloud/config/get b/gcloud/config/get index 7b2eb1b45..802e38207 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -648,6 +648,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/config/help b/gcloud/config/help index d22aa5f29..3573a4160 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -680,6 +680,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/config/list b/gcloud/config/list index bd62c98e4..26fec789d 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -692,6 +692,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/config/set b/gcloud/config/set index 8672b2677..dcd47d5c1 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -695,6 +695,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/config/unset b/gcloud/config/unset index 41d44ab10..aab6c6f33 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -656,6 +656,12 @@ AVAILABLE PROPERTIES SERVICE_ACCOUNT_2. SERVICE_ACCOUNT_1 is the impersonated service account and SERVICE_ACCOUNT_2 is the delegate. + login_config_file + Sets the created login configuration file in + auth/login_config_file. Calling gcloud auth login will + automatically use this login configuration unless it is explicitly + unset. + service_account_disable_id_token_refresh If True, disable ID token refresh for service account. diff --git a/gcloud/firebase/test/android/run b/gcloud/firebase/test/android/run index 103f642fb..7496d789d 100644 --- a/gcloud/firebase/test/android/run +++ b/gcloud/firebase/test/android/run @@ -109,6 +109,12 @@ EXAMPLES executions, but only the subset of executions with valid dimension combinations will actually run your tests. + To help you identify and locate your test matrix in the Firebase console, + run: + + $ gcloud firebase test android run --app=APP_APK \ + --client-details=matrixLabel="Example matrix label" + Controlling Results Storage By default, Firebase Test Lab stores detailed test results for a limited diff --git a/gcloud/firebase/test/ios/run b/gcloud/firebase/test/ios/run index 85415e796..32266a613 100644 --- a/gcloud/firebase/test/ios/run +++ b/gcloud/firebase/test/ios/run @@ -31,12 +31,6 @@ DESCRIPTION for more information about argument files. EXAMPLES - To help you identify and locate your test matrix in the Firebase console, - run: - - $ gcloud firebase test ios run --test=XCTEST_ZIP \ - --client-details=matrixLabel="Example matrix label" - To invoke an XCTest lasting up to five minutes against the default device environment, run: @@ -59,6 +53,12 @@ EXAMPLES $ gcloud firebase test ios run --test=XCTEST_ZIP \ --xcode-version=9.4.1 + To help you identify and locate your test matrix in the Firebase console, + run: + + $ gcloud firebase test ios run --test=XCTEST_ZIP \ + --client-details=matrixLabel="Example matrix label" + All test arguments for a given test may alternatively be stored in an argument group within a YAML-formatted argument file. The ARG_FILE may contain one or more named argument groups, and argument groups may be diff --git a/gcloud/iam/workforce-pools/create-login-config b/gcloud/iam/workforce-pools/create-login-config new file mode 100644 index 000000000..2955d03f4 --- /dev/null +++ b/gcloud/iam/workforce-pools/create-login-config @@ -0,0 +1,50 @@ +NAME + gcloud iam workforce-pools create-login-config - create a login + configuration file to enable sign-in via a web-based authorization flow + using Workforce Identity Federation + +SYNOPSIS + gcloud iam workforce-pools create-login-config AUDIENCE + --output-file=OUTPUT_FILE [--activate] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command creates a configuration file to enable browser based + third-party sign in with Workforce Identity Federation through gcloud auth + login --login-config=/path/to/config.json. + +EXAMPLES + To create a login configuration for your project, run: + + $ gcloud iam workforce-pools create-login-config \ + locations/global/workforcePools/$WORKFORCE_POOL_ID/providers/\ + $PROVIDER_ID --output-file=login-config.json + +POSITIONAL ARGUMENTS + AUDIENCE + Workforce pool provider resource name. + +REQUIRED FLAGS + --output-file=OUTPUT_FILE + Location to store the generated login configuration file. + +OPTIONAL FLAGS + --activate + Sets the property auth/login_config_file to the created login + configuration file. Calling gcloud auth login will automatically use + this login configuration unless it is explicitly unset. + +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 iam workforce-pools create-login-config + + $ gcloud beta iam workforce-pools create-login-config + diff --git a/gcloud/iam/workforce-pools/help b/gcloud/iam/workforce-pools/help index 8e9ad4b11..fe67f672f 100644 --- a/gcloud/iam/workforce-pools/help +++ b/gcloud/iam/workforce-pools/help @@ -34,6 +34,10 @@ COMMANDS create-cred-config Create a configuration file for generated credentials. + create-login-config + Create a login configuration file to enable sign-in via a web-based + authorization flow using Workforce Identity Federation. + delete Delete a workforce pool. diff --git a/gcloud/logging/buckets/create b/gcloud/logging/buckets/create index 4b1ad5629..796706623 100644 --- a/gcloud/logging/buckets/create +++ b/gcloud/logging/buckets/create @@ -2,9 +2,9 @@ NAME gcloud logging buckets create - create a bucket SYNOPSIS - gcloud logging buckets create BUCKET_ID --location=LOCATION + gcloud logging buckets create BUCKET_ID --location=LOCATION [--async] [--cmek-kms-key-name=CMEK_KMS_KEY_NAME] [--description=DESCRIPTION] - [--index=[KEY=VALUE, ...,...]] + [--enable-analytics] [--index=[KEY=VALUE, ...,...]] [--restricted-fields=[RESTRICTED_FIELD,...]] [--retention-days=RETENTION_DAYS] [GCLOUD_WIDE_FLAG ...] @@ -36,6 +36,11 @@ EXAMPLES $ gcloud logging buckets create my-bucket --location=us-central1 \ --cmek-kms-key-name=CMEK_KMS_KEY_NAME + To asynchronously create a bucket enrolled into Log Analytics, run: + + $ gcloud logging buckets create my-bucket --location=global \ + --async --enable-analytics + POSITIONAL ARGUMENTS BUCKET_ID ID of the bucket to create. @@ -46,12 +51,20 @@ REQUIRED FLAGS location cannot be changed. OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + --cmek-kms-key-name=CMEK_KMS_KEY_NAME A valid kms_key_name will enable CMEK for the bucket. --description=DESCRIPTION A textual description for the bucket. + --enable-analytics + Whether to opt the bucket into Log Analytics. Once opted in, the bucket + cannot be opted out of Log Analytics. + --index=[KEY=VALUE, ...,...] Specify an index to be added to the log bucket. This flag can be repeated. The fieldPath and type attributes are required. For example: diff --git a/gcloud/logging/buckets/update b/gcloud/logging/buckets/update index 79cf26ac6..760329270 100644 --- a/gcloud/logging/buckets/update +++ b/gcloud/logging/buckets/update @@ -3,9 +3,9 @@ NAME SYNOPSIS gcloud logging buckets update BUCKET_ID --location=LOCATION - [--add-index=[KEY=VALUE, ...,...]] [--clear-indexes] + [--add-index=[KEY=VALUE, ...,...]] [--async] [--clear-indexes] [--cmek-kms-key-name=CMEK_KMS_KEY_NAME] [--description=DESCRIPTION] - [--locked] [--remove-indexes=[FIELD PATH,...]] + [--enable-analytics] [--locked] [--remove-indexes=[FIELD PATH,...]] [--restricted-fields=[RESTRICTED_FIELD,...]] [--retention-days=RETENTION_DAYS] [--update-index=[KEY=VALUE, ...,...]] [GCLOUD_WIDE_FLAG ...] @@ -44,6 +44,11 @@ EXAMPLES $ gcloud logging buckets update my-bucket --location=global \ --cmek-kms-key-name=CMEK_KEY_NAME + To asynchronously enroll a bucket in your project into Log Analytics, run: + + $ gcloud logging buckets update my-bucket --location=global \ + --async --enable-analytics + POSITIONAL ARGUMENTS BUCKET_ID The id of the bucket to update. @@ -69,6 +74,10 @@ OPTIONAL FLAGS The type of data in this index. For example: INDEX_TYPE_STRING Supported types are strings and integers. + --async + Return immediately, without waiting for the operation in progress to + complete. + --clear-indexes Remove all logging indexes from the bucket. @@ -78,6 +87,10 @@ OPTIONAL FLAGS --description=DESCRIPTION A new description for the bucket. + --enable-analytics + Whether to opt the bucket into Log Analytics. Once opted in, the bucket + cannot be opted out of Log Analytics. + --locked Lock the bucket and prevent it from being modified or deleted (unless it is empty). diff --git a/gcloud/logging/help b/gcloud/logging/help index df2463ea9..5ccf4add1 100644 --- a/gcloud/logging/help +++ b/gcloud/logging/help @@ -18,6 +18,9 @@ GROUPS buckets Manage Cloud Logging buckets. + links + Manage log links. + locations Query Cloud Logging locations. diff --git a/gcloud/logging/links/create b/gcloud/logging/links/create new file mode 100644 index 000000000..e62c76a08 --- /dev/null +++ b/gcloud/logging/links/create @@ -0,0 +1,78 @@ +NAME + gcloud logging links create - create a link on an analytics log bucket + +SYNOPSIS + gcloud logging links create LINK_ID --bucket=BUCKET --location=LOCATION + [--async] [--description=DESCRIPTION] + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a link for a log bucket. + +EXAMPLES + To create a link in a project, run: + + $ gcloud logging links create my-link --bucket=my-bucket \ + --location=global + +POSITIONAL ARGUMENTS + LINK_ID + ID of the link to create. + +REQUIRED FLAGS + --bucket=BUCKET + ID of the bucket that will hold the link + + --location=LOCATION + Location of the bucket that will hold the link. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A textual description for the link. + + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the link to create. + + --folder=FOLDER_ID + Folder of the link to create. + + --organization=ORGANIZATION_ID + Organization of the link to create. + + --project=PROJECT_ID + Project of the link to create. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha logging links create + + $ gcloud beta logging links create + diff --git a/gcloud/logging/links/delete b/gcloud/logging/links/delete new file mode 100644 index 000000000..ebb46dd16 --- /dev/null +++ b/gcloud/logging/links/delete @@ -0,0 +1,75 @@ +NAME + gcloud logging links delete - delete a link + +SYNOPSIS + gcloud logging links delete LINK_ID --bucket=BUCKET --location=LOCATION + [--async] + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Deletes a bucket's link. + +EXAMPLES + To delete a bucket's link, run: + + $ gcloud logging links delete my-link --bucket=my-bucket \ + --location=global + +POSITIONAL ARGUMENTS + LINK_ID + ID of the link to delete. + +REQUIRED FLAGS + --bucket=BUCKET + ID of bucket + + --location=LOCATION + Location of the bucket. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the link to delete. + + --folder=FOLDER_ID + Folder of the link to delete. + + --organization=ORGANIZATION_ID + Organization of the link to delete. + + --project=PROJECT_ID + Project of the link to delete. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha logging links delete + + $ gcloud beta logging links delete + diff --git a/gcloud/logging/links/describe b/gcloud/logging/links/describe new file mode 100644 index 000000000..175e6fac1 --- /dev/null +++ b/gcloud/logging/links/describe @@ -0,0 +1,70 @@ +NAME + gcloud logging links describe - display information about a link + +SYNOPSIS + gcloud logging links describe LINK_ID --bucket=BUCKET --location=LOCATION + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Displays information about a link. + +EXAMPLES + To describe a link in a project, run: + + $ gcloud logging links describe my-link --bucket=my-bucket \ + --location=global + +POSITIONAL ARGUMENTS + LINK_ID + Id of the link to describe. + +REQUIRED FLAGS + --bucket=BUCKET + ID of bucket + + --location=LOCATION + Location of the bucket. + +OPTIONAL FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the link to describe. + + --folder=FOLDER_ID + Folder of the link to describe. + + --organization=ORGANIZATION_ID + Organization of the link to describe. + + --project=PROJECT_ID + Project of the link to describe. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha logging links describe + + $ gcloud beta logging links describe + diff --git a/gcloud/logging/links/help b/gcloud/logging/links/help new file mode 100644 index 000000000..d579814bd --- /dev/null +++ b/gcloud/logging/links/help @@ -0,0 +1,37 @@ +NAME + gcloud logging links - manage log links + +SYNOPSIS + gcloud logging links COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing links. A log link represents a linked BigQuery + dataset that contains log data for the link's parent log bucket. + +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 link on an analytics log bucket. + + delete + Delete a link. + + describe + Display information about a link. + + list + List created links on the specified bucket. + +NOTES + These variants are also available: + + $ gcloud alpha logging links + + $ gcloud beta logging links + diff --git a/gcloud/logging/links/list b/gcloud/logging/links/list new file mode 100644 index 000000000..dbe07acae --- /dev/null +++ b/gcloud/logging/links/list @@ -0,0 +1,98 @@ +NAME + gcloud logging links list - list created links on the specified bucket + +SYNOPSIS + gcloud logging links list --bucket=BUCKET --location=LOCATION + [--billing-account=BILLING_ACCOUNT_ID | --folder=FOLDER_ID + | --organization=ORGANIZATION_ID | --project=PROJECT_ID] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Lists the links created for a bucket. + +EXAMPLES + To list the links created for a bucket, run: + + $ gcloud logging links list + +REQUIRED FLAGS + --bucket=BUCKET + ID of bucket + + --location=LOCATION + Location of the specified bucket + +FLAGS + At most one of these can be specified: + + --billing-account=BILLING_ACCOUNT_ID + Billing account of the links to list. + + --folder=FOLDER_ID + Folder of the links to list. + + --organization=ORGANIZATION_ID + Organization of the links to list. + + --project=PROJECT_ID + Project of the links to list. + + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha logging links list + + $ gcloud beta logging links list + diff --git a/gcloud/ml-engine/jobs/submit/training b/gcloud/ml-engine/jobs/submit/training index 2b8a7985d..8056a011e 100644 --- a/gcloud/ml-engine/jobs/submit/training +++ b/gcloud/ml-engine/jobs/submit/training @@ -146,7 +146,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. @@ -186,7 +186,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. @@ -304,7 +304,7 @@ FLAGS type Type of the accelerator. Choices are - nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod + nvidia-tesla-a100,nvidia-tesla-k80,nvidia-tesla-p100,nvidia-tesla-p4,nvidia-tesla-t4,nvidia-tesla-v100,tpu-v2,tpu-v2-pod,tpu-v3,tpu-v3-pod,tpu-v4-pod count Number of accelerators to attach to each machine running the job. diff --git a/gcloud/privateca/certificates/create b/gcloud/privateca/certificates/create index 854aec40d..d4b6a32ca 100644 --- a/gcloud/privateca/certificates/create +++ b/gcloud/privateca/certificates/create @@ -16,8 +16,16 @@ SYNOPSIS : --use-preset-profile=USE_PRESET_PROFILE | --extended-key-usages=[EXTENDED_KEY_USAGES,...] --is-ca-cert --key-usages=[KEY_USAGES,...] --max-chain-length=MAX_CHAIN_LENGTH - | --unconstrained-chain-length]) [--ca=CA] [--labels=[KEY=VALUE,...]] - [--validity=VALIDITY; default="P30D"] + | --unconstrained-chain-length --no-name-constraints-critical + --name-excluded-dns=[NAME_EXCLUDED_DNS,...] + --name-excluded-email=[NAME_EXCLUDED_EMAIL,...] + --name-excluded-ip=[NAME_EXCLUDED_IP,...] + --name-excluded-uri=[NAME_EXCLUDED_URI,...] + --name-permitted-dns=[NAME_PERMITTED_DNS,...] + --name-permitted-email=[NAME_PERMITTED_EMAIL,...] + --name-permitted-ip=[NAME_PERMITTED_IP,...] + --name-permitted-uri=[NAME_PERMITTED_URI,...]]) [--ca=CA] + [--labels=[KEY=VALUE,...]] [--validity=VALIDITY; default="P30D"] [--template=TEMPLATE : --template-location=TEMPLATE_LOCATION] [GCLOUD_WIDE_FLAG ...] @@ -237,6 +245,68 @@ REQUIRED FLAGS neither --use-preset-profile nor --max-chain-length are provided. + The x509 name constraints configurations + + --name-constraints-critical + Indicates whether or not name constraints are marked as + critical. Name constraints are considered critical unless + explicitly set to false. Enabled by default, use + --no-name-constraints-critical to disable. + + --name-excluded-dns=[NAME_EXCLUDED_DNS,...] + One or more comma-separated DNS names which are excluded from + being issued certificates. Any DNS name that can be constructed + by simply adding zero or more labels to the left-hand side of + the name satisfies the name constraint. For example, + example.com, www.example.com, www.sub.example.com would satisfy + example.com, while example1.com does not. + + --name-excluded-email=[NAME_EXCLUDED_EMAIL,...] + One or more comma-separated emails which are excluded from + being issued certificates. The value can be a particular email + address, a hostname to indicate all email addresses on that + host or a domain with a leading period (e.g. .example.com) to + indicate all email addresses in that domain. + + --name-excluded-ip=[NAME_EXCLUDED_IP,...] + One or more comma-separated IP ranges which are excluded from + being issued certificates. For IPv4 addresses, the ranges are + expressed using CIDR notation as specified in RFC 4632. For + IPv6 addresses, the ranges are expressed in similar encoding as + IPv4 + + --name-excluded-uri=[NAME_EXCLUDED_URI,...] + One or more comma-separated URIs which are excluded from being + issued certificates. The value can be a hostname or a domain + with a leading period (like .example.com) + + --name-permitted-dns=[NAME_PERMITTED_DNS,...] + One or more comma-separated DNS names which are permitted to be + issued certificates. Any DNS name that can be constructed by + simply adding zero or more labels to the left-hand side of the + name satisfies the name constraint. For example, example.com, + www.example.com, www.sub.example.com would satisfy example.com, + while example1.com does not. + + --name-permitted-email=[NAME_PERMITTED_EMAIL,...] + One or more comma-separated email addresses which are permitted + to be issued certificates. The value can be a particular email + address, a hostname to indicate all email addresses on that + host or a domain with a leading period (e.g. .example.com) to + indicate all email addresses in that domain. + + --name-permitted-ip=[NAME_PERMITTED_IP,...] + One or more comma-separated IP ranges which are permitted to be + issued certificates. For IPv4 addresses, the ranges are + expressed using CIDR notation as specified in RFC 4632. For + IPv6 addresses, the ranges are expressed in similar encoding as + IPv4 + + --name-permitted-uri=[NAME_PERMITTED_URI,...] + One or more comma-separated URIs which are permitted to be + issued certificates. The value can be a hostname or a domain + with a leading period (like .example.com) + OPTIONAL FLAGS --ca=CA The name of an existing certificate authority to use for issuing the diff --git a/gcloud/privateca/roots/create b/gcloud/privateca/roots/create index e2d7702b5..147657725 100644 --- a/gcloud/privateca/roots/create +++ b/gcloud/privateca/roots/create @@ -16,7 +16,15 @@ SYNOPSIS [--use-preset-profile=USE_PRESET_PROFILE | --extended-key-usages=[EXTENDED_KEY_USAGES,...] --key-usages=[KEY_USAGES,...] --max-chain-length=MAX_CHAIN_LENGTH - | --unconstrained-chain-length] [GCLOUD_WIDE_FLAG ...] + | --unconstrained-chain-length --no-name-constraints-critical + --name-excluded-dns=[NAME_EXCLUDED_DNS,...] + --name-excluded-email=[NAME_EXCLUDED_EMAIL,...] + --name-excluded-ip=[NAME_EXCLUDED_IP,...] + --name-excluded-uri=[NAME_EXCLUDED_URI,...] + --name-permitted-dns=[NAME_PERMITTED_DNS,...] + --name-permitted-email=[NAME_PERMITTED_EMAIL,...] + --name-permitted-ip=[NAME_PERMITTED_IP,...] + --name-permitted-uri=[NAME_PERMITTED_URI,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION TIP: Consider setting a project lien @@ -230,6 +238,66 @@ FLAGS newly issued CA certificate. This can only be provided if neither --use-preset-profile nor --max-chain-length are provided. + The x509 name constraints configurations + + --name-constraints-critical + Indicates whether or not name constraints are marked as critical. + Name constraints are considered critical unless explicitly set to + false. Enabled by default, use --no-name-constraints-critical to + disable. + + --name-excluded-dns=[NAME_EXCLUDED_DNS,...] + One or more comma-separated DNS names which are excluded from being + issued certificates. Any DNS name that can be constructed by simply + adding zero or more labels to the left-hand side of the name + satisfies the name constraint. For example, example.com, + www.example.com, www.sub.example.com would satisfy example.com, + while example1.com does not. + + --name-excluded-email=[NAME_EXCLUDED_EMAIL,...] + One or more comma-separated emails which are excluded from being + issued certificates. The value can be a particular email address, a + hostname to indicate all email addresses on that host or a domain + with a leading period (e.g. .example.com) to indicate all email + addresses in that domain. + + --name-excluded-ip=[NAME_EXCLUDED_IP,...] + One or more comma-separated IP ranges which are excluded from being + issued certificates. For IPv4 addresses, the ranges are expressed + using CIDR notation as specified in RFC 4632. For IPv6 addresses, + the ranges are expressed in similar encoding as IPv4 + + --name-excluded-uri=[NAME_EXCLUDED_URI,...] + One or more comma-separated URIs which are excluded from being + issued certificates. The value can be a hostname or a domain with a + leading period (like .example.com) + + --name-permitted-dns=[NAME_PERMITTED_DNS,...] + One or more comma-separated DNS names which are permitted to be + issued certificates. Any DNS name that can be constructed by simply + adding zero or more labels to the left-hand side of the name + satisfies the name constraint. For example, example.com, + www.example.com, www.sub.example.com would satisfy example.com, + while example1.com does not. + + --name-permitted-email=[NAME_PERMITTED_EMAIL,...] + One or more comma-separated email addresses which are permitted to + be issued certificates. The value can be a particular email + address, a hostname to indicate all email addresses on that host or + a domain with a leading period (e.g. .example.com) to indicate all + email addresses in that domain. + + --name-permitted-ip=[NAME_PERMITTED_IP,...] + One or more comma-separated IP ranges which are permitted to be + issued certificates. For IPv4 addresses, the ranges are expressed + using CIDR notation as specified in RFC 4632. For IPv6 addresses, + the ranges are expressed in similar encoding as IPv4 + + --name-permitted-uri=[NAME_PERMITTED_URI,...] + One or more comma-separated URIs which are permitted to be issued + certificates. The value can be a hostname or a domain with a + leading period (like .example.com) + 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/privateca/subordinates/create b/gcloud/privateca/subordinates/create index 7b643c3e3..c396e4b48 100644 --- a/gcloud/privateca/subordinates/create +++ b/gcloud/privateca/subordinates/create @@ -20,7 +20,15 @@ SYNOPSIS [--use-preset-profile=USE_PRESET_PROFILE | --extended-key-usages=[EXTENDED_KEY_USAGES,...] --key-usages=[KEY_USAGES,...] --max-chain-length=MAX_CHAIN_LENGTH - | --unconstrained-chain-length] [GCLOUD_WIDE_FLAG ...] + | --unconstrained-chain-length --no-name-constraints-critical + --name-excluded-dns=[NAME_EXCLUDED_DNS,...] + --name-excluded-email=[NAME_EXCLUDED_EMAIL,...] + --name-excluded-ip=[NAME_EXCLUDED_IP,...] + --name-excluded-uri=[NAME_EXCLUDED_URI,...] + --name-permitted-dns=[NAME_PERMITTED_DNS,...] + --name-permitted-email=[NAME_PERMITTED_EMAIL,...] + --name-permitted-ip=[NAME_PERMITTED_IP,...] + --name-permitted-uri=[NAME_PERMITTED_URI,...]] [GCLOUD_WIDE_FLAG ...] EXAMPLES To create a subordinate CA named 'server-tls-1' whose issuer is on Private @@ -295,6 +303,66 @@ OPTIONAL FLAGS newly issued CA certificate. This can only be provided if neither --use-preset-profile nor --max-chain-length are provided. + The x509 name constraints configurations + + --name-constraints-critical + Indicates whether or not name constraints are marked as critical. + Name constraints are considered critical unless explicitly set to + false. Enabled by default, use --no-name-constraints-critical to + disable. + + --name-excluded-dns=[NAME_EXCLUDED_DNS,...] + One or more comma-separated DNS names which are excluded from being + issued certificates. Any DNS name that can be constructed by simply + adding zero or more labels to the left-hand side of the name + satisfies the name constraint. For example, example.com, + www.example.com, www.sub.example.com would satisfy example.com, + while example1.com does not. + + --name-excluded-email=[NAME_EXCLUDED_EMAIL,...] + One or more comma-separated emails which are excluded from being + issued certificates. The value can be a particular email address, a + hostname to indicate all email addresses on that host or a domain + with a leading period (e.g. .example.com) to indicate all email + addresses in that domain. + + --name-excluded-ip=[NAME_EXCLUDED_IP,...] + One or more comma-separated IP ranges which are excluded from being + issued certificates. For IPv4 addresses, the ranges are expressed + using CIDR notation as specified in RFC 4632. For IPv6 addresses, + the ranges are expressed in similar encoding as IPv4 + + --name-excluded-uri=[NAME_EXCLUDED_URI,...] + One or more comma-separated URIs which are excluded from being + issued certificates. The value can be a hostname or a domain with a + leading period (like .example.com) + + --name-permitted-dns=[NAME_PERMITTED_DNS,...] + One or more comma-separated DNS names which are permitted to be + issued certificates. Any DNS name that can be constructed by simply + adding zero or more labels to the left-hand side of the name + satisfies the name constraint. For example, example.com, + www.example.com, www.sub.example.com would satisfy example.com, + while example1.com does not. + + --name-permitted-email=[NAME_PERMITTED_EMAIL,...] + One or more comma-separated email addresses which are permitted to + be issued certificates. The value can be a particular email + address, a hostname to indicate all email addresses on that host or + a domain with a leading period (e.g. .example.com) to indicate all + email addresses in that domain. + + --name-permitted-ip=[NAME_PERMITTED_IP,...] + One or more comma-separated IP ranges which are permitted to be + issued certificates. For IPv4 addresses, the ranges are expressed + using CIDR notation as specified in RFC 4632. For IPv6 addresses, + the ranges are expressed in similar encoding as IPv4 + + --name-permitted-uri=[NAME_PERMITTED_URI,...] + One or more comma-separated URIs which are permitted to be issued + certificates. The value can be a hostname or a domain with a + leading period (like .example.com) + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/storage/mv b/gcloud/storage/mv index 670e01ad7..88ba45039 100644 --- a/gcloud/storage/mv +++ b/gcloud/storage/mv @@ -42,8 +42,7 @@ DESCRIPTION under gs://my_bucket/oldprefix to be under gs://my_bucket/newprefix, otherwise preserving the naming structure: - $ gcloud storage mv mv gs://my_bucket/oldprefix \ - gs://my_bucket/newprefix + $ gcloud storage mv gs://my_bucket/oldprefix gs://my_bucket/newprefix Note that when using mv to rename groups of objects with a common prefix, you cannot specify the source URL using wildcards; you must spell out the