diff --git a/gcloud/_version b/gcloud/_version index 8b86030ea..da3f0b613 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,6 +1,6 @@ -Google Cloud SDK 385.0.0 -alpha 2022.05.06 -beta 2022.05.06 +Google Cloud SDK 386.0.0 +alpha 2022.05.13 +beta 2022.05.13 bq 2.0.74 -core 2022.05.06 +core 2022.05.13 gsutil 5.10 diff --git a/gcloud/active-directory/domains/backups/create b/gcloud/active-directory/domains/backups/create new file mode 100644 index 000000000..631bccb01 --- /dev/null +++ b/gcloud/active-directory/domains/backups/create @@ -0,0 +1,83 @@ +NAME + gcloud active-directory domains backups create - create a Managed Microsoft + AD domain backup + +SYNOPSIS + gcloud active-directory domains backups create (BACKUP : --domain=DOMAIN) + [--async] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new Managed Microsoft AD domain backup with the specified name + using Google Cloud's Managed Service for Microsoft Active Directory. + + This command can fail for the following reasons: + ▪ The specified domain doesn't exist. + ▪ The specified domain is being created. + ▪ A backup already exists with the same target domain name. + ▪ The active account doesn't have permission to access the specified + domain. + ▪ The active account doesn't have permission to create AD domain + backups. + +EXAMPLES + To create an AD domain backup named my-backup under domain my-domain.com, + run: + + $ gcloud active-directory domains backups create my-backup \ + --domain=my-domain.com --project=my-proj --async + +POSITIONAL ARGUMENTS + Backup resource - Name of the Managed Microsoft AD domain backup you want + to create. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. To set the project + attribute: + ◆ provide the argument backup 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. + + BACKUP + ID of the backup or fully qualified identifier for the backup. To set + the backup attribute: + ▸ provide the argument backup on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --domain=DOMAIN + The fully-qualified domain name of the Microsoft Active Directory + domain. To set the domain attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --domain on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --labels=KEY=VALUE + List of label KEY=VALUE pairs to add. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 managedidentities/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/managed-microsoft-ad/ + +NOTES + These variants are also available: + + $ gcloud alpha active-directory domains backups create + + $ gcloud beta active-directory domains backups create + diff --git a/gcloud/active-directory/domains/backups/delete b/gcloud/active-directory/domains/backups/delete new file mode 100644 index 000000000..119c67558 --- /dev/null +++ b/gcloud/active-directory/domains/backups/delete @@ -0,0 +1,78 @@ +NAME + gcloud active-directory domains backups delete - delete a Managed Microsoft + AD domain backup + +SYNOPSIS + gcloud active-directory domains backups delete (BACKUP : --domain=DOMAIN) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Managed Microsoft AD domain backup with the specified name using + Google Cloud's Managed Service for Microsoft Active Directory. + + This command can fail for the following reasons: + ▪ The specified backup doesn't exist. + ▪ The active account doesn't have permission to access the specified + domain. + ▪ The active account doesn't have permission to access the specified AD + domain backup. + +EXAMPLES + To delete an AD domain backup my-backup under domain `projects/my-proj/locations/global/domains/my-domain.com`, run: + + $ gcloud active-directory domains backups delete \ + projects/my-proj/locations/global/domains/my-domain.com/\ + backups/my-backup --async + +POSITIONAL ARGUMENTS + Backup resource - Name of the Managed Microsoft AD domain backup 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 backup 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. + + BACKUP + ID of the backup or fully qualified identifier for the backup. To set + the backup attribute: + ▸ provide the argument backup on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --domain=DOMAIN + The fully-qualified domain name of the Microsoft Active Directory + domain. To set the domain attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --domain on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedidentities/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/managed-microsoft-ad/ + +NOTES + These variants are also available: + + $ gcloud alpha active-directory domains backups delete + + $ gcloud beta active-directory domains backups delete + diff --git a/gcloud/active-directory/domains/backups/describe b/gcloud/active-directory/domains/backups/describe new file mode 100644 index 000000000..db07289bf --- /dev/null +++ b/gcloud/active-directory/domains/backups/describe @@ -0,0 +1,74 @@ +NAME + gcloud active-directory domains backups describe - describe a Managed + Microsoft AD domain backup + +SYNOPSIS + gcloud active-directory domains backups describe (BACKUP : --domain=DOMAIN) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show metadata for a Managed Microsoft AD domain backup. + + Displays all metadata associated with an Active Directory domain backup + when provided with a valid domain backup name. + + This command can fail for the following reasons: + ▪ The specified domain backup doesn't exist. + ▪ The active account doesn't have permission to access the specified + domain. + +EXAMPLES + To display all metadata associated with an AD domain backup with the name + my-backup under the domain my-domain in project my-project, run: + + $ gcloud active-directory domains backups describe \ + projects/my-proj/locations/global/domains/my-domain.com/\ + backups/my-backup + +POSITIONAL ARGUMENTS + Backup resource - Name of the Managed Microsoft AD domain backup 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 backup 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. + + BACKUP + ID of the backup or fully qualified identifier for the backup. To set + the backup attribute: + ▸ provide the argument backup on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --domain=DOMAIN + The fully-qualified domain name of the Microsoft Active Directory + domain. To set the domain attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --domain 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 managedidentities/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/managed-microsoft-ad/ + +NOTES + These variants are also available: + + $ gcloud alpha active-directory domains backups describe + + $ gcloud beta active-directory domains backups describe + diff --git a/gcloud/active-directory/domains/backups/help b/gcloud/active-directory/domains/backups/help new file mode 100644 index 000000000..f0c400d79 --- /dev/null +++ b/gcloud/active-directory/domains/backups/help @@ -0,0 +1,39 @@ +NAME + gcloud active-directory domains backups - managed Microsoft AD Backups + +SYNOPSIS + gcloud active-directory domains backups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Managed Microsoft AD Backups. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Managed Microsoft AD domain backup. + + delete + Delete a Managed Microsoft AD domain backup. + + describe + Describe a Managed Microsoft AD domain backup. + + list + List all Managed Microsoft AD domain backups. + + update + Update a Managed Microsoft AD domain backup. + +NOTES + These variants are also available: + + $ gcloud alpha active-directory domains backups + + $ gcloud beta active-directory domains backups + diff --git a/gcloud/active-directory/domains/backups/list b/gcloud/active-directory/domains/backups/list new file mode 100644 index 000000000..87b1bafa3 --- /dev/null +++ b/gcloud/active-directory/domains/backups/list @@ -0,0 +1,94 @@ +NAME + gcloud active-directory domains backups list - list all Managed Microsoft + AD domain backups + +SYNOPSIS + gcloud active-directory domains backups list --domain=DOMAIN + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all Managed Microsoft AD domain backups in the specified Managed + Microsoft AD domain. + + Displays associated Active Directory domain backups. + + This command can fail for the following reasons: + ▪ The active account doesn't have permission to access the specified + domain. + +EXAMPLES + To list all AD domain backups in the project my-project under domain + my-domain.com, run: + + $ gcloud active-directory domains backups list \ + --project=my-project --domain=my-domain.com --limit=5 + +REQUIRED FLAGS + Domain resource - Name of the domain for which you want to list all + associated Managed Microsoft AD domain backups. 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 --domain 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. + + --domain=DOMAIN + ID of the domain or fully qualified identifier for the domain. To set + the domain attribute: + ▸ provide the argument --domain on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedidentities/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/managed-microsoft-ad/ + +NOTES + These variants are also available: + + $ gcloud alpha active-directory domains backups list + + $ gcloud beta active-directory domains backups list + diff --git a/gcloud/active-directory/domains/backups/update b/gcloud/active-directory/domains/backups/update new file mode 100644 index 000000000..602ef3c22 --- /dev/null +++ b/gcloud/active-directory/domains/backups/update @@ -0,0 +1,105 @@ +NAME + gcloud active-directory domains backups update - update a Managed Microsoft + AD domain backup + +SYNOPSIS + gcloud active-directory domains backups update (BACKUP : --domain=DOMAIN) + [--async] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Managed Microsoft AD domain backup. + ▪ The specified backup doesn't exist. + ▪ The active account doesn't have permission to access the specified + domain. + ▪ The active account doesn't have permission to access the specified + domain backup. + +EXAMPLES + To update an AD domain backup my-backup under domain `projects/my-proj/locations/global/domains/my-domain.com` with the labels `l1` and `l2`, run: + + $ gcloud active-directory domains backups update \ + projects/my-proj/locations/global/domains/my-domain.com/\ + backups/my-backup --update-labels=l1=1,l2=2 + +POSITIONAL ARGUMENTS + Backup resource - Name of the Managed Microsoft AD domain backup you want + to update. 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 backup 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. + + BACKUP + ID of the backup or fully qualified identifier for the backup. To set + the backup attribute: + ▸ provide the argument backup on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --domain=DOMAIN + The fully-qualified domain name of the Microsoft Active Directory + domain. To set the domain attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --domain on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + 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-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud active-directory domains backups update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud active-directory domains backups update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 managedidentities/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/managed-microsoft-ad/ + +NOTES + These variants are also available: + + $ gcloud alpha active-directory domains backups update + + $ gcloud beta active-directory domains backups update + diff --git a/gcloud/active-directory/domains/help b/gcloud/active-directory/domains/help index 4bd9c7e75..453f76c50 100644 --- a/gcloud/active-directory/domains/help +++ b/gcloud/active-directory/domains/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + backups + Managed Microsoft AD Backups. + trusts Manage Managed Microsoft AD domains. @@ -42,6 +45,9 @@ COMMANDS reset-admin-password Reset the admin password for a Managed Microsoft AD domain. + restore + Restore a domain from the specified backup. + set-iam-policy Set the IAM policy for a Managed Microsoft AD domain. diff --git a/gcloud/active-directory/domains/restore b/gcloud/active-directory/domains/restore new file mode 100644 index 000000000..342337f37 --- /dev/null +++ b/gcloud/active-directory/domains/restore @@ -0,0 +1,70 @@ +NAME + gcloud active-directory domains restore - restore a domain from the + specified backup + +SYNOPSIS + gcloud active-directory domains restore DOMAIN --backup=BACKUP [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Restore a Managed Microsoft AD domain to a previous point in time when the + backup was taken. + + This command can fail for the following reasons: + ▪ The specified domain doesn't exist. + ▪ The specified backup doesn't exist. + ▪ The active account doesn't have permission to restore the specified + domain. + +EXAMPLES + To restore the domain my-domain.com from backup my-backup, run: + + $ gcloud active-directory domains restore my-domain.com \ + --backup=my-backup --async + +POSITIONAL ARGUMENTS + Domain resource - Name of the Managed Microsoft AD domain you want to + restore. 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 domain 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. + + DOMAIN + ID of the domain or fully qualified identifier for the domain. To set + the domain attribute: + ▸ provide the argument domain on the command line. + +REQUIRED FLAGS + --backup=BACKUP + Name of the domain backup from which you want to restore the Managed + Microsoft AD domain. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the managedidentities/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/managed-microsoft-ad/ + +NOTES + These variants are also available: + + $ gcloud alpha active-directory domains restore + + $ gcloud beta active-directory domains restore + diff --git a/gcloud/alpha/active-directory/domains/backups/create b/gcloud/alpha/active-directory/domains/backups/create index bfc5d3e33..a56cb31dc 100644 --- a/gcloud/alpha/active-directory/domains/backups/create +++ b/gcloud/alpha/active-directory/domains/backups/create @@ -1,6 +1,6 @@ NAME gcloud alpha active-directory domains backups create - create a Managed - Microsoft Active Directory domain backup + Microsoft AD domain backup SYNOPSIS gcloud alpha active-directory domains backups create @@ -8,21 +8,21 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Create a new Managed Microsoft AD domain backup with the given name - using Google Cloud's Managed Service for Microsoft Active Directory. + (ALPHA) Create a new Managed Microsoft AD domain backup with the specified + name using Google Cloud's Managed Service for Microsoft Active Directory. This command can fail for the following reasons: - ▪ The domain specified does not exist. - ▪ The domain specified is being created. + ▪ The specified domain doesn't exist. + ▪ The specified domain is being created. ▪ A backup already exists with the same target domain name. - ▪ The active account does not have permission to access the given + ▪ The active account doesn't have permission to access the specified domain. - ▪ The active account does not have permission to create AD domain + ▪ The active account doesn't have permission to create AD domain backups. EXAMPLES - The following command creates an Active Directory domain backup named - my-backup under domain my-domain.com + To create an AD domain backup named my-backup under domain my-domain.com, + run: $ gcloud alpha active-directory domains backups create my-backup \ --domain=my-domain.com --project=my-proj --async @@ -80,7 +80,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud active-directory domains backups create $ gcloud beta active-directory domains backups create diff --git a/gcloud/alpha/active-directory/domains/backups/delete b/gcloud/alpha/active-directory/domains/backups/delete index 98531661b..1665b860c 100644 --- a/gcloud/alpha/active-directory/domains/backups/delete +++ b/gcloud/alpha/active-directory/domains/backups/delete @@ -1,24 +1,24 @@ NAME gcloud alpha active-directory domains backups delete - delete a Managed - Microsoft Active Directory domain backup + Microsoft AD domain backup SYNOPSIS gcloud alpha active-directory domains backups delete (BACKUP : --domain=DOMAIN) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Delete a Managed Microsoft AD domain backup with the given name + (ALPHA) Delete a Managed Microsoft AD domain backup with the specified name using Google Cloud's Managed Service for Microsoft Active Directory. This command can fail for the following reasons: - ▪ TThe backup specified does not exist. - ▪ The active account does not have permission to access the given + ▪ The specified backup doesn't exist. + ▪ The active account doesn't have permission to access the specified domain. - ▪ The active account does not have permission to access the given AD - backup. + ▪ The active account doesn't have permission to access the specified AD + domain backup. EXAMPLES - The following command deletes an AD domain backup my-backup under domain projects/my-proj/locations/global/domains/my-domain.com + To delete an AD domain backup my-backup under domain `projects/my-proj/locations/global/domains/my-domain.com`, run: $ gcloud alpha active-directory domains backups delete \ projects/my-proj/locations/global/domains/my-domain.com/\ @@ -74,7 +74,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud active-directory domains backups delete $ gcloud beta active-directory domains backups delete diff --git a/gcloud/alpha/active-directory/domains/backups/describe b/gcloud/alpha/active-directory/domains/backups/describe index f05f6cfbe..1d7a09e0b 100644 --- a/gcloud/alpha/active-directory/domains/backups/describe +++ b/gcloud/alpha/active-directory/domains/backups/describe @@ -1,6 +1,6 @@ NAME gcloud alpha active-directory domains backups describe - describe a Managed - Microsoft Active Directory domain backup + Microsoft AD domain backup SYNOPSIS gcloud alpha active-directory domains backups describe @@ -9,17 +9,17 @@ SYNOPSIS DESCRIPTION (ALPHA) Show metadata for a Managed Microsoft AD domain backup. - Displays all metadata associated with a Active Directory domain backup - given a valid domain backup name. + Displays all metadata associated with an Active Directory domain backup + when provided with a valid domain backup name. This command can fail for the following reasons: - ▪ The specified domain backup does not exist. - ▪ The active account does not have permission to access the given + ▪ The specified domain backup doesn't exist. + ▪ The active account doesn't have permission to access the specified domain. EXAMPLES - The following command gets metadata for an AD domain backup with the name - my-backup under the domain my-domain in project my-project. + To display all metadata associated with an AD domain backup with the name + my-backup under the domain my-domain in project my-project, run: $ gcloud alpha active-directory domains backups describe \ projects/my-proj/locations/global/domains/my-domain.com/\ @@ -70,7 +70,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud active-directory domains backups describe $ gcloud beta active-directory domains backups describe diff --git a/gcloud/alpha/active-directory/domains/backups/help b/gcloud/alpha/active-directory/domains/backups/help index d07918dae..843bcc5b4 100644 --- a/gcloud/alpha/active-directory/domains/backups/help +++ b/gcloud/alpha/active-directory/domains/backups/help @@ -18,25 +18,27 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create a Managed Microsoft Active Directory domain backup. + (ALPHA) Create a Managed Microsoft AD domain backup. delete - (ALPHA) Delete a Managed Microsoft Active Directory domain backup. + (ALPHA) Delete a Managed Microsoft AD domain backup. describe - (ALPHA) Describe a Managed Microsoft Active Directory domain backup. + (ALPHA) Describe a Managed Microsoft AD domain backup. list - (ALPHA) List all Managed Microsoft Active Directory domain backups. + (ALPHA) List all Managed Microsoft AD domain backups. update - (ALPHA) Update a managed Microsoft Active Directory domain backup. + (ALPHA) Update a Managed Microsoft AD domain backup. NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud active-directory domains backups $ gcloud beta active-directory domains backups diff --git a/gcloud/alpha/active-directory/domains/backups/list b/gcloud/alpha/active-directory/domains/backups/list index 3425c0a47..9adfe911b 100644 --- a/gcloud/alpha/active-directory/domains/backups/list +++ b/gcloud/alpha/active-directory/domains/backups/list @@ -1,6 +1,6 @@ NAME gcloud alpha active-directory domains backups list - list all Managed - Microsoft Active Directory domain backups + Microsoft AD domain backups SYNOPSIS gcloud alpha active-directory domains backups list --domain=DOMAIN @@ -8,27 +8,27 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List all Managed Microsoft AD domain backups in the given Managed - Microsoft AD domain. + (ALPHA) List all Managed Microsoft AD domain backups in the specified + Managed Microsoft AD domain. Displays associated Active Directory domain backups. This command can fail for the following reasons: - ▪ The active account does not have permission to access the given + ▪ The active account doesn't have permission to access the specified domain. EXAMPLES - The following command lists all an AD domain backups in the project - my-project and domain my-domain.com. + To list all AD domain backups in the project my-project under domain + my-domain.com, run: $ gcloud alpha active-directory domains backups list \ --project=my-project --domain=my-domain.com --limit=5 REQUIRED FLAGS - Domain resource - Name of the domain under which you want to list all - Managed Microsoft AD domain backups. 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: + Domain resource - Name of the domain for which you want to list all + associated Managed Microsoft AD domain backups. 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 --domain on the command line with a fully specified name; ◆ set the property core/project; @@ -90,7 +90,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud active-directory domains backups list $ gcloud beta active-directory domains backups list diff --git a/gcloud/alpha/active-directory/domains/backups/update b/gcloud/alpha/active-directory/domains/backups/update index 261ac76ea..e442bacb6 100644 --- a/gcloud/alpha/active-directory/domains/backups/update +++ b/gcloud/alpha/active-directory/domains/backups/update @@ -1,6 +1,6 @@ NAME - gcloud alpha active-directory domains backups update - update a managed - Microsoft Active Directory domain backup + gcloud alpha active-directory domains backups update - update a Managed + Microsoft AD domain backup SYNOPSIS gcloud alpha active-directory domains backups update @@ -8,15 +8,15 @@ SYNOPSIS [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Update a managed Microsoft Active Directory domain backup. - ▪ The backup specified does not exist. - ▪ The active account does not have permission to access the given + (ALPHA) Update a Managed Microsoft AD domain backup. + ▪ The specified backup doesn't exist. + ▪ The active account doesn't have permission to access the specified domain. - ▪ The active account does not have permission to access the given - backup. + ▪ The active account doesn't have permission to access the specified + domain backup. EXAMPLES - The following command updates an AD domain backup my-backup under domain projects/my-proj/locations/global/domains/my-domain.com with the labels l1 and l2 + To update an AD domain backup my-backup under domain `projects/my-proj/locations/global/domains/my-domain.com` with the labels `l1` and `l2`, run: $ gcloud alpha active-directory domains backups update \ projects/my-proj/locations/global/domains/my-domain.com/\ @@ -101,7 +101,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud active-directory domains backups update $ gcloud beta active-directory domains backups update diff --git a/gcloud/alpha/active-directory/domains/help b/gcloud/alpha/active-directory/domains/help index 5279d858b..736129f43 100644 --- a/gcloud/alpha/active-directory/domains/help +++ b/gcloud/alpha/active-directory/domains/help @@ -51,7 +51,7 @@ COMMANDS (ALPHA) Reset the admin password for a Managed Microsoft AD domain. restore - (ALPHA) Restore the domain from The specified backup. + (ALPHA) Restore a domain from the specified backup. set-iam-policy (ALPHA) Set the IAM policy for a Managed Microsoft AD domain. diff --git a/gcloud/alpha/active-directory/domains/restore b/gcloud/alpha/active-directory/domains/restore index 4ddb0ce20..478008908 100644 --- a/gcloud/alpha/active-directory/domains/restore +++ b/gcloud/alpha/active-directory/domains/restore @@ -1,5 +1,5 @@ NAME - gcloud alpha active-directory domains restore - restore the domain from The + gcloud alpha active-directory domains restore - restore a domain from the specified backup SYNOPSIS @@ -7,24 +7,25 @@ SYNOPSIS [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Restore a Managed Microsoft Active Directory domain to a previous - point in time when the backup was taken. + (ALPHA) Restore a Managed Microsoft AD domain to a previous point in time + when the backup was taken. This command can fail for the following reasons: - ▪ The domain specified does not exist. - ▪ The backup specified does not exist. - ▪ The active account does not have permission to restore the domain. + ▪ The specified domain doesn't exist. + ▪ The specified backup doesn't exist. + ▪ The active account doesn't have permission to restore the specified + domain. EXAMPLES - To restore the domain my-domain.com from backup my-backup: + To restore the domain my-domain.com from backup my-backup, run: $ gcloud alpha active-directory domains restore my-domain.com \ --backup=my-backup --async POSITIONAL ARGUMENTS - Domain resource - Name of the managed Managed Microsoft AD domain you want - to restore. 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 + Domain resource - Name of the Managed Microsoft AD domain you want to + restore. 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 domain on the command line with a fully specified name; @@ -40,8 +41,8 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --backup=BACKUP - Name of the managed Managed Microsoft AD domain backup you want to - restore from to. + Name of the domain backup from which you want to restore the Managed + Microsoft AD domain. OPTIONAL FLAGS --async @@ -65,7 +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. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud active-directory domains restore $ gcloud beta active-directory domains restore diff --git a/gcloud/alpha/alloydb/backups/create b/gcloud/alpha/alloydb/backups/create new file mode 100644 index 000000000..1d299f5ce --- /dev/null +++ b/gcloud/alpha/alloydb/backups/create @@ -0,0 +1,50 @@ +NAME + gcloud alpha alloydb backups create - creates a new AlloyDB backup within a + given project + +SYNOPSIS + gcloud alpha alloydb backups create BACKUP --cluster=CLUSTER + --region=REGION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates a new AlloyDB backup within a given project. + +EXAMPLES + To create a new backup, run: + + $ gcloud alpha alloydb backups create my-backup \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + BACKUP + AlloyDB backup ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + The region of the cluster to backup. Note: both the cluster and the + backup have to be in the same region. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb backups create + diff --git a/gcloud/alpha/alloydb/backups/delete b/gcloud/alpha/alloydb/backups/delete new file mode 100644 index 000000000..99eea5bac --- /dev/null +++ b/gcloud/alpha/alloydb/backups/delete @@ -0,0 +1,46 @@ +NAME + gcloud alpha alloydb backups delete - deletes an AlloyDB backup within a + given project + +SYNOPSIS + gcloud alpha alloydb backups delete BACKUP --region=REGION [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes an AlloyDB backup within a given project. + +EXAMPLES + To delete a backup, run: + + $ gcloud alpha alloydb backups delete my-backup --region=us-central1 + +POSITIONAL ARGUMENTS + BACKUP + AlloyDB backup ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb backups delete + diff --git a/gcloud/alpha/alloydb/backups/describe b/gcloud/alpha/alloydb/backups/describe new file mode 100644 index 000000000..256652b88 --- /dev/null +++ b/gcloud/alpha/alloydb/backups/describe @@ -0,0 +1,42 @@ +NAME + gcloud alpha alloydb backups describe - creates a new AlloyDB backup within + a given project and location + +SYNOPSIS + gcloud alpha alloydb backups describe BACKUP --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates a new AlloyDB backup within a given project and location. + +EXAMPLES + To describe a backup, run: + + $ gcloud alpha alloydb backups describe my-backup \ + --region=us-central1 + +POSITIONAL ARGUMENTS + BACKUP + AlloyDB backup ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb backups describe + diff --git a/gcloud/alpha/alloydb/backups/help b/gcloud/alpha/alloydb/backups/help new file mode 100644 index 000000000..a3b240094 --- /dev/null +++ b/gcloud/alpha/alloydb/backups/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha alloydb backups - provide commands for managing AlloyDB + backups + +SYNOPSIS + gcloud alpha alloydb backups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Provide commands for managing AlloyDB backups including creating, + deleting, and listing backups. + +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) Creates a new AlloyDB backup within a given project. + + delete + (ALPHA) Deletes an AlloyDB backup within a given project. + + describe + (ALPHA) Creates a new AlloyDB backup within a given project and + location. + + list + (ALPHA) Lists AlloyDB backups in a given project. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb backups + diff --git a/gcloud/alpha/alloydb/backups/list b/gcloud/alpha/alloydb/backups/list new file mode 100644 index 000000000..8e2a6460d --- /dev/null +++ b/gcloud/alpha/alloydb/backups/list @@ -0,0 +1,72 @@ +NAME + gcloud alpha alloydb backups list - lists AlloyDB backups in a given + project + +SYNOPSIS + gcloud alpha alloydb backups list [--region=REGION; default="-"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists AlloyDB backups in a given project in the alphabetical order + of the backup name. + +EXAMPLES + To list backups, run: + + $ gcloud alpha alloydb backups list --region=us-central1 + +FLAGS + --region=REGION; default="-" + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + Default: list clusters in all regions. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb backups list + diff --git a/gcloud/alpha/alloydb/clusters/create b/gcloud/alpha/alloydb/clusters/create new file mode 100644 index 000000000..47c4b8bf2 --- /dev/null +++ b/gcloud/alpha/alloydb/clusters/create @@ -0,0 +1,57 @@ +NAME + gcloud alpha alloydb clusters create - creates a new AlloyDB cluster within + a given project + +SYNOPSIS + gcloud alpha alloydb clusters create CLUSTER --password=PASSWORD + --region=REGION [--async] [--network=NETWORK] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates a new AlloyDB cluster within a given project. + +EXAMPLES + To create a new cluster, run: + + $ gcloud alpha alloydb clusters create my-cluster \ + --region=us-central1 --password=postgres + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + --password=PASSWORD + Initial postgres user password to set up during cluster creation. + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --network=NETWORK + Network in the current project that the instance will be part of. To + specify using a network with a shared VPC, use the full URL of the + network. For an example host project, 'testproject', and shared + network, 'testsharednetwork', this would be of the + form:--network=projects/testproject/global/networks/testsharednetwork + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb clusters create + diff --git a/gcloud/alpha/alloydb/clusters/delete b/gcloud/alpha/alloydb/clusters/delete new file mode 100644 index 000000000..027e6179f --- /dev/null +++ b/gcloud/alpha/alloydb/clusters/delete @@ -0,0 +1,56 @@ +NAME + gcloud alpha alloydb clusters delete - deletes an AlloyDB cluster in a + given region + +SYNOPSIS + gcloud alpha alloydb clusters delete CLUSTER --region=REGION [--async] + [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes an AlloyDB cluster in a given region. + +EXAMPLES + To delete a cluster, run: + + $ gcloud alpha alloydb clusters delete my-cluster \ + --region=us-central1 + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --force + Default value is false. + + If flag is specified, deletes instances (if any) within this cluster, + before deleting the cluster. + + If flag is not specified, cluster delete will fail if there are + instances present in the cluster. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb clusters delete + diff --git a/gcloud/alpha/alloydb/clusters/describe b/gcloud/alpha/alloydb/clusters/describe new file mode 100644 index 000000000..e4d968cad --- /dev/null +++ b/gcloud/alpha/alloydb/clusters/describe @@ -0,0 +1,42 @@ +NAME + gcloud alpha alloydb clusters describe - describes an AlloyDB cluster in a + given project and region + +SYNOPSIS + gcloud alpha alloydb clusters describe CLUSTER --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describes an AlloyDB cluster in a given project and region. + +EXAMPLES + To describe a cluster, run: + + $ gcloud alpha alloydb clusters describe my-cluster \ + --region=us-central1 + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb clusters describe + diff --git a/gcloud/alpha/alloydb/clusters/help b/gcloud/alpha/alloydb/clusters/help new file mode 100644 index 000000000..26300ff81 --- /dev/null +++ b/gcloud/alpha/alloydb/clusters/help @@ -0,0 +1,45 @@ +NAME + gcloud alpha alloydb clusters - provide commands for managing AlloyDB + clusters + +SYNOPSIS + gcloud alpha alloydb clusters COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Provide commands for managing AlloyDB clusters including creating, + configuring, restarting, and deleting clusters. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Creates a new AlloyDB cluster within a given project. + + delete + (ALPHA) Deletes an AlloyDB cluster in a given region. + + describe + (ALPHA) Describes an AlloyDB cluster in a given project and region. + + list + (ALPHA) Lists AlloyDB clusters in a given project and region. + + restore + (ALPHA) Restores an AlloyDB cluster from a given backup. + + update + (ALPHA) Updates an AlloyDB cluster within a given project and region. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb clusters + diff --git a/gcloud/alpha/alloydb/clusters/list b/gcloud/alpha/alloydb/clusters/list new file mode 100644 index 000000000..b433a9d7e --- /dev/null +++ b/gcloud/alpha/alloydb/clusters/list @@ -0,0 +1,72 @@ +NAME + gcloud alpha alloydb clusters list - lists AlloyDB clusters in a given + project and region + +SYNOPSIS + gcloud alpha alloydb clusters list [--region=REGION; default="-"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists AlloyDB clusters in a given project in the alphabetical order + of the cluster name. + +EXAMPLES + To list clusters, run: + + $ gcloud alpha alloydb clusters list --region=us-central1 + +FLAGS + --region=REGION; default="-" + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + Default: list clusters in all regions. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb clusters list + diff --git a/gcloud/alpha/alloydb/clusters/restore b/gcloud/alpha/alloydb/clusters/restore new file mode 100644 index 000000000..e08a03c3f --- /dev/null +++ b/gcloud/alpha/alloydb/clusters/restore @@ -0,0 +1,57 @@ +NAME + gcloud alpha alloydb clusters restore - restores an AlloyDB cluster from a + given backup + +SYNOPSIS + gcloud alpha alloydb clusters restore CLUSTER --backup=BACKUP + --region=REGION [--async] [--network=NETWORK] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Restores an AlloyDB cluster from a given backup. + +EXAMPLES + To restore a cluster from a backup, run: + + $ gcloud alpha alloydb clusters restore my-cluster \ + --region=us-central1 --backup=my-backup + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + --backup=BACKUP + AlloyDB backup ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --network=NETWORK + Network in the current project that the instance will be part of. To + specify using a network with a shared VPC, use the full URL of the + network. For an example host project, 'testproject', and shared + network, 'testsharednetwork', this would be of the + form:--network=projects/testproject/global/networks/testsharednetwork + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb clusters restore + diff --git a/gcloud/alpha/alloydb/clusters/update b/gcloud/alpha/alloydb/clusters/update new file mode 100644 index 000000000..c5e21bb4b --- /dev/null +++ b/gcloud/alpha/alloydb/clusters/update @@ -0,0 +1,106 @@ +NAME + gcloud alpha alloydb clusters update - updates an AlloyDB cluster within a + given project and region + +SYNOPSIS + gcloud alpha alloydb clusters update CLUSTER --region=REGION [--async] + [--clear-automated-backup | --disable-automated-backup + | [--automated-backup-days-of-week=[DAYS_OF_WEEK,...] + --automated-backup-start-times=[START_TIMES,...] + : --automated-backup-window=TIMEOUT_PERIOD + --automated-backup-retention-count=RETENTION_COUNT + | --automated-backup-retention-period=RETENTION_PERIOD]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates an AlloyDB cluster within a given project and region. + +EXAMPLES + To update a cluster, run: + + $ gcloud alpha alloydb clusters update my-cluster \ + --region=us-central1 --automated-backup-start-times=12:00 \ + --automated-backup-days-of-week=MONDAY \ + --automated-backup-retention-count=10 + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + Automated backup policy. + + At most one of these can be specified: + + --clear-automated-backup + Clears the automated backup policy on the cluster. The default + automated backup policy will be used. + + --disable-automated-backup + Disables automated backups on the cluster. + + Enable automated backup policy. + + --automated-backup-days-of-week=[DAYS_OF_WEEK,...] + Comma-separated list of days of the week to perform a backup. At + least one day of the week must be provided. (e.g., + --automated-backup-days-of-week=MONDAY,WEDNESDAY,SUNDAY). + DAYS_OF_WEEK must be one of: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, + FRIDAY, SATURDAY, SUNDAY. + + This flag must be specified if any of the other arguments in this + group are specified. + + --automated-backup-start-times=[START_TIMES,...] + Comma-separated list of times during the day to start a backup. At + least one start time must be provided. The start times are assumed + to be in UTC and required to be an exact hour in the format HH:00. + (e.g., --automated-backup-start-times=01:00,13:00) + + This flag must be specified if any of the other arguments in this + group are specified. + + --automated-backup-window=TIMEOUT_PERIOD + The length of the time window beginning at start time during which + a backup can be taken. If a backup does not succeed within this + time window, it will be canceled and considered failed. The backup + window must be at least 5 minutes long. There is no upper bound on + the window. If not set, it will default to 1 hour. + + Retention policy. If no retention policy is provided, all automated + backups will be retained. + + At most one of these can be specified: + + --automated-backup-retention-count=RETENTION_COUNT + Number of most recent successful backups retained. + + --automated-backup-retention-period=RETENTION_PERIOD + Retention period of the backup relative to creation time. See $ + gcloud topic datetimes for information on duration formats. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb clusters update + diff --git a/gcloud/alpha/alloydb/help b/gcloud/alpha/alloydb/help new file mode 100644 index 000000000..ef0b4845e --- /dev/null +++ b/gcloud/alpha/alloydb/help @@ -0,0 +1,43 @@ +NAME + gcloud alpha alloydb - create and manage AlloyDB databases + +SYNOPSIS + gcloud alpha alloydb GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The gcloud alloydb command group lets you create and manage Google + Cloud AlloyDB databases. + + AlloyDB is a fully-managed database service that makes it easy to set up, + maintain, manage, and administer your Alloydb databases in the cloud. + + More information on AlloyDB can be found here at go/alloydb + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + backups + (ALPHA) Provide commands for managing AlloyDB backups. + + clusters + (ALPHA) Provide commands for managing AlloyDB clusters. + + instances + (ALPHA) Provide commands for managing AlloyDB instances. + + operations + (ALPHA) Provide commands for managing AlloyDB operations. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb + diff --git a/gcloud/alpha/alloydb/instances/create b/gcloud/alpha/alloydb/instances/create new file mode 100644 index 000000000..75bbf48c1 --- /dev/null +++ b/gcloud/alpha/alloydb/instances/create @@ -0,0 +1,102 @@ +NAME + gcloud alpha alloydb instances create - creates a new AlloyDB instance + within a given cluster + +SYNOPSIS + gcloud alpha alloydb instances create INSTANCE --cluster=CLUSTER + --cpu-count=CPU_COUNT --instance-type=INSTANCE_TYPE --region=REGION + [--async] [--availability-type=AVAILABILITY_TYPE] + [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--read-pool-node-count=READ_POOL_NODE_COUNT] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates a new AlloyDB instance within a given cluster. + +EXAMPLES + To create a new primary instance, run: + + $ gcloud alpha alloydb instances create my-instance \ + --cluster=my-cluster --region=us-central1 \ + --instance-type=PRIMARY --cpu-count=4 + + To create a new read pool instance, run: + + $ gcloud alpha alloydb instances create my-instance \ + --cluster=my-cluster --region=us-central1 \ + --instance-type=READ_POOL --read-pool-node-count=1 --cpu-count=4 + +POSITIONAL ARGUMENTS + INSTANCE + AlloyDB instance ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --cpu-count=CPU_COUNT + Whole number value indicating how many vCPUs the machine should + contain. Each vCPU count corresponds to a N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). + CPU_COUNT must be one of: 4, 8, 16, 32, 64. + + --instance-type=INSTANCE_TYPE + Specifies instance type. INSTANCE_TYPE must be one of: + + PRIMARY + PRIMARY instances support read and write operations. + READ_POOL + READ_POOL instances support read operations only. Each read pool + instance consists of one or more homogeneous nodes. * Read pool of + size 1 can only have zonal availability. * Read pools with node + count of 2 or more can have regional availability (nodes are + present in 2 or more zones in a region). + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --availability-type=AVAILABILITY_TYPE + Specifies level of availability. AVAILABILITY_TYPE must be (currently + only one value is supported): + + REGIONAL + Provides high availability and is recommended for production + instances; instance automatically fails over to another zone within + your selected region. + + --database-flags=FLAG=VALUE,[FLAG=VALUE,...] + Comma-separated list of database flags to set on the instance. Use an + equals sign to separate flag name and value. Flags without values, like + skip_grant_tables, can be written out without a value after, e.g., + skip_grant_tables=. Use on/off for booleans. View the Instance Resource + API for allowed flags. (e.g., --database-flags + max_allowed_packet=55555,skip_grant_tables=,log_output=1) + + --read-pool-node-count=READ_POOL_NODE_COUNT + Read capacity, i.e. number of nodes in a read pool instance. + + --zone=ZONE + Primary Compute Engine zone (e.g. us-central1, us-central1, etc. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb instances create + diff --git a/gcloud/alpha/alloydb/instances/delete b/gcloud/alpha/alloydb/instances/delete new file mode 100644 index 000000000..88004061a --- /dev/null +++ b/gcloud/alpha/alloydb/instances/delete @@ -0,0 +1,50 @@ +NAME + gcloud alpha alloydb instances delete - deletes an AlloyDB instance within + a given cluster + +SYNOPSIS + gcloud alpha alloydb instances delete INSTANCE --cluster=CLUSTER + --region=REGION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes an AlloyDB instance within a given cluster. + +EXAMPLES + To delete an instance, run: + + $ gcloud alpha alloydb instances delete my-instance \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + INSTANCE + AlloyDB instance ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb instances delete + diff --git a/gcloud/alpha/alloydb/instances/describe b/gcloud/alpha/alloydb/instances/describe new file mode 100644 index 000000000..873fe2935 --- /dev/null +++ b/gcloud/alpha/alloydb/instances/describe @@ -0,0 +1,45 @@ +NAME + gcloud alpha alloydb instances describe - describes an AlloyDB instance + within a given cluster + +SYNOPSIS + gcloud alpha alloydb instances describe INSTANCE --cluster=CLUSTER + --region=REGION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describes an AlloyDB instance within a given cluster. + +EXAMPLES + To describe an instance, run: + + $ gcloud alpha alloydb instances describe my-instance \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + INSTANCE + AlloyDB instance ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb instances describe + diff --git a/gcloud/alpha/alloydb/instances/failover b/gcloud/alpha/alloydb/instances/failover new file mode 100644 index 000000000..fa21521f2 --- /dev/null +++ b/gcloud/alpha/alloydb/instances/failover @@ -0,0 +1,50 @@ +NAME + gcloud alpha alloydb instances failover - failover an AlloyDB instance + within a given cluster + +SYNOPSIS + gcloud alpha alloydb instances failover INSTANCE --cluster=CLUSTER + --region=REGION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Failover an AlloyDB instance within a given cluster. + +EXAMPLES + To failover an instance, run: + + $ gcloud alpha alloydb instances failover my-instance \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + INSTANCE + AlloyDB instance ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb instances failover + diff --git a/gcloud/alpha/alloydb/instances/help b/gcloud/alpha/alloydb/instances/help new file mode 100644 index 000000000..def1ada99 --- /dev/null +++ b/gcloud/alpha/alloydb/instances/help @@ -0,0 +1,48 @@ +NAME + gcloud alpha alloydb instances - provide commands for managing AlloyDB + instances + +SYNOPSIS + gcloud alpha alloydb instances COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Provide commands for managing AlloyDB clusters including creating, + configuring, restarting, and deleting instances. + +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) Creates a new AlloyDB instance within a given cluster. + + delete + (ALPHA) Deletes an AlloyDB instance within a given cluster. + + describe + (ALPHA) Describes an AlloyDB instance within a given cluster. + + failover + (ALPHA) Failover an AlloyDB instance within a given cluster. + + list + (ALPHA) Lists AlloyDB instances in a given cluster. + + restart + (ALPHA) Restarts an AlloyDB instance within a given cluster. + + update + (ALPHA) Updates an AlloyDB instance within a given cluster. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb instances + diff --git a/gcloud/alpha/alloydb/instances/list b/gcloud/alpha/alloydb/instances/list new file mode 100644 index 000000000..4c97621be --- /dev/null +++ b/gcloud/alpha/alloydb/instances/list @@ -0,0 +1,84 @@ +NAME + gcloud alpha alloydb instances list - lists AlloyDB instances in a given + cluster + +SYNOPSIS + gcloud alpha alloydb instances list [--cluster=CLUSTER --region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists AlloyDB instances in a given cluster. + +EXAMPLES + To list instances, run: + + $ gcloud alpha alloydb instances list --cluster=my-cluster \ + --region=us-central1 + +FLAGS + Cluster + + --cluster=CLUSTER + AlloyDB cluster ID + + This flag must be specified if any of the other arguments in this + group are specified. + + --region=REGION + Regional location (e.g. asia-east1, us-east1) of CLUSTER. See the + full list of regions at + https://cloud.google.com/sql/docs/instance-locations. Default: list + clusters in all regions. + + This flag must be specified if any of the other arguments in this + group are specified. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb instances list + diff --git a/gcloud/alpha/alloydb/instances/restart b/gcloud/alpha/alloydb/instances/restart new file mode 100644 index 000000000..b2a3c8ab6 --- /dev/null +++ b/gcloud/alpha/alloydb/instances/restart @@ -0,0 +1,50 @@ +NAME + gcloud alpha alloydb instances restart - restarts an AlloyDB instance + within a given cluster + +SYNOPSIS + gcloud alpha alloydb instances restart INSTANCE --cluster=CLUSTER + --region=REGION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Restarts an AlloyDB instance within a given cluster. + +EXAMPLES + To describe an instance, run: + + $ gcloud alpha alloydb instances restart my-instance \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + INSTANCE + AlloyDB instance ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb instances restart + diff --git a/gcloud/alpha/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update new file mode 100644 index 000000000..f9d48c5a7 --- /dev/null +++ b/gcloud/alpha/alloydb/instances/update @@ -0,0 +1,83 @@ +NAME + gcloud alpha alloydb instances update - updates an AlloyDB instance within + a given cluster + +SYNOPSIS + gcloud alpha alloydb instances update INSTANCE --cluster=CLUSTER + --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE] + [--cpu-count=CPU_COUNT] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--read-pool-node-count=READ_POOL_NODE_COUNT] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Updates an AlloyDB instance within a given cluster. + +EXAMPLES + To update the number of nodes in the read pool, run: + + $ gcloud alpha alloydb instances update my-read-instance \ + --cluster=my-cluster --region=us-central1 \ + --read-pool-node-count=3 + +POSITIONAL ARGUMENTS + INSTANCE + AlloyDB instance ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --availability-type=AVAILABILITY_TYPE + Specifies level of availability. AVAILABILITY_TYPE must be (currently + only one value is supported): + + REGIONAL + Provides high availability and is recommended for production + instances; instance automatically fails over to another zone within + your selected region. + + --cpu-count=CPU_COUNT + Whole number value indicating how many vCPUs the machine should + contain. Each vCPU count corresponds to a N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). + CPU_COUNT must be one of: 4, 8, 16, 32, 64. + + --database-flags=FLAG=VALUE,[FLAG=VALUE,...] + Comma-separated list of database flags to set on the instance. Use an + equals sign to separate flag name and value. Flags without values, like + skip_grant_tables, can be written out without a value after, e.g., + skip_grant_tables=. Use on/off for booleans. View the Instance Resource + API for allowed flags. (e.g., --database-flags + max_allowed_packet=55555,skip_grant_tables=,log_output=1) + + --read-pool-node-count=READ_POOL_NODE_COUNT + Read capacity, i.e. number of nodes in a read pool instance. + + --zone=ZONE + Primary Compute Engine zone (e.g. us-central1, us-central1, etc. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb instances update + diff --git a/gcloud/alpha/alloydb/operations/cancel b/gcloud/alpha/alloydb/operations/cancel new file mode 100644 index 000000000..f1e6a34d2 --- /dev/null +++ b/gcloud/alpha/alloydb/operations/cancel @@ -0,0 +1,41 @@ +NAME + gcloud alpha alloydb operations cancel - cancels an AlloyDB operation + +SYNOPSIS + gcloud alpha alloydb operations cancel OPERATION --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancels an AlloyDB operation. + +EXAMPLES + To cancel an operation, run: + + $ gcloud alpha alloydb operations cancel operation-123456789 \ + --region=us-central1 + +POSITIONAL ARGUMENTS + OPERATION + AlloyDB operation ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb operations cancel + diff --git a/gcloud/alpha/alloydb/operations/delete b/gcloud/alpha/alloydb/operations/delete new file mode 100644 index 000000000..0ab6f4318 --- /dev/null +++ b/gcloud/alpha/alloydb/operations/delete @@ -0,0 +1,41 @@ +NAME + gcloud alpha alloydb operations delete - deletes an AlloyDB operation + +SYNOPSIS + gcloud alpha alloydb operations delete OPERATION --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes an AlloyDB operation. + +EXAMPLES + To delete an operation, run: + + $ gcloud alpha alloydb operations delete operation-123456789 \ + --region=us-central1 + +POSITIONAL ARGUMENTS + OPERATION + AlloyDB operation ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb operations delete + diff --git a/gcloud/alpha/alloydb/operations/describe b/gcloud/alpha/alloydb/operations/describe new file mode 100644 index 000000000..498c31162 --- /dev/null +++ b/gcloud/alpha/alloydb/operations/describe @@ -0,0 +1,41 @@ +NAME + gcloud alpha alloydb operations describe - describe an AlloyDB operation + +SYNOPSIS + gcloud alpha alloydb operations describe OPERATION --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe an AlloyDB operation. + +EXAMPLES + To describe an operation, run: + + $ gcloud alpha alloydb operations describe operation-123456789 \ + --region=us-central1 + +POSITIONAL ARGUMENTS + OPERATION + AlloyDB operation ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb operations describe + diff --git a/gcloud/alpha/alloydb/operations/help b/gcloud/alpha/alloydb/operations/help new file mode 100644 index 000000000..871bb4938 --- /dev/null +++ b/gcloud/alpha/alloydb/operations/help @@ -0,0 +1,39 @@ +NAME + gcloud alpha alloydb operations - provide commands for managing AlloyDB + operations + +SYNOPSIS + gcloud alpha alloydb operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Provide commands for managing AlloyDB operations including + cancelling, deleting, describing, and listing. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancels an AlloyDB operation. + + delete + (ALPHA) Deletes an AlloyDB operation. + + describe + (ALPHA) Describe an AlloyDB operation. + + list + (ALPHA) Lists AlloyDB operations. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb operations + diff --git a/gcloud/alpha/alloydb/operations/list b/gcloud/alpha/alloydb/operations/list new file mode 100644 index 000000000..63616cd24 --- /dev/null +++ b/gcloud/alpha/alloydb/operations/list @@ -0,0 +1,70 @@ +NAME + gcloud alpha alloydb operations list - lists AlloyDB operations + +SYNOPSIS + gcloud alpha alloydb operations list [--region=REGION; default="-"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists AlloyDB operations. + +EXAMPLES + To list operations, run: + + $ gcloud alpha alloydb operations list --region=us-central1 + +FLAGS + --region=REGION; default="-" + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + Default: list operations in all regions. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta alloydb operations list + diff --git a/gcloud/alpha/bigtable/instances/tables/restore b/gcloud/alpha/bigtable/instances/tables/restore index 024918627..901508a6a 100644 --- a/gcloud/alpha/bigtable/instances/tables/restore +++ b/gcloud/alpha/bigtable/instances/tables/restore @@ -31,8 +31,8 @@ EXAMPLES table2 REQUIRED FLAGS - Table resource - The destination to copy to. The arguments in this group - can be used to specify the attributes of this resource. (NOTE) Some + Table resource - The destination to restore to. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --destination on the command line with a fully @@ -58,10 +58,10 @@ REQUIRED FLAGS ▸ provide the argument --destination-instance on the command line; ▸ provide the argument --source-instance on the command line. - Backup resource - The source to copy from. 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: + Backup resource - The source to restore from. 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 --source on the command line with a fully specified name; ◆ provide the argument --project on the command line; @@ -71,7 +71,7 @@ REQUIRED FLAGS --source=SOURCE ID of the backup or fully qualified identifier for the backup. To set - the backup attribute: + the source attribute: ▸ provide the argument --source on the command line. This flag must be specified if any of the other arguments in this diff --git a/gcloud/alpha/builds/triggers/create/github b/gcloud/alpha/builds/triggers/create/github index 4ec312e10..9dc529a51 100644 --- a/gcloud/alpha/builds/triggers/create/github +++ b/gcloud/alpha/builds/triggers/create/github @@ -12,7 +12,8 @@ SYNOPSIS | --dockerfile=DOCKERFILE --dockerfile-dir=DOCKERFILE_DIR; default="/" --dockerfile-image=DOCKERFILE_IMAGE) : --description=DESCRIPTION --ignored-files=[GLOB,...] - --included-files=[GLOB,...] --name=NAME --require-approval + --include-logs-with-status --included-files=[GLOB,...] --name=NAME + --require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -67,6 +68,10 @@ REQUIRED FLAGS Glob filter. Changes only affecting ignored files won't trigger builds. + --include-logs-with-status + Build logs will be sent back to GitHub as part of the checkrun + result. + --included-files=[GLOB,...] Glob filter. Changes affecting at least one included file will trigger builds. diff --git a/gcloud/alpha/compute/backend-services/add-service-bindings b/gcloud/alpha/compute/backend-services/add-service-bindings index 5b886f762..733dc5384 100644 --- a/gcloud/alpha/compute/backend-services/add-service-bindings +++ b/gcloud/alpha/compute/backend-services/add-service-bindings @@ -46,7 +46,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute backend-services add-service-bindings $ gcloud beta compute backend-services add-service-bindings diff --git a/gcloud/alpha/compute/backend-services/remove-service-bindings b/gcloud/alpha/compute/backend-services/remove-service-bindings index 61e316218..470e6ff30 100644 --- a/gcloud/alpha/compute/backend-services/remove-service-bindings +++ b/gcloud/alpha/compute/backend-services/remove-service-bindings @@ -46,7 +46,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute backend-services remove-service-bindings $ gcloud beta compute backend-services remove-service-bindings diff --git a/gcloud/alpha/compute/firewall-rules/migrate b/gcloud/alpha/compute/firewall-rules/migrate index 0538d733c..27c9acf64 100644 --- a/gcloud/alpha/compute/firewall-rules/migrate +++ b/gcloud/alpha/compute/firewall-rules/migrate @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud alpha compute firewall-rules migrate --source-network=SOURCE_NETWORK - --target-firewall-policy=TARGET_FIREWALL_POLICY [GCLOUD_WIDE_FLAG ...] + (--export-tag-mapping + | --target-firewall-policy=TARGET_FIREWALL_POLICY) + [--tag-mapping-file=TAG_MAPPING_FILE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute firewall-rules migrate is used to create a new @@ -23,9 +25,20 @@ REQUIRED FLAGS --source-network=SOURCE_NETWORK The VPC Network for which the migration should be performed. - --target-firewall-policy=TARGET_FIREWALL_POLICY - Name of the new Network Firewall Policy used to store the migration - result. + Exactly one of these must be specified: + + --export-tag-mapping + If set, migration tool will inspect all VPC Firewalls attached to + SOURCE_NETWORK, collect all source and target tags, and store them in + TAG_MAPPING_FILE. + + --target-firewall-policy=TARGET_FIREWALL_POLICY + Name of the new Network Firewall Policy used to store the migration + result. + +OPTIONAL FLAGS + --tag-mapping-file=TAG_MAPPING_FILE + Path to a JSON file with legacy to secure tag mapping. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/images/import b/gcloud/alpha/compute/images/import index a600e35d7..e738d854f 100644 --- a/gcloud/alpha/compute/images/import +++ b/gcloud/alpha/compute/images/import @@ -261,8 +261,8 @@ OPTIONAL FLAGS windows-10-x86-byol, windows-2008r2, windows-2008r2-byol, windows-2012, windows-2012-byol, windows-2012r2, windows-2012r2-byol, windows-2016, windows-2016-byol, windows-2019, windows-2019-byol, - windows-7-x64-byol, windows-7-x86-byol, windows-8-x64-byol, - windows-8-x86-byol. + windows-2022, windows-2022-byol, windows-7-x64-byol, + windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index d4d35941b..925c1af31 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -29,6 +29,7 @@ SYNOPSIS [--min-count=MIN_COUNT] [--min-cpu-platform=PLATFORM] [--min-node-cpu=MIN_NODE_CPU] [--network=NETWORK] [--network-interface=[PROPERTY=VALUE,...]] + [--network-performance-configs=[PROPERTY=VALUE,...]] [--network-tier=NETWORK_TIER] [--numa-node-count=NUMA_NODE_COUNT] [--post-key-revocation-action-type=POLICY] [--preemptible] [--provisioning-model=PROVISIONING_MODEL] @@ -566,6 +567,17 @@ OPTIONAL FLAGS Specifies the Network Interface Controller (NIC) type for the interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + --network-performance-configs=[PROPERTY=VALUE,...] + Configures network performance settings for the instance. If this flag + is not specified, the instance will be created with its default network + performance configuration. + + total-egress-bandwidth-tier + Total egress bandwidth is the available outbound bandwidth from a + VM, regardless of whether the traffic is going to internal IP or + external IP destinations. The following tier values are allowed: + [DEFAULT,TIER_1] + --network-tier=NETWORK_TIER Specifies the network tier that will be used to configure the instance. NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. The diff --git a/gcloud/alpha/compute/instances/import b/gcloud/alpha/compute/instances/import index e21a98fdf..6674fd440 100644 --- a/gcloud/alpha/compute/instances/import +++ b/gcloud/alpha/compute/instances/import @@ -172,8 +172,9 @@ OPTIONAL FLAGS ubuntu-1604, ubuntu-1804, ubuntu-2004, windows-10-x64-byol, windows-10-x86-byol, windows-2008r2, windows-2008r2-byol, windows-2012, windows-2012-byol, windows-2012r2, windows-2012r2-byol, windows-2016, - windows-2016-byol, windows-2019, windows-2019-byol, windows-7-x64-byol, - windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol. + windows-2016-byol, windows-2019, windows-2019-byol, windows-2022, + windows-2022-byol, windows-7-x64-byol, windows-7-x86-byol, + windows-8-x64-byol, windows-8-x86-byol. --private-network-ip=PRIVATE_NETWORK_IP Specifies the RFC1918 IP to assign to the instance. The IP should be in diff --git a/gcloud/alpha/compute/machine-images/import b/gcloud/alpha/compute/machine-images/import index d7e42ff2c..54ba8abc5 100644 --- a/gcloud/alpha/compute/machine-images/import +++ b/gcloud/alpha/compute/machine-images/import @@ -165,8 +165,9 @@ OPTIONAL FLAGS ubuntu-1604, ubuntu-1804, ubuntu-2004, windows-10-x64-byol, windows-10-x86-byol, windows-2008r2, windows-2008r2-byol, windows-2012, windows-2012-byol, windows-2012r2, windows-2012r2-byol, windows-2016, - windows-2016-byol, windows-2019, windows-2019-byol, windows-7-x64-byol, - windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol. + windows-2016-byol, windows-2019, windows-2019-byol, windows-2022, + windows-2022-byol, windows-7-x64-byol, windows-7-x86-byol, + windows-8-x64-byol, windows-8-x86-byol. --restart-on-failure The VMs created from the imported machine image are restarted if they diff --git a/gcloud/alpha/compute/networks/peerings/create b/gcloud/alpha/compute/networks/peerings/create index f10e1611b..b0e260a14 100644 --- a/gcloud/alpha/compute/networks/peerings/create +++ b/gcloud/alpha/compute/networks/peerings/create @@ -85,7 +85,7 @@ OPTIONAL FLAGS IPV4_IPV6 IPv4 traffic and routes will be exchanged across this peering. IPv6 traffic and routes will be exchanged if the matching peering - also has stack_type IPV4_IPV6. + configuration also has stack_type set to IPV4_IPV6. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/networks/peerings/update b/gcloud/alpha/compute/networks/peerings/update index 2f4dcadda..58361efc9 100644 --- a/gcloud/alpha/compute/networks/peerings/update +++ b/gcloud/alpha/compute/networks/peerings/update @@ -61,7 +61,7 @@ OPTIONAL FLAGS IPV4_IPV6 IPv4 traffic and routes will be exchanged across this peering. IPv6 traffic and routes will be exchanged if the matching peering - also has stack_type IPV4_IPV6. + configuration also has stack_type set to IPV4_IPV6. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create index 641c9175c..e008f1fe0 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/create +++ b/gcloud/alpha/compute/tpus/queued-resources/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha compute tpus queued-resources create (QUEUED_RESOURCE : --zone=ZONE) --accelerator-type=ACCELERATOR_TYPE - --node-id=NODE_ID --runtime-version=RUNTIME_VERSION [--async] + --node-id=[NODE_ID,...] --runtime-version=RUNTIME_VERSION [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -20,6 +20,13 @@ EXAMPLES --runtime-version=v2-alpha --node-id=my-node-001 \ --zone=us-central1-b --project=my-project + To create a Queued Resource with multiple nodes, run: + + $ gcloud alpha compute tpus queued-resources create \ + my-queued-resource --accelerator-type=v2-8 \ + --runtime-version=v2-alpha --node-id=my-node-001,my-node-002 \ + --zone=us-central1-b --project=my-project + POSITIONAL ARGUMENTS Queued resource resource - The Queued Resource you want to create. The arguments in this group can be used to specify the attributes of this @@ -55,10 +62,13 @@ REQUIRED FLAGS --accelerator-type=ACCELERATOR_TYPE Accelerator type for the TPU. - --node-id=NODE_ID + --node-id=[NODE_ID,...] The unqualified Node identifier, used to identify the TPU in the Nodes collection once provisioned. + To request a resource with multiple nodes, enter multiple, unique, + unqualified Node identifiers as a comma delimited list. + --runtime-version=RUNTIME_VERSION Runtime version for the TPU, such as 2.3. diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index 07b629efa..831f8fe94 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -516,7 +516,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -539,8 +539,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index b06c735ab..7aefdb22b 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -521,7 +521,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -544,8 +544,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 62d1f41d3..f3cf6e2bb 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -534,7 +534,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -557,8 +557,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 05381eee5..4c981840f 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -495,7 +495,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -518,8 +518,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/alpha/container/fleet/identity-service/apply b/gcloud/alpha/container/fleet/identity-service/apply index 72a5cac7a..ec241f191 100644 --- a/gcloud/alpha/container/fleet/identity-service/apply +++ b/gcloud/alpha/container/fleet/identity-service/apply @@ -41,7 +41,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet identity-service apply $ gcloud beta container fleet identity-service apply diff --git a/gcloud/alpha/container/fleet/identity-service/delete b/gcloud/alpha/container/fleet/identity-service/delete index 4382822eb..1e6617bcb 100644 --- a/gcloud/alpha/container/fleet/identity-service/delete +++ b/gcloud/alpha/container/fleet/identity-service/delete @@ -31,7 +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. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet identity-service delete $ gcloud beta container fleet identity-service delete diff --git a/gcloud/alpha/container/fleet/identity-service/describe b/gcloud/alpha/container/fleet/identity-service/describe index 3df5396cb..d75037443 100644 --- a/gcloud/alpha/container/fleet/identity-service/describe +++ b/gcloud/alpha/container/fleet/identity-service/describe @@ -60,7 +60,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet identity-service describe $ gcloud beta container fleet identity-service describe diff --git a/gcloud/alpha/container/fleet/identity-service/disable b/gcloud/alpha/container/fleet/identity-service/disable index cc23e6c00..d39659700 100644 --- a/gcloud/alpha/container/fleet/identity-service/disable +++ b/gcloud/alpha/container/fleet/identity-service/disable @@ -31,7 +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. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet identity-service disable $ gcloud beta container fleet identity-service disable diff --git a/gcloud/alpha/container/fleet/identity-service/enable b/gcloud/alpha/container/fleet/identity-service/enable index 09130999c..beb13681c 100644 --- a/gcloud/alpha/container/fleet/identity-service/enable +++ b/gcloud/alpha/container/fleet/identity-service/enable @@ -25,7 +25,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet identity-service enable $ gcloud beta container fleet identity-service enable diff --git a/gcloud/alpha/container/fleet/identity-service/help b/gcloud/alpha/container/fleet/identity-service/help index 2bef7cf1c..8b88293aa 100644 --- a/gcloud/alpha/container/fleet/identity-service/help +++ b/gcloud/alpha/container/fleet/identity-service/help @@ -38,7 +38,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container fleet identity-service $ gcloud beta container fleet identity-service diff --git a/gcloud/alpha/container/hub/identity-service/apply b/gcloud/alpha/container/hub/identity-service/apply index b0d00c762..0b98d617d 100644 --- a/gcloud/alpha/container/hub/identity-service/apply +++ b/gcloud/alpha/container/hub/identity-service/apply @@ -41,7 +41,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub identity-service apply $ gcloud beta container hub identity-service apply diff --git a/gcloud/alpha/container/hub/identity-service/delete b/gcloud/alpha/container/hub/identity-service/delete index 92647aecc..df592399d 100644 --- a/gcloud/alpha/container/hub/identity-service/delete +++ b/gcloud/alpha/container/hub/identity-service/delete @@ -31,7 +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. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub identity-service delete $ gcloud beta container hub identity-service delete diff --git a/gcloud/alpha/container/hub/identity-service/describe b/gcloud/alpha/container/hub/identity-service/describe index 1f4c28a84..d79927d82 100644 --- a/gcloud/alpha/container/hub/identity-service/describe +++ b/gcloud/alpha/container/hub/identity-service/describe @@ -60,7 +60,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub identity-service describe $ gcloud beta container hub identity-service describe diff --git a/gcloud/alpha/container/hub/identity-service/disable b/gcloud/alpha/container/hub/identity-service/disable index 1a2233c97..15d569f17 100644 --- a/gcloud/alpha/container/hub/identity-service/disable +++ b/gcloud/alpha/container/hub/identity-service/disable @@ -31,7 +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. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub identity-service disable $ gcloud beta container hub identity-service disable diff --git a/gcloud/alpha/container/hub/identity-service/enable b/gcloud/alpha/container/hub/identity-service/enable index 53085008a..bc4d4c813 100644 --- a/gcloud/alpha/container/hub/identity-service/enable +++ b/gcloud/alpha/container/hub/identity-service/enable @@ -25,7 +25,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub identity-service enable $ gcloud beta container hub identity-service enable diff --git a/gcloud/alpha/container/hub/identity-service/help b/gcloud/alpha/container/hub/identity-service/help index c1ae711f4..9f3cea279 100644 --- a/gcloud/alpha/container/hub/identity-service/help +++ b/gcloud/alpha/container/hub/identity-service/help @@ -37,7 +37,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud container hub identity-service $ gcloud beta container hub identity-service diff --git a/gcloud/alpha/database-migration/migration-jobs/create b/gcloud/alpha/database-migration/migration-jobs/create index 75adac31e..cfd761a2f 100644 --- a/gcloud/alpha/database-migration/migration-jobs/create +++ b/gcloud/alpha/database-migration/migration-jobs/create @@ -7,7 +7,7 @@ SYNOPSIS (MIGRATION_JOB : --region=REGION) --destination=DESTINATION --source=SOURCE --type=TYPE [--display-name=DISPLAY_NAME] [--dump-path=DUMP_PATH] [--labels=[KEY=VALUE,...]] - [--peer-vpc=PEER_VPC + [--peer-vpc=PEER_VPC | --static-ip | [--vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC : --vm=VM]] [GCLOUD_WIDE_FLAG ...] @@ -106,15 +106,20 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - The connectivity method used by the migration job. If not specified, uses - the default IP allowlist method which will create a public IP when used - with a Cloud SQL destination DB. + The connectivity method used by the migration job. If a connectivity + method isn't specified, then it isn't added to the migration job. At most one of these can be specified: --peer-vpc=PEER_VPC Name of the VPC network to peer with the Cloud SQL private network. + --static-ip + Use the default IP allowlist method. This method creates a public IP + that will be used with the destination Cloud SQL database. The method + works by configuring the source database server to accept connections + from the outgoing IP of the Cloud SQL instance. + Parameters for the reverse-SSH tunnel connectivity method. --vm-ip=VM_IP diff --git a/gcloud/alpha/database-migration/migration-jobs/update b/gcloud/alpha/database-migration/migration-jobs/update index 64f5fc135..8d66d5cbc 100644 --- a/gcloud/alpha/database-migration/migration-jobs/update +++ b/gcloud/alpha/database-migration/migration-jobs/update @@ -8,7 +8,7 @@ SYNOPSIS --source=SOURCE [--display-name=DISPLAY_NAME] [--dump-path=DUMP_PATH] [--type=TYPE] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] - [--peer-vpc=PEER_VPC + [--peer-vpc=PEER_VPC | --static-ip | --vm=VM --vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC] [GCLOUD_WIDE_FLAG ...] @@ -125,15 +125,20 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. - The connectivity method used by the migration job. If not specified, uses - the default IP allowlist method which will create a public IP when used - with a Cloud SQL destination DB. + The connectivity method used by the migration job. If a connectivity + method isn't specified, then it isn't updated for the migration job. At most one of these can be specified: --peer-vpc=PEER_VPC Name of the VPC network to peer with the Cloud SQL private network. + --static-ip + Use the default IP allowlist method. This method creates a public IP + that will be used with the destination Cloud SQL database. The method + works by configuring the source database server to accept connections + from the outgoing IP of the Cloud SQL instance. + Parameters for the reverse-SSH tunnel connectivity method. --vm=VM diff --git a/gcloud/alpha/dns/record-sets/create b/gcloud/alpha/dns/record-sets/create index b3c78e63c..7456bfe31 100644 --- a/gcloud/alpha/dns/record-sets/create +++ b/gcloud/alpha/dns/record-sets/create @@ -20,6 +20,15 @@ EXAMPLES $ gcloud alpha dns record-sets create foo.bar.com. \ --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone + To create a geo routed record-set with dnsName foo.bar.com., record type A, + routing_policy_data "us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5.6,9.8.7.6" + and ttl 60 in my_zone. + + $ gcloud alpha dns record-sets create foo.bar.com. \ + --routing_policy_data="us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5\ + .6,9.8.7.6" --routing_policy_type=GEO --type=A --ttl=60 \ + --zone=my_zone --location=us-east1-a + To create a record-set with dnsName foo.bar.com., record type A, rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone in us-east1-a run this: diff --git a/gcloud/alpha/edge-cloud/container/clusters/node-pools/list b/gcloud/alpha/edge-cloud/container/clusters/node-pools/list index 6a11773fc..a22c8b044 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/node-pools/list +++ b/gcloud/alpha/edge-cloud/container/clusters/node-pools/list @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha edge-cloud container clusters node-pools list - (--cluster=CLUSTER : --location=LOCATION) [--filter=EXPRESSION] + [--cluster=CLUSTER --location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -17,29 +17,29 @@ EXAMPLES $ gcloud alpha edge-cloud container clusters node-pools list \ --location=us-central1 --cluster= -REQUIRED FLAGS +FLAGS Cluster resource - Parent Edge Container location to list all contained Edge Container nodePools. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: + ◆ provide the argument --cluster on the command line with a fully + specified name; ◆ provide the argument --cluster 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. - --cluster=CLUSTER ID of the cluster or fully qualified identifier for the cluster. To set the cluster attribute: + ▸ provide the argument --cluster on the command line; ▸ provide the argument --cluster on the command line. - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION The global location name. To set the location attribute: + ▸ provide the argument --cluster on the command line with a fully + specified name; ▸ provide the argument --cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; diff --git a/gcloud/alpha/edge-cloud/container/clusters/update b/gcloud/alpha/edge-cloud/container/clusters/update index c8855fa6e..37153091e 100644 --- a/gcloud/alpha/edge-cloud/container/clusters/update +++ b/gcloud/alpha/edge-cloud/container/clusters/update @@ -5,9 +5,10 @@ NAME SYNOPSIS gcloud alpha edge-cloud container clusters update (CLUSTER : --location=LOCATION) [--async] - [--maintenance-window-end=MAINTENANCE_WINDOW_END] - [--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE] - [--maintenance-window-start=MAINTENANCE_WINDOW_START] + [--clear-maintenance-window + | --maintenance-window-end=MAINTENANCE_WINDOW_END + --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE + --maintenance-window-start=MAINTENANCE_WINDOW_START] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -53,20 +54,28 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. - --maintenance-window-end=MAINTENANCE_WINDOW_END - End time of the recurring cluster maintenance window in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. - "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + At most one of these can be specified: - --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE - An RFC 5545 (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) - recurrence rule for how the cluster maintenance window recurs. They go - on for the span of time between the start and the end time. + --clear-maintenance-window + If set, removes the maintenance window setting from the cluster. - --maintenance-window-start=MAINTENANCE_WINDOW_START - Start time of the recurring cluster maintenance window in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. - "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + Updates cluster maintenance window setting (more than one flags can be + specified from this group) + + --maintenance-window-end=MAINTENANCE_WINDOW_END + End time of the recurring cluster maintenance window in the RFC + 3339 (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + + --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE + An RFC 5545 (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) + recurrence rule for how the cluster maintenance window recurs. They + go on for the span of time between the start and the end time. + + --maintenance-window-start=MAINTENANCE_WINDOW_START + Start time of the recurring cluster maintenance window in the RFC + 3339 (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/firestore/databases/help b/gcloud/alpha/firestore/databases/help index 5c255d8ae..84f77cb0f 100644 --- a/gcloud/alpha/firestore/databases/help +++ b/gcloud/alpha/firestore/databases/help @@ -22,6 +22,10 @@ COMMANDS describe (ALPHA) Describe a Google Cloud Firestore database. + update + (ALPHA) Update the database configuration of a Cloud Firestore + database. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/firestore/databases/update b/gcloud/alpha/firestore/databases/update new file mode 100644 index 000000000..d285a3739 --- /dev/null +++ b/gcloud/alpha/firestore/databases/update @@ -0,0 +1,44 @@ +NAME + gcloud alpha firestore databases update - update the database configuration + of a Cloud Firestore database + +SYNOPSIS + gcloud alpha firestore databases update [--async] [--type=TYPE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update the database configuration of a Cloud Firestore database. + +EXAMPLES + The following command updates the database type of a Cloud Firestore + database. + + $ gcloud alpha firestore databases update --type=firestore-native + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --type=TYPE + The database type. TYPE must be one of: datastore-mode, + firestore-native. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 firestore/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/firestore + +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/iam/policies/create b/gcloud/alpha/iam/policies/create index 31cb25b57..5902c49a7 100644 --- a/gcloud/alpha/iam/policies/create +++ b/gcloud/alpha/iam/policies/create @@ -21,17 +21,20 @@ EXAMPLES POSITIONAL ARGUMENTS POLICY_ID - Id of the policy. + Policy ID that is unique for the resource to which the policy is + attached. REQUIRED FLAGS --attachment-point=ATTACHMENT_POINT - Resource to which the policy is attached. + Resource to which the policy is attached. For valid formats, see + https://cloud.google.com/iam/help/deny/attachment-point. --kind=KIND - Kind of the policy. + Policy type. Use denypolicies for deny policies. --policy-file=POLICY_FILE - Contents of the policy. + Path to the file that contains the policy, in JSON or YAML format. For + valid syntax, see https://cloud.google.com/iam/help/deny/policy-syntax. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/iam/policies/delete b/gcloud/alpha/iam/policies/delete index 8aff974b6..a38e6db78 100644 --- a/gcloud/alpha/iam/policies/delete +++ b/gcloud/alpha/iam/policies/delete @@ -18,23 +18,23 @@ EXAMPLES --attachment-point=cloudresourcemanager.googleapis.com/\ projects/123 --kind=denypolicies --etag=abc - If etag isn't provided, the command will try to get the etag using the - calling user permissions. - POSITIONAL ARGUMENTS POLICY_ID - Id of the policy. + Policy ID that is unique for the resource to which the policy is + attached. REQUIRED FLAGS --attachment-point=ATTACHMENT_POINT - Resource to which the policy is attached. + Resource to which the policy is attached. For valid formats, see + https://cloud.google.com/iam/help/deny/attachment-point. --kind=KIND - Kind of the policy. + Policy type. Use denypolicies for deny policies. OPTIONAL FLAGS --etag=ETAG - Etag of the existing policy. + Etag that identifies the version of the existing policy. If omitted, + the command gets the etag for the current version of the policy. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/iam/policies/get b/gcloud/alpha/iam/policies/get index c9666fcf2..20d99eec9 100644 --- a/gcloud/alpha/iam/policies/get +++ b/gcloud/alpha/iam/policies/get @@ -19,14 +19,16 @@ EXAMPLES POSITIONAL ARGUMENTS POLICY_ID - Id of the policy. + Policy ID that is unique for the resource to which the policy is + attached. REQUIRED FLAGS --attachment-point=ATTACHMENT_POINT - Resource to which the policy is attached. + Resource to which the policy is attached. For valid formats, see + https://cloud.google.com/iam/help/deny/attachment-point. --kind=KIND - Kind of the policy. + Policy type. Use denypolicies for deny policies. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/iam/policies/list b/gcloud/alpha/iam/policies/list index 409c873db..004c54c8e 100644 --- a/gcloud/alpha/iam/policies/list +++ b/gcloud/alpha/iam/policies/list @@ -21,14 +21,16 @@ EXAMPLES REQUIRED FLAGS --attachment-point=ATTACHMENT_POINT - Resource to which the policy is attached. + Resource to which the policy is attached. For valid formats, see + https://cloud.google.com/iam/help/deny/attachment-point. --kind=KIND - Kind of the policy. + Policy type. Use denypolicies for deny policies. FLAGS --page_token=PAGE_TOKEN - Page token received from a previous call. + Page token received from a previous call. Provide this token to + retrieve the next page. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/iam/policies/update b/gcloud/alpha/iam/policies/update index 4f315a0da..5724bbcf5 100644 --- a/gcloud/alpha/iam/policies/update +++ b/gcloud/alpha/iam/policies/update @@ -20,26 +20,27 @@ EXAMPLES projects/123 --kind=denypolicies --policy-file=policy.json \ --etag=abc - If etag isn't provided, the command will try to get the etag using the - calling user permissions. - POSITIONAL ARGUMENTS POLICY_ID - Id of the policy. + Policy ID that is unique for the resource to which the policy is + attached. REQUIRED FLAGS --attachment-point=ATTACHMENT_POINT - Resource to which the policy is attached. + Resource to which the policy is attached. For valid formats, see + https://cloud.google.com/iam/help/deny/attachment-point. --kind=KIND - Kind of the policy. + Policy type. Use denypolicies for deny policies. --policy-file=POLICY_FILE - Contents of the policy. + Path to the file that contains the policy, in JSON or YAML format. For + valid syntax, see https://cloud.google.com/iam/help/deny/policy-syntax. OPTIONAL FLAGS --etag=ETAG - Etag of the existing policy. + Etag that identifies the version of the existing policy. If omitted, + the command gets the etag for the current version of the policy. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/iap/help b/gcloud/alpha/iap/help index 44bf5668d..428625f76 100644 --- a/gcloud/alpha/iap/help +++ b/gcloud/alpha/iap/help @@ -34,6 +34,9 @@ GROUPS settings (ALPHA) Manage IAP settings. + tcp + (ALPHA) Manage IAP TCP resources. + web (ALPHA) Manage IAP web policies. diff --git a/gcloud/alpha/iap/tcp/dest-groups/add-iam-policy-binding b/gcloud/alpha/iap/tcp/dest-groups/add-iam-policy-binding new file mode 100644 index 000000000..ced4e679e --- /dev/null +++ b/gcloud/alpha/iap/tcp/dest-groups/add-iam-policy-binding @@ -0,0 +1,128 @@ +NAME + gcloud alpha iap tcp dest-groups add-iam-policy-binding - add IAM policy + binding to an IAP TCP Tunnel Destination Group resource + +SYNOPSIS + gcloud alpha iap tcp dest-groups add-iam-policy-binding + --group-name=GROUP_NAME --member=PRINCIPAL --region=REGION --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Adds a policy binding to the IAM policy of an IAP TCP Tunnel + Destination Group resource. One binding consists of a member, a role, and + an optional condition. + +EXAMPLES + To add an IAM policy binding for the role of + 'roles/iap.tunnelResourceAccessor' for the user 'test-user@gmail.com' in + the group 'my-group' located in the region 'us-west1', run: + + $ gcloud alpha iap tcp dest-groups add-iam-policy-binding \ + --member='user:test-user@gmail.com' \ + --role='roles/iap.tunnelResourceAccessor' \ + --group-name='my-group' --region='us-west1' + + To add an IAM policy binding for the role of + 'roles/iap.tunnelResourceAccessor' for all authenticated users in the group + 'my-group' located in the region 'us-west1', run: + + $ gcloud alpha iap tcp dest-groups add-iam-policy-binding \ + --member='allAuthenticatedUsers' \ + --role='roles/iap.tunnelResourceAccessor' \ + --group-name='my-group' --region='us-west1' + + To add an IAM policy binding which expires at the end of the year 2018 for + the role of 'roles/iap.tunnelResourceAccessor' and the user + 'test-user@gmail.com' in the group 'my-group' located in the region + 'us-west1', run: + + $ gcloud alpha iap tcp dest-groups add-iam-policy-binding \ + --member='user:test-user@gmail.com' \ + --role='roles/iap.tunnelResourceAccessor' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, + description=Expires at midnight on 2018-12-31' --group-name='my-group' --region='us-west1' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +REQUIRED FLAGS + --group-name=GROUP_NAME + Name of the Destination Group. + + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --region=REGION + Region of the Destination Group. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/iap/tcp/dest-groups/create b/gcloud/alpha/iap/tcp/dest-groups/create new file mode 100644 index 000000000..53cc7e487 --- /dev/null +++ b/gcloud/alpha/iap/tcp/dest-groups/create @@ -0,0 +1,67 @@ +NAME + gcloud alpha iap tcp dest-groups create - create the IAP TCP Destination + Group resource + +SYNOPSIS + gcloud alpha iap tcp dest-groups create GROUP_NAME --region=REGION + [--fqdn-list=FQDN_LIST] [--ip-range-list=IP_RANGE_LIST] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create the IAP TCP Destination Group resource. + +EXAMPLES + To create a DestGroup with name GROUP_NAME, in region REGION in the current + project run: + + $ gcloud alpha iap tcp dest-groups create DEST_GROUP_NAME \ + --region=REGION + + To create a DestGroup with name GROUP_NAME, in region REGION with ip ranges + CIDR1, CIDR2 in the current project run: + + $ gcloud alpha iap tcp dest-groups create DEST_GROUP_NAME \ + --region=REGION --ip-range-list=CIDR1,CIDR2 + + To create a DestGroup with name GROUP_NAME, in region REGION with fqdns + FQDN1, FQDN2 in the current project run: + + $ gcloud alpha iap tcp dest-groups create DEST_GROUP_NAME \ + --region=REGION --fqdn-list=FQDN1,FQDN2 + + To create a DestGroup with name GROUP_NAME, in region REGION with fqdns + FQDN1, FQDN2 and ip ranges CIDR1,CIDR2 in the project PROJECT_ID run: + + $ gcloud alpha iap tcp dest-groups create DEST_GROUP_NAME \ + --region=REGION --fqdn-list=FQDN1,FQDN2 \ + --ip-range-list=CIDR1,CIDR2 --project=PROJECT_ID + +POSITIONAL ARGUMENTS + GROUP_NAME + Name of the Destination Group. + +REQUIRED FLAGS + --region=REGION + Region of the Destination Group. + +OPTIONAL FLAGS + --fqdn-list=FQDN_LIST + List of FQDNs in the Destination Group. + + --ip-range-list=IP_RANGE_LIST + List of ip-ranges in the Destination Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/iap/tcp/dest-groups/delete b/gcloud/alpha/iap/tcp/dest-groups/delete new file mode 100644 index 000000000..3147bfd50 --- /dev/null +++ b/gcloud/alpha/iap/tcp/dest-groups/delete @@ -0,0 +1,46 @@ +NAME + gcloud alpha iap tcp dest-groups delete - delete the IAP TCP Destination + Group resource + +SYNOPSIS + gcloud alpha iap tcp dest-groups delete GROUP_NAME --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete the IAP TCP Destination Group resource. + +EXAMPLES + To delete a DestGroup with name GROUP_NAME, in region REGION in the current + project run: + + $ gcloud alpha iap tcp dest-groups delete DEST_GROUP_NAME \ + --region=REGION + + To delete a DestGroup with name GROUP_NAME, in region REGION in the project + PROJECT_ID run: + + $ gcloud alpha iap tcp dest-groups delete DEST_GROUP_NAME \ + --region=REGION --project=PROJECT_ID + +POSITIONAL ARGUMENTS + GROUP_NAME + Name of the Destination Group. + +REQUIRED FLAGS + --region=REGION + Region of the Destination Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/iap/tcp/dest-groups/describe b/gcloud/alpha/iap/tcp/dest-groups/describe new file mode 100644 index 000000000..ee9dde340 --- /dev/null +++ b/gcloud/alpha/iap/tcp/dest-groups/describe @@ -0,0 +1,46 @@ +NAME + gcloud alpha iap tcp dest-groups describe - describe the IAP TCP + Destination Group resource + +SYNOPSIS + gcloud alpha iap tcp dest-groups describe GROUP_NAME --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe the IAP TCP Destination Group resource. + +EXAMPLES + To get a DestGroup with name GROUP_NAME, in region REGION in the current + project run: + + $ gcloud alpha iap tcp dest-groups describe DEST_GROUP_NAME \ + --region=REGION + + To get a DestGroup with name GROUP_NAME, in region REGION in the project + PROJECT run: + + $ gcloud alpha iap tcp dest-groups describe DEST_GROUP_NAME \ + --region=REGION --project=PROJECT + +POSITIONAL ARGUMENTS + GROUP_NAME + Name of the Destination Group. + +REQUIRED FLAGS + --region=REGION + Region of the Destination Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/iap/tcp/dest-groups/get-iam-policy b/gcloud/alpha/iap/tcp/dest-groups/get-iam-policy new file mode 100644 index 000000000..938e46f4b --- /dev/null +++ b/gcloud/alpha/iap/tcp/dest-groups/get-iam-policy @@ -0,0 +1,79 @@ +NAME + gcloud alpha iap tcp dest-groups get-iam-policy - get IAM policy for an IAP + TCP Destination Group resource + +SYNOPSIS + gcloud alpha iap tcp dest-groups get-iam-policy --group-name=GROUP_NAME + --region=REGION [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha iap tcp dest-groups get-iam-policy displays the IAM + policy associated with an IAP TCP Destination Group resource. If formatted + as JSON, the output can be edited and used as a policy file for + set-iam-policy. The output includes an "etag" field identifying the version + emitted and allowing detection of concurrent policy updates; see $ gcloud + alpha iap tcp dest-groups set-iam-policy for additional \ details. + +EXAMPLES + To get the IAM policy for the TCP Destination Group resource with name + 'my-group' and located in the region 'us-west1' within the active project, + run: + + $ gcloud alpha iap tcp dest-groups get-iam-policy \ + --group-name='my-group' --region='us-west1' + + To get the IAM policy for the TCP Destination Group resource with name + 'my-group' and located in the region 'us-west1' within project 'project', + run: + + $ gcloud alpha iap tcp dest-groups get-iam-policy \ + --group-name='my-group' --region='us-west1' --project='project' + +REQUIRED FLAGS + --group-name=GROUP_NAME + Name of the Destination Group. + + --region=REGION + Region of the Destination Group. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/iap/tcp/dest-groups/help b/gcloud/alpha/iap/tcp/dest-groups/help new file mode 100644 index 000000000..58dbb1c54 --- /dev/null +++ b/gcloud/alpha/iap/tcp/dest-groups/help @@ -0,0 +1,53 @@ +NAME + gcloud alpha iap tcp dest-groups - manage IAP TCP Destination Group + resources + +SYNOPSIS + gcloud alpha iap tcp dest-groups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage IAP TCP Destination Group resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + (ALPHA) Add IAM policy binding to an IAP TCP Tunnel Destination Group + resource. + + create + (ALPHA) Create the IAP TCP Destination Group resource. + + delete + (ALPHA) Delete the IAP TCP Destination Group resource. + + describe + (ALPHA) Describe the IAP TCP Destination Group resource. + + get-iam-policy + (ALPHA) Get IAM policy for an IAP TCP Destination Group resource. + + list + (ALPHA) Lists the IAP TCP Destination Group resource. + + remove-iam-policy-binding + (ALPHA) Remove IAM policy binding from an IAP TCP Destination Group + resource. + + set-iam-policy + (ALPHA) Set the IAM policy for an IAP TCP Destination Group resource. + + update + (ALPHA) Update the IAP TCP Destination Group resource. + +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/iap/tcp/dest-groups/list b/gcloud/alpha/iap/tcp/dest-groups/list new file mode 100644 index 000000000..d25f42ed1 --- /dev/null +++ b/gcloud/alpha/iap/tcp/dest-groups/list @@ -0,0 +1,90 @@ +NAME + gcloud alpha iap tcp dest-groups list - lists the IAP TCP Destination Group + resource + +SYNOPSIS + gcloud alpha iap tcp dest-groups list [--region=REGION; default="-"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists the IAP TCP Destination Group resource. + +EXAMPLES + To list all Destination Groups in the current project run: + + $ gcloud alpha iap tcp dest-groups list + + To list all Destination Groups in region REGION in the current project run: + + $ gcloud alpha iap tcp dest-groups list --region=REGION + + To limit the results returned by the server to be at most PAGE_SIZE, run: + + $ gcloud alpha iap tcp dest-groups list --page-size=PAGE_SIZE + + To list at most 5 Destination Groups sorted alphabetically by project ID, + run: + + $ gcloud alpha iap tcp dest-groups list --sort-by=projectId --limit=5 + + To list all Destination Groups in the project PROJECT run: + + $ gcloud alpha iap tcp dest-groups list --project=PROJECT + + To list all Destination Groups that have cidr CIDR run: + + $ gcloud alpha iap tcp dest-groups list --filter="cidrs=CIDR" + + To list all Destination Groups that have FQDN FQDN run: + + $ gcloud alpha iap tcp dest-groups list --filter="fqdns=FQDN" + + To list all Destination Groups that have name NAME run: + + $ gcloud alpha iap tcp dest-groups list --filter="name=NAME" + +FLAGS + --region=REGION; default="-" + Region of the Destination Group, will list all regions by default + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/iap/tcp/dest-groups/remove-iam-policy-binding b/gcloud/alpha/iap/tcp/dest-groups/remove-iam-policy-binding new file mode 100644 index 000000000..14e1de853 --- /dev/null +++ b/gcloud/alpha/iap/tcp/dest-groups/remove-iam-policy-binding @@ -0,0 +1,144 @@ +NAME + gcloud alpha iap tcp dest-groups remove-iam-policy-binding - remove IAM + policy binding from an IAP TCP Destination Group resource + +SYNOPSIS + gcloud alpha iap tcp dest-groups remove-iam-policy-binding + --group-name=GROUP_NAME --member=PRINCIPAL --region=REGION --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Removes a policy binding from the IAM policy of an IAP TCP + Destination Group resource. One binding consists of a member, a role and an + optional condition. + +EXAMPLES + To remove an IAM policy binding for the role of + 'roles/iap.tunnelResourceAccessor' for the user 'test-user@gmail.com' in + the group 'my-group' located in the region 'us-west1', run: + + $ gcloud alpha iap tcp dest-groups remove-iam-policy-binding \ + --member='user:test-user@gmail.com' \ + --role='roles/iap.tunnelResourceAccessor' \ + --group-name='my-group' --region='us-west1' + + To remove an IAM policy binding for the role of + 'roles/iap.tunnelResourceAccessor' from all authenticated users in the + group 'my-group' located in the region 'us-west1', run: + + $ gcloud alpha iap tcp dest-groups remove-iam-policy-binding \ + --member='allAuthenticatedUsers' \ + --role='roles/iap.tunnelResourceAccessor' \ + --group-name='my-group' --region='us-west1' + + To remove an IAM policy binding which expires at the end of the year 2018 + for the role of 'roles/iap.tunnelResourceAccessor' for the user + 'test-user@gmail.com' in the group 'my-group' located in the region + 'us-west1', run: + + $ gcloud alpha iap tcp dest-groups remove-iam-policy-binding \ + --member='user:test-user@gmail.com' \ + --role='roles/iap.tunnelResourceAccessor' \ + --condition='expression=request.time < + timestamp("2019-01-01T00:00:00Z"),title=expires_end_of_2018, + description=Expires at midnight on 2018-12-31' \ + --group-name='my-group' --region='us-west1' + + To remove all IAM policy bindings regardless of the condition for the role + of 'roles/iap.tunnelResourceAccessor' and for the user + 'test-user@gmail.com' in the group 'my-group' located in the region + 'us-west1', run: + + $ gcloud alpha iap tcp dest-groups remove-iam-policy-binding \ + --member='user:test-user@gmail.com' \ + --role='roles/iap.tunnelResourceAccessor' \ + --group-name='my-group' --region='us-west1' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +REQUIRED FLAGS + --group-name=GROUP_NAME + Name of the Destination Group. + + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --region=REGION + Region of the Destination Group. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/iap/tcp/dest-groups/set-iam-policy b/gcloud/alpha/iap/tcp/dest-groups/set-iam-policy new file mode 100644 index 000000000..c2d9f6fc9 --- /dev/null +++ b/gcloud/alpha/iap/tcp/dest-groups/set-iam-policy @@ -0,0 +1,57 @@ +NAME + gcloud alpha iap tcp dest-groups set-iam-policy - set the IAM policy for an + IAP TCP Destination Group resource + +SYNOPSIS + gcloud alpha iap tcp dest-groups set-iam-policy POLICY_FILE + --group-name=GROUP_NAME --region=REGION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command replaces the existing IAM policy for an IAP TCP + Destination Group resource, given a file encoded in JSON or YAML that + contains the IAM policy. If the given policy file specifies an "etag" + value, then the replacement will succeed only if the policy already in + place matches that etag. (An etag obtained via $ gcloud alpha iap tcp + dest-groups get-iam-policy will prevent the replacement if the policy for + the resource has been subsequently updated.) A policy file that does not + contain an etag value will replace any existing policy for the resource. + +EXAMPLES + To set the IAM policy for the TCP Destination Group resource within the + active project in the group 'my-group' located in the region 'us-west1', + run: + + $ gcloud alpha iap tcp dest-groups set-iam-policy POLICY_FILE \ + --group-name='my-group' --region='us-west1' + + To set the IAM policy for the TCP Destination Group resource within project + PROJECT_ID in the group 'my-group' located in the region 'us-west1', run: + + $ gcloud alpha iap tcp dest-groups set-iam-policy POLICY_FILE \ + --project=PROJECT_ID --group-name='my-group' --region='us-west1' + +POSITIONAL ARGUMENTS + POLICY_FILE + JSON or YAML file containing the IAM policy. + +REQUIRED FLAGS + --group-name=GROUP_NAME + Name of the Destination Group. + + --region=REGION + Region of the Destination Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/iap/tcp/dest-groups/update b/gcloud/alpha/iap/tcp/dest-groups/update new file mode 100644 index 000000000..16c78ca14 --- /dev/null +++ b/gcloud/alpha/iap/tcp/dest-groups/update @@ -0,0 +1,74 @@ +NAME + gcloud alpha iap tcp dest-groups update - update the IAP TCP Destination + Group resource + +SYNOPSIS + gcloud alpha iap tcp dest-groups update GROUP_NAME --region=REGION + (--fqdn-list=FQDN_LIST --ip-range-list=IP_RANGE_LIST) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update the IAP TCP Destination Group resource. + +EXAMPLES + To update a DestGroup with name GROUP_NAME, in region REGION with ip ranges + CIDR1, CIDR2 in the current project run: + + $ gcloud alpha iap tcp dest-groups update DEST_GROUP_NAME \ + --region=REGION --ip-range-list=CIDR1,CIDR2 + + To update a DestGroup with name GROUP_NAME, in region REGION with fqdns + FQDN1, FQDN2 in the current project run: + + $ gcloud alpha iap tcp dest-groups update DEST_GROUP_NAME \ + --region=REGION --fqdn-list=FQDN1,FQDN2 + + To update a DestGroup with name GROUP_NAME, in region REGION with fqdns + FQDN1, FQDN2 and ip ranges CIDR1, CIDR2 in the project PROJECT_ID run: + + $ gcloud alpha iap tcp dest-groups update DEST_GROUP_NAME \ + --region=REGION --fqdn-list=FQDN1,FQDN2 \ + --ip-range-list=CIDR1,CIDR2 --project=PROJECT_ID + + To clear the fqdn list in a DestGroup with name GROUP_NAME, in region + REGION in the current project run: + + $ gcloud alpha iap tcp dest-groups update DEST_GROUP_NAME \ + --region=REGION --fqdn-list="" + + To clear the ip range list in a DestGroup with name GROUP_NAME, in region + REGION in the current project run: + + $ gcloud alpha iap tcp dest-groups update DEST_GROUP_NAME \ + --region=REGION --ip-range-list="" + +POSITIONAL ARGUMENTS + GROUP_NAME + Name of the Destination Group. + +REQUIRED FLAGS + --region=REGION + Region of the Destination Group. + + At least one of these must be specified: + + --fqdn-list=FQDN_LIST + List of FQDNs in the Destination Group. + + --ip-range-list=IP_RANGE_LIST + List of ip-ranges in the Destination Group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/iap/tcp/help b/gcloud/alpha/iap/tcp/help new file mode 100644 index 000000000..86269b9f4 --- /dev/null +++ b/gcloud/alpha/iap/tcp/help @@ -0,0 +1,26 @@ +NAME + gcloud alpha iap tcp - manage IAP TCP resources + +SYNOPSIS + gcloud alpha iap tcp GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage IAP TCP resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + dest-groups + (ALPHA) Manage IAP TCP Destination Group resources. + +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/immersive-stream/help b/gcloud/alpha/immersive-stream/help new file mode 100644 index 000000000..4bbf08674 --- /dev/null +++ b/gcloud/alpha/immersive-stream/help @@ -0,0 +1,26 @@ +NAME + gcloud alpha immersive-stream - manage Immersive Stream resources + +SYNOPSIS + gcloud alpha immersive-stream GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Immersive Stream resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + xr + (ALPHA) Manage Immersive Stream for XR resources. + +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/immersive-stream/xr/contents/build b/gcloud/alpha/immersive-stream/xr/contents/build new file mode 100644 index 000000000..2e313e2f1 --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/contents/build @@ -0,0 +1,74 @@ +NAME + gcloud alpha immersive-stream xr contents build - build an Immersive Stream + for XR content resource + +SYNOPSIS + gcloud alpha immersive-stream xr contents build + (CONTENT : --location=LOCATION) --version=VERSION [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Build an Immersive Stream for XR content resource and tag it with a + user specified version tag. + +EXAMPLES + To build a content resource 'my-content' tagged with version tag + 'my-version', run: + + $ gcloud alpha immersive-stream xr contents build my-content \ + --version=my-version + +POSITIONAL ARGUMENTS + Content resource - Immersive Stream for XR content resource to be built. + 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 content 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. + + CONTENT + ID of the content or fully qualified identifier for the content. To + set the content attribute: + ▸ provide the argument content on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Global location name. To set the location attribute: + ▸ provide the argument content on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +REQUIRED FLAGS + --version=VERSION + User-specified version tag of content build. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the stream/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com + +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/immersive-stream/xr/contents/create b/gcloud/alpha/immersive-stream/xr/contents/create new file mode 100644 index 000000000..916fdc202 --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/contents/create @@ -0,0 +1,74 @@ +NAME + gcloud alpha immersive-stream xr contents create - create an Immersive + Stream for XR content resource + +SYNOPSIS + gcloud alpha immersive-stream xr contents create + (CONTENT : --location=LOCATION) --bucket=BUCKET [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create an Immersive Stream for XR content resource. + +EXAMPLES + To create a content resource called 'my-content' using Cloud Storage bucket + 'my-bucket', run: + + $ gcloud alpha immersive-stream xr contents create my-content \ + --bucket=my-bucket + +POSITIONAL ARGUMENTS + Content resource - Immersive Stream for XR content resource to be created. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: + ◆ provide the argument content 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. + + CONTENT + ID of the content or fully qualified identifier for the content. To + set the content attribute: + ▸ provide the argument content on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Global location name. To set the location attribute: + ▸ provide the argument content on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +REQUIRED FLAGS + --bucket=BUCKET + The name of the Cloud Storage bucket in the consumer project that + stores the content source. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the stream/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com + +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/immersive-stream/xr/contents/delete b/gcloud/alpha/immersive-stream/xr/contents/delete new file mode 100644 index 000000000..8b038eab3 --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/contents/delete @@ -0,0 +1,66 @@ +NAME + gcloud alpha immersive-stream xr contents delete - delete an Immersive + Stream for XR content resource + +SYNOPSIS + gcloud alpha immersive-stream xr contents delete + (CONTENT : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an Immersive Stream for XR content resource. + +EXAMPLES + To delete a content called 'my-content', run: + + $ gcloud alpha immersive-stream xr contents delete my-content + +POSITIONAL ARGUMENTS + Content resource - Immersive Stream for XR content resource 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 content 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. + + CONTENT + ID of the content or fully qualified identifier for the content. To + set the content attribute: + ▸ provide the argument content on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Global location name. To set the location attribute: + ▸ provide the argument content on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the stream/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com + +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/immersive-stream/xr/contents/describe b/gcloud/alpha/immersive-stream/xr/contents/describe new file mode 100644 index 000000000..f63e51fce --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/contents/describe @@ -0,0 +1,61 @@ +NAME + gcloud alpha immersive-stream xr contents describe - describe a specific + Immersive Stream for XR content resource + +SYNOPSIS + gcloud alpha immersive-stream xr contents describe + (CONTENT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a specific Immersive Stream for XR content resource. + +EXAMPLES + To describe the content, run: + + $ gcloud alpha immersive-stream xr contents describe my-content + +POSITIONAL ARGUMENTS + Content resource - The name of the content resource 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 content 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. + + CONTENT + ID of the content or fully qualified identifier for the content. To + set the content attribute: + ▸ provide the argument content on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Global location name. To set the location attribute: + ▸ provide the argument content on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the stream/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com + +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/immersive-stream/xr/contents/help b/gcloud/alpha/immersive-stream/xr/contents/help new file mode 100644 index 000000000..f0bf50ffa --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/contents/help @@ -0,0 +1,42 @@ +NAME + gcloud alpha immersive-stream xr contents - manage Immersive Stream for XR + contents + +SYNOPSIS + gcloud alpha immersive-stream xr contents COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Immersive Stream for XR contents. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + build + (ALPHA) Build an Immersive Stream for XR content resource. + + create + (ALPHA) Create an Immersive Stream for XR content resource. + + delete + (ALPHA) Delete an Immersive Stream for XR content resource. + + describe + (ALPHA) Describe a specific Immersive Stream for XR content resource. + + list + (ALPHA) List Immersive Stream for XR content resources. + + update + (ALPHA) Update an Immersive Stream for XR content resource. + +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/immersive-stream/xr/contents/list b/gcloud/alpha/immersive-stream/xr/contents/list new file mode 100644 index 000000000..6d78ec02a --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/contents/list @@ -0,0 +1,84 @@ +NAME + gcloud alpha immersive-stream xr contents list - list Immersive Stream for + XR content resources + +SYNOPSIS + gcloud alpha immersive-stream xr contents list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Immersive Stream for XR content resources. + +EXAMPLES + To list Immersive Stream for XR content resources, run: + + $ gcloud alpha immersive-stream xr contents list + +FLAGS + Location resource - Location to list all Immersive Stream for XR content + resources, defaults to global. 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; + ◆ global is the only supported 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; + ▸ global is the only supported 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 stream/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com + +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/immersive-stream/xr/contents/update b/gcloud/alpha/immersive-stream/xr/contents/update new file mode 100644 index 000000000..9060a1357 --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/contents/update @@ -0,0 +1,84 @@ +NAME + gcloud alpha immersive-stream xr contents update - update an Immersive + Stream for XR content resource + +SYNOPSIS + gcloud alpha immersive-stream xr contents update + (CONTENT : --location=LOCATION) (--bucket=BUCKET | --uiconfig) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an Immersive Stream for XR content resource. + +EXAMPLES + To update the Cloud Storage bucket used by the content resource + 'my-content', to 'my-new-bucket' run: + + $ gcloud alpha immersive-stream xr contents update my-content \ + --bucket=my-new-bucket + + To trigger an update to the UI configuration, run: + + $ gcloud alpha immersive-stream xr contents update my-content \ + --uiconfig + +POSITIONAL ARGUMENTS + Content resource - Immersive Stream for XR content resource to be updated. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: + ◆ provide the argument content 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. + + CONTENT + ID of the content or fully qualified identifier for the content. To + set the content attribute: + ▸ provide the argument content on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Global location name. To set the location attribute: + ▸ provide the argument content on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --bucket=BUCKET + The name of the Cloud Storage bucket in the consumer project that + stores the content source. + + --uiconfig + Boolean flag indicating that the update call is for UI configuration. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the stream/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com + +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/immersive-stream/xr/help b/gcloud/alpha/immersive-stream/xr/help new file mode 100644 index 000000000..492e5d1e9 --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha immersive-stream xr - manage Immersive Stream for XR resources + +SYNOPSIS + gcloud alpha immersive-stream xr GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Immersive Stream for XR resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + contents + (ALPHA) Manage Immersive Stream for XR contents. + + instances + (ALPHA) Manage Immersive Stream for XR instances. + + operations + (ALPHA) Manage Immersive Stream for XR operations. + +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/immersive-stream/xr/instances/create b/gcloud/alpha/immersive-stream/xr/instances/create new file mode 100644 index 000000000..a9d532d04 --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/instances/create @@ -0,0 +1,95 @@ +NAME + gcloud alpha immersive-stream xr instances create - create an Immersive + Stream for XR service instance + +SYNOPSIS + gcloud alpha immersive-stream xr instances create INSTANCE + --add-realm=[capacity=CAPACITY],[realm=REALM] --version=VERSION + (--content=CONTENT : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create an Immersive Stream for XR service instance. + +EXAMPLES + To create a service instance called 'my-instance' serving content + 'my-content' with version 'my-version' that has availablilty for 2 + concurent sessions in REALM_NA_WEST and 3 concurrent sessions in + REALM_NA_EAST, run: + + $ gcloud alpha immersive-stream xr instances create my-instance \ + --content=my-content --version=my-version \ + --add-realm=realm=REALM_NA_WEST,capacity=2 \ + --add-realm=realm=REALM_NA_EAST,capacity=3 + +POSITIONAL ARGUMENTS + INSTANCE + Name of the instance to be created + +REQUIRED FLAGS + --add-realm=[capacity=CAPACITY],[realm=REALM] + Flag used to specify realm and capacity required for the service + instance's availability. + + 'realm' is the realm in which the instance is deployed, and must be one of the following: + REALM_UNSPECIFIED + REALM_NA_CENTRAL + REALM_NA_EAST + REALM_NA_WEST + REALM_ASIA_NORTHEAST + REALM_ASIA_SOUTHEAST + REALM_EU_WEST + + 'capacity' is the maxium number of concurrent streaming sessions that the instance can support in the given realm. + + This is a repeatable flag. + + --version=VERSION + Build version tag of the content served by this instance + + Content resource - Immersive Stream for XR content resource served by the + instance. 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 --content 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. + + --content=CONTENT + ID of the content or fully qualified identifier for the content. To + set the name attribute: + ▸ provide the argument --content on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --location=LOCATION + Google Cloud location for the content. To set the location attribute: + ▸ provide the argument --content on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ location is always global. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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/immersive-stream/xr/instances/delete b/gcloud/alpha/immersive-stream/xr/instances/delete new file mode 100644 index 000000000..dcdf18250 --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/instances/delete @@ -0,0 +1,66 @@ +NAME + gcloud alpha immersive-stream xr instances delete - delete an Immersive + Stream for XR service instance + +SYNOPSIS + gcloud alpha immersive-stream xr instances delete + (INSTANCE : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete an Immersive Stream for XR service instance. + +EXAMPLES + To delete a service instance called 'my-instance', run: + + $ gcloud alpha immersive-stream xr instances delete my-instance + +POSITIONAL ARGUMENTS + Instance resource - Immersive Stream for XR service instance 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 instance 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. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. To + set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Global location name. To set the location attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the stream/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com + +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/immersive-stream/xr/instances/describe b/gcloud/alpha/immersive-stream/xr/instances/describe new file mode 100644 index 000000000..091d240c4 --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/instances/describe @@ -0,0 +1,61 @@ +NAME + gcloud alpha immersive-stream xr instances describe - describe a specific + Immersive Stream for XR service instance + +SYNOPSIS + gcloud alpha immersive-stream xr instances describe + (INSTANCE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a specific Immersive Stream for XR service instance. + +EXAMPLES + To describe the service instance, run: + + $ gcloud alpha immersive-stream xr instances describe my-instance + +POSITIONAL ARGUMENTS + Instance resource - The name of the service instance 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 instance 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. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. To + set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Global location name. To set the location attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the stream/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com + +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/immersive-stream/xr/instances/help b/gcloud/alpha/immersive-stream/xr/instances/help new file mode 100644 index 000000000..42ccc57dc --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/instances/help @@ -0,0 +1,39 @@ +NAME + gcloud alpha immersive-stream xr instances - manage Immersive Stream for XR + instances + +SYNOPSIS + gcloud alpha immersive-stream xr instances COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Immersive Stream for XR instances. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create an Immersive Stream for XR service instance. + + delete + (ALPHA) Delete an Immersive Stream for XR service instance. + + describe + (ALPHA) Describe a specific Immersive Stream for XR service instance. + + list + (ALPHA) List Immersive Stream for XR service instances. + + update + (ALPHA) Update an Immersive Stream for XR service instance. + +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/immersive-stream/xr/instances/list b/gcloud/alpha/immersive-stream/xr/instances/list new file mode 100644 index 000000000..5142f64ef --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/instances/list @@ -0,0 +1,84 @@ +NAME + gcloud alpha immersive-stream xr instances list - list Immersive Stream for + XR service instances + +SYNOPSIS + gcloud alpha immersive-stream xr instances list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Immersive Stream for XR service instances. + +EXAMPLES + To list Immersive Stream for XR service instances, run: + + $ gcloud alpha immersive-stream xr instances list + +FLAGS + Location resource - Location to list all Immersive Stream for XR service + instances, defaults to global. 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; + ◆ global is the only supported 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; + ▸ global is the only supported 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 stream/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com + +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/immersive-stream/xr/instances/update b/gcloud/alpha/immersive-stream/xr/instances/update new file mode 100644 index 000000000..6f330f683 --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/instances/update @@ -0,0 +1,98 @@ +NAME + gcloud alpha immersive-stream xr instances update - update an Immersive + Stream for XR service instance + +SYNOPSIS + gcloud alpha immersive-stream xr instances update + (INSTANCE : --location=LOCATION) + (--update-realm=[capacity=CAPACITY],[realm=REALM] | --version=VERSION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an Immersive Stream for XR service instance. This command + can either be used to update the capacity for an existing realm of the + service instance or to update the content build version served by the + instance. If updating the capacity, only one realm may be updated for each + command execution, and the new capacity may not be 0 or exceed the quota + limit. + +EXAMPLES + To update the service instance 'my-instance' to have capacity 2 for realm + REALM_NA_WEST, run: + + $ gcloud alpha immersive-stream xr instances update my-instance \ + --update-realm=realm=REALM_NA_WEST,capacity=2 + + To update the service instance 'my-instance' to serve content build version + 'my-version', run: + + $ gcloud alpha immersive-stream xr instances update my-instance \ + --version=my-version + +POSITIONAL ARGUMENTS + Instance resource - Immersive Stream for XR service instance to update. + 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 instance 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. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. To + set the name attribute: + ▸ provide the argument instance on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Google Cloud location for the instance. To set the location + attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ location is always global. + +REQUIRED FLAGS + Update options + + Exactly one of these must be specified: + + --update-realm=[capacity=CAPACITY],[realm=REALM] + Flag used to specify realm and capacity required for the service + instance's availability. + + 'realm' is the realm in which the instance is deployed, and must be + one of the following: REALM_UNSPECIFIED REALM_NA_CENTRAL + REALM_NA_EAST REALM_NA_WEST REALM_ASIA_NORTHEAST REALM_ASIA_SOUTHEAST + REALM_EU_WEST + + 'capacity' is the maxium number of concurrent streaming sessions that + the instance can support in the given realm. + + --version=VERSION + Build version tag of the content served by this instance + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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/immersive-stream/xr/operations/describe b/gcloud/alpha/immersive-stream/xr/operations/describe new file mode 100644 index 000000000..8b9f3242b --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/operations/describe @@ -0,0 +1,69 @@ +NAME + gcloud alpha immersive-stream xr operations describe - get description of a + long-running Immersive Stream for XR operation + +SYNOPSIS + gcloud alpha immersive-stream xr operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get information about a long-running Immersive Stream for XR + operation. + +EXAMPLES + To get information about a long-running operation with name + 'projects/my-project/locations/global/operations/operation-123', run the + following command: + + $ gcloud alpha immersive-stream xr operations describe \ + projects/my-project/locations/global/operations/operation-123 + + or simply run + + $ gcloud alpha immersive-stream xr operations describe operation-123 + +POSITIONAL ARGUMENTS + Operation resource - The ID of the operation 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Global location name. To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the stream/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com + +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/immersive-stream/xr/operations/help b/gcloud/alpha/immersive-stream/xr/operations/help new file mode 100644 index 000000000..210396572 --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/operations/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha immersive-stream xr operations - manage Immersive Stream for + XR operations + +SYNOPSIS + gcloud alpha immersive-stream xr operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Immersive Stream for XR operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Get description of a long-running Immersive Stream for XR + operation. + + wait + (ALPHA) Poll long-running Immersive Stream for XR operation until it + completes. + +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/immersive-stream/xr/operations/wait b/gcloud/alpha/immersive-stream/xr/operations/wait new file mode 100644 index 000000000..35fd2200f --- /dev/null +++ b/gcloud/alpha/immersive-stream/xr/operations/wait @@ -0,0 +1,70 @@ +NAME + gcloud alpha immersive-stream xr operations wait - poll long-running + Immersive Stream for XR operation until it completes + +SYNOPSIS + gcloud alpha immersive-stream xr operations wait + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Poll a long-running Immersive Stream for XR operation until it + completes. When the operation is complete, this command will display the + results of the analysis. + +EXAMPLES + To poll a long-running Immersive Stream for XR operation named + 'projects/my-project/locations/global/operations/operation-123' until it + completes, run the following: + + $ gcloud alpha immersive-stream xr operations wait \ + projects/my-project/locations/global/operations/operation-123 + + or simply run + + $ gcloud alpha immersive-stream xr operations wait operation-123 + +POSITIONAL ARGUMENTS + Operation resource - The ID of the operation to poll until complete. 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 operation 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. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Global location name. To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the stream/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com + +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/memcache/instances/create b/gcloud/alpha/memcache/instances/create index bd10ff07d..91c643391 100644 --- a/gcloud/alpha/memcache/instances/create +++ b/gcloud/alpha/memcache/instances/create @@ -96,7 +96,7 @@ OPTIONAL FLAGS sunday, thursday, tuesday, wednesday. --maintenance-window-duration=MAINTENANCE_WINDOW_DURATION - Duration of the maintenance window in integer hours, e.g 4. + Duration in integer hours (3 to 8) of the maintenance window. --maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME Hour of day (0 to 23) for the start of maintenance window, in UTC time diff --git a/gcloud/alpha/memcache/instances/reschedule-maintenance b/gcloud/alpha/memcache/instances/reschedule-maintenance index 43b3045c7..6a7153e00 100644 --- a/gcloud/alpha/memcache/instances/reschedule-maintenance +++ b/gcloud/alpha/memcache/instances/reschedule-maintenance @@ -86,7 +86,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud memcache instances reschedule-maintenance $ gcloud beta memcache instances reschedule-maintenance diff --git a/gcloud/alpha/memcache/instances/update b/gcloud/alpha/memcache/instances/update index 03c443c83..7230ffd39 100644 --- a/gcloud/alpha/memcache/instances/update +++ b/gcloud/alpha/memcache/instances/update @@ -158,7 +158,7 @@ REQUIRED FLAGS sunday, thursday, tuesday, wednesday. --maintenance-window-duration=MAINTENANCE_WINDOW_DURATION - Duration of the maintenance window in integer hours, e.g '4'. + Duration in integer hours (3 to 8) of the maintenance window. --maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME Hour of day (0 to 23) for the start of maintenance window, in UTC diff --git a/gcloud/alpha/pubsub/subscriptions/create b/gcloud/alpha/pubsub/subscriptions/create index c1228a7b8..64623b964 100644 --- a/gcloud/alpha/pubsub/subscriptions/create +++ b/gcloud/alpha/pubsub/subscriptions/create @@ -71,12 +71,12 @@ OPTIONAL FLAGS acknowledge receiving a message before re-attempting delivery. --enable-exactly-once-delivery - Whether or not to enble exactly once delivery on the subscription. If + Whether or not to enable exactly-once delivery on the subscription. If true, Pub/Sub provides the following guarantees for the delivery of a message with a given value of message_id on this subscription: The message sent to a subscriber is guaranteed not to be resent before the - message's acknowledgement deadline expires. An acknowledged message - will not be resent to a subscriber. + message's acknowledgment deadline expires. An acknowledged message will + not be resent to a subscriber. --enable-message-ordering Whether to receive messages with the same ordering key in order. If diff --git a/gcloud/alpha/pubsub/subscriptions/update b/gcloud/alpha/pubsub/subscriptions/update index 55d347d65..4a89cae09 100644 --- a/gcloud/alpha/pubsub/subscriptions/update +++ b/gcloud/alpha/pubsub/subscriptions/update @@ -45,12 +45,13 @@ FLAGS acknowledge receiving a message before re-attempting delivery. --enable-exactly-once-delivery - Whether or not to enble exactly once delivery on the subscription. If + Whether or not to enable exactly-once delivery on the subscription. If true, Pub/Sub provides the following guarantees for the delivery of a message with a given value of message_id on this subscription: The message sent to a subscriber is guaranteed not to be resent before the - message's acknowledgement deadline expires. An acknowledged message - will not be resent to a subscriber. + message's acknowledgment deadline expires. An acknowledged message will + not be resent to a subscriber. To disable exactly-once delivery use + --no-enable-exactly-once-delivery. --expiration-period=EXPIRATION_PERIOD The subscription will expire if it is inactive for the given period. diff --git a/gcloud/alpha/redis/instances/create b/gcloud/alpha/redis/instances/create index 90de5455c..49bfe76f5 100644 --- a/gcloud/alpha/redis/instances/create +++ b/gcloud/alpha/redis/instances/create @@ -4,8 +4,10 @@ NAME SYNOPSIS gcloud alpha redis instances create (INSTANCE : --region=REGION) [--alternative-zone=ALTERNATIVE_ZONE] [--async] - [--connect-mode=CONNECT_MODE] [--display-name=DISPLAY_NAME] - [--enable-auth] [--labels=[KEY=VALUE,...]] + [--connect-mode=CONNECT_MODE] + [--customer-managed-key=CUSTOMER_MANAGED_KEY] + [--display-name=DISPLAY_NAME] [--enable-auth] + [--labels=[KEY=VALUE,...]] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [--network=NETWORK; default="default"] @@ -79,6 +81,10 @@ FLAGS Network connection mode used by instances. CONNECT_MODE must be one of: connect-mode-unspecified, direct-peering, private-service-access. + --customer-managed-key=CUSTOMER_MANAGED_KEY + The KMS key reference that you want to use to encrypt the data at rest + for this Redis instance. If this is provided, CMEK is enabled. + --display-name=DISPLAY_NAME A human-readable name for the instance. diff --git a/gcloud/alpha/transfer/jobs/create b/gcloud/alpha/transfer/jobs/create index 7fbc0cb7c..1b753981b 100644 --- a/gcloud/alpha/transfer/jobs/create +++ b/gcloud/alpha/transfer/jobs/create @@ -241,8 +241,10 @@ FLAGS are different (e.g., if etags or checksums don't match) ▸ 'always' - Overwrite destination file whenever source file has the same name -- even if they're identical + ▸ 'never' - Never overwrite destination file when source file has + the same name - OVERWRITE_WHEN must be one of: always, different. + OVERWRITE_WHEN must be one of: always, different, never. --delete-from=DELETE_FROM By default, transfer jobs won't delete any data from your source or diff --git a/gcloud/alpha/transfer/jobs/update b/gcloud/alpha/transfer/jobs/update index c9cbaa7d9..139f746e5 100644 --- a/gcloud/alpha/transfer/jobs/update +++ b/gcloud/alpha/transfer/jobs/update @@ -292,8 +292,10 @@ FLAGS are different (e.g., if etags or checksums don't match) ▸ 'always' - Overwrite destination file whenever source file has the same name -- even if they're identical + ▸ 'never' - Never overwrite destination file when source file has + the same name - OVERWRITE_WHEN must be one of: always, different. + OVERWRITE_WHEN must be one of: always, different, never. --delete-from=DELETE_FROM By default, transfer jobs won't delete any data from your source or diff --git a/gcloud/alpha/vmware/clusters/create b/gcloud/alpha/vmware/clusters/create index 4777cf5eb..963363619 100644 --- a/gcloud/alpha/vmware/clusters/create +++ b/gcloud/alpha/vmware/clusters/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha vmware clusters create (CLUSTER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) - --node-count=NODE_COUNT --node-type=NODE_TYPE [GCLOUD_WIDE_FLAG ...] + --node-count=NODE_COUNT --node-type=NODE_TYPE [--async] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a cluster in a VMware Engine private cloud. Successful @@ -85,6 +86,12 @@ REQUIRED FLAGS To set the node-type attribute: ▸ provide the argument --node-type on the command line. +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + 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/vmware/clusters/delete b/gcloud/alpha/vmware/clusters/delete index d91996f06..1e273f4b4 100644 --- a/gcloud/alpha/vmware/clusters/delete +++ b/gcloud/alpha/vmware/clusters/delete @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha vmware clusters delete - (CLUSTER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + (CLUSTER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -59,6 +59,12 @@ POSITIONAL ARGUMENTS specified name; ▸ provide the argument --private-cloud on the command line. +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + 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/vmware/clusters/update b/gcloud/alpha/vmware/clusters/update index 0c0c8c404..6cdfcd216 100644 --- a/gcloud/alpha/vmware/clusters/update +++ b/gcloud/alpha/vmware/clusters/update @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha vmware clusters update (CLUSTER : --location=LOCATION --private-cloud=PRIVATE_CLOUD) - --node-count=NODE_COUNT [GCLOUD_WIDE_FLAG ...] + --node-count=NODE_COUNT [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Adjust the number of nodes in the VMware Engine cluster. Successful @@ -64,6 +64,12 @@ REQUIRED FLAGS --node-count=NODE_COUNT Nodes count for cluster +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + 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/vmware/hcx/activationkeys/create b/gcloud/alpha/vmware/hcx/activationkeys/create index 4654079d1..e6a8c7be8 100644 --- a/gcloud/alpha/vmware/hcx/activationkeys/create +++ b/gcloud/alpha/vmware/hcx/activationkeys/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha vmware hcx activationkeys create (HCX_ACTIVATION_KEY - : --location=LOCATION --private-cloud=PRIVATE_CLOUD) + : --location=LOCATION --private-cloud=PRIVATE_CLOUD) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -63,6 +63,12 @@ POSITIONAL ARGUMENTS a fully specified name; ▸ provide the argument --private-cloud on the command line. +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + 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/vmware/network-peerings/create b/gcloud/alpha/vmware/network-peerings/create index e86331573..371153915 100644 --- a/gcloud/alpha/vmware/network-peerings/create +++ b/gcloud/alpha/vmware/network-peerings/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha vmware network-peerings create NETWORK_PEERING --peer-network=PEER_NETWORK --peer-network-type=PEER_NETWORK_TYPE (--vmware-engine-network=VMWARE_ENGINE_NETWORK : --location=LOCATION) - [--description=DESCRIPTION] [--no-exchange-subnet-routes] + [--async] [--description=DESCRIPTION] [--no-exchange-subnet-routes] [--no-export-custom-routes] [--no-export-custom-routes-with-public-ip] [--no-import-custom-routes] [--no-import-custom-routes-with-public-ip] [--peer-mtu=PEER_MTU] [GCLOUD_WIDE_FLAG ...] @@ -111,6 +111,11 @@ REQUIRED FLAGS ▸ set location as 'global' (default) or a region. OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + --description=DESCRIPTION User-provided description of the VPC network peering. diff --git a/gcloud/alpha/vmware/network-peerings/delete b/gcloud/alpha/vmware/network-peerings/delete index bc50ad2d7..1c8185fc4 100644 --- a/gcloud/alpha/vmware/network-peerings/delete +++ b/gcloud/alpha/vmware/network-peerings/delete @@ -3,7 +3,7 @@ NAME Engine VPC network peering SYNOPSIS - gcloud alpha vmware network-peerings delete NETWORK_PEERING + gcloud alpha vmware network-peerings delete NETWORK_PEERING [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -37,6 +37,12 @@ POSITIONAL ARGUMENTS network-peering attribute: ▸ provide the argument network_peering on the command line. +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + 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/vmware/network-peerings/update b/gcloud/alpha/vmware/network-peerings/update index df4d407ff..7f620ff12 100644 --- a/gcloud/alpha/vmware/network-peerings/update +++ b/gcloud/alpha/vmware/network-peerings/update @@ -3,7 +3,7 @@ NAME Engine VPC network peering SYNOPSIS - gcloud alpha vmware network-peerings update NETWORK_PEERING + gcloud alpha vmware network-peerings update NETWORK_PEERING [--async] [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -38,6 +38,11 @@ POSITIONAL ARGUMENTS ▸ provide the argument network_peering on the command line. FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + --description=DESCRIPTION Updated description for this VPC network peering. diff --git a/gcloud/alpha/vmware/nsx/credentials/reset b/gcloud/alpha/vmware/nsx/credentials/reset index b3f232596..a54e08898 100644 --- a/gcloud/alpha/vmware/nsx/credentials/reset +++ b/gcloud/alpha/vmware/nsx/credentials/reset @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha vmware nsx credentials reset - (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) + (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -54,6 +54,12 @@ REQUIRED FLAGS ▸ provide the argument --location on the command line; ▸ set the property compute/zone. +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + 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/vmware/private-clouds/create b/gcloud/alpha/vmware/private-clouds/create index 3b83ef387..f4a676f24 100644 --- a/gcloud/alpha/vmware/private-clouds/create +++ b/gcloud/alpha/vmware/private-clouds/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha vmware private-clouds create (PRIVATE_CLOUD : --location=LOCATION) --cluster=CLUSTER --management-range=MANAGEMENT_RANGE --network=NETWORK - --node-count=NODE_COUNT --node-type=NODE_TYPE + --node-count=NODE_COUNT --node-type=NODE_TYPE [--async] [--description=DESCRIPTION] [--network-project=NETWORK_PROJECT] [GCLOUD_WIDE_FLAG ...] @@ -117,6 +117,11 @@ REQUIRED FLAGS ▸ provide the argument --node-type on the command line. OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + --description=DESCRIPTION Text describing the private cloud. diff --git a/gcloud/alpha/vmware/private-clouds/delete b/gcloud/alpha/vmware/private-clouds/delete index c8140c367..a6b08c4b3 100644 --- a/gcloud/alpha/vmware/private-clouds/delete +++ b/gcloud/alpha/vmware/private-clouds/delete @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha vmware private-clouds delete - (PRIVATE_CLOUD : --location=LOCATION) + (PRIVATE_CLOUD : --location=LOCATION) [--async] [--delay-hours=DELAY_HOURS; default=3] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -53,6 +53,11 @@ POSITIONAL ARGUMENTS ▸ set the property compute/zone. FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + --delay-hours=DELAY_HOURS; default=3 Number of hours to wait before deleting the private cloud. Specifying a value of 0 for this field begins the deletion process immediately. diff --git a/gcloud/alpha/vmware/private-clouds/undelete b/gcloud/alpha/vmware/private-clouds/undelete index 3556c4c71..60f118e88 100644 --- a/gcloud/alpha/vmware/private-clouds/undelete +++ b/gcloud/alpha/vmware/private-clouds/undelete @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha vmware private-clouds undelete - (PRIVATE_CLOUD : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + (PRIVATE_CLOUD : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Unmark a VMware Engine private cloud that was previously marked for @@ -50,6 +50,12 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line; ▸ set the property compute/zone. +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + 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/vmware/private-clouds/update b/gcloud/alpha/vmware/private-clouds/update index 0ed565343..26ec03ab8 100644 --- a/gcloud/alpha/vmware/private-clouds/update +++ b/gcloud/alpha/vmware/private-clouds/update @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha vmware private-clouds update - (PRIVATE_CLOUD : --location=LOCATION) [--description=DESCRIPTION] - [GCLOUD_WIDE_FLAG ...] + (PRIVATE_CLOUD : --location=LOCATION) [--async] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a VMware Engine private cloud. @@ -54,6 +54,11 @@ POSITIONAL ARGUMENTS ▸ set the property compute/zone. FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + --description=DESCRIPTION Text describing the private cloud diff --git a/gcloud/alpha/vmware/vcenter/credentials/reset b/gcloud/alpha/vmware/vcenter/credentials/reset index 00dbf9d00..41db9666e 100644 --- a/gcloud/alpha/vmware/vcenter/credentials/reset +++ b/gcloud/alpha/vmware/vcenter/credentials/reset @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha vmware vcenter credentials reset - (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) + (--private-cloud=PRIVATE_CLOUD : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -55,6 +55,12 @@ REQUIRED FLAGS ▸ provide the argument --location on the command line; ▸ set the property compute/zone. +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + 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/app/deploy b/gcloud/app/deploy index d7aeacbc5..1d1f2564f 100644 --- a/gcloud/app/deploy +++ b/gcloud/app/deploy @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud app deploy [DEPLOYABLES ...] [--appyaml=APPYAML] [--bucket=BUCKET] [--no-cache] [--ignore-file=IGNORE_FILE] [--image-url=IMAGE_URL] - [--no-promote] [--no-stop-previous-version] - [--version=VERSION, -v VERSION] [GCLOUD_WIDE_FLAG ...] + [--no-promote] [--service-account=SERVICE_ACCOUNT] + [--no-stop-previous-version] [--version=VERSION, -v VERSION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command is used to deploy both code and configuration to the App @@ -66,6 +67,11 @@ EXAMPLES $ gcloud config set app/promote_by_default false + To deploy a service that will run as a service account, run: + + $ gcloud app deploy ~/my_app/app.yaml \ + --service-account=SERVICE_ACCOUNT + POSITIONAL ARGUMENTS [DEPLOYABLES ...] The yaml files for the services or configurations you want to deploy. @@ -101,6 +107,11 @@ FLAGS default app/promote_by_default property value for this command invocation. Use --no-promote to disable. + --service-account=SERVICE_ACCOUNT + The service account that this deployed version will run as. If this + argument is not specified, the App Engine default service account will + be used for your current deployed version. + --stop-previous-version Stop the previously running version when deploying a new version that receives all traffic. diff --git a/gcloud/beta/active-directory/domains/backups/create b/gcloud/beta/active-directory/domains/backups/create index 25f9f06ba..b07b7d94e 100644 --- a/gcloud/beta/active-directory/domains/backups/create +++ b/gcloud/beta/active-directory/domains/backups/create @@ -1,6 +1,6 @@ NAME gcloud beta active-directory domains backups create - create a Managed - Microsoft Active Directory domain backup + Microsoft AD domain backup SYNOPSIS gcloud beta active-directory domains backups create @@ -8,21 +8,21 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Create a new Managed Microsoft AD domain backup with the given name - using Google Cloud's Managed Service for Microsoft Active Directory. + (BETA) Create a new Managed Microsoft AD domain backup with the specified + name using Google Cloud's Managed Service for Microsoft Active Directory. This command can fail for the following reasons: - ▪ The domain specified does not exist. - ▪ The domain specified is being created. + ▪ The specified domain doesn't exist. + ▪ The specified domain is being created. ▪ A backup already exists with the same target domain name. - ▪ The active account does not have permission to access the given + ▪ The active account doesn't have permission to access the specified domain. - ▪ The active account does not have permission to create AD domain + ▪ The active account doesn't have permission to create AD domain backups. EXAMPLES - The following command creates an Active Directory domain backup named - my-backup under domain my-domain.com + To create an AD domain backup named my-backup under domain my-domain.com, + run: $ gcloud beta active-directory domains backups create my-backup \ --domain=my-domain.com --project=my-proj --async @@ -77,8 +77,10 @@ API REFERENCE https://cloud.google.com/managed-microsoft-ad/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud active-directory domains backups create $ gcloud alpha active-directory domains backups create diff --git a/gcloud/beta/active-directory/domains/backups/delete b/gcloud/beta/active-directory/domains/backups/delete index 9e3034113..753aa8e29 100644 --- a/gcloud/beta/active-directory/domains/backups/delete +++ b/gcloud/beta/active-directory/domains/backups/delete @@ -1,24 +1,24 @@ NAME gcloud beta active-directory domains backups delete - delete a Managed - Microsoft Active Directory domain backup + Microsoft AD domain backup SYNOPSIS gcloud beta active-directory domains backups delete (BACKUP : --domain=DOMAIN) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Delete a Managed Microsoft AD domain backup with the given name + (BETA) Delete a Managed Microsoft AD domain backup with the specified name using Google Cloud's Managed Service for Microsoft Active Directory. This command can fail for the following reasons: - ▪ TThe backup specified does not exist. - ▪ The active account does not have permission to access the given + ▪ The specified backup doesn't exist. + ▪ The active account doesn't have permission to access the specified domain. - ▪ The active account does not have permission to access the given AD - backup. + ▪ The active account doesn't have permission to access the specified AD + domain backup. EXAMPLES - The following command deletes an AD domain backup my-backup under domain projects/my-proj/locations/global/domains/my-domain.com + To delete an AD domain backup my-backup under domain `projects/my-proj/locations/global/domains/my-domain.com`, run: $ gcloud beta active-directory domains backups delete \ projects/my-proj/locations/global/domains/my-domain.com/\ @@ -71,8 +71,10 @@ API REFERENCE https://cloud.google.com/managed-microsoft-ad/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud active-directory domains backups delete $ gcloud alpha active-directory domains backups delete diff --git a/gcloud/beta/active-directory/domains/backups/describe b/gcloud/beta/active-directory/domains/backups/describe index a1d58f064..c929cbb79 100644 --- a/gcloud/beta/active-directory/domains/backups/describe +++ b/gcloud/beta/active-directory/domains/backups/describe @@ -1,6 +1,6 @@ NAME gcloud beta active-directory domains backups describe - describe a Managed - Microsoft Active Directory domain backup + Microsoft AD domain backup SYNOPSIS gcloud beta active-directory domains backups describe @@ -9,17 +9,17 @@ SYNOPSIS DESCRIPTION (BETA) Show metadata for a Managed Microsoft AD domain backup. - Displays all metadata associated with a Active Directory domain backup - given a valid domain backup name. + Displays all metadata associated with an Active Directory domain backup + when provided with a valid domain backup name. This command can fail for the following reasons: - ▪ The specified domain backup does not exist. - ▪ The active account does not have permission to access the given + ▪ The specified domain backup doesn't exist. + ▪ The active account doesn't have permission to access the specified domain. EXAMPLES - The following command gets metadata for an AD domain backup with the name - my-backup under the domain my-domain in project my-project. + To display all metadata associated with an AD domain backup with the name + my-backup under the domain my-domain in project my-project, run: $ gcloud beta active-directory domains backups describe \ projects/my-proj/locations/global/domains/my-domain.com/\ @@ -67,8 +67,10 @@ API REFERENCE https://cloud.google.com/managed-microsoft-ad/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud active-directory domains backups describe $ gcloud alpha active-directory domains backups describe diff --git a/gcloud/beta/active-directory/domains/backups/help b/gcloud/beta/active-directory/domains/backups/help index ac42a93fa..cb9ea4a83 100644 --- a/gcloud/beta/active-directory/domains/backups/help +++ b/gcloud/beta/active-directory/domains/backups/help @@ -16,23 +16,25 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create a Managed Microsoft Active Directory domain backup. + (BETA) Create a Managed Microsoft AD domain backup. delete - (BETA) Delete a Managed Microsoft Active Directory domain backup. + (BETA) Delete a Managed Microsoft AD domain backup. describe - (BETA) Describe a Managed Microsoft Active Directory domain backup. + (BETA) Describe a Managed Microsoft AD domain backup. list - (BETA) List all Managed Microsoft Active Directory domain backups. + (BETA) List all Managed Microsoft AD domain backups. update - (BETA) Update a managed Microsoft Active Directory domain backup. + (BETA) Update a Managed Microsoft AD domain backup. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud active-directory domains backups $ gcloud alpha active-directory domains backups diff --git a/gcloud/beta/active-directory/domains/backups/list b/gcloud/beta/active-directory/domains/backups/list index 31b0fdddd..ebe053147 100644 --- a/gcloud/beta/active-directory/domains/backups/list +++ b/gcloud/beta/active-directory/domains/backups/list @@ -1,6 +1,6 @@ NAME gcloud beta active-directory domains backups list - list all Managed - Microsoft Active Directory domain backups + Microsoft AD domain backups SYNOPSIS gcloud beta active-directory domains backups list --domain=DOMAIN @@ -8,27 +8,27 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List all Managed Microsoft AD domain backups in the given Managed - Microsoft AD domain. + (BETA) List all Managed Microsoft AD domain backups in the specified + Managed Microsoft AD domain. Displays associated Active Directory domain backups. This command can fail for the following reasons: - ▪ The active account does not have permission to access the given + ▪ The active account doesn't have permission to access the specified domain. EXAMPLES - The following command lists all an AD domain backups in the project - my-project and domain my-domain.com. + To list all AD domain backups in the project my-project under domain + my-domain.com, run: $ gcloud beta active-directory domains backups list \ --project=my-project --domain=my-domain.com --limit=5 REQUIRED FLAGS - Domain resource - Name of the domain under which you want to list all - Managed Microsoft AD domain backups. 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: + Domain resource - Name of the domain for which you want to list all + associated Managed Microsoft AD domain backups. 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 --domain on the command line with a fully specified name; ◆ set the property core/project; @@ -87,8 +87,10 @@ API REFERENCE https://cloud.google.com/managed-microsoft-ad/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud active-directory domains backups list $ gcloud alpha active-directory domains backups list diff --git a/gcloud/beta/active-directory/domains/backups/update b/gcloud/beta/active-directory/domains/backups/update index 37fc9eb70..2b52c0118 100644 --- a/gcloud/beta/active-directory/domains/backups/update +++ b/gcloud/beta/active-directory/domains/backups/update @@ -1,6 +1,6 @@ NAME - gcloud beta active-directory domains backups update - update a managed - Microsoft Active Directory domain backup + gcloud beta active-directory domains backups update - update a Managed + Microsoft AD domain backup SYNOPSIS gcloud beta active-directory domains backups update @@ -8,15 +8,15 @@ SYNOPSIS [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Update a managed Microsoft Active Directory domain backup. - ▪ The backup specified does not exist. - ▪ The active account does not have permission to access the given + (BETA) Update a Managed Microsoft AD domain backup. + ▪ The specified backup doesn't exist. + ▪ The active account doesn't have permission to access the specified domain. - ▪ The active account does not have permission to access the given - backup. + ▪ The active account doesn't have permission to access the specified + domain backup. EXAMPLES - The following command updates an AD domain backup my-backup under domain projects/my-proj/locations/global/domains/my-domain.com with the labels l1 and l2 + To update an AD domain backup my-backup under domain `projects/my-proj/locations/global/domains/my-domain.com` with the labels `l1` and `l2`, run: $ gcloud beta active-directory domains backups update \ projects/my-proj/locations/global/domains/my-domain.com/\ @@ -98,8 +98,10 @@ API REFERENCE https://cloud.google.com/managed-microsoft-ad/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud active-directory domains backups update $ gcloud alpha active-directory domains backups update diff --git a/gcloud/beta/active-directory/domains/help b/gcloud/beta/active-directory/domains/help index 11d4378f4..42af6fc44 100644 --- a/gcloud/beta/active-directory/domains/help +++ b/gcloud/beta/active-directory/domains/help @@ -50,7 +50,7 @@ COMMANDS (BETA) Reset the admin password for a Managed Microsoft AD domain. restore - (BETA) Restore the domain from The specified backup. + (BETA) Restore a domain from the specified backup. set-iam-policy (BETA) Set the IAM policy for a Managed Microsoft AD domain. diff --git a/gcloud/beta/active-directory/domains/restore b/gcloud/beta/active-directory/domains/restore index cc1a93655..30845da12 100644 --- a/gcloud/beta/active-directory/domains/restore +++ b/gcloud/beta/active-directory/domains/restore @@ -1,5 +1,5 @@ NAME - gcloud beta active-directory domains restore - restore the domain from The + gcloud beta active-directory domains restore - restore a domain from the specified backup SYNOPSIS @@ -7,24 +7,25 @@ SYNOPSIS [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Restore a Managed Microsoft Active Directory domain to a previous - point in time when the backup was taken. + (BETA) Restore a Managed Microsoft AD domain to a previous point in time + when the backup was taken. This command can fail for the following reasons: - ▪ The domain specified does not exist. - ▪ The backup specified does not exist. - ▪ The active account does not have permission to restore the domain. + ▪ The specified domain doesn't exist. + ▪ The specified backup doesn't exist. + ▪ The active account doesn't have permission to restore the specified + domain. EXAMPLES - To restore the domain my-domain.com from backup my-backup: + To restore the domain my-domain.com from backup my-backup, run: $ gcloud beta active-directory domains restore my-domain.com \ --backup=my-backup --async POSITIONAL ARGUMENTS - Domain resource - Name of the managed Managed Microsoft AD domain you want - to restore. 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 + Domain resource - Name of the Managed Microsoft AD domain you want to + restore. 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 domain on the command line with a fully specified name; @@ -40,8 +41,8 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --backup=BACKUP - Name of the managed Managed Microsoft AD domain backup you want to - restore from to. + Name of the domain backup from which you want to restore the Managed + Microsoft AD domain. OPTIONAL FLAGS --async @@ -62,8 +63,10 @@ API REFERENCE https://cloud.google.com/managed-microsoft-ad/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud active-directory domains restore $ gcloud alpha active-directory domains restore diff --git a/gcloud/beta/alloydb/backups/create b/gcloud/beta/alloydb/backups/create new file mode 100644 index 000000000..84dee5106 --- /dev/null +++ b/gcloud/beta/alloydb/backups/create @@ -0,0 +1,48 @@ +NAME + gcloud beta alloydb backups create - creates a new AlloyDB backup within a + given project + +SYNOPSIS + gcloud beta alloydb backups create BACKUP --cluster=CLUSTER --region=REGION + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Creates a new AlloyDB backup within a given project. + +EXAMPLES + To create a new backup, run: + + $ gcloud beta alloydb backups create my-backup \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + BACKUP + AlloyDB backup ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + The region of the cluster to backup. Note: both the cluster and the + backup have to be in the same region. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb backups create + diff --git a/gcloud/beta/alloydb/backups/delete b/gcloud/beta/alloydb/backups/delete new file mode 100644 index 000000000..e8734e8a8 --- /dev/null +++ b/gcloud/beta/alloydb/backups/delete @@ -0,0 +1,44 @@ +NAME + gcloud beta alloydb backups delete - deletes an AlloyDB backup within a + given project + +SYNOPSIS + gcloud beta alloydb backups delete BACKUP --region=REGION [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes an AlloyDB backup within a given project. + +EXAMPLES + To delete a backup, run: + + $ gcloud beta alloydb backups delete my-backup --region=us-central1 + +POSITIONAL ARGUMENTS + BACKUP + AlloyDB backup ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb backups delete + diff --git a/gcloud/beta/alloydb/backups/describe b/gcloud/beta/alloydb/backups/describe new file mode 100644 index 000000000..5994bced5 --- /dev/null +++ b/gcloud/beta/alloydb/backups/describe @@ -0,0 +1,39 @@ +NAME + gcloud beta alloydb backups describe - creates a new AlloyDB backup within + a given project and location + +SYNOPSIS + gcloud beta alloydb backups describe BACKUP --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Creates a new AlloyDB backup within a given project and location. + +EXAMPLES + To describe a backup, run: + + $ gcloud beta alloydb backups describe my-backup --region=us-central1 + +POSITIONAL ARGUMENTS + BACKUP + AlloyDB backup ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb backups describe + diff --git a/gcloud/beta/alloydb/backups/help b/gcloud/beta/alloydb/backups/help new file mode 100644 index 000000000..0aff92a8b --- /dev/null +++ b/gcloud/beta/alloydb/backups/help @@ -0,0 +1,37 @@ +NAME + gcloud beta alloydb backups - provide commands for managing AlloyDB backups + +SYNOPSIS + gcloud beta alloydb backups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Provide commands for managing AlloyDB backups including creating, + deleting, and listing backups. + +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) Creates a new AlloyDB backup within a given project. + + delete + (BETA) Deletes an AlloyDB backup within a given project. + + describe + (BETA) Creates a new AlloyDB backup within a given project and + location. + + list + (BETA) Lists AlloyDB backups in a given project. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb backups + diff --git a/gcloud/beta/alloydb/backups/list b/gcloud/beta/alloydb/backups/list new file mode 100644 index 000000000..6650ccbf7 --- /dev/null +++ b/gcloud/beta/alloydb/backups/list @@ -0,0 +1,69 @@ +NAME + gcloud beta alloydb backups list - lists AlloyDB backups in a given project + +SYNOPSIS + gcloud beta alloydb backups list [--region=REGION; default="-"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Lists AlloyDB backups in a given project in the alphabetical order + of the backup name. + +EXAMPLES + To list backups, run: + + $ gcloud beta alloydb backups list --region=us-central1 + +FLAGS + --region=REGION; default="-" + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + Default: list clusters in all regions. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb backups list + diff --git a/gcloud/beta/alloydb/clusters/create b/gcloud/beta/alloydb/clusters/create new file mode 100644 index 000000000..b95aa25c7 --- /dev/null +++ b/gcloud/beta/alloydb/clusters/create @@ -0,0 +1,55 @@ +NAME + gcloud beta alloydb clusters create - creates a new AlloyDB cluster within + a given project + +SYNOPSIS + gcloud beta alloydb clusters create CLUSTER --password=PASSWORD + --region=REGION [--async] [--network=NETWORK] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Creates a new AlloyDB cluster within a given project. + +EXAMPLES + To create a new cluster, run: + + $ gcloud beta alloydb clusters create my-cluster \ + --region=us-central1 --password=postgres + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + --password=PASSWORD + Initial postgres user password to set up during cluster creation. + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --network=NETWORK + Network in the current project that the instance will be part of. To + specify using a network with a shared VPC, use the full URL of the + network. For an example host project, 'testproject', and shared + network, 'testsharednetwork', this would be of the + form:--network=projects/testproject/global/networks/testsharednetwork + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb clusters create + diff --git a/gcloud/beta/alloydb/clusters/delete b/gcloud/beta/alloydb/clusters/delete new file mode 100644 index 000000000..f1ab48dba --- /dev/null +++ b/gcloud/beta/alloydb/clusters/delete @@ -0,0 +1,53 @@ +NAME + gcloud beta alloydb clusters delete - deletes an AlloyDB cluster in a given + region + +SYNOPSIS + gcloud beta alloydb clusters delete CLUSTER --region=REGION [--async] + [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes an AlloyDB cluster in a given region. + +EXAMPLES + To delete a cluster, run: + + $ gcloud beta alloydb clusters delete my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --force + Default value is false. + + If flag is specified, deletes instances (if any) within this cluster, + before deleting the cluster. + + If flag is not specified, cluster delete will fail if there are + instances present in the cluster. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb clusters delete + diff --git a/gcloud/beta/alloydb/clusters/describe b/gcloud/beta/alloydb/clusters/describe new file mode 100644 index 000000000..26cad0a5a --- /dev/null +++ b/gcloud/beta/alloydb/clusters/describe @@ -0,0 +1,40 @@ +NAME + gcloud beta alloydb clusters describe - describes an AlloyDB cluster in a + given project and region + +SYNOPSIS + gcloud beta alloydb clusters describe CLUSTER --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describes an AlloyDB cluster in a given project and region. + +EXAMPLES + To describe a cluster, run: + + $ gcloud beta alloydb clusters describe my-cluster \ + --region=us-central1 + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb clusters describe + diff --git a/gcloud/beta/alloydb/clusters/help b/gcloud/beta/alloydb/clusters/help new file mode 100644 index 000000000..bd18d378e --- /dev/null +++ b/gcloud/beta/alloydb/clusters/help @@ -0,0 +1,43 @@ +NAME + gcloud beta alloydb clusters - provide commands for managing AlloyDB + clusters + +SYNOPSIS + gcloud beta alloydb clusters COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Provide commands for managing AlloyDB clusters including creating, + configuring, restarting, and deleting clusters. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Creates a new AlloyDB cluster within a given project. + + delete + (BETA) Deletes an AlloyDB cluster in a given region. + + describe + (BETA) Describes an AlloyDB cluster in a given project and region. + + list + (BETA) Lists AlloyDB clusters in a given project and region. + + restore + (BETA) Restores an AlloyDB cluster from a given backup. + + update + (BETA) Updates an AlloyDB cluster within a given project and region. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb clusters + diff --git a/gcloud/beta/alloydb/clusters/list b/gcloud/beta/alloydb/clusters/list new file mode 100644 index 000000000..2444a9f9e --- /dev/null +++ b/gcloud/beta/alloydb/clusters/list @@ -0,0 +1,70 @@ +NAME + gcloud beta alloydb clusters list - lists AlloyDB clusters in a given + project and region + +SYNOPSIS + gcloud beta alloydb clusters list [--region=REGION; default="-"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Lists AlloyDB clusters in a given project in the alphabetical order + of the cluster name. + +EXAMPLES + To list clusters, run: + + $ gcloud beta alloydb clusters list --region=us-central1 + +FLAGS + --region=REGION; default="-" + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + Default: list clusters in all regions. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb clusters list + diff --git a/gcloud/beta/alloydb/clusters/restore b/gcloud/beta/alloydb/clusters/restore new file mode 100644 index 000000000..4819c1bca --- /dev/null +++ b/gcloud/beta/alloydb/clusters/restore @@ -0,0 +1,55 @@ +NAME + gcloud beta alloydb clusters restore - restores an AlloyDB cluster from a + given backup + +SYNOPSIS + gcloud beta alloydb clusters restore CLUSTER --backup=BACKUP + --region=REGION [--async] [--network=NETWORK] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Restores an AlloyDB cluster from a given backup. + +EXAMPLES + To restore a cluster from a backup, run: + + $ gcloud beta alloydb clusters restore my-cluster \ + --region=us-central1 --backup=my-backup + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + --backup=BACKUP + AlloyDB backup ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --network=NETWORK + Network in the current project that the instance will be part of. To + specify using a network with a shared VPC, use the full URL of the + network. For an example host project, 'testproject', and shared + network, 'testsharednetwork', this would be of the + form:--network=projects/testproject/global/networks/testsharednetwork + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb clusters restore + diff --git a/gcloud/beta/alloydb/clusters/update b/gcloud/beta/alloydb/clusters/update new file mode 100644 index 000000000..3695ff637 --- /dev/null +++ b/gcloud/beta/alloydb/clusters/update @@ -0,0 +1,104 @@ +NAME + gcloud beta alloydb clusters update - updates an AlloyDB cluster within a + given project and region + +SYNOPSIS + gcloud beta alloydb clusters update CLUSTER --region=REGION [--async] + [--clear-automated-backup | --disable-automated-backup + | [--automated-backup-days-of-week=[DAYS_OF_WEEK,...] + --automated-backup-start-times=[START_TIMES,...] + : --automated-backup-window=TIMEOUT_PERIOD + --automated-backup-retention-count=RETENTION_COUNT + | --automated-backup-retention-period=RETENTION_PERIOD]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates an AlloyDB cluster within a given project and region. + +EXAMPLES + To update a cluster, run: + + $ gcloud beta alloydb clusters update my-cluster \ + --region=us-central1 --automated-backup-start-times=12:00 \ + --automated-backup-days-of-week=MONDAY \ + --automated-backup-retention-count=10 + +POSITIONAL ARGUMENTS + CLUSTER + AlloyDB cluster ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + Automated backup policy. + + At most one of these can be specified: + + --clear-automated-backup + Clears the automated backup policy on the cluster. The default + automated backup policy will be used. + + --disable-automated-backup + Disables automated backups on the cluster. + + Enable automated backup policy. + + --automated-backup-days-of-week=[DAYS_OF_WEEK,...] + Comma-separated list of days of the week to perform a backup. At + least one day of the week must be provided. (e.g., + --automated-backup-days-of-week=MONDAY,WEDNESDAY,SUNDAY). + DAYS_OF_WEEK must be one of: MONDAY, TUESDAY, WEDNESDAY, THURSDAY, + FRIDAY, SATURDAY, SUNDAY. + + This flag must be specified if any of the other arguments in this + group are specified. + + --automated-backup-start-times=[START_TIMES,...] + Comma-separated list of times during the day to start a backup. At + least one start time must be provided. The start times are assumed + to be in UTC and required to be an exact hour in the format HH:00. + (e.g., --automated-backup-start-times=01:00,13:00) + + This flag must be specified if any of the other arguments in this + group are specified. + + --automated-backup-window=TIMEOUT_PERIOD + The length of the time window beginning at start time during which + a backup can be taken. If a backup does not succeed within this + time window, it will be canceled and considered failed. The backup + window must be at least 5 minutes long. There is no upper bound on + the window. If not set, it will default to 1 hour. + + Retention policy. If no retention policy is provided, all automated + backups will be retained. + + At most one of these can be specified: + + --automated-backup-retention-count=RETENTION_COUNT + Number of most recent successful backups retained. + + --automated-backup-retention-period=RETENTION_PERIOD + Retention period of the backup relative to creation time. See $ + gcloud topic datetimes for information on duration formats. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb clusters update + diff --git a/gcloud/beta/alloydb/help b/gcloud/beta/alloydb/help new file mode 100644 index 000000000..2abb406a7 --- /dev/null +++ b/gcloud/beta/alloydb/help @@ -0,0 +1,41 @@ +NAME + gcloud beta alloydb - create and manage AlloyDB databases + +SYNOPSIS + gcloud beta alloydb GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The gcloud alloydb command group lets you create and manage Google + Cloud AlloyDB databases. + + AlloyDB is a fully-managed database service that makes it easy to set up, + maintain, manage, and administer your Alloydb databases in the cloud. + + More information on AlloyDB can be found here at go/alloydb + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + backups + (BETA) Provide commands for managing AlloyDB backups. + + clusters + (BETA) Provide commands for managing AlloyDB clusters. + + instances + (BETA) Provide commands for managing AlloyDB instances. + + operations + (BETA) Provide commands for managing AlloyDB operations. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb + diff --git a/gcloud/beta/alloydb/instances/create b/gcloud/beta/alloydb/instances/create new file mode 100644 index 000000000..0d24a896b --- /dev/null +++ b/gcloud/beta/alloydb/instances/create @@ -0,0 +1,100 @@ +NAME + gcloud beta alloydb instances create - creates a new AlloyDB instance + within a given cluster + +SYNOPSIS + gcloud beta alloydb instances create INSTANCE --cluster=CLUSTER + --cpu-count=CPU_COUNT --instance-type=INSTANCE_TYPE --region=REGION + [--async] [--availability-type=AVAILABILITY_TYPE] + [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--read-pool-node-count=READ_POOL_NODE_COUNT] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Creates a new AlloyDB instance within a given cluster. + +EXAMPLES + To create a new primary instance, run: + + $ gcloud beta alloydb instances create my-instance \ + --cluster=my-cluster --region=us-central1 \ + --instance-type=PRIMARY --cpu-count=4 + + To create a new read pool instance, run: + + $ gcloud beta alloydb instances create my-instance \ + --cluster=my-cluster --region=us-central1 \ + --instance-type=READ_POOL --read-pool-node-count=1 --cpu-count=4 + +POSITIONAL ARGUMENTS + INSTANCE + AlloyDB instance ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --cpu-count=CPU_COUNT + Whole number value indicating how many vCPUs the machine should + contain. Each vCPU count corresponds to a N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). + CPU_COUNT must be one of: 4, 8, 16, 32, 64. + + --instance-type=INSTANCE_TYPE + Specifies instance type. INSTANCE_TYPE must be one of: + + PRIMARY + PRIMARY instances support read and write operations. + READ_POOL + READ_POOL instances support read operations only. Each read pool + instance consists of one or more homogeneous nodes. * Read pool of + size 1 can only have zonal availability. * Read pools with node + count of 2 or more can have regional availability (nodes are + present in 2 or more zones in a region). + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --availability-type=AVAILABILITY_TYPE + Specifies level of availability. AVAILABILITY_TYPE must be (currently + only one value is supported): + + REGIONAL + Provides high availability and is recommended for production + instances; instance automatically fails over to another zone within + your selected region. + + --database-flags=FLAG=VALUE,[FLAG=VALUE,...] + Comma-separated list of database flags to set on the instance. Use an + equals sign to separate flag name and value. Flags without values, like + skip_grant_tables, can be written out without a value after, e.g., + skip_grant_tables=. Use on/off for booleans. View the Instance Resource + API for allowed flags. (e.g., --database-flags + max_allowed_packet=55555,skip_grant_tables=,log_output=1) + + --read-pool-node-count=READ_POOL_NODE_COUNT + Read capacity, i.e. number of nodes in a read pool instance. + + --zone=ZONE + Primary Compute Engine zone (e.g. us-central1, us-central1, etc. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb instances create + diff --git a/gcloud/beta/alloydb/instances/delete b/gcloud/beta/alloydb/instances/delete new file mode 100644 index 000000000..0f313e873 --- /dev/null +++ b/gcloud/beta/alloydb/instances/delete @@ -0,0 +1,48 @@ +NAME + gcloud beta alloydb instances delete - deletes an AlloyDB instance within a + given cluster + +SYNOPSIS + gcloud beta alloydb instances delete INSTANCE --cluster=CLUSTER + --region=REGION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes an AlloyDB instance within a given cluster. + +EXAMPLES + To delete an instance, run: + + $ gcloud beta alloydb instances delete my-instance \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + INSTANCE + AlloyDB instance ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb instances delete + diff --git a/gcloud/beta/alloydb/instances/describe b/gcloud/beta/alloydb/instances/describe new file mode 100644 index 000000000..7f286b97e --- /dev/null +++ b/gcloud/beta/alloydb/instances/describe @@ -0,0 +1,43 @@ +NAME + gcloud beta alloydb instances describe - describes an AlloyDB instance + within a given cluster + +SYNOPSIS + gcloud beta alloydb instances describe INSTANCE --cluster=CLUSTER + --region=REGION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describes an AlloyDB instance within a given cluster. + +EXAMPLES + To describe an instance, run: + + $ gcloud beta alloydb instances describe my-instance \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + INSTANCE + AlloyDB instance ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb instances describe + diff --git a/gcloud/beta/alloydb/instances/failover b/gcloud/beta/alloydb/instances/failover new file mode 100644 index 000000000..54e816d82 --- /dev/null +++ b/gcloud/beta/alloydb/instances/failover @@ -0,0 +1,48 @@ +NAME + gcloud beta alloydb instances failover - failover an AlloyDB instance + within a given cluster + +SYNOPSIS + gcloud beta alloydb instances failover INSTANCE --cluster=CLUSTER + --region=REGION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Failover an AlloyDB instance within a given cluster. + +EXAMPLES + To failover an instance, run: + + $ gcloud beta alloydb instances failover my-instance \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + INSTANCE + AlloyDB instance ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb instances failover + diff --git a/gcloud/beta/alloydb/instances/help b/gcloud/beta/alloydb/instances/help new file mode 100644 index 000000000..d7f5ce672 --- /dev/null +++ b/gcloud/beta/alloydb/instances/help @@ -0,0 +1,46 @@ +NAME + gcloud beta alloydb instances - provide commands for managing AlloyDB + instances + +SYNOPSIS + gcloud beta alloydb instances COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Provide commands for managing AlloyDB clusters including creating, + configuring, restarting, and deleting instances. + +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) Creates a new AlloyDB instance within a given cluster. + + delete + (BETA) Deletes an AlloyDB instance within a given cluster. + + describe + (BETA) Describes an AlloyDB instance within a given cluster. + + failover + (BETA) Failover an AlloyDB instance within a given cluster. + + list + (BETA) Lists AlloyDB instances in a given cluster. + + restart + (BETA) Restarts an AlloyDB instance within a given cluster. + + update + (BETA) Updates an AlloyDB instance within a given cluster. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb instances + diff --git a/gcloud/beta/alloydb/instances/list b/gcloud/beta/alloydb/instances/list new file mode 100644 index 000000000..5a9f02104 --- /dev/null +++ b/gcloud/beta/alloydb/instances/list @@ -0,0 +1,82 @@ +NAME + gcloud beta alloydb instances list - lists AlloyDB instances in a given + cluster + +SYNOPSIS + gcloud beta alloydb instances list [--cluster=CLUSTER --region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Lists AlloyDB instances in a given cluster. + +EXAMPLES + To list instances, run: + + $ gcloud beta alloydb instances list --cluster=my-cluster \ + --region=us-central1 + +FLAGS + Cluster + + --cluster=CLUSTER + AlloyDB cluster ID + + This flag must be specified if any of the other arguments in this + group are specified. + + --region=REGION + Regional location (e.g. asia-east1, us-east1) of CLUSTER. See the + full list of regions at + https://cloud.google.com/sql/docs/instance-locations. Default: list + clusters in all regions. + + This flag must be specified if any of the other arguments in this + group are specified. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb instances list + diff --git a/gcloud/beta/alloydb/instances/restart b/gcloud/beta/alloydb/instances/restart new file mode 100644 index 000000000..aa78774e3 --- /dev/null +++ b/gcloud/beta/alloydb/instances/restart @@ -0,0 +1,48 @@ +NAME + gcloud beta alloydb instances restart - restarts an AlloyDB instance within + a given cluster + +SYNOPSIS + gcloud beta alloydb instances restart INSTANCE --cluster=CLUSTER + --region=REGION [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Restarts an AlloyDB instance within a given cluster. + +EXAMPLES + To describe an instance, run: + + $ gcloud beta alloydb instances restart my-instance \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + INSTANCE + AlloyDB instance ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb instances restart + diff --git a/gcloud/beta/alloydb/instances/update b/gcloud/beta/alloydb/instances/update new file mode 100644 index 000000000..b81e35e13 --- /dev/null +++ b/gcloud/beta/alloydb/instances/update @@ -0,0 +1,81 @@ +NAME + gcloud beta alloydb instances update - updates an AlloyDB instance within a + given cluster + +SYNOPSIS + gcloud beta alloydb instances update INSTANCE --cluster=CLUSTER + --region=REGION [--async] [--availability-type=AVAILABILITY_TYPE] + [--cpu-count=CPU_COUNT] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] + [--read-pool-node-count=READ_POOL_NODE_COUNT] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates an AlloyDB instance within a given cluster. + +EXAMPLES + To update the number of nodes in the read pool, run: + + $ gcloud beta alloydb instances update my-read-instance \ + --cluster=my-cluster --region=us-central1 \ + --read-pool-node-count=3 + +POSITIONAL ARGUMENTS + INSTANCE + AlloyDB instance ID + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --availability-type=AVAILABILITY_TYPE + Specifies level of availability. AVAILABILITY_TYPE must be (currently + only one value is supported): + + REGIONAL + Provides high availability and is recommended for production + instances; instance automatically fails over to another zone within + your selected region. + + --cpu-count=CPU_COUNT + Whole number value indicating how many vCPUs the machine should + contain. Each vCPU count corresponds to a N2 high-mem machine: + (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). + CPU_COUNT must be one of: 4, 8, 16, 32, 64. + + --database-flags=FLAG=VALUE,[FLAG=VALUE,...] + Comma-separated list of database flags to set on the instance. Use an + equals sign to separate flag name and value. Flags without values, like + skip_grant_tables, can be written out without a value after, e.g., + skip_grant_tables=. Use on/off for booleans. View the Instance Resource + API for allowed flags. (e.g., --database-flags + max_allowed_packet=55555,skip_grant_tables=,log_output=1) + + --read-pool-node-count=READ_POOL_NODE_COUNT + Read capacity, i.e. number of nodes in a read pool instance. + + --zone=ZONE + Primary Compute Engine zone (e.g. us-central1, us-central1, etc. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb instances update + diff --git a/gcloud/beta/alloydb/operations/cancel b/gcloud/beta/alloydb/operations/cancel new file mode 100644 index 000000000..653247b33 --- /dev/null +++ b/gcloud/beta/alloydb/operations/cancel @@ -0,0 +1,39 @@ +NAME + gcloud beta alloydb operations cancel - cancels an AlloyDB operation + +SYNOPSIS + gcloud beta alloydb operations cancel OPERATION --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Cancels an AlloyDB operation. + +EXAMPLES + To cancel an operation, run: + + $ gcloud beta alloydb operations cancel operation-123456789 \ + --region=us-central1 + +POSITIONAL ARGUMENTS + OPERATION + AlloyDB operation ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb operations cancel + diff --git a/gcloud/beta/alloydb/operations/delete b/gcloud/beta/alloydb/operations/delete new file mode 100644 index 000000000..2cd73ae11 --- /dev/null +++ b/gcloud/beta/alloydb/operations/delete @@ -0,0 +1,39 @@ +NAME + gcloud beta alloydb operations delete - deletes an AlloyDB operation + +SYNOPSIS + gcloud beta alloydb operations delete OPERATION --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes an AlloyDB operation. + +EXAMPLES + To delete an operation, run: + + $ gcloud beta alloydb operations delete operation-123456789 \ + --region=us-central1 + +POSITIONAL ARGUMENTS + OPERATION + AlloyDB operation ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb operations delete + diff --git a/gcloud/beta/alloydb/operations/describe b/gcloud/beta/alloydb/operations/describe new file mode 100644 index 000000000..080885b61 --- /dev/null +++ b/gcloud/beta/alloydb/operations/describe @@ -0,0 +1,39 @@ +NAME + gcloud beta alloydb operations describe - describe an AlloyDB operation + +SYNOPSIS + gcloud beta alloydb operations describe OPERATION --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an AlloyDB operation. + +EXAMPLES + To describe an operation, run: + + $ gcloud beta alloydb operations describe operation-123456789 \ + --region=us-central1 + +POSITIONAL ARGUMENTS + OPERATION + AlloyDB operation ID + +REQUIRED FLAGS + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb operations describe + diff --git a/gcloud/beta/alloydb/operations/help b/gcloud/beta/alloydb/operations/help new file mode 100644 index 000000000..d0be562c6 --- /dev/null +++ b/gcloud/beta/alloydb/operations/help @@ -0,0 +1,37 @@ +NAME + gcloud beta alloydb operations - provide commands for managing AlloyDB + operations + +SYNOPSIS + gcloud beta alloydb operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Provide commands for managing AlloyDB operations including + cancelling, deleting, describing, and listing. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (BETA) Cancels an AlloyDB operation. + + delete + (BETA) Deletes an AlloyDB operation. + + describe + (BETA) Describe an AlloyDB operation. + + list + (BETA) Lists AlloyDB operations. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb operations + diff --git a/gcloud/beta/alloydb/operations/list b/gcloud/beta/alloydb/operations/list new file mode 100644 index 000000000..53c480edd --- /dev/null +++ b/gcloud/beta/alloydb/operations/list @@ -0,0 +1,68 @@ +NAME + gcloud beta alloydb operations list - lists AlloyDB operations + +SYNOPSIS + gcloud beta alloydb operations list [--region=REGION; default="-"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Lists AlloyDB operations. + +EXAMPLES + To list operations, run: + + $ gcloud beta alloydb operations list --region=us-central1 + +FLAGS + --region=REGION; default="-" + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + Default: list operations in all regions. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha alloydb operations list + diff --git a/gcloud/beta/app/deploy b/gcloud/beta/app/deploy index bdd8b843a..02cd7398a 100644 --- a/gcloud/beta/app/deploy +++ b/gcloud/beta/app/deploy @@ -68,6 +68,11 @@ EXAMPLES $ gcloud config set app/promote_by_default false + To deploy a service that will run as a service account, run: + + $ gcloud beta app deploy ~/my_app/app.yaml \ + --service-account=SERVICE_ACCOUNT + POSITIONAL ARGUMENTS [DEPLOYABLES ...] The yaml files for the services or configurations you want to deploy. diff --git a/gcloud/beta/bigtable/instances/tables/restore b/gcloud/beta/bigtable/instances/tables/restore index dd1494672..808e79583 100644 --- a/gcloud/beta/bigtable/instances/tables/restore +++ b/gcloud/beta/bigtable/instances/tables/restore @@ -31,8 +31,8 @@ EXAMPLES table2 REQUIRED FLAGS - Table resource - The destination to copy to. The arguments in this group - can be used to specify the attributes of this resource. (NOTE) Some + Table resource - The destination to restore to. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --destination on the command line with a fully @@ -58,10 +58,10 @@ REQUIRED FLAGS ▸ provide the argument --destination-instance on the command line; ▸ provide the argument --source-instance on the command line. - Backup resource - The source to copy from. 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: + Backup resource - The source to restore from. 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 --source on the command line with a fully specified name; ◆ provide the argument --project on the command line; @@ -71,7 +71,7 @@ REQUIRED FLAGS --source=SOURCE ID of the backup or fully qualified identifier for the backup. To set - the backup attribute: + the source attribute: ▸ provide the argument --source on the command line. This flag must be specified if any of the other arguments in this diff --git a/gcloud/beta/builds/triggers/create/github b/gcloud/beta/builds/triggers/create/github index fe64f17d7..6dde47102 100644 --- a/gcloud/beta/builds/triggers/create/github +++ b/gcloud/beta/builds/triggers/create/github @@ -12,7 +12,8 @@ SYNOPSIS | --dockerfile=DOCKERFILE --dockerfile-dir=DOCKERFILE_DIR; default="/" --dockerfile-image=DOCKERFILE_IMAGE) : --description=DESCRIPTION --ignored-files=[GLOB,...] - --included-files=[GLOB,...] --name=NAME --require-approval + --include-logs-with-status --included-files=[GLOB,...] --name=NAME + --require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -67,6 +68,10 @@ REQUIRED FLAGS Glob filter. Changes only affecting ignored files won't trigger builds. + --include-logs-with-status + Build logs will be sent back to GitHub as part of the checkrun + result. + --included-files=[GLOB,...] Glob filter. Changes affecting at least one included file will trigger builds. diff --git a/gcloud/beta/compute/backend-services/add-service-bindings b/gcloud/beta/compute/backend-services/add-service-bindings index 3bb74fb14..21927c92a 100644 --- a/gcloud/beta/compute/backend-services/add-service-bindings +++ b/gcloud/beta/compute/backend-services/add-service-bindings @@ -43,8 +43,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute backend-services add-service-bindings $ gcloud alpha compute backend-services add-service-bindings diff --git a/gcloud/beta/compute/backend-services/remove-service-bindings b/gcloud/beta/compute/backend-services/remove-service-bindings index a8a85cd30..60a8bf4b5 100644 --- a/gcloud/beta/compute/backend-services/remove-service-bindings +++ b/gcloud/beta/compute/backend-services/remove-service-bindings @@ -43,8 +43,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute backend-services remove-service-bindings $ gcloud alpha compute backend-services remove-service-bindings diff --git a/gcloud/beta/compute/forwarding-rules/create b/gcloud/beta/compute/forwarding-rules/create index 5742c1a17..1be8d276a 100644 --- a/gcloud/beta/compute/forwarding-rules/create +++ b/gcloud/beta/compute/forwarding-rules/create @@ -14,8 +14,8 @@ SYNOPSIS | --target-ssl-proxy=TARGET_SSL_PROXY | --target-tcp-proxy=TARGET_TCP_PROXY | --target-vpn-gateway=TARGET_VPN_GATEWAY) [--allow-global-access] - [--description=DESCRIPTION] [--ip-protocol=IP_PROTOCOL] - [--is-mirroring-collector] + [--description=DESCRIPTION] [--disable-automate-dns-zone] + [--ip-protocol=IP_PROTOCOL] [--is-mirroring-collector] [--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--network=NETWORK] [--network-tier=NETWORK_TIER] [--service-directory-registration=SERVICE_DIRECTORY_REGISTRATION] @@ -174,6 +174,13 @@ OPTIONAL FLAGS --description=DESCRIPTION Optional textual description for the forwarding rule. + --disable-automate-dns-zone + If specified, then a DNS zone will not be auto-generated for this + Private Service Connect forwarding rule. This can only be specified if + the forwarding rule's target is a service attachment + (--target-service-attachment=SERVICE_ATTACHMENT) or Google APIs bundle + (--target-google-apis-bundle=API_BUNDLE) + --ip-protocol=IP_PROTOCOL IP protocol that the rule will serve. The default is TCP. diff --git a/gcloud/beta/compute/images/import b/gcloud/beta/compute/images/import index 368c01081..f4b6d5015 100644 --- a/gcloud/beta/compute/images/import +++ b/gcloud/beta/compute/images/import @@ -261,8 +261,8 @@ OPTIONAL FLAGS windows-10-x86-byol, windows-2008r2, windows-2008r2-byol, windows-2012, windows-2012-byol, windows-2012r2, windows-2012r2-byol, windows-2016, windows-2016-byol, windows-2019, windows-2019-byol, - windows-7-x64-byol, windows-7-x86-byol, windows-8-x64-byol, - windows-8-x86-byol. + windows-2022, windows-2022-byol, windows-7-x64-byol, + windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index d9622098c..781a71995 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -27,6 +27,7 @@ SYNOPSIS [--min-count=MIN_COUNT] [--min-cpu-platform=PLATFORM] [--min-node-cpu=MIN_NODE_CPU] [--network=NETWORK] [--network-interface=[PROPERTY=VALUE,...]] + [--network-performance-configs=[PROPERTY=VALUE,...]] [--network-tier=NETWORK_TIER] [--post-key-revocation-action-type=POLICY] [--preemptible] [--provisioning-model=PROVISIONING_MODEL] @@ -536,6 +537,17 @@ OPTIONAL FLAGS Specifies the Network Interface Controller (NIC) type for the interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + --network-performance-configs=[PROPERTY=VALUE,...] + Configures network performance settings for the instance. If this flag + is not specified, the instance will be created with its default network + performance configuration. + + total-egress-bandwidth-tier + Total egress bandwidth is the available outbound bandwidth from a + VM, regardless of whether the traffic is going to internal IP or + external IP destinations. The following tier values are allowed: + [DEFAULT,TIER_1] + --network-tier=NETWORK_TIER Specifies the network tier that will be used to configure the instance. NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. The diff --git a/gcloud/beta/compute/instances/import b/gcloud/beta/compute/instances/import index 26a6d10ba..1d0ffb88a 100644 --- a/gcloud/beta/compute/instances/import +++ b/gcloud/beta/compute/instances/import @@ -172,8 +172,9 @@ OPTIONAL FLAGS ubuntu-1604, ubuntu-1804, ubuntu-2004, windows-10-x64-byol, windows-10-x86-byol, windows-2008r2, windows-2008r2-byol, windows-2012, windows-2012-byol, windows-2012r2, windows-2012r2-byol, windows-2016, - windows-2016-byol, windows-2019, windows-2019-byol, windows-7-x64-byol, - windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol. + windows-2016-byol, windows-2019, windows-2019-byol, windows-2022, + windows-2022-byol, windows-7-x64-byol, windows-7-x86-byol, + windows-8-x64-byol, windows-8-x86-byol. --private-network-ip=PRIVATE_NETWORK_IP Specifies the RFC1918 IP to assign to the instance. The IP should be in diff --git a/gcloud/beta/compute/machine-images/import b/gcloud/beta/compute/machine-images/import index bea78ebf8..4affe5ea6 100644 --- a/gcloud/beta/compute/machine-images/import +++ b/gcloud/beta/compute/machine-images/import @@ -165,8 +165,9 @@ OPTIONAL FLAGS ubuntu-1604, ubuntu-1804, ubuntu-2004, windows-10-x64-byol, windows-10-x86-byol, windows-2008r2, windows-2008r2-byol, windows-2012, windows-2012-byol, windows-2012r2, windows-2012r2-byol, windows-2016, - windows-2016-byol, windows-2019, windows-2019-byol, windows-7-x64-byol, - windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol. + windows-2016-byol, windows-2019, windows-2019-byol, windows-2022, + windows-2022-byol, windows-7-x64-byol, windows-7-x86-byol, + windows-8-x64-byol, windows-8-x86-byol. --restart-on-failure The VMs created from the imported machine image are restarted if they diff --git a/gcloud/beta/compute/networks/peerings/create b/gcloud/beta/compute/networks/peerings/create index 11c79c954..e70c9d50d 100644 --- a/gcloud/beta/compute/networks/peerings/create +++ b/gcloud/beta/compute/networks/peerings/create @@ -7,7 +7,8 @@ SYNOPSIS --peer-network=PEER_NETWORK [--async] [--auto-create-routes] [--export-custom-routes] [--export-subnet-routes-with-public-ip] [--import-custom-routes] [--import-subnet-routes-with-public-ip] - [--peer-project=PEER_PROJECT] [GCLOUD_WIDE_FLAG ...] + [--peer-project=PEER_PROJECT] [--stack-type=STACK_TYPE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute networks peerings create is used to create @@ -73,6 +74,19 @@ OPTIONAL FLAGS The name of the project for the peer network. If not specified, defaults to current project. + --stack-type=STACK_TYPE + Stack type of the peering. If not specified, defaults to IPV4_ONLY. + + STACK_TYPE must be one of: + + IPV4_ONLY + Only IPv4 traffic and routes will be exchanged across this peering. + + IPV4_IPV6 + IPv4 traffic and routes will be exchanged across this peering. + IPv6 traffic and routes will be exchanged if the matching peering + configuration also has stack_type set to IPV4_IPV6. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/networks/peerings/update b/gcloud/beta/compute/networks/peerings/update index d02016a5e..2e3b02343 100644 --- a/gcloud/beta/compute/networks/peerings/update +++ b/gcloud/beta/compute/networks/peerings/update @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta compute networks peerings update NAME --network=NETWORK [--export-custom-routes] [--export-subnet-routes-with-public-ip] [--import-custom-routes] [--import-subnet-routes-with-public-ip] - [GCLOUD_WIDE_FLAG ...] + [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...] EXAMPLES To update the peering named peering-name to both export and import custom @@ -50,6 +50,19 @@ OPTIONAL FLAGS public IP ranges from peer network. Use --no-import-subnet-routes-with-public-ip to disable it. + --stack-type=STACK_TYPE + Stack type of the peering. If not specified, defaults to IPV4_ONLY. + + STACK_TYPE must be one of: + + IPV4_ONLY + Only IPv4 traffic and routes will be exchanged across this peering. + + IPV4_IPV6 + IPv4 traffic and routes will be exchanged across this peering. + IPv6 traffic and routes will be exchanged if the matching peering + configuration also has stack_type set to IPV4_IPV6. + 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/config/get b/gcloud/beta/config/get index e27ab04ad..2fb99745c 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -487,7 +487,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -510,8 +510,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 5f90ef711..482a0de27 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -519,7 +519,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -542,8 +542,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 6bc6208ed..38fc4f3b1 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -521,7 +521,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -544,8 +544,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index e352c0c25..f3a8bcd34 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -534,7 +534,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -557,8 +557,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 6f4f54c3e..413f378ce 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -495,7 +495,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -518,8 +518,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/beta/container/fleet/identity-service/apply b/gcloud/beta/container/fleet/identity-service/apply index 600898176..bab2d1f75 100644 --- a/gcloud/beta/container/fleet/identity-service/apply +++ b/gcloud/beta/container/fleet/identity-service/apply @@ -38,8 +38,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet identity-service apply $ gcloud alpha container fleet identity-service apply diff --git a/gcloud/beta/container/fleet/identity-service/delete b/gcloud/beta/container/fleet/identity-service/delete index 299787396..ccc18cfcd 100644 --- a/gcloud/beta/container/fleet/identity-service/delete +++ b/gcloud/beta/container/fleet/identity-service/delete @@ -28,8 +28,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet identity-service delete $ gcloud alpha container fleet identity-service delete diff --git a/gcloud/beta/container/fleet/identity-service/describe b/gcloud/beta/container/fleet/identity-service/describe index 1af3b70b0..2877fe4b4 100644 --- a/gcloud/beta/container/fleet/identity-service/describe +++ b/gcloud/beta/container/fleet/identity-service/describe @@ -57,8 +57,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet identity-service describe $ gcloud alpha container fleet identity-service describe diff --git a/gcloud/beta/container/fleet/identity-service/disable b/gcloud/beta/container/fleet/identity-service/disable index db1f55131..98b1d7a3a 100644 --- a/gcloud/beta/container/fleet/identity-service/disable +++ b/gcloud/beta/container/fleet/identity-service/disable @@ -28,8 +28,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet identity-service disable $ gcloud alpha container fleet identity-service disable diff --git a/gcloud/beta/container/fleet/identity-service/enable b/gcloud/beta/container/fleet/identity-service/enable index 80fcc80fa..cab5a3052 100644 --- a/gcloud/beta/container/fleet/identity-service/enable +++ b/gcloud/beta/container/fleet/identity-service/enable @@ -22,8 +22,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet identity-service enable $ gcloud alpha container fleet identity-service enable diff --git a/gcloud/beta/container/fleet/identity-service/help b/gcloud/beta/container/fleet/identity-service/help index 65e76c008..d2f08bcc2 100644 --- a/gcloud/beta/container/fleet/identity-service/help +++ b/gcloud/beta/container/fleet/identity-service/help @@ -34,8 +34,10 @@ COMMANDS (BETA) Enable Identity Service Feature. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet identity-service $ gcloud alpha container fleet identity-service diff --git a/gcloud/beta/container/hub/identity-service/apply b/gcloud/beta/container/hub/identity-service/apply index 9d591e838..1f64cfcd4 100644 --- a/gcloud/beta/container/hub/identity-service/apply +++ b/gcloud/beta/container/hub/identity-service/apply @@ -38,8 +38,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub identity-service apply $ gcloud alpha container hub identity-service apply diff --git a/gcloud/beta/container/hub/identity-service/delete b/gcloud/beta/container/hub/identity-service/delete index 186a268b5..a3eb03bf9 100644 --- a/gcloud/beta/container/hub/identity-service/delete +++ b/gcloud/beta/container/hub/identity-service/delete @@ -28,8 +28,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub identity-service delete $ gcloud alpha container hub identity-service delete diff --git a/gcloud/beta/container/hub/identity-service/describe b/gcloud/beta/container/hub/identity-service/describe index 8437e8d52..ed360fe94 100644 --- a/gcloud/beta/container/hub/identity-service/describe +++ b/gcloud/beta/container/hub/identity-service/describe @@ -57,8 +57,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub identity-service describe $ gcloud alpha container hub identity-service describe diff --git a/gcloud/beta/container/hub/identity-service/disable b/gcloud/beta/container/hub/identity-service/disable index cdcfa23cf..015dbb169 100644 --- a/gcloud/beta/container/hub/identity-service/disable +++ b/gcloud/beta/container/hub/identity-service/disable @@ -28,8 +28,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub identity-service disable $ gcloud alpha container hub identity-service disable diff --git a/gcloud/beta/container/hub/identity-service/enable b/gcloud/beta/container/hub/identity-service/enable index 1ed44cdea..b15d52ade 100644 --- a/gcloud/beta/container/hub/identity-service/enable +++ b/gcloud/beta/container/hub/identity-service/enable @@ -22,8 +22,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub identity-service enable $ gcloud alpha container hub identity-service enable diff --git a/gcloud/beta/container/hub/identity-service/help b/gcloud/beta/container/hub/identity-service/help index 14e983fa0..f70c5f520 100644 --- a/gcloud/beta/container/hub/identity-service/help +++ b/gcloud/beta/container/hub/identity-service/help @@ -34,8 +34,10 @@ COMMANDS (BETA) Enable Identity Service Feature. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container hub identity-service $ gcloud alpha container hub identity-service diff --git a/gcloud/beta/dns/record-sets/create b/gcloud/beta/dns/record-sets/create index 3a0d688cf..56507070a 100644 --- a/gcloud/beta/dns/record-sets/create +++ b/gcloud/beta/dns/record-sets/create @@ -19,6 +19,15 @@ EXAMPLES $ gcloud beta dns record-sets create foo.bar.com. \ --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone + To create a geo routed record-set with dnsName foo.bar.com., record type A, + routing_policy_data "us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5.6,9.8.7.6" + and ttl 60 in my_zone. + + $ gcloud beta dns record-sets create foo.bar.com. \ + --routing_policy_data="us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5\ + .6,9.8.7.6" --routing_policy_type=GEO --type=A --ttl=60 \ + --zone=my_zone --location=us-east1-a + To create a record-set with dnsName foo.bar.com., record type A, rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone in us-east1-a run this: diff --git a/gcloud/beta/iam/policies/create b/gcloud/beta/iam/policies/create index 996d3cff6..6886c4448 100644 --- a/gcloud/beta/iam/policies/create +++ b/gcloud/beta/iam/policies/create @@ -21,17 +21,20 @@ EXAMPLES POSITIONAL ARGUMENTS POLICY_ID - Id of the policy. + Policy ID that is unique for the resource to which the policy is + attached. REQUIRED FLAGS --attachment-point=ATTACHMENT_POINT - Resource to which the policy is attached. + Resource to which the policy is attached. For valid formats, see + https://cloud.google.com/iam/help/deny/attachment-point. --kind=KIND - Kind of the policy. + Policy type. Use denypolicies for deny policies. --policy-file=POLICY_FILE - Contents of the policy. + Path to the file that contains the policy, in JSON or YAML format. For + valid syntax, see https://cloud.google.com/iam/help/deny/policy-syntax. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/iam/policies/delete b/gcloud/beta/iam/policies/delete index 65d4ed5f8..b7c76492d 100644 --- a/gcloud/beta/iam/policies/delete +++ b/gcloud/beta/iam/policies/delete @@ -18,23 +18,23 @@ EXAMPLES --attachment-point=cloudresourcemanager.googleapis.com/\ projects/123 --kind=denypolicies --etag=abc - If etag isn't provided, the command will try to get the etag using the - calling user permissions. - POSITIONAL ARGUMENTS POLICY_ID - Id of the policy. + Policy ID that is unique for the resource to which the policy is + attached. REQUIRED FLAGS --attachment-point=ATTACHMENT_POINT - Resource to which the policy is attached. + Resource to which the policy is attached. For valid formats, see + https://cloud.google.com/iam/help/deny/attachment-point. --kind=KIND - Kind of the policy. + Policy type. Use denypolicies for deny policies. OPTIONAL FLAGS --etag=ETAG - Etag of the existing policy. + Etag that identifies the version of the existing policy. If omitted, + the command gets the etag for the current version of the policy. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/iam/policies/get b/gcloud/beta/iam/policies/get index 3ee786e0c..5d388694e 100644 --- a/gcloud/beta/iam/policies/get +++ b/gcloud/beta/iam/policies/get @@ -19,14 +19,16 @@ EXAMPLES POSITIONAL ARGUMENTS POLICY_ID - Id of the policy. + Policy ID that is unique for the resource to which the policy is + attached. REQUIRED FLAGS --attachment-point=ATTACHMENT_POINT - Resource to which the policy is attached. + Resource to which the policy is attached. For valid formats, see + https://cloud.google.com/iam/help/deny/attachment-point. --kind=KIND - Kind of the policy. + Policy type. Use denypolicies for deny policies. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/iam/policies/list b/gcloud/beta/iam/policies/list index 62057d076..db703cbfc 100644 --- a/gcloud/beta/iam/policies/list +++ b/gcloud/beta/iam/policies/list @@ -21,14 +21,16 @@ EXAMPLES REQUIRED FLAGS --attachment-point=ATTACHMENT_POINT - Resource to which the policy is attached. + Resource to which the policy is attached. For valid formats, see + https://cloud.google.com/iam/help/deny/attachment-point. --kind=KIND - Kind of the policy. + Policy type. Use denypolicies for deny policies. FLAGS --page_token=PAGE_TOKEN - Page token received from a previous call. + Page token received from a previous call. Provide this token to + retrieve the next page. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/iam/policies/update b/gcloud/beta/iam/policies/update index 53c56f12c..ad48e7f0e 100644 --- a/gcloud/beta/iam/policies/update +++ b/gcloud/beta/iam/policies/update @@ -19,26 +19,27 @@ EXAMPLES projects/123 --kind=denypolicies --policy-file=policy.json \ --etag=abc - If etag isn't provided, the command will try to get the etag using the - calling user permissions. - POSITIONAL ARGUMENTS POLICY_ID - Id of the policy. + Policy ID that is unique for the resource to which the policy is + attached. REQUIRED FLAGS --attachment-point=ATTACHMENT_POINT - Resource to which the policy is attached. + Resource to which the policy is attached. For valid formats, see + https://cloud.google.com/iam/help/deny/attachment-point. --kind=KIND - Kind of the policy. + Policy type. Use denypolicies for deny policies. --policy-file=POLICY_FILE - Contents of the policy. + Path to the file that contains the policy, in JSON or YAML format. For + valid syntax, see https://cloud.google.com/iam/help/deny/policy-syntax. OPTIONAL FLAGS --etag=ETAG - Etag of the existing policy. + Etag that identifies the version of the existing policy. If omitted, + the command gets the etag for the current version of the policy. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/memcache/instances/create b/gcloud/beta/memcache/instances/create index 955b3bc2d..737c13ca2 100644 --- a/gcloud/beta/memcache/instances/create +++ b/gcloud/beta/memcache/instances/create @@ -96,7 +96,7 @@ OPTIONAL FLAGS sunday, thursday, tuesday, wednesday. --maintenance-window-duration=MAINTENANCE_WINDOW_DURATION - Duration of the maintenance window in integer hours, e.g 4. + Duration in integer hours (3 to 8) of the maintenance window. --maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME Hour of day (0 to 23) for the start of maintenance window, in UTC time diff --git a/gcloud/beta/memcache/instances/reschedule-maintenance b/gcloud/beta/memcache/instances/reschedule-maintenance index ac8fee405..c91605fb1 100644 --- a/gcloud/beta/memcache/instances/reschedule-maintenance +++ b/gcloud/beta/memcache/instances/reschedule-maintenance @@ -83,8 +83,10 @@ API REFERENCE API can be found at: https://cloud.google.com/memorystore/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud memcache instances reschedule-maintenance $ gcloud alpha memcache instances reschedule-maintenance diff --git a/gcloud/beta/memcache/instances/update b/gcloud/beta/memcache/instances/update index 17c9ca663..6514f00a6 100644 --- a/gcloud/beta/memcache/instances/update +++ b/gcloud/beta/memcache/instances/update @@ -158,7 +158,7 @@ REQUIRED FLAGS sunday, thursday, tuesday, wednesday. --maintenance-window-duration=MAINTENANCE_WINDOW_DURATION - Duration of the maintenance window in integer hours, e.g '4'. + Duration in integer hours (3 to 8) of the maintenance window. --maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME Hour of day (0 to 23) for the start of maintenance window, in UTC diff --git a/gcloud/beta/pubsub/subscriptions/create b/gcloud/beta/pubsub/subscriptions/create index 91e486f62..c00b7df1b 100644 --- a/gcloud/beta/pubsub/subscriptions/create +++ b/gcloud/beta/pubsub/subscriptions/create @@ -71,12 +71,12 @@ OPTIONAL FLAGS acknowledge receiving a message before re-attempting delivery. --enable-exactly-once-delivery - Whether or not to enble exactly once delivery on the subscription. If + Whether or not to enable exactly-once delivery on the subscription. If true, Pub/Sub provides the following guarantees for the delivery of a message with a given value of message_id on this subscription: The message sent to a subscriber is guaranteed not to be resent before the - message's acknowledgement deadline expires. An acknowledged message - will not be resent to a subscriber. + message's acknowledgment deadline expires. An acknowledged message will + not be resent to a subscriber. --enable-message-ordering Whether to receive messages with the same ordering key in order. If diff --git a/gcloud/beta/pubsub/subscriptions/update b/gcloud/beta/pubsub/subscriptions/update index d1a34ff01..35f7c35b1 100644 --- a/gcloud/beta/pubsub/subscriptions/update +++ b/gcloud/beta/pubsub/subscriptions/update @@ -45,12 +45,13 @@ FLAGS acknowledge receiving a message before re-attempting delivery. --enable-exactly-once-delivery - Whether or not to enble exactly once delivery on the subscription. If + Whether or not to enable exactly-once delivery on the subscription. If true, Pub/Sub provides the following guarantees for the delivery of a message with a given value of message_id on this subscription: The message sent to a subscriber is guaranteed not to be resent before the - message's acknowledgement deadline expires. An acknowledged message - will not be resent to a subscriber. + message's acknowledgment deadline expires. An acknowledged message will + not be resent to a subscriber. To disable exactly-once delivery use + --no-enable-exactly-once-delivery. --expiration-period=EXPIRATION_PERIOD The subscription will expire if it is inactive for the given period. diff --git a/gcloud/beta/redis/instances/create b/gcloud/beta/redis/instances/create index df3fef374..947e49180 100644 --- a/gcloud/beta/redis/instances/create +++ b/gcloud/beta/redis/instances/create @@ -4,8 +4,10 @@ NAME SYNOPSIS gcloud beta redis instances create (INSTANCE : --region=REGION) [--alternative-zone=ALTERNATIVE_ZONE] [--async] - [--connect-mode=CONNECT_MODE] [--display-name=DISPLAY_NAME] - [--enable-auth] [--labels=[KEY=VALUE,...]] + [--connect-mode=CONNECT_MODE] + [--customer-managed-key=CUSTOMER_MANAGED_KEY] + [--display-name=DISPLAY_NAME] [--enable-auth] + [--labels=[KEY=VALUE,...]] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [--network=NETWORK; default="default"] @@ -79,6 +81,10 @@ FLAGS Network connection mode used by instances. CONNECT_MODE must be one of: connect-mode-unspecified, direct-peering, private-service-access. + --customer-managed-key=CUSTOMER_MANAGED_KEY + The KMS key reference that you want to use to encrypt the data at rest + for this Redis instance. If this is provided, CMEK is enabled. + --display-name=DISPLAY_NAME A human-readable name for the instance. diff --git a/gcloud/bigtable/instances/tables/restore b/gcloud/bigtable/instances/tables/restore index dcd76002c..c9e78bb29 100644 --- a/gcloud/bigtable/instances/tables/restore +++ b/gcloud/bigtable/instances/tables/restore @@ -31,8 +31,8 @@ EXAMPLES table2 REQUIRED FLAGS - Table resource - The destination to copy to. The arguments in this group - can be used to specify the attributes of this resource. (NOTE) Some + Table resource - The destination to restore to. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument --destination on the command line with a fully @@ -58,10 +58,10 @@ REQUIRED FLAGS ▸ provide the argument --destination-instance on the command line; ▸ provide the argument --source-instance on the command line. - Backup resource - The source to copy from. 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: + Backup resource - The source to restore from. 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 --source on the command line with a fully specified name; ◆ provide the argument --project on the command line; @@ -71,7 +71,7 @@ REQUIRED FLAGS --source=SOURCE ID of the backup or fully qualified identifier for the backup. To set - the backup attribute: + the source attribute: ▸ provide the argument --source on the command line. This flag must be specified if any of the other arguments in this diff --git a/gcloud/compute/backend-services/add-service-bindings b/gcloud/compute/backend-services/add-service-bindings new file mode 100644 index 000000000..5888c6211 --- /dev/null +++ b/gcloud/compute/backend-services/add-service-bindings @@ -0,0 +1,51 @@ +NAME + gcloud compute backend-services add-service-bindings - add service bindings + to a backend service + +SYNOPSIS + gcloud compute backend-services add-service-bindings BACKEND_SERVICE_NAME + --service-bindings=SERVICE_BINDING,[...] [--global | --region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add service bindings to a backend service. + +EXAMPLES + To add a service binding to a backend service, run: + + $ gcloud compute backend-services add-service-bindings NAME \ + --service-bindings=SERVICE_BINDING1 --global + +POSITIONAL ARGUMENTS + BACKEND_SERVICE_NAME + Name of the backend service to operate on. + +REQUIRED FLAGS + --service-bindings=SERVICE_BINDING,[...] + List of service binding names to be added to the backend service. + +OPTIONAL FLAGS + At most one of these can be specified: + + --global + If set, the backend service is global. + + --region=REGION + Region of the backend service to operate on. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute backend-services add-service-bindings + + $ gcloud beta compute backend-services add-service-bindings + diff --git a/gcloud/compute/backend-services/create b/gcloud/compute/backend-services/create index 66f13220a..5ce46d620 100644 --- a/gcloud/compute/backend-services/create +++ b/gcloud/compute/backend-services/create @@ -29,6 +29,7 @@ SYNOPSIS [--[no-]negative-caching] [--negative-caching-policy=[[CODE=TTL],...]] [--network=NETWORK] [--port-name=PORT_NAME] [--protocol=PROTOCOL] [--[no-]request-coalescing] [--serve-while-stale=SERVE_WHILE_STALE] + [--service-bindings=SERVICE_BINDING,[...]] [--session-affinity=SESSION_AFFINITY] [--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE] [--subsetting-policy=SUBSETTING_POLICY; default="NONE"] @@ -477,6 +478,11 @@ FLAGS Set this to zero (0) to disable serve-while-stale. + --service-bindings=SERVICE_BINDING,[...] + List of service bindings to be attached to this backend service. Can + only be set if load balancing scheme is INTERNAL_SELF_MANAGED. If set, + lists of backends and health checks must be both empty. + --session-affinity=SESSION_AFFINITY The type of session affinity to use. Supports both TCP and UDP. SESSION_AFFINITY must be one of: diff --git a/gcloud/compute/backend-services/help b/gcloud/compute/backend-services/help index c19002e7d..26b7b278d 100644 --- a/gcloud/compute/backend-services/help +++ b/gcloud/compute/backend-services/help @@ -27,6 +27,9 @@ COMMANDS add-backend Add a backend to a backend service. + add-service-bindings + Add service bindings to a backend service. + add-signed-url-key Add Cloud CDN Signed URL key to a backend service. @@ -60,6 +63,9 @@ COMMANDS remove-backend Remove a backend from a backend service. + remove-service-bindings + Remove service bindings from a backend service. + update Update a backend service. diff --git a/gcloud/compute/backend-services/remove-service-bindings b/gcloud/compute/backend-services/remove-service-bindings new file mode 100644 index 000000000..e039dbe86 --- /dev/null +++ b/gcloud/compute/backend-services/remove-service-bindings @@ -0,0 +1,51 @@ +NAME + gcloud compute backend-services remove-service-bindings - remove service + bindings from a backend service + +SYNOPSIS + gcloud compute backend-services remove-service-bindings + BACKEND_SERVICE_NAME --service-bindings=SERVICE_BINDING,[...] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove service bindings from a backend service. + +EXAMPLES + To remove a service binding from a backend service, run: + + $ gcloud compute backend-services remove-service-bindings NAME \ + --service-bindings=SERVICE_BINDING1 --global + +POSITIONAL ARGUMENTS + BACKEND_SERVICE_NAME + Name of the backend service to operate on. + +REQUIRED FLAGS + --service-bindings=SERVICE_BINDING,[...] + List of service binding names to be removed from the backend service. + +OPTIONAL FLAGS + At most one of these can be specified: + + --global + If set, the backend service is global. + + --region=REGION + Region of the backend service to operate on. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute backend-services remove-service-bindings + + $ gcloud beta compute backend-services remove-service-bindings + diff --git a/gcloud/compute/backend-services/update b/gcloud/compute/backend-services/update index d2a0e59e7..d0bf51911 100644 --- a/gcloud/compute/backend-services/update +++ b/gcloud/compute/backend-services/update @@ -42,6 +42,7 @@ SYNOPSIS [--[no-]negative-caching | --no-negative-caching-policies | --negative-caching-policy=[[CODE=TTL],...]] [--serve-while-stale=SERVE_WHILE_STALE | --no-serve-while-stale] + [--service-bindings=SERVICE_BINDING,[...] | --no-service-bindings] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -687,6 +688,16 @@ FLAGS --no-serve-while-stale Clears serve while stale value. + At most one of these can be specified: + + --service-bindings=SERVICE_BINDING,[...] + List of service bindings to be attached to this backend service. Can + only be set if load balancing scheme is INTERNAL_SELF_MANAGED. If + set, lists of backends and health checks must be both empty. + + --no-service-bindings + No service bindings should be attached to the backend service. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/compute/forwarding-rules/create b/gcloud/compute/forwarding-rules/create index 79b95b27f..ece678cb3 100644 --- a/gcloud/compute/forwarding-rules/create +++ b/gcloud/compute/forwarding-rules/create @@ -14,8 +14,8 @@ SYNOPSIS | --target-ssl-proxy=TARGET_SSL_PROXY | --target-tcp-proxy=TARGET_TCP_PROXY | --target-vpn-gateway=TARGET_VPN_GATEWAY) [--allow-global-access] - [--description=DESCRIPTION] [--ip-protocol=IP_PROTOCOL] - [--is-mirroring-collector] + [--description=DESCRIPTION] [--disable-automate-dns-zone] + [--ip-protocol=IP_PROTOCOL] [--is-mirroring-collector] [--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--network=NETWORK] [--network-tier=NETWORK_TIER] [--service-directory-registration=SERVICE_DIRECTORY_REGISTRATION] @@ -173,6 +173,13 @@ OPTIONAL FLAGS --description=DESCRIPTION Optional textual description for the forwarding rule. + --disable-automate-dns-zone + If specified, then a DNS zone will not be auto-generated for this + Private Service Connect forwarding rule. This can only be specified if + the forwarding rule's target is a service attachment + (--target-service-attachment=SERVICE_ATTACHMENT) or Google APIs bundle + (--target-google-apis-bundle=API_BUNDLE) + --ip-protocol=IP_PROTOCOL IP protocol that the rule will serve. The default is TCP. diff --git a/gcloud/compute/images/import b/gcloud/compute/images/import index a551a9b5c..5127ce627 100644 --- a/gcloud/compute/images/import +++ b/gcloud/compute/images/import @@ -189,8 +189,8 @@ OPTIONAL FLAGS windows-10-x86-byol, windows-2008r2, windows-2008r2-byol, windows-2012, windows-2012-byol, windows-2012r2, windows-2012r2-byol, windows-2016, windows-2016-byol, windows-2019, windows-2019-byol, - windows-7-x64-byol, windows-7-x86-byol, windows-8-x64-byol, - windows-8-x86-byol. + windows-2022, windows-2022-byol, windows-7-x64-byol, + windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/compute/instances/bulk/create b/gcloud/compute/instances/bulk/create index 0a7a3413b..7908e6b5b 100644 --- a/gcloud/compute/instances/bulk/create +++ b/gcloud/compute/instances/bulk/create @@ -26,6 +26,7 @@ SYNOPSIS [--min-count=MIN_COUNT] [--min-cpu-platform=PLATFORM] [--min-node-cpu=MIN_NODE_CPU] [--network=NETWORK] [--network-interface=[PROPERTY=VALUE,...]] + [--network-performance-configs=[PROPERTY=VALUE,...]] [--network-tier=NETWORK_TIER] [--post-key-revocation-action-type=POLICY] [--preemptible] [--provisioning-model=PROVISIONING_MODEL] @@ -526,6 +527,17 @@ OPTIONAL FLAGS Specifies the Network Interface Controller (NIC) type for the interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET. + --network-performance-configs=[PROPERTY=VALUE,...] + Configures network performance settings for the instance. If this flag + is not specified, the instance will be created with its default network + performance configuration. + + total-egress-bandwidth-tier + Total egress bandwidth is the available outbound bandwidth from a + VM, regardless of whether the traffic is going to internal IP or + external IP destinations. The following tier values are allowed: + [DEFAULT,TIER_1] + --network-tier=NETWORK_TIER Specifies the network tier that will be used to configure the instance. NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. The diff --git a/gcloud/compute/instances/import b/gcloud/compute/instances/import index 6cf6a1620..fcf21c13b 100644 --- a/gcloud/compute/instances/import +++ b/gcloud/compute/instances/import @@ -165,8 +165,9 @@ OPTIONAL FLAGS ubuntu-1604, ubuntu-1804, ubuntu-2004, windows-10-x64-byol, windows-10-x86-byol, windows-2008r2, windows-2008r2-byol, windows-2012, windows-2012-byol, windows-2012r2, windows-2012r2-byol, windows-2016, - windows-2016-byol, windows-2019, windows-2019-byol, windows-7-x64-byol, - windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol. + windows-2016-byol, windows-2019, windows-2019-byol, windows-2022, + windows-2022-byol, windows-7-x64-byol, windows-7-x86-byol, + windows-8-x64-byol, windows-8-x86-byol. --private-network-ip=PRIVATE_NETWORK_IP Specifies the RFC1918 IP to assign to the instance. The IP should be in diff --git a/gcloud/compute/instances/set-scheduling b/gcloud/compute/instances/set-scheduling index 09beec537..e867b1c05 100644 --- a/gcloud/compute/instances/set-scheduling +++ b/gcloud/compute/instances/set-scheduling @@ -6,7 +6,10 @@ SYNOPSIS gcloud compute instances set-scheduling INSTANCE_NAME [--clear-min-node-cpu] [--maintenance-policy=MAINTENANCE_POLICY] [--min-node-cpu=MIN_NODE_CPU] [--[no-]preemptible] - [--[no-]restart-on-failure] [--zone=ZONE] + [--provisioning-model=PROVISIONING_MODEL] [--[no-]restart-on-failure] + [--zone=ZONE] + [--clear-instance-termination-action + | --instance-termination-action=INSTANCE_TERMINATION_ACTION] [--clear-node-affinities | --node=NODE | --node-affinity-file=NODE_AFFINITY_FILE | --node-group=NODE_GROUP] [GCLOUD_WIDE_FLAG ...] @@ -58,6 +61,19 @@ FLAGS instances can not be restarted and will not migrate. Use --preemptible to enable and --no-preemptible to disable. + --provisioning-model=PROVISIONING_MODEL + Specifies provisioning model, which determines price, obtainability, + and runtime for the VM instance. PROVISIONING_MODEL must be one of: + + SPOT + Spot VMs are spare capacity; Spot VMs are discounted to have much + lower prices than standard VMs but have no guaranteed runtime. Spot + VMs are the new version of preemptible VM instances, except Spot + VMs do not have a 24-hour maximum runtime. + STANDARD + Default. Standard provisioning model for VM instances, which has + user-controlled runtime but no Spot discounts. + --[no-]restart-on-failure The instances will be restarted if they are terminated by Compute Engine. This does not affect terminations performed by the user. This @@ -88,6 +104,29 @@ FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. + Instance Termination Action + + At most one of these can be specified: + + --clear-instance-termination-action + Disables the termination action for this VM if allowed OR sets + termination action to the default value. Depending on a VM's + availability settings, a termination action is either required or not + allowed. This flag is required when you are updating a VM such that + it's previously specified termination action is no longer allowed. If + you use this flag when a VM requires a termination action, it's + termination action is just set to the default value (stop). + + --instance-termination-action=INSTANCE_TERMINATION_ACTION + Specifies the termination action that will be taken upon VM + preemption. INSTANCE_TERMINATION_ACTION must be one of: + + DELETE + Permanently delete the VM. + STOP + Default. Stop the VM without preserving memory. The VM can be + restarted later. + Sole Tenancy. At most one of these can be specified: diff --git a/gcloud/compute/instances/update b/gcloud/compute/instances/update index 04f72eb7a..f27bc00c2 100644 --- a/gcloud/compute/instances/update +++ b/gcloud/compute/instances/update @@ -7,7 +7,10 @@ SYNOPSIS [--[no-]shielded-integrity-monitoring] [--shielded-learn-integrity-policy] [--[no-]shielded-secure-boot] [--[no-]shielded-vtpm] [--update-labels=[KEY=VALUE,...]] [--zone=ZONE] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--clear-labels | --remove-labels=[KEY,...]] + [--clear-node-affinities | --node=NODE + | --node-affinity-file=NODE_AFFINITY_FILE | --node-group=NODE_GROUP] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute instances update updates labels and requested CPU Platform @@ -158,6 +161,40 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. + Sole Tenancy. + + At most one of these can be specified: + + --clear-node-affinities + Removes the node affinities field from the instance. If specified, + the instance node settings will be cleared. The instance will not be + scheduled onto a sole-tenant node. + + --node=NODE + The name of the node to schedule this instance on. + + --node-affinity-file=NODE_AFFINITY_FILE + The JSON/YAML file containing the configuration of desired nodes onto + which this instance could be scheduled. These rules filter the nodes + according to their node affinity labels. A node's affinity labels + come from the node template of the group the node is in. + + The file should contain a list of a JSON/YAML objects with the + following fields: + + key + Corresponds to the node affinity label keys of the Node resource. + operator + Specifies the node selection type. Must be one of: IN: Requires + Compute Engine to seek for matched nodes. NOT_IN: Requires + Compute Engine to avoid certain nodes. + values + Optional. A list of values which correspond to the node affinity + label values of the Node resource. + + --node-group=NODE_GROUP + The name of the node group to schedule this instance on. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/compute/machine-images/import b/gcloud/compute/machine-images/import index 53b02ed08..604c5c318 100644 --- a/gcloud/compute/machine-images/import +++ b/gcloud/compute/machine-images/import @@ -157,8 +157,9 @@ OPTIONAL FLAGS ubuntu-1604, ubuntu-1804, ubuntu-2004, windows-10-x64-byol, windows-10-x86-byol, windows-2008r2, windows-2008r2-byol, windows-2012, windows-2012-byol, windows-2012r2, windows-2012r2-byol, windows-2016, - windows-2016-byol, windows-2019, windows-2019-byol, windows-7-x64-byol, - windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol. + windows-2016-byol, windows-2019, windows-2019-byol, windows-2022, + windows-2022-byol, windows-7-x64-byol, windows-7-x86-byol, + windows-8-x64-byol, windows-8-x86-byol. --restart-on-failure The VMs created from the imported machine image are restarted if they diff --git a/gcloud/compute/networks/peerings/create b/gcloud/compute/networks/peerings/create index 2165ec929..05f9a894c 100644 --- a/gcloud/compute/networks/peerings/create +++ b/gcloud/compute/networks/peerings/create @@ -7,7 +7,8 @@ SYNOPSIS --peer-network=PEER_NETWORK [--async] [--auto-create-routes] [--export-custom-routes] [--export-subnet-routes-with-public-ip] [--import-custom-routes] [--import-subnet-routes-with-public-ip] - [--peer-project=PEER_PROJECT] [GCLOUD_WIDE_FLAG ...] + [--peer-project=PEER_PROJECT] [--stack-type=STACK_TYPE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute networks peerings create is used to create peerings between @@ -73,6 +74,19 @@ OPTIONAL FLAGS The name of the project for the peer network. If not specified, defaults to current project. + --stack-type=STACK_TYPE + Stack type of the peering. If not specified, defaults to IPV4_ONLY. + + STACK_TYPE must be one of: + + IPV4_ONLY + Only IPv4 traffic and routes will be exchanged across this peering. + + IPV4_IPV6 + IPv4 traffic and routes will be exchanged across this peering. + IPv6 traffic and routes will be exchanged if the matching peering + configuration also has stack_type set to IPV4_IPV6. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/compute/networks/peerings/update b/gcloud/compute/networks/peerings/update index 3fdaed02a..8ec238759 100644 --- a/gcloud/compute/networks/peerings/update +++ b/gcloud/compute/networks/peerings/update @@ -6,7 +6,7 @@ SYNOPSIS gcloud compute networks peerings update NAME --network=NETWORK [--export-custom-routes] [--export-subnet-routes-with-public-ip] [--import-custom-routes] [--import-subnet-routes-with-public-ip] - [GCLOUD_WIDE_FLAG ...] + [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...] EXAMPLES To update the peering named peering-name to both export and import custom @@ -50,6 +50,19 @@ OPTIONAL FLAGS public IP ranges from peer network. Use --no-import-subnet-routes-with-public-ip to disable it. + --stack-type=STACK_TYPE + Stack type of the peering. If not specified, defaults to IPV4_ONLY. + + STACK_TYPE must be one of: + + IPV4_ONLY + Only IPv4 traffic and routes will be exchanged across this peering. + + IPV4_IPV6 + IPv4 traffic and routes will be exchanged across this peering. + IPv6 traffic and routes will be exchanged if the matching peering + configuration also has stack_type set to IPV4_IPV6. + 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/config/get b/gcloud/config/get index 38691ae51..792b31db6 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -487,7 +487,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -510,8 +510,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/config/help b/gcloud/config/help index d2969081c..ea3ee89d9 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -519,7 +519,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -542,8 +542,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/config/list b/gcloud/config/list index be1af1ee7..8a8fbb17b 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -521,7 +521,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -544,8 +544,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/config/set b/gcloud/config/set index c3fa4a665..6db98f838 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -534,7 +534,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -557,8 +557,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/config/unset b/gcloud/config/unset index 261d4b11f..3c793e3ae 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -495,7 +495,7 @@ AVAILABLE PROPERTIES adds authentication to requests. impersonate_service_account - For this `gcloud` invocation, all API requests will be + While set, all API requests will be made as the given service account or target service account in an impersonation delegation chain instead of the currently selected account. You can specify either a single service account as the @@ -518,8 +518,8 @@ AVAILABLE PROPERTIES each service account delegates its permissions to the next service account in the chain. Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the - next service account in the list. For example, when - `--impersonate-service-account=` + next service account in the list. For example, when the property is set + via `gcloud config set auth/impersonate-service-account=` `_SERVICE_ACCOUNT_1_`,`_SERVICE_ACCOUNT_2_`, the active account must have the `roles/iam.serviceAccountTokenCreator` role on diff --git a/gcloud/container/fleet/help b/gcloud/container/fleet/help index 0dca5068a..eea397ff2 100644 --- a/gcloud/container/fleet/help +++ b/gcloud/container/fleet/help @@ -51,6 +51,9 @@ GROUPS features Manage Hub Feature resources. + identity-service + Manage Identity Service Feature. + ingress Manage Multi-cluster Ingress Feature. diff --git a/gcloud/container/fleet/identity-service/apply b/gcloud/container/fleet/identity-service/apply new file mode 100644 index 000000000..f25f60cdd --- /dev/null +++ b/gcloud/container/fleet/identity-service/apply @@ -0,0 +1,46 @@ +NAME + gcloud container fleet identity-service apply - update an Identity Service + Feature Spec + +SYNOPSIS + gcloud container fleet identity-service apply --config=CONFIG + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Applies the authentication configuration to the Identity Service feature + spec for this membership. This configuration is now the "source of truth" + for the cluster and can only be updated by using this command or the Cloud + Console. Any local authentication configuration on the cluster is + overwritten by this configuration, including any local updates made after + you run this command. + +EXAMPLES + To apply an Identity Service configuration for a membership, run: + + $ gcloud container fleet identity-service apply \ + --membership=CLUSTER_NAME \ + --config=/path/to/identity-service.yaml + +REQUIRED FLAGS + --config=CONFIG + The path to the identity-service.yaml config file. + +OPTIONAL FLAGS + --membership=MEMBERSHIP + The Membership name provided during registration. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet identity-service apply + + $ gcloud beta container fleet identity-service apply + diff --git a/gcloud/container/fleet/identity-service/delete b/gcloud/container/fleet/identity-service/delete new file mode 100644 index 000000000..f0e1b45b8 --- /dev/null +++ b/gcloud/container/fleet/identity-service/delete @@ -0,0 +1,36 @@ +NAME + gcloud container fleet identity-service delete - remove the Identity + Service Feature Spec for the given membership + +SYNOPSIS + gcloud container fleet identity-service delete [--membership=MEMBERSHIP] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Removes the Identity Service Feature Spec for the given membership. + +EXAMPLES + To delete an Identity Service configuration for a membership, run: + + $ gcloud container fleet identity-service delete \ + --membership=CLUSTER_NAME + +FLAGS + --membership=MEMBERSHIP + Membership name provided during registration. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet identity-service delete + + $ gcloud beta container fleet identity-service delete + diff --git a/gcloud/container/fleet/identity-service/describe b/gcloud/container/fleet/identity-service/describe new file mode 100644 index 000000000..28f135a1a --- /dev/null +++ b/gcloud/container/fleet/identity-service/describe @@ -0,0 +1,64 @@ +NAME + gcloud container fleet identity-service describe - prints the status of all + clusters with Identity Service installed + +SYNOPSIS + gcloud container fleet identity-service describe [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Prints the status of the Identity Service Feature resource in a fleet. + +EXAMPLES + To describe the status of the Identity Service configuration, run: + + $ gcloud container fleet identity-service describe + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet identity-service describe + + $ gcloud beta container fleet identity-service describe + diff --git a/gcloud/container/fleet/identity-service/disable b/gcloud/container/fleet/identity-service/disable new file mode 100644 index 000000000..3b1913219 --- /dev/null +++ b/gcloud/container/fleet/identity-service/disable @@ -0,0 +1,36 @@ +NAME + gcloud container fleet identity-service disable - disable Identity Service + Feature + +SYNOPSIS + gcloud container fleet identity-service disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command disables the Identity Service Feature in a fleet. + +EXAMPLES + To disable the Identity Service Feature, run: + + $ gcloud container fleet identity-service disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet identity-service disable + + $ gcloud beta container fleet identity-service disable + diff --git a/gcloud/container/fleet/identity-service/enable b/gcloud/container/fleet/identity-service/enable new file mode 100644 index 000000000..4d4d0c874 --- /dev/null +++ b/gcloud/container/fleet/identity-service/enable @@ -0,0 +1,30 @@ +NAME + gcloud container fleet identity-service enable - enable Identity Service + Feature + +SYNOPSIS + gcloud container fleet identity-service enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command enables the Identity Service Feature in a fleet. + +EXAMPLES + To enable the Identity Service Feature, run: + + $ gcloud container fleet identity-service enable + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet identity-service enable + + $ gcloud beta container fleet identity-service enable + diff --git a/gcloud/container/fleet/identity-service/help b/gcloud/container/fleet/identity-service/help new file mode 100644 index 000000000..781c77264 --- /dev/null +++ b/gcloud/container/fleet/identity-service/help @@ -0,0 +1,39 @@ +NAME + gcloud container fleet identity-service - manage Identity Service Feature + +SYNOPSIS + gcloud container fleet identity-service COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Identity Service Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + apply + Update an Identity Service Feature Spec. + + delete + Remove the Identity Service Feature Spec for the given membership. + + describe + Prints the status of all clusters with Identity Service installed. + + disable + Disable Identity Service Feature. + + enable + Enable Identity Service Feature. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet identity-service + + $ gcloud beta container fleet identity-service + diff --git a/gcloud/container/hub/help b/gcloud/container/hub/help index e290d6d20..e0ed94ce1 100644 --- a/gcloud/container/hub/help +++ b/gcloud/container/hub/help @@ -51,6 +51,9 @@ GROUPS features Manage Hub Feature resources. + identity-service + Manage Identity Service Feature. + ingress Manage Multi-cluster Ingress Feature. diff --git a/gcloud/container/hub/identity-service/apply b/gcloud/container/hub/identity-service/apply new file mode 100644 index 000000000..7ebaf3c24 --- /dev/null +++ b/gcloud/container/hub/identity-service/apply @@ -0,0 +1,46 @@ +NAME + gcloud container hub identity-service apply - update an Identity Service + Feature Spec + +SYNOPSIS + gcloud container hub identity-service apply --config=CONFIG + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Applies the authentication configuration to the Identity Service feature + spec for this membership. This configuration is now the "source of truth" + for the cluster and can only be updated by using this command or the Cloud + Console. Any local authentication configuration on the cluster is + overwritten by this configuration, including any local updates made after + you run this command. + +EXAMPLES + To apply an Identity Service configuration for a membership, run: + + $ gcloud container hub identity-service apply \ + --membership=CLUSTER_NAME \ + --config=/path/to/identity-service.yaml + +REQUIRED FLAGS + --config=CONFIG + The path to the identity-service.yaml config file. + +OPTIONAL FLAGS + --membership=MEMBERSHIP + The Membership name provided during registration. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container hub identity-service apply + + $ gcloud beta container hub identity-service apply + diff --git a/gcloud/container/hub/identity-service/delete b/gcloud/container/hub/identity-service/delete new file mode 100644 index 000000000..a1b09d50c --- /dev/null +++ b/gcloud/container/hub/identity-service/delete @@ -0,0 +1,36 @@ +NAME + gcloud container hub identity-service delete - remove the Identity Service + Feature Spec for the given membership + +SYNOPSIS + gcloud container hub identity-service delete [--membership=MEMBERSHIP] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Removes the Identity Service Feature Spec for the given membership. + +EXAMPLES + To delete an Identity Service configuration for a membership, run: + + $ gcloud container hub identity-service delete \ + --membership=CLUSTER_NAME + +FLAGS + --membership=MEMBERSHIP + Membership name provided during registration. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container hub identity-service delete + + $ gcloud beta container hub identity-service delete + diff --git a/gcloud/container/hub/identity-service/describe b/gcloud/container/hub/identity-service/describe new file mode 100644 index 000000000..881037223 --- /dev/null +++ b/gcloud/container/hub/identity-service/describe @@ -0,0 +1,64 @@ +NAME + gcloud container hub identity-service describe - prints the status of all + clusters with Identity Service installed + +SYNOPSIS + gcloud container hub identity-service describe [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Prints the status of the Identity Service Feature resource in a fleet. + +EXAMPLES + To describe the status of the Identity Service configuration, run: + + $ gcloud container hub identity-service describe + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container hub identity-service describe + + $ gcloud beta container hub identity-service describe + diff --git a/gcloud/container/hub/identity-service/disable b/gcloud/container/hub/identity-service/disable new file mode 100644 index 000000000..6ffcb3e9f --- /dev/null +++ b/gcloud/container/hub/identity-service/disable @@ -0,0 +1,36 @@ +NAME + gcloud container hub identity-service disable - disable Identity Service + Feature + +SYNOPSIS + gcloud container hub identity-service disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command disables the Identity Service Feature in a fleet. + +EXAMPLES + To disable the Identity Service Feature, run: + + $ gcloud container hub identity-service disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container hub identity-service disable + + $ gcloud beta container hub identity-service disable + diff --git a/gcloud/container/hub/identity-service/enable b/gcloud/container/hub/identity-service/enable new file mode 100644 index 000000000..307ec6a12 --- /dev/null +++ b/gcloud/container/hub/identity-service/enable @@ -0,0 +1,30 @@ +NAME + gcloud container hub identity-service enable - enable Identity Service + Feature + +SYNOPSIS + gcloud container hub identity-service enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command enables the Identity Service Feature in a fleet. + +EXAMPLES + To enable the Identity Service Feature, run: + + $ gcloud container hub identity-service enable + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container hub identity-service enable + + $ gcloud beta container hub identity-service enable + diff --git a/gcloud/container/hub/identity-service/help b/gcloud/container/hub/identity-service/help new file mode 100644 index 000000000..613c1df73 --- /dev/null +++ b/gcloud/container/hub/identity-service/help @@ -0,0 +1,39 @@ +NAME + gcloud container hub identity-service - manage Identity Service Feature + +SYNOPSIS + gcloud container hub identity-service COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Identity Service Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + apply + Update an Identity Service Feature Spec. + + delete + Remove the Identity Service Feature Spec for the given membership. + + describe + Prints the status of all clusters with Identity Service installed. + + disable + Disable Identity Service Feature. + + enable + Enable Identity Service Feature. + +NOTES + These variants are also available: + + $ gcloud alpha container hub identity-service + + $ gcloud beta container hub identity-service + diff --git a/gcloud/database-migration/migration-jobs/create b/gcloud/database-migration/migration-jobs/create index 5e8d99243..8f11d2309 100644 --- a/gcloud/database-migration/migration-jobs/create +++ b/gcloud/database-migration/migration-jobs/create @@ -7,7 +7,7 @@ SYNOPSIS (MIGRATION_JOB : --region=REGION) --destination=DESTINATION --source=SOURCE --type=TYPE [--display-name=DISPLAY_NAME] [--dump-path=DUMP_PATH] [--labels=[KEY=VALUE,...]] - [--peer-vpc=PEER_VPC + [--peer-vpc=PEER_VPC | --static-ip | [--vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC : --vm=VM]] [GCLOUD_WIDE_FLAG ...] @@ -106,15 +106,20 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. - The connectivity method used by the migration job. If not specified, uses - the default IP allowlist method which will create a public IP when used - with a Cloud SQL destination DB. + The connectivity method used by the migration job. If a connectivity + method isn't specified, then it isn't added to the migration job. At most one of these can be specified: --peer-vpc=PEER_VPC Name of the VPC network to peer with the Cloud SQL private network. + --static-ip + Use the default IP allowlist method. This method creates a public IP + that will be used with the destination Cloud SQL database. The method + works by configuring the source database server to accept connections + from the outgoing IP of the Cloud SQL instance. + Parameters for the reverse-SSH tunnel connectivity method. --vm-ip=VM_IP diff --git a/gcloud/database-migration/migration-jobs/update b/gcloud/database-migration/migration-jobs/update index 2222c1c33..8d661b8af 100644 --- a/gcloud/database-migration/migration-jobs/update +++ b/gcloud/database-migration/migration-jobs/update @@ -8,7 +8,7 @@ SYNOPSIS --source=SOURCE [--display-name=DISPLAY_NAME] [--dump-path=DUMP_PATH] [--type=TYPE] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] - [--peer-vpc=PEER_VPC + [--peer-vpc=PEER_VPC | --static-ip | --vm=VM --vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC] [GCLOUD_WIDE_FLAG ...] @@ -124,15 +124,20 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. - The connectivity method used by the migration job. If not specified, uses - the default IP allowlist method which will create a public IP when used - with a Cloud SQL destination DB. + The connectivity method used by the migration job. If a connectivity + method isn't specified, then it isn't updated for the migration job. At most one of these can be specified: --peer-vpc=PEER_VPC Name of the VPC network to peer with the Cloud SQL private network. + --static-ip + Use the default IP allowlist method. This method creates a public IP + that will be used with the destination Cloud SQL database. The method + works by configuring the source database server to accept connections + from the outgoing IP of the Cloud SQL instance. + Parameters for the reverse-SSH tunnel connectivity method. --vm=VM diff --git a/gcloud/dns/record-sets/create b/gcloud/dns/record-sets/create index caf06fba5..d13514515 100644 --- a/gcloud/dns/record-sets/create +++ b/gcloud/dns/record-sets/create @@ -18,6 +18,15 @@ EXAMPLES $ gcloud dns record-sets create foo.bar.com. \ --rrdatas=1.2.3.4,9.8.7.6 --type=A --ttl=60 --zone=my_zone + To create a geo routed record-set with dnsName foo.bar.com., record type A, + routing-policy-data "us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5.6,9.8.7.6" + and ttl 60 in my_zone. + + $ gcloud dns record-sets create foo.bar.com. \ + --routing-policy-data="us-centra1=1.2.3.4,2.3.4.5;us-west1=3.4.5\ + .6,9.8.7.6" --routing-policy-type=GEO --type=A --ttl=60 \ + --zone=my_zone --location=us-east1-a + To create a record-set with dnsName foo.bar.com., record type A, rrdata [1.2.3.4, 9.8.7.6] and ttl 60 in my_zone in us-east1-a run this: diff --git a/gcloud/edge-cloud/container/clusters/node-pools/list b/gcloud/edge-cloud/container/clusters/node-pools/list index 6e1c50af6..517578a12 100644 --- a/gcloud/edge-cloud/container/clusters/node-pools/list +++ b/gcloud/edge-cloud/container/clusters/node-pools/list @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud edge-cloud container clusters node-pools list - (--cluster=CLUSTER : --location=LOCATION) [--filter=EXPRESSION] + [--cluster=CLUSTER --location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -17,29 +17,29 @@ EXAMPLES $ gcloud edge-cloud container clusters node-pools list \ --location=us-central1 --cluster= -REQUIRED FLAGS +FLAGS Cluster resource - Parent Edge Container location to list all contained Edge Container nodePools. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. To set the project attribute: + ◆ provide the argument --cluster on the command line with a fully + specified name; ◆ provide the argument --cluster 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. - --cluster=CLUSTER ID of the cluster or fully qualified identifier for the cluster. To set the cluster attribute: + ▸ provide the argument --cluster on the command line; ▸ provide the argument --cluster on the command line. - This flag must be specified if any of the other arguments in this - group are specified. - --location=LOCATION The global location name. To set the location attribute: + ▸ provide the argument --cluster on the command line with a fully + specified name; ▸ provide the argument --cluster on the command line with a fully specified name; ▸ provide the argument --location on the command line; diff --git a/gcloud/edge-cloud/container/clusters/update b/gcloud/edge-cloud/container/clusters/update index 398d38ec6..c8ce3da51 100644 --- a/gcloud/edge-cloud/container/clusters/update +++ b/gcloud/edge-cloud/container/clusters/update @@ -4,9 +4,11 @@ NAME SYNOPSIS gcloud edge-cloud container clusters update (CLUSTER : --location=LOCATION) - [--async] [--maintenance-window-end=MAINTENANCE_WINDOW_END] - [--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE] - [--maintenance-window-start=MAINTENANCE_WINDOW_START] + [--async] + [--clear-maintenance-window + | --maintenance-window-end=MAINTENANCE_WINDOW_END + --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE + --maintenance-window-start=MAINTENANCE_WINDOW_START] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -52,20 +54,28 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. - --maintenance-window-end=MAINTENANCE_WINDOW_END - End time of the recurring cluster maintenance window in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. - "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + At most one of these can be specified: - --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE - An RFC 5545 (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) - recurrence rule for how the cluster maintenance window recurs. They go - on for the span of time between the start and the end time. + --clear-maintenance-window + If set, removes the maintenance window setting from the cluster. - --maintenance-window-start=MAINTENANCE_WINDOW_START - Start time of the recurring cluster maintenance window in the RFC 3339 - (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. - "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + Updates cluster maintenance window setting (more than one flags can be + specified from this group) + + --maintenance-window-end=MAINTENANCE_WINDOW_END + End time of the recurring cluster maintenance window in the RFC + 3339 (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" + + --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE + An RFC 5545 (https://tools.ietf.org/html/rfc5545#section-3.8.5.3) + recurrence rule for how the cluster maintenance window recurs. They + go on for the span of time between the start and the end time. + + --maintenance-window-start=MAINTENANCE_WINDOW_START + Start time of the recurring cluster maintenance window in the RFC + 3339 (https://www.ietf.org/rfc/rfc3339.txt) format. E.g. + "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00" GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/iam/workload-identity-pools/providers/create-saml b/gcloud/iam/workload-identity-pools/providers/create-saml new file mode 100644 index 000000000..a1c67efe7 --- /dev/null +++ b/gcloud/iam/workload-identity-pools/providers/create-saml @@ -0,0 +1,202 @@ +NAME + gcloud iam workload-identity-pools providers create-saml - create a new + SAML workload identity pool provider + +SYNOPSIS + gcloud iam workload-identity-pools providers create-saml + (PROVIDER : --location=LOCATION + --workload-identity-pool=WORKLOAD_IDENTITY_POOL) + --attribute-mapping=[ATTRIBUTE_MAPPING,...] + --idp-metadata-path=IDP_METADATA_PATH + [--attribute-condition=ATTRIBUTE_CONDITION] [--description=DESCRIPTION] + [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new SAML workload identity pool provider. + +EXAMPLES + The following command creates a disabled SAML workload identity pool + provider in the default project with the ID + my-workload-identity-pool-provider. Explicit values for all required and + optional parameters are provided. + + $ gcloud iam workload-identity-pools providers create-saml \ + my-workload-identity-pool-provider --location="global" \ + --workload-identity-pool="my-workload-identity-pool" \ + --display-name="My workload pool provider" \ + --description="My workload pool provider description" \ + --disabled --attribute-mapping="google.subject=assertion.sub" \ + --attribute-condition="true" \ + --idp-metadata-path="path/to/metadata/file.xml" + +POSITIONAL ARGUMENTS + Workload identity pool provider resource - The workload identity pool + provider to create. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. To set the project + attribute: + ◆ provide the argument provider 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. + + PROVIDER + ID of the workload identity pool provider or fully qualified + identifier for the workload identity pool provider. To set the + provider attribute: + ▸ provide the argument provider on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location name. To set the location attribute: + ▸ provide the argument provider on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --workload-identity-pool=WORKLOAD_IDENTITY_POOL + The ID to use for the pool, which becomes the final component of the + resource name. This value should be 4-32 characters, and may contain + the characters [a-z0-9-]. The prefix gcp- is reserved for use by + Google, and may not be specified. + + To set the workload-identity-pool attribute: + ▸ provide the argument provider on the command line with a fully + specified name; + ▸ provide the argument --workload-identity-pool on the command + line. + +REQUIRED FLAGS + --attribute-mapping=[ATTRIBUTE_MAPPING,...] + Maps attributes from authentication credentials issued by an external + identity provider to Google Cloud attributes, such as subject and + segment. + + Each key must be a string specifying the Google Cloud IAM attribute to + map to. + + The following keys are supported: + + ◆ google.subject: The principal IAM is authenticating. You can + reference this value in IAM bindings. This is also the subject that + appears in Cloud Logging logs. Cannot exceed 127 bytes. + + ◆ google.groups: Groups the external identity belongs to. You can + grant groups access to resources using an IAM principalSet binding; + access applies to all members of the group. + + You can also provide custom attributes by specifying + attribute.{custom_attribute}, where {custom_attribute} is the name of + the custom attribute to be mapped. You can define a maximum of 50 + custom attributes. The maximum length of a mapped attribute key is 100 + characters, and the key may only contain the characters [a-z_0-9]. + + You can reference these attributes in IAM policies to define + fine-grained access for a workload to Google Cloud resources. For + example: + + ◆ google.subject: + principal://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/subject/{value} + + ◆ google.groups: + principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/group/{value} + + ◆ attribute.{custom_attribute}: + principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/attribute.{custom_attribute}/{value} + + Each value must be a [Common Expression Language] + (https://opensource.google/projects/cel) function that maps an identity + provider credential to the normalized attribute specified by the + corresponding map key. + + You can use the assertion keyword in the expression to access a JSON + representation of the authentication credential issued by the provider. + + The maximum length of an attribute mapping expression is 2048 + characters. When evaluated, the total size of all mapped attributes + must not exceed 8KB. + + For AWS providers, the following rules apply: + + ◆ If no attribute mapping is defined, the following default mapping + applies: + + { + "google.subject":"assertion.arn", + "attribute.aws_role": + "assertion.arn.contains('assumed-role')" + " ? assertion.arn.extract('{account_arn}assumed-role/')" + " + 'assumed-role/'" + " + assertion.arn.extract('assumed-role/{role_name}/')" + " : assertion.arn", + } + + ◆ If any custom attribute mappings are defined, they must include a + mapping to the google.subject attribute. + + For OIDC providers, the following rules apply: + + ◆ Custom attribute mappings must be defined, and must include a mapping + to the google.subject attribute. For example, the following maps the + sub claim of the incoming credential to the subject attribute on a + Google token. + + {"google.subject": "assertion.sub"} + + --idp-metadata-path=IDP_METADATA_PATH + XML file with configuration metadata for the SAML identity provider. The + metadata file must follow the SAML 2.0 metadata specification + (https://www.oasis-open.org/committees/download.php/35391/sstc-saml-metadata-errata-2.0-wd-04-diff.pdf). + +OPTIONAL FLAGS + --attribute-condition=ATTRIBUTE_CONDITION + A Common Expression Language (https://opensource.google/projects/cel) + expression, in plain text, to restrict what otherwise valid + authentication credentials issued by the provider should not be + accepted. + + The expression must output a boolean representing whether to allow the + federation. + + The following keywords may be referenced in the expressions: + + ◆ assertion: JSON representing the authentication credential issued + by the provider. + ◆ google: The Google attributes mapped from the assertion in the + attribute_mappings. + ◆ attribute: The custom attributes mapped from the assertion in the + attribute_mappings. + + The maximum length of the attribute condition expression is 4096 + characters. If unspecified, all valid authentication credential are + accepted. + + The following example shows how to only allow credentials with a mapped + google.groups value of admins: + + "'admins' in google.groups" + + --description=DESCRIPTION + A description for the provider. Cannot exceed 256 characters. + + --disabled + Whether the provider is disabled. You cannot use a disabled provider to + exchange tokens. However, existing tokens still grant access. + + --display-name=DISPLAY_NAME + A display name for the provider. Cannot exceed 32 characters. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 iam/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/iam/ diff --git a/gcloud/iam/workload-identity-pools/providers/help b/gcloud/iam/workload-identity-pools/providers/help index 684dcb7ab..3250c090c 100644 --- a/gcloud/iam/workload-identity-pools/providers/help +++ b/gcloud/iam/workload-identity-pools/providers/help @@ -29,6 +29,9 @@ COMMANDS create-oidc Create a new OIDC workload identity pool provider. + create-saml + Create a new SAML workload identity pool provider. + delete Delete a workload identity pool provider. @@ -47,6 +50,9 @@ COMMANDS update-oidc Update an OIDC workload identity pool provider. + update-saml + Update a SAML workload identity pool provider. + NOTES These variants are also available: diff --git a/gcloud/iam/workload-identity-pools/providers/update-saml b/gcloud/iam/workload-identity-pools/providers/update-saml new file mode 100644 index 000000000..568d0aeb5 --- /dev/null +++ b/gcloud/iam/workload-identity-pools/providers/update-saml @@ -0,0 +1,200 @@ +NAME + gcloud iam workload-identity-pools providers update-saml - update a SAML + workload identity pool provider + +SYNOPSIS + gcloud iam workload-identity-pools providers update-saml + (PROVIDER : --location=LOCATION + --workload-identity-pool=WORKLOAD_IDENTITY_POOL) + [--attribute-condition=ATTRIBUTE_CONDITION] + [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] + [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] + [--idp-metadata-path=IDP_METADATA_PATH] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a SAML workload identity pool provider. + +EXAMPLES + The following command updates the SAML workload identity pool provider with + the ID my-workload-identity-pool-provider. Explicit values for all required + and optional parameters are provided: + + $ gcloud iam workload-identity-pools providers update-saml \ + my-workload-identity-pool-provider --location="global" \ + --workload-identity-pool="my-workload-identity-pool" \ + --display-name="My workload pool provider" \ + --description="My workload pool provider description" \ + --disabled --attribute-mapping="google.subject=assertion.sub" \ + --attribute-condition="true" \ + --idp-metadata-path="path/to/metadata/file.xml" + +POSITIONAL ARGUMENTS + Workload identity pool provider resource - The workload identity pool + provider to update. 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 provider 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. + + PROVIDER + ID of the workload identity pool provider or fully qualified + identifier for the workload identity pool provider. To set the + provider attribute: + ▸ provide the argument provider on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location name. To set the location attribute: + ▸ provide the argument provider on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --workload-identity-pool=WORKLOAD_IDENTITY_POOL + The ID to use for the pool, which becomes the final component of the + resource name. This value should be 4-32 characters, and may contain + the characters [a-z0-9-]. The prefix gcp- is reserved for use by + Google, and may not be specified. + + To set the workload-identity-pool attribute: + ▸ provide the argument provider on the command line with a fully + specified name; + ▸ provide the argument --workload-identity-pool on the command + line. + +FLAGS + --attribute-condition=ATTRIBUTE_CONDITION + A Common Expression Language (https://opensource.google/projects/cel) + expression, in plain text, to restrict what otherwise valid + authentication credentials issued by the provider should not be + accepted. + + The expression must output a boolean representing whether to allow the + federation. + + The following keywords may be referenced in the expressions: + + ◆ assertion: JSON representing the authentication credential issued + by the provider. + ◆ google: The Google attributes mapped from the assertion in the + attribute_mappings. + ◆ attribute: The custom attributes mapped from the assertion in the + attribute_mappings. + + The maximum length of the attribute condition expression is 4096 + characters. If unspecified, all valid authentication credential are + accepted. + + The following example shows how to only allow credentials with a mapped + google.groups value of admins: + + "'admins' in google.groups" + + --attribute-mapping=[ATTRIBUTE_MAPPING,...] + Maps attributes from authentication credentials issued by an external + identity provider to Google Cloud attributes, such as subject and + segment. + + Each key must be a string specifying the Google Cloud IAM attribute to + map to. + + The following keys are supported: + + ◆ google.subject: The principal IAM is authenticating. You can + reference this value in IAM bindings. This is also the subject that + appears in Cloud Logging logs. Cannot exceed 127 bytes. + + ◆ google.groups: Groups the external identity belongs to. You can + grant groups access to resources using an IAM principalSet binding; + access applies to all members of the group. + + You can also provide custom attributes by specifying + attribute.{custom_attribute}, where {custom_attribute} is the name of + the custom attribute to be mapped. You can define a maximum of 50 + custom attributes. The maximum length of a mapped attribute key is 100 + characters, and the key may only contain the characters [a-z_0-9]. + + You can reference these attributes in IAM policies to define + fine-grained access for a workload to Google Cloud resources. For + example: + + ◆ google.subject: + principal://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/subject/{value} + + ◆ google.groups: + principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/group/{value} + + ◆ attribute.{custom_attribute}: + principalSet://iam.googleapis.com/projects/{project}/locations/{location}/workloadIdentityPools/{pool}/attribute.{custom_attribute}/{value} + + Each value must be a [Common Expression Language] + (https://opensource.google/projects/cel) function that maps an identity + provider credential to the normalized attribute specified by the + corresponding map key. + + You can use the assertion keyword in the expression to access a JSON + representation of the authentication credential issued by the provider. + + The maximum length of an attribute mapping expression is 2048 + characters. When evaluated, the total size of all mapped attributes + must not exceed 8KB. + + For AWS providers, the following rules apply: + + ◆ If no attribute mapping is defined, the following default mapping + applies: + + { + "google.subject":"assertion.arn", + "attribute.aws_role": + "assertion.arn.contains('assumed-role')" + " ? assertion.arn.extract('{account_arn}assumed-role/')" + " + 'assumed-role/'" + " + assertion.arn.extract('assumed-role/{role_name}/')" + " : assertion.arn", + } + + ◆ If any custom attribute mappings are defined, they must include a + mapping to the google.subject attribute. + + For OIDC providers, the following rules apply: + + ◆ Custom attribute mappings must be defined, and must include a mapping + to the google.subject attribute. For example, the following maps the + sub claim of the incoming credential to the subject attribute on a + Google token. + + {"google.subject": "assertion.sub"} + + --description=DESCRIPTION + A description for the provider. Cannot exceed 256 characters. + + --disabled + Whether the provider is disabled. You cannot use a disabled provider to + exchange tokens. However, existing tokens still grant access. + + --display-name=DISPLAY_NAME + A display name for the provider. Cannot exceed 32 characters. + + --idp-metadata-path=IDP_METADATA_PATH + XML file with configuration metadata for the SAML identity provider. The + metadata file must follow the SAML 2.0 metadata specification + (https://www.oasis-open.org/committees/download.php/35391/sstc-saml-metadata-errata-2.0-wd-04-diff.pdf). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 iam/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/iam/ diff --git a/gcloud/memcache/instances/create b/gcloud/memcache/instances/create index 23b3294fc..0b73b848b 100644 --- a/gcloud/memcache/instances/create +++ b/gcloud/memcache/instances/create @@ -6,6 +6,9 @@ SYNOPSIS --node-count=NODE_COUNT --node-cpu=NODE_CPU --node-memory=NODE_MEMORY [--async] [--authorized-network=AUTHORIZED_NETWORK] [--display-name=DISPLAY_NAME] [--labels=KEY=VALUE] + [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] + [--maintenance-window-duration=MAINTENANCE_WINDOW_DURATION] + [--maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME] [--memcached-version=MEMCACHED_VERSION] [--parameters=KEY=VALUE] [--zones=[ZONES,...]] [GCLOUD_WIDE_FLAG ...] @@ -86,6 +89,18 @@ OPTIONAL FLAGS --labels=KEY=VALUE List of label KEY=VALUE pairs to add. + --maintenance-window-day=MAINTENANCE_WINDOW_DAY + The day of week when the window starts, e.g. sunday. + MAINTENANCE_WINDOW_DAY must be one of: friday, monday, saturday, + sunday, thursday, tuesday, wednesday. + + --maintenance-window-duration=MAINTENANCE_WINDOW_DURATION + Duration in integer hours (3 to 8) of the maintenance window. + + --maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME + Hour of day (0 to 23) for the start of maintenance window, in UTC time + zone. + --memcached-version=MEMCACHED_VERSION Optional major version of Memcached software to use with the instance. If not provided, default of "1.5" will be used. MEMCACHED_VERSION must diff --git a/gcloud/memcache/instances/help b/gcloud/memcache/instances/help index 0f2a98c2e..b3e07c64d 100644 --- a/gcloud/memcache/instances/help +++ b/gcloud/memcache/instances/help @@ -30,6 +30,9 @@ COMMANDS list List Memorystore Memcached instances. + reschedule-maintenance + Reschedule maintenance window for a Memcache instance. + update Update a Memorystore Memcached instance. diff --git a/gcloud/memcache/instances/reschedule-maintenance b/gcloud/memcache/instances/reschedule-maintenance new file mode 100644 index 000000000..dfbba8f4e --- /dev/null +++ b/gcloud/memcache/instances/reschedule-maintenance @@ -0,0 +1,91 @@ +NAME + gcloud memcache instances reschedule-maintenance - reschedule maintenance + window for a Memcache instance + +SYNOPSIS + gcloud memcache instances reschedule-maintenance + (INSTANCE : --region=REGION) --reschedule-type=RESCHEDULE_TYPE + [--async] [--schedule-time=SCHEDULE_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Reschedule maintenance window for a Memcache instance. + +EXAMPLES + To reschedule maintenance window for an instance with the name + 'my-memcache-instance' in region 'us-central-1' with next available window, + run: + + $ gcloud memcache instances reschedule-maintenance \ + my-memcache-instance --region=us-central1 \ + --reschedule-type=next-available-window + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Cloud Memorystore + for Memcache instance you want to reschedule maintenance window. 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 instance 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. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. To + set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --region=REGION + The name of the Memcached region of the instance. Overrides the + default memcache/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property memcache/region. + +REQUIRED FLAGS + --reschedule-type=RESCHEDULE_TYPE + Reschedule type to use for the reschedule maintenance window. + RESCHEDULE_TYPE must be one of: + + immediate + Reschedule the maintenance to perform now. + next-available-window + Reschedule the maintenance to the next available window. + specific-time + Reschedule the maintenance to a specific time. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --schedule-time=SCHEDULE_TIME + Time in RFC3339 format, for example: 2012-11-15T16:19:00.094Z + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memcache/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/memorystore/ + +NOTES + These variants are also available: + + $ gcloud alpha memcache instances reschedule-maintenance + + $ gcloud beta memcache instances reschedule-maintenance + diff --git a/gcloud/memcache/instances/update b/gcloud/memcache/instances/update index f8a3f3cc1..b717cc217 100644 --- a/gcloud/memcache/instances/update +++ b/gcloud/memcache/instances/update @@ -4,8 +4,11 @@ NAME SYNOPSIS gcloud memcache instances update (INSTANCE : --region=REGION) (--parameters=KEY=VALUE | --display-name=DISPLAY_NAME - --labels=KEY=VALUE --node-count=NODE_COUNT) [--async] - [GCLOUD_WIDE_FLAG ...] + --labels=KEY=VALUE --node-count=NODE_COUNT --maintenance-window-any + | --maintenance-window-day=MAINTENANCE_WINDOW_DAY + --maintenance-window-duration=MAINTENANCE_WINDOW_DURATION + --maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME) + [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update a Memcached instance with one or more of the following actions: @@ -142,6 +145,23 @@ REQUIRED FLAGS Number of memcache nodes in this instance. Valid values range from 1 to 20. + At most one of these can be specified: + + --maintenance-window-any + Removes the user-specified maintenance window. + + --maintenance-window-day=MAINTENANCE_WINDOW_DAY + The day of week when the window starts, e.g. 'sunday'. + MAINTENANCE_WINDOW_DAY must be one of: friday, monday, saturday, + sunday, thursday, tuesday, wednesday. + + --maintenance-window-duration=MAINTENANCE_WINDOW_DURATION + Duration in integer hours (3 to 8) of the maintenance window. + + --maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME + Hour of day (0 to 23) for the start of maintenance window, in UTC + time zone. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/transfer/jobs/create b/gcloud/transfer/jobs/create index 4d364f6f8..c93d3a6b8 100644 --- a/gcloud/transfer/jobs/create +++ b/gcloud/transfer/jobs/create @@ -240,8 +240,10 @@ FLAGS are different (e.g., if etags or checksums don't match) ▸ 'always' - Overwrite destination file whenever source file has the same name -- even if they're identical + ▸ 'never' - Never overwrite destination file when source file has + the same name - OVERWRITE_WHEN must be one of: always, different. + OVERWRITE_WHEN must be one of: always, different, never. --delete-from=DELETE_FROM By default, transfer jobs won't delete any data from your source or diff --git a/gcloud/transfer/jobs/update b/gcloud/transfer/jobs/update index 32e66e463..87642b70a 100644 --- a/gcloud/transfer/jobs/update +++ b/gcloud/transfer/jobs/update @@ -292,8 +292,10 @@ FLAGS are different (e.g., if etags or checksums don't match) ▸ 'always' - Overwrite destination file whenever source file has the same name -- even if they're identical + ▸ 'never' - Never overwrite destination file when source file has + the same name - OVERWRITE_WHEN must be one of: always, different. + OVERWRITE_WHEN must be one of: always, different, never. --delete-from=DELETE_FROM By default, transfer jobs won't delete any data from your source or