diff --git a/gcloud/_version b/gcloud/_version index 7729c7c9c..d4f2ea179 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 459.0.0 -alpha 2024.01.06 -beta 2024.01.06 +Google Cloud SDK 460.0.0 +alpha 2024.01.12 +beta 2024.01.12 bq 2.0.101 bundled-python3-unix 3.11.6 -core 2024.01.06 +core 2024.01.12 gcloud-crc32c 1.0.0 gsutil 5.27 diff --git a/gcloud/alpha/billing/budgets/create b/gcloud/alpha/billing/budgets/create index 93c553426..f9ef6ff0c 100644 --- a/gcloud/alpha/billing/budgets/create +++ b/gcloud/alpha/billing/budgets/create @@ -15,6 +15,7 @@ SYNOPSIS [--filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...]] [--filter-services=[FILTER_SERVICES,...]] [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]] + [--ownership-scope=OWNERSHIP_SCOPE] [--threshold-rule=[basis=BASIS],[percent=PERCENT]] [--calendar-period=CALENDAR_PERIOD | [--start-date=START_DATE : --end-date=END_DATE]] @@ -133,6 +134,20 @@ OPTIONAL FLAGS include usage from the parent account and all subaccounts, if they exist. + --ownership-scope=OWNERSHIP_SCOPE + Sets the ownership scope of the budget. The ownership scope and users' + IAM permissions determine who has full access to the budget's data. + + Must be one of: 'ALL_USERS' or 'BILLING_ACCOUNT'. Use 'ALL_USERS' to + allow billing account- level users and project-level users to have full + access to the budget (if the users have the required IAM permissions). + Use 'BILLING_ACCOUNT' to allow only billing account-level users to have + full access to the budget. Project-level users will have read-only + access, even if they have the required IAM permissions. + + OWNERSHIP_SCOPE must be one of: all-users, billing-account, + ownership-scope-unspecified. + --threshold-rule=[basis=BASIS],[percent=PERCENT] Rule that triggers alerts (notifications of thresholds being crossed) when spend exceeds the specified percentages of the budget. This flag diff --git a/gcloud/alpha/billing/budgets/update b/gcloud/alpha/billing/budgets/update index abebb0284..279756416 100644 --- a/gcloud/alpha/billing/budgets/update +++ b/gcloud/alpha/billing/budgets/update @@ -14,6 +14,7 @@ SYNOPSIS [--filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...]] [--filter-services=[FILTER_SERVICES,...]] [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]] + [--ownership-scope=OWNERSHIP_SCOPE] [--budget-amount=BUDGET_AMOUNT | --last-period-amount] [--calendar-period=CALENDAR_PERIOD | [--start-date=START_DATE : --end-date=END_DATE]] @@ -134,6 +135,20 @@ FLAGS include usage from the parent account and all subaccounts, if they exist. + --ownership-scope=OWNERSHIP_SCOPE + Sets the ownership scope of the budget. The ownership scope and users' + IAM permissions determine who has full access to the budget's data. + + Must be one of: 'ALL_USERS' or 'BILLING_ACCOUNT'. Use 'ALL_USERS' to + allow billing account- level users and project-level users to have full + access to the budget (if the users have the required IAM permissions). + Use 'BILLING_ACCOUNT' to allow only billing account-level users to have + full access to the budget. Project-level users will have read-only + access, even if they have the required IAM permissions. + + OWNERSHIP_SCOPE must be one of: all-users, billing-account, + ownership-scope-unspecified. + At most one of these can be specified: --budget-amount=BUDGET_AMOUNT diff --git a/gcloud/alpha/builds/worker-pools/describe b/gcloud/alpha/builds/worker-pools/describe index b7a1b4d7b..430c6979b 100644 --- a/gcloud/alpha/builds/worker-pools/describe +++ b/gcloud/alpha/builds/worker-pools/describe @@ -1,17 +1,17 @@ NAME - gcloud alpha builds worker-pools describe - describe a private or hybrid - worker pool used by Cloud Build + gcloud alpha builds worker-pools describe - describe a private worker pool + used by Cloud Build SYNOPSIS gcloud alpha builds worker-pools describe WORKER_POOL --region=REGION [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe a private or hybrid worker pool used by Cloud Build. + (ALPHA) Describe a private worker pool used by Cloud Build. EXAMPLES - To get information about a private or hybrid worker pool named wp1 in - region us-central1, run: + To get information about a worker pool named wp1 in region us-central1, + run: $ gcloud alpha builds worker-pools describe wp1 --region=us-central1 diff --git a/gcloud/alpha/builds/worker-pools/help b/gcloud/alpha/builds/worker-pools/help index e797ff8f3..d920a4c61 100644 --- a/gcloud/alpha/builds/worker-pools/help +++ b/gcloud/alpha/builds/worker-pools/help @@ -23,11 +23,10 @@ COMMANDS (ALPHA) Delete a private worker pool from Google Cloud Build. describe - (ALPHA) Describe a private or hybrid worker pool used by Cloud Build. + (ALPHA) Describe a private worker pool used by Cloud Build. list - (ALPHA) List all private and hybrid worker pools in a Google Cloud - project. + (ALPHA) List all private worker pools in a Google Cloud project. update (ALPHA) Update a private pool used by Cloud Build. diff --git a/gcloud/alpha/builds/worker-pools/list b/gcloud/alpha/builds/worker-pools/list index 8dfdbbc3a..d978d8950 100644 --- a/gcloud/alpha/builds/worker-pools/list +++ b/gcloud/alpha/builds/worker-pools/list @@ -1,6 +1,6 @@ NAME - gcloud alpha builds worker-pools list - list all private and hybrid worker - pools in a Google Cloud project + gcloud alpha builds worker-pools list - list all private worker pools in a + Google Cloud project SYNOPSIS gcloud alpha builds worker-pools list --region=REGION [--filter=EXPRESSION] @@ -8,20 +8,13 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List all private and hybrid worker pools in a Google Cloud project. + (ALPHA) List all private worker pools in a Google Cloud project. EXAMPLES - To fetch a list of all private and hybrid worker pools running in region - us-central1, run: + To fetch a list of worker pools running in region us-central1, run: $ gcloud alpha builds worker-pools list --region=us-central1 - To fetch a list of only hybrid worker pools running in region us-central1, - run: - - $ gcloud alpha builds worker-pools list --region=us-central1 \ - --filter="type:Hybrid" - REQUIRED FLAGS --region=REGION The Cloud region to list worker pools in. diff --git a/gcloud/alpha/compute/instance-groups/managed/create b/gcloud/alpha/compute/instance-groups/managed/create index 5fa564972..41dbf79ff 100644 --- a/gcloud/alpha/compute/instance-groups/managed/create +++ b/gcloud/alpha/compute/instance-groups/managed/create @@ -9,6 +9,7 @@ SYNOPSIS [--description=DESCRIPTION] [--[no-]force-update-on-repair] [--initial-delay=INITIAL_DELAY] [--instance-redistribution-type=TYPE] [--list-managed-instances-results=MODE] + [--resource-manager-tags=[KEY=VALUE,...]] [--standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY] [--standby-policy-mode=STANDBY_POLICY_MODE] [--stateful-disk=[auto-delete=AUTO-DELETE],[device-name=DEVICE-NAME]] @@ -143,6 +144,10 @@ OPTIONAL FLAGS Pagination is enabled for the group's listManagedInstances API method. maxResults and pageToken query parameters are respected. + --resource-manager-tags=[KEY=VALUE,...] + Specifies a list of resource manager tags to apply to the managed + instance group. + --standby-policy-initial-delay=STANDBY_POLICY_INITIAL_DELAY Specifies the number of seconds that the MIG should wait before suspending or stopping a VM. The initial delay gives the initialization diff --git a/gcloud/alpha/compute/instance-groups/managed/help b/gcloud/alpha/compute/instance-groups/managed/help index c6107c470..7969bb14d 100644 --- a/gcloud/alpha/compute/instance-groups/managed/help +++ b/gcloud/alpha/compute/instance-groups/managed/help @@ -76,7 +76,7 @@ COMMANDS (ALPHA) Set managed instance group size. resume-instances - (ALPHA) Resume instances owned by a managed instance group. + (ALPHA) Resume the suspended instances in a managed instance group. set-autohealing (ALPHA) (DEPRECATED) Set autohealing policy for managed instance group. @@ -97,7 +97,7 @@ COMMANDS (ALPHA) Set target pools of managed instance group. start-instances - (ALPHA) Start instances owned by a managed instance group. + (ALPHA) Start the stopped instances in a managed instance group. stop-autoscaling (ALPHA) Stop autoscaling a managed instance group. diff --git a/gcloud/alpha/compute/instance-groups/managed/resume-instances b/gcloud/alpha/compute/instance-groups/managed/resume-instances index a320c37af..08e39be75 100644 --- a/gcloud/alpha/compute/instance-groups/managed/resume-instances +++ b/gcloud/alpha/compute/instance-groups/managed/resume-instances @@ -1,6 +1,6 @@ NAME - gcloud alpha compute instance-groups managed resume-instances - resume - instances owned by a managed instance group + gcloud alpha compute instance-groups managed resume-instances - resume the + suspended instances in a managed instance group SYNOPSIS gcloud alpha compute instance-groups managed resume-instances NAME @@ -18,6 +18,14 @@ DESCRIPTION regional groups when the gcloud command-line tool wasn't able to resolve the zone from the instance name. +EXAMPLES + To resume an instance from a managed instance group in the us-central1-a + zone, run: + + $ gcloud alpha compute instance-groups managed resume-instances \ + example-managed-instance-group --zone=us-central1-a \ + --instances=example-instance + POSITIONAL ARGUMENTS NAME Name of the managed instance group to operate on. @@ -63,5 +71,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 compute instance-groups managed resume-instances diff --git a/gcloud/alpha/compute/instance-groups/managed/start-instances b/gcloud/alpha/compute/instance-groups/managed/start-instances index d19fe4751..7f25e83a7 100644 --- a/gcloud/alpha/compute/instance-groups/managed/start-instances +++ b/gcloud/alpha/compute/instance-groups/managed/start-instances @@ -1,6 +1,6 @@ NAME - gcloud alpha compute instance-groups managed start-instances - start - instances owned by a managed instance group + gcloud alpha compute instance-groups managed start-instances - start the + stopped instances in a managed instance group SYNOPSIS gcloud alpha compute instance-groups managed start-instances NAME @@ -17,6 +17,14 @@ DESCRIPTION regional groups when the gcloud command-line tool wasn't able to resolve the zone from the instance name. +EXAMPLES + To start an instance from a managed instance group in the us-central1-a + zone, run: + + $ gcloud alpha compute instance-groups managed start-instances \ + example-managed-instance-group --zone=us-central1-a \ + --instances=example-instance + POSITIONAL ARGUMENTS NAME Name of the managed instance group to operate on. @@ -62,5 +70,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 compute instance-groups managed start-instances diff --git a/gcloud/alpha/compute/instance-groups/managed/stop-instances b/gcloud/alpha/compute/instance-groups/managed/stop-instances index 30ce899aa..cd71dde28 100644 --- a/gcloud/alpha/compute/instance-groups/managed/stop-instances +++ b/gcloud/alpha/compute/instance-groups/managed/stop-instances @@ -11,6 +11,14 @@ DESCRIPTION (ALPHA) gcloud alpha compute instance-groups managed stop-instances stops one or more instances from a managed instance group +EXAMPLES + To stop an instance from a managed instance group in the us-central1-a + zone, run: + + $ gcloud alpha compute instance-groups managed stop-instances \ + example-managed-instance-group --zone=us-central1-a \ + --instances=example-instance + POSITIONAL ARGUMENTS NAME Name of the managed instance group to operate on. @@ -60,5 +68,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 compute instance-groups managed stop-instances diff --git a/gcloud/alpha/compute/instance-groups/managed/suspend-instances b/gcloud/alpha/compute/instance-groups/managed/suspend-instances index 436f94ba6..12bec541d 100644 --- a/gcloud/alpha/compute/instance-groups/managed/suspend-instances +++ b/gcloud/alpha/compute/instance-groups/managed/suspend-instances @@ -18,6 +18,14 @@ DESCRIPTION regional groups when the gcloud command-line tool wasn't able to resolve the zone from the instance name. +EXAMPLES + To suspend an instance from a managed instance group in the us-central1-a + zone, run: + + $ gcloud alpha compute instance-groups managed suspend-instances \ + example-managed-instance-group --zone=us-central1-a \ + --instances=example-instance + POSITIONAL ARGUMENTS NAME Name of the managed instance group to operate on. @@ -67,5 +75,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 compute instance-groups managed suspend-instances diff --git a/gcloud/alpha/compute/instances/network-interfaces/add b/gcloud/alpha/compute/instances/network-interfaces/add new file mode 100644 index 000000000..ccba5377c --- /dev/null +++ b/gcloud/alpha/compute/instances/network-interfaces/add @@ -0,0 +1,169 @@ +NAME + gcloud alpha compute instances network-interfaces add - add a Compute + Engine virtual machine network interface + +SYNOPSIS + gcloud alpha compute instances network-interfaces add INSTANCE_NAME + [--aliases=ALIASES] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] + [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] + [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] + [--internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH] + [--ipv6-address=IPV6_ADDRESS] [--ipv6-network-tier=IPV6_NETWORK_TIER] + [--ipv6-prefix-length=IPV6_PREFIX_LENGTH] [--network=NETWORK] + [--network-tier=NETWORK_TIER] [--parent-nic-name=PARENT_NIC_NAME] + [--private-network-ip=PRIVATE_NETWORK_IP] [--stack-type=STACK_TYPE] + [--subnetwork=SUBNETWORK] [--vlan=VLAN] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute instances network-interfaces add adds network + interface to a Compute Engine virtual machine. + +POSITIONAL ARGUMENTS + INSTANCE_NAME + Name of the instance to operate on. For details on valid instance + names, refer to the criteria documented under the field 'name' at: + https://cloud.google.com/compute/docs/reference/rest/v1/instances + +FLAGS + --aliases=ALIASES + The IP alias ranges to allocate for this interface. If there are + multiple IP alias ranges, they are separated by semicolons. + + For example: + + --aliases="10.128.1.0/24;range1:/32" + + Each IP alias range consists of a range name and an IP range separated + by a colon, or just the IP range. The range name is the name of the + range within the network interface's subnet from which to allocate an + IP alias range. If unspecified, it defaults to the primary IP range of + the subnet. The IP range can be a CIDR range (e.g. 192.168.100.0/24), a + single IP address (e.g. 192.168.100.1), or a netmask in CIDR format + (e.g. /24). If the IP range is specified by CIDR range or single IP + address, it must belong to the CIDR range specified by the range name + on the subnet. If the IP range is specified by netmask, the IP + allocator will pick an available range with the specified netmask and + allocate it to this network interface. + + --external-ipv6-address=EXTERNAL_IPV6_ADDRESS + Assigns the given external IPv6 address to an instance. The address + must be the first IP in the range. This option is applicable only to + dual-stack instances with stack-type=IPV4_ONLY. + + --external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH + The prefix length of the external IPv6 address range. This flag should + be used together with --external-ipv6-address. Currently only /96 is + supported and the default value is 96. + + --internal-ipv6-address=INTERNAL_IPV6_ADDRESS + Assigns the given internal IPv6 address or range to an instance. The + address must be the first IP address in the range or a /96 IP address + range. This option can only be used on a dual stack instance network + interface. + + --internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH + Optional field that indicates the prefix length of the internal IPv6 + address range, should be used together with + --internal-ipv6-address=fd20::. Only /96 IP address range is supported + and the default value is 96. If not set, then either the prefix length + from --internal-ipv6-address=fd20::/96 will be used or the default + value of 96 will be assigned. + + --ipv6-address=IPV6_ADDRESS + Assigns the given external IPv6 address to an instance. The address + must be the first IP in the range. This option is applicable only to + dual-stack instances with stack-type=IPV4_ONLY. + + --ipv6-network-tier=IPV6_NETWORK_TIER + Specifies the IPv6 network tier that will be used to configure the + instance network interface IPv6 access config. IPV6_NETWORK_TIER must + be (only one value is supported): + + PREMIUM + High quality, Google-grade network tier. + + --ipv6-prefix-length=IPV6_PREFIX_LENGTH + The prefix length of the external IPv6 address range. This flag should + be used together with --ipv6-address. Currently only /96 is supported + and the default value is 96. + + --network=NETWORK + Specifies the network this network interface belongs to. + + --network-tier=NETWORK_TIER + Specifies the network tier that will be used to configure the instance + network interface. NETWORK_TIER must be one of: PREMIUM, STANDARD, + FIXED_STANDARD. The default value is PREMIUM. NETWORK_TIER must be one + of: + + FIXED_STANDARD + Public internet quality with fixed bandwidth. + PREMIUM + High quality, Google-grade network tier. + STANDARD + Public internet quality. + + --parent-nic-name=PARENT_NIC_NAME + Name of the parent network interface of a VLAN based network interface. + If this field is specified, vlan must be set. + + --private-network-ip=PRIVATE_NETWORK_IP + Specifies the RFC1918 IP to assign to the network interface. The IP + should be in the subnet IP range. + + --stack-type=STACK_TYPE + The stack type for the default network interface. Determines if IPv6 is + enabled on the default network interface. STACK_TYPE must be one of: + + IPV4_IPV6 + The network interface can have both IPv4 and IPv6 addresses. + IPV4_ONLY + The network interface will be assigned IPv4 addresses. + + --subnetwork=SUBNETWORK + Specifies the subnetwork this network interface belongs to. + + --vlan=VLAN + VLAN tag of a VLAN based network interface, must be in range from 2 to + 4094 inclusively. This field is mandatory if the parent network + interface name is set. + + --zone=ZONE + Zone of the instance to operate on. If not specified, you might be + prompted to select a zone (interactive mode only). gcloud attempts to + identify the appropriate zone by searching for resources in your + currently active project. If the zone cannot be determined, gcloud + prompts you for a selection with all available Google Cloud Platform + zones. + + To avoid prompting when this flag is omitted, the user can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/instances/network-interfaces/help b/gcloud/alpha/compute/instances/network-interfaces/help index 06284ca2f..2b55c0b38 100644 --- a/gcloud/alpha/compute/instances/network-interfaces/help +++ b/gcloud/alpha/compute/instances/network-interfaces/help @@ -24,6 +24,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add + (ALPHA) Add a Compute Engine virtual machine network interface. + delete (ALPHA) Delete a Compute Engine virtual machine network interface. diff --git a/gcloud/alpha/compute/instances/perform-maintenance b/gcloud/alpha/compute/instances/perform-maintenance index 579d0d3db..a75d8a8a8 100644 --- a/gcloud/alpha/compute/instances/perform-maintenance +++ b/gcloud/alpha/compute/instances/perform-maintenance @@ -10,7 +10,7 @@ DESCRIPTION (ALPHA) Perform maintenance of Google Compute Engine instance. EXAMPLES - To perform a customer trigged maintenance on an instance named + To perform customer-triggered maintenance on an instance named test-instance located in zone us-east1-d, run: $ gcloud alpha compute instances perform-maintenance test-instance \ diff --git a/gcloud/alpha/dataproc/clusters/diagnose b/gcloud/alpha/dataproc/clusters/diagnose index 30b293e1a..81452d216 100644 --- a/gcloud/alpha/dataproc/clusters/diagnose +++ b/gcloud/alpha/dataproc/clusters/diagnose @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud alpha dataproc clusters diagnose (CLUSTER : --region=REGION) - [GCLOUD_WIDE_FLAG ...] + [--end-time=END_TIME] [--job-ids=JOB_IDS] [--start-time=START_TIME] + [--tarball-access=TARBALL_ACCESS] + [--yarn-application-ids=YARN_APPLICATION_IDS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Run a detailed diagnostic on a cluster. @@ -50,6 +52,25 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property dataproc/region. +FLAGS + --end-time=END_TIME + Time instant to stop the diagnosis at (in %Y-%m-%dT%H:%M:%S.%fZ + format). + + --job-ids=JOB_IDS + A list of jobs on which to perform the diagnosis. + + --start-time=START_TIME + Time instant to start the diagnosis from (in %Y-%m-%dT%H:%M:%S.%fZ + format). + + --tarball-access=TARBALL_ACCESS + Target access privileges for diagnose tarball. TARBALL_ACCESS must be + one of: GOOGLE_CLOUD_SUPPORT, GOOGLE_DATAPROC_DIAGNOSE. + + --yarn-application-ids=YARN_APPLICATION_IDS + A list of yarn applications on which to perform the diagnosis. + 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/domains/registrations/get-transfer-parameters b/gcloud/alpha/domains/registrations/get-transfer-parameters index 8d0c969d1..61eff0a47 100644 --- a/gcloud/alpha/domains/registrations/get-transfer-parameters +++ b/gcloud/alpha/domains/registrations/get-transfer-parameters @@ -7,9 +7,14 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Get parameters needed to transfer an existing domain from a - different registrar. The parameters include the current registrar, name - servers, transfer lock state, price, and supported privacy modes. + (ALPHA) (DEPRECATED) Get transfer parameters of a specific domain. + + This command is deprecated. See + https://cloud.google.com/domains/docs/deprecations/feature-deprecations. + + Get parameters needed to transfer an existing domain from a different + registrar. The parameters include the current registrar, name servers, + transfer lock state, price, and supported privacy modes. EXAMPLES To check if example.com is available for transfer, run: diff --git a/gcloud/alpha/domains/registrations/help b/gcloud/alpha/domains/registrations/help index 9e14841e3..f11f012d4 100644 --- a/gcloud/alpha/domains/registrations/help +++ b/gcloud/alpha/domains/registrations/help @@ -42,7 +42,7 @@ COMMANDS domain. get-transfer-parameters - (ALPHA) Get transfer parameters of a specific domain. + (ALPHA) (DEPRECATED) Get transfer parameters of a specific domain. import (ALPHA) (DEPRECATED) Import a domain from Google Domains registrar to @@ -52,8 +52,8 @@ COMMANDS (ALPHA) List Cloud Domains registrations. list-importable-domains - (ALPHA) List Google Domains registrations importable into Cloud - Domains. + (ALPHA) (DEPRECATED) List Google Domains registrations importable into + Cloud Domains. register (ALPHA) Register a new domain. diff --git a/gcloud/alpha/domains/registrations/list-importable-domains b/gcloud/alpha/domains/registrations/list-importable-domains index 95f1efd32..3105bf2a6 100644 --- a/gcloud/alpha/domains/registrations/list-importable-domains +++ b/gcloud/alpha/domains/registrations/list-importable-domains @@ -8,8 +8,14 @@ SYNOPSIS [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Google Domains registrations that can be imported to a Cloud - Domains project. + (ALPHA) (DEPRECATED) List Google Domains registrations importable into + Cloud Domains. + + This command is deprecated. See + https://cloud.google.com/domains/docs/deprecations/feature-deprecations. + + List Google Domains registrations that can be imported to a Cloud Domains + project. Registrations with an IMPORTABLE resource state can be imported from Google Domains registrar to Cloud Domains. diff --git a/gcloud/alpha/functions/add-iam-policy-binding b/gcloud/alpha/functions/add-iam-policy-binding index 713e64f90..7f4767318 100644 --- a/gcloud/alpha/functions/add-iam-policy-binding +++ b/gcloud/alpha/functions/add-iam-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha functions add-iam-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL --role=ROLE [--gen2] [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Adds an IAM policy binding for a Google Cloud Function. @@ -70,15 +70,6 @@ REQUIRED FLAGS for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer. -OPTIONAL FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/functions/add-invoker-policy-binding b/gcloud/alpha/functions/add-invoker-policy-binding index c4639e023..8b3805d2e 100644 --- a/gcloud/alpha/functions/add-invoker-policy-binding +++ b/gcloud/alpha/functions/add-invoker-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha functions add-invoker-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL [--gen2] [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Adds an invoker role IAM policy binding that allows the specified @@ -71,15 +71,6 @@ REQUIRED FLAGS ◆ allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account. -OPTIONAL FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/functions/call b/gcloud/alpha/functions/call index e7fefdf28..81f9ef9cd 100644 --- a/gcloud/alpha/functions/call +++ b/gcloud/alpha/functions/call @@ -2,7 +2,7 @@ NAME gcloud alpha functions call - triggers execution of a Google Cloud Function SYNOPSIS - gcloud alpha functions call (NAME : --region=REGION) [--gen2] + gcloud alpha functions call (NAME : --region=REGION) [--cloud-event=CLOUD_EVENT | --data=DATA] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -56,14 +56,6 @@ POSITIONAL ARGUMENTS ▸ set the property functions/region. FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - At most one of these can be specified: --cloud-event=CLOUD_EVENT diff --git a/gcloud/alpha/functions/delete b/gcloud/alpha/functions/delete index d5ad95b37..15d0a16b6 100644 --- a/gcloud/alpha/functions/delete +++ b/gcloud/alpha/functions/delete @@ -2,7 +2,7 @@ NAME gcloud alpha functions delete - delete a Google Cloud Function SYNOPSIS - gcloud alpha functions delete (NAME : --region=REGION) [--gen2] + gcloud alpha functions delete (NAME : --region=REGION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -41,15 +41,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property functions/region. -FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/functions/describe b/gcloud/alpha/functions/describe index 90ec2251c..b33903ecf 100644 --- a/gcloud/alpha/functions/describe +++ b/gcloud/alpha/functions/describe @@ -3,7 +3,7 @@ NAME Function SYNOPSIS - gcloud alpha functions describe (NAME : --region=REGION) [--gen2] + gcloud alpha functions describe (NAME : --region=REGION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -42,15 +42,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property functions/region. -FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/functions/get-iam-policy b/gcloud/alpha/functions/get-iam-policy index 6b8a177ff..5e1db8b47 100644 --- a/gcloud/alpha/functions/get-iam-policy +++ b/gcloud/alpha/functions/get-iam-policy @@ -3,7 +3,7 @@ NAME Function SYNOPSIS - gcloud alpha functions get-iam-policy (NAME : --region=REGION) [--gen2] + gcloud alpha functions get-iam-policy (NAME : --region=REGION) [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -48,15 +48,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property functions/region. -FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/functions/remove-iam-policy-binding b/gcloud/alpha/functions/remove-iam-policy-binding index 3ede56f61..3251ab037 100644 --- a/gcloud/alpha/functions/remove-iam-policy-binding +++ b/gcloud/alpha/functions/remove-iam-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha functions remove-iam-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL --role=ROLE [--gen2] [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Removes an IAM policy binding from a Google Cloud Function. @@ -71,15 +71,6 @@ REQUIRED FLAGS --role=ROLE The role to remove the principal from. -OPTIONAL FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/functions/remove-invoker-policy-binding b/gcloud/alpha/functions/remove-invoker-policy-binding index cac4a8fb0..22ee3fd0b 100644 --- a/gcloud/alpha/functions/remove-invoker-policy-binding +++ b/gcloud/alpha/functions/remove-invoker-policy-binding @@ -4,8 +4,7 @@ NAME SYNOPSIS gcloud alpha functions remove-invoker-policy-binding - (NAME : --region=REGION) --member=PRINCIPAL [--gen2] - [GCLOUD_WIDE_FLAG ...] + (NAME : --region=REGION) --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Removes the invoker role IAM policy binding that allows the @@ -77,15 +76,6 @@ REQUIRED FLAGS ◆ allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account. -OPTIONAL FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/functions/set-iam-policy b/gcloud/alpha/functions/set-iam-policy index 64aa408a4..1f9bf49fa 100644 --- a/gcloud/alpha/functions/set-iam-policy +++ b/gcloud/alpha/functions/set-iam-policy @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha functions set-iam-policy (NAME : --region=REGION) POLICY_FILE - [--gen2] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Sets IAM policy for a Google Cloud Function. @@ -51,15 +51,6 @@ POSITIONAL ARGUMENTS POLICY_FILE Path to a local JSON or YAML formatted file containing a valid policy. -FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/healthcare/dicom-stores/help b/gcloud/alpha/healthcare/dicom-stores/help index 64be97f4f..2813fea55 100644 --- a/gcloud/alpha/healthcare/dicom-stores/help +++ b/gcloud/alpha/healthcare/dicom-stores/help @@ -48,6 +48,9 @@ COMMANDS list (ALPHA) List Cloud Healthcare API DICOM stores. + metrics + (ALPHA) Get the metrics for a Cloud Healthcare API DICOM store. + remove-iam-policy-binding (ALPHA) Remove an IAM policy binding from a Cloud Healthcare API DICOM store. diff --git a/gcloud/alpha/healthcare/dicom-stores/metrics b/gcloud/alpha/healthcare/dicom-stores/metrics new file mode 100644 index 000000000..b2cd7cbd3 --- /dev/null +++ b/gcloud/alpha/healthcare/dicom-stores/metrics @@ -0,0 +1,81 @@ +NAME + gcloud alpha healthcare dicom-stores metrics - get the metrics for a Cloud + Healthcare API DICOM store + +SYNOPSIS + gcloud alpha healthcare dicom-stores metrics + (DICOM_STORE : --dataset=DATASET --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Gets the metrics for a Cloud Healthcare API DICOM store. + +EXAMPLES + To get metrics for the DICOM store 'test-dicom-store', run: + + $ gcloud alpha healthcare dicom-stores metrics test-dicom-store \ + --dataset=test-dataset + +POSITIONAL ARGUMENTS + DicomStore resource - Cloud Healthcare API DICOM store to get metrics for. + 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 dicom_store 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. + + DICOM_STORE + ID of the dicomStore or fully qualified identifier for the + dicomStore. + + To set the dicom_store attribute: + ▸ provide the argument dicom_store on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --dataset=DATASET + Cloud Healthcare dataset. + + To set the dataset attribute: + ▸ provide the argument dicom_store on the command line with a fully + specified name; + ▸ provide the argument --dataset on the command line. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument dicom_store on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property healthcare/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 healthcare/v1alpha2 API. The full documentation for + this API can be found at: https://cloud.google.com/healthcare + +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 healthcare dicom-stores metrics + + $ gcloud beta healthcare dicom-stores metrics + diff --git a/gcloud/alpha/immersive-stream/xr/instances/create b/gcloud/alpha/immersive-stream/xr/instances/create index 8ea88e713..52844bde2 100644 --- a/gcloud/alpha/immersive-stream/xr/instances/create +++ b/gcloud/alpha/immersive-stream/xr/instances/create @@ -9,7 +9,8 @@ SYNOPSIS [capacity=CAPACITY], [enable_autoscaling=ENABLE_AUTOSCALING],[region=REGION] --version=VERSION (--content=CONTENT : --location=LOCATION) [--async] - [--fallback-url=FALLBACK_URL] [GCLOUD_WIDE_FLAG ...] + [--fallback-url=FALLBACK_URL] [--gpu-class=GPU_CLASS] [--mode=MODE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create an Immersive Stream for XR service instance. @@ -36,6 +37,22 @@ EXAMPLES --add-region=region=us-west1,capacity=2 \ --fallback-url="https://www.google.com" + By default, the instance is created with mode=ar, which supports both + 3D and AR experiences. Instances can also be configured to use + 3D-only mode. This configuration cannot be updated later. + To use 3D-only mode, include: + + --mode=3d + + By default, the instance is created with gpu-class=t4. This uses the + NVIDIA T4 GPU for the instance. Instances can also be configured to + use NVIDIA L4 GPUs at creation. Note that only certain regions are + available for L4, and only 3D-only mode is supported. This + configuration cannot be updated later. + To use NVIDIA L4 GPU for the instance, include: + + --gpu-class=l4 + POSITIONAL ARGUMENTS INSTANCE Name of the instance to be created @@ -94,6 +111,12 @@ OPTIONAL FLAGS Fallback url to redirect users to when this service instance is unable to provide the streaming experience + --gpu-class=GPU_CLASS + The class of GPU that is used by this service instance + + --mode=MODE + The rendering mode that is supported by this service instance + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/migration/help b/gcloud/alpha/migration/help new file mode 100644 index 000000000..c621da999 --- /dev/null +++ b/gcloud/alpha/migration/help @@ -0,0 +1,27 @@ +NAME + gcloud alpha migration - the root group for various Cloud Migration teams + +SYNOPSIS + gcloud alpha migration GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Each team must have its own sub-group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + vms + (ALPHA) Provides Migrate to Virtual Machines (VM migration) service + functionality. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/help b/gcloud/alpha/migration/vms/help new file mode 100644 index 000000000..fe88554c8 --- /dev/null +++ b/gcloud/alpha/migration/vms/help @@ -0,0 +1,35 @@ +NAME + gcloud alpha migration vms - provides Migrate to Virtual Machines + (VM migration) service functionality + +SYNOPSIS + gcloud alpha migration vms GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The gcloud alpha migration vms command group provides the CLI for + the Migrate to Virtual Machines API. Google Cloud Migrate to Virtual + Machines migrates VMs from on-premises data center and other cloud + providers to Google Compute Engine virtual machine (VM) instances. VM + Migration API must be enabled in your project. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + image-imports + (ALPHA) Imports images to Google Compute Engine from Google Cloud + Storage. + + target-projects + (ALPHA) Manage Target Projects. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/image-imports/create b/gcloud/alpha/migration/vms/image-imports/create new file mode 100644 index 000000000..1f37d479d --- /dev/null +++ b/gcloud/alpha/migration/vms/image-imports/create @@ -0,0 +1,136 @@ +NAME + gcloud alpha migration vms image-imports create - import Virtual Disk + images to Google Compute Engine + +SYNOPSIS + gcloud alpha migration vms image-imports create + (IMAGE_IMPORT_NAME : --location=LOCATION) --source-file=SOURCE_FILE + [--additional-licenses=[ADDITIONAL_LICENSES,...]] + [--description=DESCRIPTION] [--family-name=FAMILY_NAME] + [--image-name=IMAGE_NAME] [--labels=[KEY=VALUE,...]] + [--single-region-storage] [--target-project=TARGET_PROJECT] + [--skip-os-adaptation | --generalize --license-type=LICENSE_TYPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms image-imports create imports images such + as VMWare VMDK files and VHD files, from a Google Cloud Storage file + (gs://...) to Google Compute Engine, using the Migrate to Virtual Machines + service API. This command creates an Image Import resource with a nested + Image Import Job resource. The Image Import Job resource tracks the image + import progress. To use this command, you must enable VM Migration API in + your project. + +EXAMPLES + To import my-ubuntu22.04.vmdk from my-images-bucket to my-target-project in + us-central1, create my-image-import resource in my-project in us-central1. + Run: $ gcloud alpha migration vms image-imports create my-image-import \ + --source-file=gs://my-images-bucket/my-ubuntu22.04.vmdk \ + --image-name=my-ubuntu-image --location=us-central1 \ + --target-project=projects/my-project/locations/global/\ + targetProjects/my-target-project --project=my-project + +POSITIONAL ARGUMENTS + Image import resource - The Image Import resource you want to create. This + would be the image name if --image-name is not given. 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 image_import_name 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. + + IMAGE_IMPORT_NAME + ID of the image_import or fully qualified identifier for the + image_import. + + To set the image_import_name attribute: + ▸ provide the argument image_import_name on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument image_import_name on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + +REQUIRED FLAGS + --source-file=SOURCE_FILE + The path to the Google Cloud Storage file from which the image should + be imported. + +OPTIONAL FLAGS + --additional-licenses=[ADDITIONAL_LICENSES,...] + Comma-separated list of the additional licenses to assign to the image. + + --description=DESCRIPTION + A description of the image. + + --family-name=FAMILY_NAME + The name of the image family to which the new image belongs. + + --image-name=IMAGE_NAME + The name of the image that will be imported to Google Compute Engine. + Default is the Image Import name. + + --labels=[KEY=VALUE,...] + A map of labels to associate with the image. + + --single-region-storage + If true, the location of the imported image will be the region of the + import job. Otherwise the closest multi-region is selected. Default is + false. + + --target-project=TARGET_PROJECT + The target project resource path to which the image will be imported. + Default is the customer project. To get a list of the target projects + run the gcloud alpha migration vms target-projects list command. + + OS adaptation parameters + + At most one of these can be specified: + + --skip-os-adaptation + If true, skip OS adaptation. Default false. + + --generalize + If true, generalize the imported image. Default false. The + generalization process enables co-existence of multiple VMs created + from the same image. For Windows, generalizing the image removes + computer-specific information such as installed drivers and the + computer security identifier (SID). + + --license-type=LICENSE_TYPE + The license to use post migration. LICENSE_TYPE must be one of: + compute-engine-license-type-byol, + compute-engine-license-type-default, + compute-engine-license-type-payg. + +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 vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/image-imports/delete b/gcloud/alpha/migration/vms/image-imports/delete new file mode 100644 index 000000000..fbb325564 --- /dev/null +++ b/gcloud/alpha/migration/vms/image-imports/delete @@ -0,0 +1,71 @@ +NAME + gcloud alpha migration vms image-imports delete - delete an Image Import + resource + +SYNOPSIS + gcloud alpha migration vms image-imports delete + (IMAGE_IMPORT_NAME : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms image-imports delete deletes an Image + Import resource. To use this command, you must enable VM Migration API in + your project. + + This command does not delete any images imported to Google Compute Engine. + +EXAMPLES + To delete my-image-import resource in us-central1 in the default project, + run: $ gcloud alpha migration vms image-imports delete my-image-import \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Image import resource - The Image Import resource you want to delete. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument image_import_name 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. + + IMAGE_IMPORT_NAME + ID of the image_import or fully qualified identifier for the + image_import. + + To set the image_import_name attribute: + ▸ provide the argument image_import_name on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument image_import_name on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/image-imports/describe b/gcloud/alpha/migration/vms/image-imports/describe new file mode 100644 index 000000000..45a509835 --- /dev/null +++ b/gcloud/alpha/migration/vms/image-imports/describe @@ -0,0 +1,70 @@ +NAME + gcloud alpha migration vms image-imports describe - describe an Image + Import + +SYNOPSIS + gcloud alpha migration vms image-imports describe + (IMAGE_IMPORT_NAME : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms image-imports describe describes an + Image Import resource with a nested Image Import Job. The Image Import Job + resource tracks the image import progress. To use this command, you must + enable VM Migration API in your project. + +EXAMPLES + To describe my-image-import resource in us-central1 in the default project, + run: $ gcloud alpha migration vms image-imports describe \ + my-image-import --location=us-central1 + +POSITIONAL ARGUMENTS + Image import resource - The Image Import you want to describe. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument image_import_name 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. + + IMAGE_IMPORT_NAME + ID of the image_import or fully qualified identifier for the + image_import. + + To set the image_import_name attribute: + ▸ provide the argument image_import_name on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Resource location. + + To set the location attribute: + ▸ provide the argument image_import_name on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/image-imports/help b/gcloud/alpha/migration/vms/image-imports/help new file mode 100644 index 000000000..2b898724f --- /dev/null +++ b/gcloud/alpha/migration/vms/image-imports/help @@ -0,0 +1,61 @@ +NAME + gcloud alpha migration vms image-imports - imports images to Google Compute + Engine from Google Cloud Storage + +SYNOPSIS + gcloud alpha migration vms image-imports COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms image-imports provides a more robust and + better supported method for importing images to Google Compute Engine. + Other image-related operations (for example, list) can be done using gcloud + compute images, as usual. + + The commands use VM Migartion API which supports importing of an image from + a Google Cloud Storage file (gs://...) to a target project. VM Migration + API must be enabled in your project. + + gcloud alpha migration vms image-imports create creates an Image Import + resource with a nested Image Import Job resource. The Image Import Job + resource tracks the image import progress. After the Image Import Job + completes, successfully or otherwise, there's no further use for the Image + Import resource. + + The image is imported to a Google Cloud Project, desginated by the Target + Project resource. To get a list of Target Projects, run the gcloud alpha + migration vms target-projects list command. Use the Google Cloud console to + add target project resources. For information on adding target projects, + see + https://cloud.google.com/migrate/virtual-machines/docs/5.0/how-to/target-project. + + A project can support a maximum of 1000 Image Import resources per project. + Hence it's recommended to delete an Image Import resource after the Image + Import Job is complete to avoid reaching the Image Import resources limit. + Deletion of Image Import resource does not affect the imported image. + +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) import Virtual Disk images to Google Compute Engine. + + delete + (ALPHA) delete an Image Import resource. + + describe + (ALPHA) describe an Image Import. + + list + (ALPHA) list Image Imports. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/image-imports/list b/gcloud/alpha/migration/vms/image-imports/list new file mode 100644 index 000000000..31da4d850 --- /dev/null +++ b/gcloud/alpha/migration/vms/image-imports/list @@ -0,0 +1,90 @@ +NAME + gcloud alpha migration vms image-imports list - list Image Imports + +SYNOPSIS + gcloud alpha migration vms image-imports list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms image-imports list prints a detailed + list of Image Import resources. To use this command, you must enable VM + Migration API in your project. + +EXAMPLES + To list the Image Import resources in us-central1 in the default project, + run: $ gcloud alpha migration vms image-imports list \ + --location=us-central1 + +FLAGS + Location resource - The compute/region of the Image Import. To get a list + of the available regions, run gcloud compute regions list command. If not + specified, the value of the [compute/zone] property in the current gcloud + configuration is used. This represents a Cloud resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property compute/region with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property compute/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/target-projects/help b/gcloud/alpha/migration/vms/target-projects/help new file mode 100644 index 000000000..82b63afe5 --- /dev/null +++ b/gcloud/alpha/migration/vms/target-projects/help @@ -0,0 +1,30 @@ +NAME + gcloud alpha migration vms target-projects - manage Target Projects + +SYNOPSIS + gcloud alpha migration vms target-projects COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) target-projects sub-group is used to manage Target Project + resources of the Migrate to Virtual Machines service. Target projects are + defined for each customer project in the global location. A Target Project + could be used as the target project of various migration commands. VM + Migration API must be enabled in your project. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (ALPHA) list Target Projects. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/migration/vms/target-projects/list b/gcloud/alpha/migration/vms/target-projects/list new file mode 100644 index 000000000..1c9578ba2 --- /dev/null +++ b/gcloud/alpha/migration/vms/target-projects/list @@ -0,0 +1,93 @@ +NAME + gcloud alpha migration vms target-projects list - list Target Projects + +SYNOPSIS + gcloud alpha migration vms target-projects list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha migration vms target-projects list lists Target + Project resources, which are required for setting the target project for + migration. Target projects are defined for each customer project in the + global location. To use this command, you must enable VM Migration API in + your project. + +EXAMPLES + To list the Target Project resources in the global location in the default + project, run: $ gcloud alpha migration vms target-projects list + +FLAGS + Location resource - The compute/region of the Image Import. To get a list + of the available regions, run gcloud compute regions list command. If not + specified, the value of the [compute/zone] property in the current gcloud + configuration is used. This represents a Cloud resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property compute/region with a fully specified name; + ◆ use default global location with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property compute/region; + ▸ use default global location . + +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 vmmigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/migrate/virtual-machines + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/monitoring/help b/gcloud/alpha/monitoring/help index d53731c7a..607915b97 100644 --- a/gcloud/alpha/monitoring/help +++ b/gcloud/alpha/monitoring/help @@ -43,7 +43,7 @@ GROUPS (ALPHA) Manage Cloud Monitoring snoozes. uptime - (ALPHA) Manage Cloud Monitoring uptime checks. + (ALPHA) Manage Cloud Monitoring uptime checks and synthetic monitors. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/monitoring/uptime/create b/gcloud/alpha/monitoring/uptime/create index 79bc614f6..020d8b5e2 100644 --- a/gcloud/alpha/monitoring/uptime/create +++ b/gcloud/alpha/monitoring/uptime/create @@ -1,5 +1,6 @@ NAME - gcloud alpha monitoring uptime create - create a new uptime check + gcloud alpha monitoring uptime create - create a new uptime check or + synthetic monitor SYNOPSIS gcloud alpha monitoring uptime create DISPLAY_NAME @@ -22,13 +23,16 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create a new uptime check. + (ALPHA) Create a new uptime check or synthetic monitor. + + Flags only apply to uptime checks unless noted that they apply to synthetic + monitors. For information about the JSON/YAML format of an uptime check: https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.uptimeCheckConfigs EXAMPLES - To create an uptime check against an uptime_url, run: + To create an uptime check against a URL, run: $ gcloud alpha monitoring uptime create DISPLAY_NAME \ --resource-type=uptime-url \ @@ -36,16 +40,16 @@ EXAMPLES To create a synthetic monitor, run: - $ gcloud alpha monitoring uptime create fake_uptime_check \ + $ gcloud alpha monitoring uptime create SYNTHETIC_MONITOR_NAME \ --synthetic-target=projects/PROJECT_ID/locations/REGION/\ functions/FUNCTION_NAME POSITIONAL ARGUMENTS DISPLAY_NAME - Display name for the Uptime Check. + Display name for the uptime check or synthetic monitor. REQUIRED FLAGS - Uptime check resource + Uptime check resource. Exactly one of these must be specified: @@ -62,13 +66,13 @@ REQUIRED FLAGS in this group are specified. --group-type=GROUP_TYPE - The resource type of the group members, defaults to "gce-instance". + The resource type of the group members, defaults to gce-instance. GROUP_TYPE must be one of: aws-elb-load-balancer - Uptime Check against a group of Amazon ELB load balancers. + Uptime check against a group of Amazon ELB load balancers. gce-instance - Uptime Check against a group of instances from Google Cloud or + Uptime check against a group of instances from Google Cloud or Amazon Web Services. Monitored resource @@ -83,35 +87,34 @@ REQUIRED FLAGS in this group are specified. --resource-type=RESOURCE_TYPE - Type of monitored resource, defaults to "uptime-url". RESOURCE_TYPE + Type of monitored resource, defaults to uptime-url. RESOURCE_TYPE must be one of: aws-ec2-instance - Uptime Check against an AWS EC2 instance. + Uptime check against an AWS EC2 instance. aws-elb-load-balancer - Uptime Check against an ElasticLoadBalancer. + Uptime check against an ElasticLoadBalancer. cloud-run-revision - Uptime Check against a Cloud Run revision. + Uptime check against a Cloud Run revision. gae-app - Uptime Check against an App Engine module. + Uptime check against an App Engine module. gce-instance - Uptime Check against a Compute Engine instance. + Uptime check against a Compute Engine instance. servicedirectory-service - Uptime Check against a Service Directory service. + Uptime check against a Service Directory service. uptime-url - Uptime Check against a URL. + Uptime check against a URL. OPTIONAL FLAGS - Uptime check protocol settings. Cannot be used if --synthetic-target is - set. + Uptime check protocol settings. --body=BODY The request body associated with the HTTP POST request. Can only be - set if --protocol is "http" or "https". + set if --protocol is http or https. --content-type=CONTENT_TYPE The content type header to use for the check, defaults to - "unspecified". Can only be set if --protocol is "http" or "https". + unspecified. Can only be set if --protocol is http or https. CONTENT_TYPE must be one of: @@ -124,34 +127,34 @@ OPTIONAL FLAGS --custom-content-type=CUSTOM_CONTENT_TYPE A user-provided content type header to use for the check. Can only be - set if --protocol is "http" or "https". + set if --protocol is http or https. --headers=[KEY=VALUE,...] - The list of headers to send as part of the Uptime Check request. Can - only be set if --protocol is "http" or "https". + The list of headers to send as part of the uptime check request. Can + only be set if --protocol is http or https. --mask-headers=MASK_HEADERS - Whether to encrypt the header information, defaults to "false". Can - only be set if --protocol is "http" or "https". + Whether to encrypt the header information, defaults to false. Can + only be set if --protocol is http or https. --password=PASSWORD The password to use when authenticating with the HTTP server. Can - only be set if --protocol is "http" or "https". + only be set if --protocol is http or https. --path=PATH - The path to the page against which to run the check, defaults to "/". - Can only be set if --protocol is "http" or "https". + The path to the page against which to run the check, defaults to /. + Can only be set if --protocol is http or https. --pings-count=PINGS_COUNT Number of ICMP pings to send alongside the request. --port=PORT - The port on the server against which to run the check. Defaults to - "80" when --protocol is "http". Defaults to "443" when --protocol is - "https". Required if --protocol is "tcp". + The port on the server against which to run the check. Defaults to 80 + when --protocol is http. Defaults to 443 when --protocol is https. + Required if --protocol is tcp. --protocol=PROTOCOL - The protocol of the request, defaults to "http". PROTOCOL must be one + The protocol of the request, defaults to http. PROTOCOL must be one of: http @@ -162,8 +165,8 @@ OPTIONAL FLAGS A TCP check. --request-method=REQUEST_METHOD - The HTTP request method to use, defaults to "get". Can only be set if - --protocol is "http" or "https". + The HTTP request method to use, defaults to get. Can only be set if + --protocol is http or https. REQUEST_METHOD must be one of: @@ -174,20 +177,21 @@ OPTIONAL FLAGS --username=USERNAME The username to use when authenticating with the HTTP server. Can - only be set if --protocol is "http" or "https". + only be set if --protocol is http or https. --validate-ssl=VALIDATE_SSL - Whether to include SSL certificate validation as a part of the Uptime - Check, defaults to "false". Can only be set if --protocol is "https". + Whether to include SSL certificate validation as a part of the uptime + check, defaults to false. Can only be set if --protocol is http or + https. - Uptime Status + Uptime check status. At most one of these can be specified: --status-classes=[status-class,...] - List of HTTP Status Classes. The Uptime Check will only pass if the - response code is contained in this list. Defaults to "2xx". Can - only be set if --protocol is "http" or "https". + List of HTTP status classes. The uptime check only passes when the + response code is contained in this list. Defaults to 2xx. Can only + be set if --protocol is http or https. status-class must be one of: @@ -205,11 +209,11 @@ OPTIONAL FLAGS Any response code --status-codes=[status-code,...] - List of HTTP Status Codes. The Uptime Check will only pass if the + List of HTTP Status Codes. The uptime check will only pass if the response code is present in this list. Can only be set if - --protocol is "http" or "https". + --protocol is http or https. - Uptime matcher settings. Cannot be used if --synthetic-target is set. + Uptime check matcher settings. --matcher-content=MATCHER_CONTENT String, regex or JSON content to match. @@ -218,8 +222,8 @@ OPTIONAL FLAGS this group are specified. --matcher-type=MATCHER_TYPE - The type of content matcher that will be applied to the server - output, defaults to "contains-string". + The type of content matcher that is applied to the server output, + defaults to contains-string. MATCHER_TYPE must be one of: @@ -236,20 +240,20 @@ OPTIONAL FLAGS not-matches-regex Response does not match regex - Uptime matcher settings for JSON responses + Uptime check matcher settings for JSON responses. --json-path=JSON_PATH JSONPath within the response output pointing to the expected - content to match. Only used if matcher-type is "matches-json-path" - or "not-matches-json-path". + content to match. Only used if --matcher-type is matches-json-path + or not-matches-json-path. This flag argument must be specified if any of the other arguments in this group are specified. --json-path-matcher-type=JSON_PATH_MATCHER_TYPE - The type of JSONPath match that will be applied to the JSON output, - defaults to "exact-match". Only used if matcher-type is - "matches-json-path" or "not-matches-json-path". + The type of JSONPath match that is applied to the JSON output, + defaults to exact-match. Only used if --matcher-type is + matches-json-path or not-matches-json-path. JSON_PATH_MATCHER_TYPE must be one of: @@ -258,11 +262,13 @@ OPTIONAL FLAGS regex-match Response matches regex at JSONPath - Uptime check settings + Settings. --period=PERIOD - How often, in minutes, the Uptime check is performed, defaults to - "1". PERIOD must be one of: + The time between uptime check or synthetic monitor executions in + minutes, defaults to 1. Can be set for synthetic monitors. + + PERIOD must be one of: 1 One minute @@ -274,9 +280,8 @@ OPTIONAL FLAGS Five minutes --regions=[field,...] - The list of regions from which the check will be run. At least 3 - regions must be selected. Defaults to all available regions. Cannot - be used if --synthetic-target is set. + The list of regions from which the check is run. At least 3 regions + must be selected. Defaults to all available regions. field must be one of: @@ -295,7 +300,7 @@ OPTIONAL FLAGS --timeout=TIMEOUT The maximum amount of time in seconds to wait for the request to - complete, defaults to "60". + complete, defaults to 60. Can be set for synthetic monitors. --user-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. @@ -305,10 +310,6 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - If the uptime check was given as a JSON/YAML object from a string or - file, this flag will replace the labels value in the given uptime - check. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -321,5 +322,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 monitoring uptime create + + $ gcloud beta monitoring uptime create diff --git a/gcloud/alpha/monitoring/uptime/delete b/gcloud/alpha/monitoring/uptime/delete index 9cd6ddb32..846d65489 100644 --- a/gcloud/alpha/monitoring/uptime/delete +++ b/gcloud/alpha/monitoring/uptime/delete @@ -1,24 +1,26 @@ NAME - gcloud alpha monitoring uptime delete - delete an uptime check + gcloud alpha monitoring uptime delete - delete an uptime check or synthetic + monitor SYNOPSIS gcloud alpha monitoring uptime delete CHECK_ID [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete an uptime check + (ALPHA) Delete an uptime check or synthetic monitor EXAMPLES - To delete an uptime check: + To delete an uptime check or synthetic monitor: - $ gcloud alpha monitoring uptime delete check-id + $ gcloud alpha monitoring uptime delete CHECK_ID More information can be found at https://cloud.google.com/monitoring/uptime-checks/manage#delete. POSITIONAL ARGUMENTS - Uptime check resource - The uptime check to delete. This represents a - Cloud resource. (NOTE) Some attributes are not given arguments in this - group but can be set in other ways. + Uptime check or synthetic monitor resource - The uptime check or synthetic + monitor to delete. 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 check_id on the command line with a fully @@ -29,8 +31,8 @@ POSITIONAL ARGUMENTS This must be specified. CHECK_ID - ID of the uptime_check or fully qualified identifier for the - uptime_check. + ID of the uptime check or synthetic monitor or fully qualified + identifier for the uptime check or synthetic monitor. To set the check_id attribute: ▸ provide the argument check_id on the command line. @@ -51,5 +53,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 monitoring uptime delete + + $ gcloud beta monitoring uptime delete diff --git a/gcloud/alpha/monitoring/uptime/describe b/gcloud/alpha/monitoring/uptime/describe index 28a983338..4b777ec5c 100644 --- a/gcloud/alpha/monitoring/uptime/describe +++ b/gcloud/alpha/monitoring/uptime/describe @@ -1,24 +1,26 @@ NAME - gcloud alpha monitoring uptime describe - describe an uptime check + gcloud alpha monitoring uptime describe - describe an uptime check or + synthetic monitor SYNOPSIS gcloud alpha monitoring uptime describe CHECK_ID [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describe an uptime check + (ALPHA) Describe an uptime check or synthetic monitor EXAMPLES - To describe an uptime check: + To describe an uptime check or synthetic monitor: - $ gcloud alpha monitoring uptime describe + $ gcloud alpha monitoring uptime describe CHECK_ID More information can be found at https://cloud.google.com/monitoring/uptime-checks/manage#get. POSITIONAL ARGUMENTS - Uptime check resource - The uptime check to describe. This represents a - Cloud resource. (NOTE) Some attributes are not given arguments in this - group but can be set in other ways. + Uptime check or synthetic monitor resource - The uptime check or synthetic + monitor to describe. 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 check_id on the command line with a fully @@ -29,8 +31,8 @@ POSITIONAL ARGUMENTS This must be specified. CHECK_ID - ID of the uptime_check or fully qualified identifier for the - uptime_check. + ID of the uptime check or synthetic monitor or fully qualified + identifier for the uptime check or synthetic monitor. To set the check_id attribute: ▸ provide the argument check_id on the command line. @@ -51,5 +53,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 monitoring uptime describe + + $ gcloud beta monitoring uptime describe diff --git a/gcloud/alpha/monitoring/uptime/help b/gcloud/alpha/monitoring/uptime/help index 7f6856844..10640da98 100644 --- a/gcloud/alpha/monitoring/uptime/help +++ b/gcloud/alpha/monitoring/uptime/help @@ -1,11 +1,12 @@ NAME - gcloud alpha monitoring uptime - manage Cloud Monitoring uptime checks + gcloud alpha monitoring uptime - manage Cloud Monitoring uptime checks and + synthetic monitors SYNOPSIS gcloud alpha monitoring uptime COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage Monitoring uptime checks. + (ALPHA) Manage Monitoring uptime checks and synthetic monitors. More information can be found here: https://cloud.google.com/monitoring/api/v3/ @@ -19,26 +20,30 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create a new uptime check. + (ALPHA) Create a new uptime check or synthetic monitor. delete - (ALPHA) Delete an uptime check. + (ALPHA) Delete an uptime check or synthetic monitor. describe - (ALPHA) Describe an uptime check. + (ALPHA) Describe an uptime check or synthetic monitor. list-configs - (ALPHA) List uptime checks. + (ALPHA) List uptime checks and synthetic monitors. list-ips - (ALPHA) List uptime check egress ips. + (ALPHA) List uptime check server ips. update - (ALPHA) Update an existing uptime check. + (ALPHA) Update an existing uptime check or synthetic monitor. 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 monitoring uptime + + $ gcloud beta monitoring uptime diff --git a/gcloud/alpha/monitoring/uptime/list-configs b/gcloud/alpha/monitoring/uptime/list-configs index 90440bd43..802136d0c 100644 --- a/gcloud/alpha/monitoring/uptime/list-configs +++ b/gcloud/alpha/monitoring/uptime/list-configs @@ -1,5 +1,6 @@ NAME - gcloud alpha monitoring uptime list-configs - list uptime checks + gcloud alpha monitoring uptime list-configs - list uptime checks and + synthetic monitors SYNOPSIS gcloud alpha monitoring uptime list-configs [--filter=EXPRESSION] @@ -7,10 +8,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List uptime checks. + (ALPHA) List uptime checks and synthetic monitors. EXAMPLES - To see all uptime checks: + To see all uptime checks and synthetic monitors: $ gcloud alpha monitoring uptime list-configs @@ -65,5 +66,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 monitoring uptime list-configs + + $ gcloud beta monitoring uptime list-configs diff --git a/gcloud/alpha/monitoring/uptime/list-ips b/gcloud/alpha/monitoring/uptime/list-ips index 4c75ee1ae..78786c041 100644 --- a/gcloud/alpha/monitoring/uptime/list-ips +++ b/gcloud/alpha/monitoring/uptime/list-ips @@ -1,5 +1,5 @@ NAME - gcloud alpha monitoring uptime list-ips - list uptime check egress ips + gcloud alpha monitoring uptime list-ips - list uptime check server ips SYNOPSIS gcloud alpha monitoring uptime list-ips [GCLOUD_WIDE_FLAG ...] @@ -8,7 +8,7 @@ DESCRIPTION (ALPHA) List uptime check egress ips. EXAMPLES - To see all uptime check egress ips: + To see all uptime check servers ips: $ gcloud alpha monitoring uptime list-ips @@ -31,5 +31,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 monitoring uptime list-ips + + $ gcloud beta monitoring uptime list-ips diff --git a/gcloud/alpha/monitoring/uptime/update b/gcloud/alpha/monitoring/uptime/update index 0a31362e9..245d77209 100644 --- a/gcloud/alpha/monitoring/uptime/update +++ b/gcloud/alpha/monitoring/uptime/update @@ -1,5 +1,6 @@ NAME - gcloud alpha monitoring uptime update - update an existing uptime check + gcloud alpha monitoring uptime update - update an existing uptime check or + synthetic monitor SYNOPSIS gcloud alpha monitoring uptime update CHECK_ID @@ -29,15 +30,25 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Updates an existing uptime check. + (ALPHA) Updates an existing uptime check or synthetic monitor. + + Flags only apply to uptime checks unless noted that they apply to synthetic + monitors. For information about the JSON/YAML format of an uptime check: https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.uptimeCheckConfigs +EXAMPLES + To update an uptime check or synthetic monitor, run: + + $ gcloud alpha monitoring uptime update CHECK_ID --period=5 \ + --timeout=30 + POSITIONAL ARGUMENTS - Uptime Check resource - Name of the Uptime Check to be updated. This - represents a Cloud resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + Uptime check or synthetic monitor resource - Name of the uptime check or + synthetic monitor to be updated. 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 check_id on the command line with a fully @@ -48,23 +59,22 @@ POSITIONAL ARGUMENTS This must be specified. CHECK_ID - ID of the Uptime Check or fully qualified identifier for the Uptime - Check. + ID of the uptime check or synthetic monitor or fully qualified + identifier for the uptime check or synthetic monitor. - To set the uptime_check attribute: + To set the check_id attribute: ▸ provide the argument check_id on the command line. FLAGS - Uptime check protocol settings. Cannot be used if --synthetic-target is - set. + Uptime check protocol settings. --body=BODY The request body associated with the HTTP POST request. Can only be - set if --protocol is "http" or "https". + set if --protocol is http or https. --content-type=CONTENT_TYPE The content type header to use for the check, defaults to - "unspecified". Can only be set if --protocol is "http" or "https". + unspecified. Can only be set if --protocol is http or https. CONTENT_TYPE must be one of: @@ -77,31 +87,31 @@ FLAGS --custom-content-type=CUSTOM_CONTENT_TYPE A user-provided content type header to use for the check. Can only be - set if --protocol is "http" or "https". + set if --protocol is http or https. --mask-headers=MASK_HEADERS - Whether to encrypt the header information, defaults to "false". Can - only be set if --protocol is "http" or "https". + Whether to encrypt the header information, defaults to false. Can + only be set if --protocol is http or https. --password=PASSWORD The password to use when authenticating with the HTTP server. Can - only be set if --protocol is "http" or "https". + only be set if --protocol is http or https. --path=PATH - The path to the page against which to run the check, defaults to "/". - Can only be set if --protocol is "http" or "https". + The path to the page against which to run the check, defaults to /. + Can only be set if --protocol is http or https. --pings-count=PINGS_COUNT Number of ICMP pings to send alongside the request. --port=PORT - The port on the server against which to run the check. Defaults to - "80" when --protocol is "http". Defaults to "443" when --protocol is - "https". Required if --protocol is "tcp". + The port on the server against which to run the check. Defaults to 80 + when --protocol is http. Defaults to 443 when --protocol is https. + Required if --protocol is tcp. --request-method=REQUEST_METHOD - The HTTP request method to use, defaults to "get". Can only be set if - --protocol is "http" or "https". + The HTTP request method to use, defaults to get. Can only be set if + --protocol is http or https. REQUEST_METHOD must be one of: @@ -112,22 +122,23 @@ FLAGS --username=USERNAME The username to use when authenticating with the HTTP server. Can - only be set if --protocol is "http" or "https". + only be set if --protocol is http or https. --validate-ssl=VALIDATE_SSL - Whether to include SSL certificate validation as a part of the Uptime - Check, defaults to "false". Can only be set if --protocol is "https". + Whether to include SSL certificate validation as a part of the uptime + check, defaults to false. Can only be set if --protocol is http or + https. - Uptime Status + Uptime check status. At most one of these can be specified: - Uptime Status Classes + Uptime check status classes. At most one of these can be specified: --add-status-classes=[status-class,...] - The list of HTTP Status Classes to add to the Uptime Check. + The list of HTTP status classes to add to the uptime check. status-class must be one of: 1xx @@ -144,11 +155,11 @@ FLAGS Any response code --clear-status-classes=CLEAR_STATUS_CLASSES - Clear all HTTP Status Classes on the Uptime Check. This will act - the same as if only "2xx" was selected. + Clear all HTTP status classes on the uptime check. Setting this + flag is the same as selecting only the 2xx status class. --remove-status-classes=[status-class,...] - The list of HTTP Status Classes to remove from the Uptime Check. + The list of HTTP status classes to remove from the uptime check. status-class must be one of: 1xx @@ -165,7 +176,7 @@ FLAGS Any response code --set-status-classes=[status-class,...] - List of HTTP Status Classes. The Uptime Check will only pass if + List of HTTP status classes. The uptime check will only pass if the response code is contained in this list. status-class must be one of: @@ -183,49 +194,50 @@ FLAGS any Any response code - Uptime Status Codes + Uptime check status codes. At most one of these can be specified: --add-status-codes=[status-code,...] - The list of HTTP Status Codes to add to the Uptime Check. + The list of HTTP status codes to add to the uptime check. --clear-status-codes=CLEAR_STATUS_CODES - Clear all HTTP Status Codes on the Uptime Check. This will act - the same as if only the "2xx" HTTP Status Class was selected. + Clear all HTTP status codes on the uptime check. Setting this + flag is the same as selecting only the 2xx status class. --remove-status-codes=[status-code,...] - The list of HTTP Status Codes to remove from the Uptime Check. + The list of HTTP status codes to remove from the uptime check. --set-status-codes=[status-code,...] - List of HTTP Status Codes. The Uptime Check will only pass if the + List of HTTP status codes. The uptime check will only pass if the response code is present in this list. - Uptime Headers + Uptime check headers. --update-headers=[KEY=VALUE,...] - The list of headers to add to the Uptime Check. Any existing - headers with matching "key" will be overridden by the provided - values. + The list of headers to add to the uptime check. Any existing + headers with matching "key" are overridden by the provided values. - Uptime remove Headers + Uptime check remove headers. At most one of these can be specified: --clear-headers=CLEAR_HEADERS - Clear all headers on the Uptime Check. + Clear all headers on the uptime check. --remove-headers=[KEY,...] - The list of header keys to remove from the Uptime Check. + The list of header keys to remove from the uptime check. - Uptime check settings + Settings. --display-name=DISPLAY_NAME - The display name for the Uptime Check. + The display name for the uptime check or synthetic monitor. --period=PERIOD - How often, in minutes, the Uptime check is performed, defaults to - "1". PERIOD must be one of: + The time between uptime check or synthetic monitor executions in + minutes, defaults to 1. Can be set for synthetic monitors. + + PERIOD must be one of: 1 One minute @@ -238,14 +250,14 @@ FLAGS --timeout=TIMEOUT The maximum amount of time in seconds to wait for the request to - complete, defaults to "60". + complete, defaults to 60. Can be set for synthetic monitors. - Uptime Selected Regions. Cannot be used if --synthetic-target is set. + Uptime check selected regions. At most one of these can be specified: --add-regions=[region,...] - The list of regions to add to the Uptime Check. region must be one + The list of regions to add to the uptime check. region must be one of: asia-pacific @@ -262,11 +274,11 @@ FLAGS us-east4 --clear-regions=CLEAR_REGIONS - Clear all regions on the Uptime Check. This will act the same as if - all available regions were selected. + Clear all regions on the uptime check. This setting acts the same + as if all available regions were selected. --remove-regions=[region,...] - The list of regions to remove from the Uptime Check. region must be + The list of regions to remove from the uptime check. region must be one of: asia-pacific @@ -283,8 +295,8 @@ FLAGS us-east4 --set-regions=[region,...] - The list of regions from which the check will be run. At least 3 - regions must be selected. + The list of regions from which the check is run. At least 3 regions + must be selected. region must be one of: @@ -301,7 +313,7 @@ FLAGS usa-virginia us-east4 - uptime check + User labels. Can be set for synthetic monitors. --update-user-labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to update. If a label exists, its @@ -333,7 +345,7 @@ FLAGS silently ignored. If --update-user-labels is also specified then --update-user-labels is applied first. - Uptime matcher settings. Cannot be used if --synthetic-target is set. + Uptime check matcher settings. --matcher-content=MATCHER_CONTENT String, regex or JSON content to match. @@ -342,8 +354,8 @@ FLAGS this group are specified. --matcher-type=MATCHER_TYPE - The type of content matcher that will be applied to the server - output, defaults to "contains-string". + The type of content matcher that is applied to the server output, + defaults to contains-string. MATCHER_TYPE must be one of: @@ -360,20 +372,20 @@ FLAGS not-matches-regex Response does not match regex - Uptime matcher settings for JSON responses + Uptime check matcher settings for JSON responses. --json-path=JSON_PATH JSONPath within the response output pointing to the expected - content to match. Only used if matcher-type is "matches-json-path" - or "not-matches-json-path". + content to match. Only used if --matcher-type is matches-json-path + or not-matches-json-path. This flag argument must be specified if any of the other arguments in this group are specified. --json-path-matcher-type=JSON_PATH_MATCHER_TYPE - The type of JSONPath match that will be applied to the JSON output, - defaults to "exact-match". Only used if matcher-type is - "matches-json-path" or "not-matches-json-path". + The type of JSONPath match that is applied to the JSON output, + defaults to exact-match. Only used if --matcher-type is + matches-json-path or not-matches-json-path. JSON_PATH_MATCHER_TYPE must be one of: @@ -394,5 +406,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 monitoring uptime update + + $ gcloud beta monitoring uptime update diff --git a/gcloud/alpha/netapp/storage-pools/create b/gcloud/alpha/netapp/storage-pools/create index e2433d3c2..5562421ec 100644 --- a/gcloud/alpha/netapp/storage-pools/create +++ b/gcloud/alpha/netapp/storage-pools/create @@ -17,7 +17,7 @@ DESCRIPTION EXAMPLES The following command creates a Storage Pool named NAME using all possible - arguments + arguments with a VPC network in the same project $ gcloud alpha netapp storage-pools create NAME \ --location=us-central1 --service-level=standard \ @@ -25,6 +25,17 @@ EXAMPLES --kms-config=kms-config1 --enable-ldap=true \ --description="example description" + The following command creates a Storage pool named NAME using all possible + arguments with a shared VPC network in a separate project called + VPC_PROJECT + + $ gcloud alpha netapp storage-pools create NAME \ + --location=us-central1 --service-level=standard \ + --capacity=2048 \ + --network=name=projects/VPC_PROJECT/locations/us-central1/\ + networks/default --active-directory=ad1 --kms-config=kms-config1 \ + --enable-ldap=true --description="example description" + POSITIONAL ARGUMENTS Storage pool resource - The Storage Pool to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -68,7 +79,11 @@ REQUIRED FLAGS psa-range is optional. name The name of the Google Compute Engine VPC network to which the - volume is connected. + volume is connected. Short-form (VPC network ID) or long-form (full + VPC network name: + projects/PROJECT/locations/LOCATION/networks/NETWORK) are both + accepted, but please use the long-form when attempting to create a + Storage Pool using a shared VPC. psa-range The psa-range is the name of the allocated range of the Private Service Access connection. The range you specify can't overlap with diff --git a/gcloud/alpha/network-security/firewall-endpoint-associations/create b/gcloud/alpha/network-security/firewall-endpoint-associations/create index a7e61de8e..8d248579c 100644 --- a/gcloud/alpha/network-security/firewall-endpoint-associations/create +++ b/gcloud/alpha/network-security/firewall-endpoint-associations/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha network-security firewall-endpoint-associations create - (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) --network=NETWORK + [ASSOCIATION_ID] --network=NETWORK --zone=ZONE (--endpoint=ENDPOINT : --endpoint-zone=ENDPOINT_ZONE --organization=ORGANIZATION) [--async] [--labels=[KEY=VALUE,...]] @@ -26,44 +26,15 @@ EXAMPLES To associate a network with a firewall endpoint, run: $ gcloud alpha network-security firewall-endpoint-associations \ - create my-assoc \ - --network=projects/my-project/networks/global/myNetwork \ + create --network=projects/my-project/networks/global/myNetwork \ --endpoint=organizations/1234/locations/us-central1-a/\ firewallEndpoints/my-endpoint --zone=us-central1-a \ --project=my-project POSITIONAL ARGUMENTS - Firewall endpoint association resource - Firewall Plus. 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 FIREWALL_ENDPOINT_ASSOCIATION 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. - - FIREWALL_ENDPOINT_ASSOCIATION - ID of the firewall endpoint association or fully qualified identifier - for the firewall endpoint association. - - To set the association-name attribute: - ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command - line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - Zone of the firewall endpoint association. - - To set the zone attribute: - ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command - line with a fully specified name; - ▸ provide the argument --zone on the command line. + [ASSOCIATION_ID] + Name to give the association. If not specified, an auto-generated UUID + will be used. REQUIRED FLAGS Network resource - Firewall Plus. This represents a Cloud resource. (NOTE) @@ -84,6 +55,9 @@ REQUIRED FLAGS To set the network-name attribute: ▸ provide the argument --network on the command line. + --zone=ZONE + Zone of a firewall endpoint association + Firewall endpoint resource - Firewall Plus. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/alpha/redis/instances/create b/gcloud/alpha/redis/instances/create index 95eb75cdb..8e736c725 100644 --- a/gcloud/alpha/redis/instances/create +++ b/gcloud/alpha/redis/instances/create @@ -184,6 +184,8 @@ FLAGS Redis 6.x compatibility redis_7_0 Redis 7.0 compatibility + redis_7_2 + Redis 7.2 compatibility --replica-count=REPLICA_COUNT The replica count of the instance. diff --git a/gcloud/alpha/redis/instances/upgrade b/gcloud/alpha/redis/instances/upgrade index 5817a28f8..8a6176c39 100644 --- a/gcloud/alpha/redis/instances/upgrade +++ b/gcloud/alpha/redis/instances/upgrade @@ -65,6 +65,8 @@ REQUIRED FLAGS Redis 6.x compatibility redis_7_0 Redis 7.0 compatibility + redis_7_2 + Redis 7.2 compatibility OPTIONAL FLAGS --async diff --git a/gcloud/alpha/scc/posture-deployments/update b/gcloud/alpha/scc/posture-deployments/update index 19d5db697..666af7caa 100644 --- a/gcloud/alpha/scc/posture-deployments/update +++ b/gcloud/alpha/scc/posture-deployments/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha scc posture-deployments update POSTURE_DEPLOYMENT_NAME - [--description=DESCRIPTION] [--etag=ETAG] [--update-mask=UPDATE_MASK] + [--async] [--description=DESCRIPTION] [--etag=ETAG] + [--update-mask=UPDATE_MASK] [--posture-id=POSTURE_ID --posture-revision-id=POSTURE_REVISION_ID] [GCLOUD_WIDE_FLAG ...] @@ -40,6 +41,10 @@ POSITIONAL ARGUMENTS organizations//locations//postureDeployments/. FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + --description=DESCRIPTION Updated description of posture deployment. diff --git a/gcloud/alpha/spanner/migrate/cleanup b/gcloud/alpha/spanner/migrate/cleanup new file mode 100644 index 000000000..338cc8427 --- /dev/null +++ b/gcloud/alpha/spanner/migrate/cleanup @@ -0,0 +1,70 @@ +NAME + gcloud alpha spanner migrate cleanup - cleanup migration resources given a + data migration job id + +SYNOPSIS + gcloud alpha spanner migrate cleanup --job-id=JOB_ID + --target-profile=TARGET_PROFILE [--data-shard-ids=DATA_SHARD_IDS] + [--dataflow] [--datastream] [--log-level=LOG_LEVEL] [--monitoring] + [--pub-sub] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cleanup migration resources given a data migration job id. + +EXAMPLES + To cleanup resources for a data migration job, specify the jobId and the + boolean flags for the resources that need to be cleaned up. For sharded + migrations, specific data shard Ids can also be provided. + + For a all shards of a sharded migration, or a non-sharded migration: + $ gcloud alpha spanner migrate cleanup --job-id="XXX" \ + --target-profile="XXX" --datastream --dataflow --pub-sub \ + --monitoring + + For a subset of shards of a sharded migration: + $ gcloud alpha spanner migrate cleanup --job-id="XXX" \ + --data-shard-ids="lorem,epsum" --target-profile="XXX" \ + --datastream --dataflow --pub-sub --monitoring + +REQUIRED FLAGS + --job-id=JOB_ID + The job Id of an existing migration job. + + --target-profile=TARGET_PROFILE + Flag for specifying connection profile for target database (e.g., + "dialect=postgresql)". + +OPTIONAL FLAGS + --data-shard-ids=DATA_SHARD_IDS + Relevant to sharded migrations. Optional comma separated list of data + shard Ids, if nothing is specified, all shards are cleaned up. + + --dataflow + Cleanup dataflow resource(s). + + --datastream + Cleanup datastream resource(s). + + --log-level=LOG_LEVEL + To configure the log level for the execution (INFO, VERBOSE). + + --monitoring + Cleanup monitoring dashboard(s). + + --pub-sub + Cleanup pubsub resource(s). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/spanner/migrate/data b/gcloud/alpha/spanner/migrate/data index 7537fc8e5..a91e2c86b 100644 --- a/gcloud/alpha/spanner/migrate/data +++ b/gcloud/alpha/spanner/migrate/data @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud alpha spanner migrate data --session=SESSION --source=SOURCE - [--dry-run] [--log-level=LOG_LEVEL] [--prefix=PREFIX] - [--skip-foreign-keys] [--source-profile=SOURCE_PROFILE] - [--target=TARGET] [--target-profile=TARGET_PROFILE] + --target-profile=TARGET_PROFILE [--dry-run] [--log-level=LOG_LEVEL] + [--prefix=PREFIX] [--skip-foreign-keys] + [--source-profile=SOURCE_PROFILE] [--target=TARGET] [--write-limit=WRITE_LIMIT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -28,6 +28,10 @@ REQUIRED FLAGS Flag for specifying source database (e.g., PostgreSQL, MySQL, DynamoDB). + --target-profile=TARGET_PROFILE + Flag for specifying connection profile for target database (e.g., + "dialect=postgresql)". + OPTIONAL FLAGS --dry-run Flag for generating DDL and schema conversion report without creating a @@ -50,10 +54,6 @@ OPTIONAL FLAGS Specifies the target database, defaults to Spanner (accepted values: Spanner) (default "Spanner"). - --target-profile=TARGET_PROFILE - Flag for specifying connection profile for target database (e.g., - "dialect=postgresql)". - --write-limit=WRITE_LIMIT Number of parallel writers to Cloud Spanner during bulk data migrations (default 40). diff --git a/gcloud/alpha/spanner/migrate/help b/gcloud/alpha/spanner/migrate/help index b0fe20e83..5b8524032 100644 --- a/gcloud/alpha/spanner/migrate/help +++ b/gcloud/alpha/spanner/migrate/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + cleanup + (ALPHA) Cleanup migration resources given a data migration job id. + data (ALPHA) Migrate data from a source database to Cloud Spanner given a schema. diff --git a/gcloud/alpha/spanner/migrate/schema b/gcloud/alpha/spanner/migrate/schema index 6b04f2ddc..c37a6cd27 100644 --- a/gcloud/alpha/spanner/migrate/schema +++ b/gcloud/alpha/spanner/migrate/schema @@ -3,10 +3,10 @@ NAME to Cloud Spanner SYNOPSIS - gcloud alpha spanner migrate schema --source=SOURCE [--dry-run] - [--log-level=LOG_LEVEL] [--prefix=PREFIX] - [--source-profile=SOURCE_PROFILE] [--target=TARGET] - [--target-profile=TARGET_PROFILE] [GCLOUD_WIDE_FLAG ...] + gcloud alpha spanner migrate schema --source=SOURCE + --target-profile=TARGET_PROFILE [--dry-run] [--log-level=LOG_LEVEL] + [--prefix=PREFIX] [--source-profile=SOURCE_PROFILE] [--target=TARGET] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Migrate schema from a source database to Cloud Spanner. @@ -22,6 +22,10 @@ REQUIRED FLAGS Flag for specifying source database (e.g., PostgreSQL, MySQL, DynamoDB). + --target-profile=TARGET_PROFILE + Flag for specifying connection profile for target database (e.g., + "dialect=postgresql)". + OPTIONAL FLAGS --dry-run Flag for generating DDL and schema conversion report without creating a @@ -41,10 +45,6 @@ OPTIONAL FLAGS Specifies the target database, defaults to Spanner (accepted values: Spanner) (default "Spanner"). - --target-profile=TARGET_PROFILE - Flag for specifying connection profile for target database (e.g., - "dialect=postgresql)". - 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/spanner/migrate/schema-and-data b/gcloud/alpha/spanner/migrate/schema-and-data index fff9d7e69..92708d6f2 100644 --- a/gcloud/alpha/spanner/migrate/schema-and-data +++ b/gcloud/alpha/spanner/migrate/schema-and-data @@ -3,11 +3,11 @@ NAME database to Cloud Spanner given a schema SYNOPSIS - gcloud alpha spanner migrate schema-and-data --source=SOURCE [--dry-run] - [--log-level=LOG_LEVEL] [--prefix=PREFIX] [--skip-foreign-keys] + gcloud alpha spanner migrate schema-and-data --source=SOURCE + --target-profile=TARGET_PROFILE [--dry-run] [--log-level=LOG_LEVEL] + [--prefix=PREFIX] [--skip-foreign-keys] [--source-profile=SOURCE_PROFILE] [--target=TARGET] - [--target-profile=TARGET_PROFILE] [--write-limit=WRITE_LIMIT] - [GCLOUD_WIDE_FLAG ...] + [--write-limit=WRITE_LIMIT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Migrate data from a source database to Cloud Spanner given a @@ -24,6 +24,10 @@ REQUIRED FLAGS Flag for specifying source database (e.g., PostgreSQL, MySQL, DynamoDB). + --target-profile=TARGET_PROFILE + Flag for specifying connection profile for target database (e.g., + "dialect=postgresql)". + OPTIONAL FLAGS --dry-run Flag for generating DDL and schema conversion report without creating a @@ -46,10 +50,6 @@ OPTIONAL FLAGS Specifies the target database, defaults to Spanner (accepted values: Spanner) (default "Spanner"). - --target-profile=TARGET_PROFILE - Flag for specifying connection profile for target database (e.g., - "dialect=postgresql)". - --write-limit=WRITE_LIMIT Number of parallel writers to Cloud Spanner during bulk data migrations (default 40). diff --git a/gcloud/alpha/sql/backups/describe b/gcloud/alpha/sql/backups/describe index 13ecc8bbd..94aa1b934 100644 --- a/gcloud/alpha/sql/backups/describe +++ b/gcloud/alpha/sql/backups/describe @@ -2,7 +2,7 @@ NAME gcloud alpha sql backups describe - retrieves information about a backup SYNOPSIS - gcloud alpha sql backups describe ID --instance=INSTANCE, -i INSTANCE + gcloud alpha sql backups describe ID [--instance=INSTANCE, -i INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -10,10 +10,10 @@ DESCRIPTION POSITIONAL ARGUMENTS ID - The ID of the backup run. You can find the ID by running $ gcloud sql - backups list -i {instance}. + The ID of the backup run. To find the ID, run the following command: $ + gcloud sql backups list -i {instance}. -REQUIRED FLAGS +FLAGS --instance=INSTANCE, -i INSTANCE Cloud SQL instance ID. diff --git a/gcloud/alpha/sql/generate-login-token b/gcloud/alpha/sql/generate-login-token index 33e5c9657..f8253da4b 100644 --- a/gcloud/alpha/sql/generate-login-token +++ b/gcloud/alpha/sql/generate-login-token @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha sql generate-login-token [--application-default-credential] - [--instance=INSTANCE] [GCLOUD_WIDE_FLAG ...] + [--instance=INSTANCE, -i INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha sql generate-login-token generates an IAM token to use @@ -35,7 +35,7 @@ FLAGS --application-default-credential Use application default credentials to generate the login token. - --instance=INSTANCE + --instance=INSTANCE, -i INSTANCE Cloud SQL instance ID. GCLOUD WIDE FLAGS diff --git a/gcloud/alpha/storage/buckets/update b/gcloud/alpha/storage/buckets/update index e463c79fd..cd3a9b840 100644 --- a/gcloud/alpha/storage/buckets/update +++ b/gcloud/alpha/storage/buckets/update @@ -2,11 +2,11 @@ NAME gcloud alpha storage buckets update - update bucket settings SYNOPSIS - gcloud alpha storage buckets update URL [URL ...] + gcloud alpha storage buckets update [URL ...] [--additional-headers=HEADER=VALUE] [--clear-soft-delete] [--continue-on-error, -c] [--[no-]default-event-based-hold] [--default-storage-class=DEFAULT_STORAGE_CLASS] - [--lock-retention-period] + [--lock-retention-period] [--read-paths-from-stdin, -I] [--recovery-point-objective=SETTING, --rpo=SETTING] [--[no-]requester-pays] [--soft-delete-duration=SOFT_DELETE_DURATION] [--[no-]uniform-bucket-level-access] [--[no-]versioning] @@ -51,8 +51,8 @@ EXAMPLES --clear-retention-period POSITIONAL ARGUMENTS - URL [URL ...] - URLs of the buckets to update. + [URL ...] + Specifies the URLs of the buckets to update. FLAGS --additional-headers=HEADER=VALUE @@ -87,6 +87,9 @@ FLAGS duration. Once locked, deleting the bucket is the only way to "remove" a retention policy. + --read-paths-from-stdin, -I + Read the list of URLs from stdin. + --recovery-point-objective=SETTING, --rpo=SETTING Sets the recovery point objective (https://cloud.google.com/architecture/dr-scenarios-planning-guide#basics_of_dr_planning) diff --git a/gcloud/alpha/workstations/configs/create b/gcloud/alpha/workstations/configs/create index f1f932009..97739d373 100644 --- a/gcloud/alpha/workstations/configs/create +++ b/gcloud/alpha/workstations/configs/create @@ -11,8 +11,9 @@ SYNOPSIS [--container-env=[CONTAINER_ENV,...]] [--container-run-as-user=CONTAINER_RUN_AS_USER] [--container-working-dir=CONTAINER_WORKING_DIR] - [--disable-public-ip-addresses] [--enable-audit-agent] - [--enable-confidential-compute] [--enable-nested-virtualization] + [--disable-public-ip-addresses] [--disable-tcp-connections] + [--enable-audit-agent] [--enable-confidential-compute] + [--enable-nested-virtualization] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--network-tags=[NETWORK_TAGS,...]] @@ -139,6 +140,10 @@ FLAGS Default value is false. If set, instances will have no public IP address. + --disable-tcp-connections + Default value is false. If set, workstations will not allow plain TCP + connections. + --enable-audit-agent Whether to enable Linux auditd logging on the workstation. When enabled, a service account must also be specified that has diff --git a/gcloud/alpha/workstations/configs/update b/gcloud/alpha/workstations/configs/update index ae95273f3..2499da4c3 100644 --- a/gcloud/alpha/workstations/configs/update +++ b/gcloud/alpha/workstations/configs/update @@ -24,6 +24,7 @@ SYNOPSIS : --accelerator-type=ACCELERATOR_TYPE] [--container-custom-image=CONTAINER_CUSTOM_IMAGE | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE] + [--disable-tcp-connections | --enable-tcp-connections] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -243,6 +244,16 @@ FLAGS webstorm WebStorm + At most one of these can be specified: + + --disable-tcp-connections + Default value is false. If set, workstations will allow plain TCP + connections. + + --enable-tcp-connections + Default value is false. If set, workstations will allow plain TCP + connections. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/billing/budgets/create b/gcloud/beta/billing/budgets/create index 5c78bb876..93f1695dc 100644 --- a/gcloud/beta/billing/budgets/create +++ b/gcloud/beta/billing/budgets/create @@ -15,6 +15,7 @@ SYNOPSIS [--filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...]] [--filter-services=[FILTER_SERVICES,...]] [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]] + [--ownership-scope=OWNERSHIP_SCOPE] [--threshold-rule=[basis=BASIS],[percent=PERCENT]] [--calendar-period=CALENDAR_PERIOD | [--start-date=START_DATE : --end-date=END_DATE]] @@ -133,6 +134,20 @@ OPTIONAL FLAGS include usage from the parent account and all subaccounts, if they exist. + --ownership-scope=OWNERSHIP_SCOPE + Sets the ownership scope of the budget. The ownership scope and users' + IAM permissions determine who has full access to the budget's data. + + Must be one of: 'ALL_USERS' or 'BILLING_ACCOUNT'. Use 'ALL_USERS' to + allow billing account- level users and project-level users to have full + access to the budget (if the users have the required IAM permissions). + Use 'BILLING_ACCOUNT' to allow only billing account-level users to have + full access to the budget. Project-level users will have read-only + access, even if they have the required IAM permissions. + + OWNERSHIP_SCOPE must be one of: all-users, billing-account, + ownership-scope-unspecified. + --threshold-rule=[basis=BASIS],[percent=PERCENT] Rule that triggers alerts (notifications of thresholds being crossed) when spend exceeds the specified percentages of the budget. This flag diff --git a/gcloud/beta/billing/budgets/update b/gcloud/beta/billing/budgets/update index 53282e6fc..c2a0e1909 100644 --- a/gcloud/beta/billing/budgets/update +++ b/gcloud/beta/billing/budgets/update @@ -14,6 +14,7 @@ SYNOPSIS [--filter-resource-ancestors=[FILTER_RESOURCE_ANCESTORS,...]] [--filter-services=[FILTER_SERVICES,...]] [--filter-subaccounts=[FILTER_SUBACCOUNTS,...]] + [--ownership-scope=OWNERSHIP_SCOPE] [--budget-amount=BUDGET_AMOUNT | --last-period-amount] [--calendar-period=CALENDAR_PERIOD | [--start-date=START_DATE : --end-date=END_DATE]] @@ -134,6 +135,20 @@ FLAGS include usage from the parent account and all subaccounts, if they exist. + --ownership-scope=OWNERSHIP_SCOPE + Sets the ownership scope of the budget. The ownership scope and users' + IAM permissions determine who has full access to the budget's data. + + Must be one of: 'ALL_USERS' or 'BILLING_ACCOUNT'. Use 'ALL_USERS' to + allow billing account- level users and project-level users to have full + access to the budget (if the users have the required IAM permissions). + Use 'BILLING_ACCOUNT' to allow only billing account-level users to have + full access to the budget. Project-level users will have read-only + access, even if they have the required IAM permissions. + + OWNERSHIP_SCOPE must be one of: all-users, billing-account, + ownership-scope-unspecified. + At most one of these can be specified: --budget-amount=BUDGET_AMOUNT diff --git a/gcloud/beta/compute/instance-groups/managed/help b/gcloud/beta/compute/instance-groups/managed/help index 4928da7a1..64d8327be 100644 --- a/gcloud/beta/compute/instance-groups/managed/help +++ b/gcloud/beta/compute/instance-groups/managed/help @@ -75,6 +75,9 @@ COMMANDS resize (BETA) Set managed instance group size. + resume-instances + (BETA) Resume the suspended instances in a managed instance group. + set-autohealing (BETA) (DEPRECATED) Set autohealing policy for managed instance group. @@ -90,9 +93,18 @@ COMMANDS set-target-pools (BETA) Set target pools of managed instance group. + start-instances + (BETA) Start the stopped instances in a managed instance group. + stop-autoscaling (BETA) Stop autoscaling a managed instance group. + stop-instances + (BETA) Stop instances owned by a managed instance group. + + suspend-instances + (BETA) Suspend instances owned by a managed instance group. + update (BETA) Update a Compute Engine managed instance group. diff --git a/gcloud/beta/compute/instance-groups/managed/resume-instances b/gcloud/beta/compute/instance-groups/managed/resume-instances new file mode 100644 index 000000000..25c3ceebc --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/resume-instances @@ -0,0 +1,74 @@ +NAME + gcloud beta compute instance-groups managed resume-instances - resume the + suspended instances in a managed instance group + +SYNOPSIS + gcloud beta compute instance-groups managed resume-instances NAME + --instances=INSTANCE,[INSTANCE,...] [--region=REGION | --zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute instance-groups managed resume-instances resumes + one or more instances from a managed instance group, thereby increasing the + targetSize and reducing the targetSuspendedSize of the group. + + The command returns the operation status per instance, which might be FAIL, + SUCCESS, or MEMBER_NOT_FOUND. MEMBER_NOT_FOUND is returned only for + regional groups when the gcloud command-line tool wasn't able to resolve + the zone from the instance name. + +EXAMPLES + To resume an instance from a managed instance group in the us-central1-a + zone, run: + + $ gcloud beta compute instance-groups managed resume-instances \ + example-managed-instance-group --zone=us-central1-a \ + --instances=example-instance + +POSITIONAL ARGUMENTS + NAME + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --instances=INSTANCE,[INSTANCE,...] + Names of instances to resume. + +OPTIONAL FLAGS + At most one of these can be specified: + + --region=REGION + Region of the managed instance group to operate on. If not specified, + you might be prompted to select a region (interactive mode only). + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + Overrides the default compute/region property value for this command + invocation. + + --zone=ZONE + Zone of the managed instance group to operate on. If not specified, + you might be prompted to select a zone (interactive mode only). + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --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 compute instance-groups managed resume-instances + diff --git a/gcloud/beta/compute/instance-groups/managed/start-instances b/gcloud/beta/compute/instance-groups/managed/start-instances new file mode 100644 index 000000000..c506e73be --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/start-instances @@ -0,0 +1,74 @@ +NAME + gcloud beta compute instance-groups managed start-instances - start the + stopped instances in a managed instance group + +SYNOPSIS + gcloud beta compute instance-groups managed start-instances NAME + --instances=INSTANCE,[INSTANCE,...] [--region=REGION | --zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute instance-groups managed start-instances starts + one or more instances from a managed instance group, thereby increasing the + targetSize and reducing the targetStoppedSize of the group. + + The command returns the operation status per instance, which might be FAIL, + SUCCESS, or MEMBER_NOT_FOUND. MEMBER_NOT_FOUND is returned only for + regional groups when the gcloud command-line tool wasn't able to resolve + the zone from the instance name. + +EXAMPLES + To start an instance from a managed instance group in the us-central1-a + zone, run: + + $ gcloud beta compute instance-groups managed start-instances \ + example-managed-instance-group --zone=us-central1-a \ + --instances=example-instance + +POSITIONAL ARGUMENTS + NAME + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --instances=INSTANCE,[INSTANCE,...] + Names of instances to start. + +OPTIONAL FLAGS + At most one of these can be specified: + + --region=REGION + Region of the managed instance group to operate on. If not specified, + you might be prompted to select a region (interactive mode only). + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + Overrides the default compute/region property value for this command + invocation. + + --zone=ZONE + Zone of the managed instance group to operate on. If not specified, + you might be prompted to select a zone (interactive mode only). + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --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 compute instance-groups managed start-instances + diff --git a/gcloud/beta/compute/instance-groups/managed/stop-instances b/gcloud/beta/compute/instance-groups/managed/stop-instances new file mode 100644 index 000000000..dbf601239 --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/stop-instances @@ -0,0 +1,72 @@ +NAME + gcloud beta compute instance-groups managed stop-instances - stop instances + owned by a managed instance group + +SYNOPSIS + gcloud beta compute instance-groups managed stop-instances NAME + --instances=INSTANCE,[INSTANCE,...] [--force] + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute instance-groups managed stop-instances stops one + or more instances from a managed instance group + +EXAMPLES + To stop an instance from a managed instance group in the us-central1-a + zone, run: + + $ gcloud beta compute instance-groups managed stop-instances \ + example-managed-instance-group --zone=us-central1-a \ + --instances=example-instance + +POSITIONAL ARGUMENTS + NAME + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --instances=INSTANCE,[INSTANCE,...] + Names of instances to stop. + +OPTIONAL FLAGS + --force + Immediately stop the specified instances, skipping the initial delay, + if one is specified in the standby policy. + + At most one of these can be specified: + + --region=REGION + Region of the managed instance group to operate on. If not specified, + you might be prompted to select a region (interactive mode only). + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + Overrides the default compute/region property value for this command + invocation. + + --zone=ZONE + Zone of the managed instance group to operate on. If not specified, + you might be prompted to select a zone (interactive mode only). + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --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 compute instance-groups managed stop-instances + diff --git a/gcloud/beta/compute/instance-groups/managed/suspend-instances b/gcloud/beta/compute/instance-groups/managed/suspend-instances new file mode 100644 index 000000000..5d2f8ab65 --- /dev/null +++ b/gcloud/beta/compute/instance-groups/managed/suspend-instances @@ -0,0 +1,79 @@ +NAME + gcloud beta compute instance-groups managed suspend-instances - suspend + instances owned by a managed instance group + +SYNOPSIS + gcloud beta compute instance-groups managed suspend-instances NAME + --instances=INSTANCE,[INSTANCE,...] [--force] + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute instance-groups managed suspend-instances + suspends one or more instances from a managed instance group, thereby + reducing the targetSize and increasing the targetSuspendedSize of the + group. + + The command returns the operation status per instance, which might be FAIL, + SUCCESS, or MEMBER_NOT_FOUND. MEMBER_NOT_FOUND is returned only for + regional groups when the gcloud command-line tool wasn't able to resolve + the zone from the instance name. + +EXAMPLES + To suspend an instance from a managed instance group in the us-central1-a + zone, run: + + $ gcloud beta compute instance-groups managed suspend-instances \ + example-managed-instance-group --zone=us-central1-a \ + --instances=example-instance + +POSITIONAL ARGUMENTS + NAME + Name of the managed instance group to operate on. + +REQUIRED FLAGS + --instances=INSTANCE,[INSTANCE,...] + Names of instances to suspend. + +OPTIONAL FLAGS + --force + Immediately suspend the specified instances, skipping the initial + delay, if one is specified in the standby policy. + + At most one of these can be specified: + + --region=REGION + Region of the managed instance group to operate on. If not specified, + you might be prompted to select a region (interactive mode only). + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + Overrides the default compute/region property value for this command + invocation. + + --zone=ZONE + Zone of the managed instance group to operate on. If not specified, + you might be prompted to select a zone (interactive mode only). + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + Overrides the default compute/zone property value for this command + invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --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 compute instance-groups managed suspend-instances + diff --git a/gcloud/beta/compute/instance-templates/create b/gcloud/beta/compute/instance-templates/create index 5e78772df..e475534b8 100644 --- a/gcloud/beta/compute/instance-templates/create +++ b/gcloud/beta/compute/instance-templates/create @@ -931,12 +931,16 @@ FLAGS Computing can be based on Secure Encrypted Virtualization (SEV) or Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both of which are AMD virtualization features for running - confidential instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + confidential instances. Trust Domain eXtension based on Intel + virtualization features for running confidential instances is also + supported. CONFIDENTIAL_COMPUTE_TYPE must be one of: SEV Secure Encrypted Virtualization SEV_SNP Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension Custom machine type extensions. diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index 148f029ab..d4f0def92 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -845,12 +845,16 @@ OPTIONAL FLAGS Computing can be based on Secure Encrypted Virtualization (SEV) or Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both of which are AMD virtualization features for running - confidential instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + confidential instances. Trust Domain eXtension based on Intel + virtualization features for running confidential instances is also + supported. CONFIDENTIAL_COMPUTE_TYPE must be one of: SEV Secure Encrypted Virtualization SEV_SNP Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension Custom machine type extensions. diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index a7ce9c052..b46868841 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -1010,12 +1010,16 @@ FLAGS Computing can be based on Secure Encrypted Virtualization (SEV) or Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both of which are AMD virtualization features for running - confidential instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + confidential instances. Trust Domain eXtension based on Intel + virtualization features for running confidential instances is also + supported. CONFIDENTIAL_COMPUTE_TYPE must be one of: SEV Secure Encrypted Virtualization SEV_SNP Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension Custom machine type extensions. diff --git a/gcloud/beta/compute/instances/create-with-container b/gcloud/beta/compute/instances/create-with-container index cc079ffd3..0f8dd2cea 100644 --- a/gcloud/beta/compute/instances/create-with-container +++ b/gcloud/beta/compute/instances/create-with-container @@ -793,12 +793,16 @@ FLAGS Computing can be based on Secure Encrypted Virtualization (SEV) or Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both of which are AMD virtualization features for running - confidential instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + confidential instances. Trust Domain eXtension based on Intel + virtualization features for running confidential instances is also + supported. CONFIDENTIAL_COMPUTE_TYPE must be one of: SEV Secure Encrypted Virtualization SEV_SNP Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension Custom machine type extensions. diff --git a/gcloud/beta/compute/instances/perform-maintenance b/gcloud/beta/compute/instances/perform-maintenance index df53d9f9e..3dc4fabc9 100644 --- a/gcloud/beta/compute/instances/perform-maintenance +++ b/gcloud/beta/compute/instances/perform-maintenance @@ -10,7 +10,7 @@ DESCRIPTION (BETA) Perform maintenance of Google Compute Engine instance. EXAMPLES - To perform a customer trigged maintenance on an instance named + To perform customer-triggered maintenance on an instance named test-instance located in zone us-east1-d, run: $ gcloud beta compute instances perform-maintenance test-instance \ diff --git a/gcloud/beta/dataproc/clusters/diagnose b/gcloud/beta/dataproc/clusters/diagnose index 58d2b6514..1685c86ca 100644 --- a/gcloud/beta/dataproc/clusters/diagnose +++ b/gcloud/beta/dataproc/clusters/diagnose @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud beta dataproc clusters diagnose (CLUSTER : --region=REGION) - [GCLOUD_WIDE_FLAG ...] + [--end-time=END_TIME] [--job-ids=JOB_IDS] [--start-time=START_TIME] + [--tarball-access=TARBALL_ACCESS] + [--yarn-application-ids=YARN_APPLICATION_IDS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Run a detailed diagnostic on a cluster. @@ -50,6 +52,25 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property dataproc/region. +FLAGS + --end-time=END_TIME + Time instant to stop the diagnosis at (in %Y-%m-%dT%H:%M:%S.%fZ + format). + + --job-ids=JOB_IDS + A list of jobs on which to perform the diagnosis. + + --start-time=START_TIME + Time instant to start the diagnosis from (in %Y-%m-%dT%H:%M:%S.%fZ + format). + + --tarball-access=TARBALL_ACCESS + Target access privileges for diagnose tarball. TARBALL_ACCESS must be + one of: GOOGLE_CLOUD_SUPPORT, GOOGLE_DATAPROC_DIAGNOSE. + + --yarn-application-ids=YARN_APPLICATION_IDS + A list of yarn applications on which to perform the diagnosis. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/domains/registrations/get-transfer-parameters b/gcloud/beta/domains/registrations/get-transfer-parameters index a2edf64de..582f9ff9b 100644 --- a/gcloud/beta/domains/registrations/get-transfer-parameters +++ b/gcloud/beta/domains/registrations/get-transfer-parameters @@ -7,9 +7,14 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Get parameters needed to transfer an existing domain from a - different registrar. The parameters include the current registrar, name - servers, transfer lock state, price, and supported privacy modes. + (BETA) (DEPRECATED) Get transfer parameters of a specific domain. + + This command is deprecated. See + https://cloud.google.com/domains/docs/deprecations/feature-deprecations. + + Get parameters needed to transfer an existing domain from a different + registrar. The parameters include the current registrar, name servers, + transfer lock state, price, and supported privacy modes. EXAMPLES To check if example.com is available for transfer, run: diff --git a/gcloud/beta/domains/registrations/help b/gcloud/beta/domains/registrations/help index ff6058aa7..04e59b2b4 100644 --- a/gcloud/beta/domains/registrations/help +++ b/gcloud/beta/domains/registrations/help @@ -42,7 +42,7 @@ COMMANDS domain. get-transfer-parameters - (BETA) Get transfer parameters of a specific domain. + (BETA) (DEPRECATED) Get transfer parameters of a specific domain. import (BETA) (DEPRECATED) Import a domain from Google Domains registrar to @@ -52,7 +52,8 @@ COMMANDS (BETA) List Cloud Domains registrations. list-importable-domains - (BETA) List Google Domains registrations importable into Cloud Domains. + (BETA) (DEPRECATED) List Google Domains registrations importable into + Cloud Domains. register (BETA) Register a new domain. diff --git a/gcloud/beta/domains/registrations/list-importable-domains b/gcloud/beta/domains/registrations/list-importable-domains index 8324030d7..1823cd491 100644 --- a/gcloud/beta/domains/registrations/list-importable-domains +++ b/gcloud/beta/domains/registrations/list-importable-domains @@ -8,8 +8,14 @@ SYNOPSIS [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Google Domains registrations that can be imported to a Cloud - Domains project. + (BETA) (DEPRECATED) List Google Domains registrations importable into Cloud + Domains. + + This command is deprecated. See + https://cloud.google.com/domains/docs/deprecations/feature-deprecations. + + List Google Domains registrations that can be imported to a Cloud Domains + project. Registrations with an IMPORTABLE resource state can be imported from Google Domains registrar to Cloud Domains. diff --git a/gcloud/beta/eventarc/attributes/help b/gcloud/beta/eventarc/attributes/help index 78c818e1a..5add653c9 100644 --- a/gcloud/beta/eventarc/attributes/help +++ b/gcloud/beta/eventarc/attributes/help @@ -6,7 +6,9 @@ SYNOPSIS gcloud beta eventarc attributes GROUP [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Explore CloudEvents attributes in Eventarc. + (BETA) (DEPRECATED) Explore CloudEvents attributes in Eventarc. + + This command is deprecated. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,13 +19,15 @@ GROUPS GROUP is one of the following: method-names - (BETA) Explore values for the methodName CloudEvents attribute. + (BETA) (DEPRECATED) Explore values for the methodName CloudEvents + attribute. service-names - (BETA) Explore values for the serviceName CloudEvents attribute. + (BETA) (DEPRECATED) Explore values for the serviceName CloudEvents + attribute. types - (BETA) Explore event types in Eventarc. + (BETA) (DEPRECATED) Explore event types in Eventarc. NOTES This command is currently in beta and might change without notice. diff --git a/gcloud/beta/eventarc/attributes/method-names/help b/gcloud/beta/eventarc/attributes/method-names/help index d9164e777..daf1d379e 100644 --- a/gcloud/beta/eventarc/attributes/method-names/help +++ b/gcloud/beta/eventarc/attributes/method-names/help @@ -6,7 +6,10 @@ SYNOPSIS gcloud beta eventarc attributes method-names COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Explore values for the methodName CloudEvents attribute. + (BETA) (DEPRECATED) Explore values for the methodName CloudEvents + attribute. + + This command is deprecated. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -17,7 +20,8 @@ COMMANDS COMMAND is one of the following: list - (BETA) List values for the methodName CloudEvents attribute. + (BETA) (DEPRECATED) List values for the methodName CloudEvents + attribute. NOTES This command is currently in beta and might change without notice. diff --git a/gcloud/beta/eventarc/attributes/method-names/list b/gcloud/beta/eventarc/attributes/method-names/list index 69e3accfe..362359af1 100644 --- a/gcloud/beta/eventarc/attributes/method-names/list +++ b/gcloud/beta/eventarc/attributes/method-names/list @@ -8,7 +8,11 @@ SYNOPSIS [--limit=LIMIT] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List values for the methodName CloudEvents attribute. + (BETA) (DEPRECATED) This command is deprecated. + + (BETA) (DEPRECATED) List values for the methodName CloudEvents attribute. + + This command is deprecated. EXAMPLES To list methodName values for event type google.cloud.audit.log.v1.written diff --git a/gcloud/beta/eventarc/attributes/service-names/help b/gcloud/beta/eventarc/attributes/service-names/help index a1f180cfb..d24484c02 100644 --- a/gcloud/beta/eventarc/attributes/service-names/help +++ b/gcloud/beta/eventarc/attributes/service-names/help @@ -7,7 +7,10 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Explore values for the serviceName CloudEvents attribute. + (BETA) (DEPRECATED) Explore values for the serviceName CloudEvents + attribute. + + This command is deprecated. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -18,7 +21,8 @@ COMMANDS COMMAND is one of the following: list - (BETA) List values for the serviceName CloudEvents attribute. + (BETA) (DEPRECATED) List values for the serviceName CloudEvents + attribute. NOTES This command is currently in beta and might change without notice. diff --git a/gcloud/beta/eventarc/attributes/service-names/list b/gcloud/beta/eventarc/attributes/service-names/list index 1f0403997..28f78ddad 100644 --- a/gcloud/beta/eventarc/attributes/service-names/list +++ b/gcloud/beta/eventarc/attributes/service-names/list @@ -8,7 +8,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List values for the serviceName CloudEvents attribute. + (BETA) (DEPRECATED) This command is deprecated. + + (BETA) (DEPRECATED) List values for the serviceName CloudEvents attribute. + + This command is deprecated. EXAMPLES To list serviceName values for event type diff --git a/gcloud/beta/eventarc/attributes/types/describe b/gcloud/beta/eventarc/attributes/types/describe index 12aa14efb..415f60c0e 100644 --- a/gcloud/beta/eventarc/attributes/types/describe +++ b/gcloud/beta/eventarc/attributes/types/describe @@ -5,7 +5,11 @@ SYNOPSIS gcloud beta eventarc attributes types describe TYPE [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe an event type. + (BETA) (DEPRECATED) This command is deprecated. + + (BETA) (DEPRECATED) Describe an event type. + + This command is deprecated. EXAMPLES To describe the google.cloud.audit.log.v1.written event type, run: diff --git a/gcloud/beta/eventarc/attributes/types/help b/gcloud/beta/eventarc/attributes/types/help index f18e35d44..698b9351c 100644 --- a/gcloud/beta/eventarc/attributes/types/help +++ b/gcloud/beta/eventarc/attributes/types/help @@ -5,7 +5,9 @@ SYNOPSIS gcloud beta eventarc attributes types COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Explore event types in Eventarc. + (BETA) (DEPRECATED) Explore event types in Eventarc. + + This command is deprecated. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -16,10 +18,10 @@ COMMANDS COMMAND is one of the following: describe - (BETA) Describe an event type. + (BETA) (DEPRECATED) Describe an event type. list - (BETA) List event types in Eventarc. + (BETA) (DEPRECATED) List event types in Eventarc. NOTES This command is currently in beta and might change without notice. diff --git a/gcloud/beta/eventarc/attributes/types/list b/gcloud/beta/eventarc/attributes/types/list index dc01dbbaf..ce77ed561 100644 --- a/gcloud/beta/eventarc/attributes/types/list +++ b/gcloud/beta/eventarc/attributes/types/list @@ -6,7 +6,11 @@ SYNOPSIS [--limit=LIMIT] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List event types in Eventarc. + (BETA) (DEPRECATED) This command is deprecated. + + (BETA) (DEPRECATED) List event types in Eventarc. + + This command is deprecated. EXAMPLES To list all supported event types, run: diff --git a/gcloud/beta/eventarc/help b/gcloud/beta/eventarc/help index 9dd7e8fa9..bd4c1fa1c 100644 --- a/gcloud/beta/eventarc/help +++ b/gcloud/beta/eventarc/help @@ -5,7 +5,9 @@ SYNOPSIS gcloud beta eventarc GROUP [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Manage Eventarc resources. + (BETA) (DEPRECATED) Manage Eventarc resources. + + This command is deprecated. Please use gcloud eventarc instead. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -16,13 +18,13 @@ GROUPS GROUP is one of the following: attributes - (BETA) Explore CloudEvents attributes in Eventarc. + (BETA) (DEPRECATED) Explore CloudEvents attributes in Eventarc. locations - (BETA) Explore locations available for Eventarc. + (BETA) (DEPRECATED) Explore locations available for Eventarc. triggers - (BETA) Manage Eventarc triggers. + (BETA) (DEPRECATED) Manage Eventarc triggers. NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/eventarc/locations/help b/gcloud/beta/eventarc/locations/help index 38bdb95a0..fd678bff5 100644 --- a/gcloud/beta/eventarc/locations/help +++ b/gcloud/beta/eventarc/locations/help @@ -5,7 +5,9 @@ SYNOPSIS gcloud beta eventarc locations COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Explore locations available for Eventarc. + (BETA) (DEPRECATED) Explore locations available for Eventarc. + + This command is deprecated. Please use gcloud eventarc locations instead. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -16,7 +18,7 @@ COMMANDS COMMAND is one of the following: list - (BETA) List locations available for Eventarc. + (BETA) (DEPRECATED) List locations available for Eventarc. NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/eventarc/locations/list b/gcloud/beta/eventarc/locations/list index 7e0749908..2064c4050 100644 --- a/gcloud/beta/eventarc/locations/list +++ b/gcloud/beta/eventarc/locations/list @@ -7,7 +7,13 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List locations available for Eventarc. + (BETA) (DEPRECATED) This command is deprecated. Please use gcloud eventarc + locations list instead. + + (BETA) (DEPRECATED) List locations available for Eventarc. + + This command is deprecated. Please use gcloud eventarc locations list + instead. EXAMPLES To list all locations, run: diff --git a/gcloud/beta/eventarc/triggers/create b/gcloud/beta/eventarc/triggers/create index 74d8d8386..dfa7043fe 100644 --- a/gcloud/beta/eventarc/triggers/create +++ b/gcloud/beta/eventarc/triggers/create @@ -11,7 +11,13 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create an Eventarc trigger. + (BETA) (DEPRECATED) This command is deprecated. Please use gcloud eventarc + triggers create instead. + + (BETA) (DEPRECATED) Create an Eventarc trigger. + + This command is deprecated. Please use gcloud eventarc triggers create + instead. EXAMPLES To create a new trigger my-trigger for events of type diff --git a/gcloud/beta/eventarc/triggers/delete b/gcloud/beta/eventarc/triggers/delete index 71146a6e5..37f1977f3 100644 --- a/gcloud/beta/eventarc/triggers/delete +++ b/gcloud/beta/eventarc/triggers/delete @@ -6,7 +6,13 @@ SYNOPSIS [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete an Eventarc trigger. + (BETA) (DEPRECATED) This command is deprecated. Please use gcloud eventarc + triggers delete instead. + + (BETA) (DEPRECATED) Delete an Eventarc trigger. + + This command is deprecated. Please use gcloud eventarc triggers delete + instead. EXAMPLES To delete the trigger my-trigger, run: diff --git a/gcloud/beta/eventarc/triggers/describe b/gcloud/beta/eventarc/triggers/describe index 68e62f059..e272146ac 100644 --- a/gcloud/beta/eventarc/triggers/describe +++ b/gcloud/beta/eventarc/triggers/describe @@ -6,7 +6,13 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describe an Eventarc trigger. + (BETA) (DEPRECATED) This command is deprecated. Please use gcloud eventarc + triggers describe instead. + + (BETA) (DEPRECATED) Describe an Eventarc trigger. + + This command is deprecated. Please use gcloud eventarc triggers describe + instead. EXAMPLES To describe the trigger my-trigger, run: diff --git a/gcloud/beta/eventarc/triggers/help b/gcloud/beta/eventarc/triggers/help index b5ef23167..6c141f617 100644 --- a/gcloud/beta/eventarc/triggers/help +++ b/gcloud/beta/eventarc/triggers/help @@ -5,7 +5,9 @@ SYNOPSIS gcloud beta eventarc triggers COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Manage Eventarc triggers. + (BETA) (DEPRECATED) Manage Eventarc triggers. + + This command is deprecated. Please use gcloud eventarc triggers instead. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -16,19 +18,19 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create an Eventarc trigger. + (BETA) (DEPRECATED) Create an Eventarc trigger. delete - (BETA) Delete an Eventarc trigger. + (BETA) (DEPRECATED) Delete an Eventarc trigger. describe - (BETA) Describe an Eventarc trigger. + (BETA) (DEPRECATED) Describe an Eventarc trigger. list - (BETA) List Eventarc triggers. + (BETA) (DEPRECATED) List Eventarc triggers. update - (BETA) Update an Eventarc trigger. + (BETA) (DEPRECATED) Update an Eventarc trigger. NOTES This command is currently in beta and might change without notice. This diff --git a/gcloud/beta/eventarc/triggers/list b/gcloud/beta/eventarc/triggers/list index b153c95b9..1c9a1fb80 100644 --- a/gcloud/beta/eventarc/triggers/list +++ b/gcloud/beta/eventarc/triggers/list @@ -7,7 +7,13 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List Eventarc triggers. + (BETA) (DEPRECATED) This command is deprecated. Please use gcloud eventarc + triggers list instead. + + (BETA) (DEPRECATED) List Eventarc triggers. + + This command is deprecated. Please use gcloud eventarc triggers list + instead. EXAMPLES To list all triggers in location us-central1, run: diff --git a/gcloud/beta/eventarc/triggers/update b/gcloud/beta/eventarc/triggers/update index f3f4e810b..9a409c695 100644 --- a/gcloud/beta/eventarc/triggers/update +++ b/gcloud/beta/eventarc/triggers/update @@ -11,7 +11,13 @@ SYNOPSIS | --destination-run-path=DESTINATION_RUN_PATH] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update an Eventarc trigger. + (BETA) (DEPRECATED) This command is deprecated. Please use gcloud eventarc + triggers update instead. + + (BETA) (DEPRECATED) Update an Eventarc trigger. + + This command is deprecated. Please use gcloud eventarc triggers update + instead. EXAMPLES To update the trigger my-trigger by setting its destination Cloud Run diff --git a/gcloud/beta/functions/add-iam-policy-binding b/gcloud/beta/functions/add-iam-policy-binding index 349912ea5..19a192140 100644 --- a/gcloud/beta/functions/add-iam-policy-binding +++ b/gcloud/beta/functions/add-iam-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta functions add-iam-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL --role=ROLE [--gen2] [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Adds an IAM policy binding for a Google Cloud Function. @@ -70,15 +70,6 @@ REQUIRED FLAGS for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer. -OPTIONAL FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/functions/add-invoker-policy-binding b/gcloud/beta/functions/add-invoker-policy-binding index 77f4ae5a3..db6fb0a92 100644 --- a/gcloud/beta/functions/add-invoker-policy-binding +++ b/gcloud/beta/functions/add-invoker-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta functions add-invoker-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL [--gen2] [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Adds an invoker role IAM policy binding that allows the specified @@ -71,15 +71,6 @@ REQUIRED FLAGS ◆ allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account. -OPTIONAL FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/functions/call b/gcloud/beta/functions/call index 799a3d795..7caee0152 100644 --- a/gcloud/beta/functions/call +++ b/gcloud/beta/functions/call @@ -2,7 +2,7 @@ NAME gcloud beta functions call - triggers execution of a Google Cloud Function SYNOPSIS - gcloud beta functions call (NAME : --region=REGION) [--gen2] + gcloud beta functions call (NAME : --region=REGION) [--cloud-event=CLOUD_EVENT | --data=DATA] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -56,14 +56,6 @@ POSITIONAL ARGUMENTS ▸ set the property functions/region. FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - At most one of these can be specified: --cloud-event=CLOUD_EVENT diff --git a/gcloud/beta/functions/delete b/gcloud/beta/functions/delete index db1a06165..9089249ce 100644 --- a/gcloud/beta/functions/delete +++ b/gcloud/beta/functions/delete @@ -2,7 +2,7 @@ NAME gcloud beta functions delete - delete a Google Cloud Function SYNOPSIS - gcloud beta functions delete (NAME : --region=REGION) [--gen2] + gcloud beta functions delete (NAME : --region=REGION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -41,15 +41,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property functions/region. -FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/functions/describe b/gcloud/beta/functions/describe index 826b81fda..e7366e659 100644 --- a/gcloud/beta/functions/describe +++ b/gcloud/beta/functions/describe @@ -2,7 +2,7 @@ NAME gcloud beta functions describe - display details of a Google Cloud Function SYNOPSIS - gcloud beta functions describe (NAME : --region=REGION) [--gen2] + gcloud beta functions describe (NAME : --region=REGION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -41,15 +41,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property functions/region. -FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/functions/get-iam-policy b/gcloud/beta/functions/get-iam-policy index 6bc798e9d..7a1504641 100644 --- a/gcloud/beta/functions/get-iam-policy +++ b/gcloud/beta/functions/get-iam-policy @@ -3,7 +3,7 @@ NAME Function SYNOPSIS - gcloud beta functions get-iam-policy (NAME : --region=REGION) [--gen2] + gcloud beta functions get-iam-policy (NAME : --region=REGION) [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -48,15 +48,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property functions/region. -FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/functions/remove-iam-policy-binding b/gcloud/beta/functions/remove-iam-policy-binding index b2e98a041..02db20bcb 100644 --- a/gcloud/beta/functions/remove-iam-policy-binding +++ b/gcloud/beta/functions/remove-iam-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta functions remove-iam-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL --role=ROLE [--gen2] [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Removes an IAM policy binding from a Google Cloud Function. @@ -71,15 +71,6 @@ REQUIRED FLAGS --role=ROLE The role to remove the principal from. -OPTIONAL FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/functions/remove-invoker-policy-binding b/gcloud/beta/functions/remove-invoker-policy-binding index 79f83d876..8e403e921 100644 --- a/gcloud/beta/functions/remove-invoker-policy-binding +++ b/gcloud/beta/functions/remove-invoker-policy-binding @@ -4,8 +4,7 @@ NAME SYNOPSIS gcloud beta functions remove-invoker-policy-binding - (NAME : --region=REGION) --member=PRINCIPAL [--gen2] - [GCLOUD_WIDE_FLAG ...] + (NAME : --region=REGION) --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Removes the invoker role IAM policy binding that allows the @@ -77,15 +76,6 @@ REQUIRED FLAGS ◆ allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account. -OPTIONAL FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/functions/set-iam-policy b/gcloud/beta/functions/set-iam-policy index 85a564d3f..44d7202b4 100644 --- a/gcloud/beta/functions/set-iam-policy +++ b/gcloud/beta/functions/set-iam-policy @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta functions set-iam-policy (NAME : --region=REGION) POLICY_FILE - [--gen2] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Sets IAM policy for a Google Cloud Function. @@ -51,15 +51,6 @@ POSITIONAL ARGUMENTS POLICY_FILE Path to a local JSON or YAML formatted file containing a valid policy. -FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/healthcare/dicom-stores/help b/gcloud/beta/healthcare/dicom-stores/help index b81d22f0b..da270eed8 100644 --- a/gcloud/beta/healthcare/dicom-stores/help +++ b/gcloud/beta/healthcare/dicom-stores/help @@ -47,6 +47,9 @@ COMMANDS list (BETA) List Cloud Healthcare API DICOM stores. + metrics + (BETA) Get the metrics for a Cloud Healthcare API DICOM store. + remove-iam-policy-binding (BETA) Remove an IAM policy binding from a Cloud Healthcare API DICOM store. diff --git a/gcloud/beta/healthcare/dicom-stores/metrics b/gcloud/beta/healthcare/dicom-stores/metrics new file mode 100644 index 000000000..834401105 --- /dev/null +++ b/gcloud/beta/healthcare/dicom-stores/metrics @@ -0,0 +1,79 @@ +NAME + gcloud beta healthcare dicom-stores metrics - get the metrics for a Cloud + Healthcare API DICOM store + +SYNOPSIS + gcloud beta healthcare dicom-stores metrics + (DICOM_STORE : --dataset=DATASET --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Gets the metrics for a Cloud Healthcare API DICOM store. + +EXAMPLES + To get metrics for the DICOM store 'test-dicom-store', run: + + $ gcloud beta healthcare dicom-stores metrics test-dicom-store \ + --dataset=test-dataset + +POSITIONAL ARGUMENTS + DicomStore resource - Cloud Healthcare API DICOM store to get metrics for. + 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 dicom_store 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. + + DICOM_STORE + ID of the dicomStore or fully qualified identifier for the + dicomStore. + + To set the dicom_store attribute: + ▸ provide the argument dicom_store on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --dataset=DATASET + Cloud Healthcare dataset. + + To set the dataset attribute: + ▸ provide the argument dicom_store on the command line with a fully + specified name; + ▸ provide the argument --dataset on the command line. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument dicom_store on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property healthcare/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 healthcare/v1beta1 API. The full documentation for + this API can be found at: https://cloud.google.com/healthcare + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud healthcare dicom-stores metrics + + $ gcloud alpha healthcare dicom-stores metrics + diff --git a/gcloud/beta/monitoring/help b/gcloud/beta/monitoring/help index 9d4d5fcc3..86b48e296 100644 --- a/gcloud/beta/monitoring/help +++ b/gcloud/beta/monitoring/help @@ -36,6 +36,9 @@ GROUPS snoozes (BETA) Manage Cloud Monitoring snoozes. + uptime + (BETA) Manage Cloud Monitoring uptime checks and synthetic monitors. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/monitoring/uptime/create b/gcloud/beta/monitoring/uptime/create new file mode 100644 index 000000000..4fcbebf6e --- /dev/null +++ b/gcloud/beta/monitoring/uptime/create @@ -0,0 +1,328 @@ +NAME + gcloud beta monitoring uptime create - create a new uptime check or + synthetic monitor + +SYNOPSIS + gcloud beta monitoring uptime create DISPLAY_NAME + (--synthetic-target=SYNTHETIC_TARGET + | [--group-id=GROUP_ID : --group-type=GROUP_TYPE] + | [--resource-labels=[KEY=VALUE,...] + : --resource-type=RESOURCE_TYPE]) + [--body=BODY --content-type=CONTENT_TYPE + --custom-content-type=CUSTOM_CONTENT_TYPE --headers=[KEY=VALUE,...] + --mask-headers=MASK_HEADERS --password=PASSWORD --path=PATH + --pings-count=PINGS_COUNT --port=PORT --protocol=PROTOCOL + --request-method=REQUEST_METHOD --username=USERNAME + --validate-ssl=VALIDATE_SSL --status-classes=[status-class,...] + | --status-codes=[status-code,...]] + [--matcher-content=MATCHER_CONTENT + : --matcher-type=MATCHER_TYPE [--json-path=JSON_PATH + : --json-path-matcher-type=JSON_PATH_MATCHER_TYPE]] + [--period=PERIOD --regions=[field,...] + --timeout=TIMEOUT --user-labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new uptime check or synthetic monitor. + + Flags only apply to uptime checks unless noted that they apply to synthetic + monitors. + + For information about the JSON/YAML format of an uptime check: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.uptimeCheckConfigs + +EXAMPLES + To create an uptime check against a URL, run: + + $ gcloud beta monitoring uptime create DISPLAY_NAME \ + --resource-type=uptime-url \ + --resource-labels=host=google.com,project_id=PROJECT_ID + + To create a synthetic monitor, run: + + $ gcloud beta monitoring uptime create SYNTHETIC_MONITOR_NAME \ + --synthetic-target=projects/PROJECT_ID/locations/REGION/\ + functions/FUNCTION_NAME + +POSITIONAL ARGUMENTS + DISPLAY_NAME + Display name for the uptime check or synthetic monitor. + +REQUIRED FLAGS + Uptime check resource. + + Exactly one of these must be specified: + + --synthetic-target=SYNTHETIC_TARGET + The target of the Synthetic Monitor. This is the fully qualified + GCFv2 resource name. + + Monitored resource group + + --group-id=GROUP_ID + The group of resources being monitored. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --group-type=GROUP_TYPE + The resource type of the group members, defaults to gce-instance. + GROUP_TYPE must be one of: + + aws-elb-load-balancer + Uptime check against a group of Amazon ELB load balancers. + gce-instance + Uptime check against a group of instances from Google Cloud or + Amazon Web Services. + + Monitored resource + + --resource-labels=[KEY=VALUE,...] + Values for all of the labels listed in the associated monitored + resource descriptor. See + https://cloud.google.com/monitoring/api/resources for more + information and allowed keys. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --resource-type=RESOURCE_TYPE + Type of monitored resource, defaults to uptime-url. RESOURCE_TYPE + must be one of: + + aws-ec2-instance + Uptime check against an AWS EC2 instance. + aws-elb-load-balancer + Uptime check against an ElasticLoadBalancer. + cloud-run-revision + Uptime check against a Cloud Run revision. + gae-app + Uptime check against an App Engine module. + gce-instance + Uptime check against a Compute Engine instance. + servicedirectory-service + Uptime check against a Service Directory service. + uptime-url + Uptime check against a URL. + +OPTIONAL FLAGS + Uptime check protocol settings. + + --body=BODY + The request body associated with the HTTP POST request. Can only be + set if --protocol is http or https. + + --content-type=CONTENT_TYPE + The content type header to use for the check, defaults to + unspecified. Can only be set if --protocol is http or https. + + CONTENT_TYPE must be one of: + + unspecified + Not specified + url-encoded + URL encoded + user-provided + User provided + + --custom-content-type=CUSTOM_CONTENT_TYPE + A user-provided content type header to use for the check. Can only be + set if --protocol is http or https. + + --headers=[KEY=VALUE,...] + The list of headers to send as part of the uptime check request. Can + only be set if --protocol is http or https. + + --mask-headers=MASK_HEADERS + Whether to encrypt the header information, defaults to false. Can + only be set if --protocol is http or https. + + --password=PASSWORD + The password to use when authenticating with the HTTP server. Can + only be set if --protocol is http or https. + + --path=PATH + The path to the page against which to run the check, defaults to /. + Can only be set if --protocol is http or https. + + --pings-count=PINGS_COUNT + Number of ICMP pings to send alongside the request. + + --port=PORT + The port on the server against which to run the check. Defaults to 80 + when --protocol is http. Defaults to 443 when --protocol is https. + Required if --protocol is tcp. + + --protocol=PROTOCOL + The protocol of the request, defaults to http. PROTOCOL must be one + of: + + http + An HTTP check. + https + An HTTPS check. + tcp + A TCP check. + + --request-method=REQUEST_METHOD + The HTTP request method to use, defaults to get. Can only be set if + --protocol is http or https. + + REQUEST_METHOD must be one of: + + get + HTTP GET method + post + HTTP POST method + + --username=USERNAME + The username to use when authenticating with the HTTP server. Can + only be set if --protocol is http or https. + + --validate-ssl=VALIDATE_SSL + Whether to include SSL certificate validation as a part of the uptime + check, defaults to false. Can only be set if --protocol is http or + https. + + Uptime check status. + + At most one of these can be specified: + + --status-classes=[status-class,...] + List of HTTP status classes. The uptime check only passes when the + response code is contained in this list. Defaults to 2xx. Can only + be set if --protocol is http or https. + + status-class must be one of: + + 1xx + Any response code from 100-199 inclusive + 2xx + Any response code from 200-299 inclusive + 3xx + Any response code from 300-399 inclusive + 4xx + Any response code from 400-499 inclusive + 5xx + Any response code from 500-599 inclusive + any + Any response code + + --status-codes=[status-code,...] + List of HTTP Status Codes. The uptime check will only pass if the + response code is present in this list. Can only be set if + --protocol is http or https. + + Uptime check matcher settings. + + --matcher-content=MATCHER_CONTENT + String, regex or JSON content to match. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --matcher-type=MATCHER_TYPE + The type of content matcher that is applied to the server output, + defaults to contains-string. + + MATCHER_TYPE must be one of: + + contains-string + Response contains string + matches-json-path + Response matches at JSONPath + matches-regex + Response matches regex + not-contains-string + Response does not contain string + not-matches-json-path + Response does not match at JSONPath + not-matches-regex + Response does not match regex + + Uptime check matcher settings for JSON responses. + + --json-path=JSON_PATH + JSONPath within the response output pointing to the expected + content to match. Only used if --matcher-type is matches-json-path + or not-matches-json-path. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --json-path-matcher-type=JSON_PATH_MATCHER_TYPE + The type of JSONPath match that is applied to the JSON output, + defaults to exact-match. Only used if --matcher-type is + matches-json-path or not-matches-json-path. + + JSON_PATH_MATCHER_TYPE must be one of: + + exact-match + Response matches exact string at JSONPath + regex-match + Response matches regex at JSONPath + + Settings. + + --period=PERIOD + The time between uptime check or synthetic monitor executions in + minutes, defaults to 1. Can be set for synthetic monitors. + + PERIOD must be one of: + + 1 + One minute + 10 + Ten minutes + 15 + Fifteen minutes + 5 + Five minutes + + --regions=[field,...] + The list of regions from which the check is run. At least 3 regions + must be selected. Defaults to all available regions. + + field must be one of: + + asia-pacific + asia-southeast1 + europe + europe-west1 + south-america + southamerica-east1 + usa-iowa + us-central1 + usa-oregon + us-west1 + usa-virginia + us-east4 + + --timeout=TIMEOUT + The maximum amount of time in seconds to wait for the request to + complete, defaults to 60. Can be set for synthetic monitors. + + --user-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +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 monitoring uptime create + + $ gcloud alpha monitoring uptime create + diff --git a/gcloud/beta/monitoring/uptime/delete b/gcloud/beta/monitoring/uptime/delete new file mode 100644 index 000000000..b9c6421c8 --- /dev/null +++ b/gcloud/beta/monitoring/uptime/delete @@ -0,0 +1,59 @@ +NAME + gcloud beta monitoring uptime delete - delete an uptime check or synthetic + monitor + +SYNOPSIS + gcloud beta monitoring uptime delete CHECK_ID [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete an uptime check or synthetic monitor + +EXAMPLES + To delete an uptime check or synthetic monitor: + + $ gcloud beta monitoring uptime delete CHECK_ID + + More information can be found at + https://cloud.google.com/monitoring/uptime-checks/manage#delete. + +POSITIONAL ARGUMENTS + Uptime check or synthetic monitor resource - The uptime check or synthetic + monitor to delete. 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 check_id 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. + + CHECK_ID + ID of the uptime check or synthetic monitor or fully qualified + identifier for the uptime check or synthetic monitor. + + To set the check_id attribute: + ▸ provide the argument check_id on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring uptime delete + + $ gcloud alpha monitoring uptime delete + diff --git a/gcloud/beta/monitoring/uptime/describe b/gcloud/beta/monitoring/uptime/describe new file mode 100644 index 000000000..b0d1603af --- /dev/null +++ b/gcloud/beta/monitoring/uptime/describe @@ -0,0 +1,59 @@ +NAME + gcloud beta monitoring uptime describe - describe an uptime check or + synthetic monitor + +SYNOPSIS + gcloud beta monitoring uptime describe CHECK_ID [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an uptime check or synthetic monitor + +EXAMPLES + To describe an uptime check or synthetic monitor: + + $ gcloud beta monitoring uptime describe CHECK_ID + + More information can be found at + https://cloud.google.com/monitoring/uptime-checks/manage#get. + +POSITIONAL ARGUMENTS + Uptime check or synthetic monitor resource - The uptime check or synthetic + monitor to describe. 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 check_id 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. + + CHECK_ID + ID of the uptime check or synthetic monitor or fully qualified + identifier for the uptime check or synthetic monitor. + + To set the check_id attribute: + ▸ provide the argument check_id on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring uptime describe + + $ gcloud alpha monitoring uptime describe + diff --git a/gcloud/beta/monitoring/uptime/help b/gcloud/beta/monitoring/uptime/help new file mode 100644 index 000000000..383f17bb9 --- /dev/null +++ b/gcloud/beta/monitoring/uptime/help @@ -0,0 +1,47 @@ +NAME + gcloud beta monitoring uptime - manage Cloud Monitoring uptime checks and + synthetic monitors + +SYNOPSIS + gcloud beta monitoring uptime COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Monitoring uptime checks and synthetic monitors. + + More information can be found here: + https://cloud.google.com/monitoring/api/v3/ + +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 uptime check or synthetic monitor. + + delete + (BETA) Delete an uptime check or synthetic monitor. + + describe + (BETA) Describe an uptime check or synthetic monitor. + + list-configs + (BETA) List uptime checks and synthetic monitors. + + list-ips + (BETA) List uptime check server ips. + + update + (BETA) Update an existing uptime check or synthetic monitor. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring uptime + + $ gcloud alpha monitoring uptime + diff --git a/gcloud/beta/monitoring/uptime/list-configs b/gcloud/beta/monitoring/uptime/list-configs new file mode 100644 index 000000000..57bce0409 --- /dev/null +++ b/gcloud/beta/monitoring/uptime/list-configs @@ -0,0 +1,72 @@ +NAME + gcloud beta monitoring uptime list-configs - list uptime checks and + synthetic monitors + +SYNOPSIS + gcloud beta monitoring uptime list-configs [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List uptime checks and synthetic monitors. + +EXAMPLES + To see all uptime checks and synthetic monitors: + + $ gcloud beta monitoring uptime list-configs + + More information can be found at + https://cloud.google.com/monitoring/uptime-checks/using-uptime-checks + +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 monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring uptime list-configs + + $ gcloud alpha monitoring uptime list-configs + diff --git a/gcloud/beta/monitoring/uptime/list-ips b/gcloud/beta/monitoring/uptime/list-ips new file mode 100644 index 000000000..4b133bfcd --- /dev/null +++ b/gcloud/beta/monitoring/uptime/list-ips @@ -0,0 +1,37 @@ +NAME + gcloud beta monitoring uptime list-ips - list uptime check server ips + +SYNOPSIS + gcloud beta monitoring uptime list-ips [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List uptime check egress ips. + +EXAMPLES + To see all uptime check servers ips: + + $ gcloud beta monitoring uptime list-ips + + More information can be found at + https://cloud.google.com/monitoring/uptime-checks/using-uptime-checks + +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 monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud monitoring uptime list-ips + + $ gcloud alpha monitoring uptime list-ips + diff --git a/gcloud/beta/monitoring/uptime/update b/gcloud/beta/monitoring/uptime/update new file mode 100644 index 000000000..b7034b251 --- /dev/null +++ b/gcloud/beta/monitoring/uptime/update @@ -0,0 +1,412 @@ +NAME + gcloud beta monitoring uptime update - update an existing uptime check or + synthetic monitor + +SYNOPSIS + gcloud beta monitoring uptime update CHECK_ID + [--body=BODY --content-type=CONTENT_TYPE + --custom-content-type=CUSTOM_CONTENT_TYPE --mask-headers=MASK_HEADERS + --password=PASSWORD --path=PATH --pings-count=PINGS_COUNT --port=PORT + --request-method=REQUEST_METHOD --username=USERNAME + --validate-ssl=VALIDATE_SSL --add-status-classes=[status-class,...] + | --clear-status-classes=CLEAR_STATUS_CLASSES + | --remove-status-classes=[status-class,...] + | --set-status-classes=[status-class,...] + | --add-status-codes=[status-code,...] + | --clear-status-codes=CLEAR_STATUS_CODES + | --remove-status-codes=[status-code,...] + | --set-status-codes=[status-code,...] + --update-headers=[KEY=VALUE,...] --clear-headers=CLEAR_HEADERS + | --remove-headers=[KEY,...]] + [--display-name=DISPLAY_NAME + --period=PERIOD --timeout=TIMEOUT --add-regions=[region,...] + | --clear-regions=CLEAR_REGIONS | --remove-regions=[region,...] + | --set-regions=[region,...] + --update-user-labels=[KEY=VALUE,...] --clear-user-labels + | --remove-user-labels=[KEY,...]] + [--matcher-content=MATCHER_CONTENT + : --matcher-type=MATCHER_TYPE [--json-path=JSON_PATH + : --json-path-matcher-type=JSON_PATH_MATCHER_TYPE]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates an existing uptime check or synthetic monitor. + + Flags only apply to uptime checks unless noted that they apply to synthetic + monitors. + + For information about the JSON/YAML format of an uptime check: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.uptimeCheckConfigs + +EXAMPLES + To update an uptime check or synthetic monitor, run: + + $ gcloud beta monitoring uptime update CHECK_ID --period=5 \ + --timeout=30 + +POSITIONAL ARGUMENTS + Uptime check or synthetic monitor resource - Name of the uptime check or + synthetic monitor to be updated. 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 check_id 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. + + CHECK_ID + ID of the uptime check or synthetic monitor or fully qualified + identifier for the uptime check or synthetic monitor. + + To set the check_id attribute: + ▸ provide the argument check_id on the command line. + +FLAGS + Uptime check protocol settings. + + --body=BODY + The request body associated with the HTTP POST request. Can only be + set if --protocol is http or https. + + --content-type=CONTENT_TYPE + The content type header to use for the check, defaults to + unspecified. Can only be set if --protocol is http or https. + + CONTENT_TYPE must be one of: + + unspecified + Not specified + url-encoded + URL encoded + user-provided + User provided + + --custom-content-type=CUSTOM_CONTENT_TYPE + A user-provided content type header to use for the check. Can only be + set if --protocol is http or https. + + --mask-headers=MASK_HEADERS + Whether to encrypt the header information, defaults to false. Can + only be set if --protocol is http or https. + + --password=PASSWORD + The password to use when authenticating with the HTTP server. Can + only be set if --protocol is http or https. + + --path=PATH + The path to the page against which to run the check, defaults to /. + Can only be set if --protocol is http or https. + + --pings-count=PINGS_COUNT + Number of ICMP pings to send alongside the request. + + --port=PORT + The port on the server against which to run the check. Defaults to 80 + when --protocol is http. Defaults to 443 when --protocol is https. + Required if --protocol is tcp. + + --request-method=REQUEST_METHOD + The HTTP request method to use, defaults to get. Can only be set if + --protocol is http or https. + + REQUEST_METHOD must be one of: + + get + HTTP GET method + post + HTTP POST method + + --username=USERNAME + The username to use when authenticating with the HTTP server. Can + only be set if --protocol is http or https. + + --validate-ssl=VALIDATE_SSL + Whether to include SSL certificate validation as a part of the uptime + check, defaults to false. Can only be set if --protocol is http or + https. + + Uptime check status. + + At most one of these can be specified: + + Uptime check status classes. + + At most one of these can be specified: + + --add-status-classes=[status-class,...] + The list of HTTP status classes to add to the uptime check. + status-class must be one of: + + 1xx + Any response code from 100-199 inclusive + 2xx + Any response code from 200-299 inclusive + 3xx + Any response code from 300-399 inclusive + 4xx + Any response code from 400-499 inclusive + 5xx + Any response code from 500-599 inclusive + any + Any response code + + --clear-status-classes=CLEAR_STATUS_CLASSES + Clear all HTTP status classes on the uptime check. Setting this + flag is the same as selecting only the 2xx status class. + + --remove-status-classes=[status-class,...] + The list of HTTP status classes to remove from the uptime check. + status-class must be one of: + + 1xx + Any response code from 100-199 inclusive + 2xx + Any response code from 200-299 inclusive + 3xx + Any response code from 300-399 inclusive + 4xx + Any response code from 400-499 inclusive + 5xx + Any response code from 500-599 inclusive + any + Any response code + + --set-status-classes=[status-class,...] + List of HTTP status classes. The uptime check will only pass if + the response code is contained in this list. + + status-class must be one of: + + 1xx + Any response code from 100-199 inclusive + 2xx + Any response code from 200-299 inclusive + 3xx + Any response code from 300-399 inclusive + 4xx + Any response code from 400-499 inclusive + 5xx + Any response code from 500-599 inclusive + any + Any response code + + Uptime check status codes. + + At most one of these can be specified: + + --add-status-codes=[status-code,...] + The list of HTTP status codes to add to the uptime check. + + --clear-status-codes=CLEAR_STATUS_CODES + Clear all HTTP status codes on the uptime check. Setting this + flag is the same as selecting only the 2xx status class. + + --remove-status-codes=[status-code,...] + The list of HTTP status codes to remove from the uptime check. + + --set-status-codes=[status-code,...] + List of HTTP status codes. The uptime check will only pass if the + response code is present in this list. + + Uptime check headers. + + --update-headers=[KEY=VALUE,...] + The list of headers to add to the uptime check. Any existing + headers with matching "key" are overridden by the provided values. + + Uptime check remove headers. + + At most one of these can be specified: + + --clear-headers=CLEAR_HEADERS + Clear all headers on the uptime check. + + --remove-headers=[KEY,...] + The list of header keys to remove from the uptime check. + + Settings. + + --display-name=DISPLAY_NAME + The display name for the uptime check or synthetic monitor. + + --period=PERIOD + The time between uptime check or synthetic monitor executions in + minutes, defaults to 1. Can be set for synthetic monitors. + + PERIOD must be one of: + + 1 + One minute + 10 + Ten minutes + 15 + Fifteen minutes + 5 + Five minutes + + --timeout=TIMEOUT + The maximum amount of time in seconds to wait for the request to + complete, defaults to 60. Can be set for synthetic monitors. + + Uptime check selected regions. + + At most one of these can be specified: + + --add-regions=[region,...] + The list of regions to add to the uptime check. region must be one + of: + + asia-pacific + asia-southeast1 + europe + europe-west1 + south-america + southamerica-east1 + usa-iowa + us-central1 + usa-oregon + us-west1 + usa-virginia + us-east4 + + --clear-regions=CLEAR_REGIONS + Clear all regions on the uptime check. This setting acts the same + as if all available regions were selected. + + --remove-regions=[region,...] + The list of regions to remove from the uptime check. region must be + one of: + + asia-pacific + asia-southeast1 + europe + europe-west1 + south-america + southamerica-east1 + usa-iowa + us-central1 + usa-oregon + us-west1 + usa-virginia + us-east4 + + --set-regions=[region,...] + The list of regions from which the check is run. At least 3 regions + must be selected. + + region must be one of: + + asia-pacific + asia-southeast1 + europe + europe-west1 + south-america + southamerica-east1 + usa-iowa + us-central1 + usa-oregon + us-west1 + usa-virginia + us-east4 + + User labels. Can be set for synthetic monitors. + + --update-user-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. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values + must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + At most one of these can be specified: + + --clear-user-labels + Remove all labels. If --update-user-labels is also specified then + --clear-user-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta monitoring uptime update --clear-user-labels + + To remove all existing labels and create two new labels, foo and + baz: + + $ gcloud beta monitoring uptime update --clear-user-labels \ + --update-user-labels foo=bar,baz=qux + + --remove-user-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-user-labels is also specified then + --update-user-labels is applied first. + + Uptime check matcher settings. + + --matcher-content=MATCHER_CONTENT + String, regex or JSON content to match. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --matcher-type=MATCHER_TYPE + The type of content matcher that is applied to the server output, + defaults to contains-string. + + MATCHER_TYPE must be one of: + + contains-string + Response contains string + matches-json-path + Response matches at JSONPath + matches-regex + Response matches regex + not-contains-string + Response does not contain string + not-matches-json-path + Response does not match at JSONPath + not-matches-regex + Response does not match regex + + Uptime check matcher settings for JSON responses. + + --json-path=JSON_PATH + JSONPath within the response output pointing to the expected + content to match. Only used if --matcher-type is matches-json-path + or not-matches-json-path. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --json-path-matcher-type=JSON_PATH_MATCHER_TYPE + The type of JSONPath match that is applied to the JSON output, + defaults to exact-match. Only used if --matcher-type is + matches-json-path or not-matches-json-path. + + JSON_PATH_MATCHER_TYPE must be one of: + + exact-match + Response matches exact string at JSONPath + regex-match + Response matches regex at JSONPath + +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 monitoring uptime update + + $ gcloud alpha monitoring uptime update + diff --git a/gcloud/beta/netapp/storage-pools/create b/gcloud/beta/netapp/storage-pools/create index c4ff0f941..c3617aeff 100644 --- a/gcloud/beta/netapp/storage-pools/create +++ b/gcloud/beta/netapp/storage-pools/create @@ -17,7 +17,7 @@ DESCRIPTION EXAMPLES The following command creates a Storage Pool named NAME using all possible - arguments + arguments with a VPC network in the same project $ gcloud beta netapp storage-pools create NAME \ --location=us-central1 --service-level=standard \ @@ -25,6 +25,17 @@ EXAMPLES --kms-config=kms-config1 --enable-ldap=true \ --description="example description" + The following command creates a Storage pool named NAME using all possible + arguments with a shared VPC network in a separate project called + VPC_PROJECT + + $ gcloud beta netapp storage-pools create NAME \ + --location=us-central1 --service-level=standard \ + --capacity=2048 \ + --network=name=projects/VPC_PROJECT/locations/us-central1/\ + networks/default --active-directory=ad1 --kms-config=kms-config1 \ + --enable-ldap=true --description="example description" + POSITIONAL ARGUMENTS Storage pool resource - The Storage Pool to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -68,7 +79,11 @@ REQUIRED FLAGS psa-range is optional. name The name of the Google Compute Engine VPC network to which the - volume is connected. + volume is connected. Short-form (VPC network ID) or long-form (full + VPC network name: + projects/PROJECT/locations/LOCATION/networks/NETWORK) are both + accepted, but please use the long-form when attempting to create a + Storage Pool using a shared VPC. psa-range The psa-range is the name of the allocated range of the Private Service Access connection. The range you specify can't overlap with diff --git a/gcloud/beta/network-security/firewall-endpoint-associations/create b/gcloud/beta/network-security/firewall-endpoint-associations/create index 3b6b6cb33..efeda4871 100644 --- a/gcloud/beta/network-security/firewall-endpoint-associations/create +++ b/gcloud/beta/network-security/firewall-endpoint-associations/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta network-security firewall-endpoint-associations create - (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) --network=NETWORK + [ASSOCIATION_ID] --network=NETWORK --zone=ZONE (--endpoint=ENDPOINT : --endpoint-zone=ENDPOINT_ZONE --organization=ORGANIZATION) [--async] [--labels=[KEY=VALUE,...]] @@ -26,44 +26,15 @@ EXAMPLES To associate a network with a firewall endpoint, run: $ gcloud beta network-security firewall-endpoint-associations \ - create my-assoc \ - --network=projects/my-project/networks/global/myNetwork \ + create --network=projects/my-project/networks/global/myNetwork \ --endpoint=organizations/1234/locations/us-central1-a/\ firewallEndpoints/my-endpoint --zone=us-central1-a \ --project=my-project POSITIONAL ARGUMENTS - Firewall endpoint association resource - Firewall Plus. 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 FIREWALL_ENDPOINT_ASSOCIATION 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. - - FIREWALL_ENDPOINT_ASSOCIATION - ID of the firewall endpoint association or fully qualified identifier - for the firewall endpoint association. - - To set the association-name attribute: - ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command - line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --zone=ZONE - Zone of the firewall endpoint association. - - To set the zone attribute: - ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command - line with a fully specified name; - ▸ provide the argument --zone on the command line. + [ASSOCIATION_ID] + Name to give the association. If not specified, an auto-generated UUID + will be used. REQUIRED FLAGS Network resource - Firewall Plus. This represents a Cloud resource. (NOTE) @@ -84,6 +55,9 @@ REQUIRED FLAGS To set the network-name attribute: ▸ provide the argument --network on the command line. + --zone=ZONE + Zone of a firewall endpoint association + Firewall endpoint resource - Firewall Plus. The arguments in this group can be used to specify the attributes of this resource. diff --git a/gcloud/beta/sql/backups/describe b/gcloud/beta/sql/backups/describe index fc2a86b6a..b5a5522bd 100644 --- a/gcloud/beta/sql/backups/describe +++ b/gcloud/beta/sql/backups/describe @@ -2,7 +2,7 @@ NAME gcloud beta sql backups describe - retrieves information about a backup SYNOPSIS - gcloud beta sql backups describe ID --instance=INSTANCE, -i INSTANCE + gcloud beta sql backups describe ID [--instance=INSTANCE, -i INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -10,10 +10,10 @@ DESCRIPTION POSITIONAL ARGUMENTS ID - The ID of the backup run. You can find the ID by running $ gcloud sql - backups list -i {instance}. + The ID of the backup run. To find the ID, run the following command: $ + gcloud sql backups list -i {instance}. -REQUIRED FLAGS +FLAGS --instance=INSTANCE, -i INSTANCE Cloud SQL instance ID. diff --git a/gcloud/beta/sql/generate-login-token b/gcloud/beta/sql/generate-login-token index 9cf8ff13c..5f9cdbe90 100644 --- a/gcloud/beta/sql/generate-login-token +++ b/gcloud/beta/sql/generate-login-token @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud beta sql generate-login-token [--application-default-credential] - [--instance=INSTANCE] [GCLOUD_WIDE_FLAG ...] + [--instance=INSTANCE, -i INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta sql generate-login-token generates an IAM token to use @@ -35,7 +35,7 @@ FLAGS --application-default-credential Use application default credentials to generate the login token. - --instance=INSTANCE + --instance=INSTANCE, -i INSTANCE Cloud SQL instance ID. GCLOUD WIDE FLAGS diff --git a/gcloud/beta/workstations/configs/create b/gcloud/beta/workstations/configs/create index a598f2030..8498f50c2 100644 --- a/gcloud/beta/workstations/configs/create +++ b/gcloud/beta/workstations/configs/create @@ -11,8 +11,9 @@ SYNOPSIS [--container-env=[CONTAINER_ENV,...]] [--container-run-as-user=CONTAINER_RUN_AS_USER] [--container-working-dir=CONTAINER_WORKING_DIR] - [--disable-public-ip-addresses] [--enable-audit-agent] - [--enable-confidential-compute] [--enable-nested-virtualization] + [--disable-public-ip-addresses] [--disable-tcp-connections] + [--enable-audit-agent] [--enable-confidential-compute] + [--enable-nested-virtualization] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--network-tags=[NETWORK_TAGS,...]] @@ -139,6 +140,10 @@ FLAGS Default value is false. If set, instances will have no public IP address. + --disable-tcp-connections + Default value is false. If set, workstations will not allow plain TCP + connections. + --enable-audit-agent Whether to enable Linux auditd logging on the workstation. When enabled, a service account must also be specified that has diff --git a/gcloud/beta/workstations/configs/update b/gcloud/beta/workstations/configs/update index f7fee2035..16c9050aa 100644 --- a/gcloud/beta/workstations/configs/update +++ b/gcloud/beta/workstations/configs/update @@ -24,6 +24,7 @@ SYNOPSIS : --accelerator-type=ACCELERATOR_TYPE] [--container-custom-image=CONTAINER_CUSTOM_IMAGE | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE] + [--disable-tcp-connections | --enable-tcp-connections] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -243,6 +244,16 @@ FLAGS webstorm WebStorm + At most one of these can be specified: + + --disable-tcp-connections + Default value is false. If set, workstations will allow plain TCP + connections. + + --enable-tcp-connections + Default value is false. If set, workstations will allow plain TCP + connections. + 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/billing/budgets/create b/gcloud/billing/budgets/create index 7a2a1c074..e316d55f2 100644 --- a/gcloud/billing/budgets/create +++ b/gcloud/billing/budgets/create @@ -16,6 +16,7 @@ SYNOPSIS [--notifications-rule-monitoring-notification-channels=[NOTIFICATIONS_RULE_MONITORING_NOTIFICATION_CHANNELS, ...]] [--notifications-rule-pubsub-topic=NOTIFICATIONS_RULE_PUBSUB_TOPIC] + [--ownership-scope=OWNERSHIP_SCOPE] [--threshold-rule=[basis=BASIS],[percent=PERCENT]] [--calendar-period=CALENDAR_PERIOD | [--start-date=START_DATE : --end-date=END_DATE]] @@ -134,6 +135,20 @@ OPTIONAL FLAGS Name of the Cloud Pub/Sub topic where budget related messages will be published, in the form projects/{project_id}/topics/{topic_id}. + --ownership-scope=OWNERSHIP_SCOPE + Sets the ownership scope of the budget. The ownership scope and users' + IAM permissions determine who has full access to the budget's data. + + Must be one of: 'ALL_USERS' or 'BILLING_ACCOUNT'. Use 'ALL_USERS' to + allow billing account- level users and project-level users to have full + access to the budget (if the users have the required IAM permissions). + Use 'BILLING_ACCOUNT' to allow only billing account-level users to have + full access to the budget. Project-level users will have read-only + access, even if they have the required IAM permissions. + + OWNERSHIP_SCOPE must be one of: all-users, billing-account, + ownership-scope-unspecified. + --threshold-rule=[basis=BASIS],[percent=PERCENT] Rule that triggers alerts (notifications of thresholds being crossed) when spend exceeds the specified percentages of the budget. This flag diff --git a/gcloud/billing/budgets/update b/gcloud/billing/budgets/update index 704240ff6..e44418b31 100644 --- a/gcloud/billing/budgets/update +++ b/gcloud/billing/budgets/update @@ -14,6 +14,7 @@ SYNOPSIS [--notifications-rule-monitoring-notification-channels=[NOTIFICATIONS_RULE_MONITORING_NOTIFICATION_CHANNELS, ...]] [--notifications-rule-pubsub-topic=NOTIFICATIONS_RULE_PUBSUB_TOPIC] + [--ownership-scope=OWNERSHIP_SCOPE] [--budget-amount=BUDGET_AMOUNT | --last-period-amount] [--calendar-period=CALENDAR_PERIOD | [--start-date=START_DATE : --end-date=END_DATE]] @@ -134,6 +135,20 @@ FLAGS Name of the Cloud Pub/Sub topic where budget related messages will be published, in the form projects/{project_id}/topics/{topic_id}. + --ownership-scope=OWNERSHIP_SCOPE + Sets the ownership scope of the budget. The ownership scope and users' + IAM permissions determine who has full access to the budget's data. + + Must be one of: 'ALL_USERS' or 'BILLING_ACCOUNT'. Use 'ALL_USERS' to + allow billing account- level users and project-level users to have full + access to the budget (if the users have the required IAM permissions). + Use 'BILLING_ACCOUNT' to allow only billing account-level users to have + full access to the budget. Project-level users will have read-only + access, even if they have the required IAM permissions. + + OWNERSHIP_SCOPE must be one of: all-users, billing-account, + ownership-scope-unspecified. + At most one of these can be specified: --budget-amount=BUDGET_AMOUNT diff --git a/gcloud/compute/instances/perform-maintenance b/gcloud/compute/instances/perform-maintenance index 334b4d289..8c779c1c4 100644 --- a/gcloud/compute/instances/perform-maintenance +++ b/gcloud/compute/instances/perform-maintenance @@ -10,7 +10,7 @@ DESCRIPTION Perform maintenance of Google Compute Engine instance. EXAMPLES - To perform a customer trigged maintenance on an instance named + To perform customer-triggered maintenance on an instance named test-instance located in zone us-east1-d, run: $ gcloud compute instances perform-maintenance test-instance \ diff --git a/gcloud/dataproc/clusters/diagnose b/gcloud/dataproc/clusters/diagnose index 4d5b64799..5682227a7 100644 --- a/gcloud/dataproc/clusters/diagnose +++ b/gcloud/dataproc/clusters/diagnose @@ -3,7 +3,9 @@ NAME SYNOPSIS gcloud dataproc clusters diagnose (CLUSTER : --region=REGION) - [GCLOUD_WIDE_FLAG ...] + [--end-time=END_TIME] [--job-ids=JOB_IDS] [--start-time=START_TIME] + [--tarball-access=TARBALL_ACCESS] + [--yarn-application-ids=YARN_APPLICATION_IDS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Run a detailed diagnostic on a cluster. @@ -48,6 +50,25 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property dataproc/region. +FLAGS + --end-time=END_TIME + Time instant to stop the diagnosis at (in %Y-%m-%dT%H:%M:%S.%fZ + format). + + --job-ids=JOB_IDS + A list of jobs on which to perform the diagnosis. + + --start-time=START_TIME + Time instant to start the diagnosis from (in %Y-%m-%dT%H:%M:%S.%fZ + format). + + --tarball-access=TARBALL_ACCESS + Target access privileges for diagnose tarball. TARBALL_ACCESS must be + one of: GOOGLE_CLOUD_SUPPORT, GOOGLE_DATAPROC_DIAGNOSE. + + --yarn-application-ids=YARN_APPLICATION_IDS + A list of yarn applications on which to perform the diagnosis. + 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/domains/registrations/get-transfer-parameters b/gcloud/domains/registrations/get-transfer-parameters index 819f765eb..6d45aa934 100644 --- a/gcloud/domains/registrations/get-transfer-parameters +++ b/gcloud/domains/registrations/get-transfer-parameters @@ -7,6 +7,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) Get transfer parameters of a specific domain. + + This command is deprecated. See + https://cloud.google.com/domains/docs/deprecations/feature-deprecations. + Get parameters needed to transfer an existing domain from a different registrar. The parameters include the current registrar, name servers, transfer lock state, price, and supported privacy modes. diff --git a/gcloud/domains/registrations/help b/gcloud/domains/registrations/help index f5e15b14e..ee5a2fc47 100644 --- a/gcloud/domains/registrations/help +++ b/gcloud/domains/registrations/help @@ -41,7 +41,7 @@ COMMANDS Get register parameters (including availability) of a specific domain. get-transfer-parameters - Get transfer parameters of a specific domain. + (DEPRECATED) Get transfer parameters of a specific domain. import (DEPRECATED) Import a domain from Google Domains registrar to Cloud @@ -51,7 +51,8 @@ COMMANDS List Cloud Domains registrations. list-importable-domains - List Google Domains registrations importable into Cloud Domains. + (DEPRECATED) List Google Domains registrations importable into Cloud + Domains. register Register a new domain. diff --git a/gcloud/domains/registrations/list-importable-domains b/gcloud/domains/registrations/list-importable-domains index fcc07b451..f401dc54c 100644 --- a/gcloud/domains/registrations/list-importable-domains +++ b/gcloud/domains/registrations/list-importable-domains @@ -8,6 +8,12 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION + (DEPRECATED) List Google Domains registrations importable into Cloud + Domains. + + This command is deprecated. See + https://cloud.google.com/domains/docs/deprecations/feature-deprecations. + List Google Domains registrations that can be imported to a Cloud Domains project. diff --git a/gcloud/functions/add-iam-policy-binding b/gcloud/functions/add-iam-policy-binding index 61d8b8464..89e23e0b0 100644 --- a/gcloud/functions/add-iam-policy-binding +++ b/gcloud/functions/add-iam-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud functions add-iam-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL --role=ROLE [--gen2] [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] DESCRIPTION Adds an IAM policy binding for a Google Cloud Function. @@ -70,15 +70,6 @@ REQUIRED FLAGS for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer. -OPTIONAL FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/functions/add-invoker-policy-binding b/gcloud/functions/add-invoker-policy-binding index ba33777c1..f5688a0e9 100644 --- a/gcloud/functions/add-invoker-policy-binding +++ b/gcloud/functions/add-invoker-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud functions add-invoker-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL [--gen2] [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] DESCRIPTION Adds an invoker role IAM policy binding that allows the specified member to @@ -71,15 +71,6 @@ REQUIRED FLAGS ◆ allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account. -OPTIONAL FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/functions/call b/gcloud/functions/call index 734cbd961..625c94147 100644 --- a/gcloud/functions/call +++ b/gcloud/functions/call @@ -2,7 +2,7 @@ NAME gcloud functions call - triggers execution of a Google Cloud Function SYNOPSIS - gcloud functions call (NAME : --region=REGION) [--gen2] + gcloud functions call (NAME : --region=REGION) [--cloud-event=CLOUD_EVENT | --data=DATA] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -56,14 +56,6 @@ POSITIONAL ARGUMENTS ▸ set the property functions/region. FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - At most one of these can be specified: --cloud-event=CLOUD_EVENT diff --git a/gcloud/functions/delete b/gcloud/functions/delete index 2aa4f123f..6fb9f7dfb 100644 --- a/gcloud/functions/delete +++ b/gcloud/functions/delete @@ -2,8 +2,7 @@ NAME gcloud functions delete - delete a Google Cloud Function SYNOPSIS - gcloud functions delete (NAME : --region=REGION) [--gen2] - [GCLOUD_WIDE_FLAG ...] + gcloud functions delete (NAME : --region=REGION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION Delete a Google Cloud Function. @@ -41,15 +40,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property functions/region. -FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/functions/describe b/gcloud/functions/describe index 0194ea398..cded362c3 100644 --- a/gcloud/functions/describe +++ b/gcloud/functions/describe @@ -2,8 +2,7 @@ NAME gcloud functions describe - display details of a Google Cloud Function SYNOPSIS - gcloud functions describe (NAME : --region=REGION) [--gen2] - [GCLOUD_WIDE_FLAG ...] + gcloud functions describe (NAME : --region=REGION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION Display details of a Google Cloud Function. @@ -41,15 +40,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property functions/region. -FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/functions/get-iam-policy b/gcloud/functions/get-iam-policy index 8ed5ec8df..c1b1a78c0 100644 --- a/gcloud/functions/get-iam-policy +++ b/gcloud/functions/get-iam-policy @@ -3,7 +3,7 @@ NAME Function SYNOPSIS - gcloud functions get-iam-policy (NAME : --region=REGION) [--gen2] + gcloud functions get-iam-policy (NAME : --region=REGION) [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -48,15 +48,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument --region on the command line; ▸ set the property functions/region. -FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/functions/remove-iam-policy-binding b/gcloud/functions/remove-iam-policy-binding index fd784780d..81e31a96c 100644 --- a/gcloud/functions/remove-iam-policy-binding +++ b/gcloud/functions/remove-iam-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud functions remove-iam-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL --role=ROLE [--gen2] [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] DESCRIPTION Removes an IAM policy binding from a Google Cloud Function. @@ -71,15 +71,6 @@ REQUIRED FLAGS --role=ROLE The role to remove the principal from. -OPTIONAL FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/functions/remove-invoker-policy-binding b/gcloud/functions/remove-invoker-policy-binding index 1a26ac8bc..6e47e8059 100644 --- a/gcloud/functions/remove-invoker-policy-binding +++ b/gcloud/functions/remove-invoker-policy-binding @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud functions remove-invoker-policy-binding (NAME : --region=REGION) - --member=PRINCIPAL [--gen2] [GCLOUD_WIDE_FLAG ...] + --member=PRINCIPAL [GCLOUD_WIDE_FLAG ...] DESCRIPTION Removes the invoker role IAM policy binding that allows the specified @@ -76,15 +76,6 @@ REQUIRED FLAGS ◆ allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account. -OPTIONAL FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/functions/set-iam-policy b/gcloud/functions/set-iam-policy index 4ab51782a..bf1fc748f 100644 --- a/gcloud/functions/set-iam-policy +++ b/gcloud/functions/set-iam-policy @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud functions set-iam-policy (NAME : --region=REGION) POLICY_FILE - [--gen2] [GCLOUD_WIDE_FLAG ...] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Sets IAM policy for a Google Cloud Function. @@ -51,15 +51,6 @@ POSITIONAL ARGUMENTS POLICY_FILE Path to a local JSON or YAML formatted file containing a valid policy. -FLAGS - --gen2 - If enabled, this command will use Cloud Functions (Second generation). - If disabled with --no-gen2, Cloud Functions (First generation) will be - used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. If the functions/gen2 - configuration property is not set, defaults to looking up the given - function and using its generation. - 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/healthcare/dicom-stores/help b/gcloud/healthcare/dicom-stores/help index 93a6c330c..109a7e691 100644 --- a/gcloud/healthcare/dicom-stores/help +++ b/gcloud/healthcare/dicom-stores/help @@ -46,6 +46,9 @@ COMMANDS list List Cloud Healthcare API DICOM stores. + metrics + Get the metrics for a Cloud Healthcare API DICOM store. + remove-iam-policy-binding Remove an IAM policy binding from a Cloud Healthcare API DICOM store. diff --git a/gcloud/healthcare/dicom-stores/metrics b/gcloud/healthcare/dicom-stores/metrics new file mode 100644 index 000000000..7671ef650 --- /dev/null +++ b/gcloud/healthcare/dicom-stores/metrics @@ -0,0 +1,78 @@ +NAME + gcloud healthcare dicom-stores metrics - get the metrics for a Cloud + Healthcare API DICOM store + +SYNOPSIS + gcloud healthcare dicom-stores metrics + (DICOM_STORE : --dataset=DATASET --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Gets the metrics for a Cloud Healthcare API DICOM store. + +EXAMPLES + To get metrics for the DICOM store 'test-dicom-store', run: + + $ gcloud healthcare dicom-stores metrics test-dicom-store \ + --dataset=test-dataset + +POSITIONAL ARGUMENTS + DicomStore resource - Cloud Healthcare API DICOM store to get metrics for. + 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 dicom_store 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. + + DICOM_STORE + ID of the dicomStore or fully qualified identifier for the + dicomStore. + + To set the dicom_store attribute: + ▸ provide the argument dicom_store on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --dataset=DATASET + Cloud Healthcare dataset. + + To set the dataset attribute: + ▸ provide the argument dicom_store on the command line with a fully + specified name; + ▸ provide the argument --dataset on the command line. + + --location=LOCATION + Google Cloud location. + + To set the location attribute: + ▸ provide the argument dicom_store on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property healthcare/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 healthcare/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/healthcare + +NOTES + These variants are also available: + + $ gcloud alpha healthcare dicom-stores metrics + + $ gcloud beta healthcare dicom-stores metrics + diff --git a/gcloud/immersive-stream/xr/instances/create b/gcloud/immersive-stream/xr/instances/create index 4a305dcf8..b05e5341d 100644 --- a/gcloud/immersive-stream/xr/instances/create +++ b/gcloud/immersive-stream/xr/instances/create @@ -9,7 +9,8 @@ SYNOPSIS [capacity=CAPACITY], [enable_autoscaling=ENABLE_AUTOSCALING],[region=REGION] --version=VERSION (--content=CONTENT : --location=LOCATION) [--async] - [--fallback-url=FALLBACK_URL] [GCLOUD_WIDE_FLAG ...] + [--fallback-url=FALLBACK_URL] [--gpu-class=GPU_CLASS] [--mode=MODE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create an Immersive Stream for XR service instance. @@ -36,6 +37,22 @@ EXAMPLES --add-region=region=us-west1,capacity=2 \ --fallback-url="https://www.google.com" + By default, the instance is created with mode=ar, which supports both + 3D and AR experiences. Instances can also be configured to use + 3D-only mode. This configuration cannot be updated later. + To use 3D-only mode, include: + + --mode=3d + + By default, the instance is created with gpu-class=t4. This uses the + NVIDIA T4 GPU for the instance. Instances can also be configured to + use NVIDIA L4 GPUs at creation. Note that only certain regions are + available for L4, and only 3D-only mode is supported. This + configuration cannot be updated later. + To use NVIDIA L4 GPU for the instance, include: + + --gpu-class=l4 + POSITIONAL ARGUMENTS INSTANCE Name of the instance to be created @@ -94,6 +111,12 @@ OPTIONAL FLAGS Fallback url to redirect users to when this service instance is unable to provide the streaming experience + --gpu-class=GPU_CLASS + The class of GPU that is used by this service instance + + --mode=MODE + The rendering mode that is supported by this service instance + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/monitoring/help b/gcloud/monitoring/help index b3713f7bc..cc24d5d40 100644 --- a/gcloud/monitoring/help +++ b/gcloud/monitoring/help @@ -24,6 +24,9 @@ GROUPS snoozes Manage Cloud Monitoring snoozes. + uptime + Manage Cloud Monitoring uptime checks and synthetic monitors. + NOTES These variants are also available: diff --git a/gcloud/monitoring/uptime/create b/gcloud/monitoring/uptime/create new file mode 100644 index 000000000..ad3c8cd30 --- /dev/null +++ b/gcloud/monitoring/uptime/create @@ -0,0 +1,327 @@ +NAME + gcloud monitoring uptime create - create a new uptime check or synthetic + monitor + +SYNOPSIS + gcloud monitoring uptime create DISPLAY_NAME + (--synthetic-target=SYNTHETIC_TARGET + | [--group-id=GROUP_ID : --group-type=GROUP_TYPE] + | [--resource-labels=[KEY=VALUE,...] + : --resource-type=RESOURCE_TYPE]) + [--body=BODY --content-type=CONTENT_TYPE + --custom-content-type=CUSTOM_CONTENT_TYPE --headers=[KEY=VALUE,...] + --mask-headers=MASK_HEADERS --password=PASSWORD --path=PATH + --pings-count=PINGS_COUNT --port=PORT --protocol=PROTOCOL + --request-method=REQUEST_METHOD --username=USERNAME + --validate-ssl=VALIDATE_SSL --status-classes=[status-class,...] + | --status-codes=[status-code,...]] + [--matcher-content=MATCHER_CONTENT + : --matcher-type=MATCHER_TYPE [--json-path=JSON_PATH + : --json-path-matcher-type=JSON_PATH_MATCHER_TYPE]] + [--period=PERIOD --regions=[field,...] + --timeout=TIMEOUT --user-labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new uptime check or synthetic monitor. + + Flags only apply to uptime checks unless noted that they apply to synthetic + monitors. + + For information about the JSON/YAML format of an uptime check: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.uptimeCheckConfigs + +EXAMPLES + To create an uptime check against a URL, run: + + $ gcloud monitoring uptime create DISPLAY_NAME \ + --resource-type=uptime-url \ + --resource-labels=host=google.com,project_id=PROJECT_ID + + To create a synthetic monitor, run: + + $ gcloud monitoring uptime create SYNTHETIC_MONITOR_NAME \ + --synthetic-target=projects/PROJECT_ID/locations/REGION/\ + functions/FUNCTION_NAME + +POSITIONAL ARGUMENTS + DISPLAY_NAME + Display name for the uptime check or synthetic monitor. + +REQUIRED FLAGS + Uptime check resource. + + Exactly one of these must be specified: + + --synthetic-target=SYNTHETIC_TARGET + The target of the Synthetic Monitor. This is the fully qualified + GCFv2 resource name. + + Monitored resource group + + --group-id=GROUP_ID + The group of resources being monitored. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --group-type=GROUP_TYPE + The resource type of the group members, defaults to gce-instance. + GROUP_TYPE must be one of: + + aws-elb-load-balancer + Uptime check against a group of Amazon ELB load balancers. + gce-instance + Uptime check against a group of instances from Google Cloud or + Amazon Web Services. + + Monitored resource + + --resource-labels=[KEY=VALUE,...] + Values for all of the labels listed in the associated monitored + resource descriptor. See + https://cloud.google.com/monitoring/api/resources for more + information and allowed keys. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --resource-type=RESOURCE_TYPE + Type of monitored resource, defaults to uptime-url. RESOURCE_TYPE + must be one of: + + aws-ec2-instance + Uptime check against an AWS EC2 instance. + aws-elb-load-balancer + Uptime check against an ElasticLoadBalancer. + cloud-run-revision + Uptime check against a Cloud Run revision. + gae-app + Uptime check against an App Engine module. + gce-instance + Uptime check against a Compute Engine instance. + servicedirectory-service + Uptime check against a Service Directory service. + uptime-url + Uptime check against a URL. + +OPTIONAL FLAGS + Uptime check protocol settings. + + --body=BODY + The request body associated with the HTTP POST request. Can only be + set if --protocol is http or https. + + --content-type=CONTENT_TYPE + The content type header to use for the check, defaults to + unspecified. Can only be set if --protocol is http or https. + + CONTENT_TYPE must be one of: + + unspecified + Not specified + url-encoded + URL encoded + user-provided + User provided + + --custom-content-type=CUSTOM_CONTENT_TYPE + A user-provided content type header to use for the check. Can only be + set if --protocol is http or https. + + --headers=[KEY=VALUE,...] + The list of headers to send as part of the uptime check request. Can + only be set if --protocol is http or https. + + --mask-headers=MASK_HEADERS + Whether to encrypt the header information, defaults to false. Can + only be set if --protocol is http or https. + + --password=PASSWORD + The password to use when authenticating with the HTTP server. Can + only be set if --protocol is http or https. + + --path=PATH + The path to the page against which to run the check, defaults to /. + Can only be set if --protocol is http or https. + + --pings-count=PINGS_COUNT + Number of ICMP pings to send alongside the request. + + --port=PORT + The port on the server against which to run the check. Defaults to 80 + when --protocol is http. Defaults to 443 when --protocol is https. + Required if --protocol is tcp. + + --protocol=PROTOCOL + The protocol of the request, defaults to http. PROTOCOL must be one + of: + + http + An HTTP check. + https + An HTTPS check. + tcp + A TCP check. + + --request-method=REQUEST_METHOD + The HTTP request method to use, defaults to get. Can only be set if + --protocol is http or https. + + REQUEST_METHOD must be one of: + + get + HTTP GET method + post + HTTP POST method + + --username=USERNAME + The username to use when authenticating with the HTTP server. Can + only be set if --protocol is http or https. + + --validate-ssl=VALIDATE_SSL + Whether to include SSL certificate validation as a part of the uptime + check, defaults to false. Can only be set if --protocol is http or + https. + + Uptime check status. + + At most one of these can be specified: + + --status-classes=[status-class,...] + List of HTTP status classes. The uptime check only passes when the + response code is contained in this list. Defaults to 2xx. Can only + be set if --protocol is http or https. + + status-class must be one of: + + 1xx + Any response code from 100-199 inclusive + 2xx + Any response code from 200-299 inclusive + 3xx + Any response code from 300-399 inclusive + 4xx + Any response code from 400-499 inclusive + 5xx + Any response code from 500-599 inclusive + any + Any response code + + --status-codes=[status-code,...] + List of HTTP Status Codes. The uptime check will only pass if the + response code is present in this list. Can only be set if + --protocol is http or https. + + Uptime check matcher settings. + + --matcher-content=MATCHER_CONTENT + String, regex or JSON content to match. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --matcher-type=MATCHER_TYPE + The type of content matcher that is applied to the server output, + defaults to contains-string. + + MATCHER_TYPE must be one of: + + contains-string + Response contains string + matches-json-path + Response matches at JSONPath + matches-regex + Response matches regex + not-contains-string + Response does not contain string + not-matches-json-path + Response does not match at JSONPath + not-matches-regex + Response does not match regex + + Uptime check matcher settings for JSON responses. + + --json-path=JSON_PATH + JSONPath within the response output pointing to the expected + content to match. Only used if --matcher-type is matches-json-path + or not-matches-json-path. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --json-path-matcher-type=JSON_PATH_MATCHER_TYPE + The type of JSONPath match that is applied to the JSON output, + defaults to exact-match. Only used if --matcher-type is + matches-json-path or not-matches-json-path. + + JSON_PATH_MATCHER_TYPE must be one of: + + exact-match + Response matches exact string at JSONPath + regex-match + Response matches regex at JSONPath + + Settings. + + --period=PERIOD + The time between uptime check or synthetic monitor executions in + minutes, defaults to 1. Can be set for synthetic monitors. + + PERIOD must be one of: + + 1 + One minute + 10 + Ten minutes + 15 + Fifteen minutes + 5 + Five minutes + + --regions=[field,...] + The list of regions from which the check is run. At least 3 regions + must be selected. Defaults to all available regions. + + field must be one of: + + asia-pacific + asia-southeast1 + europe + europe-west1 + south-america + southamerica-east1 + usa-iowa + us-central1 + usa-oregon + us-west1 + usa-virginia + us-east4 + + --timeout=TIMEOUT + The maximum amount of time in seconds to wait for the request to + complete, defaults to 60. Can be set for synthetic monitors. + + --user-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +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 monitoring uptime create + + $ gcloud beta monitoring uptime create + diff --git a/gcloud/monitoring/uptime/delete b/gcloud/monitoring/uptime/delete new file mode 100644 index 000000000..cfd89d9f5 --- /dev/null +++ b/gcloud/monitoring/uptime/delete @@ -0,0 +1,58 @@ +NAME + gcloud monitoring uptime delete - delete an uptime check or synthetic + monitor + +SYNOPSIS + gcloud monitoring uptime delete CHECK_ID [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete an uptime check or synthetic monitor + +EXAMPLES + To delete an uptime check or synthetic monitor: + + $ gcloud monitoring uptime delete CHECK_ID + + More information can be found at + https://cloud.google.com/monitoring/uptime-checks/manage#delete. + +POSITIONAL ARGUMENTS + Uptime check or synthetic monitor resource - The uptime check or synthetic + monitor to delete. 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 check_id 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. + + CHECK_ID + ID of the uptime check or synthetic monitor or fully qualified + identifier for the uptime check or synthetic monitor. + + To set the check_id attribute: + ▸ provide the argument check_id on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + These variants are also available: + + $ gcloud alpha monitoring uptime delete + + $ gcloud beta monitoring uptime delete + diff --git a/gcloud/monitoring/uptime/describe b/gcloud/monitoring/uptime/describe new file mode 100644 index 000000000..1cc94b142 --- /dev/null +++ b/gcloud/monitoring/uptime/describe @@ -0,0 +1,58 @@ +NAME + gcloud monitoring uptime describe - describe an uptime check or synthetic + monitor + +SYNOPSIS + gcloud monitoring uptime describe CHECK_ID [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an uptime check or synthetic monitor + +EXAMPLES + To describe an uptime check or synthetic monitor: + + $ gcloud monitoring uptime describe CHECK_ID + + More information can be found at + https://cloud.google.com/monitoring/uptime-checks/manage#get. + +POSITIONAL ARGUMENTS + Uptime check or synthetic monitor resource - The uptime check or synthetic + monitor to describe. 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 check_id 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. + + CHECK_ID + ID of the uptime check or synthetic monitor or fully qualified + identifier for the uptime check or synthetic monitor. + + To set the check_id attribute: + ▸ provide the argument check_id on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + These variants are also available: + + $ gcloud alpha monitoring uptime describe + + $ gcloud beta monitoring uptime describe + diff --git a/gcloud/monitoring/uptime/help b/gcloud/monitoring/uptime/help new file mode 100644 index 000000000..5ef13484e --- /dev/null +++ b/gcloud/monitoring/uptime/help @@ -0,0 +1,46 @@ +NAME + gcloud monitoring uptime - manage Cloud Monitoring uptime checks and + synthetic monitors + +SYNOPSIS + gcloud monitoring uptime COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Monitoring uptime checks and synthetic monitors. + + More information can be found here: + https://cloud.google.com/monitoring/api/v3/ + +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 new uptime check or synthetic monitor. + + delete + Delete an uptime check or synthetic monitor. + + describe + Describe an uptime check or synthetic monitor. + + list-configs + List uptime checks and synthetic monitors. + + list-ips + List uptime check server ips. + + update + Update an existing uptime check or synthetic monitor. + +NOTES + These variants are also available: + + $ gcloud alpha monitoring uptime + + $ gcloud beta monitoring uptime + diff --git a/gcloud/monitoring/uptime/list-configs b/gcloud/monitoring/uptime/list-configs new file mode 100644 index 000000000..5e5df0b1e --- /dev/null +++ b/gcloud/monitoring/uptime/list-configs @@ -0,0 +1,71 @@ +NAME + gcloud monitoring uptime list-configs - list uptime checks and synthetic + monitors + +SYNOPSIS + gcloud monitoring uptime list-configs [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List uptime checks and synthetic monitors. + +EXAMPLES + To see all uptime checks and synthetic monitors: + + $ gcloud monitoring uptime list-configs + + More information can be found at + https://cloud.google.com/monitoring/uptime-checks/using-uptime-checks + +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 monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + These variants are also available: + + $ gcloud alpha monitoring uptime list-configs + + $ gcloud beta monitoring uptime list-configs + diff --git a/gcloud/monitoring/uptime/list-ips b/gcloud/monitoring/uptime/list-ips new file mode 100644 index 000000000..787a18243 --- /dev/null +++ b/gcloud/monitoring/uptime/list-ips @@ -0,0 +1,36 @@ +NAME + gcloud monitoring uptime list-ips - list uptime check server ips + +SYNOPSIS + gcloud monitoring uptime list-ips [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List uptime check egress ips. + +EXAMPLES + To see all uptime check servers ips: + + $ gcloud monitoring uptime list-ips + + More information can be found at + https://cloud.google.com/monitoring/uptime-checks/using-uptime-checks + +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 monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + These variants are also available: + + $ gcloud alpha monitoring uptime list-ips + + $ gcloud beta monitoring uptime list-ips + diff --git a/gcloud/monitoring/uptime/update b/gcloud/monitoring/uptime/update new file mode 100644 index 000000000..505804667 --- /dev/null +++ b/gcloud/monitoring/uptime/update @@ -0,0 +1,410 @@ +NAME + gcloud monitoring uptime update - update an existing uptime check or + synthetic monitor + +SYNOPSIS + gcloud monitoring uptime update CHECK_ID + [--body=BODY --content-type=CONTENT_TYPE + --custom-content-type=CUSTOM_CONTENT_TYPE --mask-headers=MASK_HEADERS + --password=PASSWORD --path=PATH --pings-count=PINGS_COUNT --port=PORT + --request-method=REQUEST_METHOD --username=USERNAME + --validate-ssl=VALIDATE_SSL --add-status-classes=[status-class,...] + | --clear-status-classes=CLEAR_STATUS_CLASSES + | --remove-status-classes=[status-class,...] + | --set-status-classes=[status-class,...] + | --add-status-codes=[status-code,...] + | --clear-status-codes=CLEAR_STATUS_CODES + | --remove-status-codes=[status-code,...] + | --set-status-codes=[status-code,...] + --update-headers=[KEY=VALUE,...] --clear-headers=CLEAR_HEADERS + | --remove-headers=[KEY,...]] + [--display-name=DISPLAY_NAME + --period=PERIOD --timeout=TIMEOUT --add-regions=[region,...] + | --clear-regions=CLEAR_REGIONS | --remove-regions=[region,...] + | --set-regions=[region,...] + --update-user-labels=[KEY=VALUE,...] --clear-user-labels + | --remove-user-labels=[KEY,...]] + [--matcher-content=MATCHER_CONTENT + : --matcher-type=MATCHER_TYPE [--json-path=JSON_PATH + : --json-path-matcher-type=JSON_PATH_MATCHER_TYPE]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates an existing uptime check or synthetic monitor. + + Flags only apply to uptime checks unless noted that they apply to synthetic + monitors. + + For information about the JSON/YAML format of an uptime check: + https://cloud.google.com/monitoring/api/ref_v3/rest/v3/projects.uptimeCheckConfigs + +EXAMPLES + To update an uptime check or synthetic monitor, run: + + $ gcloud monitoring uptime update CHECK_ID --period=5 --timeout=30 + +POSITIONAL ARGUMENTS + Uptime check or synthetic monitor resource - Name of the uptime check or + synthetic monitor to be updated. 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 check_id 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. + + CHECK_ID + ID of the uptime check or synthetic monitor or fully qualified + identifier for the uptime check or synthetic monitor. + + To set the check_id attribute: + ▸ provide the argument check_id on the command line. + +FLAGS + Uptime check protocol settings. + + --body=BODY + The request body associated with the HTTP POST request. Can only be + set if --protocol is http or https. + + --content-type=CONTENT_TYPE + The content type header to use for the check, defaults to + unspecified. Can only be set if --protocol is http or https. + + CONTENT_TYPE must be one of: + + unspecified + Not specified + url-encoded + URL encoded + user-provided + User provided + + --custom-content-type=CUSTOM_CONTENT_TYPE + A user-provided content type header to use for the check. Can only be + set if --protocol is http or https. + + --mask-headers=MASK_HEADERS + Whether to encrypt the header information, defaults to false. Can + only be set if --protocol is http or https. + + --password=PASSWORD + The password to use when authenticating with the HTTP server. Can + only be set if --protocol is http or https. + + --path=PATH + The path to the page against which to run the check, defaults to /. + Can only be set if --protocol is http or https. + + --pings-count=PINGS_COUNT + Number of ICMP pings to send alongside the request. + + --port=PORT + The port on the server against which to run the check. Defaults to 80 + when --protocol is http. Defaults to 443 when --protocol is https. + Required if --protocol is tcp. + + --request-method=REQUEST_METHOD + The HTTP request method to use, defaults to get. Can only be set if + --protocol is http or https. + + REQUEST_METHOD must be one of: + + get + HTTP GET method + post + HTTP POST method + + --username=USERNAME + The username to use when authenticating with the HTTP server. Can + only be set if --protocol is http or https. + + --validate-ssl=VALIDATE_SSL + Whether to include SSL certificate validation as a part of the uptime + check, defaults to false. Can only be set if --protocol is http or + https. + + Uptime check status. + + At most one of these can be specified: + + Uptime check status classes. + + At most one of these can be specified: + + --add-status-classes=[status-class,...] + The list of HTTP status classes to add to the uptime check. + status-class must be one of: + + 1xx + Any response code from 100-199 inclusive + 2xx + Any response code from 200-299 inclusive + 3xx + Any response code from 300-399 inclusive + 4xx + Any response code from 400-499 inclusive + 5xx + Any response code from 500-599 inclusive + any + Any response code + + --clear-status-classes=CLEAR_STATUS_CLASSES + Clear all HTTP status classes on the uptime check. Setting this + flag is the same as selecting only the 2xx status class. + + --remove-status-classes=[status-class,...] + The list of HTTP status classes to remove from the uptime check. + status-class must be one of: + + 1xx + Any response code from 100-199 inclusive + 2xx + Any response code from 200-299 inclusive + 3xx + Any response code from 300-399 inclusive + 4xx + Any response code from 400-499 inclusive + 5xx + Any response code from 500-599 inclusive + any + Any response code + + --set-status-classes=[status-class,...] + List of HTTP status classes. The uptime check will only pass if + the response code is contained in this list. + + status-class must be one of: + + 1xx + Any response code from 100-199 inclusive + 2xx + Any response code from 200-299 inclusive + 3xx + Any response code from 300-399 inclusive + 4xx + Any response code from 400-499 inclusive + 5xx + Any response code from 500-599 inclusive + any + Any response code + + Uptime check status codes. + + At most one of these can be specified: + + --add-status-codes=[status-code,...] + The list of HTTP status codes to add to the uptime check. + + --clear-status-codes=CLEAR_STATUS_CODES + Clear all HTTP status codes on the uptime check. Setting this + flag is the same as selecting only the 2xx status class. + + --remove-status-codes=[status-code,...] + The list of HTTP status codes to remove from the uptime check. + + --set-status-codes=[status-code,...] + List of HTTP status codes. The uptime check will only pass if the + response code is present in this list. + + Uptime check headers. + + --update-headers=[KEY=VALUE,...] + The list of headers to add to the uptime check. Any existing + headers with matching "key" are overridden by the provided values. + + Uptime check remove headers. + + At most one of these can be specified: + + --clear-headers=CLEAR_HEADERS + Clear all headers on the uptime check. + + --remove-headers=[KEY,...] + The list of header keys to remove from the uptime check. + + Settings. + + --display-name=DISPLAY_NAME + The display name for the uptime check or synthetic monitor. + + --period=PERIOD + The time between uptime check or synthetic monitor executions in + minutes, defaults to 1. Can be set for synthetic monitors. + + PERIOD must be one of: + + 1 + One minute + 10 + Ten minutes + 15 + Fifteen minutes + 5 + Five minutes + + --timeout=TIMEOUT + The maximum amount of time in seconds to wait for the request to + complete, defaults to 60. Can be set for synthetic monitors. + + Uptime check selected regions. + + At most one of these can be specified: + + --add-regions=[region,...] + The list of regions to add to the uptime check. region must be one + of: + + asia-pacific + asia-southeast1 + europe + europe-west1 + south-america + southamerica-east1 + usa-iowa + us-central1 + usa-oregon + us-west1 + usa-virginia + us-east4 + + --clear-regions=CLEAR_REGIONS + Clear all regions on the uptime check. This setting acts the same + as if all available regions were selected. + + --remove-regions=[region,...] + The list of regions to remove from the uptime check. region must be + one of: + + asia-pacific + asia-southeast1 + europe + europe-west1 + south-america + southamerica-east1 + usa-iowa + us-central1 + usa-oregon + us-west1 + usa-virginia + us-east4 + + --set-regions=[region,...] + The list of regions from which the check is run. At least 3 regions + must be selected. + + region must be one of: + + asia-pacific + asia-southeast1 + europe + europe-west1 + south-america + southamerica-east1 + usa-iowa + us-central1 + usa-oregon + us-west1 + usa-virginia + us-east4 + + User labels. Can be set for synthetic monitors. + + --update-user-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. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values + must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + At most one of these can be specified: + + --clear-user-labels + Remove all labels. If --update-user-labels is also specified then + --clear-user-labels is applied first. + + For example, to remove all labels: + + $ gcloud monitoring uptime update --clear-user-labels + + To remove all existing labels and create two new labels, foo and + baz: + + $ gcloud monitoring uptime update --clear-user-labels \ + --update-user-labels foo=bar,baz=qux + + --remove-user-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-user-labels is also specified then + --update-user-labels is applied first. + + Uptime check matcher settings. + + --matcher-content=MATCHER_CONTENT + String, regex or JSON content to match. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --matcher-type=MATCHER_TYPE + The type of content matcher that is applied to the server output, + defaults to contains-string. + + MATCHER_TYPE must be one of: + + contains-string + Response contains string + matches-json-path + Response matches at JSONPath + matches-regex + Response matches regex + not-contains-string + Response does not contain string + not-matches-json-path + Response does not match at JSONPath + not-matches-regex + Response does not match regex + + Uptime check matcher settings for JSON responses. + + --json-path=JSON_PATH + JSONPath within the response output pointing to the expected + content to match. Only used if --matcher-type is matches-json-path + or not-matches-json-path. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --json-path-matcher-type=JSON_PATH_MATCHER_TYPE + The type of JSONPath match that is applied to the JSON output, + defaults to exact-match. Only used if --matcher-type is + matches-json-path or not-matches-json-path. + + JSON_PATH_MATCHER_TYPE must be one of: + + exact-match + Response matches exact string at JSONPath + regex-match + Response matches regex at JSONPath + +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 monitoring uptime update + + $ gcloud beta monitoring uptime update + diff --git a/gcloud/netapp/storage-pools/create b/gcloud/netapp/storage-pools/create index 8fab58c36..301c56ef3 100644 --- a/gcloud/netapp/storage-pools/create +++ b/gcloud/netapp/storage-pools/create @@ -15,7 +15,7 @@ DESCRIPTION EXAMPLES The following command creates a Storage Pool named NAME using all possible - arguments + arguments with a VPC network in the same project $ gcloud netapp storage-pools create NAME --location=us-central1 \ --service-level=standard --capacity=2048 \ @@ -23,6 +23,16 @@ EXAMPLES --kms-config=kms-config1 --enable-ldap=true \ --description="example description" + The following command creates a Storage pool named NAME using all possible + arguments with a shared VPC network in a separate project called + VPC_PROJECT + + $ gcloud netapp storage-pools create NAME --location=us-central1 \ + --service-level=standard --capacity=2048 \ + --network=name=projects/VPC_PROJECT/locations/us-central1/\ + networks/default --active-directory=ad1 --kms-config=kms-config1 \ + --enable-ldap=true --description="example description" + POSITIONAL ARGUMENTS Storage pool resource - The Storage Pool to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -66,7 +76,11 @@ REQUIRED FLAGS psa-range is optional. name The name of the Google Compute Engine VPC network to which the - volume is connected. + volume is connected. Short-form (VPC network ID) or long-form (full + VPC network name: + projects/PROJECT/locations/LOCATION/networks/NETWORK) are both + accepted, but please use the long-form when attempting to create a + Storage Pool using a shared VPC. psa-range The psa-range is the name of the allocated range of the Private Service Access connection. The range you specify can't overlap with diff --git a/gcloud/projects/get-ancestors-iam-policy b/gcloud/projects/get-ancestors-iam-policy index 8e10c3e89..9fd084849 100644 --- a/gcloud/projects/get-ancestors-iam-policy +++ b/gcloud/projects/get-ancestors-iam-policy @@ -3,9 +3,9 @@ NAME and its ancestors SYNOPSIS - gcloud projects get-ancestors-iam-policy PROJECT_ID [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] + gcloud projects get-ancestors-iam-policy PROJECT_ID [--include-deny] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Get IAM policies for a project and its ancestors, given a project ID. @@ -28,6 +28,10 @@ POSITIONAL ARGUMENTS To set the project_id attribute: ▸ provide the argument project_id on the command line. +FLAGS + --include-deny + Include deny policies on the project and its ancestors in the result + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/resource-manager/folders/get-ancestors-iam-policy b/gcloud/resource-manager/folders/get-ancestors-iam-policy index 4de53ab7f..eb2065307 100644 --- a/gcloud/resource-manager/folders/get-ancestors-iam-policy +++ b/gcloud/resource-manager/folders/get-ancestors-iam-policy @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud resource-manager folders get-ancestors-iam-policy FOLDER_ID - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + [--include-deny] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Get IAM policies for a folder and its ancestors, given a folder ID. @@ -27,6 +27,10 @@ POSITIONAL ARGUMENTS To set the folder attribute: ▸ provide the argument folder_id on the command line. +FLAGS + --include-deny + Include deny policies on the project and its ancestors in the result + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/sql/backups/describe b/gcloud/sql/backups/describe index 313a15822..02578284e 100644 --- a/gcloud/sql/backups/describe +++ b/gcloud/sql/backups/describe @@ -2,7 +2,7 @@ NAME gcloud sql backups describe - retrieves information about a backup SYNOPSIS - gcloud sql backups describe ID --instance=INSTANCE, -i INSTANCE + gcloud sql backups describe ID [--instance=INSTANCE, -i INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -10,10 +10,10 @@ DESCRIPTION POSITIONAL ARGUMENTS ID - The ID of the backup run. You can find the ID by running $ gcloud sql - backups list -i {instance}. + The ID of the backup run. To find the ID, run the following command: $ + gcloud sql backups list -i {instance}. -REQUIRED FLAGS +FLAGS --instance=INSTANCE, -i INSTANCE Cloud SQL instance ID. diff --git a/gcloud/sql/generate-login-token b/gcloud/sql/generate-login-token index 68b775743..be879a3f3 100644 --- a/gcloud/sql/generate-login-token +++ b/gcloud/sql/generate-login-token @@ -3,7 +3,7 @@ NAME SYNOPSIS gcloud sql generate-login-token [--application-default-credential] - [--instance=INSTANCE] [GCLOUD_WIDE_FLAG ...] + [--instance=INSTANCE, -i INSTANCE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud sql generate-login-token generates an IAM token to use for logging @@ -33,7 +33,7 @@ FLAGS --application-default-credential Use application default credentials to generate the login token. - --instance=INSTANCE + --instance=INSTANCE, -i INSTANCE Cloud SQL instance ID. GCLOUD WIDE FLAGS diff --git a/gcloud/storage/buckets/update b/gcloud/storage/buckets/update index 7757262a3..8d120555f 100644 --- a/gcloud/storage/buckets/update +++ b/gcloud/storage/buckets/update @@ -2,11 +2,11 @@ NAME gcloud storage buckets update - update bucket settings SYNOPSIS - gcloud storage buckets update URL [URL ...] - [--additional-headers=HEADER=VALUE] [--clear-soft-delete] - [--continue-on-error, -c] [--[no-]default-event-based-hold] + gcloud storage buckets update [URL ...] [--additional-headers=HEADER=VALUE] + [--clear-soft-delete] [--continue-on-error, -c] + [--[no-]default-event-based-hold] [--default-storage-class=DEFAULT_STORAGE_CLASS] - [--lock-retention-period] + [--lock-retention-period] [--read-paths-from-stdin, -I] [--recovery-point-objective=SETTING, --rpo=SETTING] [--[no-]requester-pays] [--soft-delete-duration=SOFT_DELETE_DURATION] [--[no-]uniform-bucket-level-access] [--[no-]versioning] @@ -57,8 +57,8 @@ EXAMPLES --clear-retention-period POSITIONAL ARGUMENTS - URL [URL ...] - URLs of the buckets to update. + [URL ...] + Specifies the URLs of the buckets to update. FLAGS --additional-headers=HEADER=VALUE @@ -93,6 +93,9 @@ FLAGS duration. Once locked, deleting the bucket is the only way to "remove" a retention policy. + --read-paths-from-stdin, -I + Read the list of URLs from stdin. + --recovery-point-objective=SETTING, --rpo=SETTING Sets the recovery point objective (https://cloud.google.com/architecture/dr-scenarios-planning-guide#basics_of_dr_planning) diff --git a/gcloud/workstations/configs/create b/gcloud/workstations/configs/create index eaf3798af..71da4e9ec 100644 --- a/gcloud/workstations/configs/create +++ b/gcloud/workstations/configs/create @@ -10,8 +10,9 @@ SYNOPSIS [--container-env=[CONTAINER_ENV,...]] [--container-run-as-user=CONTAINER_RUN_AS_USER] [--container-working-dir=CONTAINER_WORKING_DIR] - [--disable-public-ip-addresses] [--enable-audit-agent] - [--enable-confidential-compute] [--enable-nested-virtualization] + [--disable-public-ip-addresses] [--disable-tcp-connections] + [--enable-audit-agent] [--enable-confidential-compute] + [--enable-nested-virtualization] [--idle-timeout=IDLE_TIMEOUT; default=7200] [--labels=[LABELS,...]] [--machine-type=MACHINE_TYPE; default="e2-standard-4"] [--network-tags=[NETWORK_TAGS,...]] @@ -135,6 +136,10 @@ FLAGS Default value is false. If set, instances will have no public IP address. + --disable-tcp-connections + Default value is false. If set, workstations will not allow plain TCP + connections. + --enable-audit-agent Whether to enable Linux auditd logging on the workstation. When enabled, a service account must also be specified that has diff --git a/gcloud/workstations/configs/update b/gcloud/workstations/configs/update index f2da48242..91cecff31 100644 --- a/gcloud/workstations/configs/update +++ b/gcloud/workstations/configs/update @@ -21,6 +21,7 @@ SYNOPSIS [--shielded-vtpm] [--container-custom-image=CONTAINER_CUSTOM_IMAGE | --container-predefined-image=CONTAINER_PREDEFINED_IMAGE] + [--disable-tcp-connections | --enable-tcp-connections] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -227,6 +228,16 @@ FLAGS webstorm WebStorm + At most one of these can be specified: + + --disable-tcp-connections + Default value is false. If set, workstations will allow plain TCP + connections. + + --enable-tcp-connections + Default value is false. If set, workstations will allow plain TCP + connections. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format,