diff --git a/gcloud/_version b/gcloud/_version index a18bcb4ff..2631168dd 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 489.0.0 -alpha 2024.08.16 -beta 2024.08.16 +Google Cloud SDK 490.0.0 +alpha 2024.08.23 +beta 2024.08.23 bq 2.1.8 bundled-python3-unix 3.11.9 -core 2024.08.16 +core 2024.08.23 gcloud-crc32c 1.0.0 gsutil 5.30 diff --git a/gcloud/alpha/access-context-manager/cloud-bindings/create b/gcloud/alpha/access-context-manager/cloud-bindings/create index 36dd079c3..d04aa268e 100644 --- a/gcloud/alpha/access-context-manager/cloud-bindings/create +++ b/gcloud/alpha/access-context-manager/cloud-bindings/create @@ -18,17 +18,18 @@ DESCRIPTION ▪ a specific service account or all service accounts in a specified project. - If a group key is specified, the access level is enforced at the - organization level for all context-aware access group members, as specified - in the binding. If a restricted client application is also specified, then - the enforcement applies only to the specified application, and not to the - entire organization. If a service account is specified, then the + If a group key is specified, the access level is globally enforced for all + context-aware access group members, as specified in the binding. If a + restricted client application is also specified, then the enforcement + applies only to the specified application, and not to the entire + organization. If the restricted client application is specified, then + --binding-file cannot be set. If a service account is specified, then the enforcement applies only to the specified service account. If a service account project is specified, then the enforcement applies to all the service accounts belongs to the specified project. EXAMPLES - To create a new cloud access binding at the organization level, run: + To create a new global cloud access binding, run: $ gcloud alpha access-context-manager cloud-bindings create \ --group-key=my-group-key \ @@ -45,8 +46,23 @@ EXAMPLES --restricted-client-application-client-ids='123456789.apps.googl\ eusercontent.com' - To create a new cloud access binding for the dry run access level at the - organization level, run: + To create a new cloud access binding for particular applications using a + yaml file, run: + + $ gcloud alpha access-context-manager cloud-bindings create \ + --group-key=my-group-key --organization='1234567890' \ + --binding-file='binding.yaml' + + To create a new global cloud access binding, and for particular + applications using a yaml file, run: + + $ gcloud alpha access-context-manager cloud-bindings create \ + --group-key=my-group-key \ + --level=accessPolicies/123/accessLevels/abc \ + --organization='1234567890' --binding-file='binding.yaml' + + To create a new global cloud access binding for the dry run access level, + run: $ gcloud alpha access-context-manager cloud-bindings create \ --group-key=my-group-key \ diff --git a/gcloud/alpha/apphub/applications/create b/gcloud/alpha/apphub/applications/create index a862e9eb1..775ef1c40 100644 --- a/gcloud/alpha/apphub/applications/create +++ b/gcloud/alpha/apphub/applications/create @@ -56,9 +56,10 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --scope-type=SCOPE_TYPE - Scope of the Application. SCOPE_TYPE must be (only one value is - supported): + Scope of the Application. SCOPE_TYPE must be one of: + GLOBAL + Represents a global application REGIONAL Represents a regional application diff --git a/gcloud/alpha/apphub/help b/gcloud/alpha/apphub/help index 569709a58..dc3715f96 100644 --- a/gcloud/alpha/apphub/help +++ b/gcloud/alpha/apphub/help @@ -24,6 +24,9 @@ GROUPS discovered-workloads (ALPHA) Manage App Hub Discovered Workloads. + locations + (ALPHA) Manage App Hub Locations. + operations (ALPHA) Manage App Hub Operations (long-running operations). diff --git a/gcloud/alpha/apphub/locations/describe b/gcloud/alpha/apphub/locations/describe new file mode 100644 index 000000000..4b6f80446 --- /dev/null +++ b/gcloud/alpha/apphub/locations/describe @@ -0,0 +1,49 @@ +NAME + gcloud alpha apphub locations describe - describe an Apphub location + +SYNOPSIS + gcloud alpha apphub locations describe LOCATION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe an Apphub location. + +EXAMPLES + To describe a specific apphub location with the name my-location, run: + + $ gcloud alpha apphub locations describe my-location + +POSITIONAL ARGUMENTS + Location resource - Location. This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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 apphub locations describe + diff --git a/gcloud/alpha/apphub/locations/help b/gcloud/alpha/apphub/locations/help new file mode 100644 index 000000000..ca18b039f --- /dev/null +++ b/gcloud/alpha/apphub/locations/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha apphub locations - manage App Hub Locations + +SYNOPSIS + gcloud alpha apphub locations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Commands for getting and listing locations where App Hub is + available. + +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) Describe an Apphub location. + + list + (ALPHA) List Apphub locations. + +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 apphub locations + diff --git a/gcloud/alpha/apphub/locations/list b/gcloud/alpha/apphub/locations/list new file mode 100644 index 000000000..163d8f439 --- /dev/null +++ b/gcloud/alpha/apphub/locations/list @@ -0,0 +1,64 @@ +NAME + gcloud alpha apphub locations list - list Apphub locations + +SYNOPSIS + gcloud alpha apphub locations list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Apphub locations. + +EXAMPLES + To list all apphub locations, run: + + $ gcloud alpha apphub locations list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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 apphub locations list + diff --git a/gcloud/alpha/assured/workloads/create b/gcloud/alpha/assured/workloads/create index d71906c23..39fcf8c66 100644 --- a/gcloud/alpha/assured/workloads/create +++ b/gcloud/alpha/assured/workloads/create @@ -10,6 +10,7 @@ SYNOPSIS [--external-identifier=EXTERNAL_IDENTIFIER] [--labels=[KEY=VALUE,...]] [--next-rotation-time=NEXT_ROTATION_TIME] [--partner=PARTNER] [--partner-permissions=[KEY=VALUE,...]] + [--partner-services-billing-account=PARTNER_SERVICES_BILLING_ACCOUNT] [--provisioned-resources-parent=PROVISIONED_RESOURCES_PARENT] [--resource-settings=[KEY=VALUE,...]] [--rotation-period=ROTATION_PERIOD] [GCLOUD_WIDE_FLAG ...] @@ -32,6 +33,7 @@ EXAMPLES ▪ with the label: key = 'LabelKey2', value = 'LabelValue2' ▪ provisioned resources parent 'folders/789' ▪ with custom project id 'my-custom-id' for consumer project + ▪ with external identifier for the workload of 'external-id' $ gcloud alpha assured workloads create --organization=123 \ --location=us-central1 --display-name=Test-Workload \ @@ -41,7 +43,40 @@ EXAMPLES --rotation-period=172800s \ --labels=LabelKey1=LabelValue1,LabelKey2=LabelValue2 \ --provisioned-resources-parent=folders/789 \ - --resource-settings=consumer-project-id=my-custom-id + --resource-settings=consumer-project-id=my-custom-id \ + --external-identifier=external-id + + The following example command creates a new Partner Assured Workloads, with + the following properties: + + ▪ belonging to an organization with ID 123 + ▪ located in the me-central2 region + ▪ display name Test-Workload + ▪ partner CNTXT + ▪ partner services billing account billingAccounts/789 + ▪ billing account billingAccounts/456 + ▪ data logs viewer partner permission enabled + ▪ first key rotation set for 10:15am on the December 30, 2020 + ▪ key rotation interval set for every 48 hours + ▪ with the label: key = 'LabelKey1', value = 'LabelValue1' + ▪ with the label: key = 'LabelKey2', value = 'LabelValue2' + ▪ provisioned resources parent 'folders/789' + ▪ with custom project id 'my-custom-id' for consumer project + ▪ with external identifier for the workload of 'external-id' + + $ gcloud alpha assured workloads create --organization=123 \ + --location=me-central2 --display-name=Test-Workload \ + --compliance-regime=ASSURED_WORKLOADS_FOR_PARTNERS \ + --partner=SOVEREIGN_CONTROLS_BY_CNTXT \ + --partner-services-billing-account=billingAccounts/\ + 01BF3F-2C6DE5-30C607 --partner-permissions=data-logs-viewer=true \ + --billing-account=billingAccounts/456 \ + --next-rotation-time=2020-12-30T10:15:00.00Z \ + --rotation-period=172800s \ + --labels=LabelKey1=LabelValue1,LabelKey2=LabelValue2 \ + --provisioned-resources-parent=folders/789 \ + --resource-settings=consumer-project-id=my-custom-id \ + --external-identifier=external-id REQUIRED FLAGS --billing-account=BILLING_ACCOUNT @@ -85,12 +120,20 @@ OPTIONAL FLAGS --partner=PARTNER The partner choice when creating a workload managed by local trusted partners. PARTNER must be one of: LOCAL_CONTROLS_BY_S3NS, - SOVEREIGN_CONTROLS_BY_T_SYSTEMS. + SOVEREIGN_CONTROLS_BY_T_SYSTEMS, SOVEREIGN_CONTROLS_BY_CNTXT, + SOVEREIGN_CONTROLS_BY_CNTXT_NO_EKM. --partner-permissions=[KEY=VALUE,...] The partner permissions for the partner regime, for example, data-logs-viewer=true/false + --partner-services-billing-account=PARTNER_SERVICES_BILLING_ACCOUNT + Billing account necessary for purchasing services from Sovereign + Partners. This field is required for creating SIA/PSN/CNTXT partner + workloads. The caller should have 'billing.resourceAssociations.create' + IAM permission on this billing-account. The format of this string is + billingAccounts/AAAAAA-BBBBBB-CCCCCC + --provisioned-resources-parent=PROVISIONED_RESOURCES_PARENT The parent of the provisioned projects, for example, folders/{FOLDER_ID} diff --git a/gcloud/alpha/backup-dr/backup-plan-associations/create b/gcloud/alpha/backup-dr/backup-plan-associations/create new file mode 100644 index 000000000..c151e3fe8 --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-plan-associations/create @@ -0,0 +1,116 @@ +NAME + gcloud alpha backup-dr backup-plan-associations create - create a new + backup plan association + +SYNOPSIS + gcloud alpha backup-dr backup-plan-associations create + (BACKUP_PLAN_ASSOCIATION + : --location=LOCATION --workload-project=WORKLOAD_PROJECT) + --backup-plan=BACKUP_PLAN --resource=RESOURCE [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new backup plan association in the project. It can only be + created in locations where Backup and DR is available. + +EXAMPLES + To create a new backup plan association sample-bpa in project + sample-project and location us-central1 for resource sample-resource-uri + with backup plan sample-backup-plan, run: + + $ gcloud alpha backup-dr backup-plan-associations create \ + sample-bpa --project=sample-project --location=us-central1 \ + --backup-plan=sample-backup-plan --resource=sample-resource-uri + +POSITIONAL ARGUMENTS + Backup Plan Association resource - Name of the backup plan association to + be created. Once the backup plan association is created, this name can't + be changed. The name must be unique for a project and location. To create + backup plan associations in a project that's different from the backup + plan, use the --workload-project flag. The arguments in this group can be + used to specify the attributes of this resource. + + This must be specified. + + BACKUP_PLAN_ASSOCIATION + ID of the Backup Plan Association or fully qualified identifier for + the Backup Plan Association. + + To set the name attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Backup Plan Association. + + To set the location attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + + --workload-project=WORKLOAD_PROJECT + Cloud project id for the Backup Plan Association. + + To set the workload-project attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION on the command line + with a fully specified name; + ▸ provide the argument --workload-project on the command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + +REQUIRED FLAGS + Backup Plan resource - The backup plan to be applied to the resource. + E.g., + projects/sample-project/locations/us-central1/backupPlans/sample-backup-plan + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --backup-plan on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument --backup-plan on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + --backup-plan=BACKUP_PLAN + ID of the Backup Plan or fully qualified identifier for the Backup + Plan. + + To set the name attribute: + ▸ provide the argument --backup-plan on the command line. + + --resource=RESOURCE + The resource to which the backup plan is to be applied. E.g., + projects/sample-project/zones/us-central1-a/instances/sample-instance + +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, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Creates a new backup plan association + +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/backup-dr/backup-plan-associations/delete b/gcloud/alpha/backup-dr/backup-plan-associations/delete new file mode 100644 index 000000000..a11455c6c --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-plan-associations/delete @@ -0,0 +1,78 @@ +NAME + gcloud alpha backup-dr backup-plan-associations delete - delete the + specified backup plan association + +SYNOPSIS + gcloud alpha backup-dr backup-plan-associations delete + (BACKUP_PLAN_ASSOCIATION + : --location=LOCATION --workload-project=WORKLOAD_PROJECT) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete the specified backup plan association. + +EXAMPLES + To delete a backup plan association sample-bpa in project sample-project + and location us-central1 , run: + + $ gcloud alpha backup-dr backup-plan-associations delete \ + sample-bpa --project=sample-project --location=us-central1 + +POSITIONAL ARGUMENTS + Backup Plan Association resource - Name of the backup plan association to + delete. The arguments in this group can be used to specify the attributes + of this resource. + + This must be specified. + + BACKUP_PLAN_ASSOCIATION + ID of the Backup Plan Association or fully qualified identifier for + the Backup Plan Association. + + To set the name attribute: + ▸ provide the argument backup_plan_association on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Backup Plan Association. + + To set the location attribute: + ▸ provide the argument backup_plan_association on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + + --workload-project=WORKLOAD_PROJECT + Cloud project id for the Backup Plan Association. + + To set the workload-project attribute: + ▸ provide the argument backup_plan_association on the command line + with a fully specified name; + ▸ provide the argument --workload-project on the command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + +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, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Delete a specific backup plan association + +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/backup-dr/backup-plan-associations/describe b/gcloud/alpha/backup-dr/backup-plan-associations/describe new file mode 100644 index 000000000..bf6541860 --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-plan-associations/describe @@ -0,0 +1,68 @@ +NAME + gcloud alpha backup-dr backup-plan-associations describe - show details of + the backup plan association + +SYNOPSIS + gcloud alpha backup-dr backup-plan-associations describe + (BACKUP_PLAN_ASSOCIATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show all configuration data associated with the specified backup + plan association. + +EXAMPLES + To view details for backup plan association BACKUP_PLAN_ASSOCIATION, run: + + $ gcloud alpha backup-dr backup-plan-associations describe \ + BACKUP_PLAN_ASSOCIATION + +POSITIONAL ARGUMENTS + Backup plan association resource - Name of the backup plan association 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_plan_association on the command line with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + BACKUP_PLAN_ASSOCIATION + ID of the backup_plan_association or fully qualified identifier for + the backup_plan_association. + + To set the backup_plan_association attribute: + ▸ provide the argument backup_plan_association on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument backup_plan_association on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +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/backup-dr/backup-plan-associations/help b/gcloud/alpha/backup-dr/backup-plan-associations/help new file mode 100644 index 000000000..bd39ff2eb --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-plan-associations/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha backup-dr backup-plan-associations - manage Backup and DR + backup plan associations + +SYNOPSIS + gcloud alpha backup-dr backup-plan-associations COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Backup and DR backup plan associations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a new backup plan association. + + delete + (ALPHA) Delete the specified backup plan association. + + describe + (ALPHA) Show details of the backup plan association. + + list + (ALPHA) List Backup and DR backup plan associations. + + trigger-backup + (ALPHA) Create an on-demand backup for a 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/backup-dr/backup-plan-associations/list b/gcloud/alpha/backup-dr/backup-plan-associations/list new file mode 100644 index 000000000..8b9682a6b --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-plan-associations/list @@ -0,0 +1,92 @@ +NAME + gcloud alpha backup-dr backup-plan-associations list - list Backup and DR + backup plan associations + +SYNOPSIS + gcloud alpha backup-dr backup-plan-associations list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List backup plan associations in the project for a specified + location. + +EXAMPLES + To list backup plan associations for all locations, run: + + $ gcloud alpha backup-dr backup-plan-associations list + + To list backup plan associations in a location my-location, run: + + $ gcloud alpha backup-dr backup-plan-associations list \ + --location=my-location + +FLAGS + Location resource - Location for which backup plan associations should be + listed. This represents a Cloud resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ default is all locations with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --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; + ▸ default is all locations . + +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 backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +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/backup-dr/backup-plan-associations/trigger-backup b/gcloud/alpha/backup-dr/backup-plan-associations/trigger-backup new file mode 100644 index 000000000..cbfdb4a5b --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-plan-associations/trigger-backup @@ -0,0 +1,86 @@ +NAME + gcloud alpha backup-dr backup-plan-associations trigger-backup - create an + on-demand backup for a resource + +SYNOPSIS + gcloud alpha backup-dr backup-plan-associations trigger-backup + (BACKUP_PLAN_ASSOCIATION + : --location=LOCATION --workload-project=WORKLOAD_PROJECT) + --backup-rule-id=BACKUP_RULE_ID [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create an on-demand backup for a resource. Trigger an on demand + backup for the given backup rule. + +EXAMPLES + To trigger an on demand backup for a backup plan association sample-bpa in + project sample-project and location us-central1 with backup rule + sample-backup-rule, run: + + $ gcloud alpha backup-dr backup-plan-associations trigger-backup \ + sample-bpa --project=sample-project --location=us-central1 \ + --backup-rule-id=sample-backup-rule + +POSITIONAL ARGUMENTS + Backup Plan Association resource - Name of an existing backup plan + association to use for creating an on-demand backup. The arguments in this + group can be used to specify the attributes of this resource. + + This must be specified. + + BACKUP_PLAN_ASSOCIATION + ID of the Backup Plan Association or fully qualified identifier for + the Backup Plan Association. + + To set the name attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Backup Plan Association. + + To set the location attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + + --workload-project=WORKLOAD_PROJECT + Cloud project id for the Backup Plan Association. + + To set the workload-project attribute: + ▸ provide the argument BACKUP_PLAN_ASSOCIATION on the command line + with a fully specified name; + ▸ provide the argument --workload-project on the command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + +REQUIRED FLAGS + --backup-rule-id=BACKUP_RULE_ID + Name of an existing backup rule to use for creating an on-demand + backup. + +OPTIONAL FLAGS + --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, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Create an on-demand 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. + diff --git a/gcloud/alpha/backup-dr/backup-plans/create b/gcloud/alpha/backup-dr/backup-plans/create new file mode 100644 index 000000000..346449fa3 --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-plans/create @@ -0,0 +1,248 @@ +NAME + gcloud alpha backup-dr backup-plans create - creates a new Backup Plan + +SYNOPSIS + gcloud alpha backup-dr backup-plans create + (BACKUP_PLAN : --location=LOCATION) --backup-rule=[PROPERTY=VALUE,...] + --backup-vault=BACKUP_VAULT --resource-type=RESOURCE_TYPE [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new backup plan in the project. It can only be created in + locations where Backup and DR is available. + +EXAMPLES + To create a new backup plan sample-backup-plan in project sample-project, + at location us-central1, with resource-type + compute..com/Instance and backup-vault backup-vault with 2 + backup-rules: + + run: + + $ gcloud alpha backup-dr backup-plans create sample-backup-plan \ + --project=sample-project --location=us-central1 \ + --resource-type 'compute..com/Instance' \ + --backup-vault --backup-rule \ + --backup-rule + + Backup Rule Examples: + + 1. Hourly backup rule with hourly backup frequency of 6 hours and store it + for 30 days, and expect the backups to run only between 10:00 to 20:00 UTC + + : + rule-id=sample-hourly-rule,retention-days=30,recurrence=HOURLY,hourly-frequency=6,time-zone=UTC,backup-window-start=10,backup-window-end=20 + + Properties: + ▪ rule-id = "sample-hourly-rule" + ▪ retention-days = 30 + ▪ recurrence = HOURLY + ▪ hourly-frequency = 6 + ▪ time-zone = UTC + ▪ backup-window-start = 10 + ▪ backup-window-end = 20 + + 2. Daily backup rule with daily backup frequency of 6 hours and store it + for 7 days + + : + rule-id=sample-daily-rule,retention-days=7,recurrence=DAILY,backup-window-start=1,backup-window-end=14 + + Properties: + ▪ rule-id = "sample-daily-rule" + ▪ retention-days = 7 + ▪ recurrence = DAILY + ▪ backup-window-start = 1 + ▪ backup-window-end = 14 + + 3. Weekly backup rule with weekly backup frequency on every MONDAY & FRIDAY + and store it for 21 days + + : + rule-id=sample-weekly-rule,retention-days=21,recurrence=WEEKLY,days-of-week="MONDAY + FRIDAY",backup-window-start=10,backup-window-end=20 + + Properties: + ▪ rule-id = "sample-weekly-rule" + ▪ retention-days: 21 + ▪ recurrence = WEEKLY + ▪ days-of-week = "MONDAY FRIDAY" + ▪ backup-window-start = 10 + ▪ backup-window-end = 20 + +POSITIONAL ARGUMENTS + Backup Plan resource - Name of the backup plan to be created. Once the + backup plan is created, this name can't be changed. The name must be + unique for a project and location. 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_PLAN 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. + + BACKUP_PLAN + ID of the Backup Plan or fully qualified identifier for the Backup + Plan. + + To set the name attribute: + ▸ provide the argument BACKUP_PLAN on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Backup Plan. + + To set the location attribute: + ▸ provide the argument BACKUP_PLAN on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --backup-rule=[PROPERTY=VALUE,...] + Backup rule that defines parameters for when and how a backup is + created. This flag can be repeated to create more backup rules. + + Parameters for the backup rule include: + + rule-id + Name of the backup rule. The name must be unique and start with a + lowercase letter followed by up to 62 lowercase letters, numbers, + or hyphens. + + retention-days + Duration for which backup data should be retained. It must be + defined in "days". The value should be greater than or equal to the + enforced retention period set for the backup vault. + + recurrence + Frequency for the backup schedule. It must be either: HOURLY, + DAILY, WEEKLY, MONTHLY or YEARLY. + + backup-window-start + Start time of the interval during which backup jobs should be + executed. It can be defined as backup-window-start=2, that means + backup window starts at 2 a.m. The start time and end time must + have an interval of 6 hours. + + backup-window-end + End time of the interval during which backup jobs should be + executed. It can be defined as backup-window-end=14, that means + backup window ends at 2 p.m. The start time and end time must have + an interval of 6 hours. + + Jobs are queued at the beginning of the window and will be marked + as SKIPPED if they do not start by the end time. Jobs that are in + progress will not be canceled at the end time. + + time-zone + The time zone to be used for the backup schedule. The value must + exist in the IANA tz database (https://www.iana.org/time-zones). + The default value is UTC. E.g., Europe/Paris + + Following flags are mutually exclusive: + + hourly-frequency + Frequency for hourly backups. An hourly frequency of 2 means backup + jobs will run every 2 hours from start time till the end time + defined. The hourly frequency must be between 6 and 23. The value + is needed only if recurrence type is HOURLY. + + days-of-week + Days of the week when the backup job should be executed. The value + is needed if recurrence type is WEEKLY. E.g., MONDAY,TUESDAY + + days-of-month + Days of the month when the backup job should be executed. The value + is needed only if recurrence type is YEARLY. E.g.,"1,5,14" + + months + Month for the backup schedule. The value is needed only if + recurrence type is YEARLY. E.g., JANUARY, MARCH + + week-day-of-month + Recurring day of the week in the month or year when the backup job + should be executed. E.g. FIRST-SUNDAY, THIRD-MONDAY. The value can + only be provided if the recurrence type is MONTHLY or YEARLY. + Allowed values for the number of week - FIRST, SECOND, THIRD, + FOURTH, LAST. Allowed values for days of the week - MONDAY to + SUNDAY. + + E.g., + "rule-id=sample-daily-rule,recurrence=WEEKLY,backup-window-start=2,backup-window-end=14,retention-days=20,days-of-week='SUNDAY + MONDAY'" + + Backup Vault resource - The backup vault where the backups gets stored + using this backup plan. This represents a Cloud resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument --backup-vault on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument --backup-vault on the command line with a fully + specified name; + ◆ provide the argument --location on the command line. + + This must be specified. + + --backup-vault=BACKUP_VAULT + ID of the Backup Vault or fully qualified identifier for the Backup + Vault. + + To set the name attribute: + ▸ provide the argument --backup-vault on the command line. + + --resource-type=RESOURCE_TYPE + Type of resource to which the backup plan should be applied. E.g., + compute..com/Instance + +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 + Provide a description of the backup plan, such as specific use cases + and relevant details, in 2048 characters or less. + + E.g., This is a backup plan that performs a daily backup at 6 p.m. and + retains data for 3 months. + + --labels=[KEY=VALUE,...] + If you have assigned labels to your resources for grouping, you can + provide the label using this flag.A label is a key-value pair. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Creates a new backup plan + +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/backup-dr/backup-plans/delete b/gcloud/alpha/backup-dr/backup-plans/delete new file mode 100644 index 000000000..aeef7be17 --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-plans/delete @@ -0,0 +1,72 @@ +NAME + gcloud alpha backup-dr backup-plans delete - deletes a Backup Plan + +SYNOPSIS + gcloud alpha backup-dr backup-plans delete + (BACKUP_PLAN : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes a Backup Plan. + +EXAMPLES + To delete a backup plan sample-backup-plan in project sample-project and + location us-central1 , run: + + $ gcloud alpha backup-dr backup-plans delete sample-backup-plan \ + --project=sample-project --location=us-central1 + +POSITIONAL ARGUMENTS + Backup Plan resource - Name of the backup plan 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_plan 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. + + BACKUP_PLAN + ID of the Backup Plan or fully qualified identifier for the Backup + Plan. + + To set the name attribute: + ▸ provide the argument backup_plan on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Backup Plan. + + To set the location attribute: + ▸ provide the argument backup_plan on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. 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, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Deletes a specific backup plan + +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/backup-dr/backup-plans/describe b/gcloud/alpha/backup-dr/backup-plans/describe new file mode 100644 index 000000000..95d9c9537 --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-plans/describe @@ -0,0 +1,66 @@ +NAME + gcloud alpha backup-dr backup-plans describe - show details of the backup + plan + +SYNOPSIS + gcloud alpha backup-dr backup-plans describe + (BACKUP_PLAN : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show all data associated with the specified backup plan. + +EXAMPLES + To view details for backup plan 'BACKUP_PLAN', run: + + $ gcloud alpha backup-dr backup-plans describe BACKUP_PLAN + +POSITIONAL ARGUMENTS + Backup plan resource - Name of the backup plan 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_plan 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. + + BACKUP_PLAN + ID of the backup_plan or fully qualified identifier for the + backup_plan. + + To set the backup_plan attribute: + ▸ provide the argument backup_plan on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument backup_plan on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +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/backup-dr/backup-plans/help b/gcloud/alpha/backup-dr/backup-plans/help new file mode 100644 index 000000000..7eb85865b --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-plans/help @@ -0,0 +1,35 @@ +NAME + gcloud alpha backup-dr backup-plans - manage Backup and DR backup plans + +SYNOPSIS + gcloud alpha backup-dr backup-plans COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Backup and DR backup plans. + +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 Backup Plan. + + delete + (ALPHA) Deletes a Backup Plan. + + describe + (ALPHA) Show details of the backup plan. + + list + (ALPHA) List backup plans in the 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. + diff --git a/gcloud/alpha/backup-dr/backup-plans/list b/gcloud/alpha/backup-dr/backup-plans/list new file mode 100644 index 000000000..aa54b9850 --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-plans/list @@ -0,0 +1,89 @@ +NAME + gcloud alpha backup-dr backup-plans list - list backup plans in the project + +SYNOPSIS + gcloud alpha backup-dr backup-plans list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List backup plans in the project. + +EXAMPLES + To list backup plans for all locations, run: + + $ gcloud alpha backup-dr backup-plans list + + To list backup plans in a location "my-location", run: + + $ gcloud alpha backup-dr backup-plans list --location=my-location + +FLAGS + Location resource - Location for which backup plans should be listed. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ default is all locations with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --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; + ▸ default is all locations . + +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 backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +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/backup-dr/backup-vaults/create b/gcloud/alpha/backup-dr/backup-vaults/create new file mode 100644 index 000000000..b99269aca --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-vaults/create @@ -0,0 +1,121 @@ +NAME + gcloud alpha backup-dr backup-vaults create - create a Backup and DR backup + vault + +SYNOPSIS + gcloud alpha backup-dr backup-vaults create + (BACKUP_VAULT : --location=LOCATION) + --backup-min-enforced-retention=BACKUP_MIN_ENFORCED_RETENTION + [--no-async] [--description=DESCRIPTION] + [--effective-time=EFFECTIVE_TIME] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Backup and DR backup vault. + +EXAMPLES + To create a new backup vault BACKUP_VAULT in location MY_LOCATION with + minimum enforced-retention for backups of 1 month and 1 day, run: + + $ gcloud alpha backup-dr backup-vaults create BACKUP_VAULT \ + --location=MY_LOCATION --backup-min-enforced-retention="p1m1d" + + To create a new backup vault BACKUP_VAULT in location MY_LOCATION with + minimum enforced-retention for backups of 1 day and description + DESCRIPTION, run: + + $ gcloud alpha backup-dr backup-vaults create BACKUP_VAULT \ + --location=MY_LOCATION --backup-min-enforced-retention="1d" \ + --description=DESCRIPTION + + To create a new backup vault BACKUP_VAULT in location MY_LOCATION with + minimum enforced-retention for backups of 1 day and label key1 with value + value1, run: + + $ gcloud alpha backup-dr backup-vaults create BACKUP_VAULT \ + --location=MY_LOCATION --backup-min-enforced-retention="1d" \ + --labels=key1=value1 + + To create a new backup vault BACKUP_VAULT in location MY_LOCATION with + minimum enforced-retention for backups of 1 day and effective-time + "2024-03-22", run: + + $ gcloud alpha backup-dr backup-vaults create BACKUP_VAULT \ + --location=MY_LOCATION --backup-min-enforced-retention="1d" \ + --effective-time="2024-03-22" + +POSITIONAL ARGUMENTS + Backup Vault resource - Name of the backup vault to create. A vault name + cannot be changed after creation. It must be between 3-63 characters long + and must be unique within the project and location. 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_vault on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + BACKUP_VAULT + ID of the Backup Vault or fully qualified identifier for the Backup + Vault. + + To set the name attribute: + ▸ provide the argument backup_vault on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Backup Vault. + + To set the location attribute: + ▸ provide the argument backup_vault on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --backup-min-enforced-retention=BACKUP_MIN_ENFORCED_RETENTION + Backups will be kept for this minimum period before they can be + deleted. Once the effective time is reached, the enforced retention + period cannot be decreased or removed. + +OPTIONAL FLAGS + --no-async + Wait for the operation in progress to complete. + + --description=DESCRIPTION + Optional description for the backup vault (2048 characters or less). + + --effective-time=EFFECTIVE_TIME + The time at which the enforced retention period becomes locked. This + flag is mutually exclusive with --unlock-backup-min-enforced-retention. + + --labels=[KEY=VALUE,...] + Optional resource labels to represent metadata provided by the user. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +BRIEF + Creates a Backup and DR backup vault. + +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/backup-dr/backup-vaults/delete b/gcloud/alpha/backup-dr/backup-vaults/delete new file mode 100644 index 000000000..eff51a879 --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-vaults/delete @@ -0,0 +1,94 @@ +NAME + gcloud alpha backup-dr backup-vaults delete - delete the specified Backup + Vault + +SYNOPSIS + gcloud alpha backup-dr backup-vaults delete + (BACKUP_VAULT : --location=LOCATION) [--allow-missing] [--no-async] + [--force-delete] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete the specified Backup Vault. + +EXAMPLES + To delete a backup vault BACKUP_VAULT in location MY_LOCATION, run: + + $ gcloud alpha backup-dr backup-vaults delete BACKUP_VAULT \ + --location=MY_LOCATION + + To override restrictions against the deletion of a backup vault + BACKUP_VAULT in location MY_LOCATION, run: + + $ gcloud alpha backup-dr backup-vaults delete BACKUP_VAULT \ + --location=MY_LOCATION --force-delete + +POSITIONAL ARGUMENTS + Backup Vault resource - Name of the backup vault to delete. Before you + delete, take a look at the prerequisites here + (https://cloud.google.com/backup-disaster-recovery/docs/configuration/decommission). + 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_vault on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + BACKUP_VAULT + ID of the Backup Vault or fully qualified identifier for the Backup + Vault. + + To set the name attribute: + ▸ provide the argument backup_vault on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Backup Vault. + + To set the location attribute: + ▸ provide the argument backup_vault on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --allow-missing + Allow idempotent deletion of backup vault. The request will still + succeed in case the backup vault does not exist. + + --no-async + Wait for the operation in progress to complete. + + --force-delete + If set, the following restrictions against deletion of the backup vault + instance can be overridden: * deletion of a backup vault instance + containing no backups,but still contains empty datasources. * deletion + of a backup vault instance containing no backups,but still contains + empty datasources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +BRIEF + Deletes a specific backup vault + +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/backup-dr/backup-vaults/describe b/gcloud/alpha/backup-dr/backup-vaults/describe new file mode 100644 index 000000000..2902fb5d1 --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-vaults/describe @@ -0,0 +1,69 @@ +NAME + gcloud alpha backup-dr backup-vaults describe - show the metadata for a + Backup and DR backup vault + +SYNOPSIS + gcloud alpha backup-dr backup-vaults describe + (BACKUP_VAULT : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show the metadata for a Backup and DR backup vault. + +EXAMPLES + To view details associated with backup vault 'BACKUP_VAULT', run: + + $ gcloud alpha backup-dr backup-vaults describe BACKUP_VAULT + +POSITIONAL ARGUMENTS + Backup Vault resource - Name of the backup vault to retreive metadata of. + 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_vault on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + BACKUP_VAULT + ID of the Backup Vault or fully qualified identifier for the Backup + Vault. + + To set the name attribute: + ▸ provide the argument backup_vault on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Backup Vault. + + To set the location attribute: + ▸ provide the argument backup_vault on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +BRIEF + Show the metadata for a Backup and DR backup vault. + +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/backup-dr/backup-vaults/help b/gcloud/alpha/backup-dr/backup-vaults/help new file mode 100644 index 000000000..6bee153c1 --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-vaults/help @@ -0,0 +1,38 @@ +NAME + gcloud alpha backup-dr backup-vaults - manage Backup and DR backup vaults + +SYNOPSIS + gcloud alpha backup-dr backup-vaults COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Backup and DR backup vaults. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a Backup and DR backup vault. + + delete + (ALPHA) Delete the specified Backup Vault. + + describe + (ALPHA) Show the metadata for a Backup and DR backup vault. + + list + (ALPHA) List Backup and DR backup vaults. + + update + (ALPHA) Update a Backup and DR backup vault. + +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/backup-dr/backup-vaults/list b/gcloud/alpha/backup-dr/backup-vaults/list new file mode 100644 index 000000000..10e6d9c10 --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-vaults/list @@ -0,0 +1,93 @@ +NAME + gcloud alpha backup-dr backup-vaults list - list Backup and DR backup + vaults + +SYNOPSIS + gcloud alpha backup-dr backup-vaults list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Backup and DR backup vaults. + +EXAMPLES + To list backup vaults in all location, run: + + $ gcloud alpha backup-dr backup-vaults list + + To list backup vaults in a location ''my-location'', run: + + $ gcloud alpha backup-dr backup-vaults list --location=my-location + +FLAGS + Location resource - Location for which backup vaults should be listed. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ Defaults to all locations with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --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; + ▸ Defaults to all locations. + +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 backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +BRIEF + List Backup and DR backup vaults. + +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/backup-dr/backup-vaults/update b/gcloud/alpha/backup-dr/backup-vaults/update new file mode 100644 index 000000000..0d5e4de9e --- /dev/null +++ b/gcloud/alpha/backup-dr/backup-vaults/update @@ -0,0 +1,112 @@ +NAME + gcloud alpha backup-dr backup-vaults update - update a Backup and DR backup + vault + +SYNOPSIS + gcloud alpha backup-dr backup-vaults update + (BACKUP_VAULT : --location=LOCATION) [--no-async] + [--backup-min-enforced-retention=BACKUP_MIN_ENFORCED_RETENTION] + [--description=DESCRIPTION] [--effective-time=EFFECTIVE_TIME] + [--force-update] [--unlock-backup-min-enforced-retention] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Backup and DR backup vault. + +EXAMPLES + To update a backup vault BACKUP_VAULT in location MY_LOCATION with one + update field, run: + + $ gcloud alpha backup-dr backup-vaults update BACKUP_VAULT \ + --location=MY_LOCATION --effective-time="2024-03-22" + + To update a backup vault BACKUP_VAULT in location MY_LOCATION with multiple + update fields, run: + + $ gcloud alpha backup-dr backup-vaults update BACKUP_VAULT \ + --location=MY_LOCATION \ + --backup-min-enforced-retention="400000s" \ + --description="Updated backup vault" + +POSITIONAL ARGUMENTS + Backup Vault resource - Name of the existing backup vault 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_vault on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + BACKUP_VAULT + ID of the Backup Vault or fully qualified identifier for the Backup + Vault. + + To set the name attribute: + ▸ provide the argument backup_vault on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location of the Backup Vault. + + To set the location attribute: + ▸ provide the argument backup_vault on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --no-async + Wait for the operation in progress to complete. + + --backup-min-enforced-retention=BACKUP_MIN_ENFORCED_RETENTION + Backups will be kept for this minimum period before they can be + deleted. Once the effective time is reached, the enforced retention + period cannot be decreased or removed. + + --description=DESCRIPTION + Optional description for the backup vault (2048 characters or less). + + --effective-time=EFFECTIVE_TIME + The time at which the enforced retention period becomes locked. This + flag is mutually exclusive with --unlock-backup-min-enforced-retention. + + --force-update + If set, allow update to extend the minimum enforced retention for + backup vault. This overrides the restriction against conflicting + retention periods. This conflict may occur when the expiration schedule + defined by the associated backup plan is shorter than the minimum + retention set by the backup vault. + + --unlock-backup-min-enforced-retention + Removes the lock on the backup minimum enforced retention period, and + resets the effective time. When unlocked, the enforced retention period + can be changed at any time. This flag is mutually exclusive with + --effective-time. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +BRIEF + Updates a Backup and DR backup vault. + +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/backup-dr/backups/delete b/gcloud/alpha/backup-dr/backups/delete new file mode 100644 index 000000000..a7ef32438 --- /dev/null +++ b/gcloud/alpha/backup-dr/backups/delete @@ -0,0 +1,90 @@ +NAME + gcloud alpha backup-dr backups delete - delete the specified Backup + +SYNOPSIS + gcloud alpha backup-dr backups delete + (BACKUP : --backup-vault=BACKUP_VAULT + --data-source=DATA_SOURCE --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete the specified Backup. + +EXAMPLES + To delete a backup sample-backup in backup vault sample-vault, data source + sample-ds, project sample-project and location us-central1 , run: + + $ gcloud alpha backup-dr backups delete sample-backup \ + --backup-vault=sample-vault --data-source=sample-ds \ + --project=sample-project --location=us-central1 + +POSITIONAL ARGUMENTS + Backup resource - Name of the backup 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + BACKUP + ID of the Backup or fully qualified identifier for the Backup. + + To set the name attribute: + ▸ provide the argument backup on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --backup-vault on the command line. + + --data-source=DATA_SOURCE + The ID of the Data Source. + + To set the data-source attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --data-source on the command line. + + --location=LOCATION + The location of the Backup. + + To set the location attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. 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, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Deletes a specific 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. + diff --git a/gcloud/alpha/backup-dr/backups/describe b/gcloud/alpha/backup-dr/backups/describe new file mode 100644 index 000000000..b6ad045e2 --- /dev/null +++ b/gcloud/alpha/backup-dr/backups/describe @@ -0,0 +1,81 @@ +NAME + gcloud alpha backup-dr backups describe - show details of the backup + +SYNOPSIS + gcloud alpha backup-dr backups describe + (BACKUP : --backup-vault=BACKUP_VAULT + --data-source=DATA_SOURCE --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show all data associated with the specified backup. + +EXAMPLES + To view details for backup 'BACKUP', run: + + $ gcloud alpha backup-dr backups describe BACKUP + +POSITIONAL ARGUMENTS + Backup resource - Name of the backup 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + 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 argument must be specified if any of the other + arguments in this group are specified. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --backup-vault on the command line. + + --data-source=DATA_SOURCE + The ID of the Data Source. + + To set the data-source attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --data-source on the command line. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +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/backup-dr/backups/help b/gcloud/alpha/backup-dr/backups/help new file mode 100644 index 000000000..c7e4eab07 --- /dev/null +++ b/gcloud/alpha/backup-dr/backups/help @@ -0,0 +1,38 @@ +NAME + gcloud alpha backup-dr backups - manage Backup and DR backups + +SYNOPSIS + gcloud alpha backup-dr backups GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Backup and DR backups. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + restore + (ALPHA) Manage restore operations for resources. + +COMMANDS + COMMAND is one of the following: + + delete + (ALPHA) Delete the specified Backup. + + describe + (ALPHA) Show details of the backup. + + list + (ALPHA) List Backups. + +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/backup-dr/backups/list b/gcloud/alpha/backup-dr/backups/list new file mode 100644 index 000000000..2871d52dd --- /dev/null +++ b/gcloud/alpha/backup-dr/backups/list @@ -0,0 +1,115 @@ +NAME + gcloud alpha backup-dr backups list - list Backups + +SYNOPSIS + gcloud alpha backup-dr backups list + [--backup-vault=BACKUP_VAULT + --data-source=DATA_SOURCE --location=LOCATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Displays all backups in a project. + +EXAMPLES + To list backups for all data sources, backup vaults and locations, run: + + $ gcloud alpha backup-dr backups list + + To list all backups for a data source my-data-source and a backup vault + my-vault in a location my-location, run: + + $ gcloud alpha backup-dr backups list --data-source=my-data-source \ + --backup-vault=my-vault --location=my-location + +FLAGS + DataSource resource - Data source to list backups 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 --data-source on the command line with a fully + specified name; + ◆ default is all data sources with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument --data-source on the command line with a + fully specified name; + ▸ default is all data sources with a fully specified name; + ▸ provide the argument --backup-vault on the command line; + ▸ default is all backup vaults . + + --data-source=DATA_SOURCE + ID of the dataSource or fully qualified identifier for the + dataSource. + + To set the data-source attribute: + ▸ provide the argument --data-source on the command line; + ▸ default is all data sources . + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument --data-source on the command line with a + fully specified name; + ▸ default is all data sources with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ default is all locations . + +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 backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +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/backup-dr/backups/restore/compute b/gcloud/alpha/backup-dr/backups/restore/compute new file mode 100644 index 000000000..fe5951f4b --- /dev/null +++ b/gcloud/alpha/backup-dr/backups/restore/compute @@ -0,0 +1,423 @@ +NAME + gcloud alpha backup-dr backups restore compute - restores a Compute Engine + VM Backup + +SYNOPSIS + gcloud alpha backup-dr backups restore compute + (BACKUP : --backup-vault=BACKUP_VAULT + --data-source=DATA_SOURCE --location=LOCATION) --name=NAME + --target-project=TARGET_PROJECT --target-zone=TARGET_ZONE + [--accelerator=[count=COUNT],[type=TYPE]] [--async] + [--[no-]can-ip-forward] [--confidential-compute] + [--create-disk=[PROPERTY=VALUE,...]] [--[no-]deletion-protection] + [--description=DESCRIPTION] [--[no-]enable-display-device] + [--[no-]enable-uefi-networking] [--hostname=HOSTNAME] + [--instance-kms-key=INSTANCE_KMS_KEY] + [--instance-termination-action=INSTANCE_TERMINATION_ACTION] + [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] + [--local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT] + [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] + [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--min-cpu-platform=PLATFORM] + [--min-node-cpu=MIN_NODE_CPU] + [--network-interface=[PROPERTY=VALUE,...]] + [--network-performance-configs=[PROPERTY=VALUE,...]] + [--[no-]preemptible] + [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] + [--provisioning-model=PROVISIONING_MODEL] + [--resource-manager-tags=[KEY=VALUE,...]] + [--resource-policies=RESOURCE_POLICY,[...]] [--[no-]restart-on-failure] + [--service-account=SERVICE_ACCOUNT] [--tags=TAG,[TAG,...]] + [--threads-per-core=THREADS_PER_CORE] + [--visible-core-count=VISIBLE_CORE_COUNT] + [--reservation=RESERVATION --reservation-affinity=RESERVATION_AFFINITY] + [--scopes=[SCOPE,...] | --no-scopes] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Restores a Compute Engine VM Backup. + +EXAMPLES + To restore a backup sample-backup in project sample-project and location + us-central1, with sample-data-store and sample-backup-vault, and additional + target properties, run: + + $ gcloud alpha backup-dr backups restore compute sample-backup \ + --project=sample-project --location=us-central1 \ + --backup-vault=sample-backup-vault \ + --data-source=sample-data-source -- + +POSITIONAL ARGUMENTS + Backup resource - The backup of a resource to be restored. 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + BACKUP + ID of the Backup or fully qualified identifier for the Backup. + + To set the name attribute: + ▸ provide the argument backup on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --backup-vault on the command line. + + --data-source=DATA_SOURCE + The ID of the Data Source. + + To set the data-source attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --data-source on the command line. + + --location=LOCATION + The location of the Backup. + + To set the location attribute: + ▸ provide the argument backup on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +REQUIRED FLAGS + --name=NAME + Name of the restored Compute Instance. + + --target-project=TARGET_PROJECT + Project where the restore should happen. + + --target-zone=TARGET_ZONE + Zone where the target instance is restored. + +OPTIONAL FLAGS + --accelerator=[count=COUNT],[type=TYPE] + Attaches accelerators (e.g. GPUs) to the instances. + + type + The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of + accelerator to attach to the instances. Use 'gcloud compute + accelerator-types list' to learn about all available accelerator + types. + + count + Number of accelerators to attach to each instance. The default + value is 1. + + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --[no-]can-ip-forward + If provided, allows the restored instances to send and receive packets + with non-matching destination or source IP addresses. Use + --can-ip-forward to enable and --no-can-ip-forward to disable. + + --confidential-compute + The restored instance boots with Confidential Computing enabled. + Confidential Computing is based on Secure Encrypted Virtualization + (SEV), an AMD virtualization feature for running confidential + instances. + + --create-disk=[PROPERTY=VALUE,...] + Creates and attaches persistent disks to the instances. + + name: Specifies the name of the disk. + + replica-zones: Required for each regional disk associated with the + instance. Specify the URLs of the zones where the disk should be + replicated to. You must provide exactly two replica zones, and one zone + must be the same as the instance zone. + + device-name: Device name of the disk from the source instance. + + --[no-]deletion-protection + Enables deletion protection for the restored instance. Use + --deletion-protection to enable and --no-deletion-protection to + disable. + + --description=DESCRIPTION + Specifies a textual description of the restored instance. + + --[no-]enable-display-device + Enable a display device on the restored VM instances. Disabled by + default. Use --enable-display-device to enable and + --no-enable-display-device to disable. + + --[no-]enable-uefi-networking + If set to true, enables UEFI networking for the instance creation. Use + --enable-uefi-networking to enable and --no-enable-uefi-networking to + disable. + + --hostname=HOSTNAME + Specify the hostname of the restore instance to be created. The + specified hostname must be RFC1035 compliant. If hostname is not + specified, the default hostname is + [INSTANCE_NAME].c.[TARGET_PROJECT_ID].internal when using the global + DNS, and [INSTANCE_NAME].[ZONE].c.[TARGET_PROJECT_ID].internal when + using zonal DNS. + + --instance-kms-key=INSTANCE_KMS_KEY + The Cloud KMS (Key Management Service) cryptokey that will be used to + protect the restored instance. + + Provide the full resource name of the cryptokey in the format: + projects//locations//keyRings//cryptoKeys/ + + --instance-termination-action=INSTANCE_TERMINATION_ACTION + Specifies the termination action that will be taken upon VM preemption + (--provisioning-model=SPOT) or automatic instance termination + (--max-run-duration or --termination-time). + + INSTANCE_TERMINATION_ACTION must be one of: + + DELETE + Permanently delete the VM. + STOP + Default only for Spot VMs. Stop the VM without preserving memory. + The VM can be restarted later. + + --key-revocation-action-type=POLICY + Specifies the behavior of the instance when the KMS key of one of its + attached disks is revoked. The default is none. POLICY must be one of: + ◆ none No operation is performed. + ◆ stop The instance is stopped when the KMS key of one of its + attached disks is revoked. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (), lowercase characters, and + numbers. + + --local-ssd-recovery-timeout=LOCAL_SSD_RECOVERY_TIMEOUT + Specifies the maximum amount of time a Local SSD VM should wait while + recovery of the Local SSD state is attempted. Its value should be in + between 0 and 168 hours with hour granularity and the default value + being 1 hour. + + --machine-type=MACHINE_TYPE + Specifies the machine type used for the restored instance. To get a + list of available machine types, run 'gcloud compute machine-types + list'. If unspecified, the default type will be based on the source + instance. + + This can either be the fully qualified path or the name. For example: + ◆ --machine-type=projects/my-project/zones/us-central1-a/machineTypes/n1-standard-1 + ◆ --machine-type=n1-standard-1 + + --maintenance-policy=MAINTENANCE_POLICY + Specifies the behavior of the VMs when their host machines undergo + maintenance. The default is MIGRATE. For more information, see + https://cloud.google.com/compute/docs/instances/host-maintenance-options. + MAINTENANCE_POLICY must be one of: + + MIGRATE + The instances should be migrated to a new host. This will + temporarily impact the performance of instances during a migration + event. + TERMINATE + The instances should be terminated. + + --metadata=KEY=VALUE,[KEY=VALUE,...] + Metadata to be made available to the guest operating system running on + the instances. Each metadata entry is a key/value pair separated by an + equals sign. Each metadata key must be unique and have a max of 128 + bytes in length. Each value must have a max of 256 KB in length. + Multiple arguments can be passed to this flag, e.g., --metadata + key-1=value-1,key-2=value-2,key-3=value-3. The combined total size for + all metadata entries is 512 KB. + + In images that have Compute Engine tools installed on them, such as the + official images (https://cloud.google.com/compute/docs/images), the + following metadata keys have special meanings: + + startup-script + Specifies a script that will be executed by the instances once they + start running. For convenience, --metadata-from-file can be used to + pull the value from a file. + + startup-script-url + Same as startup-script except that the script contents are pulled + from a publicly-accessible location on the web. + + For startup scripts on Windows instances, the following metadata + keys have special meanings: windows-startup-script-url, + windows-startup-script-cmd, windows-startup-script-bat, + windows-startup-script-ps1, sysprep-specialize-script-url, + sysprep-specialize-script-cmd, sysprep-specialize-script-bat, and + sysprep-specialize-script-ps1. For more information, see Running + startup scripts + (https://cloud.google.com/compute/docs/startupscript). + + --min-cpu-platform=PLATFORM + When specified, the VM will be scheduled on host with specified CPU + architecture or a newer one. To list available CPU platforms in given + zone, run: + + $ gcloud compute zones describe ZONE \ + --format="value(availableCpuPlatforms)" + + Default setting is "AUTOMATIC". + + CPU platform selection is available only in selected zones. + + You can find more information on-line: + https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform + + --min-node-cpu=MIN_NODE_CPU + Minimum number of virtual CPUs this instance will consume when running + on a sole-tenant node. + + --network-interface=[PROPERTY=VALUE,...] + Adds a network interface to the instance. This flag can be repeated to + specify multiple network interfaces. The following keys are allowed: + network, subnet, private-network-ip, internal-ipv6-address, + internal-ipv6-prefix-length, address, external-ipv6-address, + external-ipv6-prefix-length, public-ptr-domain, ipv6-public-ptr-domain, + network-tier, aliases, stack-type, queue-count, nic-type, + network-attachment + + --network-performance-configs=[PROPERTY=VALUE,...] + Configures network performance settings for the restored instance. If + this flag is not specified, the restored instance will be created with + its source instance's 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] + + --[no-]preemptible + If provided, instances will be preemptible and time-limited. Instances + might be preempted to free up resources for standard VM instances, and + will only be able to run for a limited amount of time. Preemptible + instances can not be restarted and will not migrate. Use --preemptible + to enable and --no-preemptible to disable. + + --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE + The private IPv6 Google access type for the restored VM. + PRIVATE_IPV6_GOOGLE_ACCESS_TYPE must be one of: inherit-subnetwork, + enable-bidirectional-access, enable-outbound-vm-access + + --provisioning-model=PROVISIONING_MODEL + Specifies provisioning model, which determines price, obtainability, + and runtime for the restored 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. + + --resource-manager-tags=[KEY=VALUE,...] + Specifies a list of resource manager tags to apply to the instance. + + --resource-policies=RESOURCE_POLICY,[...] + A list of resource policy names to be added to the instance. The + policies must exist in the same region as the instance. + + --[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. Use + --restart-on-failure to enable and --no-restart-on-failure to disable. + + --service-account=SERVICE_ACCOUNT + A service account is an identity attached to the instance. Its access + tokens can be accessed through the instance metadata server and are + used to authenticate applications on the instance. The account can be + set using an email address corresponding to the required service + account. If not provided, the instance will use the project's default + service account. + + --tags=TAG,[TAG,...] + Specifies a list of tags to apply to the instance. These tags allow + network firewall rules and routes to be applied to specified VM + instances. See gcloud compute firewall-rules create(1) for more + details. + + --threads-per-core=THREADS_PER_CORE + The number of visible threads per physical core. To disable + simultaneous multithreading (SMT) set this to 1. Valid values are: 1 or + 2. + + For more information about configuring SMT, see: + https://cloud.google.com/compute/docs/instances/configuring-simultaneous-multithreading. + + --visible-core-count=VISIBLE_CORE_COUNT + The number of physical cores to expose to the instance's guest + operating system. The number of virtual CPUs visible to the instance's + guest operating system is this number of cores multiplied by the + instance's count of visible threads per physical core. + + Specifies the reservation for the instance. + + --reservation=RESERVATION + The name of the reservation, required when + --reservation-affinity=specific. + + --reservation-affinity=RESERVATION_AFFINITY + Specifies the reservation affinity of the instance. + RESERVATION_AFFINITY must be one of: + + any + Consume any available, matching reservation. + none + Do not consume from any reserved capacity. + specific + Must consume from a specific reservation. + + At most one of these can be specified: + + --scopes=[SCOPE,...] + If not provided, the instance will be assigned the default scopes, + described below. However, if neither --scopes nor --no-scopes are + specified and the project has no default service account, then the + instance will be created with no scopes. Note that the level of + access that a service account has is determined by a combination of + access scopes and IAM roles so you must configure both access scopes + and IAM roles for the service account to work properly. SCOPE can be + either the full URI of the scope or an alias. Default scopes are + assigned to all instances. Available aliases are: + https://cloud.google.com/sdk/gcloud/reference/compute/instances/create#--scopes + + --no-scopes + Create the instance with no scopes. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +BRIEF + Restores the specified 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. + diff --git a/gcloud/alpha/backup-dr/backups/restore/help b/gcloud/alpha/backup-dr/backups/restore/help new file mode 100644 index 000000000..61ccc1c51 --- /dev/null +++ b/gcloud/alpha/backup-dr/backups/restore/help @@ -0,0 +1,27 @@ +NAME + gcloud alpha backup-dr backups restore - manage restore operations for + resources + +SYNOPSIS + gcloud alpha backup-dr backups restore COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage restore operations for resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + compute + (ALPHA) Restores a Compute Engine VM 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. + diff --git a/gcloud/alpha/backup-dr/data-sources/describe b/gcloud/alpha/backup-dr/data-sources/describe new file mode 100644 index 000000000..9e89526f9 --- /dev/null +++ b/gcloud/alpha/backup-dr/data-sources/describe @@ -0,0 +1,76 @@ +NAME + gcloud alpha backup-dr data-sources describe - show details of the data + source + +SYNOPSIS + gcloud alpha backup-dr data-sources describe + (DATA_SOURCE : --backup-vault=BACKUP_VAULT --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show all configuration data associated with the specified data + source. + +EXAMPLES + To view details for data source 'DATA_SOURCE', run: + + $ gcloud alpha backup-dr data-sources describe DATA_SOURCE + +POSITIONAL ARGUMENTS + Data source resource - Name of the data source 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 data_source 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. + + DATA_SOURCE + ID of the data_source or fully qualified identifier for the + data_source. + + To set the data_source attribute: + ▸ provide the argument data_source on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --backup-vault=BACKUP_VAULT + The ID of the Backup Vault. + + To set the backup-vault attribute: + ▸ provide the argument data_source on the command line with a fully + specified name; + ▸ provide the argument --backup-vault on the command line. + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument data_source on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +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/backup-dr/data-sources/help b/gcloud/alpha/backup-dr/data-sources/help new file mode 100644 index 000000000..c4da108a4 --- /dev/null +++ b/gcloud/alpha/backup-dr/data-sources/help @@ -0,0 +1,29 @@ +NAME + gcloud alpha backup-dr data-sources - view Backup and DR data sources + +SYNOPSIS + gcloud alpha backup-dr data-sources COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) View Backup and DR data sources. + +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) Show details of the data source. + + list + (ALPHA) List Data Sources. + +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/backup-dr/data-sources/list b/gcloud/alpha/backup-dr/data-sources/list new file mode 100644 index 000000000..c82bb4a7a --- /dev/null +++ b/gcloud/alpha/backup-dr/data-sources/list @@ -0,0 +1,99 @@ +NAME + gcloud alpha backup-dr data-sources list - list Data Sources + +SYNOPSIS + gcloud alpha backup-dr data-sources list + [--backup-vault=BACKUP_VAULT --location=LOCATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Displays all data sources in a project. + +EXAMPLES + To list data sources for all backup vaults and locations, run: $ gcloud alpha backup-dr data-sources list To list all data \ + sources for a backup vault `_my-vault_` in a location \ + `_my-location_`, run: $ gcloud alpha backup-dr data-sources \ + list --backup-vault=my-vault --location=my-location + +FLAGS + Backup vault resource - Backup vault to list data sources 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 --backup-vault on the command line with a fully + specified name; + ◆ default is all backup vaults with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --backup-vault=BACKUP_VAULT + ID of the backup_vault or fully qualified identifier for the + backup_vault. + + To set the backup-vault attribute: + ▸ provide the argument --backup-vault on the command line; + ▸ default is all backup vaults . + + --location=LOCATION + Location ID of the resource. + + To set the location attribute: + ▸ provide the argument --backup-vault on the command line with a + fully specified name; + ▸ default is all backup vaults with a fully specified name; + ▸ provide the argument --location on the command line; + ▸ default is all locations . + +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 backupdr/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/backup-disaster-recovery + +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/backup-dr/help b/gcloud/alpha/backup-dr/help index 2032c28c6..6264b1e5c 100644 --- a/gcloud/alpha/backup-dr/help +++ b/gcloud/alpha/backup-dr/help @@ -15,6 +15,21 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + backup-plan-associations + (ALPHA) Manage Backup and DR backup plan associations. + + backup-plans + (ALPHA) Manage Backup and DR backup plans. + + backup-vaults + (ALPHA) Manage Backup and DR backup vaults. + + backups + (ALPHA) Manage Backup and DR backups. + + data-sources + (ALPHA) View Backup and DR data sources. + locations (ALPHA) Manage Backup and DR locations. diff --git a/gcloud/alpha/compute/future-reservations/cancel b/gcloud/alpha/compute/future-reservations/cancel index c631008db..a85766ada 100644 --- a/gcloud/alpha/compute/future-reservations/cancel +++ b/gcloud/alpha/compute/future-reservations/cancel @@ -69,7 +69,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute future-reservations cancel $ gcloud beta compute future-reservations cancel diff --git a/gcloud/alpha/compute/future-reservations/create b/gcloud/alpha/compute/future-reservations/create index ac529b3d2..1286627bd 100644 --- a/gcloud/alpha/compute/future-reservations/create +++ b/gcloud/alpha/compute/future-reservations/create @@ -13,10 +13,16 @@ SYNOPSIS --maintenance-interval=MAINTENANCE_INTERVAL --min-cpu-platform=MIN_CPU_PLATFORM]) (--start-time=START_TIME (--duration=DURATION | --end-time=END_TIME)) - [--description=DESCRIPTION] [--name-prefix=NAME_PREFIX] - [--planning-status=PLANNING_STATUS] - [--[no-]require-specific-reservation] [--zone=ZONE] + [--deployment-type=DEPLOYMENT_TYPE] [--description=DESCRIPTION] + [--enable-opportunistic-maintenance=ENABLE_OPPORTUNISTIC_MAINTENANCE] + [--instance-termination-action=INSTANCE_TERMINATION_ACTION] + [--name-prefix=NAME_PREFIX] [--planning-status=PLANNING_STATUS] + [--[no-]require-specific-reservation] + [--reservation-name=RESERVATION_NAME] + [--scheduling-type=SCHEDULING_TYPE] [--zone=ZONE] [--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME | --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION] + [--commitment-name=COMMITMENT_NAME --commitment-plan=COMMITMENT_PLAN + --previous-commitment-terms=PREVIOUS_COMMITMENT_TERMS] [--share-setting=SHARE_SETTING --share-with=PROJECT,[PROJECT,...]] [GCLOUD_WIDE_FLAG ...] @@ -163,9 +169,25 @@ REQUIRED FLAGS 2021-11-20T07:00:00Z). OPTIONAL FLAGS + --deployment-type=DEPLOYMENT_TYPE + Indicates if the reservation allocation strategy is static or dynamic. + DENSE refers to a fixed size and topology, with deployment expressed in + terms of blocks. FLEXIBLE indicates a non-static distribution of + capacity that can change over time. Deployment is not expressed in + blocks. DEPLOYMENT_TYPE must be one of: DENSE, FLEXIBLE. + --description=DESCRIPTION An optional description of the future reservation to create. + --enable-opportunistic-maintenance=ENABLE_OPPORTUNISTIC_MAINTENANCE + Indicates if this group of VMs have opportunistic maintenance enabled. + Applicable only to dense coordinated maintenance. + + --instance-termination-action=INSTANCE_TERMINATION_ACTION + Specific termination action for running instances at the end of + reservation duration, it can be DELETE or STOP. + INSTANCE_TERMINATION_ACTION must be one of: DELETE, STOP. + --name-prefix=NAME_PREFIX A name prefix for the auto-created reservations when capacity is delivered at the start time. Each auto-created reservation name starts @@ -194,6 +216,18 @@ OPTIONAL FLAGS the name of the future reservation. Use --require-specific-reservation to enable and --no-require-specific-reservation to disable. + --reservation-name=RESERVATION_NAME + Name of reservations where the capacity is provisioned at the time of + delivery of future reservations. If the reservation with the given name + does not exist already, it is created automatically at the time of + Approval with INACTIVE state till specified start-time. Either provide + the reservation_name or a name_prefix. + + --scheduling-type=SCHEDULING_TYPE + Indicates the maintenance type for this group of VMs. This will be set + on the reservation via FR, and will be inherited for reservation + blocks. SCHEDULING_TYPE must be one of: GROUPED, INDEPENDENT. + --zone=ZONE Zone of the future reservation to create. If not specified and the compute/zone property isn't set, you might be prompted to select a zone @@ -233,6 +267,28 @@ OPTIONAL FLAGS for 30 minutes, or 1d2h3m4s for 1 day, 2 hours, 3 minutes, and 4 seconds. For more information, see $ gcloud topic datetimes. + Manage the commitment info properties + + --commitment-name=COMMITMENT_NAME + Name of commitment covering the delivered reservation at the time of + delivery of future reservations. If not specified, it takes the name + of the future reservation. + + --commitment-plan=COMMITMENT_PLAN + The plan for this commitment to be created, which determines duration + and discount rate. The currently supported plans are TWELVE_MONTH (1 + year), and THIRTY_SIX_MONTH (3 years). COMMITMENT_PLAN must be one + of: TWELVE_MONTH, THIRTY_SIX_MONTH. + + --previous-commitment-terms=PREVIOUS_COMMITMENT_TERMS + Applicable only if future reservation will deliver to an existing + reservation with a ramp plan. When set to EXTEND, all associated + parent Committed Used Discount's end-date/term will be extended to + the end-time of this future reservation. Default is to extend + previous commitment's time to the end_time of the reservation. + PREVIOUS_COMMITMENT_TERMS must be (only one value is supported): + EXTEND. + Manage the properties of a shared reservation. --share-setting=SHARE_SETTING @@ -257,7 +313,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 future-reservations create $ gcloud beta compute future-reservations create diff --git a/gcloud/alpha/compute/future-reservations/delete b/gcloud/alpha/compute/future-reservations/delete index 3487cf6cd..7ec81eb1f 100644 --- a/gcloud/alpha/compute/future-reservations/delete +++ b/gcloud/alpha/compute/future-reservations/delete @@ -69,7 +69,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute future-reservations delete $ gcloud beta compute future-reservations delete diff --git a/gcloud/alpha/compute/future-reservations/describe b/gcloud/alpha/compute/future-reservations/describe index c0a965348..beb281217 100644 --- a/gcloud/alpha/compute/future-reservations/describe +++ b/gcloud/alpha/compute/future-reservations/describe @@ -64,7 +64,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute future-reservations describe $ gcloud beta compute future-reservations describe diff --git a/gcloud/alpha/compute/future-reservations/help b/gcloud/alpha/compute/future-reservations/help index 072f719be..63bb74f9e 100644 --- a/gcloud/alpha/compute/future-reservations/help +++ b/gcloud/alpha/compute/future-reservations/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 compute future-reservations $ gcloud beta compute future-reservations diff --git a/gcloud/alpha/compute/future-reservations/list b/gcloud/alpha/compute/future-reservations/list index 53e4cf08e..9afc0b715 100644 --- a/gcloud/alpha/compute/future-reservations/list +++ b/gcloud/alpha/compute/future-reservations/list @@ -59,7 +59,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud compute future-reservations list $ gcloud beta compute future-reservations list diff --git a/gcloud/alpha/compute/future-reservations/update b/gcloud/alpha/compute/future-reservations/update index 5ccf36197..2eb952084 100644 --- a/gcloud/alpha/compute/future-reservations/update +++ b/gcloud/alpha/compute/future-reservations/update @@ -5,13 +5,20 @@ NAME SYNOPSIS gcloud alpha compute future-reservations update FUTURE_RESERVATION [--[no-]auto-delete-auto-created-reservations] - [--description=DESCRIPTION] [--planning-status=PLANNING_STATUS] - [--[no-]require-specific-reservation] [--total-count=TOTAL_COUNT] + [--deployment-type=DEPLOYMENT_TYPE] [--description=DESCRIPTION] + [--enable-opportunistic-maintenance=ENABLE_OPPORTUNISTIC_MAINTENANCE] + [--instance-termination-action=INSTANCE_TERMINATION_ACTION] + [--planning-status=PLANNING_STATUS] + [--[no-]require-specific-reservation] + [--reservation-name=RESERVATION_NAME] + [--scheduling-type=SCHEDULING_TYPE] [--total-count=TOTAL_COUNT] [--zone=ZONE] [--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME | --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION] [--clear-name-prefix | --name-prefix=NAME_PREFIX] [--clear-share-settings | --share-setting=SHARE_SETTING --share-with=PROJECT,[PROJECT,...]] + [--commitment-name=COMMITMENT_NAME --commitment-plan=COMMITMENT_PLAN + --previous-commitment-terms=PREVIOUS_COMMITMENT_TERMS] [--machine-type=MACHINE_TYPE --maintenance-interval=MAINTENANCE_INTERVAL --min-cpu-platform=MIN_CPU_PLATFORM @@ -44,9 +51,25 @@ FLAGS Use --auto-delete-auto-created-reservations to enable and --no-auto-delete-auto-created-reservations to disable. + --deployment-type=DEPLOYMENT_TYPE + Indicates if the reservation allocation strategy is static or dynamic. + DENSE refers to a fixed size and topology, with deployment expressed in + terms of blocks. FLEXIBLE indicates a non-static distribution of + capacity that can change over time. Deployment is not expressed in + blocks. DEPLOYMENT_TYPE must be one of: DENSE, FLEXIBLE. + --description=DESCRIPTION An optional description of the future reservation to create. + --enable-opportunistic-maintenance=ENABLE_OPPORTUNISTIC_MAINTENANCE + Indicates if this group of VMs have opportunistic maintenance enabled. + Applicable only to dense coordinated maintenance. + + --instance-termination-action=INSTANCE_TERMINATION_ACTION + Specific termination action for running instances at the end of + reservation duration, it can be DELETE or STOP. + INSTANCE_TERMINATION_ACTION must be one of: DELETE, STOP. + --planning-status=PLANNING_STATUS The planning status of the future reservation. The default value is DRAFT. While in DRAFT, any changes to the future reservation's @@ -70,6 +93,18 @@ FLAGS the name of the future reservation. Use --require-specific-reservation to enable and --no-require-specific-reservation to disable. + --reservation-name=RESERVATION_NAME + Name of reservations where the capacity is provisioned at the time of + delivery of future reservations. If the reservation with the given name + does not exist already, it is created automatically at the time of + Approval with INACTIVE state till specified start-time. Either provide + the reservation_name or a name_prefix. + + --scheduling-type=SCHEDULING_TYPE + Indicates the maintenance type for this group of VMs. This will be set + on the reservation via FR, and will be inherited for reservation + blocks. SCHEDULING_TYPE must be one of: GROUPED, INDEPENDENT. + --total-count=TOTAL_COUNT The total number of instances for which capacity assurance is requested at a future time period. @@ -145,6 +180,28 @@ FLAGS list of projects that this future reservation is shared with. The list must contain project IDs or project numbers. + Manage the commitment info properties + + --commitment-name=COMMITMENT_NAME + Name of commitment covering the delivered reservation at the time of + delivery of future reservations. If not specified, it takes the name + of the future reservation. + + --commitment-plan=COMMITMENT_PLAN + The plan for this commitment to be created, which determines duration + and discount rate. The currently supported plans are TWELVE_MONTH (1 + year), and THIRTY_SIX_MONTH (3 years). COMMITMENT_PLAN must be one + of: TWELVE_MONTH, THIRTY_SIX_MONTH. + + --previous-commitment-terms=PREVIOUS_COMMITMENT_TERMS + Applicable only if future reservation will deliver to an existing + reservation with a ramp plan. When set to EXTEND, all associated + parent Committed Used Discount's end-date/term will be extended to + the end-time of this future reservation. Default is to extend + previous commitment's time to the end_time of the reservation. + PREVIOUS_COMMITMENT_TERMS must be (only one value is supported): + EXTEND. + Manage the specific SKU reservation properties. --machine-type=MACHINE_TYPE @@ -248,7 +305,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 future-reservations update $ gcloud beta compute future-reservations update diff --git a/gcloud/alpha/compute/resource-policies/update/instance-schedule b/gcloud/alpha/compute/resource-policies/update/instance-schedule index 36f72d4b4..424647703 100644 --- a/gcloud/alpha/compute/resource-policies/update/instance-schedule +++ b/gcloud/alpha/compute/resource-policies/update/instance-schedule @@ -17,10 +17,7 @@ EXAMPLES $ gcloud alpha compute resource-policies update instance-schedule \ NAME --region=REGION --timezone=UTC \ - --vm-start-schedule="* 7 * * *" \ - --vm-stop-schedule="* 17 * * *" \ - --initiation-date=2025-05-01T00:00:00.000-07:00 \ - --end-date=2027-05-01T00:00:00.000-07:00 + --vm-start-schedule="0 7 * * *" --vm-stop-schedule="0 17 * * *" POSITIONAL ARGUMENTS NAME diff --git a/gcloud/alpha/container/backup-restore/backup-plans/create b/gcloud/alpha/container/backup-restore/backup-plans/create index c70e8f7b4..217df7f64 100644 --- a/gcloud/alpha/container/backup-restore/backup-plans/create +++ b/gcloud/alpha/container/backup-restore/backup-plans/create @@ -119,7 +119,8 @@ OPTIONAL FLAGS Number of days a backup produced via this plan cannot be deleted. Must be less than or equal to 90 days. If 0, delete operations are - allowed. + allowed. Updating this field does not affect existing backups. Backups + created after a successful update will inherit this new value. --backup-retain-days=BACKUP_RETAIN_DAYS Number of days after which a backup produced via this plan is @@ -127,7 +128,9 @@ OPTIONAL FLAGS Must be less than or equal to 365 days. If not set (value is 0), backups are not automatically deleted. If set, must be greater than the - value for backup_delete_lock_days. + value for backup_delete_lock_days. Updating this field does not affect + existing backups. Backups created after a successful update will + inherit this new value. --locked If set, subsequent updates are not allowed to the backup plan's diff --git a/gcloud/alpha/container/backup-restore/backup-plans/update b/gcloud/alpha/container/backup-restore/backup-plans/update index e71ae92b4..120e91723 100644 --- a/gcloud/alpha/container/backup-restore/backup-plans/update +++ b/gcloud/alpha/container/backup-restore/backup-plans/update @@ -114,7 +114,8 @@ FLAGS Number of days a backup produced via this plan cannot be deleted. Must be less than or equal to 90 days. If 0, delete operations are - allowed. + allowed. Updating this field does not affect existing backups. Backups + created after a successful update will inherit this new value. --backup-retain-days=BACKUP_RETAIN_DAYS Number of days after which a backup produced via this plan is @@ -122,7 +123,9 @@ FLAGS Must be less than or equal to 365 days. If not set (value is 0), backups are not automatically deleted. If set, must be greater than the - value for backup_delete_lock_days. + value for backup_delete_lock_days. Updating this field does not affect + existing backups. Backups created after a successful update will + inherit this new value. --locked If set, subsequent updates are not allowed to the backup plan's diff --git a/gcloud/alpha/container/clusters/check-autopilot-compatibility b/gcloud/alpha/container/clusters/check-autopilot-compatibility index 8eb971084..e3477bc32 100644 --- a/gcloud/alpha/container/clusters/check-autopilot-compatibility +++ b/gcloud/alpha/container/clusters/check-autopilot-compatibility @@ -26,10 +26,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/clusters/config/export b/gcloud/alpha/container/clusters/config/export index a32ed4fd6..cce090668 100644 --- a/gcloud/alpha/container/clusters/config/export +++ b/gcloud/alpha/container/clusters/config/export @@ -70,10 +70,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/clusters/config/help b/gcloud/alpha/container/clusters/config/help index 777463400..2040ab784 100644 --- a/gcloud/alpha/container/clusters/config/help +++ b/gcloud/alpha/container/clusters/config/help @@ -15,10 +15,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 1f7ce1998..30ad2f330 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -111,6 +111,8 @@ SYNOPSIS [--enable-autoscaling --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES --min-nodes=MIN_NODES --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] + [--enable-insecure-binding-system-authenticated + --enable-insecure-binding-system-unauthenticated] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-network-egress-metering @@ -1862,6 +1864,23 @@ FLAGS --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --enable-insecure-binding-system-authenticated + Allow using system:authenticated as a subject in ClusterRoleBindings + and RoleBindings. Allowing bindings that reference system:authenticated + is a security risk and is not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-authenticated flag instead. + + --enable-insecure-binding-system-unauthenticated + Allow using system:unauthenticated and system:anonymous as subjects in + ClusterRoleBindings and RoleBindings. Allowing bindings that reference + system:unauthenticated and system:anonymous are a security risk and is + not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-unauthenticated flag instead. + Master Authorized Networks --enable-master-authorized-networks @@ -2076,10 +2095,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index ab93c1608..8d3bfe489 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -35,6 +35,8 @@ SYNOPSIS [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] + [--enable-insecure-binding-system-authenticated + --enable-insecure-binding-system-unauthenticated] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-private-endpoint @@ -523,6 +525,23 @@ FLAGS Enables Advanced Datapath Observability which allows for a real-time view into pod-to-pod traffic within your cluster. + --enable-insecure-binding-system-authenticated + Allow using system:authenticated as a subject in ClusterRoleBindings + and RoleBindings. Allowing bindings that reference system:authenticated + is a security risk and is not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-authenticated flag instead. + + --enable-insecure-binding-system-unauthenticated + Allow using system:unauthenticated and system:anonymous as subjects in + ClusterRoleBindings and RoleBindings. Allowing bindings that reference + system:unauthenticated and system:anonymous are a security risk and is + not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-unauthenticated flag instead. + Master Authorized Networks --enable-master-authorized-networks @@ -565,10 +584,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/clusters/delete b/gcloud/alpha/container/clusters/delete index be491ccf1..f70bfc8ff 100644 --- a/gcloud/alpha/container/clusters/delete +++ b/gcloud/alpha/container/clusters/delete @@ -42,10 +42,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/clusters/describe b/gcloud/alpha/container/clusters/describe index 684375d3a..e070373bd 100644 --- a/gcloud/alpha/container/clusters/describe +++ b/gcloud/alpha/container/clusters/describe @@ -24,10 +24,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/clusters/get-credentials b/gcloud/alpha/container/clusters/get-credentials index 48a4d7ca2..9e2760eb6 100644 --- a/gcloud/alpha/container/clusters/get-credentials +++ b/gcloud/alpha/container/clusters/get-credentials @@ -53,10 +53,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/clusters/help b/gcloud/alpha/container/clusters/help index 184f00c0e..3acb8831b 100644 --- a/gcloud/alpha/container/clusters/help +++ b/gcloud/alpha/container/clusters/help @@ -19,10 +19,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/clusters/list b/gcloud/alpha/container/clusters/list index 014c21dcf..8bc780b39 100644 --- a/gcloud/alpha/container/clusters/list +++ b/gcloud/alpha/container/clusters/list @@ -24,10 +24,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/clusters/resize b/gcloud/alpha/container/clusters/resize index 3db85a807..5a26a0a21 100644 --- a/gcloud/alpha/container/clusters/resize +++ b/gcloud/alpha/container/clusters/resize @@ -68,10 +68,14 @@ OPTIONAL FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 9c4b1aaaf..5e652c1e7 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -92,6 +92,8 @@ SYNOPSIS --enable-autoprovisioning-autoupgrade [--max-accelerator=[type=TYPE,count=COUNT,...] : --min-accelerator=[type=TYPE,count=COUNT,...]]] + | --enable-insecure-binding-system-authenticated + --enable-insecure-binding-system-unauthenticated | --enable-tpu --enable-tpu-service-networking | --tpu-ipv4-cidr=CIDR | --logging=[COMPONENT,...] --monitoring=[COMPONENT,...] --disable-managed-prometheus @@ -1342,6 +1344,23 @@ REQUIRED FLAGS (Required) The minimum number of accelerators to which the cluster can be scaled. + --enable-insecure-binding-system-authenticated + Allow using system:authenticated as a subject in ClusterRoleBindings + and RoleBindings. Allowing bindings that reference + system:authenticated is a security risk and is not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-authenticated flag instead. + + --enable-insecure-binding-system-unauthenticated + Allow using system:unauthenticated and system:anonymous as subjects + in ClusterRoleBindings and RoleBindings. Allowing bindings that + reference system:unauthenticated and system:anonymous are a security + risk and is not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-unauthenticated flag instead. + Flags relating to Cloud TPUs: --enable-tpu @@ -1513,10 +1532,14 @@ OPTIONAL FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/clusters/upgrade b/gcloud/alpha/container/clusters/upgrade index e53894265..f01e71887 100644 --- a/gcloud/alpha/container/clusters/upgrade +++ b/gcloud/alpha/container/clusters/upgrade @@ -96,10 +96,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/get-server-config b/gcloud/alpha/container/get-server-config index a373c3f99..af36d8115 100644 --- a/gcloud/alpha/container/get-server-config +++ b/gcloud/alpha/container/get-server-config @@ -21,10 +21,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/node-pools/complete-upgrade b/gcloud/alpha/container/node-pools/complete-upgrade index 9016a6521..dd8c9de21 100644 --- a/gcloud/alpha/container/node-pools/complete-upgrade +++ b/gcloud/alpha/container/node-pools/complete-upgrade @@ -33,10 +33,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/node-pools/config/export b/gcloud/alpha/container/node-pools/config/export index 5582aea26..79929fddb 100644 --- a/gcloud/alpha/container/node-pools/config/export +++ b/gcloud/alpha/container/node-pools/config/export @@ -99,10 +99,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/node-pools/config/help b/gcloud/alpha/container/node-pools/config/help index 08a5b4007..8f5b3e5c3 100644 --- a/gcloud/alpha/container/node-pools/config/help +++ b/gcloud/alpha/container/node-pools/config/help @@ -15,10 +15,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index 5ba0e3329..a852cf6de 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -1028,10 +1028,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/node-pools/delete b/gcloud/alpha/container/node-pools/delete index fe820c9a7..ce8ba745f 100644 --- a/gcloud/alpha/container/node-pools/delete +++ b/gcloud/alpha/container/node-pools/delete @@ -40,10 +40,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/node-pools/describe b/gcloud/alpha/container/node-pools/describe index f5fc7712a..ba1d17fa3 100644 --- a/gcloud/alpha/container/node-pools/describe +++ b/gcloud/alpha/container/node-pools/describe @@ -30,10 +30,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/node-pools/help b/gcloud/alpha/container/node-pools/help index 1e1d1dbdb..319c1c30c 100644 --- a/gcloud/alpha/container/node-pools/help +++ b/gcloud/alpha/container/node-pools/help @@ -16,10 +16,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/node-pools/list b/gcloud/alpha/container/node-pools/list index f4ac3e5fd..15b2041f4 100644 --- a/gcloud/alpha/container/node-pools/list +++ b/gcloud/alpha/container/node-pools/list @@ -26,10 +26,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/node-pools/rollback b/gcloud/alpha/container/node-pools/rollback index 8605c5bb2..29e69543b 100644 --- a/gcloud/alpha/container/node-pools/rollback +++ b/gcloud/alpha/container/node-pools/rollback @@ -41,10 +41,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index 50760a760..ff8aa5291 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -519,10 +519,14 @@ OPTIONAL FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/operations/cancel b/gcloud/alpha/container/operations/cancel index f17b6919e..971a0df37 100644 --- a/gcloud/alpha/container/operations/cancel +++ b/gcloud/alpha/container/operations/cancel @@ -31,10 +31,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/operations/describe b/gcloud/alpha/container/operations/describe index 4a24a2bdf..b829a6083 100644 --- a/gcloud/alpha/container/operations/describe +++ b/gcloud/alpha/container/operations/describe @@ -23,10 +23,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/operations/help b/gcloud/alpha/container/operations/help index 8b11bf9fc..44a321545 100644 --- a/gcloud/alpha/container/operations/help +++ b/gcloud/alpha/container/operations/help @@ -15,10 +15,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/operations/list b/gcloud/alpha/container/operations/list index 932df54f6..c17766848 100644 --- a/gcloud/alpha/container/operations/list +++ b/gcloud/alpha/container/operations/list @@ -21,10 +21,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/container/operations/wait b/gcloud/alpha/container/operations/wait index 7b8d5955d..32d325cd8 100644 --- a/gcloud/alpha/container/operations/wait +++ b/gcloud/alpha/container/operations/wait @@ -23,10 +23,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/alpha/looker/instances/create b/gcloud/alpha/looker/instances/create index 375e50273..89d7599d1 100644 --- a/gcloud/alpha/looker/instances/create +++ b/gcloud/alpha/looker/instances/create @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud alpha looker instances create (INSTANCE : --region=REGION) --edition=EDITION --oauth-client-id=OAUTH_CLIENT_ID - --oauth-client-secret=OAUTH_CLIENT_SECRET [--async] - [--no-enable-public-ip] [--kms-key=KMS_KEY] - [--consumer-network=CONSUMER_NETWORK --enable-private-ip + --oauth-client-secret=OAUTH_CLIENT_SECRET [--async] [--kms-key=KMS_KEY] + [--no-public-ip-enabled] + [--consumer-network=CONSUMER_NETWORK --private-ip-enabled : --reserved-range=RESERVED_RANGE] [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE --deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] @@ -71,23 +71,29 @@ REQUIRED FLAGS --edition=EDITION The edition of the Looker instance. EDITION must be one of: - advanced - This edition provides a full-feature edition for product - exploration and development. Scales as your organization and data - add complexity. + core-embed-annual + A Looker (Google Cloud core) product for deploying and maintaining + external analytics and custom applications at scale. This can be + purchased via an annual contract. + + core-enterprise-annual + A Looker (Google Cloud core) product with enhanced security + features for a wide variety of internal BI and analytics use cases. + This can be purchased via an annual contract. + + core-standard + A Looker (Google Cloud core) product for small organizations or + teams with fewer than 50 users. This will be billed monthly while + the instance is active. + + core-standard-annual + A Looker (Google Cloud core) product for small organizations or + teams with fewer than 50 users. This can be purchased via an annual + contract. core-trial Trial edition of Looker. - elite - This edition provides a full-feature edition for product - exploration and development. Drive your business through - operational analytics. - - standard - This edition provides a full-feature edition for product - exploration and development. Exceptional for all your Analytics. - --oauth-client-id=OAUTH_CLIENT_ID The client ID from an external OAuth application. @@ -109,10 +115,6 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. - --enable-public-ip - This specifies whether public IP is enabled on the Looker instance. - Enabled by default, use --no-enable-public-ip to disable. - Key resource - The Cloud KMS (Key Management Service) cryptokey that will be used to protect the Looker instance and backups. The 'Looker Service Agent' service account must hold permission 'Cloud KMS CryptoKey @@ -124,6 +126,10 @@ OPTIONAL FLAGS kms-key attribute: ▸ provide the argument --kms-key on the command line. + --public-ip-enabled + This specifies whether public IP is enabled on the Looker instance. + Enabled by default, use --no-public-ip-enabled to disable. + Private IP - Assigns an internal, Google-hosted VPC IP address. Private IP connectivity requires additional APIs and permissions. Private IP cannot be disabled once it has been enabled. If enabled, consumer-network must be @@ -136,7 +142,7 @@ OPTIONAL FLAGS This flag argument must be specified if any of the other arguments in this group are specified. - --enable-private-ip + --private-ip-enabled This specifies whether private IP is enabled on the Looker instance. This flag argument must be specified if any of the other arguments in @@ -206,7 +212,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the looker/v1alpha1 API. The full documentation for this + This command uses the looker/v1alpha2 API. The full documentation for this API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES diff --git a/gcloud/alpha/looker/instances/delete b/gcloud/alpha/looker/instances/delete index 944db1da0..8b5e2fb61 100644 --- a/gcloud/alpha/looker/instances/delete +++ b/gcloud/alpha/looker/instances/delete @@ -69,7 +69,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the looker/v1alpha1 API. The full documentation for this + This command uses the looker/v1alpha2 API. The full documentation for this API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES diff --git a/gcloud/alpha/looker/instances/describe b/gcloud/alpha/looker/instances/describe index 9da379457..075f701c4 100644 --- a/gcloud/alpha/looker/instances/describe +++ b/gcloud/alpha/looker/instances/describe @@ -67,7 +67,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the looker/v1alpha1 API. The full documentation for this + This command uses the looker/v1alpha2 API. The full documentation for this API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES diff --git a/gcloud/alpha/looker/instances/list b/gcloud/alpha/looker/instances/list index d1943bf5d..105e71367 100644 --- a/gcloud/alpha/looker/instances/list +++ b/gcloud/alpha/looker/instances/list @@ -76,7 +76,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the looker/v1alpha1 API. The full documentation for this + This command uses the looker/v1alpha2 API. The full documentation for this API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES diff --git a/gcloud/alpha/looker/instances/restart b/gcloud/alpha/looker/instances/restart index 182fc1e96..3adfb5b8f 100644 --- a/gcloud/alpha/looker/instances/restart +++ b/gcloud/alpha/looker/instances/restart @@ -66,7 +66,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the looker/v1alpha1 API. The full documentation for this + This command uses the looker/v1alpha2 API. The full documentation for this API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES diff --git a/gcloud/alpha/looker/instances/update b/gcloud/alpha/looker/instances/update index bc0e93b09..51d9ce50e 100644 --- a/gcloud/alpha/looker/instances/update +++ b/gcloud/alpha/looker/instances/update @@ -4,8 +4,9 @@ NAME SYNOPSIS gcloud alpha looker instances update (INSTANCE : --region=REGION) [--allowed-email-domains=[ALLOWED_EMAIL_DOMAINS,...]] [--async] - [--custom-domain=CUSTOM_DOMAIN] [--enable-public-ip] + [--custom-domain=CUSTOM_DOMAIN] [--linked-lsp-project-number=LINKED_LSP_PROJECT_NUMBER] + [--public-ip-enabled] [--add-developer-users=ADD_DEVELOPER_USERS --add-standard-users=ADD_STANDARD_USERS --add-viewer-users=ADD_VIEWER_USERS] @@ -89,12 +90,12 @@ FLAGS --custom-domain=CUSTOM_DOMAIN Domain name wanted to serve the Looker instance. - --enable-public-ip - This specifies whether public IP is enabled on the Looker instance. - --linked-lsp-project-number=LINKED_LSP_PROJECT_NUMBER The Looker Studio Pro project number to be linked. + --public-ip-enabled + This specifies whether public IP is enabled on the Looker instance. + User Allocations - There are ten Standard and two Developer users included in the cost of the product. You can allocate additional Standard, Viewer, and Developer users for this instance. It is an optional step and can be @@ -189,7 +190,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the looker/v1alpha1 API. The full documentation for this + This command uses the looker/v1alpha2 API. The full documentation for this API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES diff --git a/gcloud/alpha/looker/operations/cancel b/gcloud/alpha/looker/operations/cancel index 8d2d87f3f..ca6cfa604 100644 --- a/gcloud/alpha/looker/operations/cancel +++ b/gcloud/alpha/looker/operations/cancel @@ -57,7 +57,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the looker/v1alpha1 API. The full documentation for this + This command uses the looker/v1alpha2 API. The full documentation for this API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES diff --git a/gcloud/alpha/looker/operations/describe b/gcloud/alpha/looker/operations/describe index 8265641ac..444dfaf39 100644 --- a/gcloud/alpha/looker/operations/describe +++ b/gcloud/alpha/looker/operations/describe @@ -63,7 +63,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the looker/v1alpha1 API. The full documentation for this + This command uses the looker/v1alpha2 API. The full documentation for this API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES diff --git a/gcloud/alpha/looker/operations/list b/gcloud/alpha/looker/operations/list index f893db3b6..058dcdc28 100644 --- a/gcloud/alpha/looker/operations/list +++ b/gcloud/alpha/looker/operations/list @@ -76,7 +76,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the looker/v1alpha1 API. The full documentation for this + This command uses the looker/v1alpha2 API. The full documentation for this API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES diff --git a/gcloud/alpha/looker/regions/list b/gcloud/alpha/looker/regions/list index 2953bcd1b..920eb7109 100644 --- a/gcloud/alpha/looker/regions/list +++ b/gcloud/alpha/looker/regions/list @@ -55,7 +55,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the looker/v1alpha1 API. The full documentation for this + This command uses the looker/v1alpha2 API. The full documentation for this API can be found at: https://cloud.google.com/looker/docs/reference/rest/ NOTES diff --git a/gcloud/alpha/managed-kafka/clusters/create b/gcloud/alpha/managed-kafka/clusters/create index ecfe97d2f..6dc594e8c 100644 --- a/gcloud/alpha/managed-kafka/clusters/create +++ b/gcloud/alpha/managed-kafka/clusters/create @@ -44,8 +44,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/clusters/delete b/gcloud/alpha/managed-kafka/clusters/delete index 7d959aeb7..df214a6c4 100644 --- a/gcloud/alpha/managed-kafka/clusters/delete +++ b/gcloud/alpha/managed-kafka/clusters/delete @@ -41,8 +41,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/clusters/describe b/gcloud/alpha/managed-kafka/clusters/describe index 280d3b738..44e906625 100644 --- a/gcloud/alpha/managed-kafka/clusters/describe +++ b/gcloud/alpha/managed-kafka/clusters/describe @@ -41,8 +41,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/clusters/update b/gcloud/alpha/managed-kafka/clusters/update index dfebde91a..56fbd99ff 100644 --- a/gcloud/alpha/managed-kafka/clusters/update +++ b/gcloud/alpha/managed-kafka/clusters/update @@ -43,8 +43,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/consumer-groups/delete b/gcloud/alpha/managed-kafka/consumer-groups/delete index 086c31172..2eeea5c3d 100644 --- a/gcloud/alpha/managed-kafka/consumer-groups/delete +++ b/gcloud/alpha/managed-kafka/consumer-groups/delete @@ -51,8 +51,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument consumer_group on the command line with a diff --git a/gcloud/alpha/managed-kafka/consumer-groups/describe b/gcloud/alpha/managed-kafka/consumer-groups/describe index 6657f4376..98c1235f8 100644 --- a/gcloud/alpha/managed-kafka/consumer-groups/describe +++ b/gcloud/alpha/managed-kafka/consumer-groups/describe @@ -51,8 +51,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument consumer_group on the command line with a diff --git a/gcloud/alpha/managed-kafka/consumer-groups/list b/gcloud/alpha/managed-kafka/consumer-groups/list index 27e63ddbc..53ee033fd 100644 --- a/gcloud/alpha/managed-kafka/consumer-groups/list +++ b/gcloud/alpha/managed-kafka/consumer-groups/list @@ -44,8 +44,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/consumer-groups/update b/gcloud/alpha/managed-kafka/consumer-groups/update index 7e54897d8..83c3354eb 100644 --- a/gcloud/alpha/managed-kafka/consumer-groups/update +++ b/gcloud/alpha/managed-kafka/consumer-groups/update @@ -61,8 +61,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument consumer_group on the command line with a diff --git a/gcloud/alpha/managed-kafka/topics/create b/gcloud/alpha/managed-kafka/topics/create index fd8011237..9be95fe3e 100644 --- a/gcloud/alpha/managed-kafka/topics/create +++ b/gcloud/alpha/managed-kafka/topics/create @@ -52,8 +52,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/topics/delete b/gcloud/alpha/managed-kafka/topics/delete index 320e0f548..52de87728 100644 --- a/gcloud/alpha/managed-kafka/topics/delete +++ b/gcloud/alpha/managed-kafka/topics/delete @@ -49,8 +49,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/topics/describe b/gcloud/alpha/managed-kafka/topics/describe index ae1c607c3..2b1ecf8a2 100644 --- a/gcloud/alpha/managed-kafka/topics/describe +++ b/gcloud/alpha/managed-kafka/topics/describe @@ -49,8 +49,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/topics/list b/gcloud/alpha/managed-kafka/topics/list index b5f8d4732..d25b72946 100644 --- a/gcloud/alpha/managed-kafka/topics/list +++ b/gcloud/alpha/managed-kafka/topics/list @@ -44,8 +44,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/alpha/managed-kafka/topics/update b/gcloud/alpha/managed-kafka/topics/update index 11e7a6648..3f6e06793 100644 --- a/gcloud/alpha/managed-kafka/topics/update +++ b/gcloud/alpha/managed-kafka/topics/update @@ -51,8 +51,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/alpha/memorystore/help b/gcloud/alpha/memorystore/help new file mode 100644 index 000000000..9e51c0082 --- /dev/null +++ b/gcloud/alpha/memorystore/help @@ -0,0 +1,31 @@ +NAME + gcloud alpha memorystore - manage Memorystore resources + +SYNOPSIS + gcloud alpha memorystore GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Memorystore resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + instances + (ALPHA) Manage Instance resources. + + operations + (ALPHA) Manage Memorystore 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 memorystore + diff --git a/gcloud/alpha/memorystore/instances/create b/gcloud/alpha/memorystore/instances/create new file mode 100644 index 000000000..32a473d9b --- /dev/null +++ b/gcloud/alpha/memorystore/instances/create @@ -0,0 +1,299 @@ +NAME + gcloud alpha memorystore instances create - create a Memorystore instance + +SYNOPSIS + gcloud alpha memorystore instances create (INSTANCE : --location=LOCATION) + --psc-auto-connections=[network=NETWORK],[projectId=PROJECTID] + --shard-count=SHARD_COUNT [--async] + [--authorization-mode=AUTHORIZATION_MODE] + [--deletion-protection-enabled] [--engine-configs=[ENGINE_CONFIGS,...]] + [--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] + [--node-type=NODE_TYPE] [--replica-count=REPLICA_COUNT] + [--request-id=REQUEST_ID] + [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] + [--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC + --persistence-config-mode=PERSISTENCE_CONFIG_MODE + --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD + --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME] + [--zone-distribution-config=ZONE_DISTRIBUTION_CONFIG + --zone-distribution-config-mode=ZONE_DISTRIBUTION_CONFIG_MODE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Memorystore instance. + + A service connection policy for service class gcp-memorystore must already + exist for the location and network. Refer to creation prerequisites + (https://cloud.google.com/memorystore/docs/valkey/networking#prerequisites_required_before_creating_an_instance) + for more details. + +EXAMPLES + To create a three shard Memorystore instance my-instance in project + my-project and location us-central1, run: + + $ gcloud alpha memorystore instances create my-instance \ + --project=my-project --location=us-central1 --shard-count=3 \ + --psc-auto-connections="network=NETWORK,projectId=PROJECT_ID" + + To create a three shard Memorystore instance my-instance in project + my-project, location us-central1, with one replica per shard, and TLS + enabled, run: + + $ gcloud alpha memorystore instances create my-instance \ + --project=my-project --location=us-central1 --shard-count=3 \ + --psc-auto-connections="network=NETWORK,projectId=PROJECT_ID" \ + --transit-encryption-mode=server-authentication \ + --replica-count=1 + +POSITIONAL ARGUMENTS + Instance resource - Identifier. Unique name of the instance. Format: + projects/{project}/locations/{location}/instances/{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 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the instance resource. + + 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. + +REQUIRED FLAGS + --psc-auto-connections=[network=NETWORK],[projectId=PROJECTID] + Required, User inputs and resource details of the auto-created PSC + connections. + + network + The consumer network where the IP address resides, in the form of + projects/{project_id}/global/networks/{network_id}. + + projectId + The consumer project_id where the forwarding rule is created from. + + Shorthand Example: + + --psc-auto-connections=network=string,projectId=string --psc-auto-connections=network=string,projectId=string + + JSON Example: + + --psc-auto-connections='[{"network": "string", "projectId": "string"}]' + + File Example: + + --psc-auto-connections=path_to_file.(yaml|json) + + --shard-count=SHARD_COUNT + Number of shards for the instance. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --authorization-mode=AUTHORIZATION_MODE + Authorization mode of the instance. AUTHORIZATION_MODE must be one of: + + auth-disabled + Authorization disabled. + iam-auth + IAM basic authorization. + + Arguments for the deletion protection enabled. + + --deletion-protection-enabled + If set to true deletion of the instance will fail. + + --engine-configs=[ENGINE_CONFIGS,...] + User-provided engine configurations for the instance. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --engine-configs=string=string + + JSON Example: + + --engine-configs='{"string": "string"}' + + File Example: + + --engine-configs=path_to_file.(yaml|json) + + --engine-version=ENGINE_VERSION + Engine version of the instance. + + --labels=[LABELS,...] + Labels to represent user-provided metadata. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --node-type=NODE_TYPE + Machine type for individual nodes of the instance. NODE_TYPE must be + one of: + + highmem-medium + High memory medium. + highmem-xlarge + High memory extra large. + shared-core-nano + Shared core nano. + standard-small + Standard small. + + Arguments for the replica count. + + --replica-count=REPLICA_COUNT + Number of replica nodes per shard. If omitted the default is 0 + replicas. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --transit-encryption-mode=TRANSIT_ENCRYPTION_MODE + In-transit encryption mode of the instance. TRANSIT_ENCRYPTION_MODE + must be one of: + + server-authentication + Server-managed encryption is used for in-transit encryption. + transit-encryption-disabled + In-transit encryption is disabled. + + Represents persistence configuration for a instance. + + Configuration for AOF based persistence. + + --aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC + The fsync mode. AOF_CONFIG_APPEND_FSYNC must be one of: + + always + Fsync every time new write commands are appended to the AOF. + The best data loss protection at the cost of performance. + every-sec + Fsync every second. You may lose 1 second of data if there is a + disaster. + never + Never fsync. Normally Linux will flush data every 30 seconds + with this configuration, but it's up to the kernel's exact + tuning. + + --persistence-config-mode=PERSISTENCE_CONFIG_MODE + Current persistence mode. PERSISTENCE_CONFIG_MODE must be one of: + + aof + AOF based persistence is enabled. + disabled + Persistence is disabled, and any snapshot data is deleted. + rdb + RDB based persistence is enabled. + + Configuration for RDB based persistence. + + --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD + Period between RDB snapshots. RDB_CONFIG_SNAPSHOT_PERIOD must be + one of: + + one-hour + One hour. + six-hours + Six hours. + twelve-hours + Twelve hours. + twenty-four-hours + Twenty four hours. + + --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME + Time that the first snapshot was/will be attempted, and to which + future snapshots will be aligned. If not provided, the current time + will be used. + + Zone distribution configuration for allocation of instance resources. + + --zone-distribution-config=ZONE_DISTRIBUTION_CONFIG + Defines zone where all resources will be allocated with SINGLE_ZONE + mode. Ignored for MULTI_ZONE mode. + + --zone-distribution-config-mode=ZONE_DISTRIBUTION_CONFIG_MODE + Current zone distribution mode. Defaults to MULTI_ZONE. + ZONE_DISTRIBUTION_CONFIG_MODE must be one of: + + multi-zone + Distribute resources across 3 zones picked at random within the + region. + single-zone + Provision resources in a single zone. Zone field must be + specified. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +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 memorystore instances create + diff --git a/gcloud/alpha/memorystore/instances/delete b/gcloud/alpha/memorystore/instances/delete new file mode 100644 index 000000000..745499aa0 --- /dev/null +++ b/gcloud/alpha/memorystore/instances/delete @@ -0,0 +1,89 @@ +NAME + gcloud alpha memorystore instances delete - delete a Memorystore instance + +SYNOPSIS + gcloud alpha memorystore instances delete (INSTANCE : --location=LOCATION) + [--async] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Memorystore instance. + +EXAMPLES + To delete Memorystore instance my-instance in project my-project and + location us-central1, run: + + $ gcloud alpha memorystore instances delete my-instance \ + --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Instance resource - The name of the instance to delete. Format: + projects/{project}/locations/{location}/instances/{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 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the instance resource. + + 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. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +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 memorystore instances delete + diff --git a/gcloud/alpha/memorystore/instances/describe b/gcloud/alpha/memorystore/instances/describe new file mode 100644 index 000000000..bdcd0421c --- /dev/null +++ b/gcloud/alpha/memorystore/instances/describe @@ -0,0 +1,70 @@ +NAME + gcloud alpha memorystore instances describe - get details of a Memorystore + instance + +SYNOPSIS + gcloud alpha memorystore instances describe + (INSTANCE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get details of a Memorystore instance. + +EXAMPLES + To get the details of Memorystore instance my-instance in project + my-project and location us-central, run: + + $ gcloud alpha memorystore instances describe my-instance \ + --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Instance resource - The name of the instance to retrieve. Format: + projects/{project}/locations/{location}/instances/{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 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the instance resource. + + 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +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 memorystore instances describe + diff --git a/gcloud/alpha/memorystore/instances/get-certificate-authority b/gcloud/alpha/memorystore/instances/get-certificate-authority new file mode 100644 index 000000000..719234b0d --- /dev/null +++ b/gcloud/alpha/memorystore/instances/get-certificate-authority @@ -0,0 +1,70 @@ +NAME + gcloud alpha memorystore instances get-certificate-authority - get + certificate authority details of a Memorystore instance + +SYNOPSIS + gcloud alpha memorystore instances get-certificate-authority + (INSTANCE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get certificate authority details of a Memorystore instance. + +EXAMPLES + To get the certificate authority for instance my-instance in project + my-project and location us-central1, run: + + $ gcloud alpha memorystore instances get-certificate-authority \ + my-instance --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Instance resource - The name of the Memorystore instance. Format: + projects/{project}/locations/{location}/instances/{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 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location ID of the instance resource. + + 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +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 memorystore instances get-certificate-authority + diff --git a/gcloud/alpha/memorystore/instances/help b/gcloud/alpha/memorystore/instances/help new file mode 100644 index 000000000..374d50367 --- /dev/null +++ b/gcloud/alpha/memorystore/instances/help @@ -0,0 +1,44 @@ +NAME + gcloud alpha memorystore instances - manage Instance resources + +SYNOPSIS + gcloud alpha memorystore instances COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Instance resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a Memorystore instance. + + delete + (ALPHA) Delete a Memorystore instance. + + describe + (ALPHA) Get details of a Memorystore instance. + + get-certificate-authority + (ALPHA) Get certificate authority details of a Memorystore instance. + + list + (ALPHA) List all Memorystore instances in a specified project and + location. + + update + (ALPHA) Update the configuration of a Memorystore 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. This variant is also available: + + $ gcloud beta memorystore instances + diff --git a/gcloud/alpha/memorystore/instances/list b/gcloud/alpha/memorystore/instances/list new file mode 100644 index 000000000..6882c26b2 --- /dev/null +++ b/gcloud/alpha/memorystore/instances/list @@ -0,0 +1,91 @@ +NAME + gcloud alpha memorystore instances list - list all Memorystore instances in + a specified project and location + +SYNOPSIS + gcloud alpha memorystore instances list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all Memorystore instances in a specified project and location. + +EXAMPLES + To list all Memorystore instances in project my-project and location + us-central, run: + + $ gcloud alpha memorystore instances list --project=my-project \ + --location=us-central1 + +REQUIRED FLAGS + Location resource - The parent to list instances from. Format: + projects/{project}/locations/{location} This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +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 memorystore instances list + diff --git a/gcloud/alpha/memorystore/instances/update b/gcloud/alpha/memorystore/instances/update new file mode 100644 index 000000000..1f0877ecd --- /dev/null +++ b/gcloud/alpha/memorystore/instances/update @@ -0,0 +1,287 @@ +NAME + gcloud alpha memorystore instances update - update the configuration of a + Memorystore instance + +SYNOPSIS + gcloud alpha memorystore instances update (INSTANCE : --location=LOCATION) + [--async] [--deletion-protection-enabled] + [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] + [--shard-count=SHARD_COUNT] + [--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC + --persistence-config-mode=PERSISTENCE_CONFIG_MODE + --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD + --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME] + [--engine-configs=[ENGINE_CONFIGS,...] + | --update-engine-configs=[UPDATE_ENGINE_CONFIGS,...] + --clear-engine-configs + | --remove-engine-configs=[__REMOVE_ENGINE_CONFIGS,...]] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update the configuration of a Memorystore instance. + +EXAMPLES + To update Memorystore instance my-instance in project my-project and + location us-central1 to six shards, run: + + $ gcloud alpha memorystore instances update `my-instance` \ + --project=my-project --location=us-central1 --shard-count=6 + + To update Memorystore instance my-instance in project my-project and + location us-central1 to use a maxmemory-policy of allkeys-lru, run: + + $ gcloud alpha memorystore instances update `my-instance` \ + --project=my-project --location=us-central1 \ + --update-engine-configs=maxmemory-policy=allkeys-lru + +POSITIONAL ARGUMENTS + Instance resource - Identifier. Unique name of the instance. Format: + projects/{project}/locations/{location}/instances/{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 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the instance resource. + + 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. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + Arguments for the deletion protection enabled. + + --deletion-protection-enabled + If set to true deletion of the instance will fail. + + Arguments for the replica count. + + --replica-count=REPLICA_COUNT + Number of replica nodes per shard. If omitted the default is 0 + replicas. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --shard-count=SHARD_COUNT + Number of shards for the instance. + + Represents persistence configuration for a instance. + + Configuration for AOF based persistence. + + --aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC + The fsync mode. AOF_CONFIG_APPEND_FSYNC must be one of: + + always + Fsync every time new write commands are appended to the AOF. + The best data loss protection at the cost of performance. + every-sec + Fsync every second. You may lose 1 second of data if there is a + disaster. + never + Never fsync. Normally Linux will flush data every 30 seconds + with this configuration, but it's up to the kernel's exact + tuning. + + --persistence-config-mode=PERSISTENCE_CONFIG_MODE + Current persistence mode. PERSISTENCE_CONFIG_MODE must be one of: + + aof + AOF based persistence is enabled. + disabled + Persistence is disabled, and any snapshot data is deleted. + rdb + RDB based persistence is enabled. + + Configuration for RDB based persistence. + + --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD + Period between RDB snapshots. RDB_CONFIG_SNAPSHOT_PERIOD must be + one of: + + one-hour + One hour. + six-hours + Six hours. + twelve-hours + Twelve hours. + twenty-four-hours + Twenty four hours. + + --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME + Time that the first snapshot was/will be attempted, and to which + future snapshots will be aligned. If not provided, the current time + will be used. + + Update engine_configs. + + At most one of these can be specified: + + --engine-configs=[ENGINE_CONFIGS,...] + Set engine_configs to new value. User-provided engine configurations + for the instance. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --engine-configs=string=string + + JSON Example: + + --engine-configs='{"string": "string"}' + + File Example: + + --engine-configs=path_to_file.(yaml|json) + + --update-engine-configs=[UPDATE_ENGINE_CONFIGS,...] + Update engine_configs value or add key value pair. User-provided + engine configurations for the instance. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --update-engine-configs=string=string + + JSON Example: + + --update-engine-configs='{"string": "string"}' + + File Example: + + --update-engine-configs=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-engine-configs + Clear engine_configs value and set to empty map. + + --remove-engine-configs=[__REMOVE_ENGINE_CONFIGS,...] + Remove existing value from map engine_configs. + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels to represent user-provided metadata. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels to represent + user-provided metadata. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +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 memorystore instances update + diff --git a/gcloud/alpha/memorystore/operations/cancel b/gcloud/alpha/memorystore/operations/cancel new file mode 100644 index 000000000..06eef19cc --- /dev/null +++ b/gcloud/alpha/memorystore/operations/cancel @@ -0,0 +1,68 @@ +NAME + gcloud alpha memorystore operations cancel - cancel a Memorystore operation + +SYNOPSIS + gcloud alpha memorystore operations cancel + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancel a Memorystore operation. + +EXAMPLES + To cancel operation my-operation in project my-project and location + us-central1, run: + + $ gcloud alpha memorystore operations cancel my-operation \ + --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - The Memorystore operation to cancel. 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location ID of the operation resource. + + 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +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 memorystore operations cancel + diff --git a/gcloud/alpha/memorystore/operations/delete b/gcloud/alpha/memorystore/operations/delete new file mode 100644 index 000000000..63195f37b --- /dev/null +++ b/gcloud/alpha/memorystore/operations/delete @@ -0,0 +1,68 @@ +NAME + gcloud alpha memorystore operations delete - delete a Memorystore operation + +SYNOPSIS + gcloud alpha memorystore operations delete + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Memorystore operation. + +EXAMPLES + To delete operation my-operation in project my-project and location + us-central1, run: + + $ gcloud alpha memorystore operations delete my-operation \ + --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - The Memorystore operation 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 operation 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. + + 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location ID of the operation resource. + + 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +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 memorystore operations delete + diff --git a/gcloud/alpha/memorystore/operations/describe b/gcloud/alpha/memorystore/operations/describe new file mode 100644 index 000000000..2cc090f16 --- /dev/null +++ b/gcloud/alpha/memorystore/operations/describe @@ -0,0 +1,69 @@ +NAME + gcloud alpha memorystore operations describe - describe a Memorystore + operation + +SYNOPSIS + gcloud alpha memorystore operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Memorystore operation. + +EXAMPLES + To describe operation my-operation in project my-project and location + us-central1, run: + + $ gcloud alpha memorystore operations describe my-operation \ + --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - The Memorystore 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location ID of the operation resource. + + 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +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 memorystore operations describe + diff --git a/gcloud/alpha/memorystore/operations/help b/gcloud/alpha/memorystore/operations/help new file mode 100644 index 000000000..80b6e5585 --- /dev/null +++ b/gcloud/alpha/memorystore/operations/help @@ -0,0 +1,37 @@ +NAME + gcloud alpha memorystore operations - manage Memorystore operations + +SYNOPSIS + gcloud alpha memorystore operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Memorystore operations. + +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) Cancel a Memorystore operation. + + delete + (ALPHA) Delete a Memorystore operation. + + describe + (ALPHA) Describe a Memorystore operation. + + list + (ALPHA) List Memorystore 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 memorystore operations + diff --git a/gcloud/alpha/memorystore/operations/list b/gcloud/alpha/memorystore/operations/list new file mode 100644 index 000000000..68e89c8bf --- /dev/null +++ b/gcloud/alpha/memorystore/operations/list @@ -0,0 +1,89 @@ +NAME + gcloud alpha memorystore operations list - list Memorystore operations + +SYNOPSIS + gcloud alpha memorystore operations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Memorystore operations. + +EXAMPLES + To list Memorystore operations in project my-project and location + us-central1, run: + + $ gcloud alpha memorystore operations list --project=my-project \ + --location=us-central1 + +REQUIRED FLAGS + Location resource - The parent collection of the Memorystore operations. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memorystore/v1alpha API. The full documentation for + this API can be found at: https://cloud.google.com/memorystore/ + +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 memorystore operations list + diff --git a/gcloud/alpha/notebooks/instances/create b/gcloud/alpha/notebooks/instances/create index 41013c8bb..91b0b44b1 100644 --- a/gcloud/alpha/notebooks/instances/create +++ b/gcloud/alpha/notebooks/instances/create @@ -167,7 +167,7 @@ FLAGS NVIDIA_TESLA_A100, NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, - TPU_V2, TPU_V3, NVIDIA_L4. + TPU_V2, TPU_V3, NVIDIA_L4, NVIDIA_H100_80GB, NVIDIA_H100_MEGA_80GB. Boot disk configurations. diff --git a/gcloud/alpha/notebooks/instances/update b/gcloud/alpha/notebooks/instances/update index 6fbb8d838..d483590c9 100644 --- a/gcloud/alpha/notebooks/instances/update +++ b/gcloud/alpha/notebooks/instances/update @@ -78,7 +78,7 @@ REQUIRED FLAGS NVIDIA_TESLA_A100, NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, - TPU_V2, TPU_V3, NVIDIA_L4. + TPU_V2, TPU_V3, NVIDIA_L4, NVIDIA_H100_80GB, NVIDIA_H100_MEGA_80GB. --labels=[KEY=VALUE,...] Labels to apply to this instance. These can be later modified by the diff --git a/gcloud/alpha/projects/create b/gcloud/alpha/projects/create index 006d60185..93cfca45b 100644 --- a/gcloud/alpha/projects/create +++ b/gcloud/alpha/projects/create @@ -62,7 +62,7 @@ FLAGS ID for the organization to use as a parent --set-as-default - Set newly created project as [core.project] property. + Set newly created project as [core/project] property. --tags=[KEY=VALUE,...] List of tags KEY=VALUE pairs to bind. Each item must be expressed as diff --git a/gcloud/alpha/redis/clusters/create b/gcloud/alpha/redis/clusters/create index cf913b0be..7749739f7 100644 --- a/gcloud/alpha/redis/clusters/create +++ b/gcloud/alpha/redis/clusters/create @@ -5,8 +5,10 @@ NAME SYNOPSIS gcloud alpha redis clusters create (CLUSTER : --region=REGION) --network=NETWORK [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] - [--auth-mode=AUTH_MODE] [--deletion-protection] [--node-type=NODE_TYPE] - [--persistence-mode=PERSISTENCE_MODE] + [--auth-mode=AUTH_MODE] [--deletion-protection] + [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] + [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--node-type=NODE_TYPE] [--persistence-mode=PERSISTENCE_MODE] [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--redis-config=[KEY=VALUE,...]] [--replica-count=REPLICA_COUNT] @@ -116,6 +118,15 @@ OPTIONAL FLAGS Enable deletion protection for the Redis Cluster. Use --deletion-protection/--no-deletion-protection to enable/disable it. + --maintenance-window-day=MAINTENANCE_WINDOW_DAY + 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-hour=MAINTENANCE_WINDOW_HOUR + Hour of day (0 to 23) for the start of maintenance window, in UTC time + zone. + --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, diff --git a/gcloud/alpha/redis/clusters/help b/gcloud/alpha/redis/clusters/help index 4c6035a04..c3ef33d7b 100644 --- a/gcloud/alpha/redis/clusters/help +++ b/gcloud/alpha/redis/clusters/help @@ -38,6 +38,10 @@ COMMANDS list (ALPHA) List Memorystore for Redis Cluster instances. + reschedule-maintenance + (ALPHA) Reschedule maintenance window for a Memorystore for Redis + Cluster instance. + switchover (ALPHA) Switchover to a secondary cluster. diff --git a/gcloud/alpha/redis/clusters/reschedule-maintenance b/gcloud/alpha/redis/clusters/reschedule-maintenance new file mode 100644 index 000000000..9c1602fcf --- /dev/null +++ b/gcloud/alpha/redis/clusters/reschedule-maintenance @@ -0,0 +1,95 @@ +NAME + gcloud alpha redis clusters reschedule-maintenance - reschedule maintenance + window for a Memorystore for Redis Cluster instance + +SYNOPSIS + gcloud alpha redis clusters reschedule-maintenance + (CLUSTER : --region=REGION) --reschedule-type=RESCHEDULE_TYPE [--async] + [--schedule-time=SCHEDULE_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Reschedule maintenance window for a Memorystore for Redis Cluster + instance. + +EXAMPLES + To reschedule maintenance window for an instance with the name + 'my-redis-cluster' in region 'us-central-1' with immediate, run: + + $ gcloud alpha redis clusters reschedule-maintenance \ + my-redis-cluster --region=us-central1 \ + --reschedule-type=IMMEDIATE + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Cloud Memorystore + for Redis cluster 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/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. + 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 redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud redis clusters reschedule-maintenance + + $ gcloud beta redis clusters reschedule-maintenance + diff --git a/gcloud/alpha/redis/clusters/update b/gcloud/alpha/redis/clusters/update index d751b37c0..a1e619e83 100644 --- a/gcloud/alpha/redis/clusters/update +++ b/gcloud/alpha/redis/clusters/update @@ -10,6 +10,9 @@ SYNOPSIS [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] [--shard-count=SHARD_COUNT] [--update-redis-config=KEY=VALUE] + [--maintenance-window-any + | --maintenance-window-day=MAINTENANCE_WINDOW_DAY + --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -124,6 +127,20 @@ FLAGS parameter is already set, its value is modified; otherwise a new Redis config parameter is added. + 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-hour=MAINTENANCE_WINDOW_HOUR + Hour of day (0 to 23) for the start of maintenance window, in UTC + time zone. + 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/run/deploy b/gcloud/alpha/run/deploy index f6d2a5e19..64d1b6334 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -11,8 +11,10 @@ SYNOPSIS [--no-traffic] [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --[no-]automatic-updates --clear-volume-mounts - --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --memory=MEMORY - --port=PORT --remove-volume-mount=[MOUNT_PATH,...] + --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU + --liveness-probe=[KEY=VALUE,...] --memory=MEMORY --port=PORT + --remove-volume-mount=[MOUNT_PATH,...] + --startup-probe=[KEY=VALUE,...] --[no-]use-http2 --base-image=BASE_IMAGE | --clear-base-image --build-env-vars-file=FILE_PATH | --clear-build-env-vars | --set-build-env-vars=[KEY=VALUE,...] @@ -38,6 +40,7 @@ SYNOPSIS --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT --[no-]invoker-iam-check --max-surge=MAX_SURGE + --max-unavailable=MAX_UNAVAILABLE --mesh=MESH --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX --scaling=SCALING --service-max-instances=SERVICE_MAX_INSTANCES --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity @@ -244,6 +247,30 @@ FLAGS Cloud Run supports values 0 or 1. 1 gpu also requires a minimum 4 --cpu value 1 gpu also requires a minimum 8Gi --memory value. + --liveness-probe=[KEY=VALUE,...] + Comma separated settings for liveness probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: + + + initialDelaySeconds: integer + + timeoutSeconds: integer + + periodSeconds: integer + + failureThreshold: integer + + httpGet.port: integer + + httpGet.path: string + + grpc.port: integer + + grpc.service: string + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --liveness-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --liveness-probe="" + --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. @@ -259,6 +286,31 @@ FLAGS Removes the volume mounted at the specified path from the current container. + --startup-probe=[KEY=VALUE,...] + Comma separated settings for startup probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: + + + initialDelaySeconds: integer + + timeoutSeconds: integer + + periodSeconds: integer + + failureThreshold: integer + + httpGet.port: integer + + httpGet.path: string + + grpc.port: integer + + grpc.service: string + + tcpSocket.port: integer + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --startup-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --startup-probe="" + --[no-]use-http2 Whether to use HTTP/2 for connections to the service. Use --use-http2 to enable and --no-use-http2 to disable. @@ -564,6 +616,16 @@ FLAGS traffic split changes. Use "default" to unset the limit and use the platform default. + --max-unavailable=MAX_UNAVAILABLE + A maximum percentage of instances that may be unavailable during + traffic split changes. Use "default" to unset the limit and use the + platform default. + + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. + Mesh resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + --remove-containers=[CONTAINER,...] List of containers to remove. diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 843f969b6..7bf1d5772 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -13,7 +13,9 @@ SYNOPSIS [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] --cpu=CPU --depends-on=[CONTAINER,...] --gpu=GPU --image=IMAGE - --memory=MEMORY --port=PORT --remove-volume-mount=[MOUNT_PATH,...] + --liveness-probe=[KEY=VALUE,...] --memory=MEMORY --port=PORT + --remove-volume-mount=[MOUNT_PATH,...] + --startup-probe=[KEY=VALUE,...] --[no-]use-http2 --base-image=BASE_IMAGE | --clear-base-image --clear-env-vars | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] @@ -25,6 +27,7 @@ SYNOPSIS --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT --[no-]invoker-iam-check --max-surge=MAX_SURGE + --max-unavailable=MAX_UNAVAILABLE --mesh=MESH --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX --scaling=SCALING --service-max-instances=SERVICE_MAX_INSTANCES --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity @@ -231,6 +234,30 @@ FLAGS Name of the container image to deploy (e.g. gcr.io/cloudrun/hello:latest). + --liveness-probe=[KEY=VALUE,...] + Comma separated settings for liveness probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: + + + initialDelaySeconds: integer + + timeoutSeconds: integer + + periodSeconds: integer + + failureThreshold: integer + + httpGet.port: integer + + httpGet.path: string + + grpc.port: integer + + grpc.service: string + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --liveness-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --liveness-probe="" + --memory=MEMORY Set a memory limit. Ex: 1024Mi, 4Gi. @@ -246,6 +273,31 @@ FLAGS Removes the volume mounted at the specified path from the current container. + --startup-probe=[KEY=VALUE,...] + Comma separated settings for startup probe in the form KEY=VALUE. + Each key stands for a field of the probe described in + https://cloud.google.com/run/docs/reference/rest/v1/Container#Probe. + Currently supported keys are: + + + initialDelaySeconds: integer + + timeoutSeconds: integer + + periodSeconds: integer + + failureThreshold: integer + + httpGet.port: integer + + httpGet.path: string + + grpc.port: integer + + grpc.service: string + + tcpSocket.port: integer + + For example, to set a probe with 10s timeout and HTTP probe + requests sent to 8080 port of the container: + + $ --startup-probe=timeoutSeconds=10,httpGet.port=8080 + + To remove existing probe: + + $ --startup-probe="" + --[no-]use-http2 Whether to use HTTP/2 for connections to the service. Use --use-http2 to enable and --no-use-http2 to disable. @@ -377,6 +429,16 @@ FLAGS traffic split changes. Use "default" to unset the limit and use the platform default. + --max-unavailable=MAX_UNAVAILABLE + A maximum percentage of instances that may be unavailable during + traffic split changes. Use "default" to unset the limit and use the + platform default. + + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. + Mesh resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + --remove-containers=[CONTAINER,...] List of containers to remove. diff --git a/gcloud/alpha/run/workers/deploy b/gcloud/alpha/run/workers/deploy index 0a61d8ae1..e8b3794da 100644 --- a/gcloud/alpha/run/workers/deploy +++ b/gcloud/alpha/run/workers/deploy @@ -5,6 +5,7 @@ SYNOPSIS gcloud alpha run workers deploy [WORKER] [--async] [--breakglass=JUSTIFICATION] [--description=DESCRIPTION] [--max-instances=MAX_INSTANCES] [--max-surge=MAX_SURGE] + [--max-unavailable=MAX_UNAVAILABLE] [--mesh=MESH] [--min-instances=MIN_INSTANCES] [--no-promote] [--region=REGION] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] [--service-account=SERVICE_ACCOUNT] [--vpc-egress=VPC_EGRESS] @@ -95,6 +96,16 @@ FLAGS instance split changes. Use "default" to unset the limit and use the platform default. + --max-unavailable=MAX_UNAVAILABLE + A maximum percentage of instances that may be unavailable during + instance split changes. Use "default" to unset the limit and use the + platform default. + + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. Mesh + resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + --min-instances=MIN_INSTANCES The minimum number of container instances for this Worker to run or 'default' to remove any minimum. These instances will be divided among diff --git a/gcloud/alpha/run/workers/update b/gcloud/alpha/run/workers/update index 4ce335589..66b76d3d4 100644 --- a/gcloud/alpha/run/workers/update +++ b/gcloud/alpha/run/workers/update @@ -6,6 +6,7 @@ SYNOPSIS gcloud alpha run workers update [WORKER] [--async] [--breakglass=JUSTIFICATION] [--description=DESCRIPTION] [--max-instances=MAX_INSTANCES] [--max-surge=MAX_SURGE] + [--max-unavailable=MAX_UNAVAILABLE] [--mesh=MESH] [--min-instances=MIN_INSTANCES] [--no-promote] [--region=REGION] [--revision-suffix=REVISION_SUFFIX] [--scaling=SCALING] [--service-account=SERVICE_ACCOUNT] [--[no-]session-affinity] @@ -96,6 +97,16 @@ FLAGS instance split changes. Use "default" to unset the limit and use the platform default. + --max-unavailable=MAX_UNAVAILABLE + A maximum percentage of instances that may be unavailable during + instance split changes. Use "default" to unset the limit and use the + platform default. + + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. Mesh + resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + --min-instances=MIN_INSTANCES The minimum number of container instances for this Worker to run or 'default' to remove any minimum. These instances will be divided among diff --git a/gcloud/apphub/help b/gcloud/apphub/help index f3c4bdb98..6e8d92c5c 100644 --- a/gcloud/apphub/help +++ b/gcloud/apphub/help @@ -24,6 +24,9 @@ GROUPS discovered-workloads Manage App Hub Discovered Workloads. + locations + Manage App Hub Locations. + operations Manage App Hub Operations (long-running operations). diff --git a/gcloud/apphub/locations/describe b/gcloud/apphub/locations/describe new file mode 100644 index 000000000..960bc4f59 --- /dev/null +++ b/gcloud/apphub/locations/describe @@ -0,0 +1,46 @@ +NAME + gcloud apphub locations describe - describe an Apphub location + +SYNOPSIS + gcloud apphub locations describe LOCATION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe an Apphub location. + +EXAMPLES + To describe a specific apphub location with the name my-location, run: + + $ gcloud apphub locations describe my-location + +POSITIONAL ARGUMENTS + Location resource - Location. This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha apphub locations describe + diff --git a/gcloud/apphub/locations/help b/gcloud/apphub/locations/help new file mode 100644 index 000000000..262552ce4 --- /dev/null +++ b/gcloud/apphub/locations/help @@ -0,0 +1,28 @@ +NAME + gcloud apphub locations - manage App Hub Locations + +SYNOPSIS + gcloud apphub locations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for getting and listing locations where App Hub is available. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe an Apphub location. + + list + List Apphub locations. + +NOTES + This variant is also available: + + $ gcloud alpha apphub locations + diff --git a/gcloud/apphub/locations/list b/gcloud/apphub/locations/list new file mode 100644 index 000000000..6bf56dc21 --- /dev/null +++ b/gcloud/apphub/locations/list @@ -0,0 +1,61 @@ +NAME + gcloud apphub locations list - list Apphub locations + +SYNOPSIS + gcloud apphub locations list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Apphub locations. + +EXAMPLES + To list all apphub locations, run: + + $ gcloud apphub locations list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha apphub locations list + diff --git a/gcloud/assured/workloads/create b/gcloud/assured/workloads/create index 377e0f39c..cc15d4b56 100644 --- a/gcloud/assured/workloads/create +++ b/gcloud/assured/workloads/create @@ -10,6 +10,7 @@ SYNOPSIS [--external-identifier=EXTERNAL_IDENTIFIER] [--labels=[KEY=VALUE,...]] [--next-rotation-time=NEXT_ROTATION_TIME] [--partner=PARTNER] [--partner-permissions=[KEY=VALUE,...]] + [--partner-services-billing-account=PARTNER_SERVICES_BILLING_ACCOUNT] [--provisioned-resources-parent=PROVISIONED_RESOURCES_PARENT] [--resource-settings=[KEY=VALUE,...]] [--rotation-period=ROTATION_PERIOD] [GCLOUD_WIDE_FLAG ...] @@ -32,6 +33,7 @@ EXAMPLES ▪ with the label: key = 'LabelKey2', value = 'LabelValue2' ▪ provisioned resources parent 'folders/789' ▪ with custom project id 'my-custom-id' for consumer project + ▪ with external identifier for the workload of 'external-id' $ gcloud assured workloads create --organization=123 \ --location=us-central1 --display-name=Test-Workload \ @@ -41,7 +43,40 @@ EXAMPLES --rotation-period=172800s \ --labels=LabelKey1=LabelValue1,LabelKey2=LabelValue2 \ --provisioned-resources-parent=folders/789 \ - --resource-settings=consumer-project-id=my-custom-id + --resource-settings=consumer-project-id=my-custom-id \ + --external-identifier=external-id + + The following example command creates a new Partner Assured Workloads, with + the following properties: + + ▪ belonging to an organization with ID 123 + ▪ located in the me-central2 region + ▪ display name Test-Workload + ▪ partner CNTXT + ▪ partner services billing account billingAccounts/789 + ▪ billing account billingAccounts/456 + ▪ data logs viewer partner permission enabled + ▪ first key rotation set for 10:15am on the December 30, 2020 + ▪ key rotation interval set for every 48 hours + ▪ with the label: key = 'LabelKey1', value = 'LabelValue1' + ▪ with the label: key = 'LabelKey2', value = 'LabelValue2' + ▪ provisioned resources parent 'folders/789' + ▪ with custom project id 'my-custom-id' for consumer project + ▪ with external identifier for the workload of 'external-id' + + $ gcloud assured workloads create --organization=123 \ + --location=me-central2 --display-name=Test-Workload \ + --compliance-regime=ASSURED_WORKLOADS_FOR_PARTNERS \ + --partner=SOVEREIGN_CONTROLS_BY_CNTXT \ + --partner-services-billing-account=billingAccounts/\ + 01BF3F-2C6DE5-30C607 --partner-permissions=data-logs-viewer=true \ + --billing-account=billingAccounts/456 \ + --next-rotation-time=2020-12-30T10:15:00.00Z \ + --rotation-period=172800s \ + --labels=LabelKey1=LabelValue1,LabelKey2=LabelValue2 \ + --provisioned-resources-parent=folders/789 \ + --resource-settings=consumer-project-id=my-custom-id \ + --external-identifier=external-id REQUIRED FLAGS --billing-account=BILLING_ACCOUNT @@ -85,12 +120,20 @@ OPTIONAL FLAGS --partner=PARTNER The partner choice when creating a workload managed by local trusted partners. PARTNER must be one of: LOCAL_CONTROLS_BY_S3NS, - SOVEREIGN_CONTROLS_BY_T_SYSTEMS. + SOVEREIGN_CONTROLS_BY_T_SYSTEMS, SOVEREIGN_CONTROLS_BY_CNTXT, + SOVEREIGN_CONTROLS_BY_CNTXT_NO_EKM. --partner-permissions=[KEY=VALUE,...] The partner permissions for the partner regime, for example, data-logs-viewer=true/false + --partner-services-billing-account=PARTNER_SERVICES_BILLING_ACCOUNT + Billing account necessary for purchasing services from Sovereign + Partners. This field is required for creating SIA/PSN/CNTXT partner + workloads. The caller should have 'billing.resourceAssociations.create' + IAM permission on this billing-account. The format of this string is + billingAccounts/AAAAAA-BBBBBB-CCCCCC + --provisioned-resources-parent=PROVISIONED_RESOURCES_PARENT The parent of the provisioned projects, for example, folders/{FOLDER_ID} diff --git a/gcloud/beta/assured/workloads/create b/gcloud/beta/assured/workloads/create index 078f20f37..7e953dca0 100644 --- a/gcloud/beta/assured/workloads/create +++ b/gcloud/beta/assured/workloads/create @@ -10,6 +10,7 @@ SYNOPSIS [--external-identifier=EXTERNAL_IDENTIFIER] [--labels=[KEY=VALUE,...]] [--next-rotation-time=NEXT_ROTATION_TIME] [--partner=PARTNER] [--partner-permissions=[KEY=VALUE,...]] + [--partner-services-billing-account=PARTNER_SERVICES_BILLING_ACCOUNT] [--provisioned-resources-parent=PROVISIONED_RESOURCES_PARENT] [--resource-settings=[KEY=VALUE,...]] [--rotation-period=ROTATION_PERIOD] [GCLOUD_WIDE_FLAG ...] @@ -32,6 +33,7 @@ EXAMPLES ▪ with the label: key = 'LabelKey2', value = 'LabelValue2' ▪ provisioned resources parent 'folders/789' ▪ with custom project id 'my-custom-id' for consumer project + ▪ with external identifier for the workload of 'external-id' $ gcloud beta assured workloads create --organization=123 \ --location=us-central1 --display-name=Test-Workload \ @@ -41,7 +43,40 @@ EXAMPLES --rotation-period=172800s \ --labels=LabelKey1=LabelValue1,LabelKey2=LabelValue2 \ --provisioned-resources-parent=folders/789 \ - --resource-settings=consumer-project-id=my-custom-id + --resource-settings=consumer-project-id=my-custom-id \ + --external-identifier=external-id + + The following example command creates a new Partner Assured Workloads, with + the following properties: + + ▪ belonging to an organization with ID 123 + ▪ located in the me-central2 region + ▪ display name Test-Workload + ▪ partner CNTXT + ▪ partner services billing account billingAccounts/789 + ▪ billing account billingAccounts/456 + ▪ data logs viewer partner permission enabled + ▪ first key rotation set for 10:15am on the December 30, 2020 + ▪ key rotation interval set for every 48 hours + ▪ with the label: key = 'LabelKey1', value = 'LabelValue1' + ▪ with the label: key = 'LabelKey2', value = 'LabelValue2' + ▪ provisioned resources parent 'folders/789' + ▪ with custom project id 'my-custom-id' for consumer project + ▪ with external identifier for the workload of 'external-id' + + $ gcloud beta assured workloads create --organization=123 \ + --location=me-central2 --display-name=Test-Workload \ + --compliance-regime=ASSURED_WORKLOADS_FOR_PARTNERS \ + --partner=SOVEREIGN_CONTROLS_BY_CNTXT \ + --partner-services-billing-account=billingAccounts/\ + 01BF3F-2C6DE5-30C607 --partner-permissions=data-logs-viewer=true \ + --billing-account=billingAccounts/456 \ + --next-rotation-time=2020-12-30T10:15:00.00Z \ + --rotation-period=172800s \ + --labels=LabelKey1=LabelValue1,LabelKey2=LabelValue2 \ + --provisioned-resources-parent=folders/789 \ + --resource-settings=consumer-project-id=my-custom-id \ + --external-identifier=external-id REQUIRED FLAGS --billing-account=BILLING_ACCOUNT @@ -85,12 +120,20 @@ OPTIONAL FLAGS --partner=PARTNER The partner choice when creating a workload managed by local trusted partners. PARTNER must be one of: LOCAL_CONTROLS_BY_S3NS, - SOVEREIGN_CONTROLS_BY_T_SYSTEMS. + SOVEREIGN_CONTROLS_BY_T_SYSTEMS, SOVEREIGN_CONTROLS_BY_CNTXT, + SOVEREIGN_CONTROLS_BY_CNTXT_NO_EKM. --partner-permissions=[KEY=VALUE,...] The partner permissions for the partner regime, for example, data-logs-viewer=true/false + --partner-services-billing-account=PARTNER_SERVICES_BILLING_ACCOUNT + Billing account necessary for purchasing services from Sovereign + Partners. This field is required for creating SIA/PSN/CNTXT partner + workloads. The caller should have 'billing.resourceAssociations.create' + IAM permission on this billing-account. The format of this string is + billingAccounts/AAAAAA-BBBBBB-CCCCCC + --provisioned-resources-parent=PROVISIONED_RESOURCES_PARENT The parent of the provisioned projects, for example, folders/{FOLDER_ID} diff --git a/gcloud/beta/colab-enterprise/runtime-templates/add-iam-policy-binding b/gcloud/beta/colab-enterprise/runtime-templates/add-iam-policy-binding new file mode 100644 index 000000000..927293ad0 --- /dev/null +++ b/gcloud/beta/colab-enterprise/runtime-templates/add-iam-policy-binding @@ -0,0 +1,87 @@ +NAME + gcloud beta colab-enterprise runtime-templates add-iam-policy-binding - add + an IAM policy binding to a Colab Enterprise runtime template + +SYNOPSIS + gcloud beta colab-enterprise runtime-templates add-iam-policy-binding + (RUNTIME_TEMPLATE : --region=REGION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Adds an IAM policy binding to a Colab Enterprise runtime template. + +EXAMPLES + To set someone@example.com to have the roles/aiplatform.notebookRuntimeUser + role for a runtime template with id my-runtime-template in region + us-central1, run: + + $ gcloud beta colab-enterprise runtime-templates \ add-iam-policy-binding my-runtime-template \ + --region=us-central1 --member=user:someone@example.com \ + --role=roles/aiplatform.notebookRuntimeUser + +POSITIONAL ARGUMENTS + Runtime template resource - Unique name of the runtime template to add IAM + policy binding to. This was optionally provided by setting + --runtime-template-id in the create runtime-template command, or was + system-generated if unspecified. 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 runtime_template 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. + + RUNTIME_TEMPLATE + ID of the runtime template or fully qualified identifier for the + runtime template. + + To set the name attribute: + ▸ provide the argument runtime_template on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the runtime template. + + To set the region attribute: + ▸ provide the argument runtime_template on the command line with a + fully specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + --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. + + --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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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. + diff --git a/gcloud/beta/colab-enterprise/runtime-templates/get-iam-policy b/gcloud/beta/colab-enterprise/runtime-templates/get-iam-policy new file mode 100644 index 000000000..963d68dea --- /dev/null +++ b/gcloud/beta/colab-enterprise/runtime-templates/get-iam-policy @@ -0,0 +1,93 @@ +NAME + gcloud beta colab-enterprise runtime-templates get-iam-policy - get IAM + policy for a Colab Enterprise runtime template + +SYNOPSIS + gcloud beta colab-enterprise runtime-templates get-iam-policy + (RUNTIME_TEMPLATE : --region=REGION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Gets the IAM policy for a Colab Enterprise runtime template. + +EXAMPLES + To get the IAM policy for a runtime template with id my-runtime-template in + region us-central1, run: + + $ gcloud beta colab-enterprise runtime-templates get-iam-policy \ + get-iam-policy my-runtime-template --location=us-central1 \ + --member=user:someone@example.com \ + --role=roles/aiplatform.notebookRuntimeUser + +POSITIONAL ARGUMENTS + Runtime template resource - Unique name of the runtime template to get IAM + policy for. This was optionally provided by setting --runtime-template-id + in the create runtime-template command, or was system-generated if + unspecified. 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 runtime_template 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. + + RUNTIME_TEMPLATE + ID of the runtime template or fully qualified identifier for the + runtime template. + + To set the name attribute: + ▸ provide the argument runtime_template on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the runtime template. + + To set the region attribute: + ▸ provide the argument runtime_template on the command line with a + fully specified name; + ▸ provide the argument --region on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/colab-enterprise/runtime-templates/help b/gcloud/beta/colab-enterprise/runtime-templates/help index 67db31d19..330839b97 100644 --- a/gcloud/beta/colab-enterprise/runtime-templates/help +++ b/gcloud/beta/colab-enterprise/runtime-templates/help @@ -18,6 +18,10 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + add-iam-policy-binding + (BETA) Add an IAM policy binding to a Colab Enterprise runtime + template. + create (BETA) Creates a runtime template. @@ -27,9 +31,20 @@ COMMANDS describe (BETA) Describes a runtime template. + get-iam-policy + (BETA) Get IAM policy for a Colab Enterprise runtime template. + list (BETA) Lists your runtime templates. + remove-iam-policy-binding + (BETA) Remove an IAM policy binding from a Colab Enterprise runtime + template. + + set-iam-policy + (BETA) Set IAM policy for a Colab Enterprise runtime template as + defined in a JSON or YAML file. + NOTES This command is currently in beta and might change without notice. diff --git a/gcloud/beta/colab-enterprise/runtime-templates/remove-iam-policy-binding b/gcloud/beta/colab-enterprise/runtime-templates/remove-iam-policy-binding new file mode 100644 index 000000000..8220a783c --- /dev/null +++ b/gcloud/beta/colab-enterprise/runtime-templates/remove-iam-policy-binding @@ -0,0 +1,89 @@ +NAME + gcloud beta colab-enterprise runtime-templates remove-iam-policy-binding - + remove an IAM policy binding from a Colab Enterprise runtime template + +SYNOPSIS + gcloud beta colab-enterprise runtime-templates remove-iam-policy-binding + (RUNTIME_TEMPLATE : --region=REGION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Removes an IAM policy binding from a Colab Enterprise runtime + template. + +EXAMPLES + To remove an IAM policy binding of roles/aiplatform.notebookRuntimeUser for + someone@example.com, from the runtime template with id my-runtime-template + in region us-central1, run: + + $ gcloud beta colab-enterprise runtime-templates \ remove-iam-policy-binding my-runtime-template \ + --region=us-central1 --member=user:someone@example.com \ + --role=roles/aiplatform.notebookRuntimeUser + +POSITIONAL ARGUMENTS + Runtime template resource - Unique name of the runtime template to remove + IAM policy from. This was optionally provided by setting + --runtime-template-id in the create runtime-template command, or was + system-generated if unspecified. 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 runtime_template 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. + + RUNTIME_TEMPLATE + ID of the runtime template or fully qualified identifier for the + runtime template. + + To set the name attribute: + ▸ provide the argument runtime_template on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the runtime template. + + To set the region attribute: + ▸ provide the argument runtime_template on the command line with a + fully specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + --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. + + --role=ROLE + The role to remove the principal from. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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. + diff --git a/gcloud/beta/colab-enterprise/runtime-templates/set-iam-policy b/gcloud/beta/colab-enterprise/runtime-templates/set-iam-policy new file mode 100644 index 000000000..cbc991cb2 --- /dev/null +++ b/gcloud/beta/colab-enterprise/runtime-templates/set-iam-policy @@ -0,0 +1,75 @@ +NAME + gcloud beta colab-enterprise runtime-templates set-iam-policy - set IAM + policy for a Colab Enterprise runtime template as defined in a JSON or + YAML file + +SYNOPSIS + gcloud beta colab-enterprise runtime-templates set-iam-policy + (RUNTIME_TEMPLATE : --region=REGION) POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Sets the IAM policy for a Colab Enterprise runtime template as + defined in a JSON or YAML file. + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + To set the IAM policy for a runtime template with id my-runtime-template in + region us-central1 to the policy defined in policy.json, run: + + $ gcloud beta colab-enterprise runtime-templates set-iam-policy \ + my-runtime-template policy.json --region=us-central1 + +POSITIONAL ARGUMENTS + Runtime template resource - Unique name of the runtime template to set IAM + policy for. This was optionally provided by setting --runtime-template-id + in the create runtime-template command, or was system-generated if + unspecified. 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 runtime_template 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. + + RUNTIME_TEMPLATE + ID of the runtime template or fully qualified identifier for the + runtime template. + + To set the name attribute: + ▸ provide the argument runtime_template on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Cloud region for the runtime template. + + To set the region attribute: + ▸ provide the argument runtime_template on the command line with a + fully specified name; + ▸ provide the argument --region on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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. + diff --git a/gcloud/beta/compute/backend-services/update b/gcloud/beta/compute/backend-services/update index 8e51d7aa3..82ed13561 100644 --- a/gcloud/beta/compute/backend-services/update +++ b/gcloud/beta/compute/backend-services/update @@ -15,6 +15,7 @@ SYNOPSIS [--description=DESCRIPTION] [--drop-traffic-if-unhealthy] [--edge-security-policy=EDGE_SECURITY_POLICY] [--[no-]enable-cdn] [--[no-]enable-logging] [--[no-]enable-strong-affinity] + [--external-managed-migration-testing-percentage=EXTERNAL_MANAGED_MIGRATION_TESTING_PERCENTAGE] [--failover-ratio=FAILOVER_RATIO] [--health-checks=HEALTH_CHECK,[...]] [--no-health-checks] [--http-health-checks=HTTP_HEALTH_CHECK,[...]] [--https-health-checks=HTTPS_HEALTH_CHECK,[...]] @@ -22,6 +23,7 @@ SYNOPSIS oauth2-client-secret=OAUTH2-CLIENT-SECRET]] [--idle-timeout-sec=IDLE_TIMEOUT_SEC] [--ip-address-selection-policy=IP_ADDRESS_SELECTION_POLICY] + [--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--locality-lb-policy=LOCALITY_LB_POLICY] [--logging-optional=LOGGING_OPTIONAL] [--logging-optional-fields=[LOGGING_OPTIONAL_FIELDS,...]] @@ -37,6 +39,8 @@ SYNOPSIS | --no-bypass-cache-on-request-headers] [--cache-key-query-string-blacklist=[QUERY_STRING,...] | --cache-key-query-string-whitelist=QUERY_STRING,[...]] + [--clear-external-managed-migration-state + | --external-managed-migration-state=EXTERNAL_MANAGED_MIGRATION_STATE] [--client-ttl=CLIENT_TTL | --no-client-ttl] [--custom-request-header=CUSTOM_REQUEST_HEADER | --no-custom-request-headers] @@ -203,6 +207,12 @@ FLAGS loadbalancingScheme EXTERNAL. Use --enable-strong-affinity to enable and --no-enable-strong-affinity to disable. + --external-managed-migration-testing-percentage=EXTERNAL_MANAGED_MIGRATION_TESTING_PERCENTAGE + Determines the fraction of requests that should be processed by the + Global external Application Load Balancer. + + The value of this field must be in the range [0, 100]. + --failover-ratio=FAILOVER_RATIO Applicable only to backend service-based external passthrough Network load balancers and internal passthrough Network load balancers as part @@ -288,6 +298,13 @@ FLAGS IP_ADDRESS_SELECTION_POLICY must be one of: IPV4_ONLY, PREFER_IPV6, IPV6_ONLY. + --load-balancing-scheme=LOAD_BALANCING_SCHEME + Only for the Global external ALB migration. + + The value of this field must be EXTERNAL or EXTERNAL_MANAGED. + + LOAD_BALANCING_SCHEME must be one of: EXTERNAL, EXTERNAL_MANAGED. + --locality-lb-policy=LOCALITY_LB_POLICY The load balancing algorithm used within the scope of the locality. LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN, @@ -573,6 +590,25 @@ FLAGS percent encoded and not treated as delimiters. Can only be applied for global resources. + At most one of these can be specified: + + --clear-external-managed-migration-state + Clears current state of external managed migration. + + --external-managed-migration-state=EXTERNAL_MANAGED_MIGRATION_STATE + Specifies the canary migration state. Possible values are PREPARE, + TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. + + To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state + must be changed to PREPARE. The state must be changed to + TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to + EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be + used to migrate traffic by percentage using + externalManagedMigrationTestingPercentage. + + EXTERNAL_MANAGED_MIGRATION_STATE must be one of: PREPARE, + TEST_BY_PERCENTAGE, TEST_ALL_TRAFFIC. + At most one of these can be specified: --client-ttl=CLIENT_TTL diff --git a/gcloud/beta/compute/forwarding-rules/update b/gcloud/beta/compute/forwarding-rules/update index 5ed775886..83f0d14da 100644 --- a/gcloud/beta/compute/forwarding-rules/update +++ b/gcloud/beta/compute/forwarding-rules/update @@ -4,8 +4,13 @@ NAME SYNOPSIS gcloud beta compute forwarding-rules update NAME [--allow-global-access] - [--allow-psc-global-access] [--source-ip-ranges=SOURCE_IP_RANGE,[...]] + [--allow-psc-global-access] + [--external-managed-backend-bucket-migration-testing-percentage=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_TESTING_PERCENTAGE] + [--load-balancing-scheme=LOAD_BALANCING_SCHEME] + [--source-ip-ranges=SOURCE_IP_RANGE,[...]] [--update-labels=[KEY=VALUE,...]] + [--clear-external-managed-backend-bucket-migration-state + | --external-managed-backend-bucket-migration-state=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE] [--clear-labels | --remove-labels=[KEY,...]] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] @@ -52,6 +57,19 @@ FLAGS Connect forwarding rule. This can only be specified if the forwarding rule's target is a service attachment (--target-service-attachment). + --external-managed-backend-bucket-migration-testing-percentage=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_TESTING_PERCENTAGE + Determines the fraction of requests that should be processed by the + Global external Application Load Balancer. + + The value of this field must be in the range [0, 100]. + + --load-balancing-scheme=LOAD_BALANCING_SCHEME + Only for the Global external ALB migration. + + The value of this field must be EXTERNAL or EXTERNAL_MANAGED. + + LOAD_BALANCING_SCHEME must be one of: EXTERNAL, EXTERNAL_MANAGED. + --source-ip-ranges=SOURCE_IP_RANGE,[...] List of comma-separated IP addresses or IP ranges. If set, this forwarding rule only forwards traffic when the packet's source IP @@ -66,6 +84,26 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + At most one of these can be specified: + + --clear-external-managed-backend-bucket-migration-state + Clears current state of external managed migration. + + --external-managed-backend-bucket-migration-state=EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE + Specifies the canary migration state. Possible values are PREPARE, + TEST_BY_PERCENTAGE, and TEST_ALL_TRAFFIC. + + To begin the migration from EXTERNAL to EXTERNAL_MANAGED, the state + must be changed to PREPARE. The state must be changed to + TEST_ALL_TRAFFIC before the loadBalancingScheme can be changed to + EXTERNAL_MANAGED. Optionally, the TEST_BY_PERCENTAGE state can be + used to migrate traffic to backend buckets attached to this + forwarding rule by percentage using + externalManagedBackendBucketMigrationTestingPercentage. + + EXTERNAL_MANAGED_BACKEND_BUCKET_MIGRATION_STATE must be one of: + PREPARE, TEST_BY_PERCENTAGE, TEST_ALL_TRAFFIC. + At most one of these can be specified: --clear-labels diff --git a/gcloud/beta/compute/future-reservations/cancel b/gcloud/beta/compute/future-reservations/cancel index 948353155..8cc8563e1 100644 --- a/gcloud/beta/compute/future-reservations/cancel +++ b/gcloud/beta/compute/future-reservations/cancel @@ -66,8 +66,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute future-reservations cancel $ gcloud alpha compute future-reservations cancel diff --git a/gcloud/beta/compute/future-reservations/create b/gcloud/beta/compute/future-reservations/create index c8c070956..a1cb57605 100644 --- a/gcloud/beta/compute/future-reservations/create +++ b/gcloud/beta/compute/future-reservations/create @@ -219,8 +219,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 future-reservations create $ gcloud alpha compute future-reservations create diff --git a/gcloud/beta/compute/future-reservations/delete b/gcloud/beta/compute/future-reservations/delete index 4cf68954f..c625dd8e8 100644 --- a/gcloud/beta/compute/future-reservations/delete +++ b/gcloud/beta/compute/future-reservations/delete @@ -66,8 +66,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute future-reservations delete $ gcloud alpha compute future-reservations delete diff --git a/gcloud/beta/compute/future-reservations/describe b/gcloud/beta/compute/future-reservations/describe index 5aea44bd0..70adbcbfa 100644 --- a/gcloud/beta/compute/future-reservations/describe +++ b/gcloud/beta/compute/future-reservations/describe @@ -61,8 +61,10 @@ API REFERENCE can be found at: https://cloud.google.com/compute/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute future-reservations describe $ gcloud alpha compute future-reservations describe diff --git a/gcloud/beta/compute/future-reservations/help b/gcloud/beta/compute/future-reservations/help index 3a482a508..1166c0ee6 100644 --- a/gcloud/beta/compute/future-reservations/help +++ b/gcloud/beta/compute/future-reservations/help @@ -35,8 +35,10 @@ COMMANDS (BETA) Update Compute Engine future reservations. 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 future-reservations $ gcloud alpha compute future-reservations diff --git a/gcloud/beta/compute/future-reservations/list b/gcloud/beta/compute/future-reservations/list index 5f547d72a..67e6f2e20 100644 --- a/gcloud/beta/compute/future-reservations/list +++ b/gcloud/beta/compute/future-reservations/list @@ -56,8 +56,10 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute future-reservations list $ gcloud alpha compute future-reservations list diff --git a/gcloud/beta/compute/future-reservations/update b/gcloud/beta/compute/future-reservations/update index eb353b820..74d592bc4 100644 --- a/gcloud/beta/compute/future-reservations/update +++ b/gcloud/beta/compute/future-reservations/update @@ -215,8 +215,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 future-reservations update $ gcloud alpha compute future-reservations update diff --git a/gcloud/beta/compute/resource-policies/update/instance-schedule b/gcloud/beta/compute/resource-policies/update/instance-schedule index 11919d8af..acf1e759a 100644 --- a/gcloud/beta/compute/resource-policies/update/instance-schedule +++ b/gcloud/beta/compute/resource-policies/update/instance-schedule @@ -17,10 +17,7 @@ EXAMPLES $ gcloud beta compute resource-policies update instance-schedule \ NAME --region=REGION --timezone=UTC \ - --vm-start-schedule="* 7 * * *" \ - --vm-stop-schedule="* 17 * * *" \ - --initiation-date=2025-05-01T00:00:00.000-07:00 \ - --end-date=2027-05-01T00:00:00.000-07:00 + --vm-start-schedule="0 7 * * *" --vm-stop-schedule="0 17 * * *" POSITIONAL ARGUMENTS NAME diff --git a/gcloud/beta/container/backup-restore/backup-plans/create b/gcloud/beta/container/backup-restore/backup-plans/create index 36d3d583f..e5f7c478c 100644 --- a/gcloud/beta/container/backup-restore/backup-plans/create +++ b/gcloud/beta/container/backup-restore/backup-plans/create @@ -119,7 +119,8 @@ OPTIONAL FLAGS Number of days a backup produced via this plan cannot be deleted. Must be less than or equal to 90 days. If 0, delete operations are - allowed. + allowed. Updating this field does not affect existing backups. Backups + created after a successful update will inherit this new value. --backup-retain-days=BACKUP_RETAIN_DAYS Number of days after which a backup produced via this plan is @@ -127,7 +128,9 @@ OPTIONAL FLAGS Must be less than or equal to 365 days. If not set (value is 0), backups are not automatically deleted. If set, must be greater than the - value for backup_delete_lock_days. + value for backup_delete_lock_days. Updating this field does not affect + existing backups. Backups created after a successful update will + inherit this new value. --locked If set, subsequent updates are not allowed to the backup plan's diff --git a/gcloud/beta/container/backup-restore/backup-plans/update b/gcloud/beta/container/backup-restore/backup-plans/update index 40bc6454b..9b76314d1 100644 --- a/gcloud/beta/container/backup-restore/backup-plans/update +++ b/gcloud/beta/container/backup-restore/backup-plans/update @@ -114,7 +114,8 @@ FLAGS Number of days a backup produced via this plan cannot be deleted. Must be less than or equal to 90 days. If 0, delete operations are - allowed. + allowed. Updating this field does not affect existing backups. Backups + created after a successful update will inherit this new value. --backup-retain-days=BACKUP_RETAIN_DAYS Number of days after which a backup produced via this plan is @@ -122,7 +123,9 @@ FLAGS Must be less than or equal to 365 days. If not set (value is 0), backups are not automatically deleted. If set, must be greater than the - value for backup_delete_lock_days. + value for backup_delete_lock_days. Updating this field does not affect + existing backups. Backups created after a successful update will + inherit this new value. --locked If set, subsequent updates are not allowed to the backup plan's diff --git a/gcloud/beta/container/clusters/check-autopilot-compatibility b/gcloud/beta/container/clusters/check-autopilot-compatibility index 5ca2d329e..51591ef7a 100644 --- a/gcloud/beta/container/clusters/check-autopilot-compatibility +++ b/gcloud/beta/container/clusters/check-autopilot-compatibility @@ -26,10 +26,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index de78062b6..1e767fb2c 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -109,6 +109,8 @@ SYNOPSIS [--enable-autoscaling --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES --min-nodes=MIN_NODES --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] + [--enable-insecure-binding-system-authenticated + --enable-insecure-binding-system-unauthenticated] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-network-egress-metering @@ -1819,6 +1821,23 @@ FLAGS --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --enable-insecure-binding-system-authenticated + Allow using system:authenticated as a subject in ClusterRoleBindings + and RoleBindings. Allowing bindings that reference system:authenticated + is a security risk and is not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-authenticated flag instead. + + --enable-insecure-binding-system-unauthenticated + Allow using system:unauthenticated and system:anonymous as subjects in + ClusterRoleBindings and RoleBindings. Allowing bindings that reference + system:unauthenticated and system:anonymous are a security risk and is + not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-unauthenticated flag instead. + Master Authorized Networks --enable-master-authorized-networks @@ -2006,10 +2025,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 79249f67d..46f29b160 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -34,6 +34,8 @@ SYNOPSIS [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] + [--enable-insecure-binding-system-authenticated + --enable-insecure-binding-system-unauthenticated] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-private-endpoint @@ -513,6 +515,23 @@ FLAGS Enables Advanced Datapath Observability which allows for a real-time view into pod-to-pod traffic within your cluster. + --enable-insecure-binding-system-authenticated + Allow using system:authenticated as a subject in ClusterRoleBindings + and RoleBindings. Allowing bindings that reference system:authenticated + is a security risk and is not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-authenticated flag instead. + + --enable-insecure-binding-system-unauthenticated + Allow using system:unauthenticated and system:anonymous as subjects in + ClusterRoleBindings and RoleBindings. Allowing bindings that reference + system:unauthenticated and system:anonymous are a security risk and is + not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-unauthenticated flag instead. + Master Authorized Networks --enable-master-authorized-networks @@ -555,10 +574,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/clusters/delete b/gcloud/beta/container/clusters/delete index 9a6919342..8e36b6f76 100644 --- a/gcloud/beta/container/clusters/delete +++ b/gcloud/beta/container/clusters/delete @@ -42,10 +42,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/clusters/describe b/gcloud/beta/container/clusters/describe index 969bf4f99..3aa5743a6 100644 --- a/gcloud/beta/container/clusters/describe +++ b/gcloud/beta/container/clusters/describe @@ -24,10 +24,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/clusters/get-credentials b/gcloud/beta/container/clusters/get-credentials index dffacd600..3c5425e37 100644 --- a/gcloud/beta/container/clusters/get-credentials +++ b/gcloud/beta/container/clusters/get-credentials @@ -53,10 +53,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/clusters/help b/gcloud/beta/container/clusters/help index ffa2b5025..3c3ece1cb 100644 --- a/gcloud/beta/container/clusters/help +++ b/gcloud/beta/container/clusters/help @@ -19,10 +19,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/clusters/list b/gcloud/beta/container/clusters/list index e97f6ffca..1c3965eae 100644 --- a/gcloud/beta/container/clusters/list +++ b/gcloud/beta/container/clusters/list @@ -24,10 +24,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/clusters/resize b/gcloud/beta/container/clusters/resize index b553aad9d..f0a17f275 100644 --- a/gcloud/beta/container/clusters/resize +++ b/gcloud/beta/container/clusters/resize @@ -68,10 +68,14 @@ OPTIONAL FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 4aa5fb932..44d9685aa 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -90,6 +90,8 @@ SYNOPSIS --enable-autoprovisioning-autoupgrade [--max-accelerator=[type=TYPE,count=COUNT,...] : --min-accelerator=[type=TYPE,count=COUNT,...]]] + | --enable-insecure-binding-system-authenticated + --enable-insecure-binding-system-unauthenticated | --enable-tpu --enable-tpu-service-networking | --tpu-ipv4-cidr=CIDR | --logging=[COMPONENT,...] --monitoring=[COMPONENT,...] --disable-managed-prometheus @@ -1321,6 +1323,23 @@ REQUIRED FLAGS (Required) The minimum number of accelerators to which the cluster can be scaled. + --enable-insecure-binding-system-authenticated + Allow using system:authenticated as a subject in ClusterRoleBindings + and RoleBindings. Allowing bindings that reference + system:authenticated is a security risk and is not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-authenticated flag instead. + + --enable-insecure-binding-system-unauthenticated + Allow using system:unauthenticated and system:anonymous as subjects + in ClusterRoleBindings and RoleBindings. Allowing bindings that + reference system:unauthenticated and system:anonymous are a security + risk and is not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-unauthenticated flag instead. + Flags relating to Cloud TPUs: --enable-tpu @@ -1492,10 +1511,14 @@ OPTIONAL FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/clusters/upgrade b/gcloud/beta/container/clusters/upgrade index b5e46bc1c..5ed9e62bf 100644 --- a/gcloud/beta/container/clusters/upgrade +++ b/gcloud/beta/container/clusters/upgrade @@ -95,10 +95,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/get-server-config b/gcloud/beta/container/get-server-config index 860f162a8..c73fed6d0 100644 --- a/gcloud/beta/container/get-server-config +++ b/gcloud/beta/container/get-server-config @@ -21,10 +21,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/node-pools/complete-upgrade b/gcloud/beta/container/node-pools/complete-upgrade index ff8d8caf3..08e2e2ecc 100644 --- a/gcloud/beta/container/node-pools/complete-upgrade +++ b/gcloud/beta/container/node-pools/complete-upgrade @@ -33,10 +33,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index ee9358680..1f6655d48 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -982,10 +982,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/node-pools/delete b/gcloud/beta/container/node-pools/delete index 243a6284e..306aba719 100644 --- a/gcloud/beta/container/node-pools/delete +++ b/gcloud/beta/container/node-pools/delete @@ -40,10 +40,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/node-pools/describe b/gcloud/beta/container/node-pools/describe index 08754d609..5a0a53c45 100644 --- a/gcloud/beta/container/node-pools/describe +++ b/gcloud/beta/container/node-pools/describe @@ -30,10 +30,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/node-pools/help b/gcloud/beta/container/node-pools/help index ed2865545..4809ca0f6 100644 --- a/gcloud/beta/container/node-pools/help +++ b/gcloud/beta/container/node-pools/help @@ -16,10 +16,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/node-pools/list b/gcloud/beta/container/node-pools/list index 252646a96..443e25efc 100644 --- a/gcloud/beta/container/node-pools/list +++ b/gcloud/beta/container/node-pools/list @@ -26,10 +26,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/node-pools/rollback b/gcloud/beta/container/node-pools/rollback index e3dbe8d33..3b751c04b 100644 --- a/gcloud/beta/container/node-pools/rollback +++ b/gcloud/beta/container/node-pools/rollback @@ -41,10 +41,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index 696772380..4c628436d 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -519,10 +519,14 @@ OPTIONAL FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/operations/cancel b/gcloud/beta/container/operations/cancel index 4cf5e24c9..61a5a6095 100644 --- a/gcloud/beta/container/operations/cancel +++ b/gcloud/beta/container/operations/cancel @@ -31,10 +31,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/operations/describe b/gcloud/beta/container/operations/describe index 9ef99039c..4df66877c 100644 --- a/gcloud/beta/container/operations/describe +++ b/gcloud/beta/container/operations/describe @@ -23,10 +23,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/operations/help b/gcloud/beta/container/operations/help index 12b47e9a6..aec4c95ca 100644 --- a/gcloud/beta/container/operations/help +++ b/gcloud/beta/container/operations/help @@ -15,10 +15,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/operations/list b/gcloud/beta/container/operations/list index c9b50a18f..a0a398dbc 100644 --- a/gcloud/beta/container/operations/list +++ b/gcloud/beta/container/operations/list @@ -21,10 +21,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/container/operations/wait b/gcloud/beta/container/operations/wait index ac04576aa..5b01f9713 100644 --- a/gcloud/beta/container/operations/wait +++ b/gcloud/beta/container/operations/wait @@ -23,10 +23,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/beta/dataproc/sessions/help b/gcloud/beta/dataproc/sessions/help index 254518548..ec8384eee 100644 --- a/gcloud/beta/dataproc/sessions/help +++ b/gcloud/beta/dataproc/sessions/help @@ -27,11 +27,6 @@ DESCRIPTION $ gcloud beta dataproc sessions terminate SESSION_ID - Enable Personal Auth on an active session: - - $ gcloud beta dataproc sessions enable-personal-auth-session \ - SESSION_ID - GCLOUD WIDE FLAGS These flags are available to all commands: --help. diff --git a/gcloud/beta/managed-kafka/clusters/create b/gcloud/beta/managed-kafka/clusters/create index fa304e463..022e7e8a5 100644 --- a/gcloud/beta/managed-kafka/clusters/create +++ b/gcloud/beta/managed-kafka/clusters/create @@ -44,8 +44,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/beta/managed-kafka/clusters/delete b/gcloud/beta/managed-kafka/clusters/delete index ddd5fef26..b110f4193 100644 --- a/gcloud/beta/managed-kafka/clusters/delete +++ b/gcloud/beta/managed-kafka/clusters/delete @@ -41,8 +41,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/beta/managed-kafka/clusters/describe b/gcloud/beta/managed-kafka/clusters/describe index eeabc7789..976a6bee3 100644 --- a/gcloud/beta/managed-kafka/clusters/describe +++ b/gcloud/beta/managed-kafka/clusters/describe @@ -41,8 +41,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/beta/managed-kafka/clusters/update b/gcloud/beta/managed-kafka/clusters/update index c53fa406c..0e1838870 100644 --- a/gcloud/beta/managed-kafka/clusters/update +++ b/gcloud/beta/managed-kafka/clusters/update @@ -43,8 +43,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/beta/managed-kafka/consumer-groups/delete b/gcloud/beta/managed-kafka/consumer-groups/delete index 596db901c..8ddf23402 100644 --- a/gcloud/beta/managed-kafka/consumer-groups/delete +++ b/gcloud/beta/managed-kafka/consumer-groups/delete @@ -51,8 +51,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument consumer_group on the command line with a diff --git a/gcloud/beta/managed-kafka/consumer-groups/describe b/gcloud/beta/managed-kafka/consumer-groups/describe index 665fa2d1c..5d2cf2e44 100644 --- a/gcloud/beta/managed-kafka/consumer-groups/describe +++ b/gcloud/beta/managed-kafka/consumer-groups/describe @@ -51,8 +51,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument consumer_group on the command line with a diff --git a/gcloud/beta/managed-kafka/consumer-groups/list b/gcloud/beta/managed-kafka/consumer-groups/list index 89d0e29c0..e99e1c9e9 100644 --- a/gcloud/beta/managed-kafka/consumer-groups/list +++ b/gcloud/beta/managed-kafka/consumer-groups/list @@ -44,8 +44,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/beta/managed-kafka/consumer-groups/update b/gcloud/beta/managed-kafka/consumer-groups/update index 3d1c76f7d..095cf8d66 100644 --- a/gcloud/beta/managed-kafka/consumer-groups/update +++ b/gcloud/beta/managed-kafka/consumer-groups/update @@ -61,8 +61,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument consumer_group on the command line with a diff --git a/gcloud/beta/managed-kafka/topics/create b/gcloud/beta/managed-kafka/topics/create index b1a6f27af..dca97d724 100644 --- a/gcloud/beta/managed-kafka/topics/create +++ b/gcloud/beta/managed-kafka/topics/create @@ -52,8 +52,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/beta/managed-kafka/topics/delete b/gcloud/beta/managed-kafka/topics/delete index baad6e5a9..9bb6efc31 100644 --- a/gcloud/beta/managed-kafka/topics/delete +++ b/gcloud/beta/managed-kafka/topics/delete @@ -49,8 +49,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/beta/managed-kafka/topics/describe b/gcloud/beta/managed-kafka/topics/describe index 93d307fa4..176c8a8d8 100644 --- a/gcloud/beta/managed-kafka/topics/describe +++ b/gcloud/beta/managed-kafka/topics/describe @@ -49,8 +49,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/beta/managed-kafka/topics/list b/gcloud/beta/managed-kafka/topics/list index 95029bbb4..b8fc5c05d 100644 --- a/gcloud/beta/managed-kafka/topics/list +++ b/gcloud/beta/managed-kafka/topics/list @@ -43,8 +43,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument cluster on the command line with a fully diff --git a/gcloud/beta/managed-kafka/topics/update b/gcloud/beta/managed-kafka/topics/update index 81181636c..3376102cd 100644 --- a/gcloud/beta/managed-kafka/topics/update +++ b/gcloud/beta/managed-kafka/topics/update @@ -51,8 +51,9 @@ POSITIONAL ARGUMENTS --location=LOCATION ID of the location of the Managed Service for Apache Kafka resource. - See https://cloud.google.com/managed-kafka/docs/locations for a list - of supported locations. + See + https://cloud.google.com/managed-service-for-apache-kafka/docs/locations + for a list of supported locations. To set the location attribute: ▸ provide the argument topic on the command line with a fully diff --git a/gcloud/beta/memorystore/help b/gcloud/beta/memorystore/help new file mode 100644 index 000000000..8983e5bc3 --- /dev/null +++ b/gcloud/beta/memorystore/help @@ -0,0 +1,29 @@ +NAME + gcloud beta memorystore - manage Memorystore resources + +SYNOPSIS + gcloud beta memorystore GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Memorystore resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + instances + (BETA) Manage Instance resources. + + operations + (BETA) Manage Memorystore operations. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore + diff --git a/gcloud/beta/memorystore/instances/create b/gcloud/beta/memorystore/instances/create new file mode 100644 index 000000000..e226e0f9b --- /dev/null +++ b/gcloud/beta/memorystore/instances/create @@ -0,0 +1,297 @@ +NAME + gcloud beta memorystore instances create - create a Memorystore instance + +SYNOPSIS + gcloud beta memorystore instances create (INSTANCE : --location=LOCATION) + --psc-auto-connections=[network=NETWORK],[projectId=PROJECTID] + --shard-count=SHARD_COUNT [--async] + [--authorization-mode=AUTHORIZATION_MODE] + [--deletion-protection-enabled] [--engine-configs=[ENGINE_CONFIGS,...]] + [--engine-version=ENGINE_VERSION] [--labels=[LABELS,...]] + [--node-type=NODE_TYPE] [--replica-count=REPLICA_COUNT] + [--request-id=REQUEST_ID] + [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] + [--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC + --persistence-config-mode=PERSISTENCE_CONFIG_MODE + --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD + --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME] + [--zone-distribution-config=ZONE_DISTRIBUTION_CONFIG + --zone-distribution-config-mode=ZONE_DISTRIBUTION_CONFIG_MODE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Memorystore instance. + + A service connection policy for service class gcp-memorystore must already + exist for the location and network. Refer to creation prerequisites + (https://cloud.google.com/memorystore/docs/valkey/networking#prerequisites_required_before_creating_an_instance) + for more details. + +EXAMPLES + To create a three shard Memorystore instance my-instance in project + my-project and location us-central1, run: + + $ gcloud beta memorystore instances create my-instance \ + --project=my-project --location=us-central1 --shard-count=3 \ + --psc-auto-connections="network=NETWORK,projectId=PROJECT_ID" + + To create a three shard Memorystore instance my-instance in project + my-project, location us-central1, with one replica per shard, and TLS + enabled, run: + + $ gcloud beta memorystore instances create my-instance \ + --project=my-project --location=us-central1 --shard-count=3 \ + --psc-auto-connections="network=NETWORK,projectId=PROJECT_ID" \ + --transit-encryption-mode=server-authentication \ + --replica-count=1 + +POSITIONAL ARGUMENTS + Instance resource - Identifier. Unique name of the instance. Format: + projects/{project}/locations/{location}/instances/{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 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the instance resource. + + 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. + +REQUIRED FLAGS + --psc-auto-connections=[network=NETWORK],[projectId=PROJECTID] + Required, User inputs and resource details of the auto-created PSC + connections. + + network + The consumer network where the IP address resides, in the form of + projects/{project_id}/global/networks/{network_id}. + + projectId + The consumer project_id where the forwarding rule is created from. + + Shorthand Example: + + --psc-auto-connections=network=string,projectId=string --psc-auto-connections=network=string,projectId=string + + JSON Example: + + --psc-auto-connections='[{"network": "string", "projectId": "string"}]' + + File Example: + + --psc-auto-connections=path_to_file.(yaml|json) + + --shard-count=SHARD_COUNT + Number of shards for the instance. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --authorization-mode=AUTHORIZATION_MODE + Authorization mode of the instance. AUTHORIZATION_MODE must be one of: + + auth-disabled + Authorization disabled. + iam-auth + IAM basic authorization. + + Arguments for the deletion protection enabled. + + --deletion-protection-enabled + If set to true deletion of the instance will fail. + + --engine-configs=[ENGINE_CONFIGS,...] + User-provided engine configurations for the instance. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --engine-configs=string=string + + JSON Example: + + --engine-configs='{"string": "string"}' + + File Example: + + --engine-configs=path_to_file.(yaml|json) + + --engine-version=ENGINE_VERSION + Engine version of the instance. + + --labels=[LABELS,...] + Labels to represent user-provided metadata. + + KEY + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --node-type=NODE_TYPE + Machine type for individual nodes of the instance. NODE_TYPE must be + one of: + + highmem-medium + High memory medium. + highmem-xlarge + High memory extra large. + shared-core-nano + Shared core nano. + standard-small + Standard small. + + Arguments for the replica count. + + --replica-count=REPLICA_COUNT + Number of replica nodes per shard. If omitted the default is 0 + replicas. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --transit-encryption-mode=TRANSIT_ENCRYPTION_MODE + In-transit encryption mode of the instance. TRANSIT_ENCRYPTION_MODE + must be one of: + + server-authentication + Server-managed encryption is used for in-transit encryption. + transit-encryption-disabled + In-transit encryption is disabled. + + Represents persistence configuration for a instance. + + Configuration for AOF based persistence. + + --aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC + The fsync mode. AOF_CONFIG_APPEND_FSYNC must be one of: + + always + Fsync every time new write commands are appended to the AOF. + The best data loss protection at the cost of performance. + every-sec + Fsync every second. You may lose 1 second of data if there is a + disaster. + never + Never fsync. Normally Linux will flush data every 30 seconds + with this configuration, but it's up to the kernel's exact + tuning. + + --persistence-config-mode=PERSISTENCE_CONFIG_MODE + Current persistence mode. PERSISTENCE_CONFIG_MODE must be one of: + + aof + AOF based persistence is enabled. + disabled + Persistence is disabled, and any snapshot data is deleted. + rdb + RDB based persistence is enabled. + + Configuration for RDB based persistence. + + --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD + Period between RDB snapshots. RDB_CONFIG_SNAPSHOT_PERIOD must be + one of: + + one-hour + One hour. + six-hours + Six hours. + twelve-hours + Twelve hours. + twenty-four-hours + Twenty four hours. + + --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME + Time that the first snapshot was/will be attempted, and to which + future snapshots will be aligned. If not provided, the current time + will be used. + + Zone distribution configuration for allocation of instance resources. + + --zone-distribution-config=ZONE_DISTRIBUTION_CONFIG + Defines zone where all resources will be allocated with SINGLE_ZONE + mode. Ignored for MULTI_ZONE mode. + + --zone-distribution-config-mode=ZONE_DISTRIBUTION_CONFIG_MODE + Current zone distribution mode. Defaults to MULTI_ZONE. + ZONE_DISTRIBUTION_CONFIG_MODE must be one of: + + multi-zone + Distribute resources across 3 zones picked at random within the + region. + single-zone + Provision resources in a single zone. Zone field must be + specified. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1beta API. The full documentation for + this 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: + + $ gcloud alpha memorystore instances create + diff --git a/gcloud/beta/memorystore/instances/delete b/gcloud/beta/memorystore/instances/delete new file mode 100644 index 000000000..b62c213fa --- /dev/null +++ b/gcloud/beta/memorystore/instances/delete @@ -0,0 +1,87 @@ +NAME + gcloud beta memorystore instances delete - delete a Memorystore instance + +SYNOPSIS + gcloud beta memorystore instances delete (INSTANCE : --location=LOCATION) + [--async] [--request-id=REQUEST_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Memorystore instance. + +EXAMPLES + To delete Memorystore instance my-instance in project my-project and + location us-central1, run: + + $ gcloud beta memorystore instances delete my-instance \ + --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Instance resource - The name of the instance to delete. Format: + projects/{project}/locations/{location}/instances/{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 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the instance resource. + + 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. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes after the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memorystore/v1beta API. The full documentation for + this 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: + + $ gcloud alpha memorystore instances delete + diff --git a/gcloud/beta/memorystore/instances/describe b/gcloud/beta/memorystore/instances/describe new file mode 100644 index 000000000..eacfa0093 --- /dev/null +++ b/gcloud/beta/memorystore/instances/describe @@ -0,0 +1,68 @@ +NAME + gcloud beta memorystore instances describe - get details of a Memorystore + instance + +SYNOPSIS + gcloud beta memorystore instances describe (INSTANCE : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get details of a Memorystore instance. + +EXAMPLES + To get the details of Memorystore instance my-instance in project + my-project and location us-central, run: + + $ gcloud beta memorystore instances describe my-instance \ + --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Instance resource - The name of the instance to retrieve. Format: + projects/{project}/locations/{location}/instances/{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 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the instance resource. + + 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1beta API. The full documentation for + this 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: + + $ gcloud alpha memorystore instances describe + diff --git a/gcloud/beta/memorystore/instances/get-certificate-authority b/gcloud/beta/memorystore/instances/get-certificate-authority new file mode 100644 index 000000000..9e6e5d666 --- /dev/null +++ b/gcloud/beta/memorystore/instances/get-certificate-authority @@ -0,0 +1,68 @@ +NAME + gcloud beta memorystore instances get-certificate-authority - get + certificate authority details of a Memorystore instance + +SYNOPSIS + gcloud beta memorystore instances get-certificate-authority + (INSTANCE : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get certificate authority details of a Memorystore instance. + +EXAMPLES + To get the certificate authority for instance my-instance in project + my-project and location us-central1, run: + + $ gcloud beta memorystore instances get-certificate-authority \ + my-instance --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Instance resource - The name of the Memorystore instance. Format: + projects/{project}/locations/{location}/instances/{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 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location ID of the instance resource. + + 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1beta API. The full documentation for + this 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: + + $ gcloud alpha memorystore instances get-certificate-authority + diff --git a/gcloud/beta/memorystore/instances/help b/gcloud/beta/memorystore/instances/help new file mode 100644 index 000000000..f9e3bc3ec --- /dev/null +++ b/gcloud/beta/memorystore/instances/help @@ -0,0 +1,42 @@ +NAME + gcloud beta memorystore instances - manage Instance resources + +SYNOPSIS + gcloud beta memorystore instances COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Instance resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a Memorystore instance. + + delete + (BETA) Delete a Memorystore instance. + + describe + (BETA) Get details of a Memorystore instance. + + get-certificate-authority + (BETA) Get certificate authority details of a Memorystore instance. + + list + (BETA) List all Memorystore instances in a specified project and + location. + + update + (BETA) Update the configuration of a Memorystore instance. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore instances + diff --git a/gcloud/beta/memorystore/instances/list b/gcloud/beta/memorystore/instances/list new file mode 100644 index 000000000..0ad7d314f --- /dev/null +++ b/gcloud/beta/memorystore/instances/list @@ -0,0 +1,89 @@ +NAME + gcloud beta memorystore instances list - list all Memorystore instances in + a specified project and location + +SYNOPSIS + gcloud beta memorystore instances list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all Memorystore instances in a specified project and location. + +EXAMPLES + To list all Memorystore instances in project my-project and location + us-central, run: + + $ gcloud beta memorystore instances list --project=my-project \ + --location=us-central1 + +REQUIRED FLAGS + Location resource - The parent to list instances from. Format: + projects/{project}/locations/{location} This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memorystore/v1beta API. The full documentation for + this 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: + + $ gcloud alpha memorystore instances list + diff --git a/gcloud/beta/memorystore/instances/update b/gcloud/beta/memorystore/instances/update new file mode 100644 index 000000000..cc0261079 --- /dev/null +++ b/gcloud/beta/memorystore/instances/update @@ -0,0 +1,285 @@ +NAME + gcloud beta memorystore instances update - update the configuration of a + Memorystore instance + +SYNOPSIS + gcloud beta memorystore instances update (INSTANCE : --location=LOCATION) + [--async] [--deletion-protection-enabled] + [--replica-count=REPLICA_COUNT] [--request-id=REQUEST_ID] + [--shard-count=SHARD_COUNT] + [--aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC + --persistence-config-mode=PERSISTENCE_CONFIG_MODE + --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD + --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME] + [--engine-configs=[ENGINE_CONFIGS,...] + | --update-engine-configs=[UPDATE_ENGINE_CONFIGS,...] + --clear-engine-configs + | --remove-engine-configs=[__REMOVE_ENGINE_CONFIGS,...]] + [--labels=[LABELS,...] + | --update-labels=[UPDATE_LABELS,...] --clear-labels + | --remove-labels=[__REMOVE_LABELS,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the configuration of a Memorystore instance. + +EXAMPLES + To update Memorystore instance my-instance in project my-project and + location us-central1 to six shards, run: + + $ gcloud beta memorystore instances update `my-instance` \ + --project=my-project --location=us-central1 --shard-count=6 + + To update Memorystore instance my-instance in project my-project and + location us-central1 to use a maxmemory-policy of allkeys-lru, run: + + $ gcloud beta memorystore instances update `my-instance` \ + --project=my-project --location=us-central1 \ + --update-engine-configs=maxmemory-policy=allkeys-lru + +POSITIONAL ARGUMENTS + Instance resource - Identifier. Unique name of the instance. Format: + projects/{project}/locations/{location}/instances/{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 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location id of the instance resource. + + 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. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + Arguments for the deletion protection enabled. + + --deletion-protection-enabled + If set to true deletion of the instance will fail. + + Arguments for the replica count. + + --replica-count=REPLICA_COUNT + Number of replica nodes per shard. If omitted the default is 0 + replicas. + + --request-id=REQUEST_ID + An optional request ID to identify requests. Specify a unique request + ID so that if you must retry your request, the server will know to + ignore the request if it has already been completed. The server will + guarantee that for at least 60 minutes since the first request. + + For example, consider a situation where you make an initial request and + the request times out. If you make the request again with the same + request ID, the server can check if original operation with the same + request ID was received, and if so, will ignore the second request. + This prevents clients from accidentally creating duplicate commitments. + + The request ID must be a valid UUID with the exception that zero UUID + is not supported (00000000-0000-0000-0000-000000000000). + + --shard-count=SHARD_COUNT + Number of shards for the instance. + + Represents persistence configuration for a instance. + + Configuration for AOF based persistence. + + --aof-config-append-fsync=AOF_CONFIG_APPEND_FSYNC + The fsync mode. AOF_CONFIG_APPEND_FSYNC must be one of: + + always + Fsync every time new write commands are appended to the AOF. + The best data loss protection at the cost of performance. + every-sec + Fsync every second. You may lose 1 second of data if there is a + disaster. + never + Never fsync. Normally Linux will flush data every 30 seconds + with this configuration, but it's up to the kernel's exact + tuning. + + --persistence-config-mode=PERSISTENCE_CONFIG_MODE + Current persistence mode. PERSISTENCE_CONFIG_MODE must be one of: + + aof + AOF based persistence is enabled. + disabled + Persistence is disabled, and any snapshot data is deleted. + rdb + RDB based persistence is enabled. + + Configuration for RDB based persistence. + + --rdb-config-snapshot-period=RDB_CONFIG_SNAPSHOT_PERIOD + Period between RDB snapshots. RDB_CONFIG_SNAPSHOT_PERIOD must be + one of: + + one-hour + One hour. + six-hours + Six hours. + twelve-hours + Twelve hours. + twenty-four-hours + Twenty four hours. + + --rdb-config-snapshot-start-time=RDB_CONFIG_SNAPSHOT_START_TIME + Time that the first snapshot was/will be attempted, and to which + future snapshots will be aligned. If not provided, the current time + will be used. + + Update engine_configs. + + At most one of these can be specified: + + --engine-configs=[ENGINE_CONFIGS,...] + Set engine_configs to new value. User-provided engine configurations + for the instance. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --engine-configs=string=string + + JSON Example: + + --engine-configs='{"string": "string"}' + + File Example: + + --engine-configs=path_to_file.(yaml|json) + + --update-engine-configs=[UPDATE_ENGINE_CONFIGS,...] + Update engine_configs value or add key value pair. User-provided + engine configurations for the instance. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --update-engine-configs=string=string + + JSON Example: + + --update-engine-configs='{"string": "string"}' + + File Example: + + --update-engine-configs=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-engine-configs + Clear engine_configs value and set to empty map. + + --remove-engine-configs=[__REMOVE_ENGINE_CONFIGS,...] + Remove existing value from map engine_configs. + + Update labels. + + At most one of these can be specified: + + --labels=[LABELS,...] + Set labels to new value. Labels to represent user-provided metadata. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --labels=string=string + + JSON Example: + + --labels='{"string": "string"}' + + File Example: + + --labels=path_to_file.(yaml|json) + + --update-labels=[UPDATE_LABELS,...] + Update labels value or add key value pair. Labels to represent + user-provided metadata. + + KEY + Keys must start with a lowercase character and contain only + hyphens (-), underscores (_), lowercase characters, and numbers. + + VALUE + Values must contain only hyphens (-), underscores (_), lowercase + characters, and numbers. + + Shorthand Example: + + --update-labels=string=string + + JSON Example: + + --update-labels='{"string": "string"}' + + File Example: + + --update-labels=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-labels + Clear labels value and set to empty map. + + --remove-labels=[__REMOVE_LABELS,...] + Remove existing value from map labels. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1beta API. The full documentation for + this 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: + + $ gcloud alpha memorystore instances update + diff --git a/gcloud/beta/memorystore/operations/cancel b/gcloud/beta/memorystore/operations/cancel new file mode 100644 index 000000000..ebe5dfdca --- /dev/null +++ b/gcloud/beta/memorystore/operations/cancel @@ -0,0 +1,66 @@ +NAME + gcloud beta memorystore operations cancel - cancel a Memorystore operation + +SYNOPSIS + gcloud beta memorystore operations cancel (OPERATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Cancel a Memorystore operation. + +EXAMPLES + To cancel operation my-operation in project my-project and location + us-central1, run: + + $ gcloud beta memorystore operations cancel my-operation \ + --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - The Memorystore operation to cancel. 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location ID of the operation resource. + + 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1beta API. The full documentation for + this 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: + + $ gcloud alpha memorystore operations cancel + diff --git a/gcloud/beta/memorystore/operations/delete b/gcloud/beta/memorystore/operations/delete new file mode 100644 index 000000000..ffd49caba --- /dev/null +++ b/gcloud/beta/memorystore/operations/delete @@ -0,0 +1,66 @@ +NAME + gcloud beta memorystore operations delete - delete a Memorystore operation + +SYNOPSIS + gcloud beta memorystore operations delete (OPERATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Memorystore operation. + +EXAMPLES + To delete operation my-operation in project my-project and location + us-central1, run: + + $ gcloud beta memorystore operations delete my-operation \ + --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - The Memorystore operation 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 operation 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. + + 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location ID of the operation resource. + + 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1beta API. The full documentation for + this 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: + + $ gcloud alpha memorystore operations delete + diff --git a/gcloud/beta/memorystore/operations/describe b/gcloud/beta/memorystore/operations/describe new file mode 100644 index 000000000..0d2d03235 --- /dev/null +++ b/gcloud/beta/memorystore/operations/describe @@ -0,0 +1,67 @@ +NAME + gcloud beta memorystore operations describe - describe a Memorystore + operation + +SYNOPSIS + gcloud beta memorystore operations describe + (OPERATION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Memorystore operation. + +EXAMPLES + To describe operation my-operation in project my-project and location + us-central1, run: + + $ gcloud beta memorystore operations describe my-operation \ + --project=my-project --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - The Memorystore 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; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location ID of the operation resource. + + 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 memorystore/v1beta API. The full documentation for + this 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: + + $ gcloud alpha memorystore operations describe + diff --git a/gcloud/beta/memorystore/operations/help b/gcloud/beta/memorystore/operations/help new file mode 100644 index 000000000..6675cc402 --- /dev/null +++ b/gcloud/beta/memorystore/operations/help @@ -0,0 +1,35 @@ +NAME + gcloud beta memorystore operations - manage Memorystore operations + +SYNOPSIS + gcloud beta memorystore operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Memorystore operations. + +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) Cancel a Memorystore operation. + + delete + (BETA) Delete a Memorystore operation. + + describe + (BETA) Describe a Memorystore operation. + + list + (BETA) List Memorystore operations. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha memorystore operations + diff --git a/gcloud/beta/memorystore/operations/list b/gcloud/beta/memorystore/operations/list new file mode 100644 index 000000000..a868e0332 --- /dev/null +++ b/gcloud/beta/memorystore/operations/list @@ -0,0 +1,87 @@ +NAME + gcloud beta memorystore operations list - list Memorystore operations + +SYNOPSIS + gcloud beta memorystore operations list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Memorystore operations. + +EXAMPLES + To list Memorystore operations in project my-project and location + us-central1, run: + + $ gcloud beta memorystore operations list --project=my-project \ + --location=us-central1 + +REQUIRED FLAGS + Location resource - The parent collection of the Memorystore operations. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the memorystore/v1beta API. The full documentation for + this 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: + + $ gcloud alpha memorystore operations list + diff --git a/gcloud/beta/notebooks/instances/create b/gcloud/beta/notebooks/instances/create index f63e87f70..852a17e9c 100644 --- a/gcloud/beta/notebooks/instances/create +++ b/gcloud/beta/notebooks/instances/create @@ -167,7 +167,7 @@ FLAGS NVIDIA_TESLA_A100, NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, - TPU_V2, TPU_V3, NVIDIA_L4. + TPU_V2, TPU_V3, NVIDIA_L4, NVIDIA_H100_80GB, NVIDIA_H100_MEGA_80GB. Boot disk configurations. diff --git a/gcloud/beta/notebooks/instances/update b/gcloud/beta/notebooks/instances/update index d7aaedfcd..1937ec327 100644 --- a/gcloud/beta/notebooks/instances/update +++ b/gcloud/beta/notebooks/instances/update @@ -78,7 +78,7 @@ REQUIRED FLAGS NVIDIA_TESLA_A100, NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, - TPU_V2, TPU_V3, NVIDIA_L4. + TPU_V2, TPU_V3, NVIDIA_L4, NVIDIA_H100_80GB, NVIDIA_H100_MEGA_80GB. --labels=[KEY=VALUE,...] Labels to apply to this instance. These can be later modified by the diff --git a/gcloud/beta/projects/create b/gcloud/beta/projects/create index d38414676..a204874dd 100644 --- a/gcloud/beta/projects/create +++ b/gcloud/beta/projects/create @@ -62,7 +62,7 @@ FLAGS ID for the organization to use as a parent --set-as-default - Set newly created project as [core.project] property. + Set newly created project as [core/project] property. --tags=[KEY=VALUE,...] List of tags KEY=VALUE pairs to bind. Each item must be expressed as diff --git a/gcloud/beta/redis/clusters/create b/gcloud/beta/redis/clusters/create index f7f9ae94a..1a490b004 100644 --- a/gcloud/beta/redis/clusters/create +++ b/gcloud/beta/redis/clusters/create @@ -5,8 +5,10 @@ NAME SYNOPSIS gcloud beta redis clusters create (CLUSTER : --region=REGION) --network=NETWORK [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] - [--auth-mode=AUTH_MODE] [--deletion-protection] [--node-type=NODE_TYPE] - [--persistence-mode=PERSISTENCE_MODE] + [--auth-mode=AUTH_MODE] [--deletion-protection] + [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] + [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--node-type=NODE_TYPE] [--persistence-mode=PERSISTENCE_MODE] [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--redis-config=[KEY=VALUE,...]] [--replica-count=REPLICA_COUNT] @@ -116,6 +118,15 @@ OPTIONAL FLAGS Enable deletion protection for the Redis Cluster. Use --deletion-protection/--no-deletion-protection to enable/disable it. + --maintenance-window-day=MAINTENANCE_WINDOW_DAY + 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-hour=MAINTENANCE_WINDOW_HOUR + Hour of day (0 to 23) for the start of maintenance window, in UTC time + zone. + --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, diff --git a/gcloud/beta/redis/clusters/help b/gcloud/beta/redis/clusters/help index 10333b1e7..f1610caa0 100644 --- a/gcloud/beta/redis/clusters/help +++ b/gcloud/beta/redis/clusters/help @@ -37,6 +37,10 @@ COMMANDS list (BETA) List Memorystore for Redis Cluster instances. + reschedule-maintenance + (BETA) Reschedule maintenance window for a Memorystore for Redis + Cluster instance. + switchover (BETA) Switchover to a secondary cluster. diff --git a/gcloud/beta/redis/clusters/reschedule-maintenance b/gcloud/beta/redis/clusters/reschedule-maintenance new file mode 100644 index 000000000..acc0f9dd8 --- /dev/null +++ b/gcloud/beta/redis/clusters/reschedule-maintenance @@ -0,0 +1,93 @@ +NAME + gcloud beta redis clusters reschedule-maintenance - reschedule maintenance + window for a Memorystore for Redis Cluster instance + +SYNOPSIS + gcloud beta redis clusters reschedule-maintenance + (CLUSTER : --region=REGION) --reschedule-type=RESCHEDULE_TYPE [--async] + [--schedule-time=SCHEDULE_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Reschedule maintenance window for a Memorystore for Redis Cluster + instance. + +EXAMPLES + To reschedule maintenance window for an instance with the name + 'my-redis-cluster' in region 'us-central-1' with immediate, run: + + $ gcloud beta redis clusters reschedule-maintenance \ + my-redis-cluster --region=us-central1 \ + --reschedule-type=IMMEDIATE + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Cloud Memorystore + for Redis cluster 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/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. + 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 redis/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud redis clusters reschedule-maintenance + + $ gcloud alpha redis clusters reschedule-maintenance + diff --git a/gcloud/beta/redis/clusters/update b/gcloud/beta/redis/clusters/update index b7eb6b532..9cbe22bc3 100644 --- a/gcloud/beta/redis/clusters/update +++ b/gcloud/beta/redis/clusters/update @@ -10,6 +10,9 @@ SYNOPSIS [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] [--shard-count=SHARD_COUNT] [--update-redis-config=KEY=VALUE] + [--maintenance-window-any + | --maintenance-window-day=MAINTENANCE_WINDOW_DAY + --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -124,6 +127,20 @@ FLAGS parameter is already set, its value is modified; otherwise a new Redis config parameter is added. + 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-hour=MAINTENANCE_WINDOW_HOUR + Hour of day (0 to 23) for the start of maintenance window, in UTC + time zone. + 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/run/deploy b/gcloud/beta/run/deploy index 80edf32dc..fa1176a0e 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -37,7 +37,8 @@ SYNOPSIS --[no-]default-url --[no-]deploy-health-check --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT --gpu-type=GPU_TYPE - --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX + --mesh=MESH --remove-containers=[CONTAINER,...] + --revision-suffix=REVISION_SUFFIX --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -550,6 +551,11 @@ FLAGS --gpu-type=GPU_TYPE The GPU type to use. + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. + Mesh resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + --remove-containers=[CONTAINER,...] List of containers to remove. diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 130be2502..497ad23d5 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -22,7 +22,8 @@ SYNOPSIS [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling --[no-]default-url --[no-]deploy-health-check --execution-environment=EXECUTION_ENVIRONMENT --gpu-type=GPU_TYPE - --remove-containers=[CONTAINER,...] --revision-suffix=REVISION_SUFFIX + --mesh=MESH --remove-containers=[CONTAINER,...] + --revision-suffix=REVISION_SUFFIX --service-min-instances=SERVICE_MIN_INSTANCES --[no-]session-affinity --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -349,6 +350,11 @@ FLAGS --gpu-type=GPU_TYPE The GPU type to use. + --mesh=MESH + Enables Cloud Service Mesh using the specified mesh resource name. + Mesh resource name must be in the format of + projects/PROJECT/locations/global/meshes/MESH_NAME. + --remove-containers=[CONTAINER,...] List of containers to remove. diff --git a/gcloud/compute/future-reservations/cancel b/gcloud/compute/future-reservations/cancel new file mode 100644 index 000000000..d8e753ce8 --- /dev/null +++ b/gcloud/compute/future-reservations/cancel @@ -0,0 +1,74 @@ +NAME + gcloud compute future-reservations cancel - cancel a Compute Engine future + reservation + +SYNOPSIS + gcloud compute future-reservations cancel + (FUTURE_RESERVATION : --zone=ZONE) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Cancel a Compute Engine future reservation. + +EXAMPLES + To cancel a given Compute Engine future reservation, run: + + $ gcloud compute future-reservations cancel my-reservation \ + --zone=ZONE + +POSITIONAL ARGUMENTS + Future reservation resource - The name of the future reservation to + cancel. 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 future_reservation 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. + + FUTURE_RESERVATION + ID of the future reservation or fully qualified identifier for the + future reservation. + + To set the future_reservation attribute: + ▸ provide the argument future_reservation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --zone=ZONE + The name of the Google Compute Engine zone. + + To set the zone attribute: + ▸ provide the argument future_reservation on the command line with + a fully specified name; + ▸ provide the argument --zone on the command line; + ▸ set the property compute/zone. + +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 compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute future-reservations cancel + + $ gcloud beta compute future-reservations cancel + diff --git a/gcloud/compute/future-reservations/create b/gcloud/compute/future-reservations/create new file mode 100644 index 000000000..a567d0aac --- /dev/null +++ b/gcloud/compute/future-reservations/create @@ -0,0 +1,205 @@ +NAME + gcloud compute future-reservations create - create a Compute Engine + reservation + +SYNOPSIS + gcloud compute future-reservations create FUTURE_RESERVATION + --[no-]auto-delete-auto-created-reservations --total-count=TOTAL_COUNT + (--source-instance-template=SOURCE_INSTANCE_TEMPLATE + | [--machine-type=MACHINE_TYPE + : --accelerator=[count=COUNT],[type=TYPE] + --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE] + --min-cpu-platform=MIN_CPU_PLATFORM]) + (--start-time=START_TIME (--duration=DURATION | --end-time=END_TIME)) + [--description=DESCRIPTION] [--name-prefix=NAME_PREFIX] + [--planning-status=PLANNING_STATUS] [--zone=ZONE] + [--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME | --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION] + [--share-setting=SHARE_SETTING --share-with=PROJECT,[PROJECT,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Compute Engine reservation. + +POSITIONAL ARGUMENTS + FUTURE_RESERVATION + Name of the future reservation to create. + +REQUIRED FLAGS + --[no-]auto-delete-auto-created-reservations + If specified, the auto-created reservations for a future reservation + are deleted at the end time (default) or at a specified delete time. + Use --auto-delete-auto-created-reservations to enable and + --no-auto-delete-auto-created-reservations to disable. + + --total-count=TOTAL_COUNT + The total number of instances for which capacity assurance is requested + at a future time period. + + Manage the instance properties for the auto-created reservations. You must + either provide a source instance template or define the instance + properties. + + Exactly one of these must be specified: + + --source-instance-template=SOURCE_INSTANCE_TEMPLATE + The url of the instance template that will be used to populate the + fields of the reservation. Instance properties can not be defined in + addition to source instance template. + + Define individual instance properties for the specific SKU reservation. + + --machine-type=MACHINE_TYPE + The type of machine (name only) that has a fixed number of vCPUs + and a fixed amount of memory. You can also specify a custom machine + type by using the pattern + custom-number_of_CPUs-amount_of_memory-for example, + custom-32-29440. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --accelerator=[count=COUNT],[type=TYPE] + Manage the configuration of the type and number of accelerator + cards attached. + count + The number of accelerators to attach to each instance in the + reservation. + type + The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) + of accelerator to attach to instances in the reservation. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. + + --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE] + Manage the size and the interface of local SSD to use. See + https://cloud.google.com/compute/docs/disks/local-ssd for more + information. + interface + The kind of disk interface exposed to the VM for this SSD. + Valid values are scsi and nvme. SCSI is the default and is + supported by more guest operating systems. NVME may provide + higher performance. + size + The size of the local SSD in base-2 GB. + count + The number of local SSD to use per VM. Default value is 1. + + --min-cpu-platform=MIN_CPU_PLATFORM + Optional minimum CPU platform of the reservation to create. + + Manage the time specific properties for requesting future capacity + + This must be specified. + + --start-time=START_TIME + Start time of the Future Reservation. The start time must be an + RFC3339 valid string formatted by date, time, and timezone or + "YYYY-MM-DDTHH:MM:SSZ"; where YYYY = year, MM = month, DD = day, HH = + hours, MM = minutes, SS = seconds, and Z = timezone (i.e. + 2021-11-20T07:00:00Z). + + This flag argument must be specified if any of the other arguments in + this group are specified. + + Exactly one of these must be specified: + + --duration=DURATION + Alternate way of specifying time in the number of seconds to + terminate capacity request relative to the start time of a request. + + --end-time=END_TIME + End time of the Future Reservation. The end time must be an RFC3339 + valid string formatted by date, time, and timezone or + "YYYY-MM-DDTHH:MM:SSZ"; where YYYY = year, MM = month, DD = day, HH + = hours, MM = minutes, SS = seconds, and Z = timezone (i.e. + 2021-11-20T07:00:00Z). + +OPTIONAL FLAGS + --description=DESCRIPTION + An optional description of the future reservation to create. + + --name-prefix=NAME_PREFIX + A name prefix for the auto-created reservations when capacity is + delivered at the start time. Each auto-created reservation name starts + with the name prefix. + + --planning-status=PLANNING_STATUS + The planning status of the future reservation. The default value is + DRAFT. While in DRAFT, any changes to the future reservation's + properties will be allowed. If set to SUBMITTED, the future reservation + will submit and its procurementStatus will change to PENDING_APPROVAL. + Once the future reservation is pending approval, changes to the future + reservation's properties will not be allowed. PLANNING_STATUS must be + one of: + + DRAFT + Default planning status value. + SUBMITTED + Planning status value to immediately submit the future reservation. + + --zone=ZONE + Zone of the future reservation to create. If not specified and the + compute/zone property isn't set, you might be prompted to select a zone + (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + + Manage the auto-delete time properties. + + At most one of these can be specified: + + --auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME + Automatically deletes an auto-created reservations at a specific + time. The specified time must be an RFC3339 timestamp, which must be + formatted as "YYYY-MM-DDTHH:MM:SSZ" where YYYY = year, MM = month, DD + = day, HH = hours, MM = minutes, SS = seconds, and Z = time zone in + Coordinated Universal Time (UTC). For example, specify + 2021-11-20T07:00:00Z. + + --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION + Automatically deletes an auto-created reservations after a specified + number of days, hours, minutes, or seconds. For example, specify 30m + for 30 minutes, or 1d2h3m4s for 1 day, 2 hours, 3 minutes, and 4 + seconds. For more information, see $ gcloud topic datetimes. + + Manage the properties of a shared reservation. + + --share-setting=SHARE_SETTING + Specify if this future reservation is shared, and if so, the type of + sharing. If you omit this flag, this value is local by default. + SHARE_SETTING must be one of: local, projects. + + --share-with=PROJECT,[PROJECT,...] + If this future reservation is shared, provide a comma-separated list + of projects that this future reservation is shared with. The list + must contain project IDs or project numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha compute future-reservations create + + $ gcloud beta compute future-reservations create + diff --git a/gcloud/compute/future-reservations/delete b/gcloud/compute/future-reservations/delete new file mode 100644 index 000000000..83bd407a0 --- /dev/null +++ b/gcloud/compute/future-reservations/delete @@ -0,0 +1,74 @@ +NAME + gcloud compute future-reservations delete - delete a Compute Engine future + reservation + +SYNOPSIS + gcloud compute future-reservations delete + (FUTURE_RESERVATION : --zone=ZONE) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Compute Engine future reservation. + +EXAMPLES + To delete a given Compute Engine future reservation, run: + + $ gcloud compute future-reservations delete my-reservation \ + --zone=ZONE + +POSITIONAL ARGUMENTS + Future reservation resource - The name of the future reservation 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 future_reservation 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. + + FUTURE_RESERVATION + ID of the future reservation or fully qualified identifier for the + future reservation. + + To set the future_reservation attribute: + ▸ provide the argument future_reservation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --zone=ZONE + The name of the Google Compute Engine zone. + + To set the zone attribute: + ▸ provide the argument future_reservation on the command line with + a fully specified name; + ▸ provide the argument --zone on the command line; + ▸ set the property compute/zone. + +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 compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute future-reservations delete + + $ gcloud beta compute future-reservations delete + diff --git a/gcloud/compute/future-reservations/describe b/gcloud/compute/future-reservations/describe new file mode 100644 index 000000000..5a9903eee --- /dev/null +++ b/gcloud/compute/future-reservations/describe @@ -0,0 +1,69 @@ +NAME + gcloud compute future-reservations describe - show details about a Compute + Engine future reservation + +SYNOPSIS + gcloud compute future-reservations describe + (FUTURE_RESERVATION : --zone=ZONE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details about a Compute Engine future reservation. + +EXAMPLES + To describe a given Compute Engine future reservation, run: + + $ gcloud compute future-reservations describe my-reservation \ + --zone=ZONE + +POSITIONAL ARGUMENTS + Future reservation resource - The name of the future reservation 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 future_reservation 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. + + FUTURE_RESERVATION + ID of the future reservation or fully qualified identifier for the + future reservation. + + To set the future_reservation attribute: + ▸ provide the argument future_reservation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --zone=ZONE + The name of the Google Compute Engine zone. + + To set the zone attribute: + ▸ provide the argument future_reservation on the command line with + a fully specified name; + ▸ provide the argument --zone on the command line; + ▸ set the property compute/zone. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the compute/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/compute/ + +NOTES + These variants are also available: + + $ gcloud alpha compute future-reservations describe + + $ gcloud beta compute future-reservations describe + diff --git a/gcloud/compute/future-reservations/help b/gcloud/compute/future-reservations/help new file mode 100644 index 000000000..00539551b --- /dev/null +++ b/gcloud/compute/future-reservations/help @@ -0,0 +1,43 @@ +NAME + gcloud compute future-reservations - manage Compute Engine future + reservations + +SYNOPSIS + gcloud compute future-reservations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Compute Engine future reservations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + Cancel a Compute Engine future reservation. + + create + Create a Compute Engine reservation. + + delete + Delete a Compute Engine future reservation. + + describe + Show details about a Compute Engine future reservation. + + list + List Compute Engine future reservations. + + update + Update Compute Engine future reservations. + +NOTES + These variants are also available: + + $ gcloud alpha compute future-reservations + + $ gcloud beta compute future-reservations + diff --git a/gcloud/compute/future-reservations/list b/gcloud/compute/future-reservations/list new file mode 100644 index 000000000..b6b5af6a1 --- /dev/null +++ b/gcloud/compute/future-reservations/list @@ -0,0 +1,64 @@ +NAME + gcloud compute future-reservations list - list Compute Engine future + reservations + +SYNOPSIS + gcloud compute future-reservations list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Compute Engine future reservations. + +EXAMPLES + To list all Compute Engine future reservations, run: + + $ gcloud compute future-reservations list my-future-reservation + +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 compute future-reservations list + + $ gcloud beta compute future-reservations list + diff --git a/gcloud/compute/future-reservations/update b/gcloud/compute/future-reservations/update new file mode 100644 index 000000000..c6749dbb6 --- /dev/null +++ b/gcloud/compute/future-reservations/update @@ -0,0 +1,222 @@ +NAME + gcloud compute future-reservations update - update Compute Engine future + reservations + +SYNOPSIS + gcloud compute future-reservations update FUTURE_RESERVATION + [--[no-]auto-delete-auto-created-reservations] + [--description=DESCRIPTION] [--planning-status=PLANNING_STATUS] + [--total-count=TOTAL_COUNT] [--zone=ZONE] + [--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME | --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION] + [--clear-name-prefix | --name-prefix=NAME_PREFIX] + [--clear-share-settings + | --share-setting=SHARE_SETTING --share-with=PROJECT,[PROJECT,...]] + [--machine-type=MACHINE_TYPE --min-cpu-platform=MIN_CPU_PLATFORM + --accelerator=[count=COUNT],[type=TYPE] + | --clear-accelerator --clear-local-ssd + | --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE]] + [--start-time=START_TIME --duration=DURATION | --end-time=END_TIME] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update Compute Engine future reservations. + +EXAMPLES + To update total count, start and end time of a Compute Engine future + reservation in us-central1-a, run: + + $ gcloud compute future-reservations update my-future-reservation \ + --total-count=1000 --start-time=2021-11-10T07:00:00Z \ + --end-time=2021-12-10T07:00:00Z --zone=us-central1-a + +POSITIONAL ARGUMENTS + FUTURE_RESERVATION + Name of the future reservation to update. + +FLAGS + --[no-]auto-delete-auto-created-reservations + If specified, the auto-created reservations for a future reservation + are deleted at the end time (default) or at a specified delete time. + Use --auto-delete-auto-created-reservations to enable and + --no-auto-delete-auto-created-reservations to disable. + + --description=DESCRIPTION + An optional description of the future reservation to create. + + --planning-status=PLANNING_STATUS + The planning status of the future reservation. The default value is + DRAFT. While in DRAFT, any changes to the future reservation's + properties will be allowed. If set to SUBMITTED, the future reservation + will submit and its procurementStatus will change to PENDING_APPROVAL. + Once the future reservation is pending approval, changes to the future + reservation's properties will not be allowed. PLANNING_STATUS must be + one of: + + DRAFT + Default planning status value. + SUBMITTED + Planning status value to immediately submit the future reservation. + + --total-count=TOTAL_COUNT + The total number of instances for which capacity assurance is requested + at a future time period. + + --zone=ZONE + Zone of the future reservation to update. If not specified and the + compute/zone property isn't set, you might be prompted to select a zone + (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + + Manage the auto-delete time properties. + + At most one of these can be specified: + + --auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME + Automatically deletes an auto-created reservations at a specific + time. The specified time must be an RFC3339 timestamp, which must be + formatted as "YYYY-MM-DDTHH:MM:SSZ" where YYYY = year, MM = month, DD + = day, HH = hours, MM = minutes, SS = seconds, and Z = time zone in + Coordinated Universal Time (UTC). For example, specify + 2021-11-20T07:00:00Z. + + --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION + Automatically deletes an auto-created reservations after a specified + number of days, hours, minutes, or seconds. For example, specify 30m + for 30 minutes, or 1d2h3m4s for 1 day, 2 hours, 3 minutes, and 4 + seconds. For more information, see $ gcloud topic datetimes. + + Manage the name-prefix of a future reservation. + + At most one of these can be specified: + + --clear-name-prefix + Clears the name prefix for the system generated reservations. + + --name-prefix=NAME_PREFIX + A name prefix for the auto-created reservations when capacity is + delivered at the start time. Each auto-created reservation name + starts with the name prefix. + + Manage the properties of a shared future reservation. + + At most one of these can be specified: + + --clear-share-settings + Clear share settings on future reservation. This will result in + non-shared future reservation. + + Manage the share settings of a future reservation. + + --share-setting=SHARE_SETTING + Specify if this future reservation is shared, and if so, the type + of sharing. If you omit this flag, this value is local by default. + SHARE_SETTING must be one of: local, projects. + + --share-with=PROJECT,[PROJECT,...] + If this future reservation is shared, provide a comma-separated + list of projects that this future reservation is shared with. The + list must contain project IDs or project numbers. + + Manage the specific SKU reservation properties. + + --machine-type=MACHINE_TYPE + The type of machine (name only) that has a fixed number of vCPUs and + a fixed amount of memory. You can also specify a custom machine type + by using the pattern custom-number_of_CPUs-amount_of_memory-for + example, custom-32-29440. + + --min-cpu-platform=MIN_CPU_PLATFORM + Optional minimum CPU platform of the reservation to create. + + Manage the accelerators of a future reservation. + + At most one of these can be specified: + + --accelerator=[count=COUNT],[type=TYPE] + Manage the configuration of the type and number of accelerator + cards attached. + count + The number of accelerators to attach to each instance in the + reservation. + type + The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) + of accelerator to attach to instances in the reservation. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. + + --clear-accelerator + Remove all accelerators from the future reservation. + + Manage the local ssd of a future reservation. + + At most one of these can be specified: + + --clear-local-ssd + Remove all local ssd information on the future reservation. + + --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE] + Manage the size and the interface of local SSD to use. See + https://cloud.google.com/compute/docs/disks/local-ssd for more + information. + interface + The kind of disk interface exposed to the VM for this SSD. + Valid values are scsi and nvme. SCSI is the default and is + supported by more guest operating systems. NVME may provide + higher performance. + size + The size of the local SSD in base-2 GB. + count + The number of local SSD to use per VM. Default value is 1. + + Manage the time specific properties for requesting future capacity + + --start-time=START_TIME + Start time of the Future Reservation. The start time must be an + RFC3339 valid string formatted by date, time, and timezone or + "YYYY-MM-DDTHH:MM:SSZ"; where YYYY = year, MM = month, DD = day, HH = + hours, MM = minutes, SS = seconds, and Z = timezone (i.e. + 2021-11-20T07:00:00Z). + + At most one of these can be specified: + + --duration=DURATION + Alternate way of specifying time in the number of seconds to + terminate capacity request relative to the start time of a request. + + --end-time=END_TIME + End time of the Future Reservation. The end time must be an RFC3339 + valid string formatted by date, time, and timezone or + "YYYY-MM-DDTHH:MM:SSZ"; where YYYY = year, MM = month, DD = day, HH + = hours, MM = minutes, SS = seconds, and Z = timezone (i.e. + 2021-11-20T07:00:00Z). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 future-reservations update + + $ gcloud beta compute future-reservations update + diff --git a/gcloud/compute/help b/gcloud/compute/help index 9c88a608d..9366f4c47 100644 --- a/gcloud/compute/help +++ b/gcloud/compute/help @@ -60,6 +60,9 @@ GROUPS forwarding-rules Read and manipulate traffic forwarding rules to network load balancers. + future-reservations + Manage Compute Engine future reservations. + health-checks Read and manipulate health checks for load balanced instances. diff --git a/gcloud/compute/resource-policies/update/instance-schedule b/gcloud/compute/resource-policies/update/instance-schedule index aaf5075ae..c64cc0eac 100644 --- a/gcloud/compute/resource-policies/update/instance-schedule +++ b/gcloud/compute/resource-policies/update/instance-schedule @@ -16,10 +16,8 @@ EXAMPLES To update an instance schedule resource policy with specified parameters: $ gcloud compute resource-policies update instance-schedule NAME \ - --region=REGION --timezone=UTC --vm-start-schedule="* 7 * * *" \ - --vm-stop-schedule="* 17 * * *" \ - --initiation-date=2025-05-01T00:00:00.000-07:00 \ - --end-date=2027-05-01T00:00:00.000-07:00 + --region=REGION --timezone=UTC --vm-start-schedule="0 7 * * *" \ + --vm-stop-schedule="0 17 * * *" POSITIONAL ARGUMENTS NAME diff --git a/gcloud/container/clusters/check-autopilot-compatibility b/gcloud/container/clusters/check-autopilot-compatibility index 14b1fa4de..0eeef6097 100644 --- a/gcloud/container/clusters/check-autopilot-compatibility +++ b/gcloud/container/clusters/check-autopilot-compatibility @@ -26,10 +26,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 0468460c0..b0d0fb77e 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -102,6 +102,8 @@ SYNOPSIS [--enable-autoscaling --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES --min-nodes=MIN_NODES --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES] + [--enable-insecure-binding-system-authenticated + --enable-insecure-binding-system-unauthenticated] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-network-egress-metering @@ -1695,6 +1697,23 @@ FLAGS --node-pool (or default node pool if unspecified) can scale. Ignored unless --enable-autoscaling is also specified. + --enable-insecure-binding-system-authenticated + Allow using system:authenticated as a subject in ClusterRoleBindings + and RoleBindings. Allowing bindings that reference system:authenticated + is a security risk and is not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-authenticated flag instead. + + --enable-insecure-binding-system-unauthenticated + Allow using system:unauthenticated and system:anonymous as subjects in + ClusterRoleBindings and RoleBindings. Allowing bindings that reference + system:unauthenticated and system:anonymous are a security risk and is + not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-unauthenticated flag instead. + Master Authorized Networks --enable-master-authorized-networks @@ -1845,10 +1864,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index 14d53f610..5bd1aede7 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -31,6 +31,8 @@ SYNOPSIS [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] + [--enable-insecure-binding-system-authenticated + --enable-insecure-binding-system-unauthenticated] [--enable-master-authorized-networks --master-authorized-networks=NETWORK,[NETWORK,...]] [--enable-private-endpoint @@ -493,6 +495,23 @@ FLAGS Enables Advanced Datapath Observability which allows for a real-time view into pod-to-pod traffic within your cluster. + --enable-insecure-binding-system-authenticated + Allow using system:authenticated as a subject in ClusterRoleBindings + and RoleBindings. Allowing bindings that reference system:authenticated + is a security risk and is not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-authenticated flag instead. + + --enable-insecure-binding-system-unauthenticated + Allow using system:unauthenticated and system:anonymous as subjects in + ClusterRoleBindings and RoleBindings. Allowing bindings that reference + system:unauthenticated and system:anonymous are a security risk and is + not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-unauthenticated flag instead. + Master Authorized Networks --enable-master-authorized-networks @@ -535,10 +554,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/clusters/delete b/gcloud/container/clusters/delete index 696c55690..abba46e8d 100644 --- a/gcloud/container/clusters/delete +++ b/gcloud/container/clusters/delete @@ -42,10 +42,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/clusters/describe b/gcloud/container/clusters/describe index a929cb171..59048aa1d 100644 --- a/gcloud/container/clusters/describe +++ b/gcloud/container/clusters/describe @@ -24,10 +24,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/clusters/get-credentials b/gcloud/container/clusters/get-credentials index 44745a42f..d8aab5edf 100644 --- a/gcloud/container/clusters/get-credentials +++ b/gcloud/container/clusters/get-credentials @@ -56,10 +56,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/clusters/help b/gcloud/container/clusters/help index 7273649c6..1715e6ed6 100644 --- a/gcloud/container/clusters/help +++ b/gcloud/container/clusters/help @@ -19,10 +19,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/clusters/list b/gcloud/container/clusters/list index ef01d30ad..e63f47d34 100644 --- a/gcloud/container/clusters/list +++ b/gcloud/container/clusters/list @@ -24,10 +24,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/clusters/resize b/gcloud/container/clusters/resize index 3a05e730d..9f3a60869 100644 --- a/gcloud/container/clusters/resize +++ b/gcloud/container/clusters/resize @@ -68,10 +68,14 @@ OPTIONAL FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 3d14d4473..3168f21e5 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -84,6 +84,8 @@ SYNOPSIS --enable-autoprovisioning-autoupgrade [--max-accelerator=[type=TYPE,count=COUNT,...] : --min-accelerator=[type=TYPE,count=COUNT,...]]] + | --enable-insecure-binding-system-authenticated + --enable-insecure-binding-system-unauthenticated | --logging=[COMPONENT,...] --monitoring=[COMPONENT,...] --disable-managed-prometheus | --enable-managed-prometheus | --logging-service=LOGGING_SERVICE @@ -1229,6 +1231,23 @@ REQUIRED FLAGS (Required) The minimum number of accelerators to which the cluster can be scaled. + --enable-insecure-binding-system-authenticated + Allow using system:authenticated as a subject in ClusterRoleBindings + and RoleBindings. Allowing bindings that reference + system:authenticated is a security risk and is not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-authenticated flag instead. + + --enable-insecure-binding-system-unauthenticated + Allow using system:unauthenticated and system:anonymous as subjects + in ClusterRoleBindings and RoleBindings. Allowing bindings that + reference system:unauthenticated and system:anonymous are a security + risk and is not recommended. + + To disallow binding system:authenticated in a cluster, explicitly set + the --no-enable-insecure-binding-system-unauthenticated flag instead. + --logging=[COMPONENT,...] Set the components that have logging enabled. Valid component values are: SYSTEM, WORKLOAD, API_SERVER, CONTROLLER_MANAGER, SCHEDULER, @@ -1353,10 +1372,14 @@ OPTIONAL FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/clusters/upgrade b/gcloud/container/clusters/upgrade index 4fa2693e1..b59444ba0 100644 --- a/gcloud/container/clusters/upgrade +++ b/gcloud/container/clusters/upgrade @@ -94,10 +94,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/get-server-config b/gcloud/container/get-server-config index f76068f25..9ce73c17b 100644 --- a/gcloud/container/get-server-config +++ b/gcloud/container/get-server-config @@ -20,10 +20,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/node-pools/complete-upgrade b/gcloud/container/node-pools/complete-upgrade index 2dcbf0fdc..033be5785 100644 --- a/gcloud/container/node-pools/complete-upgrade +++ b/gcloud/container/node-pools/complete-upgrade @@ -32,10 +32,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index cd76c8c34..bc632ca82 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -934,10 +934,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/node-pools/delete b/gcloud/container/node-pools/delete index bc6a537ba..1ee6673c0 100644 --- a/gcloud/container/node-pools/delete +++ b/gcloud/container/node-pools/delete @@ -40,10 +40,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/node-pools/describe b/gcloud/container/node-pools/describe index 1d5c41219..a7fbb7f22 100644 --- a/gcloud/container/node-pools/describe +++ b/gcloud/container/node-pools/describe @@ -30,10 +30,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/node-pools/help b/gcloud/container/node-pools/help index b0397ad9f..d6a55182e 100644 --- a/gcloud/container/node-pools/help +++ b/gcloud/container/node-pools/help @@ -15,10 +15,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/node-pools/list b/gcloud/container/node-pools/list index b8d9bc417..35afbaffa 100644 --- a/gcloud/container/node-pools/list +++ b/gcloud/container/node-pools/list @@ -25,10 +25,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/node-pools/rollback b/gcloud/container/node-pools/rollback index 0457bee8d..45ed7c522 100644 --- a/gcloud/container/node-pools/rollback +++ b/gcloud/container/node-pools/rollback @@ -41,10 +41,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index e2886056e..b58d1fa2d 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -502,10 +502,14 @@ OPTIONAL FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/operations/cancel b/gcloud/container/operations/cancel index 4edaaf2f4..8ad4d2919 100644 --- a/gcloud/container/operations/cancel +++ b/gcloud/container/operations/cancel @@ -31,10 +31,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/operations/describe b/gcloud/container/operations/describe index c69de2afd..09cca86a0 100644 --- a/gcloud/container/operations/describe +++ b/gcloud/container/operations/describe @@ -23,10 +23,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/operations/help b/gcloud/container/operations/help index 5b05839e8..7c9113703 100644 --- a/gcloud/container/operations/help +++ b/gcloud/container/operations/help @@ -15,10 +15,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/operations/list b/gcloud/container/operations/list index cf831fd9b..84d2c8e7d 100644 --- a/gcloud/container/operations/list +++ b/gcloud/container/operations/list @@ -20,10 +20,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/container/operations/wait b/gcloud/container/operations/wait index b4ca4bf34..60ef37853 100644 --- a/gcloud/container/operations/wait +++ b/gcloud/container/operations/wait @@ -23,10 +23,14 @@ FLAGS --location=LOCATION Compute zone or region (e.g. us-central1-a or us-central1) for the - cluster. Prefer using this flag over the --region or --zone flags. + cluster. Overrides the default compute/region or compute/zone value + for this command invocation. Prefer using this flag over the --region + or --zone flags. --region=REGION - Compute region (e.g. us-central1) for a regional cluster. + Compute region (e.g. us-central1) for a regional cluster. Overrides + the default compute/region property value for this command + invocation. --zone=ZONE, -z ZONE Compute zone (e.g. us-central1-a) for a zonal cluster. Overrides the diff --git a/gcloud/database-migration/connection-profiles/create/cloudsql b/gcloud/database-migration/connection-profiles/create/cloudsql index 6405ed6cb..be90e1165 100644 --- a/gcloud/database-migration/connection-profiles/create/cloudsql +++ b/gcloud/database-migration/connection-profiles/create/cloudsql @@ -80,8 +80,8 @@ REQUIRED FLAGS MYSQL_5_7, MYSQL_5_6, MYSQL_8_0, MYSQL_8_0_18, MYSQL_8_0_26, MYSQL_8_0_27, MYSQL_8_0_28, MYSQL_8_0_30, MYSQL_8_0_31, MYSQL_8_0_32, MYSQL_8_0_33, MYSQL_8_0_34, MYSQL_8_0_35, MYSQL_8_0_36, MYSQL_8_0_37, - POSTGRES_9_6, POSTGRES_10, POSTGRES_11, POSTGRES_12, POSTGRES_13, - POSTGRES_14, POSTGRES_15, POSTGRES_16. + MYSQL_8_4, POSTGRES_9_6, POSTGRES_10, POSTGRES_11, POSTGRES_12, + POSTGRES_13, POSTGRES_14, POSTGRES_15, POSTGRES_16. Connection profile resource - Database Migration Service source connection profile ID. This represents a Cloud resource. (NOTE) Some attributes are diff --git a/gcloud/database-migration/migration-jobs/create b/gcloud/database-migration/migration-jobs/create index 465157926..78d079b0b 100644 --- a/gcloud/database-migration/migration-jobs/create +++ b/gcloud/database-migration/migration-jobs/create @@ -14,8 +14,8 @@ SYNOPSIS : --cmek-keyring=CMEK_KEYRING --cmek-project=CMEK_PROJECT] [--peer-vpc=PEER_VPC | --static-ip | [--vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC : --vm=VM]] - [--sqlserver-databases=databaseName,[...] - : --sqlserver-encrypted-databases=SQLSERVER_ENCRYPTED_DATABASES] + [--sqlserver-databases=databaseName,[...] : --sqlserver-diff-backup + --sqlserver-encrypted-databases=SQLSERVER_ENCRYPTED_DATABASES] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -57,16 +57,16 @@ EXAMPLES --region=us-central1 --type=CONTINUOUS --source=cp1 \ --destination=cp2 --conversion-workspace=cw - To create a continuous SQL Server to SQL Server homogeneous migration job: $ gcloud database-migration migration-jobs create my-migration-job \ + To create a continuous SQL Server to SQL Server homogeneous migration job + with differential backup enabled: $ gcloud database-migration migration-jobs create my-migration-job \ --region=us-central1 --type=CONTINUOUS --source=cp1 \ - --destination=cp2 --sqlserver-backup-file-pattern=pattern \ + --destination=cp2 --sqlserver-diff-backup \ --sqlserver-databases=db1,db2,db3 To create a continuous SQL Server to SQL Server homogeneous migration job with encrypted databases: $ gcloud database-migration migration-jobs create my-migration-job \ --region=us-central1 --type=CONTINUOUS --source=cp1 \ - --destination=cp2 --sqlserver-backup-file-pattern=pattern \ - --sqlserver-databases=db1,db2,db3 \ + --destination=cp2 --sqlserver-databases=db1,db2,db3 \ --sqlserver-encrypted-databases=PATH/TO/ENCRYPTION/SETTINGS POSITIONAL ARGUMENTS @@ -303,6 +303,12 @@ OPTIONAL FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + --sqlserver-diff-backup + Enable differential backups. If not specified, differential backups + are disabled by default. Use --sqlserver-diff-backup to enable and + --no-sqlserver-diff-backup to disable. This flag is used only for + homogeneous SQL Server to Cloud SQL for SQL Server migrations. + --sqlserver-encrypted-databases=SQLSERVER_ENCRYPTED_DATABASES A JSON/YAML file describing the encryption settings per database for all encrytped databases. An example of a JSON request: [{ "database": diff --git a/gcloud/database-migration/migration-jobs/update b/gcloud/database-migration/migration-jobs/update index e951e61c1..e889c9edb 100644 --- a/gcloud/database-migration/migration-jobs/update +++ b/gcloud/database-migration/migration-jobs/update @@ -12,7 +12,7 @@ SYNOPSIS [--clear-labels | --remove-labels=[KEY,...]] [--peer-vpc=PEER_VPC | --static-ip | --vm=VM --vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC] - [--sqlserver-databases=databaseName,[...] + [--sqlserver-databases=databaseName,[...] --sqlserver-diff-backup --sqlserver-encrypted-databases=SQLSERVER_ENCRYPTED_DATABASES] [GCLOUD_WIDE_FLAG ...] @@ -214,6 +214,12 @@ FLAGS should contain all encrypted and non-encrypted database names. This flag is used only for SQL Server to Cloud SQL migrations. + --sqlserver-diff-backup + Enable differential backups. If not specified, differential backups + are disabled by default. Use --sqlserver-diff-backup to enable and + --no-sqlserver-diff-backup to disable. This flag is used only for + homogeneous SQL Server to Cloud SQL for SQL Server migrations. + --sqlserver-encrypted-databases=SQLSERVER_ENCRYPTED_DATABASES A JSON/YAML file describing the encryption settings per database for all encrytped databases. An example of a JSON request: [{ "database": diff --git a/gcloud/notebooks/instances/create b/gcloud/notebooks/instances/create index 0b34b35e8..a1ff7d11c 100644 --- a/gcloud/notebooks/instances/create +++ b/gcloud/notebooks/instances/create @@ -164,7 +164,7 @@ FLAGS NVIDIA_TESLA_A100, NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, - TPU_V2, TPU_V3, NVIDIA_L4. + TPU_V2, TPU_V3, NVIDIA_L4, NVIDIA_H100_80GB, NVIDIA_H100_MEGA_80GB. Boot disk configurations. diff --git a/gcloud/notebooks/instances/update b/gcloud/notebooks/instances/update index 972d03dda..e5348d438 100644 --- a/gcloud/notebooks/instances/update +++ b/gcloud/notebooks/instances/update @@ -75,7 +75,7 @@ REQUIRED FLAGS NVIDIA_TESLA_A100, NVIDIA_TESLA_K80, NVIDIA_TESLA_P100, NVIDIA_TESLA_V100, NVIDIA_TESLA_P4, NVIDIA_TESLA_T4, NVIDIA_TESLA_T4_VWS, NVIDIA_TESLA_P100_VWS, NVIDIA_TESLA_P4_VWS, - TPU_V2, TPU_V3, NVIDIA_L4. + TPU_V2, TPU_V3, NVIDIA_L4, NVIDIA_H100_80GB, NVIDIA_H100_MEGA_80GB. --labels=[KEY=VALUE,...] Labels to apply to this instance. These can be later modified by the diff --git a/gcloud/projects/create b/gcloud/projects/create index 1a43683a4..23b41065a 100644 --- a/gcloud/projects/create +++ b/gcloud/projects/create @@ -62,7 +62,7 @@ FLAGS ID for the organization to use as a parent --set-as-default - Set newly created project as [core.project] property. + Set newly created project as [core/project] property. --tags=[KEY=VALUE,...] List of tags KEY=VALUE pairs to bind. Each item must be expressed as diff --git a/gcloud/redis/clusters/create b/gcloud/redis/clusters/create index c983e0275..22ba065fa 100644 --- a/gcloud/redis/clusters/create +++ b/gcloud/redis/clusters/create @@ -5,8 +5,10 @@ NAME SYNOPSIS gcloud redis clusters create (CLUSTER : --region=REGION) --network=NETWORK [--aof-append-fsync=AOF_APPEND_FSYNC] [--async] [--auth-mode=AUTH_MODE] - [--deletion-protection] [--node-type=NODE_TYPE] - [--persistence-mode=PERSISTENCE_MODE] + [--deletion-protection] + [--maintenance-window-day=MAINTENANCE_WINDOW_DAY] + [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] + [--node-type=NODE_TYPE] [--persistence-mode=PERSISTENCE_MODE] [--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD] [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--redis-config=[KEY=VALUE,...]] [--replica-count=REPLICA_COUNT] @@ -116,6 +118,15 @@ OPTIONAL FLAGS Enable deletion protection for the Redis Cluster. Use --deletion-protection/--no-deletion-protection to enable/disable it. + --maintenance-window-day=MAINTENANCE_WINDOW_DAY + 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-hour=MAINTENANCE_WINDOW_HOUR + Hour of day (0 to 23) for the start of maintenance window, in UTC time + zone. + --node-type=NODE_TYPE Node Type of the redis cluster Node. NODE_TYPE must be one of: redis-highmem-medium, redis-highmem-xlarge, redis-shared-core-nano, diff --git a/gcloud/redis/clusters/help b/gcloud/redis/clusters/help index 9f9888d6f..ed0bb6c42 100644 --- a/gcloud/redis/clusters/help +++ b/gcloud/redis/clusters/help @@ -37,6 +37,10 @@ COMMANDS list List Memorystore for Redis Cluster instances. + reschedule-maintenance + Reschedule maintenance window for a Memorystore for Redis Cluster + instance. + switchover Switchover to a secondary cluster. diff --git a/gcloud/redis/clusters/reschedule-maintenance b/gcloud/redis/clusters/reschedule-maintenance new file mode 100644 index 000000000..872a66809 --- /dev/null +++ b/gcloud/redis/clusters/reschedule-maintenance @@ -0,0 +1,90 @@ +NAME + gcloud redis clusters reschedule-maintenance - reschedule maintenance + window for a Memorystore for Redis Cluster instance + +SYNOPSIS + gcloud redis clusters reschedule-maintenance (CLUSTER : --region=REGION) + --reschedule-type=RESCHEDULE_TYPE [--async] + [--schedule-time=SCHEDULE_TIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Reschedule maintenance window for a Memorystore for Redis Cluster instance. + +EXAMPLES + To reschedule maintenance window for an instance with the name + 'my-redis-cluster' in region 'us-central-1' with immediate, run: + + $ gcloud redis clusters reschedule-maintenance my-redis-cluster \ + --region=us-central1 --reschedule-type=IMMEDIATE + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Cloud Memorystore + for Redis cluster 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/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. + 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 redis/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + These variants are also available: + + $ gcloud alpha redis clusters reschedule-maintenance + + $ gcloud beta redis clusters reschedule-maintenance + diff --git a/gcloud/redis/clusters/update b/gcloud/redis/clusters/update index c7ccccd80..a44b84be3 100644 --- a/gcloud/redis/clusters/update +++ b/gcloud/redis/clusters/update @@ -10,6 +10,9 @@ SYNOPSIS [--rdb-snapshot-start-time=RDB_SNAPSHOT_START_TIME] [--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT] [--shard-count=SHARD_COUNT] [--update-redis-config=KEY=VALUE] + [--maintenance-window-any + | --maintenance-window-day=MAINTENANCE_WINDOW_DAY + --maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -123,6 +126,20 @@ FLAGS parameter is already set, its value is modified; otherwise a new Redis config parameter is added. + 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-hour=MAINTENANCE_WINDOW_HOUR + Hour of day (0 to 23) for the start of maintenance window, in UTC + time zone. + 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/run/deploy b/gcloud/run/deploy index ecab887ae..59687c2ff 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -9,11 +9,12 @@ SYNOPSIS [--platform=PLATFORM; default="managed"] [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] - [--args=[ARG,...] --command=[COMMAND,...] --cpu=CPU - --depends-on=[CONTAINER,...] - --memory=MEMORY --port=PORT --[no-]use-http2 --clear-env-vars - | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] - | --remove-env-vars=[KEY,...] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] + --cpu=CPU --depends-on=[CONTAINER,...] --memory=MEMORY --port=PORT + --remove-volume-mount=[MOUNT_PATH,...] + --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...] --image=IMAGE | --source=SOURCE] @@ -37,7 +38,8 @@ SYNOPSIS | --clear-custom-audiences | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --binary-authorization=POLICY + --add-volume=[KEY=VALUE,...] --clear-volumes + --remove-volume=[VOLUME,...] --binary-authorization=POLICY | --clear-binary-authorization --clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS --clear-key | --key=KEY --clear-network @@ -192,6 +194,12 @@ FLAGS The following flags apply to a single container. If the --container flag is specified these flags may only be specified after a --container flag. Otherwise they will apply to the primary ingress container. + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume + on this resource and PATH is the path within the container's + filesystem to mount this volume. + --args=[ARG,...] Comma-separated arguments passed to the command run by the container image. If not specified and no '--command' is provided, @@ -199,6 +207,9 @@ FLAGS specified, no arguments are passed. To reset this field to its default, pass an empty string. + --clear-volume-mounts + Remove all existing mounts from the current container. + --command=[COMMAND,...] Entrypoint for the container image. If not specified, the container image's default Entrypoint is run. To reset this field to its @@ -228,6 +239,10 @@ FLAGS to the previous container port, this will also update the probe port. + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + --[no-]use-http2 Whether to use HTTP/2 for connections to the service. Use --use-http2 to enable and --no-use-http2 to disable. @@ -509,6 +524,35 @@ FLAGS Completely replace the current custom audiences with the given values. + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + At most one of these can be specified: --binary-authorization=POLICY diff --git a/gcloud/run/jobs/create b/gcloud/run/jobs/create index 0f2731a24..879806aa6 100644 --- a/gcloud/run/jobs/create +++ b/gcloud/run/jobs/create @@ -12,6 +12,10 @@ SYNOPSIS [--set-secrets=[KEY=SECRET_NAME:SECRET_VERSION,...]] [--task-timeout=TASK_TIMEOUT] [--tasks=TASKS; default=1] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --clear-volume-mounts --remove-volume-mount=[MOUNT_PATH,...]] [--async | --execute-now --wait] [--env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...]] [--network=NETWORK --network-tags=[TAG,...] --subnet=SUBNET] @@ -164,6 +168,48 @@ OPTIONAL FLAGS https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services for more information. + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume on + this resource and PATH is the path within the container's filesystem to + mount this volume. + + --clear-volume-mounts + Remove all existing mounts from the current container. + + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + At most one of these can be specified: --async diff --git a/gcloud/run/jobs/deploy b/gcloud/run/jobs/deploy index c368b7e19..7021d20c7 100644 --- a/gcloud/run/jobs/deploy +++ b/gcloud/run/jobs/deploy @@ -12,6 +12,10 @@ SYNOPSIS [--set-secrets=[KEY=SECRET_NAME:SECRET_VERSION,...]] [--task-timeout=TASK_TIMEOUT] [--tasks=TASKS; default=1] [--vpc-connector=VPC_CONNECTOR] [--vpc-egress=VPC_EGRESS] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --clear-volume-mounts --remove-volume-mount=[MOUNT_PATH,...]] [--async | --execute-now --wait] [--clear-env-vars | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] @@ -163,6 +167,48 @@ FLAGS https://cloud.google.com/run/docs/securing/private-networking#send_requests_to_other_services_and_services for more information. + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume on + this resource and PATH is the path within the container's filesystem to + mount this volume. + + --clear-volume-mounts + Remove all existing mounts from the current container. + + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + At most one of these can be specified: --async diff --git a/gcloud/run/jobs/update b/gcloud/run/jobs/update index 389960a6c..3f3010e3c 100644 --- a/gcloud/run/jobs/update +++ b/gcloud/run/jobs/update @@ -14,6 +14,10 @@ SYNOPSIS | --clear-cloudsql-instances | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] + [--add-volume=[KEY=VALUE,...] + --clear-volumes --remove-volume=[VOLUME,...]] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --clear-volume-mounts --remove-volume-mount=[MOUNT_PATH,...]] [--async | --execute-now --wait] [--binary-authorization=POLICY | --clear-binary-authorization] [--clear-env-vars | --env-vars-file=FILE_PATH @@ -173,6 +177,48 @@ FLAGS Completely replace the current Cloud SQL instances with the given values. + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume on + this resource and PATH is the path within the container's filesystem to + mount this volume. + + --clear-volume-mounts + Remove all existing mounts from the current container. + + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + At most one of these can be specified: --async diff --git a/gcloud/run/services/update b/gcloud/run/services/update index 0f5f83195..70ab3b888 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -10,11 +10,12 @@ SYNOPSIS [--platform=PLATFORM; default="managed"] [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] - [--args=[ARG,...] --command=[COMMAND,...] --cpu=CPU - --depends-on=[CONTAINER,...] --image=IMAGE - --memory=MEMORY --port=PORT --[no-]use-http2 --clear-env-vars - | --env-vars-file=FILE_PATH | --set-env-vars=[KEY=VALUE,...] - | --remove-env-vars=[KEY,...] + [--add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + --args=[ARG,...] --clear-volume-mounts --command=[COMMAND,...] + --cpu=CPU --depends-on=[CONTAINER,...] --image=IMAGE --memory=MEMORY + --port=PORT --remove-volume-mount=[MOUNT_PATH,...] + --[no-]use-http2 --clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...] --clear-secrets | --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...] --update-secrets=[KEY=VALUE,...]] @@ -31,7 +32,8 @@ SYNOPSIS | --clear-custom-audiences | --remove-custom-audiences=[CUSTOM-AUDIENCES,...] | --set-custom-audiences=[CUSTOM-AUDIENCES,...] - --binary-authorization=POLICY + --add-volume=[KEY=VALUE,...] --clear-volumes + --remove-volume=[VOLUME,...] --binary-authorization=POLICY | --clear-binary-authorization --clear-encryption-key-shutdown-hours | --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS --clear-key | --key=KEY --clear-network @@ -181,6 +183,12 @@ FLAGS If the --container or --remove-containers flag is specified the following arguments may only be specified after a --container flag. + --add-volume-mount=[volume=NAME,mount-path=MOUNT_PATH,...] + Adds a mount to the current container. Must contain the keys + volume=NAME and mount-path=/PATH where NAME is the name of a volume + on this resource and PATH is the path within the container's + filesystem to mount this volume. + --args=[ARG,...] Comma-separated arguments passed to the command run by the container image. If not specified and no '--command' is provided, @@ -188,6 +196,9 @@ FLAGS specified, no arguments are passed. To reset this field to its default, pass an empty string. + --clear-volume-mounts + Remove all existing mounts from the current container. + --command=[COMMAND,...] Entrypoint for the container image. If not specified, the container image's default Entrypoint is run. To reset this field to its @@ -221,6 +232,10 @@ FLAGS to the previous container port, this will also update the probe port. + --remove-volume-mount=[MOUNT_PATH,...] + Removes the volume mounted at the specified path from the current + container. + --[no-]use-http2 Whether to use HTTP/2 for connections to the service. Use --use-http2 to enable and --no-use-http2 to disable. @@ -391,6 +406,35 @@ FLAGS Completely replace the current custom audiences with the given values. + --add-volume=[KEY=VALUE,...] + Adds a volume to the Cloud Run resource. To add more than one volume, + specify this flag multiple times. Volumes must have a name and type + key. Only certain values are supported for type. Depending on the + provided type, other keys will be required. The following types are + supported with the specified additional keys: + + cloud-storage: A volume representing a Cloud Storage bucket. This + volume type is mounted using Cloud Storage FUSE. See + https://cloud.google.com/storage/docs/gcs-fuse for the details and + limitations of this filesystem. Additional keys: + ◆ bucket: (required) the name of the bucket to use as the source of + this volume + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + nfs: Represents a volume backed by an NFS server. Additional keys: + ◆ location: (required) The location of the NFS Server, in the form + SERVER:/PATH + ◆ readonly: (optional) A boolean. If true, this volume will be + read-only from all mounts. + + --clear-volumes + Remove all existing volumes from the Cloud Run resource, including + volumes mounted as secrets + + --remove-volume=[VOLUME,...] + Removes volumes from the Cloud Run resource. + At most one of these can be specified: --binary-authorization=POLICY diff --git a/gcloud/workbench/instances/help b/gcloud/workbench/instances/help index 3d9358ee4..cad7d024d 100644 --- a/gcloud/workbench/instances/help +++ b/gcloud/workbench/instances/help @@ -51,6 +51,9 @@ COMMANDS resize-disk Resizes the workbench instance's disk. + restore + Restores the workbench instance to a snapshot state. + rollback Rolls back a workbench instance. diff --git a/gcloud/workbench/instances/restore b/gcloud/workbench/instances/restore new file mode 100644 index 000000000..903265085 --- /dev/null +++ b/gcloud/workbench/instances/restore @@ -0,0 +1,84 @@ +NAME + gcloud workbench instances restore - restores the workbench instance to a + snapshot state + +SYNOPSIS + gcloud workbench instances restore (INSTANCE : --location=LOCATION) + (--snapshot=SNAPSHOT --snapshot-project=SNAPSHOT_PROJECT) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Restores the workbench instance to a snapshot state. + +EXAMPLES + For valid configurations, run: + + $ gcloud workbench instances restore example-instance \ + --snapshot-project=example-project --snapshot=example-snapshot \ + --location=us-west1-a + +POSITIONAL ARGUMENTS + Instance resource - User-defined unique name of this instance. The + instance name must be 1 to 63 characters long and contain only lowercase + letters, numeric characters, and dashes. The first character must be a + lowercase letter and the last character cannot be a dash. 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 argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location of this environment + https://cloud.google.com/compute/docs/regions-zones/#locations. + + 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; + ▸ set the property notebooks/location. + +REQUIRED FLAGS + Snapshot source to be restored from + + This must be specified. + + --snapshot=SNAPSHOT + The snapshot name to be restored from. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --snapshot-project=SNAPSHOT_PROJECT + The project id of the snapshot to be restored from. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +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.