diff --git a/gcloud/_version b/gcloud/_version index 44ae904c1..0c7bb9ec2 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 545.0.0 -alpha 2025.10.24 -beta 2025.10.24 +Google Cloud SDK 547.0.0 +alpha 2025.11.07 +beta 2025.11.07 bq 2.1.25 -bundled-python3-unix 3.12.9 -core 2025.10.24 +bundled-python3-unix 3.13.7 +core 2025.11.07 gcloud-crc32c 1.0.0 gsutil 5.35 diff --git a/gcloud/alpha/ai/endpoints/deploy-model b/gcloud/alpha/ai/endpoints/deploy-model index 05f37685d..6342dfd35 100644 --- a/gcloud/alpha/ai/endpoints/deploy-model +++ b/gcloud/alpha/ai/endpoints/deploy-model @@ -8,9 +8,12 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--autoscaling-metric-specs=[METRIC-NAME=TARGET,...]] [--deployed-model-id=DEPLOYED_MODEL_ID] [--enable-access-logging] - [--enable-container-logging] [--machine-type=MACHINE_TYPE] - [--max-replica-count=MAX_REPLICA_COUNT] + [--enable-container-logging] + [--idle-scaledown-period=IDLE_SCALEDOWN_PERIOD] + [--initial-replica-count=INITIAL_REPLICA_COUNT] + [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] + [--min-scaleup-period=MIN_SCALEUP_PERIOD] [--multihost-gpu-node-count=MULTIHOST_GPU_NODE_COUNT] [--required-replica-count=REQUIRED_REPLICA_COUNT] [--reservation-affinity=[key=KEY], @@ -125,6 +128,15 @@ OPTIONAL FLAGS Currently, only supported for custom-trained Models and AutoML Tabular Models. + --idle-scaledown-period=IDLE_SCALEDOWN_PERIOD + Duration (in seconds) without traffic before a deployment is scaled + down to zero replicas. Defaults to 1 hour if min replica count is 0. + + --initial-replica-count=INITIAL_REPLICA_COUNT + Initial number of replicas for the deployment resources the model will + be scaled up to. Cannot be smaller than min replica count or larger + than max replica count. + --machine-type=MACHINE_TYPE The machine resources to be used for each node of this deployment. For available machine types, see @@ -144,6 +156,11 @@ OPTIONAL FLAGS NOTE: DeploymentResourcePools (model-cohosting) is currently not supported for scale-to-zero deployments. + --min-scaleup-period=MIN_SCALEUP_PERIOD + Minimum duration (in seconds) that a deployment will be scaled up + before traffic is evaluated for potential scale-down. Defaults to 1 + hour if min replica count is 0. + --multihost-gpu-node-count=MULTIHOST_GPU_NODE_COUNT The number of nodes per replica for multihost GPU deployments. Required for multihost GPU deployments. diff --git a/gcloud/alpha/backup-dr/backups/fetch-for-resource-type b/gcloud/alpha/backup-dr/backups/fetch-for-resource-type new file mode 100644 index 000000000..40e9416e4 --- /dev/null +++ b/gcloud/alpha/backup-dr/backups/fetch-for-resource-type @@ -0,0 +1,118 @@ +NAME + gcloud alpha backup-dr backups fetch-for-resource-type - fetch Backups for + a given resource type and location + +SYNOPSIS + gcloud alpha backup-dr backups fetch-for-resource-type RESOURCE_TYPE + (--data-source=DATA_SOURCE + : --backup-vault=BACKUP_VAULT --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Fetch Backups for a given resource type and location. List backups + for the specified resource type for a data source. + +EXAMPLES + To list backups for Cloud SQL instance resources for data source + my-data-source with location us-central1 under backup vault, my-vault. + + $ gcloud alpha backup-dr backups fetch-for-resource-type \ + sqladmin.googleapis.com/Instance --data-source=my-data-source \ + --backup-vault=my-vault --location=us-central1 + +POSITIONAL ARGUMENTS + RESOURCE_TYPE + Resource type for which backup plan associations should be fetched. + +REQUIRED FLAGS + Data Source resource - Data source for which backups should be fetched. + 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=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 flag 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 + The location of the Data Source. + + 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. + +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. + +BRIEF + List backups in a specified location and resource type in a project. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud backup-dr backups fetch-for-resource-type + diff --git a/gcloud/alpha/backup-dr/backups/help b/gcloud/alpha/backup-dr/backups/help index 8bdaed742..4e0981cf3 100644 --- a/gcloud/alpha/backup-dr/backups/help +++ b/gcloud/alpha/backup-dr/backups/help @@ -27,6 +27,9 @@ COMMANDS describe (ALPHA) Show details of the backup. + fetch-for-resource-type + (ALPHA) Fetch Backups for a given resource type and location. + list (ALPHA) List Backups. diff --git a/gcloud/alpha/backup-dr/data-source-references/help b/gcloud/alpha/backup-dr/data-source-references/help index 01bada706..7336856c8 100644 --- a/gcloud/alpha/backup-dr/data-source-references/help +++ b/gcloud/alpha/backup-dr/data-source-references/help @@ -24,6 +24,9 @@ COMMANDS (ALPHA) Fetch Data Source References for a given resource type and location. + list + (ALPHA) List Backup and DR data source references. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/backup-dr/data-source-references/list b/gcloud/alpha/backup-dr/data-source-references/list new file mode 100644 index 000000000..9e3dabdcc --- /dev/null +++ b/gcloud/alpha/backup-dr/data-source-references/list @@ -0,0 +1,93 @@ +NAME + gcloud alpha backup-dr data-source-references list - list Backup and DR + data source references + +SYNOPSIS + gcloud alpha backup-dr data-source-references list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List Backup and DR data source references. + +EXAMPLES + To list data source references in all locations, run: + + $ gcloud alpha backup-dr data-source-references list + + To list data source references in a location 'my-location', run: + + $ gcloud alpha backup-dr data-source-references list \ + --location=my-location + +FLAGS + Location resource - Location for which data source references 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. This variant is also available: + + $ gcloud backup-dr data-source-references list + diff --git a/gcloud/alpha/biglake/iceberg/help b/gcloud/alpha/biglake/iceberg/help index ca2290ba1..b8e0192c1 100644 --- a/gcloud/alpha/biglake/iceberg/help +++ b/gcloud/alpha/biglake/iceberg/help @@ -21,9 +21,6 @@ GROUPS namespaces (ALPHA) Manage BigLake Iceberg REST catalog namespaces. - tables - (ALPHA) Manage BigLake Iceberg REST catalog tables. - NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/biglake/iceberg/tables/set-iam-policy b/gcloud/alpha/biglake/iceberg/tables/set-iam-policy deleted file mode 100644 index f53eb98fe..000000000 --- a/gcloud/alpha/biglake/iceberg/tables/set-iam-policy +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud alpha biglake iceberg tables set-iam-policy - set the IAM policy for - a BigLake Iceberg REST catalog table - -SYNOPSIS - gcloud alpha biglake iceberg tables set-iam-policy - (TABLE : --catalog=CATALOG --namespace=NAMESPACE) POLICY_FILE - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Sets the IAM policy for a BigLake Iceberg REST catalog table. - -EXAMPLES - To set the IAM policy for the catalog my-catalog, namespace my-namespace, - and table my-table with the policy in policy.json run: - - $ gcloud alpha biglake iceberg tables set-iam-policy my-table \ - policy.json --catalog=my-catalog --namespace=my-namespace - -POSITIONAL ARGUMENTS - Table resource - The Iceberg Table to set the IAM policy for. The - arguments in this group can be used to specify the attributes of this - resource. (NOTE) Some attributes are not given arguments in this group but - can be set in other ways. - - To set the project attribute: - ◆ provide the argument table 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. - - TABLE - ID of the table or fully qualified identifier for the table. - - To set the table attribute: - ▸ provide the argument table on the command line. - - This positional argument must be specified if any of the other - arguments in this group are specified. - - --catalog=CATALOG - The Iceberg Catalog for the resource. - - To set the catalog attribute: - ▸ provide the argument table on the command line with a fully - specified name; - ▸ provide the argument --catalog on the command line. - - --namespace=NAMESPACE - The Iceberg Namespace for the resource. - - To set the namespace attribute: - ▸ provide the argument table on the command line with a fully - specified name; - ▸ provide the argument --namespace 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 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/bigtable/help b/gcloud/alpha/bigtable/help index 16c3151c9..ff0e21097 100644 --- a/gcloud/alpha/bigtable/help +++ b/gcloud/alpha/bigtable/help @@ -42,6 +42,9 @@ GROUPS operations (ALPHA) Manage Cloud Bigtable operations. + schema-bundles + (ALPHA) Manage Bigtable schema bundles. + tables (ALPHA) Query Cloud Bigtable tables. diff --git a/gcloud/alpha/bigtable/schema-bundles/add-iam-policy-binding b/gcloud/alpha/bigtable/schema-bundles/add-iam-policy-binding new file mode 100644 index 000000000..3a7ed1dc1 --- /dev/null +++ b/gcloud/alpha/bigtable/schema-bundles/add-iam-policy-binding @@ -0,0 +1,162 @@ +NAME + gcloud alpha bigtable schema-bundles add-iam-policy-binding - add an IAM + policy binding to a Bigtable schema bundle + +SYNOPSIS + gcloud alpha bigtable schema-bundles add-iam-policy-binding + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) --member=PRINCIPAL + --role=ROLE + [--condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Add an IAM policy binding to a Bigtable schema bundle. One binding + consists of a member, a role, and an optional condition. + +EXAMPLES + To add an IAM policy binding for the role of roles/editor for the user + 222larabrown@gmail.com with schema bundle my-schema-bundle in instance + my-instance and table my-table, run: + + $ gcloud alpha bigtable schema-bundles add-iam-policy-binding \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + --member=`user:222larabrown@gmail.com` --role=`roles/editor` + + To add an IAM policy binding which expires at the end of the year 2025 for + the role of roles/bigtable.admin and the user 222larabrown@gmail.com with + schema bundle my-schema-bundle in instance my-instance and table my-table, + run: + + $ gcloud alpha bigtable schema-bundles add-iam-policy-binding \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + --member=`user:222larabrown@gmail.com` \ + --role=`roles/bigtable.admin` \ + --condition=`expression=request.time < \ + timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,\ + description=Expires at midnight on 2020-12-31` + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to add the IAM policy + binding to. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=PATH_TO_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. Use a full or + relative path to a local file containing the value of condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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 bigtable schema-bundles add-iam-policy-binding + + $ gcloud beta bigtable schema-bundles add-iam-policy-binding + diff --git a/gcloud/alpha/bigtable/schema-bundles/create b/gcloud/alpha/bigtable/schema-bundles/create new file mode 100644 index 000000000..e4b7c2ca6 --- /dev/null +++ b/gcloud/alpha/bigtable/schema-bundles/create @@ -0,0 +1,102 @@ +NAME + gcloud alpha bigtable schema-bundles create - create a new Bigtable schema + bundle + +SYNOPSIS + gcloud alpha bigtable schema-bundles create + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + --proto-descriptors-file=PROTO_DESCRIPTORS_FILE [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new Bigtable schema bundle. + +EXAMPLES + To create a schema bundle my-schema-bundle in instance my-instance and + table my-table, using the descriptor file my-descriptor-file.pb: + + $ gcloud alpha bigtable schema-bundles create my-schema-bundle \ + --instance=test-instance --table=test-table \ + --proto-descriptors-file=my-descriptor-file.pb + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to create. The arguments + in this group can be used to specify the attributes of this resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +REQUIRED FLAGS + --proto-descriptors-file=PROTO_DESCRIPTORS_FILE + Path of a file that contains a protobuf-serialized + google.protobuf.FileDescriptorSet message. If specified, the schema + bundle contains the protobuf schema. To generate the file, install and + run protoc with the following command: + + protoc --proto_path=IMPORT_PATH --include_imports --descriptor_set_out=DESCRIPTOR_OUTPUT_LOCATION path/to/file.proto + + where the --proto_path option specificies where to look for .proto + files when resolving import directives (the current directory is used + if you do not provide a value), and the --descriptor_set_out option + specifies where you want the generated FileDescriptorSet to be written. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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 bigtable schema-bundles create + + $ gcloud beta bigtable schema-bundles create + diff --git a/gcloud/alpha/bigtable/schema-bundles/delete b/gcloud/alpha/bigtable/schema-bundles/delete new file mode 100644 index 000000000..a9d708ed6 --- /dev/null +++ b/gcloud/alpha/bigtable/schema-bundles/delete @@ -0,0 +1,81 @@ +NAME + gcloud alpha bigtable schema-bundles delete - delete a Bigtable schema + bundle + +SYNOPSIS + gcloud alpha bigtable schema-bundles delete + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Bigtable schema bundle. + +EXAMPLES + To delete the schema bundle my-schema-bundle in instance my-instance and + table my-table: + + $ gcloud alpha bigtable schema-bundles delete my-schema-bundle \ + --instance=test-instance --table=test-table + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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 bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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 bigtable schema-bundles delete + + $ gcloud beta bigtable schema-bundles delete + diff --git a/gcloud/alpha/bigtable/schema-bundles/describe b/gcloud/alpha/bigtable/schema-bundles/describe new file mode 100644 index 000000000..5ce34dfbd --- /dev/null +++ b/gcloud/alpha/bigtable/schema-bundles/describe @@ -0,0 +1,81 @@ +NAME + gcloud alpha bigtable schema-bundles describe - describe a Bigtable schema + bundle + +SYNOPSIS + gcloud alpha bigtable schema-bundles describe + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Bigtable schema bundle. + +EXAMPLES + To describe the schema bundle my-schema-bundle in instance my-instance and + table my-table: + + $ gcloud alpha bigtable schema-bundles describe my-schema-bundle \ + --instance=test-instance --table=test-table + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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 bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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 bigtable schema-bundles describe + + $ gcloud beta bigtable schema-bundles describe + diff --git a/gcloud/alpha/bigtable/schema-bundles/get-iam-policy b/gcloud/alpha/bigtable/schema-bundles/get-iam-policy new file mode 100644 index 000000000..f02469749 --- /dev/null +++ b/gcloud/alpha/bigtable/schema-bundles/get-iam-policy @@ -0,0 +1,111 @@ +NAME + gcloud alpha bigtable schema-bundles get-iam-policy - get an IAM policy on + a Bigtable schema bundle + +SYNOPSIS + gcloud alpha bigtable schema-bundles get-iam-policy + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get an IAM policy on a Bigtable schema bundle. + +EXAMPLES + To get the IAM policy on the schema bundle my-schema-bundle in instance + my-instance and table my-table, run: + + $ gcloud alpha bigtable schema-bundles get-iam-policy \ + my-schema-bundle --instance=`my-instance` --table=`my-table` + + See https://cloud.google.com/iam/docs/managing-policies for more + information. + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to get the IAM policy for. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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 bigtable schema-bundles get-iam-policy + + $ gcloud beta bigtable schema-bundles get-iam-policy + diff --git a/gcloud/alpha/bigtable/schema-bundles/help b/gcloud/alpha/bigtable/schema-bundles/help new file mode 100644 index 000000000..3e82d20c9 --- /dev/null +++ b/gcloud/alpha/bigtable/schema-bundles/help @@ -0,0 +1,54 @@ +NAME + gcloud alpha bigtable schema-bundles - manage Bigtable schema bundles + +SYNOPSIS + gcloud alpha bigtable schema-bundles COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Bigtable schema bundles. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + (ALPHA) Add an IAM policy binding to a Bigtable schema bundle. + + create + (ALPHA) Create a new Bigtable schema bundle. + + delete + (ALPHA) Delete a Bigtable schema bundle. + + describe + (ALPHA) Describe a Bigtable schema bundle. + + get-iam-policy + (ALPHA) Get an IAM policy on a Bigtable schema bundle. + + list + (ALPHA) List all schema bundles of a Bigtable table. + + remove-iam-policy-binding + (ALPHA) Remove an IAM policy binding from a Bigtable schema bundle. + + set-iam-policy + (ALPHA) Set an IAM policy on a Bigtable schema bundle. + + update + (ALPHA) Update an existing Bigtable schema bundle. + +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 bigtable schema-bundles + + $ gcloud beta bigtable schema-bundles + diff --git a/gcloud/alpha/biglake/iceberg/tables/get-iam-policy b/gcloud/alpha/bigtable/schema-bundles/list similarity index 56% rename from gcloud/alpha/biglake/iceberg/tables/get-iam-policy rename to gcloud/alpha/bigtable/schema-bundles/list index 1020137c9..8e17ccc80 100644 --- a/gcloud/alpha/biglake/iceberg/tables/get-iam-policy +++ b/gcloud/alpha/bigtable/schema-bundles/list @@ -1,61 +1,57 @@ NAME - gcloud alpha biglake iceberg tables get-iam-policy - get the IAM policy for - a BigLake Iceberg REST catalog table + gcloud alpha bigtable schema-bundles list - list all schema bundles of a + Bigtable table SYNOPSIS - gcloud alpha biglake iceberg tables get-iam-policy - (TABLE : --catalog=CATALOG --namespace=NAMESPACE) [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + gcloud alpha bigtable schema-bundles list + (--table=TABLE : --instance=INSTANCE) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Gets the IAM policy for a BigLake Iceberg REST catalog table. + (ALPHA) List all schema bundles of a Bigtable table. EXAMPLES - To get the IAM policy for the catalog my-catalog, namespace my-namespace, - and table my-table run: + To list the schema bundles in instance my-instance and table my-table: - $ gcloud alpha biglake iceberg tables get-iam-policy my-table \ - --catalog=my-catalog --namespace=my-namespace + $ gcloud alpha bigtable schema-bundles list --instance=my-instance \ + --table=my-table -POSITIONAL ARGUMENTS - Table resource - The Iceberg Table to get the IAM policy for. The + To list all schema bundles that match the given filter: + + $ gcloud alpha bigtable schema-bundles list --instance=my-instance \ + --table=my-table --filter="name=( `NAME` ... )" + +REQUIRED FLAGS + Table resource - Bigtable table for which to list all schema bundles. 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 table on the command line with a fully specified - name; + ◆ provide the argument --table 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. - TABLE + --table=TABLE ID of the table or fully qualified identifier for the table. To set the table attribute: - ▸ provide the argument table on the command line. + ▸ provide the argument --table on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. + This flag argument must be specified if any of the other arguments in + this group are specified. - --catalog=CATALOG - The Iceberg Catalog for the resource. + --instance=INSTANCE + Name of the Bigtable instance. - To set the catalog attribute: - ▸ provide the argument table on the command line with a fully + To set the instance attribute: + ▸ provide the argument --table on the command line with a fully specified name; - ▸ provide the argument --catalog on the command line. - - --namespace=NAMESPACE - The Iceberg Namespace for the resource. - - To set the namespace attribute: - ▸ provide the argument table on the command line with a fully - specified name; - ▸ provide the argument --namespace on the command line. + ▸ provide the argument --instance on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -83,6 +79,12 @@ LIST COMMAND FLAGS 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, @@ -91,9 +93,17 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud bigtable schema-bundles list + + $ gcloud beta bigtable schema-bundles list diff --git a/gcloud/alpha/bigtable/schema-bundles/remove-iam-policy-binding b/gcloud/alpha/bigtable/schema-bundles/remove-iam-policy-binding new file mode 100644 index 000000000..2adb037b0 --- /dev/null +++ b/gcloud/alpha/bigtable/schema-bundles/remove-iam-policy-binding @@ -0,0 +1,167 @@ +NAME + gcloud alpha bigtable schema-bundles remove-iam-policy-binding - remove an + IAM policy binding from a Bigtable schema bundle + +SYNOPSIS + gcloud alpha bigtable schema-bundles remove-iam-policy-binding + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) --member=PRINCIPAL + --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=PATH_TO_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Remove an IAM policy binding from a Bigtable schema bundle. One + binding consists of a member, a role, and an optional condition. + +EXAMPLES + To remove an IAM policy binding for the role of roles/editor for the user + 222larabrown@gmail.com with schema bundle my-schema-bundle in instance + my-instance and table my-table, run: + + $ gcloud alpha bigtable schema-bundles remove-iam-policy-binding \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + --member=`user:222larabrown@gmail.com` --role=`roles/editor` + + To remove an IAM policy binding which expires at the end of the year 2025 + for the role of roles/bigtable.admin and the user 222larabrown@gmail.com + with schema bundle my-schema-bundle in instance my-instance and table + my-table, run: + + $ gcloud alpha bigtable schema-bundles remove-iam-policy-binding \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + --member=`user:222larabrown@gmail.com` \ + --role=`roles/bigtable.admin` \ + --condition=`expression=request.time < \ + timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,\ + description=Expires at midnight on 2020-12-31` + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to remove the IAM policy + binding 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=PATH_TO_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. Use a full or + relative path to a local file containing the value of condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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 bigtable schema-bundles remove-iam-policy-binding + + $ gcloud beta bigtable schema-bundles remove-iam-policy-binding + diff --git a/gcloud/alpha/bigtable/schema-bundles/set-iam-policy b/gcloud/alpha/bigtable/schema-bundles/set-iam-policy new file mode 100644 index 000000000..46b39c85a --- /dev/null +++ b/gcloud/alpha/bigtable/schema-bundles/set-iam-policy @@ -0,0 +1,92 @@ +NAME + gcloud alpha bigtable schema-bundles set-iam-policy - set an IAM policy on + a Bigtable schema bundle + +SYNOPSIS + gcloud alpha bigtable schema-bundles set-iam-policy + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Set an IAM policy on a Bigtable schema bundle. + +EXAMPLES + To set the IAM policy from file my-policy on the schema bundle + my-schema-bundle in instance my-instance and table my-table, run: + + $ gcloud alpha bigtable schema-bundles set-iam-policy \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + my-policy + + See https://cloud.google.com/iam/docs/managing-policies for more + information. + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to set the IAM policy on. + 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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 bigtable schema-bundles set-iam-policy + + $ gcloud beta bigtable schema-bundles set-iam-policy + diff --git a/gcloud/alpha/bigtable/schema-bundles/update b/gcloud/alpha/bigtable/schema-bundles/update new file mode 100644 index 000000000..f9ab56edd --- /dev/null +++ b/gcloud/alpha/bigtable/schema-bundles/update @@ -0,0 +1,105 @@ +NAME + gcloud alpha bigtable schema-bundles update - update an existing Bigtable + schema bundle + +SYNOPSIS + gcloud alpha bigtable schema-bundles update + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + --proto-descriptors-file=PROTO_DESCRIPTORS_FILE [--async] + [--ignore-warnings] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an existing Bigtable schema bundle. + +EXAMPLES + To update a schema bundle my-schema-bundle in instance my-instance and + table my-table, using the descriptor file my-descriptor-file.pb: + + $ gcloud alpha bigtable schema-bundles update my-schema-bundle \ + --instance=my-instance --table=my-table \ + --proto-descriptors-file=my-descriptor-file.pb + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +REQUIRED FLAGS + --proto-descriptors-file=PROTO_DESCRIPTORS_FILE + Path of a file that contains a protobuf-serialized + google.protobuf.FileDescriptorSet message. If specified, the schema + bundle contains the protobuf schema. To generate the file, install and + run protoc with the following command: + + protoc --proto_path=IMPORT_PATH --include_imports --descriptor_set_out=DESCRIPTOR_OUTPUT_LOCATION path/to/file.proto + + where the --proto_path option specificies where to look for .proto + files when resolving import directives (the current directory is used + if you do not provide a value), and the --descriptor_set_out option + specifies where you want the generated FileDescriptorSet to be written. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --ignore-warnings + If true, backwards incompatible changes will be allowed. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +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 bigtable schema-bundles update + + $ gcloud beta bigtable schema-bundles update + diff --git a/gcloud/alpha/cluster-director/clusters/create b/gcloud/alpha/cluster-director/clusters/create index 749747d5d..9513bcc90 100644 --- a/gcloud/alpha/cluster-director/clusters/create +++ b/gcloud/alpha/cluster-director/clusters/create @@ -5,9 +5,11 @@ NAME SYNOPSIS gcloud alpha cluster-director clusters create (CLUSTER : --location=LOCATION) - (--config=[computeResources=COMPUTERESOURCES],[description=DESCRIPTION], - [labels=LABELS],[name=NAME],[networkResources=NETWORKRESOURCES], - [orchestrator=ORCHESTRATOR],[storageResources=STORAGERESOURCES] + (--config=[compute=COMPUTE],[computeResources=COMPUTERESOURCES], + [description=DESCRIPTION],[labels=LABELS],[name=NAME], + [networkResources=NETWORKRESOURCES],[networks=NETWORKS], + [orchestrator=ORCHESTRATOR], + [storageResources=STORAGERESOURCES],[storages=STORAGES] | [--slurm-login-node=[count=COUNT],[enableOSLogin=ENABLEOSLOGIN], [enablePublicIPs=ENABLEPUBLICIPS],[labels=LABELS], [machineType=MACHINETYPE],[startupScript=STARTUPSCRIPT],[zone=ZONE] @@ -122,10 +124,61 @@ REQUIRED FLAGS Exactly one of these must be specified: - --config=[computeResources=COMPUTERESOURCES],[description=DESCRIPTION],[labels=LABELS],[name=NAME],[networkResources=NETWORKRESOURCES],[orchestrator=ORCHESTRATOR],[storageResources=STORAGERESOURCES] + --config=[compute=COMPUTE],[computeResources=COMPUTERESOURCES],[description=DESCRIPTION],[labels=LABELS],[name=NAME],[networkResources=NETWORKRESOURCES],[networks=NETWORKS],[orchestrator=ORCHESTRATOR],[storageResources=STORAGERESOURCES],[storages=STORAGES] Configuration of the cluster specs in the form of a JSON object. Sets config value. + compute + Sets compute value. + + resourceRequests + Sets resourceRequests value. + + disks + Sets disks value. + + boot + Required, sets boot value. + + sizeGb + Sets sizeGb value. + + sourceImage + Sets sourceImage value. + + type + Required, sets type value. + + id + Sets id value. + + machineType + Sets machineType value. + + maxRunDuration + Sets maxRunDuration value. + + provisioningModel + Sets provisioningModel value. + + reservationAffinity + Sets reservationAffinity value. + + key + Sets key value. + + type + Sets type value. + + values + Sets values value. + + terminationAction + Sets terminationAction value. + + zone + Sets zone value. + computeResources Sets computeResources value. @@ -141,30 +194,108 @@ REQUIRED FLAGS newDwsFlexInstances Sets newDwsFlexInstances value. + atmTags + Sets atmTags value. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + bootDisk + Sets bootDisk value. + + boot + Required, sets boot value. + + sizeGb + Sets sizeGb value. + + sourceImage + Sets sourceImage value. + + type + Required, sets type value. + machineType Sets machineType value. maxDuration Sets maxDuration value. + terminationAction + Sets terminationAction value. + zone Sets zone value. newFlexStartInstances Sets newFlexStartInstances value. + atmTags + Sets atmTags value. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + bootDisk + Sets bootDisk value. + + boot + Required, sets boot value. + + sizeGb + Sets sizeGb value. + + sourceImage + Sets sourceImage value. + + type + Required, sets type value. + machineType Sets machineType value. maxDuration Sets maxDuration value. + terminationAction + Sets terminationAction value. + zone Sets zone value. newOnDemandInstances Sets newOnDemandInstances value. + atmTags + Sets atmTags value. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + bootDisk + Sets bootDisk value. + + boot + Required, sets boot value. + + sizeGb + Sets sizeGb value. + + sourceImage + Sets sourceImage value. + + type + Required, sets type value. + machineType Sets machineType value. @@ -174,12 +305,42 @@ REQUIRED FLAGS newReservedInstances Sets newReservedInstances value. + atmTags + Sets atmTags value. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + bootDisk + Sets bootDisk value. + + boot + Required, sets boot value. + + sizeGb + Sets sizeGb value. + + sourceImage + Sets sourceImage value. + + type + Required, sets type value. + machineType Sets machineType value. reservation Sets reservation value. + reservationBlock + Sets reservationBlock value. + + reservationSubBlock + Sets reservationSubBlock value. + type Sets type value. @@ -189,9 +350,36 @@ REQUIRED FLAGS newSpotInstances Sets newSpotInstances value. + atmTags + Sets atmTags value. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + bootDisk + Sets bootDisk value. + + boot + Required, sets boot value. + + sizeGb + Sets sizeGb value. + + sourceImage + Sets sourceImage value. + + type + Required, sets type value. + machineType Sets machineType value. + terminationAction + Sets terminationAction value. + zone Sets zone value. @@ -222,6 +410,15 @@ REQUIRED FLAGS config Sets config value. + existingComputeNetwork + Sets existingComputeNetwork value. + + network + Sets network value. + + subnetwork + Sets subnetwork value. + existingNetwork Sets existingNetwork value. @@ -231,6 +428,15 @@ REQUIRED FLAGS subnetwork Sets subnetwork value. + newComputeNetwork + Sets newComputeNetwork value. + + description + Sets description value. + + network + Sets network value. + newNetwork Sets newNetwork value. @@ -240,18 +446,105 @@ REQUIRED FLAGS network Sets network value. + networks + Sets networks value. + + initializeParams + Sets initializeParams value. + + description + Sets description value. + + network + Sets network value. + + networkSource + Sets networkSource value. + + network + Sets network value. + + subnetwork + Sets subnetwork value. + orchestrator Sets orchestrator value. slurm Sets slurm value. + config + Sets config value. + + accountingStorageEnforceFlags + Sets accountingStorageEnforceFlags value. + + preemptExemptTime + Sets preemptExemptTime value. + + preemptMode + Sets preemptMode value. + + preemptType + Sets preemptType value. + + priorityType + Sets priorityType value. + + priorityWeightAge + Sets priorityWeightAge value. + + priorityWeightAssoc + Sets priorityWeightAssoc value. + + priorityWeightFairshare + Sets priorityWeightFairshare value. + + priorityWeightJobSize + Sets priorityWeightJobSize value. + + priorityWeightPartition + Sets priorityWeightPartition value. + + priorityWeightQos + Sets priorityWeightQos value. + + priorityWeightTres + Sets priorityWeightTres value. + + prologEpilogTimeout + Sets prologEpilogTimeout value. + + prologFlags + Sets prologFlags value. + + requeueExitCodes + Sets requeueExitCodes value. + + requeueHoldExitCodes + Sets requeueHoldExitCodes value. + defaultPartition Sets defaultPartition value. + epilogBashScripts + Sets epilogBashScripts value. + loginNodes Sets loginNodes value. + bootDisk + Sets bootDisk value. + + image + Sets image value. + + sizeGb + Required, sets sizeGb value. + + type + Required, sets type value. + count Sets count value. @@ -288,6 +581,15 @@ REQUIRED FLAGS machineType Sets machineType value. + serviceAccount + Sets serviceAccount value. + + email + Sets email value. + + scopes + Sets scopes value. + startupScript Sets startupScript value. @@ -321,6 +623,48 @@ REQUIRED FLAGS type Required, sets type value. + canIpForward + Sets canIpForward value. + + computeId + Sets computeId value. + + computeInstance + Sets computeInstance value. + + bootDisk + Sets bootDisk value. + + image + Sets image value. + + sizeGb + Required, sets sizeGb value. + + type + Required, sets type value. + + labels + Sets labels value. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + startupScript + Sets startupScript value. + + containerNodePool + Sets containerNodePool value. + + enableOsLogin + Sets enableOsLogin value. + + enablePublicIps + Sets enablePublicIps value. + id Sets id value. @@ -339,6 +683,15 @@ REQUIRED FLAGS resourceRequestId Sets resourceRequestId value. + serviceAccount + Sets serviceAccount value. + + email + Sets email value. + + scopes + Sets scopes value. + startupScript Sets startupScript value. @@ -366,6 +719,15 @@ REQUIRED FLAGS nodeSetIds Sets nodeSetIds value. + prologBashScripts + Sets prologBashScripts value. + + taskEpilogBashScripts + Sets taskEpilogBashScripts value. + + taskPrologBashScripts + Sets taskPrologBashScripts value. + storageResources Sets storageResources value. @@ -405,6 +767,9 @@ REQUIRED FLAGS enabled Sets enabled value. + terminalStorageClass + Sets terminalStorageClass value. + bucket Sets bucket value. @@ -456,13 +821,100 @@ REQUIRED FLAGS lustre Sets lustre value. + perUnitStorageThroughput + Sets perUnitStorageThroughput value. + + storages + Sets storages value. + + id + Sets id value. + + initializeParams + Sets initializeParams value. + + filestore + Sets filestore value. + + description + Sets description value. + + fileShares + Sets fileShares value. + + capacityGb + Sets capacityGb value. + + fileShare + Sets fileShare value. + + filestore + Sets filestore value. + + protocol + Sets protocol value. + + tier + Sets tier value. + + gcs + Sets gcs value. + + autoclass + Sets autoclass value. + + enabled + Sets enabled value. + + terminalStorageClass + Sets terminalStorageClass value. + + bucket + Sets bucket value. + + hierarchicalNamespace + Sets hierarchicalNamespace value. + + enabled + Sets enabled value. + + storageClass + Sets storageClass value. + + lustre + Sets lustre value. + + capacityGb + Sets capacityGb value. + + description + Sets description value. + + filesystem + Sets filesystem value. + + lustre + Sets lustre value. + + storageSource + Sets storageSource value. + + bucket + Sets bucket value. + + filestore + Sets filestore value. + + lustre + Sets lustre value. + Shorthand Example: - --config=computeResources={string={config={newDwsFlexInstances={machineType=string,maxDuration=string,zone=string},newFlexStartInstances={machineType=string,maxDuration=string,zone=string},newOnDemandInstances={machineType=string,zone=string},newReservedInstances={machineType=string,reservation=string,type=string,zone=string},newSpotInstances={machineType=string,zone=string}}}},description=string,labels={string=string},name=string,networkResources={string={config={existingNetwork={network=string,subnetwork=string},newNetwork={description=string,network=string}}}},orchestrator={slurm={defaultPartition=string,loginNodes={count=int,disks=[{boot=boolean,sizeGb=int,sourceImage=string,type=string}],enableOsLogin=boolean,enablePublicIps=boolean,labels={string=string},machineType=string,startupScript=string,storageConfigs=[{id=string,localMount=string}],zone=string},nodeSets=[{bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},id=string,labels={string=string},maxDynamicNodeCount=int,resourceRequestId=string,startupScript=string,staticNodeCount=int,storageConfigs=[{id=string,localMount=string}]}],partitions=[{exclusive=boolean,id=string,nodeSetIds=[string]}]}},storageResources={string={config={existingBucket={bucket=string},existingFilestore={filestore=string},existingLustre={lustre=string},newBucket={autoclass={enabled=boolean},bucket=string,hierarchicalNamespace={enabled=boolean},storageClass=string},newFilestore={description=string,fileShares=[{capacityGb=int,fileShare=string}],filestore=string,protocol=string,tier=string},newLustre={capacityGb=int,description=string,filesystem=string,lustre=string}}}} + --config=compute={resourceRequests=[{disks=[{boot=boolean,sizeGb=int,sourceImage=string,type=string}],id=string,machineType=string,maxRunDuration=int,provisioningModel=string,reservationAffinity={key=string,type=string,values},terminationAction=string,zone=string}]},computeResources={string={config={newDwsFlexInstances={atmTags={string=string},bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},machineType=string,maxDuration=string,terminationAction=string,zone=string},newFlexStartInstances={atmTags={string=string},bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},machineType=string,maxDuration=string,terminationAction=string,zone=string},newOnDemandInstances={atmTags={string=string},bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},machineType=string,zone=string},newReservedInstances={atmTags={string=string},bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},machineType=string,reservation=string,reservationBlock=string,reservationSubBlock=string,type=string,zone=string},newSpotInstances={atmTags={string=string},bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},machineType=string,terminationAction=string,zone=string}}}},description=string,labels={string=string},name=string,networkResources={string={config={existingComputeNetwork={network=string,subnetwork=string},existingNetwork={network=string,subnetwork=string},newComputeNetwork={description=string,network=string},newNetwork={description=string,network=string}}}},networks=[{initializeParams={description=string,network=string},networkSource={network=string,subnetwork=string}}],orchestrator={slurm={config={accountingStorageEnforceFlags,preemptExemptTime=string,preemptMode,preemptType=string,priorityType=string,priorityWeightAge=int,priorityWeightAssoc=int,priorityWeightFairshare=int,priorityWeightJobSize=int,priorityWeightPartition=int,priorityWeightQos=int,priorityWeightTres=string,prologEpilogTimeout=string,prologFlags,requeueExitCodes,requeueHoldExitCodes},defaultPartition=string,epilogBashScripts,loginNodes={bootDisk={image=string,sizeGb=int,type=string},count=int,disks=[{boot=boolean,sizeGb=int,sourceImage=string,type=string}],enableOsLogin=boolean,enablePublicIps=boolean,labels={string=string},machineType=string,serviceAccount={email=string,scopes},startupScript=string,storageConfigs=[{id=string,localMount=string}],zone=string},nodeSets=[{bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},canIpForward=boolean,computeId=string,computeInstance={bootDisk={image=string,sizeGb=int,type=string},labels={string=string},startupScript=string},containerNodePool,enableOsLogin=boolean,enablePublicIps=boolean,id=string,labels={string=string},maxDynamicNodeCount=int,resourceRequestId=string,serviceAccount={email=string,scopes},startupScript=string,staticNodeCount=int,storageConfigs=[{id=string,localMount=string}]}],partitions=[{exclusive=boolean,id=string,nodeSetIds=[string]}],prologBashScripts,taskEpilogBashScripts,taskPrologBashScripts}},storageResources={string={config={existingBucket={bucket=string},existingFilestore={filestore=string},existingLustre={lustre=string},newBucket={autoclass={enabled=boolean,terminalStorageClass=string},bucket=string,hierarchicalNamespace={enabled=boolean},storageClass=string},newFilestore={description=string,fileShares=[{capacityGb=int,fileShare=string}],filestore=string,protocol=string,tier=string},newLustre={capacityGb=int,description=string,filesystem=string,lustre=string,perUnitStorageThroughput=int}}}},storages=[{id=string,initializeParams={filestore={description=string,fileShares=[{capacityGb=int,fileShare=string}],filestore=string,protocol=string,tier=string},gcs={autoclass={enabled=boolean,terminalStorageClass=string},bucket=string,hierarchicalNamespace={enabled=boolean},storageClass=string},lustre={capacityGb=int,description=string,filesystem=string,lustre=string}},storageSource={bucket=string,filestore=string,lustre=string}}] JSON Example: - --config='{"computeResources": {"string": {"config": {"newDwsFlexInstances": {"machineType": "string", "maxDuration": "string", "zone": "string"}, "newFlexStartInstances": {"machineType": "string", "maxDuration": "string", "zone": "string"}, "newOnDemandInstances": {"machineType": "string", "zone": "string"}, "newReservedInstances": {"machineType": "string", "reservation": "string", "type": "string", "zone": "string"}, "newSpotInstances": {"machineType": "string", "zone": "string"}}}}, "description": "string", "labels": {"string": "string"}, "name": "string", "networkResources": {"string": {"config": {"existingNetwork": {"network": "string", "subnetwork": "string"}, "newNetwork": {"description": "string", "network": "string"}}}}, "orchestrator": {"slurm": {"defaultPartition": "string", "loginNodes": {"count": int, "disks": [{"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}], "enableOsLogin": boolean, "enablePublicIps": boolean, "labels": {"string": "string"}, "machineType": "string", "startupScript": "string", "storageConfigs": [{"id": "string", "localMount": "string"}], "zone": "string"}, "nodeSets": [{"bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "id": "string", "labels": {"string": "string"}, "maxDynamicNodeCount": int, "resourceRequestId": "string", "startupScript": "string", "staticNodeCount": int, "storageConfigs": [{"id": "string", "localMount": "string"}]}], "partitions": [{"exclusive": boolean, "id": "string", "nodeSetIds": ["string"]}]}}, "storageResources": {"string": {"config": {"existingBucket": {"bucket": "string"}, "existingFilestore": {"filestore": "string"}, "existingLustre": {"lustre": "string"}, "newBucket": {"autoclass": {"enabled": boolean}, "bucket": "string", "hierarchicalNamespace": {"enabled": boolean}, "storageClass": "string"}, "newFilestore": {"description": "string", "fileShares": [{"capacityGb": int, "fileShare": "string"}], "filestore": "string", "protocol": "string", "tier": "string"}, "newLustre": {"capacityGb": int, "description": "string", "filesystem": "string", "lustre": "string"}}}}}' + --config='{"compute": {"resourceRequests": [{"disks": [{"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}], "id": "string", "machineType": "string", "maxRunDuration": int, "provisioningModel": "string", "reservationAffinity": {"key": "string", "type": "string", "values"}, "terminationAction": "string", "zone": "string"}]}, "computeResources": {"string": {"config": {"newDwsFlexInstances": {"atmTags": {"string": "string"}, "bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "machineType": "string", "maxDuration": "string", "terminationAction": "string", "zone": "string"}, "newFlexStartInstances": {"atmTags": {"string": "string"}, "bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "machineType": "string", "maxDuration": "string", "terminationAction": "string", "zone": "string"}, "newOnDemandInstances": {"atmTags": {"string": "string"}, "bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "machineType": "string", "zone": "string"}, "newReservedInstances": {"atmTags": {"string": "string"}, "bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "machineType": "string", "reservation": "string", "reservationBlock": "string", "reservationSubBlock": "string", "type": "string", "zone": "string"}, "newSpotInstances": {"atmTags": {"string": "string"}, "bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "machineType": "string", "terminationAction": "string", "zone": "string"}}}}, "description": "string", "labels": {"string": "string"}, "name": "string", "networkResources": {"string": {"config": {"existingComputeNetwork": {"network": "string", "subnetwork": "string"}, "existingNetwork": {"network": "string", "subnetwork": "string"}, "newComputeNetwork": {"description": "string", "network": "string"}, "newNetwork": {"description": "string", "network": "string"}}}}, "networks": [{"initializeParams": {"description": "string", "network": "string"}, "networkSource": {"network": "string", "subnetwork": "string"}}], "orchestrator": {"slurm": {"config": {"accountingStorageEnforceFlags", "preemptExemptTime": "string", "preemptMode", "preemptType": "string", "priorityType": "string", "priorityWeightAge": int, "priorityWeightAssoc": int, "priorityWeightFairshare": int, "priorityWeightJobSize": int, "priorityWeightPartition": int, "priorityWeightQos": int, "priorityWeightTres": "string", "prologEpilogTimeout": "string", "prologFlags", "requeueExitCodes", "requeueHoldExitCodes"}, "defaultPartition": "string", "epilogBashScripts", "loginNodes": {"bootDisk": {"image": "string", "sizeGb": int, "type": "string"}, "count": int, "disks": [{"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}], "enableOsLogin": boolean, "enablePublicIps": boolean, "labels": {"string": "string"}, "machineType": "string", "serviceAccount": {"email": "string", "scopes"}, "startupScript": "string", "storageConfigs": [{"id": "string", "localMount": "string"}], "zone": "string"}, "nodeSets": [{"bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "canIpForward": boolean, "computeId": "string", "computeInstance": {"bootDisk": {"image": "string", "sizeGb": int, "type": "string"}, "labels": {"string": "string"}, "startupScript": "string"}, "containerNodePool": {}, "enableOsLogin": boolean, "enablePublicIps": boolean, "id": "string", "labels": {"string": "string"}, "maxDynamicNodeCount": int, "resourceRequestId": "string", "serviceAccount": {"email": "string", "scopes"}, "startupScript": "string", "staticNodeCount": int, "storageConfigs": [{"id": "string", "localMount": "string"}]}], "partitions": [{"exclusive": boolean, "id": "string", "nodeSetIds": ["string"]}], "prologBashScripts", "taskEpilogBashScripts", "taskPrologBashScripts"}}, "storageResources": {"string": {"config": {"existingBucket": {"bucket": "string"}, "existingFilestore": {"filestore": "string"}, "existingLustre": {"lustre": "string"}, "newBucket": {"autoclass": {"enabled": boolean, "terminalStorageClass": "string"}, "bucket": "string", "hierarchicalNamespace": {"enabled": boolean}, "storageClass": "string"}, "newFilestore": {"description": "string", "fileShares": [{"capacityGb": int, "fileShare": "string"}], "filestore": "string", "protocol": "string", "tier": "string"}, "newLustre": {"capacityGb": int, "description": "string", "filesystem": "string", "lustre": "string", "perUnitStorageThroughput": int}}}}, "storages": [{"id": "string", "initializeParams": {"filestore": {"description": "string", "fileShares": [{"capacityGb": int, "fileShare": "string"}], "filestore": "string", "protocol": "string", "tier": "string"}, "gcs": {"autoclass": {"enabled": boolean, "terminalStorageClass": "string"}, "bucket": "string", "hierarchicalNamespace": {"enabled": boolean}, "storageClass": "string"}, "lustre": {"capacityGb": int, "description": "string", "filesystem": "string", "lustre": "string"}}, "storageSource": {"bucket": "string", "filestore": "string", "lustre": "string"}}]}' File Example: diff --git a/gcloud/alpha/cluster-director/clusters/update b/gcloud/alpha/cluster-director/clusters/update index a5d056e9d..67c5401a4 100644 --- a/gcloud/alpha/cluster-director/clusters/update +++ b/gcloud/alpha/cluster-director/clusters/update @@ -7,7 +7,16 @@ SYNOPSIS (CLUSTER : --location=LOCATION) (--add-dws-flex-instances=[id=ID], [machineType=MACHINETYPE],[maxDuration=MAXDURATION],[zone=ZONE] + --add-filestore-instances=[ADD_FILESTORE_INSTANCES,...] --add-labels=[ADD_LABELS,...] + --add-lustre-instances=[ADD_LUSTRE_INSTANCES,...] + --add-new-filestore-instances=[capacityGb=CAPACITYGB], + [description=DESCRIPTION], + [fileshare=FILESHARE],[name=NAME],[protocol=PROTOCOL],[tier=TIER] + --add-new-lustre-instances=[capacityGb=CAPACITYGB], + [description=DESCRIPTION],[filesystem=FILESYSTEM],[name=NAME] + --add-new-storage-buckets=[enableAutoclass=ENABLEAUTOCLASS], + [enableHNS=ENABLEHNS],[name=NAME],[storageClass=STORAGECLASS] --add-on-demand-instances=[id=ID], [machineType=MACHINETYPE],[zone=ZONE] --add-reserved-instances=[id=ID], @@ -18,14 +27,18 @@ SYNOPSIS --add-slurm-partitions=[exclusive=EXCLUSIVE], [id=ID],[nodesetIds=NODESETIDS] --add-spot-instances=[id=ID],[machineType=MACHINETYPE],[zone=ZONE] + --add-storage-buckets=[ADD_STORAGE_BUCKETS,...] --description=DESCRIPTION --remove-dws-flex-instances=[REMOVE_DWS_FLEX_INSTANCES,...] + --remove-filestore-instances=[REMOVE_FILESTORE_INSTANCES,...] --remove-labels=[REMOVE_LABELS,...] + --remove-lustre-instances=[REMOVE_LUSTRE_INSTANCES,...] --remove-on-demand-instances=[REMOVE_ON_DEMAND_INSTANCES,...] --remove-reserved-instances=[REMOVE_RESERVED_INSTANCES,...] --remove-slurm-node-sets=[REMOVE_SLURM_NODE_SETS,...] --remove-slurm-partitions=[REMOVE_SLURM_PARTITIONS,...] --remove-spot-instances=[REMOVE_SPOT_INSTANCES,...] + --remove-storage-buckets=[REMOVE_STORAGE_BUCKETS,...] --slurm-default-partition=SLURM_DEFAULT_PARTITION --update-slurm-login-node=[count=COUNT],[startupScript=STARTUPSCRIPT] --update-slurm-node-sets=[id=ID], @@ -33,10 +46,11 @@ SYNOPSIS [staticNodeCount=STATICNODECOUNT] --update-slurm-partitions=[exclusive=EXCLUSIVE], [id=ID],[nodesetIds=NODESETIDS] - | --config=[computeResources=COMPUTERESOURCES], + | --config=[compute=COMPUTE],[computeResources=COMPUTERESOURCES], [description=DESCRIPTION],[labels=LABELS],[name=NAME], - [networkResources=NETWORKRESOURCES], - [orchestrator=ORCHESTRATOR],[storageResources=STORAGERESOURCES] + [networkResources=NETWORKRESOURCES],[networks=NETWORKS], + [orchestrator=ORCHESTRATOR], + [storageResources=STORAGERESOURCES],[storages=STORAGES] --update-mask=UPDATE_MASK) [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -80,6 +94,11 @@ EXAMPLES --add-dws-flex-instances \ id=compute4,zone=us-central1-a,machineType=a4-highgpu-8g,\ maxDuration=10000s \ + --add-new-lustre-instances \ + lustre=locations/us-central1-a/instances/lustre1,\ + capacityGb=1024,filesystem=lustre1 \ + --add-lustre-instances \ + locations/us-central1-a/instances/lustre0 \ --add-slurm-node-sets id=nodeset1,computeId=compute1 \ --add-slurm-node-sets id=nodeset2,computeId=compute2 \ --add-slurm-node-sets id=nodeset3,computeId=compute3 \ @@ -104,6 +123,8 @@ EXAMPLES $ gcloud alpha cluster-director clusters update my-cluster \ --location us-central1-a --slurm-default-partition partition0 \ --remove-labels env,client \ + --remove-lustre-instances \ + locations/us-central1-a/instances/lustre0 \ --remove-slurm-partitions partition1 \ --remove-slurm-partitions partition2 \ --remove-slurm-node-sets nodeset1 \ @@ -208,6 +229,12 @@ REQUIRED FLAGS --add-dws-flex-instances=path_to_file.(yaml|json) + --add-filestore-instances=[ADD_FILESTORE_INSTANCES,...] + Reference of existing filestore instance. + + For e.g. --add-filestore-instances + locations/{location}/instances/{filestore} + --add-labels=[ADD_LABELS,...] Cluster labels as key value pairs. @@ -233,6 +260,139 @@ REQUIRED FLAGS --add-labels=path_to_file.(yaml|json) + --add-lustre-instances=[ADD_LUSTRE_INSTANCES,...] + Reference of existing Lustre instance. + + For e.g. --add-lustre-instances + locations/{location}/instances/{lustre} + + --add-new-filestore-instances=[capacityGb=CAPACITYGB],[description=DESCRIPTION],[fileshare=FILESHARE],[name=NAME],[protocol=PROTOCOL],[tier=TIER] + Parameters to create a filestore instance. + + For e.g. --create-filestores + name=locations/{location}/instances/{filestore},tier=REGIONAL,capacityGb={filestoreSize},fileshare={fileshare} + + Supported tier values: + ▫ ZONAL + ▫ REGIONAL + + Supported protocol values: + ▫ NFSV3 + ▫ NFSV41 + ▫ If not specified, defaults to NFSV3 + + Defaults: + ▫ protocol: NFSV3. + + Sets add_new_filestore_instances value. + + capacityGb + Required, sets capacityGb value. + + description + Sets description value. + + fileshare + Required, sets fileshare value. + + name + Required, sets name value. + + protocol + Sets protocol value. + + tier + Required, sets tier value. + + Shorthand Example: + + --add-new-filestore-instances=capacityGb=int,description=string,fileshare=string,name=string,protocol=string,tier=string --add-new-filestore-instances=capacityGb=int,description=string,fileshare=string,name=string,protocol=string,tier=string + + JSON Example: + + --add-new-filestore-instances='[{"capacityGb": int, "description": "string", "fileshare": "string", "name": "string", "protocol": "string", "tier": "string"}]' + + File Example: + + --add-new-filestore-instances=path_to_file.(yaml|json) + + --add-new-lustre-instances=[capacityGb=CAPACITYGB],[description=DESCRIPTION],[filesystem=FILESYSTEM],[name=NAME] + Parameters to create a Lustre instance. + + For e.g. --add-new-lustre-instances + name=locations/{location}/instances/{lustre},capacityGb={lustreSize},filesystem={filesystem}. + + Sets add_new_lustre_instances value. + + capacityGb + Required, sets capacityGb value. + + description + Sets description value. + + filesystem + Required, sets filesystem value. + + name + Required, sets name value. + + Shorthand Example: + + --add-new-lustre-instances=capacityGb=int,description=string,filesystem=string,name=string --add-new-lustre-instances=capacityGb=int,description=string,filesystem=string,name=string + + JSON Example: + + --add-new-lustre-instances='[{"capacityGb": int, "description": "string", "filesystem": "string", "name": "string"}]' + + File Example: + + --add-new-lustre-instances=path_to_file.(yaml|json) + + --add-new-storage-buckets=[enableAutoclass=ENABLEAUTOCLASS],[enableHNS=ENABLEHNS],[name=NAME],[storageClass=STORAGECLASS] + Parameters to create a Google Cloud Storage bucket. + + For e.g. --add-new-storage-buckets name={bucket-path} + + Supported storageClass values: + ▫ STANDARD + ▫ NEARLINE + ▫ COLDLINE + ▫ ARCHIVE + + Defaults: + ▫ storageClass: STANDARD + + Note: + ▫ Either storageClass or enableAutoclass can be set. + ▫ if enableAutoclass is set, enableHNS should not be set. + ▫ HNS: Hierarchical namespace. + + Sets add_new_storage_buckets value. + + enableAutoclass + Sets enableAutoclass value. + + enableHNS + Sets enableHNS value. + + name + Required, sets name value. + + storageClass + Sets storageClass value. + + Shorthand Example: + + --add-new-storage-buckets=enableAutoclass=boolean,enableHNS=boolean,name=string,storageClass=string --add-new-storage-buckets=enableAutoclass=boolean,enableHNS=boolean,name=string,storageClass=string + + JSON Example: + + --add-new-storage-buckets='[{"enableAutoclass": boolean, "enableHNS": boolean, "name": "string", "storageClass": "string"}]' + + File Example: + + --add-new-storage-buckets=path_to_file.(yaml|json) + --add-on-demand-instances=[id=ID],[machineType=MACHINETYPE],[zone=ZONE] Parameters to define cluster on demand instances. @@ -404,6 +564,11 @@ REQUIRED FLAGS --add-spot-instances=path_to_file.(yaml|json) + --add-storage-buckets=[ADD_STORAGE_BUCKETS,...] + Reference of existing Google Cloud Storage bucket. + + For e.g. --add-storage-buckets {bucket-path} + --description=DESCRIPTION Description of the cluster. @@ -414,11 +579,23 @@ REQUIRED FLAGS For e.g. --remove-dws-flex-instances {computeId1},{computeId2},... + --remove-filestore-instances=[REMOVE_FILESTORE_INSTANCES,...] + Parameters to remove filestore instance config by filestore name. + + For e.g. --remove-filestore-instances + locations/{location}/instances/{filestore1},locations/{location}/instances/{filestore2},... + --remove-labels=[REMOVE_LABELS,...] Parameters to remove cluster label by key. For e.g. --remove-labels {key1},{key2},... + --remove-lustre-instances=[REMOVE_LUSTRE_INSTANCES,...] + Parameters to remove lustre instance config by lustre name. + + For e.g. --remove-lustre-instances + locations/{location}/instances/{lustre1},locations/{location}/instances/{lustre2},... + --remove-on-demand-instances=[REMOVE_ON_DEMAND_INSTANCES,...] Parameters to remove on demand instances config by compute id. @@ -445,6 +622,11 @@ REQUIRED FLAGS For e.g. --remove-spot-instances {computeId1},{computeId2},... + --remove-storage-buckets=[REMOVE_STORAGE_BUCKETS,...] + Parameters to remove Google Cloud Storage bucket by bucket name. + + For e.g. --remove-storage-buckets {bucket1},{bucket2},... + --slurm-default-partition=SLURM_DEFAULT_PARTITION Parameters to define slurm cluster default partition. @@ -537,10 +719,61 @@ REQUIRED FLAGS Cluster configuration for updates. - --config=[computeResources=COMPUTERESOURCES],[description=DESCRIPTION],[labels=LABELS],[name=NAME],[networkResources=NETWORKRESOURCES],[orchestrator=ORCHESTRATOR],[storageResources=STORAGERESOURCES] + --config=[compute=COMPUTE],[computeResources=COMPUTERESOURCES],[description=DESCRIPTION],[labels=LABELS],[name=NAME],[networkResources=NETWORKRESOURCES],[networks=NETWORKS],[orchestrator=ORCHESTRATOR],[storageResources=STORAGERESOURCES],[storages=STORAGES] Configuration of the cluster specs in the form of a JSON object. Required, sets config value. + compute + Sets compute value. + + resourceRequests + Sets resourceRequests value. + + disks + Sets disks value. + + boot + Required, sets boot value. + + sizeGb + Sets sizeGb value. + + sourceImage + Sets sourceImage value. + + type + Required, sets type value. + + id + Sets id value. + + machineType + Sets machineType value. + + maxRunDuration + Sets maxRunDuration value. + + provisioningModel + Sets provisioningModel value. + + reservationAffinity + Sets reservationAffinity value. + + key + Sets key value. + + type + Sets type value. + + values + Sets values value. + + terminationAction + Sets terminationAction value. + + zone + Sets zone value. + computeResources Sets computeResources value. @@ -556,30 +789,108 @@ REQUIRED FLAGS newDwsFlexInstances Sets newDwsFlexInstances value. + atmTags + Sets atmTags value. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + bootDisk + Sets bootDisk value. + + boot + Required, sets boot value. + + sizeGb + Sets sizeGb value. + + sourceImage + Sets sourceImage value. + + type + Required, sets type value. + machineType Sets machineType value. maxDuration Sets maxDuration value. + terminationAction + Sets terminationAction value. + zone Sets zone value. newFlexStartInstances Sets newFlexStartInstances value. + atmTags + Sets atmTags value. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + bootDisk + Sets bootDisk value. + + boot + Required, sets boot value. + + sizeGb + Sets sizeGb value. + + sourceImage + Sets sourceImage value. + + type + Required, sets type value. + machineType Sets machineType value. maxDuration Sets maxDuration value. + terminationAction + Sets terminationAction value. + zone Sets zone value. newOnDemandInstances Sets newOnDemandInstances value. + atmTags + Sets atmTags value. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + bootDisk + Sets bootDisk value. + + boot + Required, sets boot value. + + sizeGb + Sets sizeGb value. + + sourceImage + Sets sourceImage value. + + type + Required, sets type value. + machineType Sets machineType value. @@ -589,12 +900,42 @@ REQUIRED FLAGS newReservedInstances Sets newReservedInstances value. + atmTags + Sets atmTags value. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + bootDisk + Sets bootDisk value. + + boot + Required, sets boot value. + + sizeGb + Sets sizeGb value. + + sourceImage + Sets sourceImage value. + + type + Required, sets type value. + machineType Sets machineType value. reservation Sets reservation value. + reservationBlock + Sets reservationBlock value. + + reservationSubBlock + Sets reservationSubBlock value. + type Sets type value. @@ -604,9 +945,36 @@ REQUIRED FLAGS newSpotInstances Sets newSpotInstances value. + atmTags + Sets atmTags value. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + bootDisk + Sets bootDisk value. + + boot + Required, sets boot value. + + sizeGb + Sets sizeGb value. + + sourceImage + Sets sourceImage value. + + type + Required, sets type value. + machineType Sets machineType value. + terminationAction + Sets terminationAction value. + zone Sets zone value. @@ -637,6 +1005,15 @@ REQUIRED FLAGS config Sets config value. + existingComputeNetwork + Sets existingComputeNetwork value. + + network + Sets network value. + + subnetwork + Sets subnetwork value. + existingNetwork Sets existingNetwork value. @@ -646,6 +1023,15 @@ REQUIRED FLAGS subnetwork Sets subnetwork value. + newComputeNetwork + Sets newComputeNetwork value. + + description + Sets description value. + + network + Sets network value. + newNetwork Sets newNetwork value. @@ -655,18 +1041,105 @@ REQUIRED FLAGS network Sets network value. + networks + Sets networks value. + + initializeParams + Sets initializeParams value. + + description + Sets description value. + + network + Sets network value. + + networkSource + Sets networkSource value. + + network + Sets network value. + + subnetwork + Sets subnetwork value. + orchestrator Sets orchestrator value. slurm Sets slurm value. + config + Sets config value. + + accountingStorageEnforceFlags + Sets accountingStorageEnforceFlags value. + + preemptExemptTime + Sets preemptExemptTime value. + + preemptMode + Sets preemptMode value. + + preemptType + Sets preemptType value. + + priorityType + Sets priorityType value. + + priorityWeightAge + Sets priorityWeightAge value. + + priorityWeightAssoc + Sets priorityWeightAssoc value. + + priorityWeightFairshare + Sets priorityWeightFairshare value. + + priorityWeightJobSize + Sets priorityWeightJobSize value. + + priorityWeightPartition + Sets priorityWeightPartition value. + + priorityWeightQos + Sets priorityWeightQos value. + + priorityWeightTres + Sets priorityWeightTres value. + + prologEpilogTimeout + Sets prologEpilogTimeout value. + + prologFlags + Sets prologFlags value. + + requeueExitCodes + Sets requeueExitCodes value. + + requeueHoldExitCodes + Sets requeueHoldExitCodes value. + defaultPartition Sets defaultPartition value. + epilogBashScripts + Sets epilogBashScripts value. + loginNodes Sets loginNodes value. + bootDisk + Sets bootDisk value. + + image + Sets image value. + + sizeGb + Required, sets sizeGb value. + + type + Required, sets type value. + count Sets count value. @@ -703,6 +1176,15 @@ REQUIRED FLAGS machineType Sets machineType value. + serviceAccount + Sets serviceAccount value. + + email + Sets email value. + + scopes + Sets scopes value. + startupScript Sets startupScript value. @@ -736,6 +1218,48 @@ REQUIRED FLAGS type Required, sets type value. + canIpForward + Sets canIpForward value. + + computeId + Sets computeId value. + + computeInstance + Sets computeInstance value. + + bootDisk + Sets bootDisk value. + + image + Sets image value. + + sizeGb + Required, sets sizeGb value. + + type + Required, sets type value. + + labels + Sets labels value. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + startupScript + Sets startupScript value. + + containerNodePool + Sets containerNodePool value. + + enableOsLogin + Sets enableOsLogin value. + + enablePublicIps + Sets enablePublicIps value. + id Sets id value. @@ -754,6 +1278,15 @@ REQUIRED FLAGS resourceRequestId Sets resourceRequestId value. + serviceAccount + Sets serviceAccount value. + + email + Sets email value. + + scopes + Sets scopes value. + startupScript Sets startupScript value. @@ -781,6 +1314,15 @@ REQUIRED FLAGS nodeSetIds Sets nodeSetIds value. + prologBashScripts + Sets prologBashScripts value. + + taskEpilogBashScripts + Sets taskEpilogBashScripts value. + + taskPrologBashScripts + Sets taskPrologBashScripts value. + storageResources Sets storageResources value. @@ -820,6 +1362,9 @@ REQUIRED FLAGS enabled Sets enabled value. + terminalStorageClass + Sets terminalStorageClass value. + bucket Sets bucket value. @@ -871,13 +1416,100 @@ REQUIRED FLAGS lustre Sets lustre value. + perUnitStorageThroughput + Sets perUnitStorageThroughput value. + + storages + Sets storages value. + + id + Sets id value. + + initializeParams + Sets initializeParams value. + + filestore + Sets filestore value. + + description + Sets description value. + + fileShares + Sets fileShares value. + + capacityGb + Sets capacityGb value. + + fileShare + Sets fileShare value. + + filestore + Sets filestore value. + + protocol + Sets protocol value. + + tier + Sets tier value. + + gcs + Sets gcs value. + + autoclass + Sets autoclass value. + + enabled + Sets enabled value. + + terminalStorageClass + Sets terminalStorageClass value. + + bucket + Sets bucket value. + + hierarchicalNamespace + Sets hierarchicalNamespace value. + + enabled + Sets enabled value. + + storageClass + Sets storageClass value. + + lustre + Sets lustre value. + + capacityGb + Sets capacityGb value. + + description + Sets description value. + + filesystem + Sets filesystem value. + + lustre + Sets lustre value. + + storageSource + Sets storageSource value. + + bucket + Sets bucket value. + + filestore + Sets filestore value. + + lustre + Sets lustre value. + Shorthand Example: - --config=computeResources={string={config={newDwsFlexInstances={machineType=string,maxDuration=string,zone=string},newFlexStartInstances={machineType=string,maxDuration=string,zone=string},newOnDemandInstances={machineType=string,zone=string},newReservedInstances={machineType=string,reservation=string,type=string,zone=string},newSpotInstances={machineType=string,zone=string}}}},description=string,labels={string=string},name=string,networkResources={string={config={existingNetwork={network=string,subnetwork=string},newNetwork={description=string,network=string}}}},orchestrator={slurm={defaultPartition=string,loginNodes={count=int,disks=[{boot=boolean,sizeGb=int,sourceImage=string,type=string}],enableOsLogin=boolean,enablePublicIps=boolean,labels={string=string},machineType=string,startupScript=string,storageConfigs=[{id=string,localMount=string}],zone=string},nodeSets=[{bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},id=string,labels={string=string},maxDynamicNodeCount=int,resourceRequestId=string,startupScript=string,staticNodeCount=int,storageConfigs=[{id=string,localMount=string}]}],partitions=[{exclusive=boolean,id=string,nodeSetIds=[string]}]}},storageResources={string={config={existingBucket={bucket=string},existingFilestore={filestore=string},existingLustre={lustre=string},newBucket={autoclass={enabled=boolean},bucket=string,hierarchicalNamespace={enabled=boolean},storageClass=string},newFilestore={description=string,fileShares=[{capacityGb=int,fileShare=string}],filestore=string,protocol=string,tier=string},newLustre={capacityGb=int,description=string,filesystem=string,lustre=string}}}} + --config=compute={resourceRequests=[{disks=[{boot=boolean,sizeGb=int,sourceImage=string,type=string}],id=string,machineType=string,maxRunDuration=int,provisioningModel=string,reservationAffinity={key=string,type=string,values},terminationAction=string,zone=string}]},computeResources={string={config={newDwsFlexInstances={atmTags={string=string},bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},machineType=string,maxDuration=string,terminationAction=string,zone=string},newFlexStartInstances={atmTags={string=string},bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},machineType=string,maxDuration=string,terminationAction=string,zone=string},newOnDemandInstances={atmTags={string=string},bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},machineType=string,zone=string},newReservedInstances={atmTags={string=string},bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},machineType=string,reservation=string,reservationBlock=string,reservationSubBlock=string,type=string,zone=string},newSpotInstances={atmTags={string=string},bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},machineType=string,terminationAction=string,zone=string}}}},description=string,labels={string=string},name=string,networkResources={string={config={existingComputeNetwork={network=string,subnetwork=string},existingNetwork={network=string,subnetwork=string},newComputeNetwork={description=string,network=string},newNetwork={description=string,network=string}}}},networks=[{initializeParams={description=string,network=string},networkSource={network=string,subnetwork=string}}],orchestrator={slurm={config={accountingStorageEnforceFlags,preemptExemptTime=string,preemptMode,preemptType=string,priorityType=string,priorityWeightAge=int,priorityWeightAssoc=int,priorityWeightFairshare=int,priorityWeightJobSize=int,priorityWeightPartition=int,priorityWeightQos=int,priorityWeightTres=string,prologEpilogTimeout=string,prologFlags,requeueExitCodes,requeueHoldExitCodes},defaultPartition=string,epilogBashScripts,loginNodes={bootDisk={image=string,sizeGb=int,type=string},count=int,disks=[{boot=boolean,sizeGb=int,sourceImage=string,type=string}],enableOsLogin=boolean,enablePublicIps=boolean,labels={string=string},machineType=string,serviceAccount={email=string,scopes},startupScript=string,storageConfigs=[{id=string,localMount=string}],zone=string},nodeSets=[{bootDisk={boot=boolean,sizeGb=int,sourceImage=string,type=string},canIpForward=boolean,computeId=string,computeInstance={bootDisk={image=string,sizeGb=int,type=string},labels={string=string},startupScript=string},containerNodePool,enableOsLogin=boolean,enablePublicIps=boolean,id=string,labels={string=string},maxDynamicNodeCount=int,resourceRequestId=string,serviceAccount={email=string,scopes},startupScript=string,staticNodeCount=int,storageConfigs=[{id=string,localMount=string}]}],partitions=[{exclusive=boolean,id=string,nodeSetIds=[string]}],prologBashScripts,taskEpilogBashScripts,taskPrologBashScripts}},storageResources={string={config={existingBucket={bucket=string},existingFilestore={filestore=string},existingLustre={lustre=string},newBucket={autoclass={enabled=boolean,terminalStorageClass=string},bucket=string,hierarchicalNamespace={enabled=boolean},storageClass=string},newFilestore={description=string,fileShares=[{capacityGb=int,fileShare=string}],filestore=string,protocol=string,tier=string},newLustre={capacityGb=int,description=string,filesystem=string,lustre=string,perUnitStorageThroughput=int}}}},storages=[{id=string,initializeParams={filestore={description=string,fileShares=[{capacityGb=int,fileShare=string}],filestore=string,protocol=string,tier=string},gcs={autoclass={enabled=boolean,terminalStorageClass=string},bucket=string,hierarchicalNamespace={enabled=boolean},storageClass=string},lustre={capacityGb=int,description=string,filesystem=string,lustre=string}},storageSource={bucket=string,filestore=string,lustre=string}}] JSON Example: - --config='{"computeResources": {"string": {"config": {"newDwsFlexInstances": {"machineType": "string", "maxDuration": "string", "zone": "string"}, "newFlexStartInstances": {"machineType": "string", "maxDuration": "string", "zone": "string"}, "newOnDemandInstances": {"machineType": "string", "zone": "string"}, "newReservedInstances": {"machineType": "string", "reservation": "string", "type": "string", "zone": "string"}, "newSpotInstances": {"machineType": "string", "zone": "string"}}}}, "description": "string", "labels": {"string": "string"}, "name": "string", "networkResources": {"string": {"config": {"existingNetwork": {"network": "string", "subnetwork": "string"}, "newNetwork": {"description": "string", "network": "string"}}}}, "orchestrator": {"slurm": {"defaultPartition": "string", "loginNodes": {"count": int, "disks": [{"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}], "enableOsLogin": boolean, "enablePublicIps": boolean, "labels": {"string": "string"}, "machineType": "string", "startupScript": "string", "storageConfigs": [{"id": "string", "localMount": "string"}], "zone": "string"}, "nodeSets": [{"bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "id": "string", "labels": {"string": "string"}, "maxDynamicNodeCount": int, "resourceRequestId": "string", "startupScript": "string", "staticNodeCount": int, "storageConfigs": [{"id": "string", "localMount": "string"}]}], "partitions": [{"exclusive": boolean, "id": "string", "nodeSetIds": ["string"]}]}}, "storageResources": {"string": {"config": {"existingBucket": {"bucket": "string"}, "existingFilestore": {"filestore": "string"}, "existingLustre": {"lustre": "string"}, "newBucket": {"autoclass": {"enabled": boolean}, "bucket": "string", "hierarchicalNamespace": {"enabled": boolean}, "storageClass": "string"}, "newFilestore": {"description": "string", "fileShares": [{"capacityGb": int, "fileShare": "string"}], "filestore": "string", "protocol": "string", "tier": "string"}, "newLustre": {"capacityGb": int, "description": "string", "filesystem": "string", "lustre": "string"}}}}}' + --config='{"compute": {"resourceRequests": [{"disks": [{"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}], "id": "string", "machineType": "string", "maxRunDuration": int, "provisioningModel": "string", "reservationAffinity": {"key": "string", "type": "string", "values"}, "terminationAction": "string", "zone": "string"}]}, "computeResources": {"string": {"config": {"newDwsFlexInstances": {"atmTags": {"string": "string"}, "bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "machineType": "string", "maxDuration": "string", "terminationAction": "string", "zone": "string"}, "newFlexStartInstances": {"atmTags": {"string": "string"}, "bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "machineType": "string", "maxDuration": "string", "terminationAction": "string", "zone": "string"}, "newOnDemandInstances": {"atmTags": {"string": "string"}, "bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "machineType": "string", "zone": "string"}, "newReservedInstances": {"atmTags": {"string": "string"}, "bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "machineType": "string", "reservation": "string", "reservationBlock": "string", "reservationSubBlock": "string", "type": "string", "zone": "string"}, "newSpotInstances": {"atmTags": {"string": "string"}, "bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "machineType": "string", "terminationAction": "string", "zone": "string"}}}}, "description": "string", "labels": {"string": "string"}, "name": "string", "networkResources": {"string": {"config": {"existingComputeNetwork": {"network": "string", "subnetwork": "string"}, "existingNetwork": {"network": "string", "subnetwork": "string"}, "newComputeNetwork": {"description": "string", "network": "string"}, "newNetwork": {"description": "string", "network": "string"}}}}, "networks": [{"initializeParams": {"description": "string", "network": "string"}, "networkSource": {"network": "string", "subnetwork": "string"}}], "orchestrator": {"slurm": {"config": {"accountingStorageEnforceFlags", "preemptExemptTime": "string", "preemptMode", "preemptType": "string", "priorityType": "string", "priorityWeightAge": int, "priorityWeightAssoc": int, "priorityWeightFairshare": int, "priorityWeightJobSize": int, "priorityWeightPartition": int, "priorityWeightQos": int, "priorityWeightTres": "string", "prologEpilogTimeout": "string", "prologFlags", "requeueExitCodes", "requeueHoldExitCodes"}, "defaultPartition": "string", "epilogBashScripts", "loginNodes": {"bootDisk": {"image": "string", "sizeGb": int, "type": "string"}, "count": int, "disks": [{"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}], "enableOsLogin": boolean, "enablePublicIps": boolean, "labels": {"string": "string"}, "machineType": "string", "serviceAccount": {"email": "string", "scopes"}, "startupScript": "string", "storageConfigs": [{"id": "string", "localMount": "string"}], "zone": "string"}, "nodeSets": [{"bootDisk": {"boot": boolean, "sizeGb": int, "sourceImage": "string", "type": "string"}, "canIpForward": boolean, "computeId": "string", "computeInstance": {"bootDisk": {"image": "string", "sizeGb": int, "type": "string"}, "labels": {"string": "string"}, "startupScript": "string"}, "containerNodePool": {}, "enableOsLogin": boolean, "enablePublicIps": boolean, "id": "string", "labels": {"string": "string"}, "maxDynamicNodeCount": int, "resourceRequestId": "string", "serviceAccount": {"email": "string", "scopes"}, "startupScript": "string", "staticNodeCount": int, "storageConfigs": [{"id": "string", "localMount": "string"}]}], "partitions": [{"exclusive": boolean, "id": "string", "nodeSetIds": ["string"]}], "prologBashScripts", "taskEpilogBashScripts", "taskPrologBashScripts"}}, "storageResources": {"string": {"config": {"existingBucket": {"bucket": "string"}, "existingFilestore": {"filestore": "string"}, "existingLustre": {"lustre": "string"}, "newBucket": {"autoclass": {"enabled": boolean, "terminalStorageClass": "string"}, "bucket": "string", "hierarchicalNamespace": {"enabled": boolean}, "storageClass": "string"}, "newFilestore": {"description": "string", "fileShares": [{"capacityGb": int, "fileShare": "string"}], "filestore": "string", "protocol": "string", "tier": "string"}, "newLustre": {"capacityGb": int, "description": "string", "filesystem": "string", "lustre": "string", "perUnitStorageThroughput": int}}}}, "storages": [{"id": "string", "initializeParams": {"filestore": {"description": "string", "fileShares": [{"capacityGb": int, "fileShare": "string"}], "filestore": "string", "protocol": "string", "tier": "string"}, "gcs": {"autoclass": {"enabled": boolean, "terminalStorageClass": "string"}, "bucket": "string", "hierarchicalNamespace": {"enabled": boolean}, "storageClass": "string"}, "lustre": {"capacityGb": int, "description": "string", "filesystem": "string", "lustre": "string"}}, "storageSource": {"bucket": "string", "filestore": "string", "lustre": "string"}}]}' File Example: diff --git a/gcloud/alpha/compute/advice/calendar-mode b/gcloud/alpha/compute/advice/calendar-mode index a42990a71..3b289ca52 100644 --- a/gcloud/alpha/compute/advice/calendar-mode +++ b/gcloud/alpha/compute/advice/calendar-mode @@ -153,8 +153,8 @@ OPTIONAL FLAGS gcloud compute advice calendar-mode --location-policy=us-central1-a=allow,us-central1-b=deny --region=REGION - Region of the to None. If not specified, you might be prompted to - select a region (interactive mode only). + Region of the resources to get advice on. If not specified, you might + be prompted to select a region (interactive mode only). To avoid prompting when this flag is omitted, you can set the compute/region property: diff --git a/gcloud/alpha/compute/backend-services/create b/gcloud/alpha/compute/backend-services/create index 4e65a32a4..eaf9daa1f 100644 --- a/gcloud/alpha/compute/backend-services/create +++ b/gcloud/alpha/compute/backend-services/create @@ -43,9 +43,7 @@ SYNOPSIS [--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE] [--subsetting-policy=SUBSETTING_POLICY; default="NONE"] [--subsetting-subset-size=SUBSETTING_SUBSET_SIZE] - [--timeout=TIMEOUT; default="30s"] - [--tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG],[sni=SNI]] - [--tracking-mode=TRACKING_MODE] + [--timeout=TIMEOUT; default="30s"] [--tracking-mode=TRACKING_MODE] [--zonal-affinity-spillover=ZONAL_AFFINITY_SPILLOVER] [--zonal-affinity-spillover-ratio=ZONAL_AFFINITY_SPILLOVER_RATIO] [--cache-key-query-string-blacklist=[QUERY_STRING,...] @@ -54,7 +52,9 @@ SYNOPSIS | --custom-metrics-file=[CUSTOM_METRICS,...]] [--global | --region=REGION] [--global-health-checks | --health-checks-region=HEALTH_CHECKS_REGION] - [GCLOUD_WIDE_FLAG ...] + [--identity=IDENTITY + | --tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG], + [sni=SNI]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute backend-services create creates a backend @@ -749,14 +749,6 @@ FLAGS The full range of timeout values allowed is 1 - 2,147,483,647 seconds. - --tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG],[sni=SNI] - Configuration for Backend Authenticated TLS and mTLS. May only be - specified when the backend protocol is SSL, HTTPS or HTTP2. - - Example: $ gcloud alpha compute backend-services create \ - --tls-settings='sni=example.com,authenticationConfig=${AUTH_CONF\ - IG_NAME}' - --tracking-mode=TRACKING_MODE Specifies the connection key used for connection tracking. The default value is PER_CONNECTION. Applicable only for backend service-based @@ -934,6 +926,37 @@ FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: + + --identity=IDENTITY + Assigns the Managed Identity for the BackendService Workload. Use + this property to configure the load balancer back-end to use + certificates and roots of trust provisioned by the Managed Workload + Identity system. The identity property is the scheme-less SPIFFE ID + to use in the SVID presented by the Load Balancer Workload. The + SPIFFE ID must be a resource starting with the trustDomain property + value, followed by the path to the Managed Workload Identity. + Supported SPIFFE ID format: + ///ns//sa/ The Trust Domain within + the Managed Identity must refer to a valid Workload Identity Pool. + The TrustConfig and CertificateIssuanceConfig will be inherited from + the Workload Identity Pool. Restrictions: If you set the identity + property, you cannot manually set the following fields: + tlsSettings.sni, tlsSettings.subjectAltNames, + tlsSettings.authenticationConfig. When defining a identity for a + RegionBackendServices, the corresponding Workload Identity Pool must + have a ca_pool configured in the same region. The system will set up + a read-only tlsSettings.authenticationConfig for the Managed + Identity. + + --tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG],[sni=SNI] + Configuration for Backend Authenticated TLS and mTLS. May only be + specified when the backend protocol is SSL, HTTPS or HTTP2. + + Example: $ gcloud alpha compute backend-services create \ + --tls-settings='sni=example.com,authenticationConfig=${AUTH_CONF\ + IG_NAME}' + 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/compute/commitments/create b/gcloud/alpha/compute/commitments/create index 4da3c4a0d..2c6bc1475 100644 --- a/gcloud/alpha/compute/commitments/create +++ b/gcloud/alpha/compute/commitments/create @@ -109,11 +109,12 @@ OPTIONAL FLAGS for memory-optimized VMs. TYPE must be one of: accelerator-optimized, accelerator-optimized-a3, accelerator-optimized-a3-mega, accelerator-optimized-a3-ultra, accelerator-optimized-a4, - accelerator-optimized-a4x, compute-optimized, compute-optimized-c2d, - compute-optimized-c3, compute-optimized-c3d, compute-optimized-h3, - compute-optimized-h4d, general-purpose, general-purpose-c4, - general-purpose-c4a, general-purpose-c4d, general-purpose-e2, - general-purpose-n2, general-purpose-n2d, general-purpose-n4, + accelerator-optimized-a4x, accelerator-optimized-a4x-max, + compute-optimized, compute-optimized-c2d, compute-optimized-c3, + compute-optimized-c3d, compute-optimized-h3, compute-optimized-h4d, + general-purpose, general-purpose-c4, general-purpose-c4a, + general-purpose-c4d, general-purpose-e2, general-purpose-n2, + general-purpose-n2d, general-purpose-n4, general-purpose-n4a, general-purpose-n4d, general-purpose-t2d, graphics-optimized, graphics-optimized-g4, memory-optimized, memory-optimized-m3, memory-optimized-m4, memory-optimized-m4-6tb, memory-optimized-x4, diff --git a/gcloud/alpha/compute/health-checks/create/grpc-with-tls b/gcloud/alpha/compute/health-checks/create/grpc-with-tls index 0631f9da9..d2240e20d 100644 --- a/gcloud/alpha/compute/health-checks/create/grpc-with-tls +++ b/gcloud/alpha/compute/health-checks/create/grpc-with-tls @@ -115,5 +115,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud compute health-checks create grpc-with-tls + + $ gcloud beta compute health-checks create grpc-with-tls diff --git a/gcloud/alpha/compute/health-checks/update/grpc-with-tls b/gcloud/alpha/compute/health-checks/update/grpc-with-tls index 8dc32e085..495165f4e 100644 --- a/gcloud/alpha/compute/health-checks/update/grpc-with-tls +++ b/gcloud/alpha/compute/health-checks/update/grpc-with-tls @@ -111,5 +111,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud compute health-checks update grpc-with-tls + + $ gcloud beta compute health-checks update grpc-with-tls diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index 2fe40e6f1..84befd2fb 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -22,6 +22,7 @@ SYNOPSIS [--graceful-shutdown] [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] + [--identity=IDENTITY] [--[no-]identity-certificate] [--instance-template-region=INSTANCE_TEMPLATE_REGION] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] @@ -466,6 +467,14 @@ FLAGS with 30 second increments, with a range of 90 to 330 seconds. If unset, the default behavior of the host error recovery is used. + --identity=IDENTITY + The workload identity to use for the instance. + + --[no-]identity-certificate + Enables or disables managed workload identities on a VM. Use + --identity-certificate to enable and --no-identity-certificate to + disable. + --instance-template-region=INSTANCE_TEMPLATE_REGION Specifies the region of the regional instance template. diff --git a/gcloud/alpha/compute/instance-templates/create-with-container b/gcloud/alpha/compute/instance-templates/create-with-container index a50486efa..34b26e5ed 100644 --- a/gcloud/alpha/compute/instance-templates/create-with-container +++ b/gcloud/alpha/compute/instance-templates/create-with-container @@ -29,6 +29,7 @@ SYNOPSIS [interface=INTERFACE],[mode=MODE],[name=NAME]] [--external-ipv6-address=EXTERNAL_IPV6_ADDRESS] [--external-ipv6-prefix-length=EXTERNAL_IPV6_PREFIX_LENGTH] + [--identity=IDENTITY] [--[no-]identity-certificate] [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] [--internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH] [--ipv6-address=IPV6_ADDRESS] [--ipv6-network-tier=IPV6_NETWORK_TIER] @@ -463,6 +464,14 @@ FLAGS be used together with --external-ipv6-address. Only the /96 IP address range is supported, and the default value is 96. + --identity=IDENTITY + The workload identity to use for the instance. + + --[no-]identity-certificate + Enables or disables managed workload identities on a VM. Use + --identity-certificate to enable and --no-identity-certificate to + disable. + --internal-ipv6-address=INTERNAL_IPV6_ADDRESS Assigns the given internal IPv6 address or range to the instance that is created. The address must be the first IP address in the range or diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 61a6a8c3f..1589e0e2b 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -23,6 +23,7 @@ SYNOPSIS [--erase-windows-vss-signature] [--graceful-shutdown] [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] + [--identity=IDENTITY] [--[no-]identity-certificate] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME], @@ -66,6 +67,9 @@ SYNOPSIS [--image-project=IMAGE_PROJECT --source-snapshot-region=SOURCE_SNAPSHOT_REGION --image=IMAGE | --image-family=IMAGE_FAMILY | --source-snapshot=SOURCE_SNAPSHOT] + [--instance-selection=name=NAME[, + rank=RANK][,machine-type=MACHINE_TYPE]...[,disk=DISK_JSON]... + | --instance-selection-machine-types=[MACHINE_TYPE,...]] [--maintenance-policy=MAINTENANCE_POLICY | --on-host-maintenance=MAINTENANCE_POLICY] [--public-dns | --no-public-dns] @@ -477,6 +481,14 @@ OPTIONAL FLAGS with 30 second increments, with a range of 90 to 330 seconds. If unset, the default behavior of the host error recovery is used. + --identity=IDENTITY + The workload identity to use for the instance. + + --[no-]identity-certificate + Enables or disables managed workload identities on a VM. Use + --identity-certificate to enable and --no-identity-certificate to + disable. + --instance-termination-action=INSTANCE_TERMINATION_ACTION Specifies the termination action that will be taken upon VM preemption (--provisioning-model=SPOT) or automatic instance termination @@ -1078,6 +1090,27 @@ OPTIONAL FLAGS ▸ https://compute.googleapis.com/compute/v1/projects/myproject/global/snapshots/snapshot ▸ snapshot + At most one of these can be specified: + + --instance-selection=name=NAME[,rank=RANK][,machine-type=MACHINE_TYPE]...[,disk=DISK_JSON]... + \ Specifies a list of machine types to consider for instance + creation. The bulk create operation will attempt to create instances + from this list based on capacity availability. This flag is only + valid when a region is specified. + + Keys for each instance selection: + + name: (Required) A unique name for this instance selection group. + machine-type: (Required) Repeatable. Specifies a machine type to include in this group (e.g., machine-type=n1-standard-1). + rank: (Optional) An integer representing the priority. Lower ranks are preferred. Defaults to 0. + disk: (Optional) Repeatable. A JSON string defining a disk to attach or override, conforming to the Compute Engine AttachedDisk API structure. Example: disk='{"deviceName": "boot-disk", "boot": true, "initializeParams": {"sourceImage": "IMAGE_URL"}}' + + --instance-selection-machine-types=[MACHINE_TYPE,...] + \ Specifies a list of machine types to consider for instance + creation. The bulk create operation will attempt to create instances + from this list based on capacity availability. This flag is only + valid when a region is specified. + Maintenance Behavior. At most one of these can be specified: diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 559e626f3..248edeb10 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -27,7 +27,8 @@ SYNOPSIS [--graceful-shutdown] [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] - [--hostname=HOSTNAME] + [--hostname=HOSTNAME] [--identity=IDENTITY] + [--[no-]identity-certificate] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] [--internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH] @@ -595,6 +596,14 @@ FLAGS the global DNS, and [INSTANCE_NAME].[ZONE].c.[PROJECT_ID].internal when using zonal DNS. + --identity=IDENTITY + The workload identity to use for the instance. + + --[no-]identity-certificate + Enables or disables managed workload identities on a VM. Use + --identity-certificate to enable and --no-identity-certificate to + disable. + --instance-termination-action=INSTANCE_TERMINATION_ACTION Specifies the termination action that will be taken upon VM preemption (--provisioning-model=SPOT) or automatic instance termination diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index 347484725..b36004521 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -35,6 +35,7 @@ SYNOPSIS [--graceful-shutdown] [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] + [--identity=IDENTITY] [--[no-]identity-certificate] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--internal-ipv6-address=INTERNAL_IPV6_ADDRESS] [--internal-ipv6-prefix-length=INTERNAL_IPV6_PREFIX_LENGTH] @@ -521,6 +522,14 @@ FLAGS with 30 second increments, with a range of 90 to 330 seconds. If unset, the default behavior of the host error recovery is used. + --identity=IDENTITY + The workload identity to use for the instance. + + --[no-]identity-certificate + Enables or disables managed workload identities on a VM. Use + --identity-certificate to enable and --no-identity-certificate to + disable. + --instance-termination-action=INSTANCE_TERMINATION_ACTION Specifies the termination action that will be taken upon VM preemption (--provisioning-model=SPOT) or automatic instance termination diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/add-mapping b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/add-mapping index 3f420abc2..f2e794d62 100644 --- a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/add-mapping +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/add-mapping @@ -69,5 +69,10 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding add-mapping + + $ gcloud beta compute interconnects attachments l2-forwarding \ + add-mapping diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/create b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/create index 05a47faf9..3421065d3 100644 --- a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/create +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/create @@ -129,5 +129,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding create + + $ gcloud beta compute interconnects attachments l2-forwarding create diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/describe-mapping b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/describe-mapping index 5e3f59f35..767d592d2 100644 --- a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/describe-mapping +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/describe-mapping @@ -55,5 +55,11 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding \ + describe-mapping + + $ gcloud beta compute interconnects attachments l2-forwarding \ + describe-mapping diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/help b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/help index 1e5c777db..6e769aedc 100644 --- a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/help +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/help @@ -51,5 +51,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding + + $ gcloud beta compute interconnects attachments l2-forwarding diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/list-mapping b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/list-mapping index d16fdaa56..04336fa33 100644 --- a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/list-mapping +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/list-mapping @@ -103,5 +103,10 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding list-mapping + + $ gcloud beta compute interconnects attachments l2-forwarding \ + list-mapping diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/remove-mapping b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/remove-mapping index be30b4234..41bf09bbf 100644 --- a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/remove-mapping +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/remove-mapping @@ -53,5 +53,11 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding \ + remove-mapping + + $ gcloud beta compute interconnects attachments l2-forwarding \ + remove-mapping diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update index 112a90c95..fa56d3a92 100644 --- a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update @@ -137,5 +137,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding update + + $ gcloud beta compute interconnects attachments l2-forwarding update diff --git a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update-mapping b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update-mapping index 915e275ce..99d35ecb3 100644 --- a/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update-mapping +++ b/gcloud/alpha/compute/interconnects/attachments/l2-forwarding/update-mapping @@ -70,5 +70,11 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding \ + update-mapping + + $ gcloud beta compute interconnects attachments l2-forwarding \ + update-mapping diff --git a/gcloud/alpha/compute/networks/subnets/create b/gcloud/alpha/compute/networks/subnets/create index e3b8edea3..b8d2d7257 100644 --- a/gcloud/alpha/compute/networks/subnets/create +++ b/gcloud/alpha/compute/networks/subnets/create @@ -85,15 +85,19 @@ OPTIONAL FLAGS is 0.5 which means half of all collected logs are reported. --internal-ipv6-prefix=INTERNAL_IPV6_PREFIX - Set internal IPv6 prefix to be allocated for this subnetwork. When ULA - is enabled, the prefix will be ignored. + The /64 internal IPv6 CIDR range to assign to this subnet. The range + must be associated with an IPv6 BYOIP sub-prefix that is defined by the + --ip-collection flag. If you specify --ip-collection but not + --internal-ipv6-prefix, a random /64 range is allocated from the + sub-prefix. For example, --internal-ipv6-prefix 2600:1901:0:0:0:0:0:0/64 --ip-collection=IP_COLLECTION Resource reference to a public delegated prefix. The PublicDelegatedPrefix must be a sub-prefix in - EXTERNAL_IPV6_SUBNETWORK_CREATION mode. + EXTERNAL_IPV6_SUBNETWORK_CREATION or INTERNAL_IPV6_SUBNETWORK_CREATION + mode. --ipv6-access-type=IPV6_ACCESS_TYPE IPv6 access type can be specified only when the subnet is created, or diff --git a/gcloud/alpha/compute/networks/subnets/update b/gcloud/alpha/compute/networks/subnets/update index 95155cf3b..24e22a227 100644 --- a/gcloud/alpha/compute/networks/subnets/update +++ b/gcloud/alpha/compute/networks/subnets/update @@ -87,15 +87,19 @@ FLAGS half of all collected logs are reported. --internal-ipv6-prefix=INTERNAL_IPV6_PREFIX - Set internal IPv6 prefix to be allocated for this subnetwork. When ULA - is enabled, the prefix will be ignored. + The /64 internal IPv6 CIDR range to assign to this subnet. The range + must be associated with an IPv6 BYOIP sub-prefix that is defined by the + --ip-collection flag. If you specify --ip-collection but not + --internal-ipv6-prefix, a random /64 range is allocated from the + sub-prefix. For example, --internal-ipv6-prefix 2600:1901:0:0:0:0:0:0/64 --ip-collection=IP_COLLECTION Resource reference to a public delegated prefix. The PublicDelegatedPrefix must be a sub-prefix in - EXTERNAL_IPV6_SUBNETWORK_CREATION mode. + EXTERNAL_IPV6_SUBNETWORK_CREATION or INTERNAL_IPV6_SUBNETWORK_CREATION + mode. --ipv6-access-type=IPV6_ACCESS_TYPE IPv6 access type can be specified only when the subnet is created, or diff --git a/gcloud/alpha/compute/public-advertised-prefixes/create b/gcloud/alpha/compute/public-advertised-prefixes/create index 0dbc3d379..feab76fef 100644 --- a/gcloud/alpha/compute/public-advertised-prefixes/create +++ b/gcloud/alpha/compute/public-advertised-prefixes/create @@ -1,6 +1,6 @@ NAME - gcloud alpha compute public-advertised-prefixes create - create a public - advertised prefix in the Alpha release track + gcloud alpha compute public-advertised-prefixes create - creates a Compute + Engine public advertised prefix SYNOPSIS gcloud alpha compute public-advertised-prefixes create NAME --range=RANGE diff --git a/gcloud/alpha/compute/public-advertised-prefixes/help b/gcloud/alpha/compute/public-advertised-prefixes/help index 93cbb6da9..65d62dd2d 100644 --- a/gcloud/alpha/compute/public-advertised-prefixes/help +++ b/gcloud/alpha/compute/public-advertised-prefixes/help @@ -18,7 +18,7 @@ COMMANDS COMMAND is one of the following: create - (ALPHA) Create a public advertised prefix in the Alpha release track. + (ALPHA) Creates a Compute Engine public advertised prefix. delete (ALPHA) Deletes a Compute Engine public advertised prefix. diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index c9d343a3e..b517e7387 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -24,6 +24,7 @@ SYNOPSIS [--erase-windows-vss-signature] [--graceful-shutdown] [--graceful-shutdown-max-duration=GRACEFUL_SHUTDOWN_MAX_DURATION] [--host-error-timeout-seconds=HOST_ERROR_TIMEOUT_SECONDS] + [--identity=IDENTITY] [--[no-]identity-certificate] [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME], @@ -66,6 +67,9 @@ SYNOPSIS [--image-project=IMAGE_PROJECT --source-snapshot-region=SOURCE_SNAPSHOT_REGION --image=IMAGE | --image-family=IMAGE_FAMILY | --source-snapshot=SOURCE_SNAPSHOT] + [--instance-selection=name=NAME[, + rank=RANK][,machine-type=MACHINE_TYPE]...[,disk=DISK_JSON]... + | --instance-selection-machine-types=[MACHINE_TYPE,...]] [--maintenance-policy=MAINTENANCE_POLICY | --on-host-maintenance=MAINTENANCE_POLICY] [--public-dns | --no-public-dns] @@ -461,6 +465,14 @@ OPTIONAL FLAGS with 30 second increments, with a range of 90 to 330 seconds. If unset, the default behavior of the host error recovery is used. + --identity=IDENTITY + The workload identity to use for the instance. + + --[no-]identity-certificate + Enables or disables managed workload identities on a VM. Use + --identity-certificate to enable and --no-identity-certificate to + disable. + --instance-termination-action=INSTANCE_TERMINATION_ACTION Specifies the termination action that will be taken upon VM preemption (--provisioning-model=SPOT) or automatic instance termination @@ -1075,6 +1087,27 @@ OPTIONAL FLAGS ▸ https://compute.googleapis.com/compute/v1/projects/myproject/global/snapshots/snapshot ▸ snapshot + At most one of these can be specified: + + --instance-selection=name=NAME[,rank=RANK][,machine-type=MACHINE_TYPE]...[,disk=DISK_JSON]... + \ Specifies a list of machine types to consider for instance + creation. The bulk create operation will attempt to create instances + from this list based on capacity availability. This flag is only + valid when a region is specified. + + Keys for each instance selection: + + name: (Required) A unique name for this instance selection group. + machine-type: (Required) Repeatable. Specifies a machine type to include in this group (e.g., machine-type=n1-standard-1). + rank: (Optional) An integer representing the priority. Lower ranks are preferred. Defaults to 0. + disk: (Optional) Repeatable. A JSON string defining a disk to attach or override, conforming to the Compute Engine AttachedDisk API structure. Example: disk='{"deviceName": "boot-disk", "boot": true, "initializeParams": {"sourceImage": "IMAGE_URL"}}' + + --instance-selection-machine-types=[MACHINE_TYPE,...] + \ Specifies a list of machine types to consider for instance + creation. The bulk create operation will attempt to create instances + from this list based on capacity availability. This flag is only + valid when a region is specified. + Maintenance Behavior. At most one of these can be specified: diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/create b/gcloud/alpha/compute/zone-vm-extension-policies/create index 60072845a..eb24a1c0a 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/create +++ b/gcloud/alpha/compute/zone-vm-extension-policies/create @@ -26,6 +26,11 @@ EXAMPLES --inclusion-labels=env=preprod,workload=load-test \ --priority=1000 + Available extensions: + ops-agent + google-cloud-sap-extension + google-cloud-workload-extension + POSITIONAL ARGUMENTS NAME Name of the zone vm extension policy to create. @@ -129,5 +134,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute zone-vm-extension-policies create diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/delete b/gcloud/alpha/compute/zone-vm-extension-policies/delete index 1d95e0f3f..1a9784d6e 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/delete +++ b/gcloud/alpha/compute/zone-vm-extension-policies/delete @@ -53,5 +53,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute zone-vm-extension-policies delete diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/describe b/gcloud/alpha/compute/zone-vm-extension-policies/describe index 81555c835..9810c1264 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/describe +++ b/gcloud/alpha/compute/zone-vm-extension-policies/describe @@ -53,5 +53,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute zone-vm-extension-policies describe diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/help b/gcloud/alpha/compute/zone-vm-extension-policies/help index 77884c67d..20fd068d8 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/help +++ b/gcloud/alpha/compute/zone-vm-extension-policies/help @@ -36,5 +36,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute zone-vm-extension-policies diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/list b/gcloud/alpha/compute/zone-vm-extension-policies/list index 4932bfbdd..93182d814 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/list +++ b/gcloud/alpha/compute/zone-vm-extension-policies/list @@ -63,5 +63,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute zone-vm-extension-policies list diff --git a/gcloud/alpha/compute/zone-vm-extension-policies/update b/gcloud/alpha/compute/zone-vm-extension-policies/update index f51585e94..f9d9da125 100644 --- a/gcloud/alpha/compute/zone-vm-extension-policies/update +++ b/gcloud/alpha/compute/zone-vm-extension-policies/update @@ -129,5 +129,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta compute zone-vm-extension-policies update diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index dbfe0c74c..09c7bff9c 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -114,6 +114,7 @@ SYNOPSIS | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] [--disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics] + [--disable-pod-snapshots | --enable-pod-snapshots] [--enable-autoprovisioning --autoprovisioning-config-file=PATH_TO_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE --autoprovisioning-locations=ZONE,[ZONE,...] @@ -2114,6 +2115,14 @@ FLAGS --enable-dataplane-v2-metrics Exposes advanced datapath flow metrics on node port. + At most one of these can be specified: + + --disable-pod-snapshots + Disable the Pod Snapshot feature on the cluster. + + --enable-pod-snapshots + Enable the Pod Snapshot feature on the cluster. + Node autoprovisioning --enable-autoprovisioning diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index 634bec458..f13f10ee6 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -50,6 +50,7 @@ SYNOPSIS [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] + [--disable-pod-snapshots | --enable-pod-snapshots] [--enable-insecure-binding-system-authenticated --enable-insecure-binding-system-unauthenticated] [--enable-master-authorized-networks @@ -660,6 +661,14 @@ FLAGS Enables Advanced Datapath Observability which allows for a real-time view into pod-to-pod traffic within your cluster. + At most one of these can be specified: + + --disable-pod-snapshots + Disable the Pod Snapshot feature on the cluster. + + --enable-pod-snapshots + Enable the Pod Snapshot feature on the cluster. + --enable-insecure-binding-system-authenticated Allow using system:authenticated as a subject in ClusterRoleBindings and RoleBindings. Allowing bindings that reference system:authenticated diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index eee016219..a89644196 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -94,7 +94,8 @@ SYNOPSIS --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics | --disable-auto-ipam | --enable-auto-ipam | --disable-l4-lb-firewall-reconciliation - | --enable-l4-lb-firewall-reconciliation + | --enable-l4-lb-firewall-reconciliation | --disable-pod-snapshots + | --enable-pod-snapshots | --enable-authorized-networks-on-private-endpoint --enable-dns-access --enable-google-cloud-access --enable-ip-access --enable-k8s-certs-via-dns --enable-k8s-tokens-via-dns @@ -1341,6 +1342,14 @@ REQUIRED FLAGS firewalls targeting ingress traffic. L4 LB VPC firewall reconciliation is enabled by default. + At most one of these can be specified: + + --disable-pod-snapshots + Disable the Pod Snapshot feature on the cluster. + + --enable-pod-snapshots + Enable the Pod Snapshot feature on the cluster. + --enable-authorized-networks-on-private-endpoint Enable enforcement of --master-authorized-networks CIDR ranges for traffic reaching cluster's control plane via private IP. diff --git a/gcloud/alpha/container/fleet/help b/gcloud/alpha/container/fleet/help index a6a084984..a523219d9 100644 --- a/gcloud/alpha/container/fleet/help +++ b/gcloud/alpha/container/fleet/help @@ -94,6 +94,12 @@ GROUPS rbacrolebindingactuation (ALPHA) Manage RbacRoleBinding Actuation. + rollouts + (ALPHA) Create and manage rollouts. + + rolloutsequences + (ALPHA) Create and manage rollout sequences. + scopes (ALPHA) Manage scopes of all your GKE fleets. diff --git a/gcloud/alpha/container/fleet/rollouts/describe b/gcloud/alpha/container/fleet/rollouts/describe new file mode 100644 index 000000000..f536c4f04 --- /dev/null +++ b/gcloud/alpha/container/fleet/rollouts/describe @@ -0,0 +1,53 @@ +NAME + gcloud alpha container fleet rollouts describe - describe a fleet rollout + +SYNOPSIS + gcloud alpha container fleet rollouts describe ROLLOUT + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a fleet rollout. + +EXAMPLES + To describe a rollout named my-rollout, run: + + $ gcloud alpha container fleet rollouts describe my-rollout + +POSITIONAL ARGUMENTS + Rollout resource - The group of arguments defining a Fleet Rollout. 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 rollout 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 rollout on the command line with a fully + specified name; + ◆ global is the only supported location. + + This must be specified. + + ROLLOUT + ID of the rollout or fully qualified identifier for the rollout. + + To set the rollout attribute: + ▸ provide the argument rollout 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. + diff --git a/gcloud/alpha/network-management/help b/gcloud/alpha/container/fleet/rollouts/help similarity index 51% rename from gcloud/alpha/network-management/help rename to gcloud/alpha/container/fleet/rollouts/help index d8dc92acd..b7b85e390 100644 --- a/gcloud/alpha/network-management/help +++ b/gcloud/alpha/container/fleet/rollouts/help @@ -1,24 +1,29 @@ NAME - gcloud alpha network-management - manage Network Management resources + gcloud alpha container fleet rollouts - create and manage rollouts SYNOPSIS - gcloud alpha network-management GROUP [GCLOUD_WIDE_FLAG ...] + gcloud alpha container fleet rollouts COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage Network Management resources. + (ALPHA) Create and manage rollouts. 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 a fleet rollout. + + list + (ALPHA) List all fleet rollouts. + 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 network-management - - $ gcloud beta network-management + access allowlist. diff --git a/gcloud/alpha/container/fleet/rollouts/list b/gcloud/alpha/container/fleet/rollouts/list new file mode 100644 index 000000000..02e6989d0 --- /dev/null +++ b/gcloud/alpha/container/fleet/rollouts/list @@ -0,0 +1,62 @@ +NAME + gcloud alpha container fleet rollouts list - list all fleet rollouts + +SYNOPSIS + gcloud alpha container fleet rollouts list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all fleet rollouts. + +EXAMPLES + To list all rollouts, run: + + $ gcloud alpha container fleet rollouts 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. + diff --git a/gcloud/alpha/container/fleet/rolloutsequences/create b/gcloud/alpha/container/fleet/rolloutsequences/create new file mode 100644 index 000000000..cee696e76 --- /dev/null +++ b/gcloud/alpha/container/fleet/rolloutsequences/create @@ -0,0 +1,95 @@ +NAME + gcloud alpha container fleet rolloutsequences create - create a rollout + sequence resource + +SYNOPSIS + gcloud alpha container fleet rolloutsequences create ROLLOUTSEQUENCE + --stage-config=PATH_TO_FILE [--async] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a rollout sequence resource. + +EXAMPLES + To create a rollout sequence, run: + + $ gcloud alpha container fleet rolloutsequences create \ + ROLLOUTSEQUENCE --stage-config=path/to/config.yaml + +POSITIONAL ARGUMENTS + RolloutSequence resource - The group of arguments defining a Rollout + Sequence. 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 rolloutSequence 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 rolloutSequence on the command line with a fully + specified name; + ◆ global is the only supported location. + + This must be specified. + + ROLLOUTSEQUENCE + ID of the rolloutSequence or fully qualified identifier for the + rolloutSequence. + + To set the rollout_sequence attribute: + ▸ provide the argument rolloutSequence on the command line. + +REQUIRED FLAGS + --stage-config=PATH_TO_FILE + Path to the YAML file containing the stage configurations. The YAML + file should contain a list of stages. Fleet projects and soak_duration + are required. If label_selector is not specified, there is no + filtering. A fleet project is the project where the fleet is hosted. + Example: + + - stage: + fleet-projects: + # Expected format: projects/{project} + - projects/my-dev-project + soak-duration: 604800s # 7 days + - stage: + fleet-projects: + - projects/my-prod-project + soak-duration: 604800s # 7 days + label-selector: resource.labels.canary=='true' + - stage: + fleet-projects: + # Expected format: projects/{project} + - projects/my-prod-project + soak-duration: 604800s # 7 days + + Use a full or relative path to a local file containing the value of + stage_config. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + Display name of the rollout sequence to be created (optional). + + --labels=[KEY=VALUE,...] + Labels for the rollout sequence. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/container/fleet/rolloutsequences/delete b/gcloud/alpha/container/fleet/rolloutsequences/delete new file mode 100644 index 000000000..1cbb85ad1 --- /dev/null +++ b/gcloud/alpha/container/fleet/rolloutsequences/delete @@ -0,0 +1,61 @@ +NAME + gcloud alpha container fleet rolloutsequences delete - delete a rollout + sequence resource + +SYNOPSIS + gcloud alpha container fleet rolloutsequences delete ROLLOUTSEQUENCE + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a rollout sequence resource. + +EXAMPLES + To delete a rollout sequence, run: + + $ gcloud alpha container fleet rolloutsequences delete \ + ROLLOUTSEQUENCE + +POSITIONAL ARGUMENTS + RolloutSequence resource - The group of arguments defining a Rollout + Sequence. 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 rolloutSequence 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 rolloutSequence on the command line with a fully + specified name; + ◆ global is the only supported location. + + This must be specified. + + ROLLOUTSEQUENCE + ID of the rolloutSequence or fully qualified identifier for the + rolloutSequence. + + To set the rollout_sequence attribute: + ▸ provide the argument rolloutSequence on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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/container/fleet/rolloutsequences/describe b/gcloud/alpha/container/fleet/rolloutsequences/describe new file mode 100644 index 000000000..0aac6f9b6 --- /dev/null +++ b/gcloud/alpha/container/fleet/rolloutsequences/describe @@ -0,0 +1,56 @@ +NAME + gcloud alpha container fleet rolloutsequences describe - describe a rollout + sequence + +SYNOPSIS + gcloud alpha container fleet rolloutsequences describe ROLLOUTSEQUENCE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a rollout sequence. + +EXAMPLES + To describe a rollout sequence named my-rollout-sequence, run: + + $ gcloud alpha container fleet rolloutsequences describe \ + my-rollout-sequence + +POSITIONAL ARGUMENTS + RolloutSequence resource - The group of arguments defining a Rollout + Sequence. 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 rolloutSequence 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 rolloutSequence on the command line with a fully + specified name; + ◆ global is the only supported location. + + This must be specified. + + ROLLOUTSEQUENCE + ID of the rolloutSequence or fully qualified identifier for the + rolloutSequence. + + To set the rollout_sequence attribute: + ▸ provide the argument rolloutSequence 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. + diff --git a/gcloud/alpha/container/fleet/rolloutsequences/help b/gcloud/alpha/container/fleet/rolloutsequences/help new file mode 100644 index 000000000..d6db0e42b --- /dev/null +++ b/gcloud/alpha/container/fleet/rolloutsequences/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha container fleet rolloutsequences - create and manage rollout + sequences + +SYNOPSIS + gcloud alpha container fleet rolloutsequences COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create and manage rollout sequences. + +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 rollout sequence resource. + + delete + (ALPHA) Delete a rollout sequence resource. + + describe + (ALPHA) Describe a rollout sequence. + + list + (ALPHA) List all rollout sequences. + + update + (ALPHA) Update a rollout sequence 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/container/fleet/rolloutsequences/list b/gcloud/alpha/container/fleet/rolloutsequences/list new file mode 100644 index 000000000..1c4fe7d91 --- /dev/null +++ b/gcloud/alpha/container/fleet/rolloutsequences/list @@ -0,0 +1,63 @@ +NAME + gcloud alpha container fleet rolloutsequences list - list all rollout + sequences + +SYNOPSIS + gcloud alpha container fleet rolloutsequences list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all rollout sequences. + +EXAMPLES + To list all rollout sequences, run: + + $ gcloud alpha container fleet rolloutsequences 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. + diff --git a/gcloud/alpha/container/fleet/rolloutsequences/update b/gcloud/alpha/container/fleet/rolloutsequences/update new file mode 100644 index 000000000..91efc6f33 --- /dev/null +++ b/gcloud/alpha/container/fleet/rolloutsequences/update @@ -0,0 +1,95 @@ +NAME + gcloud alpha container fleet rolloutsequences update - update a rollout + sequence resource + +SYNOPSIS + gcloud alpha container fleet rolloutsequences update ROLLOUTSEQUENCE + --stage-config=PATH_TO_FILE [--async] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a rollout sequence resource. + +EXAMPLES + To update a rollout sequence, run: + + $ gcloud alpha container fleet rolloutsequences update \ + ROLLOUT_SEQUENCE_NAME --stage-config=path/to/config.yaml + +POSITIONAL ARGUMENTS + RolloutSequence resource - The group of arguments defining a Rollout + Sequence. 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 rolloutSequence 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 rolloutSequence on the command line with a fully + specified name; + ◆ global is the only supported location. + + This must be specified. + + ROLLOUTSEQUENCE + ID of the rolloutSequence or fully qualified identifier for the + rolloutSequence. + + To set the rollout_sequence attribute: + ▸ provide the argument rolloutSequence on the command line. + +REQUIRED FLAGS + --stage-config=PATH_TO_FILE + Path to the YAML file containing the stage configurations. The YAML + file should contain a list of stages. Fleet projects and soak_duration + are required. If label_selector is not specified, there is no + filtering. A fleet project is the project where the fleet is hosted. + Example: + + - stage: + fleet-projects: + # Expected format: projects/{project} + - projects/my-dev-project + soak-duration: 604800s # 7 days + - stage: + fleet-projects: + - projects/my-prod-project + soak-duration: 604800s # 7 days + label-selector: resource.labels.canary=='true' + - stage: + fleet-projects: + # Expected format: projects/{project} + - projects/my-prod-project + soak-duration: 604800s # 7 days + + Use a full or relative path to a local file containing the value of + stage_config. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + Display name of the rollout sequence to be created (optional). + + --labels=[KEY=VALUE,...] + Labels for the rollout sequence. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/container/hub/help b/gcloud/alpha/container/hub/help index e0901b93b..a783bba1a 100644 --- a/gcloud/alpha/container/hub/help +++ b/gcloud/alpha/container/hub/help @@ -94,6 +94,12 @@ GROUPS rbacrolebindingactuation (ALPHA) Manage RbacRoleBinding Actuation. + rollouts + (ALPHA) Create and manage rollouts. + + rolloutsequences + (ALPHA) Create and manage rollout sequences. + scopes (ALPHA) Manage scopes of all your GKE fleets. diff --git a/gcloud/alpha/container/hub/rollouts/describe b/gcloud/alpha/container/hub/rollouts/describe new file mode 100644 index 000000000..32432c3d2 --- /dev/null +++ b/gcloud/alpha/container/hub/rollouts/describe @@ -0,0 +1,52 @@ +NAME + gcloud alpha container hub rollouts describe - describe a fleet rollout + +SYNOPSIS + gcloud alpha container hub rollouts describe ROLLOUT [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a fleet rollout. + +EXAMPLES + To describe a rollout named my-rollout, run: + + $ gcloud alpha container hub rollouts describe my-rollout + +POSITIONAL ARGUMENTS + Rollout resource - The group of arguments defining a Fleet Rollout. 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 rollout 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 rollout on the command line with a fully + specified name; + ◆ global is the only supported location. + + This must be specified. + + ROLLOUT + ID of the rollout or fully qualified identifier for the rollout. + + To set the rollout attribute: + ▸ provide the argument rollout 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. + diff --git a/gcloud/alpha/biglake/iceberg/tables/help b/gcloud/alpha/container/hub/rollouts/help similarity index 53% rename from gcloud/alpha/biglake/iceberg/tables/help rename to gcloud/alpha/container/hub/rollouts/help index 8f040d1d6..270ad1039 100644 --- a/gcloud/alpha/biglake/iceberg/tables/help +++ b/gcloud/alpha/container/hub/rollouts/help @@ -1,12 +1,11 @@ NAME - gcloud alpha biglake iceberg tables - manage BigLake Iceberg REST catalog - tables + gcloud alpha container hub rollouts - create and manage rollouts SYNOPSIS - gcloud alpha biglake iceberg tables COMMAND [GCLOUD_WIDE_FLAG ...] + gcloud alpha container hub rollouts COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage BigLake Iceberg REST catalog tables. + (ALPHA) Create and manage rollouts. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -16,11 +15,11 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: - get-iam-policy - (ALPHA) Get the IAM policy for a BigLake Iceberg REST catalog table. + describe + (ALPHA) Describe a fleet rollout. - set-iam-policy - (ALPHA) Set the IAM policy for a BigLake Iceberg REST catalog table. + list + (ALPHA) List all fleet rollouts. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/container/hub/rollouts/list b/gcloud/alpha/container/hub/rollouts/list new file mode 100644 index 000000000..2f0a03adf --- /dev/null +++ b/gcloud/alpha/container/hub/rollouts/list @@ -0,0 +1,62 @@ +NAME + gcloud alpha container hub rollouts list - list all fleet rollouts + +SYNOPSIS + gcloud alpha container hub rollouts list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all fleet rollouts. + +EXAMPLES + To list all rollouts, run: + + $ gcloud alpha container hub rollouts 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. + diff --git a/gcloud/alpha/container/hub/rolloutsequences/create b/gcloud/alpha/container/hub/rolloutsequences/create new file mode 100644 index 000000000..9445c94af --- /dev/null +++ b/gcloud/alpha/container/hub/rolloutsequences/create @@ -0,0 +1,95 @@ +NAME + gcloud alpha container hub rolloutsequences create - create a rollout + sequence resource + +SYNOPSIS + gcloud alpha container hub rolloutsequences create ROLLOUTSEQUENCE + --stage-config=PATH_TO_FILE [--async] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a rollout sequence resource. + +EXAMPLES + To create a rollout sequence, run: + + $ gcloud alpha container hub rolloutsequences create \ + ROLLOUTSEQUENCE --stage-config=path/to/config.yaml + +POSITIONAL ARGUMENTS + RolloutSequence resource - The group of arguments defining a Rollout + Sequence. 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 rolloutSequence 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 rolloutSequence on the command line with a fully + specified name; + ◆ global is the only supported location. + + This must be specified. + + ROLLOUTSEQUENCE + ID of the rolloutSequence or fully qualified identifier for the + rolloutSequence. + + To set the rollout_sequence attribute: + ▸ provide the argument rolloutSequence on the command line. + +REQUIRED FLAGS + --stage-config=PATH_TO_FILE + Path to the YAML file containing the stage configurations. The YAML + file should contain a list of stages. Fleet projects and soak_duration + are required. If label_selector is not specified, there is no + filtering. A fleet project is the project where the fleet is hosted. + Example: + + - stage: + fleet-projects: + # Expected format: projects/{project} + - projects/my-dev-project + soak-duration: 604800s # 7 days + - stage: + fleet-projects: + - projects/my-prod-project + soak-duration: 604800s # 7 days + label-selector: resource.labels.canary=='true' + - stage: + fleet-projects: + # Expected format: projects/{project} + - projects/my-prod-project + soak-duration: 604800s # 7 days + + Use a full or relative path to a local file containing the value of + stage_config. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + Display name of the rollout sequence to be created (optional). + + --labels=[KEY=VALUE,...] + Labels for the rollout sequence. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/container/hub/rolloutsequences/delete b/gcloud/alpha/container/hub/rolloutsequences/delete new file mode 100644 index 000000000..ccb5c0d66 --- /dev/null +++ b/gcloud/alpha/container/hub/rolloutsequences/delete @@ -0,0 +1,60 @@ +NAME + gcloud alpha container hub rolloutsequences delete - delete a rollout + sequence resource + +SYNOPSIS + gcloud alpha container hub rolloutsequences delete ROLLOUTSEQUENCE + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a rollout sequence resource. + +EXAMPLES + To delete a rollout sequence, run: + + $ gcloud alpha container hub rolloutsequences delete ROLLOUTSEQUENCE + +POSITIONAL ARGUMENTS + RolloutSequence resource - The group of arguments defining a Rollout + Sequence. 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 rolloutSequence 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 rolloutSequence on the command line with a fully + specified name; + ◆ global is the only supported location. + + This must be specified. + + ROLLOUTSEQUENCE + ID of the rolloutSequence or fully qualified identifier for the + rolloutSequence. + + To set the rollout_sequence attribute: + ▸ provide the argument rolloutSequence on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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/container/hub/rolloutsequences/describe b/gcloud/alpha/container/hub/rolloutsequences/describe new file mode 100644 index 000000000..ea61ac952 --- /dev/null +++ b/gcloud/alpha/container/hub/rolloutsequences/describe @@ -0,0 +1,56 @@ +NAME + gcloud alpha container hub rolloutsequences describe - describe a rollout + sequence + +SYNOPSIS + gcloud alpha container hub rolloutsequences describe ROLLOUTSEQUENCE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a rollout sequence. + +EXAMPLES + To describe a rollout sequence named my-rollout-sequence, run: + + $ gcloud alpha container hub rolloutsequences describe \ + my-rollout-sequence + +POSITIONAL ARGUMENTS + RolloutSequence resource - The group of arguments defining a Rollout + Sequence. 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 rolloutSequence 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 rolloutSequence on the command line with a fully + specified name; + ◆ global is the only supported location. + + This must be specified. + + ROLLOUTSEQUENCE + ID of the rolloutSequence or fully qualified identifier for the + rolloutSequence. + + To set the rollout_sequence attribute: + ▸ provide the argument rolloutSequence 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. + diff --git a/gcloud/alpha/container/hub/rolloutsequences/help b/gcloud/alpha/container/hub/rolloutsequences/help new file mode 100644 index 000000000..960139061 --- /dev/null +++ b/gcloud/alpha/container/hub/rolloutsequences/help @@ -0,0 +1,39 @@ +NAME + gcloud alpha container hub rolloutsequences - create and manage rollout + sequences + +SYNOPSIS + gcloud alpha container hub rolloutsequences COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create and manage rollout sequences. + +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 rollout sequence resource. + + delete + (ALPHA) Delete a rollout sequence resource. + + describe + (ALPHA) Describe a rollout sequence. + + list + (ALPHA) List all rollout sequences. + + update + (ALPHA) Update a rollout sequence 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/container/hub/rolloutsequences/list b/gcloud/alpha/container/hub/rolloutsequences/list new file mode 100644 index 000000000..d0d4020ea --- /dev/null +++ b/gcloud/alpha/container/hub/rolloutsequences/list @@ -0,0 +1,63 @@ +NAME + gcloud alpha container hub rolloutsequences list - list all rollout + sequences + +SYNOPSIS + gcloud alpha container hub rolloutsequences list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all rollout sequences. + +EXAMPLES + To list all rollout sequences, run: + + $ gcloud alpha container hub rolloutsequences 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. + diff --git a/gcloud/alpha/container/hub/rolloutsequences/update b/gcloud/alpha/container/hub/rolloutsequences/update new file mode 100644 index 000000000..b9578b56e --- /dev/null +++ b/gcloud/alpha/container/hub/rolloutsequences/update @@ -0,0 +1,95 @@ +NAME + gcloud alpha container hub rolloutsequences update - update a rollout + sequence resource + +SYNOPSIS + gcloud alpha container hub rolloutsequences update ROLLOUTSEQUENCE + --stage-config=PATH_TO_FILE [--async] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a rollout sequence resource. + +EXAMPLES + To update a rollout sequence, run: + + $ gcloud alpha container hub rolloutsequences update \ + ROLLOUT_SEQUENCE_NAME --stage-config=path/to/config.yaml + +POSITIONAL ARGUMENTS + RolloutSequence resource - The group of arguments defining a Rollout + Sequence. 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 rolloutSequence 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 rolloutSequence on the command line with a fully + specified name; + ◆ global is the only supported location. + + This must be specified. + + ROLLOUTSEQUENCE + ID of the rolloutSequence or fully qualified identifier for the + rolloutSequence. + + To set the rollout_sequence attribute: + ▸ provide the argument rolloutSequence on the command line. + +REQUIRED FLAGS + --stage-config=PATH_TO_FILE + Path to the YAML file containing the stage configurations. The YAML + file should contain a list of stages. Fleet projects and soak_duration + are required. If label_selector is not specified, there is no + filtering. A fleet project is the project where the fleet is hosted. + Example: + + - stage: + fleet-projects: + # Expected format: projects/{project} + - projects/my-dev-project + soak-duration: 604800s # 7 days + - stage: + fleet-projects: + - projects/my-prod-project + soak-duration: 604800s # 7 days + label-selector: resource.labels.canary=='true' + - stage: + fleet-projects: + # Expected format: projects/{project} + - projects/my-prod-project + soak-duration: 604800s # 7 days + + Use a full or relative path to a local file containing the value of + stage_config. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + Display name of the rollout sequence to be created (optional). + + --labels=[KEY=VALUE,...] + Labels for the rollout sequence. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index 317645517..eb8cee67b 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -157,9 +157,6 @@ FLAGS machine type needs to be specified with the --machine-type flag. An Accelerator Network Profiles will be created if it does not exist. - ACCELERATOR_NETWORK_PROFILE must be (only one value is supported): - auto. - --additional-node-network=[network=NETWORK_NAME,subnetwork=SUBNETWORK_NAME,...] Attach an additional network interface to each node in the pool. This parameter can be specified up to 7 times. diff --git a/gcloud/alpha/container/operations/cancel b/gcloud/alpha/container/operations/cancel index 971a0df37..a4063169e 100644 --- a/gcloud/alpha/container/operations/cancel +++ b/gcloud/alpha/container/operations/cancel @@ -17,6 +17,8 @@ DESCRIPTION would be if all the nodes have been upgraded but the operation hasn't been marked as complete. + Only node pool upgrade operations support cancellation. + EXAMPLES To cancel an operation, run: diff --git a/gcloud/alpha/dataplex/datascans/create/data-documentation b/gcloud/alpha/dataplex/datascans/create/data-documentation new file mode 100644 index 000000000..92f4b278c --- /dev/null +++ b/gcloud/alpha/dataplex/datascans/create/data-documentation @@ -0,0 +1,135 @@ +NAME + gcloud alpha dataplex datascans create data-documentation - create a + Dataplex data documentation scan job + +SYNOPSIS + gcloud alpha dataplex datascans create data-documentation + (DATASCAN : --location=LOCATION) + (--data-source-entity=DATA_SOURCE_ENTITY + | --data-source-resource=DATA_SOURCE_RESOURCE) + [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] + [--labels=[KEY=VALUE,...]] [--async | --validate-only] + [--on-demand=ON_DEMAND | --schedule=SCHEDULE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Allows users to generate documentation for Dataplex BigQuery + tables. + +EXAMPLES + To create a data documentation scan data-documentation-datascan in project + test-project located in us-central1 on entity test-entity, run: + + $ gcloud alpha dataplex datascans create data-documentation \ + data-documentation-datascan --project=test-project \ + --location=us-central1 \ + --data-source-resource="//bigquery.{universe_domain}/projects/te\ + st-project/datasets/test-dataset/tables/test-table" + +POSITIONAL ARGUMENTS + Datascan resource - Arguments and flags that define the Dataplex datascan + you want to create a data documentation scan for. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument datascan 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. + + DATASCAN + ID of the datascan or fully qualified identifier for the datascan. + + To set the dataScans attribute: + ▸ provide the argument datascan 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 Dataplex resource. + + To set the location attribute: + ▸ provide the argument datascan on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +REQUIRED FLAGS + Data source for the data documentation scan. + + Exactly one of these must be specified: + + --data-source-entity=DATA_SOURCE_ENTITY + The Dataplex entity that contains the data for the data documentation + scan, of the form: + projects/{project_id_or_number}/locations/{location_id}/lakes/{lake_id}/zones/{zone_id}/entities/{entity_id}. + Currently only BigQuery table is supported. + + --data-source-resource=DATA_SOURCE_RESOURCE + Fully-qualified service resource name of the cloud resource that + contains the data for the data documentation scan, of the form: + //bigquery.{universe_domain}/projects/{project_id_or_number}/datasets/{dataset_id}/tables/{table_id}. + +OPTIONAL FLAGS + --description=DESCRIPTION + Description of the data documentation scan. + + --display-name=DISPLAY_NAME + Display name of the data documentation scan. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of --async | --validate-only can be specified. + + At most one of these can be specified: + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --validate-only + Validate the create action, but don't actually perform it. + + Data documentation scan execution settings. + + Data documentation scan scheduling and trigger settings. + + At most one of these can be specified: + + --on-demand=ON_DEMAND + If set, the scan runs one-time shortly after data documentation + scan creation. + + --schedule=SCHEDULE + Cron schedule (https://en.wikipedia.org/wiki/Cron) for running + scans periodically. To explicitly set a timezone to the cron tab, + apply a prefix in the cron tab: "CRON_TZ=${IANA_TIME_ZONE}" or + "TZ=${IANA_TIME_ZONE}". The ${IANA_TIME_ZONE} may only be a valid + string from IANA time zone database. For example, + CRON_TZ=America/New_York 1 * * * * or TZ=America/New_York 1 * * * + *. This field is required for RECURRING scans. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/dataplex/datascans/create/help b/gcloud/alpha/dataplex/datascans/create/help index 7d4d0a4b8..615b33547 100644 --- a/gcloud/alpha/dataplex/datascans/create/help +++ b/gcloud/alpha/dataplex/datascans/create/help @@ -18,6 +18,9 @@ COMMANDS data-discovery (ALPHA) Create a Dataplex data discovery scan job. + data-documentation + (ALPHA) Create a Dataplex data documentation scan job. + data-profile (ALPHA) Create a Dataplex data profile scan job. diff --git a/gcloud/alpha/dataplex/datascans/update/data-documentation b/gcloud/alpha/dataplex/datascans/update/data-documentation new file mode 100644 index 000000000..9316664bd --- /dev/null +++ b/gcloud/alpha/dataplex/datascans/update/data-documentation @@ -0,0 +1,114 @@ +NAME + gcloud alpha dataplex datascans update data-documentation - update a + Dataplex data documentation scan job + +SYNOPSIS + gcloud alpha dataplex datascans update data-documentation + (DATASCAN : --location=LOCATION) [--description=DESCRIPTION] + [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [--async | --validate-only] + [--on-demand=ON_DEMAND | --schedule=SCHEDULE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Dataplex data documentation scan job. + +EXAMPLES + To update a data documentation scan data-documentation-datascan in project + test-project located in us-central1 with a new description, run: + + $ gcloud alpha dataplex datascans update data-documentation \ + data-documentation-datascan --project=test-project \ + --location=us-central1 --description="new description" + +POSITIONAL ARGUMENTS + Datascan resource - Arguments and flags that define the Dataplex datascan + you want to update a data documentation scan for. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument datascan 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. + + DATASCAN + ID of the datascan or fully qualified identifier for the datascan. + + To set the dataScans attribute: + ▸ provide the argument datascan 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 Dataplex resource. + + To set the location attribute: + ▸ provide the argument datascan on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property dataplex/location. + +FLAGS + --description=DESCRIPTION + Description of the data documentation scan. + + --display-name=DISPLAY_NAME + Display name of the data documentation scan. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of --async | --validate-only can be specified. + + At most one of these can be specified: + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --validate-only + Validate the update action, but don't actually perform it. + + Data documentation scan execution settings. + + Data documentation scan scheduling and trigger settings. + + At most one of these can be specified: + + --on-demand=ON_DEMAND + If set, the scan runs one-time shortly after data documentation + scan creation. + + --schedule=SCHEDULE + Cron schedule (https://en.wikipedia.org/wiki/Cron) for running + scans periodically. To explicitly set a timezone to the cron tab, + apply a prefix in the cron tab: "CRON_TZ=${IANA_TIME_ZONE}" or + "TZ=${IANA_TIME_ZONE}". The ${IANA_TIME_ZONE} may only be a valid + string from IANA time zone database. For example, + CRON_TZ=America/New_York 1 * * * * or TZ=America/New_York 1 * * * + *. This field is required for RECURRING scans. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/dataplex/datascans/update/help b/gcloud/alpha/dataplex/datascans/update/help index 305c5fcc4..3649eb80d 100644 --- a/gcloud/alpha/dataplex/datascans/update/help +++ b/gcloud/alpha/dataplex/datascans/update/help @@ -18,6 +18,9 @@ COMMANDS data-discovery (ALPHA) Update a Dataplex data discovery scan job. + data-documentation + (ALPHA) Update a Dataplex data documentation scan job. + data-profile (ALPHA) Update a Dataplex data profile scan job. diff --git a/gcloud/alpha/design-center/spaces/application-templates/help b/gcloud/alpha/design-center/spaces/application-templates/help index f672c397f..1c0e688d3 100644 --- a/gcloud/alpha/design-center/spaces/application-templates/help +++ b/gcloud/alpha/design-center/spaces/application-templates/help @@ -44,6 +44,10 @@ COMMANDS import (ALPHA) Import to an application template. + import-iac + (ALPHA) Import Infrastructure as Code (IaC) for an Application + Template. + list (ALPHA) List application templates. diff --git a/gcloud/alpha/design-center/spaces/application-templates/import-iac b/gcloud/alpha/design-center/spaces/application-templates/import-iac new file mode 100644 index 000000000..8e7cc87f7 --- /dev/null +++ b/gcloud/alpha/design-center/spaces/application-templates/import-iac @@ -0,0 +1,139 @@ +NAME + gcloud alpha design-center spaces application-templates import-iac - import + Infrastructure as Code (IaC) for an Application Template + +SYNOPSIS + gcloud alpha design-center spaces application-templates import-iac + (APPLICATION_TEMPLATE : --location=LOCATION --space=SPACE) + (--gcs-uri=GCS_URI | --iac-module-from-file=PATH_TO_FILE) + [--allow-partial-import] [--validate-iac] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Import Infrastructure as Code (IaC) for a Design Center Application + Template. + +EXAMPLES + To import IaC from a Google Cloud Storage URI into the application template + my-template in space dev-space and location us-central1, run: + + $ gcloud alpha design-center spaces application-templates \ + import-iac my-template --location=us-central1 \ + --space=dev-space --gcs-uri=gs://my-bucket/iac + + To import IaC from a local YAML file named iac_module.yaml into the + application template my-template in space dev-space and location + us-central1, run: + + $ gcloud alpha design-center spaces application-templates \ + import-iac my-template --location=us-central1 \ + --space=dev-space --iac-module-from-file=iac_module.yaml + + To import IaC from a Google Cloud Storage URI and allow partial import of + valid edits into the application template my-template, run: + + $ gcloud alpha design-center spaces application-templates \ + import-iac my-template --location=us-central1 \ + --space=dev-space --gcs-uri=gs://my-bucket/iac \ + --allow-partial-import + + To import IaC from a local YAML file and allow partial import of valid + edits into the application template my-template, run: + + $ gcloud alpha design-center spaces application-templates \ + import-iac my-template --location=us-central1 \ + --space=dev-space --iac-module-from-file=iac_module.yaml \ + --allow-partial-import + + To validate IaC from a Google Cloud Storage URI without importing into the + application template my-template, run: + + $ gcloud alpha design-center spaces application-templates \ + import-iac my-template --location=us-central1 \ + --space=dev-space --gcs-uri=gs://my-bucket/iac --validate-iac + + To validate IaC from a local YAML file without importing into the + application template my-template, run: + + $ gcloud alpha design-center spaces application-templates \ + import-iac my-template --location=us-central1 \ + --space=dev-space --iac-module-from-file=iac_module.yaml \ + --validate-iac + +POSITIONAL ARGUMENTS + Application template resource - The application template to import IaC + into IaC. 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 APPLICATION_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. + + APPLICATION_TEMPLATE + ID of the application_template or fully qualified identifier for the + application_template. + + To set the application_template_id attribute: + ▸ provide the argument APPLICATION_TEMPLATE on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the application_template. + + To set the location attribute: + ▸ provide the argument APPLICATION_TEMPLATE on the command line + with a fully specified name; + ▸ provide the argument --location on the command line. + + --space=SPACE + The ID of the space. + + To set the space attribute: + ▸ provide the argument APPLICATION_TEMPLATE on the command line + with a fully specified name; + ▸ provide the argument --space on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --gcs-uri=GCS_URI + The Cloud Storage URI of the Terraform code (e.g., + gs://my-bucket/iac). + + --iac-module-from-file=PATH_TO_FILE + Path to a local YAML or JSON file containing the IaC module + definition. Use a full or relative path to a local file containing + the value of iac_module. + +OPTIONAL FLAGS + --allow-partial-import + If set, partially import valid IaC changes and ignore invalid ones. + + --validate-iac + Validate the IaC without performing the import. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 designcenter/v1alpha API. The full documentation for + this API can be found at: + http://cloud.google.com/application-design-center/docs + +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/design-center/spaces/applications/create b/gcloud/alpha/design-center/spaces/applications/create index d07d3808e..2b078d8ef 100644 --- a/gcloud/alpha/design-center/spaces/applications/create +++ b/gcloud/alpha/design-center/spaces/applications/create @@ -5,6 +5,7 @@ NAME SYNOPSIS gcloud alpha design-center spaces applications create (APPLICATION : --location=LOCATION --space=SPACE) + --scope-type=SCOPE_TYPE (--source-application-template-revision=SOURCE_APPLICATION_TEMPLATE_REVISION | --source-shared-template-revision-uri=SOURCE_SHARED_TEMPLATE_REVISION_URI) [--app-parameters=[key=KEY],[value=VALUE]] [--component-parameters=[component=COMPONENT],[parameters=PARAMETERS]] @@ -14,8 +15,7 @@ SYNOPSIS [--deployment-project=DEPLOYMENT_PROJECT] [--deployment-region=DEPLOYMENT_REGION] [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--import-existing-resources] - [--scope-type=SCOPE_TYPE] [--service-account=SERVICE_ACCOUNT] - [--type=TYPE] + [--service-account=SERVICE_ACCOUNT] [--type=TYPE] [--attributes-business-owners=[channel=CHANNEL], [displayName=DISPLAYNAME],[email=EMAIL] --attributes-developer-owners=[channel=CHANNEL], @@ -104,6 +104,18 @@ POSITIONAL ARGUMENTS ▸ provide the argument --space on the command line. REQUIRED FLAGS + Scope of an application. + + This must be specified. + + --scope-type=SCOPE_TYPE + Scope Type. SCOPE_TYPE must be one of: + + global + Global type. + regional + Regional type. + Source template information for the deployment. This must be specified. @@ -221,16 +233,6 @@ OPTIONAL FLAGS --import-existing-resources Import existing resources into the application. - Scope of an application. - - --scope-type=SCOPE_TYPE - Scope Type. SCOPE_TYPE must be one of: - - global - Global type. - regional - Regional type. - --service-account=SERVICE_ACCOUNT Your own service account that you use to deploy an application. diff --git a/gcloud/alpha/design-center/spaces/applications/deploy b/gcloud/alpha/design-center/spaces/applications/deploy index 68f6c9862..1b1f63eb4 100644 --- a/gcloud/alpha/design-center/spaces/applications/deploy +++ b/gcloud/alpha/design-center/spaces/applications/deploy @@ -117,11 +117,12 @@ FLAGS --worker-pool=WORKER_POOL The user-specified Worker Pool resource in which the Cloud Build job - will execute, in the following format: + will execute. Format: projects/{project}/locations/{location}/workerPools/{workerPoolId} If - this field is unspecified, the default Cloud Build worker pool will be - used. If omitted and application resource ref provided has worker_pool - defined, that worker pool is used. + this flag is omitted, the worker pool already defined on the + application will be used. If no worker pool is defined on the + application, the default Cloud Build worker pool is used. The worker + pool must exist in the same region as the application. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/design-center/spaces/applications/help b/gcloud/alpha/design-center/spaces/applications/help index 1e9bb6331..1ef89cc1f 100644 --- a/gcloud/alpha/design-center/spaces/applications/help +++ b/gcloud/alpha/design-center/spaces/applications/help @@ -32,6 +32,9 @@ COMMANDS generate (ALPHA) Generate IaC for an application. + import-iac + (ALPHA) Import Infrastructure as Code (IaC) for an Application. + list (ALPHA) List applications. diff --git a/gcloud/alpha/design-center/spaces/applications/import-iac b/gcloud/alpha/design-center/spaces/applications/import-iac new file mode 100644 index 000000000..cb7da2fe7 --- /dev/null +++ b/gcloud/alpha/design-center/spaces/applications/import-iac @@ -0,0 +1,151 @@ +NAME + gcloud alpha design-center spaces applications import-iac - import + Infrastructure as Code (IaC) for an Application + +SYNOPSIS + gcloud alpha design-center spaces applications import-iac + (APPLICATION : --location=LOCATION --space=SPACE) + (--gcs-uri=GCS_URI | --iac-module-from-file=PATH_TO_FILE) + [--allow-partial-import] [--validate-iac] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Import Infrastructure as Code (IaC) for a Design Center + Application. + +EXAMPLES + To import IaC from a Google Cloud Storage URI into the application my-app + in space dev-space and location us-central1, run: + + $ gcloud alpha design-center spaces applications import-iac my-app \ + --location=us-central1 --space=dev-space \ + --gcs-uri=gs://my-bucket/iac + + To import IaC from a local YAML file named iac_module.yaml into the + application my-app in space dev-space and location us-central1, run: + + $ gcloud alpha design-center spaces applications import-iac my-app \ + --location=us-central1 --space=dev-space \ + --iac-module-from-file=iac_module.yaml + + To import IaC from a Google Cloud Storage URI into the application my-app, + allowing partial imports of valid edits, run: + + $ gcloud alpha design-center spaces applications import-iac my-app \ + --location=us-central1 --space=dev-space \ + --gcs-uri=gs://my-bucket/iac --allow-partial-import + + To import IaC from a local YAML file into the application my-app, allowing + partial imports of valid edits, run: + + $ gcloud alpha design-center spaces applications import-iac my-app \ + --location=us-central1 --space=dev-space \ + --iac-module-from-file=iac_module.yaml --allow-partial-import + + To validate IaC from a Google Cloud Storage URI for the application my-app + without importing, run: + + $ gcloud alpha design-center spaces applications import-iac my-app \ + --location=us-central1 --space=dev-space \ + --gcs-uri=gs://my-bucket/iac --validate-iac + + To validate IaC from a local YAML file for the application my-app without + importing, run: + + $ gcloud alpha design-center spaces applications import-iac my-app \ + --location=us-central1 --space=dev-space \ + --iac-module-from-file=iac_module.yaml --validate-iac + + To validate IaC from a Google Cloud Storage URI for the application my-app + and indicate that a future import should allow partial success, run: + + $ gcloud alpha design-center spaces applications import-iac my-app \ + --location=us-central1 --space=dev-space \ + --gcs-uri=gs://my-bucket/iac --validate-iac \ + --allow-partial-import + + To validate IaC from a local YAML file for the application my-app and + indicate that a future import should allow partial success, run: + + $ gcloud alpha design-center spaces applications import-iac my-app \ + --location=us-central1 --space=dev-space \ + --iac-module-from-file=iac_module.yaml --validate-iac \ + --allow-partial-import + +POSITIONAL ARGUMENTS + Application resource - The application to import IaC into IaC. 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 APPLICATION 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. + + APPLICATION + ID of the application or fully qualified identifier for the + application. + + To set the application attribute: + ▸ provide the argument APPLICATION on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the application. + + To set the location attribute: + ▸ provide the argument APPLICATION on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --space=SPACE + The ID of the space. + + To set the space attribute: + ▸ provide the argument APPLICATION on the command line with a fully + specified name; + ▸ provide the argument --space on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --gcs-uri=GCS_URI + The Cloud Storage URI of the Terraform code (e.g., + gs://my-bucket/iac). + + --iac-module-from-file=PATH_TO_FILE + Path to a local YAML or JSON file containing the IaC module + definition. Use a full or relative path to a local file containing + the value of iac_module. + +OPTIONAL FLAGS + --allow-partial-import + If set, partially import valid IaC changes and ignore invalid ones. + + --validate-iac + Validate the IaC without performing the import. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 designcenter/v1alpha API. The full documentation for + this API can be found at: + http://cloud.google.com/application-design-center/docs + +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/design-center/spaces/applications/preview b/gcloud/alpha/design-center/spaces/applications/preview index b4ff4967e..ce3b4154d 100644 --- a/gcloud/alpha/design-center/spaces/applications/preview +++ b/gcloud/alpha/design-center/spaces/applications/preview @@ -106,11 +106,12 @@ FLAGS --worker-pool=WORKER_POOL The user-specified Worker Pool resource in which the Cloud Build job - will execute. Format + will execute. Format: projects/{project}/locations/{location}/workerPools/{workerPoolId} If - this field is unspecified, the default Cloud Build worker pool will be - used. If omitted and application resource ref provided has worker_pool - defined, that worker pool is used. + this flag is omitted, the worker pool already defined on the + application will be used. If no worker pool is defined on the + application, the default Cloud Build worker pool is used. The worker + pool must exist in the same region as the application. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/design-center/spaces/catalogs/templates/create b/gcloud/alpha/design-center/spaces/catalogs/templates/create index f3518050a..d4ab94fbc 100644 --- a/gcloud/alpha/design-center/spaces/catalogs/templates/create +++ b/gcloud/alpha/design-center/spaces/catalogs/templates/create @@ -94,12 +94,14 @@ REQUIRED FLAGS The category of the ADC template. TEMPLATE_CATEGORY must be one of: application-template - ADC application. + ADC application template. component-template - ADC component. + ADC component template. composite-solution-template Imported as a single, complex unit without disassembling into components. + instance-template + ADC application instance. OPTIONAL FLAGS --description=DESCRIPTION @@ -118,14 +120,20 @@ OPTIONAL FLAGS asset An asset template can be used to provision resources that are not services or workloads. + composite-application-template + A composite application template. helm-application A helm chart based template. + helm-chart + A helm chart based template. jss-solution A Jumpstart Solution template. service A service template is an App Hub service. service-data-source A service data source template. + standard-application-template + A standard application template. workload A workload template is an App Hub workload. diff --git a/gcloud/alpha/design-center/spaces/catalogs/templates/update b/gcloud/alpha/design-center/spaces/catalogs/templates/update index 1f44df9ca..6502b7f7b 100644 --- a/gcloud/alpha/design-center/spaces/catalogs/templates/update +++ b/gcloud/alpha/design-center/spaces/catalogs/templates/update @@ -82,12 +82,14 @@ FLAGS The category of the ADC template. TEMPLATE_CATEGORY must be one of: application-template - ADC application. + ADC application template. component-template - ADC component. + ADC component template. composite-solution-template Imported as a single, complex unit without disassembling into components. + instance-template + ADC application instance. --type=TYPE The Application Design Center assembly template type. TYPE must be one @@ -99,14 +101,20 @@ FLAGS asset An asset template can be used to provision resources that are not services or workloads. + composite-application-template + A composite application template. helm-application A helm chart based template. + helm-chart + A helm chart based template. jss-solution A Jumpstart Solution template. service A service template is an App Hub service. service-data-source A service data source template. + standard-application-template + A standard application template. workload A workload template is an App Hub workload. diff --git a/gcloud/alpha/design-center/spaces/create b/gcloud/alpha/design-center/spaces/create index 8c7785b84..8abbb1528 100644 --- a/gcloud/alpha/design-center/spaces/create +++ b/gcloud/alpha/design-center/spaces/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud alpha design-center spaces create (SPACE : --location=LOCATION) [--description=DESCRIPTION] [--display-name=DISPLAY_NAME] [--enable-gcp-shared-templates] [--gcs-bucket=GCS_BUCKET] - [GCLOUD_WIDE_FLAG ...] + [--tags=[TAGS,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a space. @@ -84,6 +84,30 @@ FLAGS Cloud Storage bucket URI is gs:\/\/{$bucket_name}, the format is {$bucket_name}. + --tags=[TAGS,...] + Tags are key/values bound to space resource. Example: + "123/environment": "production" "123/costCenter": "marketing". For more + information on tag creation and management, see + https://cloud.google.com/resource-manager/docs/tags/tags-overview. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --tags=string=string + + JSON Example: + + --tags='{"string": "string"}' + + File Example: + + --tags=path_to_file.(yaml|json) + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/design-center/spaces/help b/gcloud/alpha/design-center/spaces/help index c4cc33a60..8ea005d4c 100644 --- a/gcloud/alpha/design-center/spaces/help +++ b/gcloud/alpha/design-center/spaces/help @@ -43,7 +43,7 @@ COMMANDS (ALPHA) Get the IAM policy for a Design Center space. infer-connections - (ALPHA) Infer connections for components in a space. + (ALPHA) Infer connections for a space. list (ALPHA) List spaces. diff --git a/gcloud/alpha/design-center/spaces/infer-connections b/gcloud/alpha/design-center/spaces/infer-connections index 942fb4f69..d628fb1c8 100644 --- a/gcloud/alpha/design-center/spaces/infer-connections +++ b/gcloud/alpha/design-center/spaces/infer-connections @@ -1,108 +1,91 @@ NAME gcloud alpha design-center spaces infer-connections - infer connections for - components in a space + a space SYNOPSIS - gcloud alpha design-center spaces infer-connections [--async] - [--location=LOCATION] [--space=SPACE] [--use-gemini] - [--catalog-template-revision-uris=[CATALOG_TEMPLATE_REVISION_URIS,...] - : --catalog=CATALOG --template=TEMPLATE] [GCLOUD_WIDE_FLAG ...] + gcloud alpha design-center spaces infer-connections + (SPACE : --location=LOCATION) [--async] + [--catalog-template-revision-uris=[CATALOG_TEMPLATE_REVISION_URI,...]] + [--use-gemini] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Infers connections for components present in a space. + (ALPHA) Infers connections for catalog and shared template revisions within + a space. If no URIs are provided, it processes all templates in the space, + but may fail if a shared template is unexpectedly missing. EXAMPLES - To infer connections for space my-space in project my-project and location - us-central1, run: + To infer connections for a space named my-space in location us-central1 and + project my-project, run: $ gcloud alpha design-center spaces infer-connections my-space \ --project=my-project --location=us-central1 - To infer connections for space my-space in project my-project and location - us-central1 using gemini, run: + To infer connections for a space named my-space in location us-central1 and + project my-project, with specific catalog template revision URIs and using + Gemini, run: - $ gcloud alpha design-center spaces infer-connections my-space \ - --project=my-project --location=us-central1 --use-gemini - - To infer connections for specific catalog template revisions rev1 and rev2 - in space my-space in project my-project and location us-central1, run: - - $ gcloud alpha design-center spaces infer-connections my-space \ + $ gcloud alpha design-center spaces infer-connections platform \ --project=my-project --location=us-central1 \ --catalog-template-revision-uris=projects/my-project/locations/\ - us-central1/spaces/my-space/catalogs/my-catalog/templates/\ - my-template/revisions/rev1,projects/my-project/locations/\ - us-central1/spaces/my-space/catalogs/my-catalog/templates/\ - my-template/revisions/rev2 + us-central1/spaces/security/catalogs/security/templates/\ + certificate-authority/revisions/rev1,projects/my-project/locations/\ + us-central1/spaces/security/catalogs/security/templates/\ + certificate-authority/revisions/rev2 --use-gemini + + To infer connections for a space using the full resource name, run: + + $ gcloud alpha design-center spaces infer-connections \ + projects/cloud-appcenter-e2e-testing/locations/us-central1/\ + spaces/platform \ + --catalog-template-revision-uris=projects/\ + cloud-appcenter-e2e-testing/locations/us-central1/spaces/security/\ + catalogs/security/templates/certificate-authority/revisions/rev1 \ + --use-gemini + +POSITIONAL ARGUMENTS + Space resource - The space ID. 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 space 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. + + SPACE + ID of the space or fully qualified identifier for the space. + + To set the space attribute: + ▸ provide the argument space on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The Cloud location for the space. + + To set the location attribute: + ▸ provide the argument space 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. - --location=LOCATION - For resources [space, catalog-template-revision-uris], provides - fallback value for resource location attribute. When the resource's - full URI path is not provided, location will fallback to this flag - value. - - --space=SPACE - For resources [space, catalog-template-revision-uris], provides - fallback value for resource space attribute. When the resource's full - URI path is not provided, space will fallback to this flag value. + --catalog-template-revision-uris=[CATALOG_TEMPLATE_REVISION_URI,...] + A comma-separated list of catalog template revision URIs to infer + connections for. If not provided, the system infers connections for the + latest revisions of all catalog templates in all the catalogs present + in the space. Format: + projects/{projectId}/locations/{locationId}/spaces/{spaceId}/catalogs/{catalogId}/templates/{templateId}/revisions/{revisionId} --use-gemini - Whether to use Gemini. - - Revision resource - A list of Catalog template revisions that you want to - infer connections for. If you don't provide this, the system infers - connections for the latest revisions of all catalog templates in all the - catalogs present in the space. 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 --catalog-template-revision-uris 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 --catalog-template-revision-uris on the command - line with a fully specified name; - ◆ provide the argument --location on the command line. - - To set the space attribute: - ◆ provide the argument --catalog-template-revision-uris on the command - line with a fully specified name; - ◆ provide the argument --space on the command line. - - --catalog-template-revision-uris=[CATALOG_TEMPLATE_REVISION_URIS,...] - IDs of the revisions or fully qualified identifiers for the - revisions. - - To set the revision attribute: - ▸ provide the argument --catalog-template-revision-uris on the - command line. - - This flag argument must be specified if any of the other arguments in - this group are specified. - - --catalog=CATALOG - The catalog id of the revisions resource. - - To set the catalog attribute: - ▸ provide the argument --catalog-template-revision-uris on the - command line with a fully specified name; - ▸ provide the argument --catalog on the command line. - - --template=TEMPLATE - The template id of the revisions resource. - - To set the template attribute: - ▸ provide the argument --catalog-template-revision-uris on the - command line with a fully specified name; - ▸ provide the argument --template on the command line. + Use Gemini to infer connections. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/emulators/spanner/help b/gcloud/alpha/emulators/spanner/help index 45a4fe416..dc2acb41a 100644 --- a/gcloud/alpha/emulators/spanner/help +++ b/gcloud/alpha/emulators/spanner/help @@ -25,6 +25,9 @@ COMMANDS (ALPHA) Print the commands required to export Spanner emulator's env variables. + notices + (ALPHA) Print third-party notices for the local Cloud Spanner emulator. + start (ALPHA) Start a local Cloud Spanner emulator. diff --git a/gcloud/alpha/emulators/spanner/notices b/gcloud/alpha/emulators/spanner/notices new file mode 100644 index 000000000..69f20dfa1 --- /dev/null +++ b/gcloud/alpha/emulators/spanner/notices @@ -0,0 +1,41 @@ +NAME + gcloud alpha emulators spanner notices - print third-party notices for the + local Cloud Spanner emulator + +SYNOPSIS + gcloud alpha emulators spanner notices [--use-docker] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Print third-party notices for the local Cloud Spanner emulator. + +EXAMPLES + To print third-party notices for the local Cloud Spanner emulator, run: + + $ gcloud alpha emulators spanner notices + +FLAGS + --use-docker + Use the Cloud Spanner emulator docker image even if the platform has a + native binary available in the gcloud CLI. Currently we only provide a + native binary for Linux. For other systems, you must install Docker for + your platform before starting the emulator. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud emulators spanner notices + + $ gcloud beta emulators spanner notices + diff --git a/gcloud/alpha/firestore/databases/clone b/gcloud/alpha/firestore/databases/clone index 8c0b9550a..9a711da3c 100644 --- a/gcloud/alpha/firestore/databases/clone +++ b/gcloud/alpha/firestore/databases/clone @@ -134,5 +134,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud firestore databases clone + + $ gcloud beta firestore databases clone diff --git a/gcloud/alpha/iam/workforce-pools/providers/keys/create b/gcloud/alpha/iam/workforce-pools/providers/keys/create index 960ce112a..7887118e1 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/keys/create +++ b/gcloud/alpha/iam/workforce-pools/providers/keys/create @@ -76,7 +76,7 @@ REQUIRED FLAGS --use=USE The purpose of the key. USE must be one of: encryption, - key-use-unspecified. + key-use-unspecified, signing. OPTIONAL FLAGS --async diff --git a/gcloud/alpha/looker/instances/update b/gcloud/alpha/looker/instances/update index 22d96ca3d..1bbdbbf2d 100644 --- a/gcloud/alpha/looker/instances/update +++ b/gcloud/alpha/looker/instances/update @@ -20,6 +20,8 @@ SYNOPSIS [domain=DOMAIN],[multiple-domains=MULTIPLE-DOMAINS]] [--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] + [--egress-enabled + --egress-fqdns=[EGRESS_FQDNS,...] --marketplace-enabled] [--gemini-enabled --gemini-preview-tester-enabled --gemini-prompt-log-enabled] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY @@ -205,6 +207,24 @@ FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + Controlled Egress - Controlled egress allows you to egress data from a + Looker (Google Cloud core) instance to a third party service provider. + + --egress-enabled + This specifies whether controlled egress is enabled on the Looker + instance. To disable controlled egress, use the --no-egress-enabled + flag. + + --egress-fqdns=[EGRESS_FQDNS,...] + List of FQDNs that are allowed to egress from the Looker instance. + Example: --egress-fqdns="github.com,my.salesforce.com". To clear all + egress FQDNs, use --egress-fqdns="". + + --marketplace-enabled + This specifies whether marketplace is enabled for controlled egress + on the Looker instance. To disable marketplace for controlled egress, + use the --no-marketplace-enabled flag. + Gemini AI - Gemini AI is a powerful AI model that can be used to answer questions, generate content, and perform a variety of other tasks. diff --git a/gcloud/alpha/lustre/instances/create b/gcloud/alpha/lustre/instances/create index bd9c7bd1f..4f95e6a14 100644 --- a/gcloud/alpha/lustre/instances/create +++ b/gcloud/alpha/lustre/instances/create @@ -5,9 +5,16 @@ SYNOPSIS gcloud alpha lustre instances create (INSTANCE : --location=LOCATION) --capacity-gib=CAPACITY_GIB --filesystem=FILESYSTEM --network=NETWORK --per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT [--async] - [--description=DESCRIPTION] [--gke-support-enabled] - [--labels=[LABELS,...]] [--request-id=REQUEST_ID] - [GCLOUD_WIDE_FLAG ...] + [--description=DESCRIPTION] [--gke-support-enabled] [--kms-key=KMS_KEY] + [--labels=[LABELS,...]] [--placement-policy=PLACEMENT_POLICY] + [--request-id=REQUEST_ID] + [[--default-squash-mode=DEFAULT_SQUASH_MODE + : --access-rules=[accessMode=ACCESSMODE], + [ipAddressRanges=IPADDRESSRANGES], + [mountableSubdirectories=MOUNTABLESUBDIRECTORIES],[name=NAME], + [squashGid=SQUASHGID],[squashMode=SQUASHMODE],[squashUid=SQUASHUID] + --default-squash-gid=DEFAULT_SQUASH_GID + --default-squash-uid=DEFAULT_SQUASH_UID]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a Managed Lustre instance. @@ -105,6 +112,13 @@ OPTIONAL FLAGS default, GKE clients are not supported. Deprecated. No longer required for GKE instance creation. + --kms-key=KMS_KEY + The Cloud KMS key name to use for data encryption. If not set, the + instance will use Google-managed encryption keys. If set, the instance + will use customer-managed encryption keys. The key must be in the same + region as the instance. The key format is: + projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{key} + --labels=[LABELS,...] Labels as key value pairs. @@ -128,6 +142,10 @@ OPTIONAL FLAGS --labels=path_to_file.(yaml|json) + --placement-policy=PLACEMENT_POLICY + The placement policy name for the instance in the format of + projects/{project}/locations/{location}/resourcePolicies/{resource_policy} + --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 @@ -143,6 +161,113 @@ OPTIONAL FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). + IP-based access rules for the Managed Lustre instance. These options + define the root user squash configuration. + + --default-squash-mode=DEFAULT_SQUASH_MODE + The squash mode for the default access rule. DEFAULT_SQUASH_MODE must + be one of: + + no-squash + Squash is disabled. + + If set inside an + [AccessRule][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule], + root users matching the [ip_ranges][AccessRule.ip_ranges] are not + squashed. + + If set as the + [default_squash_mode][google.cloud.lustre.v1alpha.AccessRulesOptions.default_squash_mode], + root squash is disabled for this instance. + + If the default squash mode is NO_SQUASH, do not set the + [default_squash_uid][google.cloud.lustre.v1alpha.AccessRulesOptions.default_squash_uid] + or + [default_squash_gid][google.cloud.lustre.v1alpha.AccessRulesOptions.default_squash_gid], + or an invalid argument error is returned. + root-squash + Root user squash is enabled. + + Not supported inside an + [AccessRule][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule]. + + If set as the + [default_squash_mode][google.cloud.lustre.v1alpha.AccessRulesOptions.default_squash_mode], + root users not matching any of the + [access_rules][google.cloud.lustre.v1alpha.AccessRulesOptions.access_rules] + are squashed to the + [default_squash_uid][google.cloud.lustre.v1alpha.AccessRulesOptions.default_squash_uid] + and + [default_squash_gid][google.cloud.lustre.v1alpha.AccessRulesOptions.default_squash_gid]. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --access-rules=[accessMode=ACCESSMODE],[ipAddressRanges=IPADDRESSRANGES],[mountableSubdirectories=MOUNTABLESUBDIRECTORIES],[name=NAME],[squashGid=SQUASHGID],[squashMode=SQUASHMODE],[squashUid=SQUASHUID] + The access rules for the instance. + + accessMode + The access mode for the access rule nodemap. Default is + [READ_WRITE][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule.AccessMode.READ_WRITE]. + + ipAddressRanges + The IP address ranges to which to apply this access rule. Accepts + non-overlapping CIDR ranges (e.g., 192.168.1.0/24) and IP + addresses (e.g., 192.168.1.0). + + mountableSubdirectories + The list of non-root directories that can be mounted from clients + in this NID range subset. Currently, there can be only a single + directory at most. If no directory is mentioned, then the root + directory will be accessible. + + name + The name of the access rule policy group. Must be 16 characters + or less and include only alphanumeric characters or ''. + + squashGid + Squash GID for the access rule. If the squash mode for this rule + is + [ROOT_SQUASH][google.cloud.lustre.v1alpha.AccessRulesOptions.SquashMode.ROOT_SQUASH], + root users matching the + [ip_address_ranges][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule.ip_address_ranges] + are squashed to this GID. Defaults to 0 (no root squash). + + squashMode + Squash mode for the access rule. + + squashUid + Squash UID for the access rule. If the squash mode for this rule + is + [ROOT_SQUASH][google.cloud.lustre.v1alpha.AccessRulesOptions.SquashMode.ROOT_SQUASH], + root users matching the + [ip_address_ranges][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule.ip_address_ranges] + are squashed to this UID. Defaults to 0 (no root squash). + + Shorthand Example: + + --access-rules=accessMode=string,ipAddressRanges=[string],mountableSubdirectories=[string],name=string,squashGid=int,squashMode=string,squashUid=int --access-rules=accessMode=string,ipAddressRanges=[string],mountableSubdirectories=[string],name=string,squashGid=int,squashMode=string,squashUid=int + + JSON Example: + + --access-rules='[{"accessMode": "string", "ipAddressRanges": ["string"], "mountableSubdirectories": ["string"], "name": "string", "squashGid": int, "squashMode": "string", "squashUid": int}]' + + File Example: + + --access-rules=path_to_file.(yaml|json) + + --default-squash-gid=DEFAULT_SQUASH_GID + The user squash GID for the default access rule. This user squash GID + applies to all root users connecting from clients that are not + matched by any of the access rules. If not set, the default is 0 (no + GID squash). + + --default-squash-uid=DEFAULT_SQUASH_UID + The user squash UID for the default access rule. This user squash UID + applies to all root users connecting from clients that are not + matched by any of the access rules. If not set, the default is 0 (no + UID squash). + 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/lustre/instances/update b/gcloud/alpha/lustre/instances/update index e36636ed1..6ba679559 100644 --- a/gcloud/alpha/lustre/instances/update +++ b/gcloud/alpha/lustre/instances/update @@ -7,7 +7,23 @@ SYNOPSIS [--async] [--capacity-gib=CAPACITY_GIB] [--description=DESCRIPTION] [--[no-]gke-support-enabled] [--per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT] - [--request-id=REQUEST_ID] + [--placement-policy=PLACEMENT_POLICY] [--request-id=REQUEST_ID] + [--clear- --default-squash-gid=DEFAULT_SQUASH_GID + --default-squash-mode=DEFAULT_SQUASH_MODE + --default-squash-uid=DEFAULT_SQUASH_UID + --access-rules=[accessMode=ACCESSMODE], + [ipAddressRanges=IPADDRESSRANGES], + [mountableSubdirectories=MOUNTABLESUBDIRECTORIES],[name=NAME], + [squashGid=SQUASHGID],[squashMode=SQUASHMODE],[squashUid=SQUASHUID] + | --add-access-rules=[accessMode=ACCESSMODE], + [ipAddressRanges=IPADDRESSRANGES], + [mountableSubdirectories=MOUNTABLESUBDIRECTORIES],[name=NAME], + [squashGid=SQUASHGID],[squashMode=SQUASHMODE],[squashUid=SQUASHUID] + --clear-access-rules + | --remove-access-rules=[accessMode=ACCESSMODE], + [ipAddressRanges=IPADDRESSRANGES], + [mountableSubdirectories=MOUNTABLESUBDIRECTORIES],[name=NAME], + [squashGid=SQUASHGID],[squashMode=SQUASHMODE],[squashUid=SQUASHUID]] [--labels=[LABELS,...] | --update-labels=[UPDATE_LABELS,...] --clear-labels | --remove-labels=REMOVE_LABELS] [GCLOUD_WIDE_FLAG ...] @@ -81,6 +97,10 @@ FLAGS (https://cloud.google.com/managed-lustre/docs/create-instance#performance-tiers) for more information. + --placement-policy=PLACEMENT_POLICY + The placement policy name for the instance in the format of + projects/{project}/locations/{location}/resourcePolicies/{resource_policy} + --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 @@ -96,6 +116,231 @@ FLAGS The request ID must be a valid UUID with the exception that zero UUID is not supported (00000000-0000-0000-0000-000000000000). + IP-based access rules for the Managed Lustre instance. These options + define the root user squash configuration. + + --clear- + Set instance.accessRulesOptions back to default value. + + --default-squash-gid=DEFAULT_SQUASH_GID + The user squash GID for the default access rule. This user squash GID + applies to all root users connecting from clients that are not + matched by any of the access rules. If not set, the default is 0 (no + GID squash). + + --default-squash-mode=DEFAULT_SQUASH_MODE + The squash mode for the default access rule. DEFAULT_SQUASH_MODE must + be one of: + + no-squash + Squash is disabled. + + If set inside an + [AccessRule][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule], + root users matching the [ip_ranges][AccessRule.ip_ranges] are not + squashed. + + If set as the + [default_squash_mode][google.cloud.lustre.v1alpha.AccessRulesOptions.default_squash_mode], + root squash is disabled for this instance. + + If the default squash mode is NO_SQUASH, do not set the + [default_squash_uid][google.cloud.lustre.v1alpha.AccessRulesOptions.default_squash_uid] + or + [default_squash_gid][google.cloud.lustre.v1alpha.AccessRulesOptions.default_squash_gid], + or an invalid argument error is returned. + root-squash + Root user squash is enabled. + + Not supported inside an + [AccessRule][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule]. + + If set as the + [default_squash_mode][google.cloud.lustre.v1alpha.AccessRulesOptions.default_squash_mode], + root users not matching any of the + [access_rules][google.cloud.lustre.v1alpha.AccessRulesOptions.access_rules] + are squashed to the + [default_squash_uid][google.cloud.lustre.v1alpha.AccessRulesOptions.default_squash_uid] + and + [default_squash_gid][google.cloud.lustre.v1alpha.AccessRulesOptions.default_squash_gid]. + + --default-squash-uid=DEFAULT_SQUASH_UID + The user squash UID for the default access rule. This user squash UID + applies to all root users connecting from clients that are not + matched by any of the access rules. If not set, the default is 0 (no + UID squash). + + Update access_rules. + + At most one of these can be specified: + + --access-rules=[accessMode=ACCESSMODE],[ipAddressRanges=IPADDRESSRANGES],[mountableSubdirectories=MOUNTABLESUBDIRECTORIES],[name=NAME],[squashGid=SQUASHGID],[squashMode=SQUASHMODE],[squashUid=SQUASHUID] + Set access_rules to new value. The access rules for the instance. + + accessMode + The access mode for the access rule nodemap. Default is + [READ_WRITE][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule.AccessMode.READ_WRITE]. + + ipAddressRanges + The IP address ranges to which to apply this access rule. + Accepts non-overlapping CIDR ranges (e.g., 192.168.1.0/24) and + IP addresses (e.g., 192.168.1.0). + + mountableSubdirectories + The list of non-root directories that can be mounted from + clients in this NID range subset. Currently, there can be only + a single directory at most. If no directory is mentioned, then + the root directory will be accessible. + + name + The name of the access rule policy group. Must be 16 characters + or less and include only alphanumeric characters or ''. + + squashGid + Squash GID for the access rule. If the squash mode for this + rule is + [ROOT_SQUASH][google.cloud.lustre.v1alpha.AccessRulesOptions.SquashMode.ROOT_SQUASH], + root users matching the + [ip_address_ranges][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule.ip_address_ranges] + are squashed to this GID. Defaults to 0 (no root squash). + + squashMode + Squash mode for the access rule. + + squashUid + Squash UID for the access rule. If the squash mode for this + rule is + [ROOT_SQUASH][google.cloud.lustre.v1alpha.AccessRulesOptions.SquashMode.ROOT_SQUASH], + root users matching the + [ip_address_ranges][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule.ip_address_ranges] + are squashed to this UID. Defaults to 0 (no root squash). + + Shorthand Example: + + --access-rules=accessMode=string,ipAddressRanges=[string],mountableSubdirectories=[string],name=string,squashGid=int,squashMode=string,squashUid=int --access-rules=accessMode=string,ipAddressRanges=[string],mountableSubdirectories=[string],name=string,squashGid=int,squashMode=string,squashUid=int + + JSON Example: + + --access-rules='[{"accessMode": "string", "ipAddressRanges": ["string"], "mountableSubdirectories": ["string"], "name": "string", "squashGid": int, "squashMode": "string", "squashUid": int}]' + + File Example: + + --access-rules=path_to_file.(yaml|json) + + --add-access-rules=[accessMode=ACCESSMODE],[ipAddressRanges=IPADDRESSRANGES],[mountableSubdirectories=MOUNTABLESUBDIRECTORIES],[name=NAME],[squashGid=SQUASHGID],[squashMode=SQUASHMODE],[squashUid=SQUASHUID] + Add new value to access_rules list. The access rules for the + instance. + + accessMode + The access mode for the access rule nodemap. Default is + [READ_WRITE][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule.AccessMode.READ_WRITE]. + + ipAddressRanges + The IP address ranges to which to apply this access rule. + Accepts non-overlapping CIDR ranges (e.g., 192.168.1.0/24) and + IP addresses (e.g., 192.168.1.0). + + mountableSubdirectories + The list of non-root directories that can be mounted from + clients in this NID range subset. Currently, there can be only + a single directory at most. If no directory is mentioned, then + the root directory will be accessible. + + name + The name of the access rule policy group. Must be 16 characters + or less and include only alphanumeric characters or ''. + + squashGid + Squash GID for the access rule. If the squash mode for this + rule is + [ROOT_SQUASH][google.cloud.lustre.v1alpha.AccessRulesOptions.SquashMode.ROOT_SQUASH], + root users matching the + [ip_address_ranges][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule.ip_address_ranges] + are squashed to this GID. Defaults to 0 (no root squash). + + squashMode + Squash mode for the access rule. + + squashUid + Squash UID for the access rule. If the squash mode for this + rule is + [ROOT_SQUASH][google.cloud.lustre.v1alpha.AccessRulesOptions.SquashMode.ROOT_SQUASH], + root users matching the + [ip_address_ranges][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule.ip_address_ranges] + are squashed to this UID. Defaults to 0 (no root squash). + + Shorthand Example: + + --add-access-rules=accessMode=string,ipAddressRanges=[string],mountableSubdirectories=[string],name=string,squashGid=int,squashMode=string,squashUid=int --add-access-rules=accessMode=string,ipAddressRanges=[string],mountableSubdirectories=[string],name=string,squashGid=int,squashMode=string,squashUid=int + + JSON Example: + + --add-access-rules='[{"accessMode": "string", "ipAddressRanges": ["string"], "mountableSubdirectories": ["string"], "name": "string", "squashGid": int, "squashMode": "string", "squashUid": int}]' + + File Example: + + --add-access-rules=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-access-rules + Clear access_rules value and set to empty list. + + --remove-access-rules=[accessMode=ACCESSMODE],[ipAddressRanges=IPADDRESSRANGES],[mountableSubdirectories=MOUNTABLESUBDIRECTORIES],[name=NAME],[squashGid=SQUASHGID],[squashMode=SQUASHMODE],[squashUid=SQUASHUID] + Remove existing value from access_rules list. The access rules + for the instance. + + accessMode + The access mode for the access rule nodemap. Default is + [READ_WRITE][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule.AccessMode.READ_WRITE]. + + ipAddressRanges + The IP address ranges to which to apply this access rule. + Accepts non-overlapping CIDR ranges (e.g., 192.168.1.0/24) + and IP addresses (e.g., 192.168.1.0). + + mountableSubdirectories + The list of non-root directories that can be mounted from + clients in this NID range subset. Currently, there can be + only a single directory at most. If no directory is + mentioned, then the root directory will be accessible. + + name + The name of the access rule policy group. Must be 16 + characters or less and include only alphanumeric characters + or ''. + + squashGid + Squash GID for the access rule. If the squash mode for this + rule is + [ROOT_SQUASH][google.cloud.lustre.v1alpha.AccessRulesOptions.SquashMode.ROOT_SQUASH], + root users matching the + [ip_address_ranges][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule.ip_address_ranges] + are squashed to this GID. Defaults to 0 (no root squash). + + squashMode + Squash mode for the access rule. + + squashUid + Squash UID for the access rule. If the squash mode for this + rule is + [ROOT_SQUASH][google.cloud.lustre.v1alpha.AccessRulesOptions.SquashMode.ROOT_SQUASH], + root users matching the + [ip_address_ranges][google.cloud.lustre.v1alpha.AccessRulesOptions.AccessRule.ip_address_ranges] + are squashed to this UID. Defaults to 0 (no root squash). + + Shorthand Example: + + --remove-access-rules=accessMode=string,ipAddressRanges=[string],mountableSubdirectories=[string],name=string,squashGid=int,squashMode=string,squashUid=int --remove-access-rules=accessMode=string,ipAddressRanges=[string],mountableSubdirectories=[string],name=string,squashGid=int,squashMode=string,squashUid=int + + JSON Example: + + --remove-access-rules='[{"accessMode": "string", "ipAddressRanges": ["string"], "mountableSubdirectories": ["string"], "name": "string", "squashGid": int, "squashMode": "string", "squashUid": int}]' + + File Example: + + --remove-access-rules=path_to_file.(yaml|json) + Update labels. At most one of these can be specified: diff --git a/gcloud/alpha/managed-kafka/clusters/create b/gcloud/alpha/managed-kafka/clusters/create index 547a44f63..fb748d42a 100644 --- a/gcloud/alpha/managed-kafka/clusters/create +++ b/gcloud/alpha/managed-kafka/clusters/create @@ -5,8 +5,9 @@ NAME SYNOPSIS gcloud alpha managed-kafka clusters create (CLUSTER : --location=LOCATION) --cpu=CPU --memory=MEMORY --subnets=[SUBNETS,...] [--async] - [--no-auto-rebalance] [--encryption-key=ENCRYPTION_KEY] - [--labels=[KEY=VALUE,...]] [--mtls-ca-pools=[MTLS_CA_POOLS,...]] + [--no-auto-rebalance] [--broker-disk-size-gb=BROKER_DISK_SIZE_GB] + [--encryption-key=ENCRYPTION_KEY] [--labels=[KEY=VALUE,...]] + [--mtls-ca-pools=[MTLS_CA_POOLS,...]] [--ssl-principal-mapping-rules=SSL_PRINCIPAL_MAPPING_RULES] [GCLOUD_WIDE_FLAG ...] @@ -85,6 +86,10 @@ OPTIONAL FLAGS by default. Use --no-auto-rebalance to disable this flag. Enabled by default, use --no-auto-rebalance to disable. + --broker-disk-size-gb=BROKER_DISK_SIZE_GB + The amount of local disk to provision for each broker in Gigabytes. + Minimum: 100 GB. + --encryption-key=ENCRYPTION_KEY The relative resource path of the Cloud KMS key to use for encryption in the form: diff --git a/gcloud/alpha/managed-kafka/clusters/update b/gcloud/alpha/managed-kafka/clusters/update index 65bfa6737..f4d8d231f 100644 --- a/gcloud/alpha/managed-kafka/clusters/update +++ b/gcloud/alpha/managed-kafka/clusters/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha managed-kafka clusters update (CLUSTER : --location=LOCATION) - (--auto-rebalance --cpu=CPU --labels=[KEY=VALUE,...] --memory=MEMORY + (--auto-rebalance --broker-disk-size-gb=BROKER_DISK_SIZE_GB --cpu=CPU + --labels=[KEY=VALUE,...] --memory=MEMORY --ssl-principal-mapping-rules=SSL_PRINCIPAL_MAPPING_RULES --subnets=[SUBNETS,...] --clear-mtls-ca-pools | --mtls-ca-pools=[MTLS_CA_POOLS,...]) @@ -64,6 +65,10 @@ REQUIRED FLAGS when the number of CPUs in the cluster changes. Automatic rebalancing is enabled by default. Use --no-auto-rebalance to disable this flag. + --broker-disk-size-gb=BROKER_DISK_SIZE_GB + The amount of local disk to provision for each broker in Gigabytes. + Minimum: 100 GB. + --cpu=CPU The number of vCPUs to provision for the cluster. The minimum is 3. diff --git a/gcloud/alpha/model-armor/floorsettings/update b/gcloud/alpha/model-armor/floorsettings/update index d1e0ef032..c0e24764c 100644 --- a/gcloud/alpha/model-armor/floorsettings/update +++ b/gcloud/alpha/model-armor/floorsettings/update @@ -5,7 +5,11 @@ NAME SYNOPSIS gcloud alpha model-armor floorsettings update --full-uri=FULL_URI [--enable-floor-setting-enforcement=ENABLE_FLOOR_SETTING_ENFORCEMENT] + [--[no-]enable-multi-language-detection] [--malicious-uri-filter-settings-enforcement=MALICIOUS_URI_FILTER_SETTINGS_ENFORCEMENT] + [--add-integrated-services=[INTEGRATED_SERVICE,...] + | --clear-integrated-services + | --remove-integrated-services=[INTEGRATED_SERVICE,...]] [--add-rai-settings-filters=confidenceLevel=CONFIDENCELEVEL], [filterType=FILTERTYPE] | --clear-rai-settings-filters | --rai-settings-filters=confidenceLevel=CONFIDENCELEVEL], @@ -13,6 +17,10 @@ SYNOPSIS | --remove-rai-settings-filters=confidenceLevel=CONFIDENCELEVEL], [filterType=FILTERTYPE]] [--advanced-config-deidentify-template=ADVANCED_CONFIG_DEIDENTIFY_TEMPLATE --advanced-config-inspect-template=ADVANCED_CONFIG_INSPECT_TEMPLATE --basic-config-filter-enforcement=BASIC_CONFIG_FILTER_ENFORCEMENT] + [--[no-]enable-google-mcp-server-cloud-logging + --google-mcp-server-enforcement-type=GOOGLE_MCP_SERVER_ENFORCEMENT_TYPE] + [--[no-]enable-vertex-ai-cloud-logging + --vertex-ai-enforcement-type=VERTEX_AI_ENFORCEMENT_TYPE] [--pi-and-jailbreak-filter-settings-confidence-level=PI_AND_JAILBREAK_FILTER_SETTINGS_CONFIDENCE_LEVEL --pi-and-jailbreak-filter-settings-enforcement=PI_AND_JAILBREAK_FILTER_SETTINGS_ENFORCEMENT] [GCLOUD_WIDE_FLAG ...] @@ -27,11 +35,35 @@ OPTIONAL FLAGS --enable-floor-setting-enforcement=ENABLE_FLOOR_SETTING_ENFORCEMENT Enable or disable the floor setting enforcement + Multi language detection enablement. + + --[no-]enable-multi-language-detection + Enable multi-language detection for floor setting, allowing Model + Armor to process content in multiple languages. Use + --enable-multi-language-detection to enable and + --no-enable-multi-language-detection to disable. + Malicious uri filter settings. --malicious-uri-filter-settings-enforcement=MALICIOUS_URI_FILTER_SETTINGS_ENFORCEMENT Malicious URI filter settings. + Manage integrated services to apply Model Armor floor settings. Integrated + services will have Model Armor sanitization enabled project-wide. + + At most one of these can be specified: + + --add-integrated-services=[INTEGRATED_SERVICE,...] + Set the list of integrated services for the floor setting. This can + be used to enable project-wide Model Armor sanitization for the + respective services. + + --clear-integrated-services + Clear all integrated services from the floor setting. + + --remove-integrated-services=[INTEGRATED_SERVICE,...] + Remove specified service(s) from the list of integrated services. + RAI filter settings. At most one of these can be specified: @@ -99,6 +131,30 @@ OPTIONAL FLAGS The sdp filter settings enforcement. The value can be either "ENABLED" or "DISABLED" + Options for Google MCP server sanitization. + + --[no-]enable-google-mcp-server-cloud-logging + Enable Cloud Logging for Google MCP server sanitization to log Model + Armor sanitization results. Use + --enable-google-mcp-server-cloud-logging to enable and + --no-enable-google-mcp-server-cloud-logging to disable. + + --google-mcp-server-enforcement-type=GOOGLE_MCP_SERVER_ENFORCEMENT_TYPE + Specifies the enforcement mode for Google MCP server sanitization, + such as "INSPECT_ONLY" or "INSPECT_AND_BLOCK". Default is + "INSPECT_ONLY". + + Options for Vertex AI sanitization. + + --[no-]enable-vertex-ai-cloud-logging + Enable Cloud Logging for Vertex AI sanitization to log Model Armor + sanitization results. Use --enable-vertex-ai-cloud-logging to enable + and --no-enable-vertex-ai-cloud-logging to disable. + + --vertex-ai-enforcement-type=VERTEX_AI_ENFORCEMENT_TYPE + Specifies the enforcement mode for Vertex AI sanitization, such as + "INSPECT_ONLY" or "INSPECT_AND_BLOCK". Default is "INSPECT_ONLY". + PI and jailbreak filter settings. --pi-and-jailbreak-filter-settings-confidence-level=PI_AND_JAILBREAK_FILTER_SETTINGS_CONFIDENCE_LEVEL diff --git a/gcloud/alpha/monitoring/alerts/describe b/gcloud/alpha/monitoring/alerts/describe index ec9872761..8260d5a11 100644 --- a/gcloud/alpha/monitoring/alerts/describe +++ b/gcloud/alpha/monitoring/alerts/describe @@ -42,5 +42,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta monitoring alerts describe diff --git a/gcloud/alpha/monitoring/alerts/help b/gcloud/alpha/monitoring/alerts/help index e64b3993e..31d4e7e2b 100644 --- a/gcloud/alpha/monitoring/alerts/help +++ b/gcloud/alpha/monitoring/alerts/help @@ -28,5 +28,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta monitoring alerts diff --git a/gcloud/alpha/monitoring/alerts/list b/gcloud/alpha/monitoring/alerts/list index d6815ee47..c708bfe31 100644 --- a/gcloud/alpha/monitoring/alerts/list +++ b/gcloud/alpha/monitoring/alerts/list @@ -77,5 +77,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta monitoring alerts list diff --git a/gcloud/alpha/netapp/help b/gcloud/alpha/netapp/help index 2e6f60260..658ad14f9 100644 --- a/gcloud/alpha/netapp/help +++ b/gcloud/alpha/netapp/help @@ -29,6 +29,9 @@ GROUPS active-directories (ALPHA) Create and manage Cloud NetApp Active Directories. + host-groups + (ALPHA) Create and manage Cloud NetApp Host Groups. + locations (ALPHA) Get and list locations where Cloud NetApp Files is available. diff --git a/gcloud/alpha/netapp/host-groups/create b/gcloud/alpha/netapp/host-groups/create new file mode 100644 index 000000000..79a9a8160 --- /dev/null +++ b/gcloud/alpha/netapp/host-groups/create @@ -0,0 +1,101 @@ +NAME + gcloud alpha netapp host-groups create - create a Cloud NetApp Host Group + +SYNOPSIS + gcloud alpha netapp host-groups create (HOST_GROUP : --location=LOCATION) + --hosts=HOST,[HOST,...] --os-type=OS_TYPE --type=TYPE [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a Cloud NetApp Host Group. + +EXAMPLES + The following command creates a Host Group named NAME using the required + arguments: + + $ gcloud alpha netapp host-groups create NAME \ + --location=us-central1 --type=ISCSI_INITIATOR \ + --hosts=host1,host2 --os-type=LINUX + +POSITIONAL ARGUMENTS + Host group resource - The Host Group to create. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument host_group 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. + + HOST_GROUP + ID of the host_group or fully qualified identifier for the + host_group. + + To set the host_group attribute: + ▸ provide the argument host_group 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 host_group. + + To set the location attribute: + ▸ provide the argument host_group on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +REQUIRED FLAGS + --hosts=HOST,[HOST,...] + List of hosts in the host group. + + --os-type=OS_TYPE + String indicating the OS type of the hosts in the host group. The + supported values are: 'LINUX', 'WINDOWS', 'ESXI'. OS_TYPE must be one + of: LINUX, WINDOWS, ESXI. + + --type=TYPE + String indicating the type of host group. The supported values are: + 'ISCSI_INITIATOR'. TYPE must be (only one value is supported): + ISCSI_INITIATOR. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A description of the Cloud NetApp Host Group + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in 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 netapp host-groups create + + $ gcloud beta netapp host-groups create + diff --git a/gcloud/alpha/netapp/host-groups/delete b/gcloud/alpha/netapp/host-groups/delete new file mode 100644 index 000000000..ed3d7d682 --- /dev/null +++ b/gcloud/alpha/netapp/host-groups/delete @@ -0,0 +1,77 @@ +NAME + gcloud alpha netapp host-groups delete - delete a Cloud NetApp Host Group + +SYNOPSIS + gcloud alpha netapp host-groups delete (HOST_GROUP : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Cloud NetApp Host Group. + +EXAMPLES + The following command deletes a Host Group named NAME: + + $ gcloud alpha netapp host-groups delete NAME --location=us-central1 + + To delete a Host Group named NAME asynchronously, run the following + command: + + $ gcloud alpha netapp host-groups delete NAME \ + --location=us-central1 --async + +POSITIONAL ARGUMENTS + Host group resource - The Host Group 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 host_group 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. + + HOST_GROUP + ID of the host_group or fully qualified identifier for the + host_group. + + To set the host_group attribute: + ▸ provide the argument host_group 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 host_group. + + To set the location attribute: + ▸ provide the argument host_group on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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 netapp host-groups delete + + $ gcloud beta netapp host-groups delete + diff --git a/gcloud/alpha/netapp/host-groups/describe b/gcloud/alpha/netapp/host-groups/describe new file mode 100644 index 000000000..598e3a41b --- /dev/null +++ b/gcloud/alpha/netapp/host-groups/describe @@ -0,0 +1,69 @@ +NAME + gcloud alpha netapp host-groups describe - describe a Cloud NetApp Host + Group + +SYNOPSIS + gcloud alpha netapp host-groups describe (HOST_GROUP : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a Cloud NetApp Host Group. + +EXAMPLES + The following command describes a Host Group named NAME in the given + location: + + $ gcloud alpha netapp host-groups describe NAME \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Host group resource - The Host Group 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 host_group 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. + + HOST_GROUP + ID of the host_group or fully qualified identifier for the + host_group. + + To set the host_group attribute: + ▸ provide the argument host_group 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 host_group. + + To set the location attribute: + ▸ provide the argument host_group on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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 netapp host-groups describe + + $ gcloud beta netapp host-groups describe + diff --git a/gcloud/alpha/netapp/host-groups/help b/gcloud/alpha/netapp/host-groups/help new file mode 100644 index 000000000..253bed5a0 --- /dev/null +++ b/gcloud/alpha/netapp/host-groups/help @@ -0,0 +1,43 @@ +NAME + gcloud alpha netapp host-groups - create and manage Cloud NetApp Host + Groups + +SYNOPSIS + gcloud alpha netapp host-groups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create and manage Cloud NetApp Host Groups. + +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 Cloud NetApp Host Group. + + delete + (ALPHA) Delete a Cloud NetApp Host Group. + + describe + (ALPHA) Describe a Cloud NetApp Host Group. + + list + (ALPHA) List Cloud NetApp Host Groups. + + update + (ALPHA) Update a Cloud NetApp Host Group. + +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 netapp host-groups + + $ gcloud beta netapp host-groups + diff --git a/gcloud/alpha/netapp/host-groups/list b/gcloud/alpha/netapp/host-groups/list new file mode 100644 index 000000000..ab6b8af86 --- /dev/null +++ b/gcloud/alpha/netapp/host-groups/list @@ -0,0 +1,87 @@ +NAME + gcloud alpha netapp host-groups list - list Cloud NetApp Host Groups + +SYNOPSIS + gcloud alpha netapp host-groups list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists Cloud NetApp Host Groups. + +EXAMPLES + The following command lists all Host Groups in the given location: + + $ gcloud alpha netapp host-groups list --location=us-central1 + +FLAGS + Location resource - The location in which to list Host Groups. 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; + ◆ uses all locations by default. with a fully specified name; + ◆ set the property netapp/location 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; + ▸ uses all locations by default.; + ▸ set the property netapp/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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 netapp host-groups list + + $ gcloud beta netapp host-groups list + diff --git a/gcloud/alpha/netapp/host-groups/update b/gcloud/alpha/netapp/host-groups/update new file mode 100644 index 000000000..e6d7d08a8 --- /dev/null +++ b/gcloud/alpha/netapp/host-groups/update @@ -0,0 +1,111 @@ +NAME + gcloud alpha netapp host-groups update - update a Cloud NetApp Host Group + +SYNOPSIS + gcloud alpha netapp host-groups update (HOST_GROUP : --location=LOCATION) + [--async] [--description=DESCRIPTION] [--hosts=HOST,[HOST,...]] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a Cloud NetApp Host Group and its specified parameters. + +EXAMPLES + The following command updates a Host Group named NAME and its specified + parameters: + + $ gcloud alpha netapp host-groups update NAME \ + --location=us-central1 --description="new description" \ + --hosts="host3,host4" --update-labels=key2=val2 + +POSITIONAL ARGUMENTS + Host group resource - The Host Group 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 host_group 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. + + HOST_GROUP + ID of the host_group or fully qualified identifier for the + host_group. + + To set the host_group attribute: + ▸ provide the argument host_group 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 host_group. + + To set the location attribute: + ▸ provide the argument host_group on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A description of the Cloud NetApp Host Group + + --hosts=HOST,[HOST,...] + List of hosts in the host group. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha netapp host-groups update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha netapp host-groups update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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 netapp host-groups update + + $ gcloud beta netapp host-groups update + diff --git a/gcloud/alpha/netapp/storage-pools/create b/gcloud/alpha/netapp/storage-pools/create index 4edb50f33..550161bda 100644 --- a/gcloud/alpha/netapp/storage-pools/create +++ b/gcloud/alpha/netapp/storage-pools/create @@ -15,7 +15,7 @@ SYNOPSIS [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] [--qos-type=QOS_TYPE] [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] [--total-throughput=TOTAL_THROUGHPUT] - [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--type=TYPE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a Storage Pool to contain Volumes with a specified Service @@ -214,6 +214,16 @@ OPTIONAL FLAGS The total throughput of the Storage Pool in MiB/s or GiB/s units. If no throughput unit is specified, MiB/s is assumed. + --type=TYPE + The type of the Storage Pool. FILE pools support file-based volumes + only. UNIFIED pools support both file and block volumes. TYPE must be + one of: + + file + File-based volumes only (default). + unified + Both file and block volumes. + --zone=ZONE String indicating active zone of the Storage Pool diff --git a/gcloud/alpha/netapp/volumes/create b/gcloud/alpha/netapp/volumes/create index d24a19b8d..e65c81260 100644 --- a/gcloud/alpha/netapp/volumes/create +++ b/gcloud/alpha/netapp/volumes/create @@ -5,6 +5,8 @@ SYNOPSIS gcloud alpha netapp volumes create (VOLUME : --location=LOCATION) --capacity=CAPACITY --protocols=PROTOCOL,[PROTOCOL,...] --storage-pool=STORAGE_POOL [--async] + [--block-devices=[host-groups=HOST-GROUPS], + [name=NAME],[os-type=OS-TYPE],[size-gib=SIZE-GIB]] [--cache-parameters=[cache-config=CACHE-CONFIG], [enable-global-file-lock=ENABLE-GLOBAL-FILE-LOCK], [peer-cluster-name=PEER-CLUSTER-NAME], @@ -140,6 +142,24 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --block-devices=[host-groups=HOST-GROUPS],[name=NAME],[os-type=OS-TYPE],[size-gib=SIZE-GIB] + A block device to be created with the volume. + + This flag can be repeated to specify multiple block devices. + + The following keys are available: + name + A user-defined name for the block device. + host-groups + A comma-separated list of host groups that can mount the block + volume. + os-type + The OS type of the volume. Allowed values are OS_TYPE_UNSPECIFIED, + LINUX, WINDOWS. + size-gib + The size of the block device in GiB. Note that this value is + ignored during volume creation and is system-managed. + --cache-parameters=[cache-config=CACHE-CONFIG],[enable-global-file-lock=ENABLE-GLOBAL-FILE-LOCK],[peer-cluster-name=PEER-CLUSTER-NAME],[peer-ip-addresses=PEER-IP-ADDRESSES],[peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME] Cache Parameters contains cache parameters of a volume. diff --git a/gcloud/alpha/netapp/volumes/update b/gcloud/alpha/netapp/volumes/update index c1e3906ba..6be454de8 100644 --- a/gcloud/alpha/netapp/volumes/update +++ b/gcloud/alpha/netapp/volumes/update @@ -3,6 +3,8 @@ NAME SYNOPSIS gcloud alpha netapp volumes update (VOLUME : --location=LOCATION) [--async] + [--block-devices=[host-groups=HOST-GROUPS], + [name=NAME],[os-type=OS-TYPE],[size-gib=SIZE-GIB]] [--cache-parameters=[cache-config=CACHE-CONFIG], [enable-global-file-lock=ENABLE-GLOBAL-FILE-LOCK], [peer-cluster-name=PEER-CLUSTER-NAME], @@ -87,6 +89,24 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --block-devices=[host-groups=HOST-GROUPS],[name=NAME],[os-type=OS-TYPE],[size-gib=SIZE-GIB] + A block device to be created with the volume. + + This flag can be repeated to specify multiple block devices. + + The following keys are available: + name + A user-defined name for the block device. + host-groups + A comma-separated list of host groups that can mount the block + volume. + os-type + The OS type of the volume. Allowed values are OS_TYPE_UNSPECIFIED, + LINUX, WINDOWS. + size-gib + The size of the block device in GiB. Note that this value is + ignored during volume creation and is system-managed. + --cache-parameters=[cache-config=CACHE-CONFIG],[enable-global-file-lock=ENABLE-GLOBAL-FILE-LOCK],[peer-cluster-name=PEER-CLUSTER-NAME],[peer-ip-addresses=PEER-IP-ADDRESSES],[peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME] Cache Parameters contains cache parameters of a volume. diff --git a/gcloud/alpha/network-security/intercept-endpoint-groups/create b/gcloud/alpha/network-security/intercept-endpoint-groups/create index 42e174dc9..fea0de305 100644 --- a/gcloud/alpha/network-security/intercept-endpoint-groups/create +++ b/gcloud/alpha/network-security/intercept-endpoint-groups/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha network-security intercept-endpoint-groups create (INTERCEPT_ENDPOINT_GROUP : --location=LOCATION) (--intercept-deployment-group=INTERCEPT_DEPLOYMENT_GROUP - : --intercept-deployment-group-location=INTERCEPT_DEPLOYMENT_GROUP_LOCATION) + : --intercept-deployment-group-location=INTERCEPT_DEPLOYMENT_GROUP_LOCATION --intercept-deployment-group-project=INTERCEPT_DEPLOYMENT_GROUP_PROJECT) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] @@ -83,14 +83,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Intercept deployment group resource - Intercept Deployment Group. 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 --intercept-deployment-group on the command line - with a fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. + resource. This must be specified. @@ -117,6 +110,19 @@ REQUIRED FLAGS ▸ provide the argument INTERCEPT_ENDPOINT_GROUP on the command line with a fully specified name. + --intercept-deployment-group-project=INTERCEPT_DEPLOYMENT_GROUP_PROJECT + Project of the intercept deployment group. + + To set the project attribute: + ▸ provide the argument --intercept-deployment-group on the command + line with a fully specified name; + ▸ provide the argument --intercept-deployment-group-project on the + command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project; + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP on the command line + with a fully specified name. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/network-security/mirroring-endpoint-groups/create b/gcloud/alpha/network-security/mirroring-endpoint-groups/create index 13dd00594..39145d3b4 100644 --- a/gcloud/alpha/network-security/mirroring-endpoint-groups/create +++ b/gcloud/alpha/network-security/mirroring-endpoint-groups/create @@ -7,7 +7,7 @@ SYNOPSIS (MIRRORING_ENDPOINT_GROUP : --location=LOCATION) (--mirroring-deployment-groups=MIRRORING_DEPLOYMENT_GROUPS,[...] | [--mirroring-deployment-group=MIRRORING_DEPLOYMENT_GROUP - : --mirroring-deployment-group-location=MIRRORING_DEPLOYMENT_GROUP_LOCATION]) + : --mirroring-deployment-group-location=MIRRORING_DEPLOYMENT_GROUP_LOCATION --mirroring-deployment-group-project=MIRRORING_DEPLOYMENT_GROUP_PROJECT]) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="20m"] [--type=TYPE] [GCLOUD_WIDE_FLAG ...] @@ -87,18 +87,13 @@ REQUIRED FLAGS --mirroring-deployment-groups=MIRRORING_DEPLOYMENT_GROUPS,[...] A comma-separated list of Mirroring Deployment Groups to associate - with the Endpoint Group. + with the Endpoint Group. Each deployment group must be specified by + its full resource name. e.g. + --mirroring-deployment-groups=projects/123/locations/global/mirroringDeploymentGroups/my-dg1,projects/456/locations/global/mirroringDeploymentGroups/my-dg2 Mirroring deployment group resource - Mirroring Deployment Group. 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 --mirroring-deployment-group on the command - line with a fully specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. + resource. --mirroring-deployment-group=MIRRORING_DEPLOYMENT_GROUP ID of the mirroring deployment group or fully qualified identifier @@ -123,6 +118,19 @@ REQUIRED FLAGS ▫ provide the argument MIRRORING_ENDPOINT_GROUP on the command line with a fully specified name. + --mirroring-deployment-group-project=MIRRORING_DEPLOYMENT_GROUP_PROJECT + Project of the mirroring deployment group. + + To set the project attribute: + ▫ provide the argument --mirroring-deployment-group on the + command line with a fully specified name; + ▫ provide the argument --mirroring-deployment-group-project on + the command line; + ▫ provide the argument --project on the command line; + ▫ set the property core/project; + ▫ provide the argument MIRRORING_ENDPOINT_GROUP on the command + line with a fully specified name. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/network-security/security-profiles/custom-mirroring/update b/gcloud/alpha/network-security/security-profiles/custom-mirroring/update index 7866f9297..7e02b7606 100644 --- a/gcloud/alpha/network-security/security-profiles/custom-mirroring/update +++ b/gcloud/alpha/network-security/security-profiles/custom-mirroring/update @@ -6,7 +6,11 @@ SYNOPSIS gcloud alpha network-security security-profiles custom-mirroring update (SECURITY_PROFILE : --location=LOCATION --organization=ORGANIZATION) [--async] [--description=DESCRIPTION] [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + [--add-mirroring-deployment-groups=[MIRRORING-DEPLOYMENT-GROUPS,...] + | --clear-mirroring-deployment-groups + | --remove-mirroring-deployment-groups=[MIRRORING-DEPLOYMENT-GROUPS, + ...]] [--clear-labels | --remove-labels=[KEY,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a Custom Mirroring Security Profile. @@ -79,6 +83,20 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + These flags modify the member mirroring deployment groups of this + security_profile. + + At most one of these can be specified: + + --add-mirroring-deployment-groups=[MIRRORING-DEPLOYMENT-GROUPS,...] + Append the given values to the current mirroring deployment groups. + + --clear-mirroring-deployment-groups + Empty the current mirroring deployment groups. + + --remove-mirroring-deployment-groups=[MIRRORING-DEPLOYMENT-GROUPS,...] + Remove the given values from the current mirroring deployment groups. + At most one of these can be specified: --clear-labels diff --git a/gcloud/alpha/network-services/multicast-domain-activations/create b/gcloud/alpha/network-services/multicast-domain-activations/create index afae53b29..65c654688 100644 --- a/gcloud/alpha/network-services/multicast-domain-activations/create +++ b/gcloud/alpha/network-services/multicast-domain-activations/create @@ -6,7 +6,8 @@ SYNOPSIS gcloud alpha network-services multicast-domain-activations create (MULTICAST_DOMAIN_ACTIVATION : --location=LOCATION) --multicast-domain=MULTICAST_DOMAIN [--async] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--disable-placement-policy] + [--labels=[KEY=VALUE,...]] [--aggr-egress-pps=AGGR_EGRESS_PPS : --aggr-ingress-pps=AGGR_INGRESS_PPS --avg-packet-size=AVG_PACKET_SIZE @@ -24,12 +25,12 @@ EXAMPLES location 'zone'. $ gcloud alpha network-services multicast-domain-activations \ - create my-multicast-group-definition \ + create my-multicast-domain-activation \ --multicast-domain=path-to-md --location=zone POSITIONAL ARGUMENTS - Multicast domain activation resource - Name of the multicast group - definition to be created. The arguments in this group can be used to + Multicast domain activation resource - Name of the multicast domain + activation to be created. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -72,6 +73,10 @@ OPTIONAL FLAGS --description=DESCRIPTION The description for the multicast domain activation. + --disable-placement-policy + True to disable the use of the placement policy for this multicast + domain activation. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/alpha/pubsub/snapshots/create b/gcloud/alpha/pubsub/snapshots/create index b9a005167..151500961 100644 --- a/gcloud/alpha/pubsub/snapshots/create +++ b/gcloud/alpha/pubsub/snapshots/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud alpha pubsub snapshots create SNAPSHOT [SNAPSHOT ...] --subscription=SUBSCRIPTION [--labels=[KEY=VALUE,...]] - [--subscription-project=SUBSCRIPTION_PROJECT] [GCLOUD_WIDE_FLAG ...] + [--subscription-project=SUBSCRIPTION_PROJECT] [--tags=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates one or more Cloud Pub/Sub snapshots. @@ -36,6 +37,11 @@ OPTIONAL FLAGS The name of the project the provided subscription belongs to. If not set, it defaults to the currently selected cloud project. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. Example: + 123/environment=production,123/costCenter=marketing + 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/pubsub/subscriptions/create b/gcloud/alpha/pubsub/subscriptions/create index ae5257c16..12a3fbb24 100644 --- a/gcloud/alpha/pubsub/subscriptions/create +++ b/gcloud/alpha/pubsub/subscriptions/create @@ -10,7 +10,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--message-filter=MESSAGE_FILTER] [--message-retention-duration=MESSAGE_RETENTION_DURATION] [--message-transforms-file=MESSAGE_TRANSFORMS_FILE] - [--retain-acked-messages] + [--retain-acked-messages] [--tags=[KEY=VALUE,...]] [[--bigquery-table=BIGQUERY_TABLE : --bigquery-service-account-email=BIGQUERY_SERVICE_ACCOUNT_EMAIL --drop-unknown-fields --write-metadata --use-table-schema @@ -139,6 +139,11 @@ OPTIONAL FLAGS retained by default. Use --no-retain-acked-messages to disable this flag. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. Example: + 123/environment=production,123/costCenter=marketing + At most one of these can be specified: BigQuery Config Options. The Cloud Pub/Sub service account associated diff --git a/gcloud/alpha/pubsub/topics/create b/gcloud/alpha/pubsub/topics/create index b771c3c69..105984341 100644 --- a/gcloud/alpha/pubsub/topics/create +++ b/gcloud/alpha/pubsub/topics/create @@ -7,6 +7,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--message-retention-duration=MESSAGE_RETENTION_DURATION] [--message-transforms-file=MESSAGE_TRANSFORMS_FILE] + [--tags=[KEY=VALUE,...]] [--ingestion-log-severity=INGESTION_LOG_SEVERITY --aws-msk-ingestion-aws-role-arn=AWS_MSK_INGESTION_AWS_ROLE_ARN --aws-msk-ingestion-cluster-arn=AWS_MSK_INGESTION_CLUSTER_ARN @@ -76,6 +77,11 @@ FLAGS --message-transforms-file=MESSAGE_TRANSFORMS_FILE Path to YAML or JSON file containing message transforms. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. Example: + 123/environment=production,123/costCenter=marketing + Following flags are for specifying the data source settings for an import topic diff --git a/gcloud/alpha/run/compose/help b/gcloud/alpha/run/compose/help index 60b3ace4a..000e3d640 100644 --- a/gcloud/alpha/run/compose/help +++ b/gcloud/alpha/run/compose/help @@ -22,5 +22,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run compose diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index d03f64359..32cadebcf 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -274,13 +274,13 @@ FLAGS scaling with the given integer as a fixed instance count. --scaling-concurrency-utilization=SCALING_CONCURRENCY_UTILIZATION - A value between 0.0 and 1.0 that indicates the target concurrency + A value between 0.5 and 0.95 that indicates the target concurrency utilization where a new instance should be started. Also accepts "default" to restore the default value or "disabled" to disable concurrency utilization scaling. --scaling-cpu-utilization=SCALING_CPU_UTILIZATION - A value between 0.0 and 1.0 that indicates the target CPU utilization + A value between 0.5 and 0.95 that indicates the target CPU utilization where a new instance should be started. Also accepts "default" to restore the default value or "disabled" to disable CPU utilization scaling. @@ -824,13 +824,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. + Clears all existing network tags from the Cloud Run service. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + service. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/alpha/run/jobs/create b/gcloud/alpha/run/jobs/create index 651501b7a..e0c9e8bee 100644 --- a/gcloud/alpha/run/jobs/create +++ b/gcloud/alpha/run/jobs/create @@ -403,8 +403,8 @@ FLAGS network settings, use --clear-network. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the Cloud - Run job. To clear existing tags, use --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + job. To clear existing tags, use --clear-network-tags. --subnet=SUBNET The VPC subnetwork that the Cloud Run job will get IPs from. The diff --git a/gcloud/alpha/run/jobs/deploy b/gcloud/alpha/run/jobs/deploy index 2427c7ddb..6b8c8f07f 100644 --- a/gcloud/alpha/run/jobs/deploy +++ b/gcloud/alpha/run/jobs/deploy @@ -443,11 +443,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run job. + Clears all existing network tags from the Cloud Run job. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run job. To clear existing tags, use --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + job. To clear existing tags, use --clear-network-tags. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/jobs/update b/gcloud/alpha/run/jobs/update index 2387e17e0..d72d4830e 100644 --- a/gcloud/alpha/run/jobs/update +++ b/gcloud/alpha/run/jobs/update @@ -475,11 +475,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run job. + Clears all existing network tags from the Cloud Run job. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run job. To clear existing tags, use --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + job. To clear existing tags, use --clear-network-tags. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/run/multi-region-services/update b/gcloud/alpha/run/multi-region-services/update index 3f8db743d..5636afbb6 100644 --- a/gcloud/alpha/run/multi-region-services/update +++ b/gcloud/alpha/run/multi-region-services/update @@ -245,13 +245,13 @@ FLAGS scaling with the given integer as a fixed instance count. --scaling-concurrency-utilization=SCALING_CONCURRENCY_UTILIZATION - A value between 0.0 and 1.0 that indicates the target concurrency + A value between 0.5 and 0.95 that indicates the target concurrency utilization where a new instance should be started. Also accepts "default" to restore the default value or "disabled" to disable concurrency utilization scaling. --scaling-cpu-utilization=SCALING_CPU_UTILIZATION - A value between 0.0 and 1.0 that indicates the target CPU utilization + A value between 0.5 and 0.95 that indicates the target CPU utilization where a new instance should be started. Also accepts "default" to restore the default value or "disabled" to disable CPU utilization scaling. @@ -616,13 +616,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. + Clears all existing network tags from the Cloud Run service. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + service. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index cfc956498..b611ee896 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -243,13 +243,13 @@ FLAGS scaling with the given integer as a fixed instance count. --scaling-concurrency-utilization=SCALING_CONCURRENCY_UTILIZATION - A value between 0.0 and 1.0 that indicates the target concurrency + A value between 0.5 and 0.95 that indicates the target concurrency utilization where a new instance should be started. Also accepts "default" to restore the default value or "disabled" to disable concurrency utilization scaling. --scaling-cpu-utilization=SCALING_CPU_UTILIZATION - A value between 0.0 and 1.0 that indicates the target CPU utilization + A value between 0.5 and 0.95 that indicates the target CPU utilization where a new instance should be started. Also accepts "default" to restore the default value or "disabled" to disable CPU utilization scaling. @@ -697,13 +697,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. + Clears all existing network tags from the Cloud Run service. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + service. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/alpha/run/worker-pools/deploy b/gcloud/alpha/run/worker-pools/deploy index b19a71c68..d11970ee7 100644 --- a/gcloud/alpha/run/worker-pools/deploy +++ b/gcloud/alpha/run/worker-pools/deploy @@ -505,13 +505,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - worker. + Clears all existing network tags from the Cloud Run worker. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run worker. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + worker. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/alpha/run/worker-pools/update b/gcloud/alpha/run/worker-pools/update index 4217db9ee..1ea201cfd 100644 --- a/gcloud/alpha/run/worker-pools/update +++ b/gcloud/alpha/run/worker-pools/update @@ -483,13 +483,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - worker. + Clears all existing network tags from the Cloud Run worker. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run worker. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + worker. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/alpha/services/groups/list-expanded-members b/gcloud/alpha/services/groups/list-expanded-members index 165b10460..8c7215ae0 100644 --- a/gcloud/alpha/services/groups/list-expanded-members +++ b/gcloud/alpha/services/groups/list-expanded-members @@ -89,5 +89,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services groups list-expanded-members diff --git a/gcloud/alpha/services/groups/list-members b/gcloud/alpha/services/groups/list-members index 5cb3dabe7..e74fb6ba2 100644 --- a/gcloud/alpha/services/groups/list-members +++ b/gcloud/alpha/services/groups/list-members @@ -88,5 +88,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services groups list-members diff --git a/gcloud/alpha/services/help b/gcloud/alpha/services/help index 6752e0be6..05dec1acc 100644 --- a/gcloud/alpha/services/help +++ b/gcloud/alpha/services/help @@ -25,6 +25,9 @@ GROUPS identity (ALPHA) Manage service identity. + mcp + (ALPHA) List, enable and disable MCP endpoints. + operations (ALPHA) Manage Operation for various services. diff --git a/gcloud/alpha/services/list b/gcloud/alpha/services/list index 2dab4b8b4..dbaf323c8 100644 --- a/gcloud/alpha/services/list +++ b/gcloud/alpha/services/list @@ -10,21 +10,19 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command lists the services that are enabled or available - (Google first party services) to be enabled by a project, folder or - organization. Service enablement and availability can be inherited from - resource ancestors. A resource's enabled services include services that are - enabled on the resource itself and enabled on all resource ancestors. - services by using exactly one of the --enabled or --available flags. - --enabled is the default. + (ALPHA) This command lists the services that are enabled or available to be + enabled by a project, folder or organization. Service enablement and + availability can be inherited from resource ancestors. A resource's enabled + services include services that are enabled on the resource itself and + enabled on all resource ancestors. services by using exactly one of the + --enabled or --available flags. --enabled is the default. EXAMPLES To list the services the current project has enabled for consumption, run: $ gcloud alpha services list --enabled - To list the Google first party services the current project can enable for - consumption, run: + To list the services the current project can enable for consumption, run: $ gcloud alpha services list --available @@ -32,8 +30,8 @@ FLAGS At most one of these can be specified: --available - Return the Google first party services available to the project, - folder or organization to enable. + Return the services available to the project, folder or organization + to enable. --enabled (DEFAULT) Return the services which the project, folder or diff --git a/gcloud/alpha/services/mcp/content-security/add b/gcloud/alpha/services/mcp/content-security/add new file mode 100644 index 000000000..8e22dcec0 --- /dev/null +++ b/gcloud/alpha/services/mcp/content-security/add @@ -0,0 +1,42 @@ +NAME + gcloud alpha services mcp content-security add - add MCP content security + provider of a project + +SYNOPSIS + gcloud alpha services mcp content-security add + MCP_CONTENT_SECURITY_PROVIDER [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Add MCP content security provider of a project. + +EXAMPLES + Add MCP content security provider of a project: + + $ gcloud alpha services mcp content-security add \ + my-mcp-content-security-provider + + Add MCP content security provider of a project my-project: + + $ gcloud alpha services mcp content-security add \ + my-mcp-content-security-provider --project=my-project + +POSITIONAL ARGUMENTS + MCP_CONTENT_SECURITY_PROVIDER + The MCP content security provider to add. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +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 services mcp content-security add + diff --git a/gcloud/alpha/services/mcp/content-security/get b/gcloud/alpha/services/mcp/content-security/get new file mode 100644 index 000000000..3dff51e4d --- /dev/null +++ b/gcloud/alpha/services/mcp/content-security/get @@ -0,0 +1,35 @@ +NAME + gcloud alpha services mcp content-security get - get MCP content security + providers for a project + +SYNOPSIS + gcloud alpha services mcp content-security get [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get MCP content security providers for a project. + +EXAMPLES + Get MCP content security providers for a project: + + $ gcloud alpha services mcp content-security get + + Get MCP content security providers for a project my-project: + + $ gcloud alpha services mcp content-security get --project=my-project + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta services mcp content-security get + diff --git a/gcloud/alpha/services/mcp/content-security/help b/gcloud/alpha/services/mcp/content-security/help new file mode 100644 index 000000000..6438348cb --- /dev/null +++ b/gcloud/alpha/services/mcp/content-security/help @@ -0,0 +1,35 @@ +NAME + gcloud alpha services mcp content-security - get/add/remove MCP content + security + +SYNOPSIS + gcloud alpha services mcp content-security COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get/add/remove MCP content security. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add + (ALPHA) Add MCP content security provider of a project. + + get + (ALPHA) Get MCP content security providers for a project. + + remove + (ALPHA) Remove MCP content security provider of a project. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta services mcp content-security + diff --git a/gcloud/alpha/services/mcp/content-security/remove b/gcloud/alpha/services/mcp/content-security/remove new file mode 100644 index 000000000..f643fa67b --- /dev/null +++ b/gcloud/alpha/services/mcp/content-security/remove @@ -0,0 +1,42 @@ +NAME + gcloud alpha services mcp content-security remove - remove MCP content + security provider of a project + +SYNOPSIS + gcloud alpha services mcp content-security remove + MCP_CONTENT_SECURITY_PROVIDER [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Remove MCP content security provider of a project. + +EXAMPLES + Remove MCP content security provider of a project: + + $ gcloud alpha services mcp content-security remove \ + my-mcp-content-security-provider + + Remove MCP content security provider of a project my-project: + + $ gcloud alpha services mcp content-security remove \ + my-mcp-content-security-provider --project=my-project + +POSITIONAL ARGUMENTS + MCP_CONTENT_SECURITY_PROVIDER + The MCP content security provider to remove. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta services mcp content-security remove + diff --git a/gcloud/alpha/services/mcp/disable b/gcloud/alpha/services/mcp/disable new file mode 100644 index 000000000..68f7e471e --- /dev/null +++ b/gcloud/alpha/services/mcp/disable @@ -0,0 +1,82 @@ +NAME + gcloud alpha services mcp disable - disable a service for MCP on a project, + folder or organization + +SYNOPSIS + gcloud alpha services mcp disable SERVICE [--async] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Disable a service for MCP on a project, folder or organization + +EXAMPLES + To disable a service for MCP called my-service on the current project, run: + + $ gcloud alpha services mcp disable my-service + + To disable a service for MCP called my-service on the project my-project, + run: + + $ gcloud alpha services mcp disable my-service --project=my-project + + To disable a service for MCP called my-service on the folder my-folder, + run: + + $ gcloud alpha services mcp disable my-service --folder=my-folder + + To disable a service for MCP called my-service on the organization + my-organization, run: + + $ gcloud alpha services mcp disable my-service \ + --organization=my-organization + + To run the same command asynchronously (non-blocking), run: + + $ gcloud alpha services mcp disable my-service --async + +POSITIONAL ARGUMENTS + SERVICE + The name of the service to disable MCP. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta services mcp disable + diff --git a/gcloud/alpha/services/mcp/enable b/gcloud/alpha/services/mcp/enable new file mode 100644 index 000000000..70d462162 --- /dev/null +++ b/gcloud/alpha/services/mcp/enable @@ -0,0 +1,86 @@ +NAME + gcloud alpha services mcp enable - enable a service for MCP on a project, + folder or organization + +SYNOPSIS + gcloud alpha services mcp enable SERVICE [--async] + [--skip-mcp-endpoint-check] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Enable a service for MCP on a project, folder or organization + +EXAMPLES + To enable a service for MCP called my-service on the current project, run: + + $ gcloud alpha services mcp enable my-service + + To enable a service for MCP called my-service on the project my-project, + run: + + $ gcloud alpha services mcp enable my-service --project=my-project + + To enable a service for MCP called my-service on the folder my-folder, run: + + $ gcloud alpha services mcp enable my-service --folder=my-folder + + To enable a service for MCP called my-service on the organization + my-organization, run: + + $ gcloud alpha services mcp enable my-service \ + --organization=my-organization + + To run the same command asynchronously (non-blocking), run: + + $ gcloud alpha services mcp enable my-service --async + +POSITIONAL ARGUMENTS + SERVICE + The name of the service to enable MCP. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --skip-mcp-endpoint-check + If true, the system will bypass the check for MCP endpoint while + enabling a service. + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta services mcp enable + diff --git a/gcloud/alpha/services/mcp/help b/gcloud/alpha/services/mcp/help new file mode 100644 index 000000000..263fa8f7d --- /dev/null +++ b/gcloud/alpha/services/mcp/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha services mcp - list, enable and disable MCP endpoints + +SYNOPSIS + gcloud alpha services mcp GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List, enable and disable MCP endpoints. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + content-security + (ALPHA) Get/add/remove MCP content security. + +COMMANDS + COMMAND is one of the following: + + disable + (ALPHA) Disable a service for MCP on a project, folder or organization. + + enable + (ALPHA) Enable a service for MCP on a project, folder or organization. + + list + (ALPHA) List MCP services for a project, folder or organization. + +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 services mcp + diff --git a/gcloud/alpha/services/mcp/list b/gcloud/alpha/services/mcp/list new file mode 100644 index 000000000..09fe112c6 --- /dev/null +++ b/gcloud/alpha/services/mcp/list @@ -0,0 +1,97 @@ +NAME + gcloud alpha services mcp list - list MCP services for a project, folder or + organization + +SYNOPSIS + gcloud alpha services mcp list [--available | --enabled] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE; default=1000] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command lists the MCP services that are enabled or available + (with MCP endpoints) to be MCP enabled by a project, folder or + organization. + +EXAMPLES + To list the services the current project has enabled for MCP, run: + + $ gcloud alpha services mcp list --enabled + + To list the services the current project can enable for MCP, run: + + $ gcloud alpha services mcp list --available + +FLAGS + At most one of these can be specified: + + --available + Return the services available to the project, folder or organization + to enable for MCP. + + --enabled + (DEFAULT) Return the MCP services which the project, folder or + organization has enabled. + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE; default=1000 + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + 1000. Paging may be applied before or after --filter and --limit + depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta services mcp list + diff --git a/gcloud/alpha/services/policies/get b/gcloud/alpha/services/policies/get index f5d0a31fa..6662cbfc6 100644 --- a/gcloud/alpha/services/policies/get +++ b/gcloud/alpha/services/policies/get @@ -64,5 +64,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services policies get diff --git a/gcloud/alpha/services/policies/get-effective b/gcloud/alpha/services/policies/get-effective index 3504c3908..bac50e4d6 100644 --- a/gcloud/alpha/services/policies/get-effective +++ b/gcloud/alpha/services/policies/get-effective @@ -57,5 +57,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services policies get-effective diff --git a/gcloud/alpha/services/policies/test-enabled b/gcloud/alpha/services/policies/test-enabled index 089e2fdcc..9e5696bba 100644 --- a/gcloud/alpha/services/policies/test-enabled +++ b/gcloud/alpha/services/policies/test-enabled @@ -58,5 +58,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services policies test-enabled diff --git a/gcloud/alpha/services/policies/update b/gcloud/alpha/services/policies/update index 9568296fd..1f7bbc84a 100644 --- a/gcloud/alpha/services/policies/update +++ b/gcloud/alpha/services/policies/update @@ -68,5 +68,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta services policies update diff --git a/gcloud/alpha/sql/backups/restore b/gcloud/alpha/sql/backups/restore index b889d7870..43021e88c 100644 --- a/gcloud/alpha/sql/backups/restore +++ b/gcloud/alpha/sql/backups/restore @@ -375,8 +375,8 @@ OPTIONAL FLAGS here: https://cloud.google.com/sql/docs/quotas#storage_limits --storage-type=STORAGE_TYPE - The storage type for the instance. The default is SSD. STORAGE_TYPE - must be one of: SSD, HDD, HYPERDISK_BALANCED. + The storage type for the instance, determined by the selected machine + type. STORAGE_TYPE must be one of: SSD, HDD, HYPERDISK_BALANCED. --tier=TIER, -t TIER Machine type for a shared-core instance e.g. db-g1-small. For all other diff --git a/gcloud/alpha/sql/connect b/gcloud/alpha/sql/connect index 4112ea66d..c9e2f2d35 100644 --- a/gcloud/alpha/sql/connect +++ b/gcloud/alpha/sql/connect @@ -58,7 +58,7 @@ FLAGS Connect to the Cloud SQL instance using private IP. --psc - Connect to the Cloud SQL instance using PSC. + Connect to the Cloud SQL instance using Private Service Connect. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/sql/import/bak b/gcloud/alpha/sql/import/bak index 363ace661..fce4fb701 100644 --- a/gcloud/alpha/sql/import/bak +++ b/gcloud/alpha/sql/import/bak @@ -60,7 +60,7 @@ OPTIONAL FLAGS Whether or not to decrypt the imported encrypted BAK file. --no-recovery - Whether or not the SQL Server import is execueted with NORECOVERY + Whether or not the SQL Server import is executed with NORECOVERY keyword. --recovery-only diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index 714de8726..10869ddc4 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -21,6 +21,7 @@ SYNOPSIS [--connection-pool-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] [--custom-subject-alternative-names=DNS,[DNS,[DNS]]] + [--data-api-access=DATA_API_ACCESS] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--database-version=DATABASE_VERSION; default="MYSQL_8_0"] [--[no-]deletion-protection] @@ -267,6 +268,19 @@ FLAGS update an instance, you can add a comma-separated list of up to three DNS names to the server certificate of your instance. + --data-api-access=DATA_API_ACCESS + Controls connectivity to the instance using ExecuteSql API. + DATA_API_ACCESS must be one of: + + ALLOW_DATA_API + Allow using ExecuteSql API to connect to the instance. For Private + IP instances, this will allow authorized users to access the + instance from the public internet using ExecuteSql API. + DATA_API_ACCESS_UNSPECIFIED + Unspecified mode, effectively the same as DISALLOW_DATA_API. + DISALLOW_DATA_API + Disallow using ExecuteSql API to connect to the instance. + --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an equals sign to separate flag name and value. Flags without values, like @@ -620,8 +634,8 @@ FLAGS here: https://cloud.google.com/sql/docs/quotas#storage_limits --storage-type=STORAGE_TYPE - The storage type for the instance. The default is SSD. STORAGE_TYPE - must be one of: SSD, HDD, HYPERDISK_BALANCED. + The storage type for the instance, determined by the selected machine + type. STORAGE_TYPE must be one of: SSD, HDD, HYPERDISK_BALANCED. --tags=TAG=VALUE,[TAG=VALUE,...] Comma-separated list of tags to set on the instance. Use an equals diff --git a/gcloud/alpha/sql/instances/help b/gcloud/alpha/sql/instances/help index 9f017a092..007098aad 100644 --- a/gcloud/alpha/sql/instances/help +++ b/gcloud/alpha/sql/instances/help @@ -60,7 +60,7 @@ COMMANDS point-in-time-restore (ALPHA) Performs a point in time restore for a Cloud SQL instance - managed by Google Cloud Backup and Disaster Recovery. + managed by Google Cloud Backup and Disaster Recovery (DR) Service. promote-replica (ALPHA) Promotes Cloud SQL read replica to a stand-alone instance. diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 611d89e68..be8de6e1f 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -18,6 +18,7 @@ SYNOPSIS [--clear-active-directory-dns-servers] [--clear-failover-dr-replica-name] [--clear-password-policy] [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] + [--data-api-access=DATA_API_ACCESS] [--database-version=DATABASE_VERSION] [--[no-]deletion-protection] [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] @@ -64,7 +65,7 @@ SYNOPSIS [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] [--storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT] - [--storage-size=STORAGE_SIZE] + [--storage-size=STORAGE_SIZE] [--storage-type=STORAGE_TYPE] [--switch-transaction-logs-to-cloud-storage] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] [--time-zone=TIME_ZONE] [--update-labels=[KEY=VALUE,...]] @@ -212,6 +213,19 @@ FLAGS should not be used when creating an Enterprise Plus edition, as the machine configuration is determined by the --tier flag instead. + --data-api-access=DATA_API_ACCESS + Controls connectivity to the instance using ExecuteSql API. + DATA_API_ACCESS must be one of: + + ALLOW_DATA_API + Allow using ExecuteSql API to connect to the instance. For Private + IP instances, this will allow authorized users to access the + instance from the public internet using ExecuteSql API. + DATA_API_ACCESS_UNSPECIFIED + Unspecified mode, effectively the same as DISALLOW_DATA_API. + DISALLOW_DATA_API + Disallow using ExecuteSql API to connect to the instance. + --database-version=DATABASE_VERSION The database engine type and versions. If left unspecified, no changes occur. See the list of database versions at @@ -551,6 +565,10 @@ FLAGS of GB. The default is 10GB. Information on storage limits can be found here: https://cloud.google.com/sql/docs/quotas#storage_limits + --storage-type=STORAGE_TYPE + The storage type for the instance, determined by the selected machine + type. STORAGE_TYPE must be one of: SSD, HDD, HYPERDISK_BALANCED. + --switch-transaction-logs-to-cloud-storage Switches the location of the transaction logs used for PITR from disk to Cloud Storage. diff --git a/gcloud/alpha/sql/instances/point-in-time-restore b/gcloud/alpha/sql/instances/point-in-time-restore index a7827ed4d..c54f34bba 100644 --- a/gcloud/alpha/sql/instances/point-in-time-restore +++ b/gcloud/alpha/sql/instances/point-in-time-restore @@ -1,7 +1,7 @@ NAME gcloud alpha sql instances point-in-time-restore - performs a point in time restore for a Cloud SQL instance managed by Google Cloud Backup and - Disaster Recovery + Disaster Recovery Service SYNOPSIS gcloud alpha sql instances point-in-time-restore DATASOURCE TARGET @@ -14,7 +14,7 @@ SYNOPSIS DESCRIPTION (ALPHA) gcloud alpha sql instances point-in-time-restore performs a point in time restore for a Cloud SQL instance managed by Google Cloud Backup and - Disaster Recovery. + Disaster Recovery (DR) Service. EXAMPLES To perform a point in time restore from an earlier point in time: @@ -24,8 +24,8 @@ EXAMPLES POSITIONAL ARGUMENTS DATASOURCE - The Google Cloud Backup and Disaster Recovery Datasource URI, of the - form projects/{project}/locations/{region}/backupVaults/ + The Google Cloud Backup and Disaster Recovery (DR) Service Datasource + URI, of the form projects/{project}/locations/{region}/backupVaults/ {backupvault}/dataSources/{datasource}. TARGET @@ -78,7 +78,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 sql instances point-in-time-restore $ gcloud beta sql instances point-in-time-restore diff --git a/gcloud/alpha/storage/batch-operations/jobs/create b/gcloud/alpha/storage/batch-operations/jobs/create index e7388e747..fab048199 100644 --- a/gcloud/alpha/storage/batch-operations/jobs/create +++ b/gcloud/alpha/storage/batch-operations/jobs/create @@ -29,13 +29,14 @@ EXAMPLES --manifest-location=gs://my-bucket/manifest.csv --delete-object To create a batch job with the name my-job to update object metadata - Content-Disposition to inline and Content-Language to en on bucket - my-bucket where you want to match objects with the prefix prefix1 or - prefix2: + Content-Disposition to inline, Content-Language to en, and set object + retention mode to locked on bucket my-bucket where you want to match + objects with prefixes prefix1 or prefix2: $ gcloud alpha storage batch-operations jobs create my-job \ --bucket=my-bucket --included-object-prefixes=prefix1,prefix2 \ - --put-metadata=Content-Disposition=inline,Content-Language=en + --put-metadata=Content-Disposition=inline,Content-Language=en,\ + Retain-Until=2025-01-01T00:00:00Z,Retention-Mode=locked To create a batch job with the name my-job to put object event based hold on objects in bucket my-bucket with logging config enabled for @@ -107,12 +108,15 @@ REQUIRED FLAGS Content-Type={VALUE}. To set how caches should handle requests and responses, specify the key-value pair Cache-Control={VALUE}. To set custom time for Cloud Storage objects in RFC 3339 format, specify the - key-value pair Custom-Time={VALUE}. To set custom metadata on + key-value pair Custom-Time={VALUE}. To set object retention, specify + Retain-Until={TIMESTAMP} in RFC 3339 format and Retention-Mode={MODE} + where mode can be Locked or Unlocked. To set custom metadata on objects, specify key-value pairs {CUSTOM-KEY}:{VALUE}. Note that all predefined keys (e.g. Content-Disposition) are case-insensitive. Any other key that is not specified above will be treated as a custom - key. Multiple key-value pairs can be specified by separating them - with commas. For example, + key. To clear a field, provide the key with an empty value (e.g. + Content-Disposition=). Multiple key-value pairs can be specified by + separating them with commas. For example, --put-metadata=Content-Disposition=inline,Content-Encoding=gzip --rewrite-object=KEY=VALUE,[KEY=VALUE,...] diff --git a/gcloud/alpha/storage/cp b/gcloud/alpha/storage/cp index eb836a626..6d4017096 100644 --- a/gcloud/alpha/storage/cp +++ b/gcloud/alpha/storage/cp @@ -41,6 +41,10 @@ DESCRIPTION (ALPHA) Copy data between your local file system and the cloud, within the cloud, and between cloud storage providers. + Please Note - By default, the cp command does not follow directory + symlinks. You can use the --preserve-symlinks flag to follow directory + symlinks. + EXAMPLES The following command uploads all text files from the local directory to a bucket: diff --git a/gcloud/alpha/storage/objects/list b/gcloud/alpha/storage/objects/list index bf0421c37..9df9ee4c4 100644 --- a/gcloud/alpha/storage/objects/list +++ b/gcloud/alpha/storage/objects/list @@ -26,12 +26,13 @@ EXAMPLES $ gcloud alpha storage objects list gs://my-bucket/** - List all objects in bucket beginning with ``o'': + List all objects in bucket beginning with ``o'', including objects across + nested directories: - $ gcloud alpha storage objects list gs://my-bucket/o* + $ gcloud alpha storage objects list gs://my-bucket/**/o* - List all objects in bucket with JSON formatting, only returning the value - of the name metadata field: + List all objects within current directory of bucket with JSON formatting, + only returning the value of the name metadata field: $ gcloud alpha storage objects list gs://my-bucket \ --format="json(name)" diff --git a/gcloud/alpha/storage/objects/update b/gcloud/alpha/storage/objects/update index 8923ea9ee..53476999d 100644 --- a/gcloud/alpha/storage/objects/update +++ b/gcloud/alpha/storage/objects/update @@ -44,16 +44,17 @@ EXAMPLES $ gcloud alpha storage objects update gs://bucket/my-object \ --custom-metadata=key1=value1,key2=value2 - One can use wildcards (https://cloud.google.com/storage/docs/wildcards) to - update multiple objects in a single command. for instance to update all + You can use wildcards (https://cloud.google.com/storage/docs/wildcards) to + update multiple objects in a single command. For instance to update all objects to have a custom-metadata key: $ gcloud alpha storage objects update gs://bucket/** \ --custom-metadata=key1=value1,key2=value2 - Rewrite all JPEG images to the NEARLINE storage class: + Rewrite all JPEG images to the NEARLINE storage class, including objects + across nested directories: - $ gcloud alpha storage objects update gs://bucket/*.jpg \ + $ gcloud alpha storage objects update gs://bucket/**/*.jpg \ --storage-class=NEARLINE You can also provide a precondition on an object's metageneration in order diff --git a/gcloud/alpha/storage/sign-url b/gcloud/alpha/storage/sign-url index 092412eff..3c0633fbc 100644 --- a/gcloud/alpha/storage/sign-url +++ b/gcloud/alpha/storage/sign-url @@ -6,7 +6,7 @@ SYNOPSIS gcloud alpha storage sign-url URL [URL ...] [--duration=DURATION, -d DURATION; default=3600] [--headers=[KEY=VALUE,...]] - [--http-verb=HTTP_VERB, -m HTTP_VERB; default="GET"] + [--http-verb=HTTP_VERB, -m HTTP_VERB; default="GET"] [--path-style-url] [--private-key-file=PRIVATE_KEY_FILE] [--private-key-password=PRIVATE_KEY_PASSWORD, -p PRIVATE_KEY_PASSWORD] [--query-params=[KEY=VALUE,...]] [--region=REGION, -r REGION] @@ -89,6 +89,17 @@ FLAGS session, you will need to specify the x-goog-resumable:start header in the request or else signature validation will fail. + --path-style-url + Generate path-style signed URL. + + By default, virtual hosted-style signed URL is generated, except for + domain-named buckets + (https://cloud.google.com/storage/docs/domain-name-verification). Use + this flag to force the generation of path-style signed URL. Signed URL + generated for domain-named buckets is always path-style. Learn more + about the two URL styles here + (https://cloud.google.com/storage/docs/request-endpoints#xml-api). + --private-key-file=PRIVATE_KEY_FILE The service account private key used to generate the cryptographic signature for the generated URL. Must be in PKCS12 or JSON format. If diff --git a/gcloud/alpha/workstations/configs/create b/gcloud/alpha/workstations/configs/create index 3245ae707..365c7749c 100644 --- a/gcloud/alpha/workstations/configs/create +++ b/gcloud/alpha/workstations/configs/create @@ -30,7 +30,8 @@ SYNOPSIS [--service-account=SERVICE_ACCOUNT] [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--vm-tags=[VM_TAGS,...]] + [--shielded-vtpm] [--startup-script-uri=STARTUP_SCRIPT_URI] + [--vm-tags=[VM_TAGS,...]] [--accelerator-count=ACCELERATOR_COUNT : --accelerator-type=ACCELERATOR_TYPE] [--container-custom-image=CONTAINER_CUSTOM_IMAGE @@ -429,6 +430,15 @@ FLAGS --shielded-vtpm Default value is false. If set, instances will have vTPM enabled. + --startup-script-uri=STARTUP_SCRIPT_URI + Link to the startup script stored in Cloud Storage. The script is + executed on the workstation VM after it is booted. + + Example: + + $ gcloud alpha workstations configs create \ + --startup-script-uri gs://{bucket-name}/{object-name} + --vm-tags=[VM_TAGS,...] Resource manager tags to be bound to the instance. Tag keys and values have the same definition as diff --git a/gcloud/alpha/workstations/configs/update b/gcloud/alpha/workstations/configs/update index 8d322b7ce..0b47c9b1f 100644 --- a/gcloud/alpha/workstations/configs/update +++ b/gcloud/alpha/workstations/configs/update @@ -23,7 +23,8 @@ SYNOPSIS [--running-timeout=RUNNING_TIMEOUT] [--service-account=SERVICE_ACCOUNT] [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--vm-tags=[VM_TAGS,...]] + [--shielded-vtpm] [--startup-script-uri=STARTUP_SCRIPT_URI] + [--vm-tags=[VM_TAGS,...]] [--accelerator-count=ACCELERATOR_COUNT : --accelerator-type=ACCELERATOR_TYPE] [--allow-unauthenticated-cors-preflight-requests @@ -345,6 +346,15 @@ FLAGS --shielded-vtpm Default value is false. If set, instances will have vTPM enabled. + --startup-script-uri=STARTUP_SCRIPT_URI + Link to the startup script stored in Cloud Storage. The script is + executed on the workstation VM after it is booted. + + Example: + + $ gcloud alpha workstations configs update \ + --startup-script-uri gs://{bucket-name}/{object-name} + --vm-tags=[VM_TAGS,...] Resource manager tags to be bound to the instance. Tag keys and values have the same definition as diff --git a/gcloud/backup-dr/backups/fetch-for-resource-type b/gcloud/backup-dr/backups/fetch-for-resource-type new file mode 100644 index 000000000..20f0ed818 --- /dev/null +++ b/gcloud/backup-dr/backups/fetch-for-resource-type @@ -0,0 +1,115 @@ +NAME + gcloud backup-dr backups fetch-for-resource-type - fetch Backups for a + given resource type and location + +SYNOPSIS + gcloud backup-dr backups fetch-for-resource-type RESOURCE_TYPE + (--data-source=DATA_SOURCE + : --backup-vault=BACKUP_VAULT --location=LOCATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Fetch Backups for a given resource type and location. List backups for the + specified resource type for a data source. + +EXAMPLES + To list backups for Cloud SQL instance resources for data source + my-data-source with location us-central1 under backup vault, my-vault. + + $ gcloud backup-dr backups fetch-for-resource-type \ + sqladmin.googleapis.com/Instance --data-source=my-data-source \ + --backup-vault=my-vault --location=us-central1 + +POSITIONAL ARGUMENTS + RESOURCE_TYPE + Resource type for which backup plan associations should be fetched. + +REQUIRED FLAGS + Data Source resource - Data source for which backups should be fetched. + 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=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 flag 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 + The location of the Data Source. + + 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. + +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. + +BRIEF + List backups in a specified location and resource type in a project. + +NOTES + This variant is also available: + + $ gcloud alpha backup-dr backups fetch-for-resource-type + diff --git a/gcloud/backup-dr/backups/help b/gcloud/backup-dr/backups/help index d3b392d69..c6eb38caf 100644 --- a/gcloud/backup-dr/backups/help +++ b/gcloud/backup-dr/backups/help @@ -27,6 +27,9 @@ COMMANDS describe Show details of the backup. + fetch-for-resource-type + Fetch Backups for a given resource type and location. + list List Backups. diff --git a/gcloud/backup-dr/data-source-references/help b/gcloud/backup-dr/data-source-references/help index 44c9882b7..335fbf487 100644 --- a/gcloud/backup-dr/data-source-references/help +++ b/gcloud/backup-dr/data-source-references/help @@ -22,6 +22,9 @@ COMMANDS fetch-for-resource-type Fetch Data Source References for a given resource type and location. + list + List Backup and DR data source references. + NOTES This variant is also available: diff --git a/gcloud/backup-dr/data-source-references/list b/gcloud/backup-dr/data-source-references/list new file mode 100644 index 000000000..22f30d91a --- /dev/null +++ b/gcloud/backup-dr/data-source-references/list @@ -0,0 +1,89 @@ +NAME + gcloud backup-dr data-source-references list - list Backup and DR data + source references + +SYNOPSIS + gcloud backup-dr data-source-references list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List Backup and DR data source references. + +EXAMPLES + To list data source references in all locations, run: + + $ gcloud backup-dr data-source-references list + + To list data source references in a location 'my-location', run: + + $ gcloud backup-dr data-source-references list --location=my-location + +FLAGS + Location resource - Location for which data source references 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 variant is also available: + + $ gcloud alpha backup-dr data-source-references list + diff --git a/gcloud/beta/ai/endpoints/deploy-model b/gcloud/beta/ai/endpoints/deploy-model index f60920b55..30ec69217 100644 --- a/gcloud/beta/ai/endpoints/deploy-model +++ b/gcloud/beta/ai/endpoints/deploy-model @@ -8,9 +8,12 @@ SYNOPSIS [--accelerator=[count=COUNT],[type=TYPE]] [--autoscaling-metric-specs=[METRIC-NAME=TARGET,...]] [--deployed-model-id=DEPLOYED_MODEL_ID] [--enable-access-logging] - [--enable-container-logging] [--machine-type=MACHINE_TYPE] - [--max-replica-count=MAX_REPLICA_COUNT] + [--enable-container-logging] + [--idle-scaledown-period=IDLE_SCALEDOWN_PERIOD] + [--initial-replica-count=INITIAL_REPLICA_COUNT] + [--machine-type=MACHINE_TYPE] [--max-replica-count=MAX_REPLICA_COUNT] [--min-replica-count=MIN_REPLICA_COUNT] + [--min-scaleup-period=MIN_SCALEUP_PERIOD] [--multihost-gpu-node-count=MULTIHOST_GPU_NODE_COUNT] [--required-replica-count=REQUIRED_REPLICA_COUNT] [--reservation-affinity=[key=KEY], @@ -125,6 +128,15 @@ OPTIONAL FLAGS Currently, only supported for custom-trained Models and AutoML Tabular Models. + --idle-scaledown-period=IDLE_SCALEDOWN_PERIOD + Duration (in seconds) without traffic before a deployment is scaled + down to zero replicas. Defaults to 1 hour if min replica count is 0. + + --initial-replica-count=INITIAL_REPLICA_COUNT + Initial number of replicas for the deployment resources the model will + be scaled up to. Cannot be smaller than min replica count or larger + than max replica count. + --machine-type=MACHINE_TYPE The machine resources to be used for each node of this deployment. For available machine types, see @@ -144,6 +156,11 @@ OPTIONAL FLAGS NOTE: DeploymentResourcePools (model-cohosting) is currently not supported for scale-to-zero deployments. + --min-scaleup-period=MIN_SCALEUP_PERIOD + Minimum duration (in seconds) that a deployment will be scaled up + before traffic is evaluated for potential scale-down. Defaults to 1 + hour if min replica count is 0. + --multihost-gpu-node-count=MULTIHOST_GPU_NODE_COUNT The number of nodes per replica for multihost GPU deployments. Required for multihost GPU deployments. diff --git a/gcloud/beta/bigtable/help b/gcloud/beta/bigtable/help index 01072ff75..f3195fb37 100644 --- a/gcloud/beta/bigtable/help +++ b/gcloud/beta/bigtable/help @@ -42,6 +42,9 @@ GROUPS operations (BETA) Manage Cloud Bigtable operations. + schema-bundles + (BETA) Manage Bigtable schema bundles. + tables (BETA) Query Cloud Bigtable tables. diff --git a/gcloud/beta/bigtable/schema-bundles/add-iam-policy-binding b/gcloud/beta/bigtable/schema-bundles/add-iam-policy-binding new file mode 100644 index 000000000..e8ab3bcb5 --- /dev/null +++ b/gcloud/beta/bigtable/schema-bundles/add-iam-policy-binding @@ -0,0 +1,160 @@ +NAME + gcloud beta bigtable schema-bundles add-iam-policy-binding - add an IAM + policy binding to a Bigtable schema bundle + +SYNOPSIS + gcloud beta bigtable schema-bundles add-iam-policy-binding + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) --member=PRINCIPAL + --role=ROLE + [--condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Add an IAM policy binding to a Bigtable schema bundle. One binding + consists of a member, a role, and an optional condition. + +EXAMPLES + To add an IAM policy binding for the role of roles/editor for the user + 222larabrown@gmail.com with schema bundle my-schema-bundle in instance + my-instance and table my-table, run: + + $ gcloud beta bigtable schema-bundles add-iam-policy-binding \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + --member=`user:222larabrown@gmail.com` --role=`roles/editor` + + To add an IAM policy binding which expires at the end of the year 2025 for + the role of roles/bigtable.admin and the user 222larabrown@gmail.com with + schema bundle my-schema-bundle in instance my-instance and table my-table, + run: + + $ gcloud beta bigtable schema-bundles add-iam-policy-binding \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + --member=`user:222larabrown@gmail.com` \ + --role=`roles/bigtable.admin` \ + --condition=`expression=request.time < \ + timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,\ + description=Expires at midnight on 2020-12-31` + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to add the IAM policy + binding to. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=PATH_TO_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. Use a full or + relative path to a local file containing the value of condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable schema-bundles add-iam-policy-binding + + $ gcloud alpha bigtable schema-bundles add-iam-policy-binding + diff --git a/gcloud/beta/bigtable/schema-bundles/create b/gcloud/beta/bigtable/schema-bundles/create new file mode 100644 index 000000000..977cff578 --- /dev/null +++ b/gcloud/beta/bigtable/schema-bundles/create @@ -0,0 +1,100 @@ +NAME + gcloud beta bigtable schema-bundles create - create a new Bigtable schema + bundle + +SYNOPSIS + gcloud beta bigtable schema-bundles create + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + --proto-descriptors-file=PROTO_DESCRIPTORS_FILE [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new Bigtable schema bundle. + +EXAMPLES + To create a schema bundle my-schema-bundle in instance my-instance and + table my-table, using the descriptor file my-descriptor-file.pb: + + $ gcloud beta bigtable schema-bundles create my-schema-bundle \ + --instance=test-instance --table=test-table \ + --proto-descriptors-file=my-descriptor-file.pb + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to create. The arguments + in this group can be used to specify the attributes of this resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +REQUIRED FLAGS + --proto-descriptors-file=PROTO_DESCRIPTORS_FILE + Path of a file that contains a protobuf-serialized + google.protobuf.FileDescriptorSet message. If specified, the schema + bundle contains the protobuf schema. To generate the file, install and + run protoc with the following command: + + protoc --proto_path=IMPORT_PATH --include_imports --descriptor_set_out=DESCRIPTOR_OUTPUT_LOCATION path/to/file.proto + + where the --proto_path option specificies where to look for .proto + files when resolving import directives (the current directory is used + if you do not provide a value), and the --descriptor_set_out option + specifies where you want the generated FileDescriptorSet to be written. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable schema-bundles create + + $ gcloud alpha bigtable schema-bundles create + diff --git a/gcloud/beta/bigtable/schema-bundles/delete b/gcloud/beta/bigtable/schema-bundles/delete new file mode 100644 index 000000000..3bf1dcc38 --- /dev/null +++ b/gcloud/beta/bigtable/schema-bundles/delete @@ -0,0 +1,79 @@ +NAME + gcloud beta bigtable schema-bundles delete - delete a Bigtable schema + bundle + +SYNOPSIS + gcloud beta bigtable schema-bundles delete + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Bigtable schema bundle. + +EXAMPLES + To delete the schema bundle my-schema-bundle in instance my-instance and + table my-table: + + $ gcloud beta bigtable schema-bundles delete my-schema-bundle \ + --instance=test-instance --table=test-table + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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 bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable schema-bundles delete + + $ gcloud alpha bigtable schema-bundles delete + diff --git a/gcloud/beta/bigtable/schema-bundles/describe b/gcloud/beta/bigtable/schema-bundles/describe new file mode 100644 index 000000000..bc7848590 --- /dev/null +++ b/gcloud/beta/bigtable/schema-bundles/describe @@ -0,0 +1,79 @@ +NAME + gcloud beta bigtable schema-bundles describe - describe a Bigtable schema + bundle + +SYNOPSIS + gcloud beta bigtable schema-bundles describe + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Bigtable schema bundle. + +EXAMPLES + To describe the schema bundle my-schema-bundle in instance my-instance and + table my-table: + + $ gcloud beta bigtable schema-bundles describe my-schema-bundle \ + --instance=test-instance --table=test-table + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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 bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable schema-bundles describe + + $ gcloud alpha bigtable schema-bundles describe + diff --git a/gcloud/beta/bigtable/schema-bundles/get-iam-policy b/gcloud/beta/bigtable/schema-bundles/get-iam-policy new file mode 100644 index 000000000..66c59ce23 --- /dev/null +++ b/gcloud/beta/bigtable/schema-bundles/get-iam-policy @@ -0,0 +1,109 @@ +NAME + gcloud beta bigtable schema-bundles get-iam-policy - get an IAM policy on a + Bigtable schema bundle + +SYNOPSIS + gcloud beta bigtable schema-bundles get-iam-policy + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get an IAM policy on a Bigtable schema bundle. + +EXAMPLES + To get the IAM policy on the schema bundle my-schema-bundle in instance + my-instance and table my-table, run: + + $ gcloud beta bigtable schema-bundles get-iam-policy \ + my-schema-bundle --instance=`my-instance` --table=`my-table` + + See https://cloud.google.com/iam/docs/managing-policies for more + information. + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to get the IAM policy for. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable schema-bundles get-iam-policy + + $ gcloud alpha bigtable schema-bundles get-iam-policy + diff --git a/gcloud/beta/bigtable/schema-bundles/help b/gcloud/beta/bigtable/schema-bundles/help new file mode 100644 index 000000000..f96e1d7fb --- /dev/null +++ b/gcloud/beta/bigtable/schema-bundles/help @@ -0,0 +1,52 @@ +NAME + gcloud beta bigtable schema-bundles - manage Bigtable schema bundles + +SYNOPSIS + gcloud beta bigtable schema-bundles COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Bigtable schema bundles. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + (BETA) Add an IAM policy binding to a Bigtable schema bundle. + + create + (BETA) Create a new Bigtable schema bundle. + + delete + (BETA) Delete a Bigtable schema bundle. + + describe + (BETA) Describe a Bigtable schema bundle. + + get-iam-policy + (BETA) Get an IAM policy on a Bigtable schema bundle. + + list + (BETA) List all schema bundles of a Bigtable table. + + remove-iam-policy-binding + (BETA) Remove an IAM policy binding from a Bigtable schema bundle. + + set-iam-policy + (BETA) Set an IAM policy on a Bigtable schema bundle. + + update + (BETA) Update an existing Bigtable schema bundle. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable schema-bundles + + $ gcloud alpha bigtable schema-bundles + diff --git a/gcloud/beta/bigtable/schema-bundles/list b/gcloud/beta/bigtable/schema-bundles/list new file mode 100644 index 000000000..9a8cbdb09 --- /dev/null +++ b/gcloud/beta/bigtable/schema-bundles/list @@ -0,0 +1,107 @@ +NAME + gcloud beta bigtable schema-bundles list - list all schema bundles of a + Bigtable table + +SYNOPSIS + gcloud beta bigtable schema-bundles list + (--table=TABLE : --instance=INSTANCE) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all schema bundles of a Bigtable table. + +EXAMPLES + To list the schema bundles in instance my-instance and table my-table: + + $ gcloud beta bigtable schema-bundles list --instance=my-instance \ + --table=my-table + + To list all schema bundles that match the given filter: + + $ gcloud beta bigtable schema-bundles list --instance=my-instance \ + --table=my-table --filter="name=( `NAME` ... )" + +REQUIRED FLAGS + Table resource - Bigtable table for which to list all schema bundles. 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 --table 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. + + --table=TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument --table on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument --table on the command line with a fully + specified name; + ▸ provide the argument --instance 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 bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable schema-bundles list + + $ gcloud alpha bigtable schema-bundles list + diff --git a/gcloud/beta/bigtable/schema-bundles/remove-iam-policy-binding b/gcloud/beta/bigtable/schema-bundles/remove-iam-policy-binding new file mode 100644 index 000000000..19c1ce3ec --- /dev/null +++ b/gcloud/beta/bigtable/schema-bundles/remove-iam-policy-binding @@ -0,0 +1,165 @@ +NAME + gcloud beta bigtable schema-bundles remove-iam-policy-binding - remove an + IAM policy binding from a Bigtable schema bundle + +SYNOPSIS + gcloud beta bigtable schema-bundles remove-iam-policy-binding + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) --member=PRINCIPAL + --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=PATH_TO_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Remove an IAM policy binding from a Bigtable schema bundle. One + binding consists of a member, a role, and an optional condition. + +EXAMPLES + To remove an IAM policy binding for the role of roles/editor for the user + 222larabrown@gmail.com with schema bundle my-schema-bundle in instance + my-instance and table my-table, run: + + $ gcloud beta bigtable schema-bundles remove-iam-policy-binding \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + --member=`user:222larabrown@gmail.com` --role=`roles/editor` + + To remove an IAM policy binding which expires at the end of the year 2025 + for the role of roles/bigtable.admin and the user 222larabrown@gmail.com + with schema bundle my-schema-bundle in instance my-instance and table + my-table, run: + + $ gcloud beta bigtable schema-bundles remove-iam-policy-binding \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + --member=`user:222larabrown@gmail.com` \ + --role=`roles/bigtable.admin` \ + --condition=`expression=request.time < \ + timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,\ + description=Expires at midnight on 2020-12-31` + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to remove the IAM policy + binding 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=PATH_TO_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. Use a full or + relative path to a local file containing the value of condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable schema-bundles remove-iam-policy-binding + + $ gcloud alpha bigtable schema-bundles remove-iam-policy-binding + diff --git a/gcloud/beta/bigtable/schema-bundles/set-iam-policy b/gcloud/beta/bigtable/schema-bundles/set-iam-policy new file mode 100644 index 000000000..00d42163b --- /dev/null +++ b/gcloud/beta/bigtable/schema-bundles/set-iam-policy @@ -0,0 +1,90 @@ +NAME + gcloud beta bigtable schema-bundles set-iam-policy - set an IAM policy on a + Bigtable schema bundle + +SYNOPSIS + gcloud beta bigtable schema-bundles set-iam-policy + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Set an IAM policy on a Bigtable schema bundle. + +EXAMPLES + To set the IAM policy from file my-policy on the schema bundle + my-schema-bundle in instance my-instance and table my-table, run: + + $ gcloud beta bigtable schema-bundles set-iam-policy \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + my-policy + + See https://cloud.google.com/iam/docs/managing-policies for more + information. + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to set the IAM policy on. + 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable schema-bundles set-iam-policy + + $ gcloud alpha bigtable schema-bundles set-iam-policy + diff --git a/gcloud/beta/bigtable/schema-bundles/update b/gcloud/beta/bigtable/schema-bundles/update new file mode 100644 index 000000000..840bb51bc --- /dev/null +++ b/gcloud/beta/bigtable/schema-bundles/update @@ -0,0 +1,103 @@ +NAME + gcloud beta bigtable schema-bundles update - update an existing Bigtable + schema bundle + +SYNOPSIS + gcloud beta bigtable schema-bundles update + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + --proto-descriptors-file=PROTO_DESCRIPTORS_FILE [--async] + [--ignore-warnings] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an existing Bigtable schema bundle. + +EXAMPLES + To update a schema bundle my-schema-bundle in instance my-instance and + table my-table, using the descriptor file my-descriptor-file.pb: + + $ gcloud beta bigtable schema-bundles update my-schema-bundle \ + --instance=my-instance --table=my-table \ + --proto-descriptors-file=my-descriptor-file.pb + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +REQUIRED FLAGS + --proto-descriptors-file=PROTO_DESCRIPTORS_FILE + Path of a file that contains a protobuf-serialized + google.protobuf.FileDescriptorSet message. If specified, the schema + bundle contains the protobuf schema. To generate the file, install and + run protoc with the following command: + + protoc --proto_path=IMPORT_PATH --include_imports --descriptor_set_out=DESCRIPTOR_OUTPUT_LOCATION path/to/file.proto + + where the --proto_path option specificies where to look for .proto + files when resolving import directives (the current directory is used + if you do not provide a value), and the --descriptor_set_out option + specifies where you want the generated FileDescriptorSet to be written. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --ignore-warnings + If true, backwards incompatible changes will be allowed. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable schema-bundles update + + $ gcloud alpha bigtable schema-bundles update + diff --git a/gcloud/beta/compute/advice/calendar-mode b/gcloud/beta/compute/advice/calendar-mode index a073cf7ee..2941d22b3 100644 --- a/gcloud/beta/compute/advice/calendar-mode +++ b/gcloud/beta/compute/advice/calendar-mode @@ -152,8 +152,8 @@ OPTIONAL FLAGS gcloud compute advice calendar-mode --location-policy=us-central1-a=allow,us-central1-b=deny --region=REGION - Region of the to None. If not specified, you might be prompted to - select a region (interactive mode only). + Region of the resources to get advice on. If not specified, you might + be prompted to select a region (interactive mode only). To avoid prompting when this flag is omitted, you can set the compute/region property: diff --git a/gcloud/beta/compute/backend-services/create b/gcloud/beta/compute/backend-services/create index 0dfd6e48c..8af4fe5f8 100644 --- a/gcloud/beta/compute/backend-services/create +++ b/gcloud/beta/compute/backend-services/create @@ -43,9 +43,7 @@ SYNOPSIS [--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE] [--subsetting-policy=SUBSETTING_POLICY; default="NONE"] [--subsetting-subset-size=SUBSETTING_SUBSET_SIZE] - [--timeout=TIMEOUT; default="30s"] - [--tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG],[sni=SNI]] - [--tracking-mode=TRACKING_MODE] + [--timeout=TIMEOUT; default="30s"] [--tracking-mode=TRACKING_MODE] [--zonal-affinity-spillover=ZONAL_AFFINITY_SPILLOVER] [--zonal-affinity-spillover-ratio=ZONAL_AFFINITY_SPILLOVER_RATIO] [--cache-key-query-string-blacklist=[QUERY_STRING,...] @@ -54,7 +52,9 @@ SYNOPSIS | --custom-metrics-file=[CUSTOM_METRICS,...]] [--global | --region=REGION] [--global-health-checks | --health-checks-region=HEALTH_CHECKS_REGION] - [GCLOUD_WIDE_FLAG ...] + [--identity=IDENTITY + | --tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG], + [sni=SNI]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute backend-services create creates a backend @@ -742,14 +742,6 @@ FLAGS The full range of timeout values allowed is 1 - 2,147,483,647 seconds. - --tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG],[sni=SNI] - Configuration for Backend Authenticated TLS and mTLS. May only be - specified when the backend protocol is SSL, HTTPS or HTTP2. - - Example: $ gcloud beta compute backend-services create \ - --tls-settings='sni=example.com,authenticationConfig=${AUTH_CONF\ - IG_NAME}' - --tracking-mode=TRACKING_MODE Specifies the connection key used for connection tracking. The default value is PER_CONNECTION. Applicable only for backend service-based @@ -927,6 +919,37 @@ FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + At most one of these can be specified: + + --identity=IDENTITY + Assigns the Managed Identity for the BackendService Workload. Use + this property to configure the load balancer back-end to use + certificates and roots of trust provisioned by the Managed Workload + Identity system. The identity property is the scheme-less SPIFFE ID + to use in the SVID presented by the Load Balancer Workload. The + SPIFFE ID must be a resource starting with the trustDomain property + value, followed by the path to the Managed Workload Identity. + Supported SPIFFE ID format: + ///ns//sa/ The Trust Domain within + the Managed Identity must refer to a valid Workload Identity Pool. + The TrustConfig and CertificateIssuanceConfig will be inherited from + the Workload Identity Pool. Restrictions: If you set the identity + property, you cannot manually set the following fields: + tlsSettings.sni, tlsSettings.subjectAltNames, + tlsSettings.authenticationConfig. When defining a identity for a + RegionBackendServices, the corresponding Workload Identity Pool must + have a ca_pool configured in the same region. The system will set up + a read-only tlsSettings.authenticationConfig for the Managed + Identity. + + --tls-settings=[authenticationConfig=AUTHENTICATIONCONFIG],[sni=SNI] + Configuration for Backend Authenticated TLS and mTLS. May only be + specified when the backend protocol is SSL, HTTPS or HTTP2. + + Example: $ gcloud beta compute backend-services create \ + --tls-settings='sni=example.com,authenticationConfig=${AUTH_CONF\ + IG_NAME}' + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/commitments/create b/gcloud/beta/compute/commitments/create index 4f345dd6c..e3af9f630 100644 --- a/gcloud/beta/compute/commitments/create +++ b/gcloud/beta/compute/commitments/create @@ -112,9 +112,10 @@ OPTIONAL FLAGS compute-optimized-c3d, compute-optimized-h3, compute-optimized-h4d, general-purpose, general-purpose-c4, general-purpose-c4a, general-purpose-c4d, general-purpose-e2, general-purpose-n2, - general-purpose-n2d, general-purpose-n4, general-purpose-t2d, - graphics-optimized, memory-optimized, memory-optimized-m3, - memory-optimized-m4, memory-optimized-m4-6tb, memory-optimized-x4-16tb, + general-purpose-n2d, general-purpose-n4, general-purpose-n4d, + general-purpose-t2d, graphics-optimized, graphics-optimized-g4, + memory-optimized, memory-optimized-m3, memory-optimized-m4, + memory-optimized-m4-6tb, memory-optimized-x4-16tb, memory-optimized-x4-24tb, memory-optimized-x4-32tb, storage-optimized-z3. diff --git a/gcloud/beta/compute/health-checks/create/grpc-with-tls b/gcloud/beta/compute/health-checks/create/grpc-with-tls new file mode 100644 index 000000000..fd9b35ae8 --- /dev/null +++ b/gcloud/beta/compute/health-checks/create/grpc-with-tls @@ -0,0 +1,121 @@ +NAME + gcloud beta compute health-checks create grpc-with-tls - create a gRPC with + TLS health check to monitor load balanced instances + +SYNOPSIS + gcloud beta compute health-checks create grpc-with-tls NAME + [--check-interval=CHECK_INTERVAL; default="5s"] + [--description=DESCRIPTION] [--enable-logging] + [--grpc-service-name=GRPC_SERVICE_NAME] + [--healthy-threshold=HEALTHY_THRESHOLD; default=2] + [--timeout=TIMEOUT; default="5s"] + [--unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2] + [--global | --region=REGION] [--port=PORT --use-serving-port] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute health-checks create grpc-with-tls is used to + create a non-legacy health check using the gRPC with TLS protocol. You can + use this health check for Google Cloud load balancers or for managed + instance group autohealing. For more information, see the health checks + overview at: + https://cloud.google.com/load-balancing/docs/health-check-concepts + +POSITIONAL ARGUMENTS + NAME + Name of the gRPC with TLS health check to create. + +FLAGS + --check-interval=CHECK_INTERVAL; default="5s" + How often to perform a health check for an instance. For example, + specifying 10s will run the check every 10 seconds. The default value + is 5s. See $ gcloud topic datetimes for information on duration + formats. + + --description=DESCRIPTION + An optional string description for the gRPC with TLS health check. + + --enable-logging + Enable logging of health check probe results to Stackdriver. Logging is + disabled by default. + + Use --no-enable-logging to disable logging. + + --grpc-service-name=GRPC_SERVICE_NAME + An optional gRPC service name string of up to 1024 characters to + include in the gRPC health check request. Only ASCII characters are + allowed. + + --healthy-threshold=HEALTHY_THRESHOLD; default=2 + The number of consecutive successful health checks before an unhealthy + instance is marked as healthy. The default is 2. + + --timeout=TIMEOUT; default="5s" + If Google Compute Engine doesn't receive a healthy response from the + instance by the time specified by the value of this flag, the health + check request is considered a failure. For example, specifying 10s will + cause the check to wait for 10 seconds before considering the request a + failure. The default value is 5s. See $ gcloud topic datetimes for + information on duration formats. + + --unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2 + The number of consecutive health check failures before a healthy + instance is marked as unhealthy. The default is 2. + + At most one of these can be specified: + + --global + If set, the gRPC with TLS health check is global. + + --region=REGION + Region of the gRPC with TLS health check to create. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + These flags configure the port that the health check monitors. + + --port=PORT + The TCP port number that this health check monitors. + + --use-serving-port + If given, use the "serving port" for health checks: + + ▸ When health checking network endpoints in a Network Endpoint + Group, use the port specified with each endpoint. + --use-serving-port must be used when using a Network Endpoint Group + as a backend as this flag specifies the portSpecification option + for a Health Check object. + ▸ When health checking other backends, use the port of the backend + service. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-checks create grpc-with-tls + + $ gcloud alpha compute health-checks create grpc-with-tls + diff --git a/gcloud/beta/compute/health-checks/create/help b/gcloud/beta/compute/health-checks/create/help index f1f35d7c4..39749b029 100644 --- a/gcloud/beta/compute/health-checks/create/help +++ b/gcloud/beta/compute/health-checks/create/help @@ -19,6 +19,10 @@ COMMANDS grpc (BETA) Create a gRPC health check to monitor load balanced instances. + grpc-with-tls + (BETA) Create a gRPC with TLS health check to monitor load balanced + instances. + http (BETA) Create a HTTP health check to monitor load balanced instances. diff --git a/gcloud/beta/compute/health-checks/update/grpc-with-tls b/gcloud/beta/compute/health-checks/update/grpc-with-tls new file mode 100644 index 000000000..519c798e9 --- /dev/null +++ b/gcloud/beta/compute/health-checks/update/grpc-with-tls @@ -0,0 +1,117 @@ +NAME + gcloud beta compute health-checks update grpc-with-tls - update a gRPC with + TLS health check + +SYNOPSIS + gcloud beta compute health-checks update grpc-with-tls NAME + [--check-interval=CHECK_INTERVAL] [--description=DESCRIPTION] + [--enable-logging] [--grpc-service-name=GRPC_SERVICE_NAME] + [--healthy-threshold=HEALTHY_THRESHOLD] [--timeout=TIMEOUT] + [--unhealthy-threshold=UNHEALTHY_THRESHOLD] + [--global | --region=REGION] [--port=PORT --use-serving-port] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute health-checks update grpc-with-tls is used to + update an existing gRPC with TLS health check. Only arguments passed in + will be updated on the health check. Other attributes will remain + unaffected. + +POSITIONAL ARGUMENTS + NAME + Name of the gRPC with TLS health check to update. + +FLAGS + --check-interval=CHECK_INTERVAL + How often to perform a health check for an instance. For example, + specifying 10s will run the check every 10 seconds. See $ gcloud topic + datetimes for information on duration formats. + + --description=DESCRIPTION + A textual description for the gRPC with TLS health check. Pass in an + empty string to unset. + + --enable-logging + Enable logging of health check probe results to Stackdriver. Logging is + disabled by default. + + Use --no-enable-logging to disable logging. + + --grpc-service-name=GRPC_SERVICE_NAME + An optional gRPC service name string of up to 1024 characters to + include in the gRPC health check request. Pass in an empty string to + unset. Only ASCII characters are allowed. + + --healthy-threshold=HEALTHY_THRESHOLD + The number of consecutive successful health checks before an unhealthy + instance is marked as healthy. + + --timeout=TIMEOUT + If Google Compute Engine doesn't receive a healthy response from the + instance by the time specified by the value of this flag, the health + check request is considered a failure. For example, specifying 10s will + cause the check to wait for 10 seconds before considering the request a + failure. See $ gcloud topic datetimes for information on duration + formats. + + --unhealthy-threshold=UNHEALTHY_THRESHOLD + The number of consecutive health check failures before a healthy + instance is marked as unhealthy. + + At most one of these can be specified: + + --global + If set, the gRPC with TLS health check is global. + + --region=REGION + Region of the gRPC with TLS health check to update. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + These flags configure the port that the health check monitors. + + --port=PORT + The TCP port number that this health check monitors. + + --use-serving-port + If given, use the "serving port" for health checks: + + ▸ When health checking network endpoints in a Network Endpoint + Group, use the port specified with each endpoint. + --use-serving-port must be used when using a Network Endpoint Group + as a backend as this flag specifies the portSpecification option + for a Health Check object. + ▸ When health checking other backends, use the port of the backend + service. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute health-checks update grpc-with-tls + + $ gcloud alpha compute health-checks update grpc-with-tls + diff --git a/gcloud/beta/compute/health-checks/update/help b/gcloud/beta/compute/health-checks/update/help index 7cd4afad4..815e85cf2 100644 --- a/gcloud/beta/compute/health-checks/update/help +++ b/gcloud/beta/compute/health-checks/update/help @@ -19,6 +19,9 @@ COMMANDS grpc (BETA) Update a gRPC health check. + grpc-with-tls + (BETA) Update a gRPC with TLS health check. + http (BETA) Update a HTTP health check. diff --git a/gcloud/beta/compute/help b/gcloud/beta/compute/help index 78ab4aab5..385e0f396 100644 --- a/gcloud/beta/compute/help +++ b/gcloud/beta/compute/help @@ -245,6 +245,9 @@ GROUPS vpn-tunnels (BETA) Read and manipulate Compute Engine VPN tunnels. + zone-vm-extension-policies + (BETA) Compute Engine zone VM extension policies. + zones (BETA) List Compute Engine zones. diff --git a/gcloud/beta/compute/interconnects/attachments/help b/gcloud/beta/compute/interconnects/attachments/help index f5a629b24..0418e2484 100644 --- a/gcloud/beta/compute/interconnects/attachments/help +++ b/gcloud/beta/compute/interconnects/attachments/help @@ -23,6 +23,9 @@ GROUPS groups (BETA) Create or manipulate interconnect attachment groups. + l2-forwarding + (BETA) Create or manipulate dedicated interconnect attachments. + partner (BETA) Create or manipulate partner interconnect attachments. diff --git a/gcloud/beta/compute/interconnects/attachments/l2-forwarding/add-mapping b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/add-mapping new file mode 100644 index 000000000..8bcdf69e6 --- /dev/null +++ b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/add-mapping @@ -0,0 +1,76 @@ +NAME + gcloud beta compute interconnects attachments l2-forwarding add-mapping - + add new vlan to ip mapping rule to an L2-forwarding attachment + +SYNOPSIS + gcloud beta compute interconnects attachments l2-forwarding add-mapping + NAME --vlan-key=VLAN_KEY [--appliance-ip-address=ADDRESSES] + [--appliance-name=APPLIANCE_NAME] + [--inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS], + [innerVlanTags=INNERVLANTAGS]] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute interconnects attachments l2-forwarding + add-mapping add new vlan to ip mapping rule to an L2-forwarding attachment. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to patch. + +REQUIRED FLAGS + --vlan-key=VLAN_KEY + Desired VLAN key for L2 forwarding mapping for the attachment. If not + supplied, all mappings will be displayed. + +OPTIONAL FLAGS + --appliance-ip-address=ADDRESSES + A single IPv4 or IPv6 address used as the destination IP address for + ingress packets that match on a VLAN tag, but do not match a more + specific inner VLAN tag. + + --appliance-name=APPLIANCE_NAME + The name of the L2 appliance mapping rule. + + --inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS],[innerVlanTags=INNERVLANTAGS] + A list of mapping rules from inner VLAN tags to IP addresses. If the + inner VLAN is not explicitly mapped to an IP address range, the + applianceIpAddress is used. + + --region=REGION + Region of the interconnect attachment to patch. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding add-mapping + + $ gcloud alpha compute interconnects attachments l2-forwarding \ + add-mapping + diff --git a/gcloud/beta/compute/interconnects/attachments/l2-forwarding/create b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/create new file mode 100644 index 000000000..8c61dff23 --- /dev/null +++ b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/create @@ -0,0 +1,132 @@ +NAME + gcloud beta compute interconnects attachments l2-forwarding create - create + a Compute Engine L2 forwarding interconnect attachment + +SYNOPSIS + gcloud beta compute interconnects attachments l2-forwarding create NAME + --geneve-vni=GENEVE_HEADER --interconnect=INTERCONNECT + --network=NETWORK + --tunnel-endpoint-ip-address=TUNNEL_ENDPOINT_IP_ADDRESS + [--bandwidth=BANDWIDTH] + [--default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS] + [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU] + [--region=REGION] [--resource-manager-tags=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute interconnects attachments l2-forwarding create + is used to create a L2 forwarding interconnect attachments. An interconnect + attachment is what binds the underlying connectivity of an interconnect to + a path into and out of the customer's cloud network. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to create. + +REQUIRED FLAGS + --geneve-vni=GENEVE_HEADER + A VNI identier for Geneve header, as defined in + https://datatracker.ietf.org/doc/html/rfc8926, used for L2 forwarding. + + --interconnect=INTERCONNECT + The interconnect for the interconnect attachment + + --network=NETWORK + The Google Network to use for L2 forwarding. + + --tunnel-endpoint-ip-address=TUNNEL_ENDPOINT_IP_ADDRESS + A single IPv4 or IPv6 address. This address will be used as the source + IP address for L2 forwarding packets sent to the appliances, and must + be used as the destination IP address for packets that should be sent + out through this attachment. + +OPTIONAL FLAGS + --bandwidth=BANDWIDTH + Provisioned capacity of the attachment. BANDWIDTH must be one of: + + 50m + 50 Mbit/s + 100m + 100 Mbit/s + 200m + 200 Mbit/s + 300m + 300 Mbit/s + 400m + 400 Mbit/s + 500m + 500 Mbit/s + 1g + 1 Gbit/s + 2g + 2 Gbit/s + 5g + 5 Gbit/s + 10g + 10 Gbit/s + 20g + 20 Gbit/s + 50g + 50 Gbit/s + 100g + 100 Gbit/s + + --default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS + A single IPv4 or IPv6 address used as the default destination IP when + there is no VLAN mapping result found for L2 forwarding. Unset field + indicates the unmatched packet should be dropped. + + --description=DESCRIPTION + Human-readable plain-text description of attachment. + + --enable-admin + Administrative status of the interconnect attachment. If not provided + on creation, defaults to enabled. When this is enabled, the attachment + is operational and will carry traffic. Use --no-enable-admin to disable + it. + + --mtu=MTU + Maximum transmission unit (MTU) is the size of the largest IP packet + passing through this interconnect attachment. Must be one of 1440, + 1460, 1500, or 8896. If not specified, the value will default to 1440. + + --region=REGION + Region of the interconnect attachment to create. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the + interconnect. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding create + + $ gcloud alpha compute interconnects attachments l2-forwarding create + diff --git a/gcloud/beta/compute/interconnects/attachments/l2-forwarding/describe-mapping b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/describe-mapping new file mode 100644 index 000000000..0dc32bb8a --- /dev/null +++ b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/describe-mapping @@ -0,0 +1,63 @@ +NAME + gcloud beta compute interconnects attachments l2-forwarding + describe-mapping - describe a Compute Engine L2 forwarding interconnect + attachment + +SYNOPSIS + gcloud beta compute interconnects attachments l2-forwarding + describe-mapping NAME --vlan-key=VLAN_KEY [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute interconnects attachments l2-forwarding + describe-mapping displays all data associated with Compute Engine + interconnect attachment in a project. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to describe. + +REQUIRED FLAGS + --vlan-key=VLAN_KEY + Desired VLAN key for L2 forwarding mapping for the attachment. If not + supplied, all mappings will be displayed. + +OPTIONAL FLAGS + --region=REGION + Region of the interconnect attachment to describe. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding \ + describe-mapping + + $ gcloud alpha compute interconnects attachments l2-forwarding \ + describe-mapping + diff --git a/gcloud/beta/compute/interconnects/attachments/l2-forwarding/help b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/help new file mode 100644 index 000000000..850103bf3 --- /dev/null +++ b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/help @@ -0,0 +1,56 @@ +NAME + gcloud beta compute interconnects attachments l2-forwarding - create or + manipulate dedicated interconnect attachments + +SYNOPSIS + gcloud beta compute interconnects attachments l2-forwarding COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create or manipulate L2 Forwarding Interconnect attachments. + + For more information about about interconnect attachments for L2 Forwaring + Interconnect, see the documentation for L2 Forwarding interconnect + attachments + (https://cloud.google.com/network-connectivity/docs/interconnect/how-to/l2-forwarding/creating-l2-attachments). + + See also: Interconnect attachments API + (https://cloud.google.com/compute/docs/reference/rest/v1/interconnectAttachments). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-mapping + (BETA) Add new vlan to ip mapping rule to an L2-forwarding attachment. + + create + (BETA) Create a Compute Engine L2 forwarding interconnect attachment. + + describe-mapping + (BETA) Describe a Compute Engine L2 forwarding interconnect attachment. + + list-mapping + (BETA) List Google Compute Engine interconnect attachments. + + remove-mapping + (BETA) Remove vlan to ip mapping rule to an L2-forwarding attachment. + + update + (BETA) Update a Compute Engine L2 forwarding interconnect attachment. + + update-mapping + (BETA) Update vlan to ip mapping rule to an L2-forwarding attachment. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding + + $ gcloud alpha compute interconnects attachments l2-forwarding + diff --git a/gcloud/beta/compute/interconnects/attachments/l2-forwarding/list-mapping b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/list-mapping new file mode 100644 index 000000000..3350a2433 --- /dev/null +++ b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/list-mapping @@ -0,0 +1,110 @@ +NAME + gcloud beta compute interconnects attachments l2-forwarding list-mapping - + list Google Compute Engine interconnect attachments + +SYNOPSIS + gcloud beta compute interconnects attachments l2-forwarding list-mapping + NAME [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute interconnects attachments l2-forwarding + list-mapping displays all Google Compute Engine interconnect attachments in + a project. + + By default, interconnect attachments from all regions are listed. The + results can be narrowed down using a filter: --filter="region:( REGION ... + )". + +EXAMPLES + To list all interconnect attachments in a project in table form, run: + + $ gcloud beta compute interconnects attachments l2-forwarding \ + list-mapping + + To list the URIs of all interconnect attachments in a project, run: + + $ gcloud beta compute interconnects attachments l2-forwarding \ + list-mapping --uri + + To list all interconnect attachments in the us-central1 and europe-west1 + regions, run: + + $ gcloud beta compute interconnects attachments l2-forwarding \ + list-mapping --filter="region:( us-central1 europe-west1 )" + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to describe. + +FLAGS + --region=REGION + Region of the interconnect attachment to describe. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding list-mapping + + $ gcloud alpha compute interconnects attachments l2-forwarding \ + list-mapping + diff --git a/gcloud/beta/compute/interconnects/attachments/l2-forwarding/remove-mapping b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/remove-mapping new file mode 100644 index 000000000..1b637396a --- /dev/null +++ b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/remove-mapping @@ -0,0 +1,61 @@ +NAME + gcloud beta compute interconnects attachments l2-forwarding remove-mapping + - remove vlan to ip mapping rule to an L2-forwarding attachment + +SYNOPSIS + gcloud beta compute interconnects attachments l2-forwarding remove-mapping + NAME --vlan-key=VLAN_KEY [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute interconnects attachments l2-forwarding + remove-mapping remove vlan to ip mapping rule to an L2-forwarding + attachment. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to create. + +REQUIRED FLAGS + --vlan-key=VLAN_KEY + Desired VLAN key for L2 forwarding mapping for the attachment. If not + supplied, all mappings will be displayed. + +OPTIONAL FLAGS + --region=REGION + Region of the interconnect attachment to create. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding \ + remove-mapping + + $ gcloud alpha compute interconnects attachments l2-forwarding \ + remove-mapping + diff --git a/gcloud/beta/compute/interconnects/attachments/l2-forwarding/update b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/update new file mode 100644 index 000000000..c57030320 --- /dev/null +++ b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/update @@ -0,0 +1,143 @@ +NAME + gcloud beta compute interconnects attachments l2-forwarding update - update + a Compute Engine L2 forwarding interconnect attachment + +SYNOPSIS + gcloud beta compute interconnects attachments l2-forwarding update NAME + [--bandwidth=BANDWIDTH] + [--default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS] + [--description=DESCRIPTION] [--enable-admin] + [--geneve-vni=GENEVE_HEADER] [--mtu=MTU] [--region=REGION] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute interconnects attachments l2-forwarding update + is used to update interconnect attachments. An interconnect attachment is + what binds the underlying connectivity of an interconnect to a path into + and out of the customer's cloud network. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to patch. + +FLAGS + --bandwidth=BANDWIDTH + Provisioned capacity of the attachment. BANDWIDTH must be one of: + + 50m + 50 Mbit/s + 100m + 100 Mbit/s + 200m + 200 Mbit/s + 300m + 300 Mbit/s + 400m + 400 Mbit/s + 500m + 500 Mbit/s + 1g + 1 Gbit/s + 2g + 2 Gbit/s + 5g + 5 Gbit/s + 10g + 10 Gbit/s + 20g + 20 Gbit/s + 50g + 50 Gbit/s + 100g + 100 Gbit/s + + --default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS + A single IPv4 or IPv6 address used as the default destination IP when + there is no VLAN mapping result found for L2 forwarding. Unset field + indicates the unmatched packet should be dropped. + + --description=DESCRIPTION + Human-readable plain-text description of attachment. + + --enable-admin + Administrative status of the interconnect attachment. If not provided + on creation, defaults to enabled. When this is enabled, the attachment + is operational and will carry traffic. Use --no-enable-admin to disable + it. + + --geneve-vni=GENEVE_HEADER + A VNI identier for Geneve header, as defined in + https://datatracker.ietf.org/doc/html/rfc8926, used for L2 forwarding. + + --mtu=MTU + Maximum transmission unit (MTU) is the size of the largest IP packet + passing through this interconnect attachment. Must be one of 1440, + 1460, 1500, or 8896. If not specified, the value will default to 1440. + + --region=REGION + Region of the interconnect attachment to patch. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta compute interconnects attachments l2-forwarding \ + update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta compute interconnects attachments l2-forwarding \ + update --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding update + + $ gcloud alpha compute interconnects attachments l2-forwarding update + diff --git a/gcloud/beta/compute/interconnects/attachments/l2-forwarding/update-mapping b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/update-mapping new file mode 100644 index 000000000..24425e793 --- /dev/null +++ b/gcloud/beta/compute/interconnects/attachments/l2-forwarding/update-mapping @@ -0,0 +1,78 @@ +NAME + gcloud beta compute interconnects attachments l2-forwarding update-mapping + - update vlan to ip mapping rule to an L2-forwarding attachment + +SYNOPSIS + gcloud beta compute interconnects attachments l2-forwarding update-mapping + NAME --vlan-key=VLAN_KEY [--appliance-ip-address=ADDRESSES] + [--appliance-name=APPLIANCE_NAME] + [--inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS], + [innerVlanTags=INNERVLANTAGS]] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta compute interconnects attachments l2-forwarding + update-mapping update vlan to ip mapping rule to an L2-forwarding + attachment. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to create. + +REQUIRED FLAGS + --vlan-key=VLAN_KEY + Desired VLAN key for L2 forwarding mapping for the attachment. If not + supplied, all mappings will be displayed. + +OPTIONAL FLAGS + --appliance-ip-address=ADDRESSES + A single IPv4 or IPv6 address used as the destination IP address for + ingress packets that match on a VLAN tag, but do not match a more + specific inner VLAN tag. + + --appliance-name=APPLIANCE_NAME + The name of the L2 appliance mapping rule. + + --inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS],[innerVlanTags=INNERVLANTAGS] + A list of mapping rules from inner VLAN tags to IP addresses. If the + inner VLAN is not explicitly mapped to an IP address range, the + applianceIpAddress is used. + + --region=REGION + Region of the interconnect attachment to create. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud compute interconnects attachments l2-forwarding \ + update-mapping + + $ gcloud alpha compute interconnects attachments l2-forwarding \ + update-mapping + diff --git a/gcloud/beta/compute/networks/subnets/create b/gcloud/beta/compute/networks/subnets/create index dcf499390..22d003555 100644 --- a/gcloud/beta/compute/networks/subnets/create +++ b/gcloud/beta/compute/networks/subnets/create @@ -7,6 +7,7 @@ SYNOPSIS [--description=DESCRIPTION] [--enable-flow-logs] [--enable-private-ip-google-access] [--external-ipv6-prefix=EXTERNAL_IPV6_PREFIX] + [--internal-ipv6-prefix=INTERNAL_IPV6_PREFIX] [--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] @@ -63,10 +64,20 @@ OPTIONAL FLAGS For example, --external-ipv6-prefix=2600:1901:0:0:0:0:0:0/64 + --internal-ipv6-prefix=INTERNAL_IPV6_PREFIX + The /64 internal IPv6 CIDR range to assign to this subnet. The range + must be associated with an IPv6 BYOIP sub-prefix that is defined by the + --ip-collection flag. If you specify --ip-collection but not + --internal-ipv6-prefix, a random /64 range is allocated from the + sub-prefix. + + For example, --internal-ipv6-prefix 2600:1901:0:0:0:0:0:0/64 + --ip-collection=IP_COLLECTION Resource reference to a public delegated prefix. The PublicDelegatedPrefix must be a sub-prefix in - EXTERNAL_IPV6_SUBNETWORK_CREATION mode. + EXTERNAL_IPV6_SUBNETWORK_CREATION or INTERNAL_IPV6_SUBNETWORK_CREATION + mode. --ipv6-access-type=IPV6_ACCESS_TYPE IPv6 access type can be specified only when the subnet is created, or diff --git a/gcloud/beta/compute/networks/subnets/update b/gcloud/beta/compute/networks/subnets/update index b98697c82..5010de323 100644 --- a/gcloud/beta/compute/networks/subnets/update +++ b/gcloud/beta/compute/networks/subnets/update @@ -7,6 +7,7 @@ SYNOPSIS [--add-secondary-ranges-with-reserved-internal-range=RANGE_NAME=INTERNAL_RANGE_URL, [...]] [--drain-timeout=DRAIN_TIMEOUT; default="0s"] [--external-ipv6-prefix=EXTERNAL_IPV6_PREFIX] + [--internal-ipv6-prefix=INTERNAL_IPV6_PREFIX] [--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] @@ -67,10 +68,20 @@ FLAGS For example, --external-ipv6-prefix=2600:1901:0:0:0:0:0:0/64 + --internal-ipv6-prefix=INTERNAL_IPV6_PREFIX + The /64 internal IPv6 CIDR range to assign to this subnet. The range + must be associated with an IPv6 BYOIP sub-prefix that is defined by the + --ip-collection flag. If you specify --ip-collection but not + --internal-ipv6-prefix, a random /64 range is allocated from the + sub-prefix. + + For example, --internal-ipv6-prefix 2600:1901:0:0:0:0:0:0/64 + --ip-collection=IP_COLLECTION Resource reference to a public delegated prefix. The PublicDelegatedPrefix must be a sub-prefix in - EXTERNAL_IPV6_SUBNETWORK_CREATION mode. + EXTERNAL_IPV6_SUBNETWORK_CREATION or INTERNAL_IPV6_SUBNETWORK_CREATION + mode. --ipv6-access-type=IPV6_ACCESS_TYPE IPv6 access type can be specified only when the subnet is created, or diff --git a/gcloud/beta/compute/public-advertised-prefixes/create b/gcloud/beta/compute/public-advertised-prefixes/create index 5b5d247c2..bb78f922e 100644 --- a/gcloud/beta/compute/public-advertised-prefixes/create +++ b/gcloud/beta/compute/public-advertised-prefixes/create @@ -1,11 +1,12 @@ NAME - gcloud beta compute public-advertised-prefixes create - create a public - advertised prefix in the Beta release track + gcloud beta compute public-advertised-prefixes create - creates a Compute + Engine public advertised prefix SYNOPSIS gcloud beta compute public-advertised-prefixes create NAME --range=RANGE [--description=DESCRIPTION] [--dns-verification-ip=DNS_VERIFICATION_IP] - [--pdp-scope=PDP_SCOPE] [GCLOUD_WIDE_FLAG ...] + [--ipv6-access-type=IPV6_ACCESS_TYPE] [--pdp-scope=PDP_SCOPE] + [GCLOUD_WIDE_FLAG ...] EXAMPLES To create a public advertised prefix: @@ -36,6 +37,10 @@ OPTIONAL FLAGS IP address to use for verification. It must be within the IP range specified in --range. + --ipv6-access-type=IPV6_ACCESS_TYPE + Specifies the IPv6 access type of the public advertised prefix. + IPV6_ACCESS_TYPE must be one of: internal, external. + --pdp-scope=PDP_SCOPE Specifies how child public delegated prefix will be scoped. PDP_SCOPE must be one of: GLOBAL, REGIONAL. diff --git a/gcloud/beta/compute/public-advertised-prefixes/help b/gcloud/beta/compute/public-advertised-prefixes/help index ab96f2fdc..43014f80b 100644 --- a/gcloud/beta/compute/public-advertised-prefixes/help +++ b/gcloud/beta/compute/public-advertised-prefixes/help @@ -18,7 +18,7 @@ COMMANDS COMMAND is one of the following: create - (BETA) Create a public advertised prefix in the Beta release track. + (BETA) Creates a Compute Engine public advertised prefix. delete (BETA) Deletes a Compute Engine public advertised prefix. diff --git a/gcloud/beta/compute/public-delegated-prefixes/create b/gcloud/beta/compute/public-delegated-prefixes/create index 4bd137a7b..22d511708 100644 --- a/gcloud/beta/compute/public-delegated-prefixes/create +++ b/gcloud/beta/compute/public-delegated-prefixes/create @@ -49,7 +49,7 @@ OPTIONAL FLAGS --mode=MODE Specifies the mode of this IPv6 PDP. MODE must be one of: delegation, external-ipv6-forwarding-rule-creation, - external-ipv6-subnetwork-creation. + external-ipv6-subnetwork-creation, internal-ipv6-subnetwork-creation. At most one of these can be specified: diff --git a/gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create b/gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create index aea2a4ebc..f0ca87625 100644 --- a/gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create +++ b/gcloud/beta/compute/public-delegated-prefixes/delegated-sub-prefixes/create @@ -58,7 +58,7 @@ OPTIONAL FLAGS --mode=MODE Specifies the mode of this IPv6 PDP. MODE must be one of: delegation, external-ipv6-forwarding-rule-creation, - external-ipv6-subnetwork-creation. + external-ipv6-subnetwork-creation, internal-ipv6-subnetwork-creation. --range=RANGE IPv4 range from this public delegated prefix that should be delegated, diff --git a/gcloud/beta/compute/zone-vm-extension-policies/create b/gcloud/beta/compute/zone-vm-extension-policies/create new file mode 100644 index 000000000..bd3cadc74 --- /dev/null +++ b/gcloud/beta/compute/zone-vm-extension-policies/create @@ -0,0 +1,138 @@ +NAME + gcloud beta compute zone-vm-extension-policies create - create a Compute + Engine zone VM extension policy + +SYNOPSIS + gcloud beta compute zone-vm-extension-policies create NAME + --extensions=EXTENSION_NAME,[...] [--config=KEY=VALUE,[KEY=VALUE,...]] + [--config-from-file=KEY=FILE_PATH,[...]] [--description=DESCRIPTION] + [--inclusion-labels=INCLUSION_LABELS] + [--priority=PRIORITY; default=1000] + [--version=KEY=VALUE,[KEY=VALUE,...]] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Compute Engine zone VM extension policy. + +EXAMPLES + To create a zone VM extension policy, run: + + $ gcloud beta compute zone-vm-extension-policies create \ + test-policy-name --description="test policy" \ + --extensions=extension1,extension2 \ + --version=extension1=version1,extension2=version2 \ + --config=extension1="config1",extension2="config2" \ + --inclusion-labels=env=prod \ + --inclusion-labels=env=preprod,workload=load-test \ + --priority=1000 + + Available extensions: + ops-agent + google-cloud-sap-extension + google-cloud-workload-extension + +POSITIONAL ARGUMENTS + NAME + Name of the zone vm extension policy to create. + +REQUIRED FLAGS + --extensions=EXTENSION_NAME,[...] + One or more extensions to be added to the policy. + +OPTIONAL FLAGS + --config=KEY=VALUE,[KEY=VALUE,...] + A comma separated key:value list where the key is the extension name + and the value is the desired config for the given extension. The + extension name must be one of the extensions specified in the + --extensions flag. + + E.g. --config=filestore='filestore config',ops-agent='ops agent config' + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + + --config-from-file=KEY=FILE_PATH,[...] + Same as --config except that the value for the entry will be read from + a local file. The extension name must be one of the extensions + specified in the --extensions flag. + + It is an error to specify the same extension in both --config and + --config-from-file. + + --description=DESCRIPTION + An optional textual description for the this extension policy. + + --inclusion-labels=INCLUSION_LABELS + A list of inclusion labels to select the target VMs. + + The expected format for a single selector is "key1=value1,key2=value2". + A VM is selected if it has ALL the inclusion labels. + + When the option is specified multiple times, it assumes a logical OR + between the selectors. + + For example, if the inclusion labels are ["env=prod,workload=frontend", + "workload=backend"], the following VMs will be selected: + ◆ VM1: env=prod, workload=frontend, something=else + ◆ VM2: env=prod, workload=backend But not: + ◆ VM3: env=prod + + If not specified, ALL VMs in the zone will be selected. + + --priority=PRIORITY; default=1000 + The priority of the policy. Lower the number, higher the priority. When + two policies tries to apply the same extension, the one with the higher + priority takes precedence. If the priority is the same, the one with + the more recent update timestamp takes precedence. When a policy is + deleted, the extension would remain installed on the VM if a lower + priority policy still applies. + + Range from 0 to 65535. Default is 1000. + + --version=KEY=VALUE,[KEY=VALUE,...] + A comma separated key:value list where the key is the extension name + and the value is the desired version for the given extension. The + extension name must be one of the extensions specified in the + --extensions flag. If no version is specified for an extension, the + latest version will be used and will be upgraded automatically. + + E.g. --version=filestore=123ABC,ops-agent=456DEF + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + + --zone=ZONE + Zone of the zone vm extension policy 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute zone-vm-extension-policies create + diff --git a/gcloud/beta/compute/zone-vm-extension-policies/delete b/gcloud/beta/compute/zone-vm-extension-policies/delete new file mode 100644 index 000000000..8e8aa20aa --- /dev/null +++ b/gcloud/beta/compute/zone-vm-extension-policies/delete @@ -0,0 +1,57 @@ +NAME + gcloud beta compute zone-vm-extension-policies delete - delete a Compute + Engine zone VM extension policy + +SYNOPSIS + gcloud beta compute zone-vm-extension-policies delete NAME [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Compute Engine zone VM extension policy. + +EXAMPLES + To delete a zone VM extension policy, run: + + $ gcloud beta compute zone-vm-extension-policies delete \ + test-policy-name + +POSITIONAL ARGUMENTS + NAME + Name of the zone vm extension policy to delete. + +FLAGS + --zone=ZONE + Zone of the zone vm extension policy to delete. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute zone-vm-extension-policies delete + diff --git a/gcloud/beta/compute/zone-vm-extension-policies/describe b/gcloud/beta/compute/zone-vm-extension-policies/describe new file mode 100644 index 000000000..2c9e329f7 --- /dev/null +++ b/gcloud/beta/compute/zone-vm-extension-policies/describe @@ -0,0 +1,57 @@ +NAME + gcloud beta compute zone-vm-extension-policies describe - describe a + Compute Engine zone VM extension policy + +SYNOPSIS + gcloud beta compute zone-vm-extension-policies describe NAME [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Compute Engine zone VM extension policy. + +EXAMPLES + To describe a zone VM extension policy, run: + + $ gcloud beta compute zone-vm-extension-policies describe \ + test-policy-name + +POSITIONAL ARGUMENTS + NAME + Name of the zone vm extension policy to describe. + +FLAGS + --zone=ZONE + Zone of the zone vm extension policy to describe. If not specified and + the compute/zone property isn't set, you might be prompted to select a + zone (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute zone-vm-extension-policies describe + diff --git a/gcloud/beta/compute/zone-vm-extension-policies/help b/gcloud/beta/compute/zone-vm-extension-policies/help new file mode 100644 index 000000000..947939218 --- /dev/null +++ b/gcloud/beta/compute/zone-vm-extension-policies/help @@ -0,0 +1,40 @@ +NAME + gcloud beta compute zone-vm-extension-policies - compute Engine zone VM + extension policies + +SYNOPSIS + gcloud beta compute zone-vm-extension-policies COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Compute Engine zone VM extension policies. + +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 Compute Engine zone VM extension policy. + + delete + (BETA) Delete a Compute Engine zone VM extension policy. + + describe + (BETA) Describe a Compute Engine zone VM extension policy. + + list + (BETA) List Compute Engine zone VM extension policies. + + update + (BETA) Update a Compute Engine zone VM extension policy. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute zone-vm-extension-policies + diff --git a/gcloud/beta/compute/zone-vm-extension-policies/list b/gcloud/beta/compute/zone-vm-extension-policies/list new file mode 100644 index 000000000..fd612faa4 --- /dev/null +++ b/gcloud/beta/compute/zone-vm-extension-policies/list @@ -0,0 +1,67 @@ +NAME + gcloud beta compute zone-vm-extension-policies list - list Compute Engine + zone VM extension policies + +SYNOPSIS + gcloud beta compute zone-vm-extension-policies list --zone=ZONE + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Compute Engine zone VM extension policies. + +EXAMPLES + To list all zone VM extension policy, run: + + $ gcloud beta compute zone-vm-extension-policies list --zone= + +REQUIRED FLAGS + --zone=ZONE + The zone to list the extension policies from. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute zone-vm-extension-policies list + diff --git a/gcloud/beta/compute/zone-vm-extension-policies/update b/gcloud/beta/compute/zone-vm-extension-policies/update new file mode 100644 index 000000000..e9a5dfea1 --- /dev/null +++ b/gcloud/beta/compute/zone-vm-extension-policies/update @@ -0,0 +1,133 @@ +NAME + gcloud beta compute zone-vm-extension-policies update - update a Compute + Engine zone VM extension policy + +SYNOPSIS + gcloud beta compute zone-vm-extension-policies update NAME + --extensions=EXTENSION_NAME,[...] [--config=KEY=VALUE,[KEY=VALUE,...]] + [--config-from-file=KEY=FILE_PATH,[...]] [--description=DESCRIPTION] + [--inclusion-labels=INCLUSION_LABELS] + [--priority=PRIORITY; default=1000] + [--version=KEY=VALUE,[KEY=VALUE,...]] [--zone=ZONE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Compute Engine zone VM extension policy. + +EXAMPLES + To update a zone VM extension policy, run: + + $ gcloud beta compute zone-vm-extension-policies update \ + test-policy-name --description="test policy" \ + --extensions=extension1,extension2 \ + --version=extension1=version1,extension2=version2 \ + --config=extension1="config1",extension2="config2" \ + --inclusion-labels=env=prod \ + --inclusion-labels=env=preprod,workload=load-test \ + --priority=1000 + +POSITIONAL ARGUMENTS + NAME + Name of the zone vm extension policy to update. + +REQUIRED FLAGS + --extensions=EXTENSION_NAME,[...] + One or more extensions to be added to the policy. + +OPTIONAL FLAGS + --config=KEY=VALUE,[KEY=VALUE,...] + A comma separated key:value list where the key is the extension name + and the value is the desired config for the given extension. The + extension name must be one of the extensions specified in the + --extensions flag. + + E.g. --config=filestore='filestore config',ops-agent='ops agent config' + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + + --config-from-file=KEY=FILE_PATH,[...] + Same as --config except that the value for the entry will be read from + a local file. The extension name must be one of the extensions + specified in the --extensions flag. + + It is an error to specify the same extension in both --config and + --config-from-file. + + --description=DESCRIPTION + An optional textual description for the this extension policy. + + --inclusion-labels=INCLUSION_LABELS + A list of inclusion labels to select the target VMs. + + The expected format for a single selector is "key1=value1,key2=value2". + A VM is selected if it has ALL the inclusion labels. + + When the option is specified multiple times, it assumes a logical OR + between the selectors. + + For example, if the inclusion labels are ["env=prod,workload=frontend", + "workload=backend"], the following VMs will be selected: + ◆ VM1: env=prod, workload=frontend, something=else + ◆ VM2: env=prod, workload=backend But not: + ◆ VM3: env=prod + + If not specified, ALL VMs in the zone will be selected. + + --priority=PRIORITY; default=1000 + The priority of the policy. Lower the number, higher the priority. When + two policies tries to apply the same extension, the one with the higher + priority takes precedence. If the priority is the same, the one with + the more recent update timestamp takes precedence. When a policy is + deleted, the extension would remain installed on the VM if a lower + priority policy still applies. + + Range from 0 to 65535. Default is 1000. + + --version=KEY=VALUE,[KEY=VALUE,...] + A comma separated key:value list where the key is the extension name + and the value is the desired version for the given extension. The + extension name must be one of the extensions specified in the + --extensions flag. If no version is specified for an extension, the + latest version will be used and will be upgraded automatically. + + E.g. --version=filestore=123ABC,ops-agent=456DEF + + Raises: ArgumentTypeError: If the extension name is not specified in + the --extensions flag. + + --zone=ZONE + Zone of the zone vm extension policy 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute zone-vm-extension-policies update + diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 378cd7945..283e120ac 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -112,6 +112,7 @@ SYNOPSIS | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] [--disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics] + [--disable-pod-snapshots | --enable-pod-snapshots] [--enable-autoprovisioning --autoprovisioning-config-file=PATH_TO_FILE | --autoprovisioning-image-type=AUTOPROVISIONING_IMAGE_TYPE --autoprovisioning-locations=ZONE,[ZONE,...] @@ -2071,6 +2072,14 @@ FLAGS --enable-dataplane-v2-metrics Exposes advanced datapath flow metrics on node port. + At most one of these can be specified: + + --disable-pod-snapshots + Disable the Pod Snapshot feature on the cluster. + + --enable-pod-snapshots + Enable the Pod Snapshot feature on the cluster. + Node autoprovisioning --enable-autoprovisioning diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index ba91733f0..8032518cf 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -49,6 +49,7 @@ SYNOPSIS [--dataplane-v2-observability-mode=DATAPLANE_V2_OBSERVABILITY_MODE | --disable-dataplane-v2-flow-observability | --enable-dataplane-v2-flow-observability] + [--disable-pod-snapshots | --enable-pod-snapshots] [--enable-insecure-binding-system-authenticated --enable-insecure-binding-system-unauthenticated] [--enable-master-authorized-networks @@ -650,6 +651,14 @@ FLAGS Enables Advanced Datapath Observability which allows for a real-time view into pod-to-pod traffic within your cluster. + At most one of these can be specified: + + --disable-pod-snapshots + Disable the Pod Snapshot feature on the cluster. + + --enable-pod-snapshots + Enable the Pod Snapshot feature on the cluster. + --enable-insecure-binding-system-authenticated Allow using system:authenticated as a subject in ClusterRoleBindings and RoleBindings. Allowing bindings that reference system:authenticated diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index d42e7385e..705658234 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -92,7 +92,8 @@ SYNOPSIS --disable-dataplane-v2-metrics | --enable-dataplane-v2-metrics | --disable-auto-ipam | --enable-auto-ipam | --disable-l4-lb-firewall-reconciliation - | --enable-l4-lb-firewall-reconciliation + | --enable-l4-lb-firewall-reconciliation | --disable-pod-snapshots + | --enable-pod-snapshots | --enable-authorized-networks-on-private-endpoint --enable-dns-access --enable-google-cloud-access --enable-ip-access --enable-k8s-certs-via-dns --enable-k8s-tokens-via-dns @@ -1320,6 +1321,14 @@ REQUIRED FLAGS firewalls targeting ingress traffic. L4 LB VPC firewall reconciliation is enabled by default. + At most one of these can be specified: + + --disable-pod-snapshots + Disable the Pod Snapshot feature on the cluster. + + --enable-pod-snapshots + Enable the Pod Snapshot feature on the cluster. + --enable-authorized-networks-on-private-endpoint Enable enforcement of --master-authorized-networks CIDR ranges for traffic reaching cluster's control plane via private IP. diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 1499040e2..61b51c6dd 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -154,9 +154,6 @@ FLAGS machine type needs to be specified with the --machine-type flag. An Accelerator Network Profiles will be created if it does not exist. - ACCELERATOR_NETWORK_PROFILE must be (only one value is supported): - auto. - --additional-node-network=[network=NETWORK_NAME,subnetwork=SUBNETWORK_NAME,...] Attach an additional network interface to each node in the pool. This parameter can be specified up to 7 times. diff --git a/gcloud/beta/container/operations/cancel b/gcloud/beta/container/operations/cancel index 61a5a6095..1617630dc 100644 --- a/gcloud/beta/container/operations/cancel +++ b/gcloud/beta/container/operations/cancel @@ -17,6 +17,8 @@ DESCRIPTION would be if all the nodes have been upgraded but the operation hasn't been marked as complete. + Only node pool upgrade operations support cancellation. + EXAMPLES To cancel an operation, run: diff --git a/gcloud/beta/dataflow/flex-template/build b/gcloud/beta/dataflow/flex-template/build index 8b03860c6..694ce6fb6 100644 --- a/gcloud/beta/dataflow/flex-template/build +++ b/gcloud/beta/dataflow/flex-template/build @@ -90,12 +90,11 @@ REQUIRED FLAGS --flex-template-base-image=FLEX_TEMPLATE_BASE_IMAGE Flex template base image to be used while building the container - image. Allowed choices are allowed labels (JAVA11, JAVA17, JAVA21, - PYTHON3, GO), supported distroless images (JAVA11_DISTROLESS, - JAVA17_DISTROLESS, JAVA21_DISTROLESS, GO_DISTROLESS), or full gcr.io - path of the specific version of the base image. For labels, we use - the latest base image version to build the container. You can also - provide a specific version from this link + image. Allowed choices are allowed labels (JAVA11/17/21/25, PYTHON3, + GO), supported distroless images (JAVA11/17/21/25_DISTROLESS, + GO_DISTROLESS), or full gcr.io path of the specific version of the + base image. For labels, we use the latest base image version to build + the container. You can also provide a specific version from this link https://gcr.io/dataflow-templates-base/ This flag argument must be specified if any of the other arguments in diff --git a/gcloud/beta/emulators/spanner/help b/gcloud/beta/emulators/spanner/help index bb82d63df..ea36360b0 100644 --- a/gcloud/beta/emulators/spanner/help +++ b/gcloud/beta/emulators/spanner/help @@ -25,6 +25,9 @@ COMMANDS (BETA) Print the commands required to export Spanner emulator's env variables. + notices + (BETA) Print third-party notices for the local Cloud Spanner emulator. + start (BETA) Start a local Cloud Spanner emulator. diff --git a/gcloud/beta/emulators/spanner/notices b/gcloud/beta/emulators/spanner/notices new file mode 100644 index 000000000..9940628ff --- /dev/null +++ b/gcloud/beta/emulators/spanner/notices @@ -0,0 +1,38 @@ +NAME + gcloud beta emulators spanner notices - print third-party notices for the + local Cloud Spanner emulator + +SYNOPSIS + gcloud beta emulators spanner notices [--use-docker] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Print third-party notices for the local Cloud Spanner emulator. + +EXAMPLES + To print third-party notices for the local Cloud Spanner emulator, run: + + $ gcloud beta emulators spanner notices + +FLAGS + --use-docker + Use the Cloud Spanner emulator docker image even if the platform has a + native binary available in the gcloud CLI. Currently we only provide a + native binary for Linux. For other systems, you must install Docker for + your platform before starting the emulator. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud emulators spanner notices + + $ gcloud alpha emulators spanner notices + diff --git a/gcloud/beta/filestore/instances/create b/gcloud/beta/filestore/instances/create index bfc3fd8c0..02324914f 100644 --- a/gcloud/beta/filestore/instances/create +++ b/gcloud/beta/filestore/instances/create @@ -5,9 +5,10 @@ SYNOPSIS gcloud beta filestore instances create (INSTANCE : --zone=ZONE) --file-share=[capacity=CAPACITY],[name=NAME], [nfs-export-options=NFS-EXPORT-OPTIONS],[source-backup=SOURCE-BACKUP], - [source-backup-region=SOURCE-BACKUP-REGION] - --network=[connect-mode=CONNECT-MODE],[name=NAME], - [psc-endpoint-project=PSC-ENDPOINT-PROJECT], + [source-backup-region=SOURCE-BACKUP-REGION], + [source-backupdr-backup=SOURCE-BACKUPDR-BACKUP] + --network=[address-mode=ADDRESS-MODE],[connect-mode=CONNECT-MODE], + [name=NAME],[psc-endpoint-project=PSC-ENDPOINT-PROJECT], [reserved-ip-range=RESERVED-IP-RANGE] [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--location=LOCATION] @@ -26,48 +27,47 @@ DESCRIPTION (BETA) Create a Filestore instance. EXAMPLES - The following command creates a Filestore instance named NAME with a single - volume. + To create a Basic HDD instance named my-instance in zone us-central1-c with + a 1TB volume named my_vol on the default network, run: - $ gcloud beta filestore instances create NAME \ - --description=DESCRIPTION --tier=TIER --protocol=PROTOCOL \ - --file-share=name=VOLUME_NAME,capacity=CAPACITY \ - --network=name=NETWORK_NAME,\ - reserved-ip-range=RESERVED_IP_RANGE,connect-mode=CONNECT_MODE,\ - psc-endpoint-project=PSC_ENDPOINT_PROJECT --zone=ZONE \ - --performance=max-iops-per-tb=MAX-IOPS-PER-TB \ - --kms-key=KMS-KEY --kms-keyring=KMS_KEYRING \ - --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT \ - --managed-ad=domain=DOMAIN,computer=COMPUTER \ - --flags-file=FLAGS_FILE --source-instance=SOURCE_INSTANCE + $ gcloud beta filestore instances create my-instance \ + --zone=us-central1-c --tier=BASIC_HDD \ + --file-share=name=my_vol,capacity=1TB --network=name=default - Example json configuration file: - { "--file-share": { "capacity": "61440", + To create an Enterprise instance named `my-ent-instance` in region `us-central1` with a 2TB volume named `my_vol` on network `my-network`, run: + + $ gcloud beta filestore instances create my-ent-instance \ + --zone=us-central1 --tier=ENTERPRISE \ + --file-share=name=my_vol,capacity=2TB --network=name=my-network + + To create an instance with specific NFS export options, you can use a JSON configuration file with `--flags-file`. For example, create a file named `config.json` with the following content: + { "--file-share": { "capacity": "1024", "name": "my_vol", "nfs-export-options": [ { "access-mode": "READ_WRITE", "ip-ranges": [ - "10.0.0.0/8", - ], - "squash-mode": "NO_ROOT_SQUASH", - "security-flavors": [ - "AUTH_SYS", - "KRB5P", + "10.0.0.0/8" ], + "squash-mode": "NO_ROOT_SQUASH" }, { "access-mode": "READ_ONLY", "ip-ranges": [ "192.168.0.0/24" ], - "squash-mode": "ROOT_SQUASH" + "squash-mode": "ROOT_SQUASH", "anon_uid": 1003, "anon_gid": 1003 } - ], + ] } } + To create a Basic SSD instance named `my-nfs-instance` using the above configuration file, run: + $ gcloud beta filestore instances create my-nfs-instance \ + --zone=us-central1-c --tier=BASIC_SSD --network=name=default \ + --flags-file=config.json + POSITIONAL ARGUMENTS Instance resource - The instance to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -105,7 +105,7 @@ POSITIONAL ARGUMENTS ▸ set the property filestore/location. REQUIRED FLAGS - --file-share=[capacity=CAPACITY],[name=NAME],[nfs-export-options=NFS-EXPORT-OPTIONS],[source-backup=SOURCE-BACKUP],[source-backup-region=SOURCE-BACKUP-REGION] + --file-share=[capacity=CAPACITY],[name=NAME],[nfs-export-options=NFS-EXPORT-OPTIONS],[source-backup=SOURCE-BACKUP],[source-backup-region=SOURCE-BACKUP-REGION],[source-backupdr-backup=SOURCE-BACKUPDR-BACKUP] File share configuration for an instance. Specifying both name and capacity is required. @@ -194,9 +194,9 @@ REQUIRED FLAGS source-backup-region The region of the source backup. - --network=[connect-mode=CONNECT-MODE],[name=NAME],[psc-endpoint-project=PSC-ENDPOINT-PROJECT],[reserved-ip-range=RESERVED-IP-RANGE] + --network=[address-mode=ADDRESS-MODE],[connect-mode=CONNECT-MODE],[name=NAME],[psc-endpoint-project=PSC-ENDPOINT-PROJECT],[reserved-ip-range=RESERVED-IP-RANGE] Network configuration for a Cloud Filestore instance. Specifying - reserved-ip-range and connect-mode is optional. + reserved-ip-range, address-mode and connect-mode is optional. name The name of the Google Compute Engine VPC network to which the instance is connected. @@ -221,6 +221,9 @@ REQUIRED FLAGS Network connection mode used by instances. CONNECT_MODE must be one of: DIRECT_PEERING, PRIVATE_SERVICE_ACCESS or PRIVATE_SERVICE_CONNECT. + address-mode + Internet protocol version for which the instance has IP address + assigned. psc-endpoint-project Consumer service project in which the psc endpoint would be set up. This is optional, and only relevant in case the network is a shared diff --git a/gcloud/beta/firestore/databases/clone b/gcloud/beta/firestore/databases/clone new file mode 100644 index 000000000..de5be6466 --- /dev/null +++ b/gcloud/beta/firestore/databases/clone @@ -0,0 +1,139 @@ +NAME + gcloud beta firestore databases clone - clone a Google Cloud Firestore + database from another + +SYNOPSIS + gcloud beta firestore databases clone + --destination-database=DESTINATION_DATABASE + --snapshot-time=SNAPSHOT_TIME --source-database=SOURCE_DATABASE + [--tags=[KEY=VALUE,...]] + [--encryption-type=ENCRYPTION_TYPE : --kms-key-name=KMS_KEY_NAME] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To clone a database from another: + + $ gcloud beta firestore databases clone \ + --source-database=projects/PROJECT_ID/databases/\ + SOURCE_DATABASE --snapshot-time=2025-05-26T10:20:00.00Z \ + --destination-database=DATABASE_ID + + To clone to a CMEK-enabled database: + + $ gcloud beta firestore databases clone \ + --source-database=projects/PROJECT_ID/databases/\ + SOURCE_DATABASE --snapshot-time=2025-05-26T10:20:00.00Z \ + --destination-database=DATABASE_ID \ + --encryption-type=customer-managed-encryption \ + --kms-key-name=projects/PROJECT_ID/locations/LOCATION_ID/\ + keyRings/KEY_RING_ID/cryptoKeys/CRYPTO_KEY_ID + +REQUIRED FLAGS + --destination-database=DESTINATION_DATABASE + Destination database to clone to. Destination database will be created + in the same location as the source database. + + This value should be 4-63 characters. Valid characters are + /[a-z][0-9]-/ with first character a letter and the last a letter or a + number. Must not be UUID-like /[0-9a-f]8(-[0-9a-f]4)3-[0-9a-f]12/. + + Using "(default)" database ID is also allowed. + + For example, to clone to database testdb: + + $ gcloud beta firestore databases clone --destination-database=testdb + + --snapshot-time=SNAPSHOT_TIME + Snapshot time at which to clone. This must be a whole minute, in the + past, and not earlier than the source database's earliest_version_time. + Additionally, if older than one hour in the past, PITR must be enabled + on the source database. + + For example, to restore from snapshot 2025-05-26T10:20:00.00Z of source + database source-db: + + $ gcloud beta firestore databases clone \ + --source-database=projects/PROJECT_ID/databases/source-db \ + --snapshot-time=2025-05-26T10:20:00.00Z + + --source-database=SOURCE_DATABASE + The source database to clone from. + + For example, to clone from database source-db: + + $ gcloud beta firestore databases clone \ + --source-database=projects/PROJECT_ID/databases/source-db + +OPTIONAL FLAGS + --tags=[KEY=VALUE,...] + Tags to attach to the destination database. Example: + --tags=key1=value1,key2=value2 + + For example, to attach tags to a database: + + $ --tags=key1=value1,key2=value2 + + The encryption configuration of the new database being created from the + database. If not specified, the same encryption settings as the database + will be used. + + To create a CMEK-enabled database: + + $ gcloud beta firestore databases clone \ + --encryption-type=customer-managed-encryption \ + --kms-key-name=projects/PROJECT_ID/locations/LOCATION_ID/\ + keyRings/KEY_RING_ID/cryptoKeys/CRYPTO_KEY_ID + + To create a Google-default-encrypted database: + + $ gcloud beta firestore databases clone \ + --encryption-type=google-default-encryption + + To create a database using the same encryption settings as the database: + + $ gcloud beta firestore databases clone \ + --encryption-type=use-source-encryption + + --encryption-type=ENCRYPTION_TYPE + The encryption type of the destination database. ENCRYPTION_TYPE must + be one of: use-source-encryption, customer-managed-encryption, + google-default-encryption. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --kms-key-name=KMS_KEY_NAME + The resource ID of a Cloud KMS key. If set, the database created will + be a Customer-Managed Encryption Key (CMEK) database encrypted with + this key. This feature is allowlist only in initial launch. + + Only a key in the same location as this database is allowed to be + used for encryption. For Firestore's nam5 multi-region, this + corresponds to Cloud KMS location us. For Firestore's eur3 + multi-region, this corresponds to Cloud KMS location europe. See + https://cloud.google.com/kms/docs/locations. + + This value should be the KMS key resource ID in the format of + projects/{project_id}/locations/{kms_location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}. + How to retrieve this resource ID is listed at + https://cloud.google.com/kms/docs/getting-resource-ids#getting_the_id_for_a_key_and_version. + + This flag must only be specified when encryption-type is + customer-managed-encryption. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud firestore databases clone + + $ gcloud alpha firestore databases clone + diff --git a/gcloud/beta/firestore/databases/help b/gcloud/beta/firestore/databases/help index c20abbb1d..17911aa07 100644 --- a/gcloud/beta/firestore/databases/help +++ b/gcloud/beta/firestore/databases/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + clone + (BETA) Clone a Google Cloud Firestore database from another. + connection-string (BETA) Prints the mongo connection string for the given Firestore database. diff --git a/gcloud/beta/iam/access-policies/create b/gcloud/beta/iam/access-policies/create new file mode 100644 index 000000000..48bf214e5 --- /dev/null +++ b/gcloud/beta/iam/access-policies/create @@ -0,0 +1,274 @@ +NAME + gcloud beta iam access-policies create - create AccessPolicy instance + +SYNOPSIS + gcloud beta iam access-policies create + (ACCESS_POLICY + : --folder=FOLDER --location=LOCATION --organization=ORGANIZATION) + [--annotations=[ANNOTATIONS,...]] [--async] + [--details-rules=[conditions=CONDITIONS],[description=DESCRIPTION], + [effect=EFFECT],[excludedPrincipals=EXCLUDEDPRINCIPALS], + [operation=OPERATION],[principals=PRINCIPALS]] + [--display-name=DISPLAY_NAME] [--etag=ETAG] [--validate-only] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create AccessPolicy instance. + +EXAMPLES + To create a policy instance called my-policy, run: + + $ gcloud beta iam access-policies create my-policy \ + --organization=123 --location=global --details.rules=rule1.json + +POSITIONAL ARGUMENTS + AccessPolicy resource - Identifier. The resource name of the access + policy. + + The following formats are supported: + projects/{project_id}/locations/{location}/accessPolicies/{policy_id} + projects/{project_number}/locations/{location}/accessPolicies/{policy_id} + folders/{folder_id}/locations/{location}/accessPolicies/{policy_id} + organizations/{organization_id}/locations/{location}/accessPolicies/{policy_id} + 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 access_policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [iam.folders.locations.accessPolicies, + iam.organizations.locations.accessPolicies, + iam.projects.locations.accessPolicies]. + + This must be specified. + + ACCESS_POLICY + ID of the accessPolicy or fully qualified identifier for the + accessPolicy. + + To set the access_policy attribute: + ▸ provide the argument access_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --folder=FOLDER + The folder id of the accessPolicy resource. + + To set the folder attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --folder on the command line. Must be + specified for resource of type + [iam.folders.locations.accessPolicies]. + + --location=LOCATION + The location id of the accessPolicy resource. + + To set the location attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + The organization id of the accessPolicy resource. + + To set the organization attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [iam.organizations.locations.accessPolicies]. + +FLAGS + --annotations=[ANNOTATIONS,...] + User defined annotations. See https://google.aip.dev/148#annotations + for more details such as format and size limitations. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --annotations=string=string + + JSON Example: + + --annotations='{"string": "string"}' + + File Example: + + --annotations=path_to_file.(yaml|json) + + --async + Return immediately, without waiting for the operation in progress to + complete. + + Access policy details. + + --details-rules=[conditions=CONDITIONS],[description=DESCRIPTION],[effect=EFFECT],[excludedPrincipals=EXCLUDEDPRINCIPALS],[operation=OPERATION],[principals=PRINCIPALS] + Required, A list of access policy rules. + + conditions + The conditions that determine whether this rule applies to a + request. Conditions are identified by their key, which is the + FQDN of the service that they are relevant to, e.g.: + + "conditions": { "iam.googleapis.com": } + + Each rule is evaluated independently. If this rule does not apply + to a request, other rules might still apply. Currently supported + keys are: + + ▫ eventarc.googleapis.com// The conditions that determine + whether this rule applies to a request. Conditions are + identified by their key, which is the FQDN of the service that + they are relevant to, e.g.: + + "conditions": { "iam.googleapis.com": { "cel_condition": } } + + Each rule is evaluated independently. If this rule does not apply + to a request, other rules might still apply. Currently supported + keys are: + + ▫ eventarc.googleapis.com + ▫ iam.googleapis.com. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + description + Description of the expression. This is a longer text + which describes the expression, e.g. when hovered over it + in a UI. + + expression + Textual representation of an expression in Common + Expression Language syntax. + + location + String indicating the location of the expression for + error reporting, e.g. a file name and a position in the + file. + + title + Title for the expression, i.e. a short string describing + its purpose. This can be used e.g. in UIs which allow to + enter the expression. + + description + Customer specified description of the rule. Must be less than or + equal to 256 characters. + + effect + The effect of the rule. + + excludedPrincipals + The identities that are excluded from the access policy rule, + even if they are listed in the principals. For example, you could + add a Google group to the principals, then exclude specific users + who belong to that group. + + operation + Attributes that are used to determine whether this rule applies + to a request. + + excludedPermissions + Specifies the permissions that this rule excludes from the + set of affected permissions given by permissions. If a + permission appears in permissions and in excluded_permissions + then it will not be subject to the policy effect. + + The excluded permissions can be specified using the same + syntax as permissions. + + permissions + The permissions that are explicitly affected by this rule. + Each permission uses the format + {service_fqdn}/{resource}.{verb}, where {service_fqdn} is the + fully qualified domain name for the service. Currently + supported permissions are: + + ◇ eventarc.googleapis.com/messageBuses.publish. + + principals + The identities for which this rule's effect governs using one or + more permissions on Google Cloud resources. This field can + contain the following values: + + ▫ principal://goog/subject/{email_id}: A specific Google + Account. Includes Gmail, Cloud Identity, and Google Workspace + user accounts. For example, + principal://goog/subject/alice@example.com. + + If an identifier that was previously set on a policy is soft deleted, then + calls to read that policy will return the identifier with a deleted + prefix. Users cannot set identifiers with this syntax. + * `deleted:principal://goog/subject/{email_id}?uid={uid}`: A specific + Google Account that was deleted recently. For example, + `deleted:principal://goog/subject/alice@example.com?uid=1234567890`. If + the Google Account is recovered, this identifier reverts to the standard + identifier for a Google Account. + + ▫ deleted:principalSet://goog/group/{group_id}?uid={uid}: A + Google group that was deleted recently. For example, + deleted:principalSet://goog/group/admins@example.com?uid=1234567890. + If the Google group is restored, this identifier reverts to the + standard identifier for a Google group. + + ▫ deleted:principal://iam.googleapis.com/projects/-/serviceAccounts/{service_account_id}?uid={uid}: + A Google Cloud service account that was deleted recently. For + example, + deleted:principal://iam.googleapis.com/projects/-/serviceAccounts/my-service-account@iam.gserviceaccount.com?uid=1234567890. + If the service account is undeleted, this identifier reverts to + the standard identifier for a service account. + + Shorthand Example: + + --details-rules=conditions={string={description=string,expression=string,location=string,title=string}},description=string,effect=string,excludedPrincipals=[string],operation={excludedPermissions=[string],permissions=[string]},principals=[string] --details-rules=conditions={string={description=string,expression=string,location=string,title=string}},description=string,effect=string,excludedPrincipals=[string],operation={excludedPermissions=[string],permissions=[string]},principals=[string] + + JSON Example: + + --details-rules='[{"conditions": {"string": {"description": "string", "expression": "string", "location": "string", "title": "string"}}, "description": "string", "effect": "string", "excludedPrincipals": ["string"], "operation": {"excludedPermissions": ["string"], "permissions": ["string"]}, "principals": ["string"]}]' + + File Example: + + --details-rules=path_to_file.(yaml|json) + + --display-name=DISPLAY_NAME + The description of the access policy. Must be less than or equal to 63 + characters. + + --etag=ETAG + The etag for the access policy. If this is provided on update, it must + match the server's etag. + + --validate-only + If set, validate the request and preview the creation, but do not + actually post it. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the iam/v3beta API. The full documentation for this API + can be found at: https://cloud.google.com/iam/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/iam/access-policies/delete b/gcloud/beta/iam/access-policies/delete new file mode 100644 index 000000000..be717b2fd --- /dev/null +++ b/gcloud/beta/iam/access-policies/delete @@ -0,0 +1,111 @@ +NAME + gcloud beta iam access-policies delete - delete AccessPolicy instance + +SYNOPSIS + gcloud beta iam access-policies delete + (ACCESS_POLICY + : --folder=FOLDER --location=LOCATION --organization=ORGANIZATION) + [--async] [--etag=ETAG] [--force] [--validate-only] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete AccessPolicy instance. + +EXAMPLES + To delete my-policy instance, run: + + $ gcloud beta iam access-policies delete my-policy + +POSITIONAL ARGUMENTS + AccessPolicy resource - The name of the access policy to delete. + + Format: + projects/{project_id}/locations/{location}/accessPolicies/{access_policy_id} + projects/{project_number}/locations/{location}/accessPolicies/{access_policy_id} + folders/{folder_id}/locations/{location}/accessPolicies/{access_policy_id} + organizations/{organization_id}/locations/{location}/accessPolicies/{access_policy_id} + 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 access_policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [iam.folders.locations.accessPolicies, + iam.organizations.locations.accessPolicies, + iam.projects.locations.accessPolicies]. + + This must be specified. + + ACCESS_POLICY + ID of the accessPolicy or fully qualified identifier for the + accessPolicy. + + To set the access_policy attribute: + ▸ provide the argument access_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --folder=FOLDER + The folder id of the accessPolicy resource. + + To set the folder attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --folder on the command line. Must be + specified for resource of type + [iam.folders.locations.accessPolicies]. + + --location=LOCATION + The location id of the accessPolicy resource. + + To set the location attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + The organization id of the accessPolicy resource. + + To set the organization attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [iam.organizations.locations.accessPolicies]. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --etag=ETAG + The etag of the access policy. If this is provided, it must match the + server's etag. + + --force + If set to true, the request will force the deletion of the Policy even + if the Policy references PolicyBindings. + + --validate-only + If set, validate the request and preview the deletion, but do not + actually post it. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the iam/v3beta API. The full documentation for this API + can be found at: https://cloud.google.com/iam/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/iam/access-policies/describe b/gcloud/beta/iam/access-policies/describe new file mode 100644 index 000000000..86e839052 --- /dev/null +++ b/gcloud/beta/iam/access-policies/describe @@ -0,0 +1,94 @@ +NAME + gcloud beta iam access-policies describe - get AccessPolicy instance + +SYNOPSIS + gcloud beta iam access-policies describe + (ACCESS_POLICY + : --folder=FOLDER --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get AccessPolicy instance. + +EXAMPLES + To get the details of a single policy my-policy in organization 123, run: + + $ gcloud beta iam access-policies describe my-policy \ + --organization=123 --location=global + +POSITIONAL ARGUMENTS + AccessPolicy resource - The name of the access policy to retrieve. + + Format: + projects/{project_id}/locations/{location}/accessPolicies/{access_policy_id} + projects/{project_number}/locations/{location}/accessPolicies/{access_policy_id} + folders/{folder_id}/locations/{location}/accessPolicies/{access_policy_id} + organizations/{organization_id}/locations/{location}/accessPolicies/{access_policy_id} + 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 access_policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [iam.folders.locations.accessPolicies, + iam.organizations.locations.accessPolicies, + iam.projects.locations.accessPolicies]. + + This must be specified. + + ACCESS_POLICY + ID of the accessPolicy or fully qualified identifier for the + accessPolicy. + + To set the access_policy attribute: + ▸ provide the argument access_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --folder=FOLDER + The folder id of the accessPolicy resource. + + To set the folder attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --folder on the command line. Must be + specified for resource of type + [iam.folders.locations.accessPolicies]. + + --location=LOCATION + The location id of the accessPolicy resource. + + To set the location attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + The organization id of the accessPolicy resource. + + To set the organization attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [iam.organizations.locations.accessPolicies]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the iam/v3beta API. The full documentation for this API + can be found at: https://cloud.google.com/iam/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/iam/access-policies/help b/gcloud/beta/iam/access-policies/help new file mode 100644 index 000000000..9c487db22 --- /dev/null +++ b/gcloud/beta/iam/access-policies/help @@ -0,0 +1,38 @@ +NAME + gcloud beta iam access-policies - manage Access Policy resources + +SYNOPSIS + gcloud beta iam access-policies COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Access Policy 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 AccessPolicy instance. + + delete + (BETA) Delete AccessPolicy instance. + + describe + (BETA) Get AccessPolicy instance. + + list + (BETA) List AccessPolicy instances. + + search-policy-bindings + (BETA) search accessPolicies. + + update + (BETA) Update AccessPolicy instance. + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/iam/access-policies/list b/gcloud/beta/iam/access-policies/list new file mode 100644 index 000000000..006a79673 --- /dev/null +++ b/gcloud/beta/iam/access-policies/list @@ -0,0 +1,114 @@ +NAME + gcloud beta iam access-policies list - list AccessPolicy instances + +SYNOPSIS + gcloud beta iam access-policies list + (--location=LOCATION : --folder=FOLDER --organization=ORGANIZATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List AccessPolicy instances. + +EXAMPLES + To list all policy instances in organization 123, run: + + $ gcloud beta iam access-policies list --organization=123 \ + --location=global + +REQUIRED FLAGS + Location resource - The parent resource, which owns the collection of + access policy resources. + + Format: projects/{project_id}/locations/{location} + projects/{project_number}/locations/{location} + folders/{folder_id}/locations/{location} + organizations/{organization_id}/locations/{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 --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [iam.folders.locations, iam.organizations.locations, + iam.projects.locations]. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --folder=FOLDER + The folder id of the location resource. + + To set the folder attribute: + ▸ provide the argument --location on the command line with a fully + specified name; + ▸ provide the argument --folder on the command line. Must be + specified for resource of type [iam.folders.locations]. + + --organization=ORGANIZATION + The organization id of the location resource. + + To set the organization attribute: + ▸ provide the argument --location on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type [iam.organizations.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 iam/v3beta API. The full documentation for this API + can be found at: https://cloud.google.com/iam/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/iam/access-policies/search-policy-bindings b/gcloud/beta/iam/access-policies/search-policy-bindings new file mode 100644 index 000000000..e62ab6108 --- /dev/null +++ b/gcloud/beta/iam/access-policies/search-policy-bindings @@ -0,0 +1,119 @@ +NAME + gcloud beta iam access-policies search-policy-bindings - search + accessPolicies + +SYNOPSIS + gcloud beta iam access-policies search-policy-bindings + (ACCESS_POLICY + : --folder=FOLDER --location=LOCATION --organization=ORGANIZATION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) search accessPolicies + +EXAMPLES + To search all accessPolicies, run: + + $ gcloud beta iam access-policies search-policy-bindings + +POSITIONAL ARGUMENTS + AccessPolicy resource - The name of the access policy. Format: + organizations/{organization_id}/locations/{location}/accessPolicies/{access_policy_id} + folders/{folder_id}/locations/{location}/accessPolicies/{access_policy_id} + projects/{project_id}/locations/{location}/accessPolicies/{access_policy_id} + projects/{project_number}/locations/{location}/accessPolicies/{access_policy_id} + 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 access_policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [iam.folders.locations.accessPolicies, + iam.organizations.locations.accessPolicies, + iam.projects.locations.accessPolicies]. + + This must be specified. + + ACCESS_POLICY + ID of the accessPolicy or fully qualified identifier for the + accessPolicy. + + To set the access_policy attribute: + ▸ provide the argument access_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --folder=FOLDER + The folder id of the accessPolicy resource. + + To set the folder attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --folder on the command line. Must be + specified for resource of type + [iam.folders.locations.accessPolicies]. + + --location=LOCATION + The location id of the accessPolicy resource. + + To set the location attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + The organization id of the accessPolicy resource. + + To set the organization attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [iam.organizations.locations.accessPolicies]. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the iam/v3beta API. The full documentation for this API + can be found at: https://cloud.google.com/iam/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/iam/access-policies/update b/gcloud/beta/iam/access-policies/update new file mode 100644 index 000000000..c587667b9 --- /dev/null +++ b/gcloud/beta/iam/access-policies/update @@ -0,0 +1,618 @@ +NAME + gcloud beta iam access-policies update - update AccessPolicy instance + +SYNOPSIS + gcloud beta iam access-policies update + (ACCESS_POLICY + : --folder=FOLDER --location=LOCATION --organization=ORGANIZATION) + [--async] [--display-name=DISPLAY_NAME] [--etag=ETAG] + [--[no-]validate-only] + [--annotations=[ANNOTATIONS,...] + | --update-annotations=[UPDATE_ANNOTATIONS,...] --clear-annotations + | --remove-annotations=REMOVE_ANNOTATIONS] + [--clear-details + --details-rules=[conditions=CONDITIONS],[description=DESCRIPTION], + [effect=EFFECT],[excludedPrincipals=EXCLUDEDPRINCIPALS], + [operation=OPERATION],[principals=PRINCIPALS] + | --add-details-rules=[conditions=CONDITIONS], + [description=DESCRIPTION],[effect=EFFECT], + [excludedPrincipals=EXCLUDEDPRINCIPALS], + [operation=OPERATION],[principals=PRINCIPALS] --clear-details-rules + | --remove-details-rules=[conditions=CONDITIONS], + [description=DESCRIPTION],[effect=EFFECT], + [excludedPrincipals=EXCLUDEDPRINCIPALS], + [operation=OPERATION],[principals=PRINCIPALS]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update AccessPolicy instance. + +EXAMPLES + To update display name of my-policy in organization 123, run: + + $ gcloud beta iam access-policies update my-policy \ + --organization=123 --location=global \ + --display-name=new-display-name + +POSITIONAL ARGUMENTS + AccessPolicy resource - Identifier. The resource name of the access + policy. + + The following formats are supported: + projects/{project_id}/locations/{location}/accessPolicies/{policy_id} + projects/{project_number}/locations/{location}/accessPolicies/{policy_id} + folders/{folder_id}/locations/{location}/accessPolicies/{policy_id} + organizations/{organization_id}/locations/{location}/accessPolicies/{policy_id} + 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 access_policy on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. This resource can be one of the + following types: [iam.folders.locations.accessPolicies, + iam.organizations.locations.accessPolicies, + iam.projects.locations.accessPolicies]. + + This must be specified. + + ACCESS_POLICY + ID of the accessPolicy or fully qualified identifier for the + accessPolicy. + + To set the access_policy attribute: + ▸ provide the argument access_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --folder=FOLDER + The folder id of the accessPolicy resource. + + To set the folder attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --folder on the command line. Must be + specified for resource of type + [iam.folders.locations.accessPolicies]. + + --location=LOCATION + The location id of the accessPolicy resource. + + To set the location attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + The organization id of the accessPolicy resource. + + To set the organization attribute: + ▸ provide the argument access_policy on the command line with a + fully specified name; + ▸ provide the argument --organization on the command line. Must be + specified for resource of type + [iam.organizations.locations.accessPolicies]. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + The description of the access policy. Must be less than or equal to 63 + characters. + + --etag=ETAG + The etag for the access policy. If this is provided on update, it must + match the server's etag. + + --[no-]validate-only + If set, validate the request and preview the update, but do not + actually post it. Use --validate-only to enable and --no-validate-only + to disable. + + Update annotations. + + At most one of these can be specified: + + --annotations=[ANNOTATIONS,...] + Set annotations to new value. User defined annotations. See + https://google.aip.dev/148#annotations for more details such as + format and size limitations. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --annotations=string=string + + JSON Example: + + --annotations='{"string": "string"}' + + File Example: + + --annotations=path_to_file.(yaml|json) + + --update-annotations=[UPDATE_ANNOTATIONS,...] + Update annotations value or add key value pair. User defined + annotations. See https://google.aip.dev/148#annotations for more + details such as format and size limitations. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + Shorthand Example: + + --update-annotations=string=string + + JSON Example: + + --update-annotations='{"string": "string"}' + + File Example: + + --update-annotations=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-annotations + Clear annotations value and set to empty map. + + --remove-annotations=REMOVE_ANNOTATIONS + Remove existing value from map annotations. Sets remove_annotations + value. + + Shorthand Example: + + --remove-annotations=string,string + + JSON Example: + + --remove-annotations=["string"] + + File Example: + + --remove-annotations=path_to_file.(yaml|json) + + Access policy details. + + --clear-details + Set googleIamV3betaAccessPolicy.details back to default value. + + Update details_rules. + + At most one of these can be specified: + + --details-rules=[conditions=CONDITIONS],[description=DESCRIPTION],[effect=EFFECT],[excludedPrincipals=EXCLUDEDPRINCIPALS],[operation=OPERATION],[principals=PRINCIPALS] + Set details_rules to new value. A list of access policy rules. + + conditions + The conditions that determine whether this rule applies to a + request. Conditions are identified by their key, which is the + FQDN of the service that they are relevant to, e.g.: + + "conditions": { "iam.googleapis.com": } + + Each rule is evaluated independently. If this rule does not + apply to a request, other rules might still apply. Currently + supported keys are: + + ◇ eventarc.googleapis.com// The conditions that determine + whether this rule applies to a request. Conditions are + identified by their key, which is the FQDN of the service + that they are relevant to, e.g.: + + "conditions": { "iam.googleapis.com": { "cel_condition": } } + + Each rule is evaluated independently. If this rule does not + apply to a request, other rules might still apply. Currently + supported keys are: + + ◇ eventarc.googleapis.com + ◇ iam.googleapis.com. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + description + Description of the expression. This is a longer text + which describes the expression, e.g. when hovered over + it in a UI. + + expression + Textual representation of an expression in Common + Expression Language syntax. + + location + String indicating the location of the expression for + error reporting, e.g. a file name and a position in the + file. + + title + Title for the expression, i.e. a short string + describing its purpose. This can be used e.g. in UIs + which allow to enter the expression. + + description + Customer specified description of the rule. Must be less than + or equal to 256 characters. + + effect + The effect of the rule. + + excludedPrincipals + The identities that are excluded from the access policy rule, + even if they are listed in the principals. For example, you + could add a Google group to the principals, then exclude + specific users who belong to that group. + + operation + Attributes that are used to determine whether this rule applies + to a request. + + excludedPermissions + Specifies the permissions that this rule excludes from the + set of affected permissions given by permissions. If a + permission appears in permissions and in + excluded_permissions then it will not be subject to the + policy effect. + + The excluded permissions can be specified using the same + syntax as permissions. + + permissions + The permissions that are explicitly affected by this rule. + Each permission uses the format + {service_fqdn}/{resource}.{verb}, where {service_fqdn} is + the fully qualified domain name for the service. Currently + supported permissions are: + + ▹ eventarc.googleapis.com/messageBuses.publish. + + principals + The identities for which this rule's effect governs using one + or more permissions on Google Cloud resources. This field can + contain the following values: + + ◇ principal://goog/subject/{email_id}: A specific Google + Account. Includes Gmail, Cloud Identity, and Google Workspace + user accounts. For example, + principal://goog/subject/alice@example.com. + + If an identifier that was previously set on a policy is soft deleted, then + calls to read that policy will return the identifier with a deleted + prefix. Users cannot set identifiers with this syntax. + * `deleted:principal://goog/subject/{email_id}?uid={uid}`: A specific + Google Account that was deleted recently. For example, + `deleted:principal://goog/subject/alice@example.com?uid=1234567890`. If + the Google Account is recovered, this identifier reverts to the standard + identifier for a Google Account. + + ◇ deleted:principalSet://goog/group/{group_id}?uid={uid}: A + Google group that was deleted recently. For example, + deleted:principalSet://goog/group/admins@example.com?uid=1234567890. + If the Google group is restored, this identifier reverts to + the standard identifier for a Google group. + + ◇ deleted:principal://iam.googleapis.com/projects/-/serviceAccounts/{service_account_id}?uid={uid}: + A Google Cloud service account that was deleted recently. For + example, + deleted:principal://iam.googleapis.com/projects/-/serviceAccounts/my-service-account@iam.gserviceaccount.com?uid=1234567890. + If the service account is undeleted, this identifier reverts + to the standard identifier for a service account. + + Shorthand Example: + + --details-rules=conditions={string={description=string,expression=string,location=string,title=string}},description=string,effect=string,excludedPrincipals=[string],operation={excludedPermissions=[string],permissions=[string]},principals=[string] --details-rules=conditions={string={description=string,expression=string,location=string,title=string}},description=string,effect=string,excludedPrincipals=[string],operation={excludedPermissions=[string],permissions=[string]},principals=[string] + + JSON Example: + + --details-rules='[{"conditions": {"string": {"description": "string", "expression": "string", "location": "string", "title": "string"}}, "description": "string", "effect": "string", "excludedPrincipals": ["string"], "operation": {"excludedPermissions": ["string"], "permissions": ["string"]}, "principals": ["string"]}]' + + File Example: + + --details-rules=path_to_file.(yaml|json) + + --add-details-rules=[conditions=CONDITIONS],[description=DESCRIPTION],[effect=EFFECT],[excludedPrincipals=EXCLUDEDPRINCIPALS],[operation=OPERATION],[principals=PRINCIPALS] + Add new value to details_rules list. A list of access policy rules. + + conditions + The conditions that determine whether this rule applies to a + request. Conditions are identified by their key, which is the + FQDN of the service that they are relevant to, e.g.: + + "conditions": { "iam.googleapis.com": } + + Each rule is evaluated independently. If this rule does not + apply to a request, other rules might still apply. Currently + supported keys are: + + ◇ eventarc.googleapis.com// The conditions that determine + whether this rule applies to a request. Conditions are + identified by their key, which is the FQDN of the service + that they are relevant to, e.g.: + + "conditions": { "iam.googleapis.com": { "cel_condition": } } + + Each rule is evaluated independently. If this rule does not + apply to a request, other rules might still apply. Currently + supported keys are: + + ◇ eventarc.googleapis.com + ◇ iam.googleapis.com. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + description + Description of the expression. This is a longer text + which describes the expression, e.g. when hovered over + it in a UI. + + expression + Textual representation of an expression in Common + Expression Language syntax. + + location + String indicating the location of the expression for + error reporting, e.g. a file name and a position in the + file. + + title + Title for the expression, i.e. a short string + describing its purpose. This can be used e.g. in UIs + which allow to enter the expression. + + description + Customer specified description of the rule. Must be less than + or equal to 256 characters. + + effect + The effect of the rule. + + excludedPrincipals + The identities that are excluded from the access policy rule, + even if they are listed in the principals. For example, you + could add a Google group to the principals, then exclude + specific users who belong to that group. + + operation + Attributes that are used to determine whether this rule applies + to a request. + + excludedPermissions + Specifies the permissions that this rule excludes from the + set of affected permissions given by permissions. If a + permission appears in permissions and in + excluded_permissions then it will not be subject to the + policy effect. + + The excluded permissions can be specified using the same + syntax as permissions. + + permissions + The permissions that are explicitly affected by this rule. + Each permission uses the format + {service_fqdn}/{resource}.{verb}, where {service_fqdn} is + the fully qualified domain name for the service. Currently + supported permissions are: + + ▹ eventarc.googleapis.com/messageBuses.publish. + + principals + The identities for which this rule's effect governs using one + or more permissions on Google Cloud resources. This field can + contain the following values: + + ◇ principal://goog/subject/{email_id}: A specific Google + Account. Includes Gmail, Cloud Identity, and Google Workspace + user accounts. For example, + principal://goog/subject/alice@example.com. + + If an identifier that was previously set on a policy is soft deleted, then + calls to read that policy will return the identifier with a deleted + prefix. Users cannot set identifiers with this syntax. + * `deleted:principal://goog/subject/{email_id}?uid={uid}`: A specific + Google Account that was deleted recently. For example, + `deleted:principal://goog/subject/alice@example.com?uid=1234567890`. If + the Google Account is recovered, this identifier reverts to the standard + identifier for a Google Account. + + ◇ deleted:principalSet://goog/group/{group_id}?uid={uid}: A + Google group that was deleted recently. For example, + deleted:principalSet://goog/group/admins@example.com?uid=1234567890. + If the Google group is restored, this identifier reverts to + the standard identifier for a Google group. + + ◇ deleted:principal://iam.googleapis.com/projects/-/serviceAccounts/{service_account_id}?uid={uid}: + A Google Cloud service account that was deleted recently. For + example, + deleted:principal://iam.googleapis.com/projects/-/serviceAccounts/my-service-account@iam.gserviceaccount.com?uid=1234567890. + If the service account is undeleted, this identifier reverts + to the standard identifier for a service account. + + Shorthand Example: + + --add-details-rules=conditions={string={description=string,expression=string,location=string,title=string}},description=string,effect=string,excludedPrincipals=[string],operation={excludedPermissions=[string],permissions=[string]},principals=[string] --add-details-rules=conditions={string={description=string,expression=string,location=string,title=string}},description=string,effect=string,excludedPrincipals=[string],operation={excludedPermissions=[string],permissions=[string]},principals=[string] + + JSON Example: + + --add-details-rules='[{"conditions": {"string": {"description": "string", "expression": "string", "location": "string", "title": "string"}}, "description": "string", "effect": "string", "excludedPrincipals": ["string"], "operation": {"excludedPermissions": ["string"], "permissions": ["string"]}, "principals": ["string"]}]' + + File Example: + + --add-details-rules=path_to_file.(yaml|json) + + At most one of these can be specified: + + --clear-details-rules + Clear details_rules value and set to empty list. + + --remove-details-rules=[conditions=CONDITIONS],[description=DESCRIPTION],[effect=EFFECT],[excludedPrincipals=EXCLUDEDPRINCIPALS],[operation=OPERATION],[principals=PRINCIPALS] + Remove existing value from details_rules list. A list of access + policy rules. + + conditions + The conditions that determine whether this rule applies to a + request. Conditions are identified by their key, which is the + FQDN of the service that they are relevant to, e.g.: + + "conditions": { "iam.googleapis.com": } + + Each rule is evaluated independently. If this rule does not + apply to a request, other rules might still apply. Currently + supported keys are: + + ▹ eventarc.googleapis.com// The conditions that determine + whether this rule applies to a request. Conditions are + identified by their key, which is the FQDN of the service + that they are relevant to, e.g.: + + "conditions": { "iam.googleapis.com": { "cel_condition": } } + + Each rule is evaluated independently. If this rule does not + apply to a request, other rules might still apply. Currently + supported keys are: + + ▹ eventarc.googleapis.com + ▹ iam.googleapis.com. + + KEY + Sets KEY value. + + VALUE + Sets VALUE value. + + description + Description of the expression. This is a longer text + which describes the expression, e.g. when hovered + over it in a UI. + + expression + Textual representation of an expression in Common + Expression Language syntax. + + location + String indicating the location of the expression for + error reporting, e.g. a file name and a position in + the file. + + title + Title for the expression, i.e. a short string + describing its purpose. This can be used e.g. in UIs + which allow to enter the expression. + + description + Customer specified description of the rule. Must be less than + or equal to 256 characters. + + effect + The effect of the rule. + + excludedPrincipals + The identities that are excluded from the access policy rule, + even if they are listed in the principals. For example, you + could add a Google group to the principals, then exclude + specific users who belong to that group. + + operation + Attributes that are used to determine whether this rule + applies to a request. + + excludedPermissions + Specifies the permissions that this rule excludes from + the set of affected permissions given by permissions. If + a permission appears in permissions and in + excluded_permissions then it will not be subject to the + policy effect. + + The excluded permissions can be specified using the same + syntax as permissions. + + permissions + The permissions that are explicitly affected by this + rule. Each permission uses the format + {service_fqdn}/{resource}.{verb}, where {service_fqdn} is + the fully qualified domain name for the service. + Currently supported permissions are: + + ▪ eventarc.googleapis.com/messageBuses.publish. + + principals + The identities for which this rule's effect governs using one + or more permissions on Google Cloud resources. This field can + contain the following values: + + ▹ principal://goog/subject/{email_id}: A specific Google + Account. Includes Gmail, Cloud Identity, and Google + Workspace user accounts. For example, + principal://goog/subject/alice@example.com. + + If an identifier that was previously set on a policy is soft deleted, then + calls to read that policy will return the identifier with a deleted + prefix. Users cannot set identifiers with this syntax. + * `deleted:principal://goog/subject/{email_id}?uid={uid}`: A specific + Google Account that was deleted recently. For example, + `deleted:principal://goog/subject/alice@example.com?uid=1234567890`. If + the Google Account is recovered, this identifier reverts to the standard + identifier for a Google Account. + + ▹ deleted:principalSet://goog/group/{group_id}?uid={uid}: A + Google group that was deleted recently. For example, + deleted:principalSet://goog/group/admins@example.com?uid=1234567890. + If the Google group is restored, this identifier reverts to + the standard identifier for a Google group. + + ▹ deleted:principal://iam.googleapis.com/projects/-/serviceAccounts/{service_account_id}?uid={uid}: + A Google Cloud service account that was deleted recently. + For example, + deleted:principal://iam.googleapis.com/projects/-/serviceAccounts/my-service-account@iam.gserviceaccount.com?uid=1234567890. + If the service account is undeleted, this identifier + reverts to the standard identifier for a service account. + + Shorthand Example: + + --remove-details-rules=conditions={string={description=string,expression=string,location=string,title=string}},description=string,effect=string,excludedPrincipals=[string],operation={excludedPermissions=[string],permissions=[string]},principals=[string] --remove-details-rules=conditions={string={description=string,expression=string,location=string,title=string}},description=string,effect=string,excludedPrincipals=[string],operation={excludedPermissions=[string],permissions=[string]},principals=[string] + + JSON Example: + + --remove-details-rules='[{"conditions": {"string": {"description": "string", "expression": "string", "location": "string", "title": "string"}}, "description": "string", "effect": "string", "excludedPrincipals": ["string"], "operation": {"excludedPermissions": ["string"], "permissions": ["string"]}, "principals": ["string"]}]' + + File Example: + + --remove-details-rules=path_to_file.(yaml|json) + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the iam/v3beta API. The full documentation for this API + can be found at: https://cloud.google.com/iam/ + +NOTES + This command is currently in beta and might change without notice. + diff --git a/gcloud/beta/iam/help b/gcloud/beta/iam/help index b6552f992..42d61539c 100644 --- a/gcloud/beta/iam/help +++ b/gcloud/beta/iam/help @@ -27,6 +27,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + access-policies + (BETA) Manage Access Policy resources. + policies (BETA) Manage IAM deny policies. diff --git a/gcloud/beta/iam/policy-bindings/create b/gcloud/beta/iam/policy-bindings/create index 09734371b..897976c27 100644 --- a/gcloud/beta/iam/policy-bindings/create +++ b/gcloud/beta/iam/policy-bindings/create @@ -5,7 +5,9 @@ SYNOPSIS gcloud beta iam policy-bindings create (POLICY_BINDING : --folder=FOLDER --location=LOCATION --organization=ORGANIZATION) - --policy=POLICY --target-principal-set=TARGET_PRINCIPAL_SET + --policy=POLICY + (--target-principal-set=TARGET_PRINCIPAL_SET + | --target-resource=TARGET_RESOURCE) [--annotations=[ANNOTATIONS,...]] [--async] [--display-name=DISPLAY_NAME] [--etag=ETAG] [--policy-kind=POLICY_KIND] [--condition-description=CONDITION_DESCRIPTION @@ -98,8 +100,8 @@ REQUIRED FLAGS The resource name of the policy to be bound. The binding parent and policy must belong to the same organization. - Target is the full resource name of the resource to which the policy will - be bound. Immutable once set. + The full resource name of the resource to which the policy will be bound. + Immutable once set. This must be specified. @@ -108,29 +110,42 @@ REQUIRED FLAGS At most one of these can be specified: --target-principal-set=TARGET_PRINCIPAL_SET - Full Resource Name used for principal access boundary policy - bindings. The principal set must be directly parented by the policy - binding's parent or same as the parent if the target is a - project/folder/organization. + The full resource name that's used for principal access boundary + policy bindings. The principal set must be directly parented by the + policy binding's parent or same as the parent if the target is a + project, folder, or organization. Examples: - ▫ For binding's parented by an organization: + + ▫ For bindings parented by an organization: ◇ Organization: //cloudresourcemanager.googleapis.com/organizations/ORGANIZATION_ID ◇ Workforce Identity: //iam.googleapis.com/locations/global/workforcePools/WORKFORCE_POOL_ID ◇ Workspace Identity: //iam.googleapis.com/locations/global/workspace/WORKSPACE_ID - ▫ For binding's parented by a folder: + ▫ For bindings parented by a folder: ◇ Folder: //cloudresourcemanager.googleapis.com/folders/FOLDER_ID - ▫ For binding's parented by a project: + ▫ For bindings parented by a project: ◇ Project: ▹ //cloudresourcemanager.googleapis.com/projects/PROJECT_NUMBER ▹ //cloudresourcemanager.googleapis.com/projects/PROJECT_ID ◇ Workload Identity Pool: //iam.googleapis.com/projects/PROJECT_NUMBER/locations/LOCATION/workloadIdentityPools/WORKLOAD_POOL_ID + --target-resource=TARGET_RESOURCE + The full resource name that's used for access policy bindings + Examples: + + ▹ Organization: + //cloudresourcemanager.googleapis.com/organizations/ORGANIZATION_ID + ▹ Folder: + //cloudresourcemanager.googleapis.com/folders/FOLDER_ID + ▹ Project: + ▪ //cloudresourcemanager.googleapis.com/projects/PROJECT_NUMBER + ▪ //cloudresourcemanager.googleapis.com/projects/PROJECT_ID + OPTIONAL FLAGS --annotations=[ANNOTATIONS,...] User-defined annotations. See https://google.aip.dev/148#annotations diff --git a/gcloud/beta/iam/workforce-pools/providers/keys/create b/gcloud/beta/iam/workforce-pools/providers/keys/create index eb4611a7b..9e862b37e 100644 --- a/gcloud/beta/iam/workforce-pools/providers/keys/create +++ b/gcloud/beta/iam/workforce-pools/providers/keys/create @@ -76,7 +76,7 @@ REQUIRED FLAGS --use=USE The purpose of the key. USE must be one of: encryption, - key-use-unspecified. + key-use-unspecified, signing. OPTIONAL FLAGS --async diff --git a/gcloud/beta/model-armor/floorsettings/update b/gcloud/beta/model-armor/floorsettings/update index fe5bf2a5c..754f824d9 100644 --- a/gcloud/beta/model-armor/floorsettings/update +++ b/gcloud/beta/model-armor/floorsettings/update @@ -5,7 +5,11 @@ NAME SYNOPSIS gcloud beta model-armor floorsettings update --full-uri=FULL_URI [--enable-floor-setting-enforcement=ENABLE_FLOOR_SETTING_ENFORCEMENT] + [--[no-]enable-multi-language-detection] [--malicious-uri-filter-settings-enforcement=MALICIOUS_URI_FILTER_SETTINGS_ENFORCEMENT] + [--add-integrated-services=[INTEGRATED_SERVICE,...] + | --clear-integrated-services + | --remove-integrated-services=[INTEGRATED_SERVICE,...]] [--add-rai-settings-filters=confidenceLevel=CONFIDENCELEVEL], [filterType=FILTERTYPE] | --clear-rai-settings-filters | --rai-settings-filters=confidenceLevel=CONFIDENCELEVEL], @@ -13,6 +17,10 @@ SYNOPSIS | --remove-rai-settings-filters=confidenceLevel=CONFIDENCELEVEL], [filterType=FILTERTYPE]] [--advanced-config-deidentify-template=ADVANCED_CONFIG_DEIDENTIFY_TEMPLATE --advanced-config-inspect-template=ADVANCED_CONFIG_INSPECT_TEMPLATE --basic-config-filter-enforcement=BASIC_CONFIG_FILTER_ENFORCEMENT] + [--[no-]enable-google-mcp-server-cloud-logging + --google-mcp-server-enforcement-type=GOOGLE_MCP_SERVER_ENFORCEMENT_TYPE] + [--[no-]enable-vertex-ai-cloud-logging + --vertex-ai-enforcement-type=VERTEX_AI_ENFORCEMENT_TYPE] [--pi-and-jailbreak-filter-settings-confidence-level=PI_AND_JAILBREAK_FILTER_SETTINGS_CONFIDENCE_LEVEL --pi-and-jailbreak-filter-settings-enforcement=PI_AND_JAILBREAK_FILTER_SETTINGS_ENFORCEMENT] [GCLOUD_WIDE_FLAG ...] @@ -27,11 +35,35 @@ OPTIONAL FLAGS --enable-floor-setting-enforcement=ENABLE_FLOOR_SETTING_ENFORCEMENT Enable or disable the floor setting enforcement + Multi language detection enablement. + + --[no-]enable-multi-language-detection + Enable multi-language detection for floor setting, allowing Model + Armor to process content in multiple languages. Use + --enable-multi-language-detection to enable and + --no-enable-multi-language-detection to disable. + Malicious uri filter settings. --malicious-uri-filter-settings-enforcement=MALICIOUS_URI_FILTER_SETTINGS_ENFORCEMENT Malicious URI filter settings. + Manage integrated services to apply Model Armor floor settings. Integrated + services will have Model Armor sanitization enabled project-wide. + + At most one of these can be specified: + + --add-integrated-services=[INTEGRATED_SERVICE,...] + Set the list of integrated services for the floor setting. This can + be used to enable project-wide Model Armor sanitization for the + respective services. + + --clear-integrated-services + Clear all integrated services from the floor setting. + + --remove-integrated-services=[INTEGRATED_SERVICE,...] + Remove specified service(s) from the list of integrated services. + RAI filter settings. At most one of these can be specified: @@ -99,6 +131,30 @@ OPTIONAL FLAGS The sdp filter settings enforcement. The value can be either "ENABLED" or "DISABLED" + Options for Google MCP server sanitization. + + --[no-]enable-google-mcp-server-cloud-logging + Enable Cloud Logging for Google MCP server sanitization to log Model + Armor sanitization results. Use + --enable-google-mcp-server-cloud-logging to enable and + --no-enable-google-mcp-server-cloud-logging to disable. + + --google-mcp-server-enforcement-type=GOOGLE_MCP_SERVER_ENFORCEMENT_TYPE + Specifies the enforcement mode for Google MCP server sanitization, + such as "INSPECT_ONLY" or "INSPECT_AND_BLOCK". Default is + "INSPECT_ONLY". + + Options for Vertex AI sanitization. + + --[no-]enable-vertex-ai-cloud-logging + Enable Cloud Logging for Vertex AI sanitization to log Model Armor + sanitization results. Use --enable-vertex-ai-cloud-logging to enable + and --no-enable-vertex-ai-cloud-logging to disable. + + --vertex-ai-enforcement-type=VERTEX_AI_ENFORCEMENT_TYPE + Specifies the enforcement mode for Vertex AI sanitization, such as + "INSPECT_ONLY" or "INSPECT_AND_BLOCK". Default is "INSPECT_ONLY". + PI and jailbreak filter settings. --pi-and-jailbreak-filter-settings-confidence-level=PI_AND_JAILBREAK_FILTER_SETTINGS_CONFIDENCE_LEVEL diff --git a/gcloud/beta/monitoring/alerts/describe b/gcloud/beta/monitoring/alerts/describe new file mode 100644 index 000000000..9dcf60ef8 --- /dev/null +++ b/gcloud/beta/monitoring/alerts/describe @@ -0,0 +1,46 @@ +NAME + gcloud beta monitoring alerts describe - describe an alert + +SYNOPSIS + gcloud beta monitoring alerts describe ALERT [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an alert. + +POSITIONAL ARGUMENTS + Alert resource - The alert to describe. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument alert 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. + + ALERT + ID of the alert or fully qualified identifier for the alert. + + To set the alert attribute: + ▸ provide the argument alert on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha monitoring alerts describe + diff --git a/gcloud/beta/monitoring/alerts/help b/gcloud/beta/monitoring/alerts/help new file mode 100644 index 000000000..2928aaf04 --- /dev/null +++ b/gcloud/beta/monitoring/alerts/help @@ -0,0 +1,32 @@ +NAME + gcloud beta monitoring alerts - manage Cloud Monitoring alerts + +SYNOPSIS + gcloud beta monitoring alerts COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Monitoring alerts. + + More information can be found here: + https://cloud.google.com/monitoring/api/v3/ + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describe an alert. + + list + (BETA) List alerts. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha monitoring alerts + diff --git a/gcloud/beta/monitoring/alerts/list b/gcloud/beta/monitoring/alerts/list new file mode 100644 index 000000000..55bcdb6c7 --- /dev/null +++ b/gcloud/beta/monitoring/alerts/list @@ -0,0 +1,81 @@ +NAME + gcloud beta monitoring alerts list - list alerts + +SYNOPSIS + gcloud beta monitoring alerts list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE; default=1000] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List alerts for a project. + +EXAMPLES + To list all open alerts: + + $ gcloud beta monitoring alerts list --filter="state='OPEN'" + + To order alerts by when the alert was opened: + + $ gcloud beta monitoring alerts list --sort-by=openTime + + To order alerts by when the alert was opened in reverse order: + + $ gcloud beta monitoring alerts list --sort-by="~openTime" + + To list alerts for a specific policy: + + $ gcloud beta monitoring alerts list \ + --filter="policy.displayName='My Policy'" + + More information can be found at + https://cloud.google.com/sdk/gcloud/reference/topic/filters + +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; default=1000 + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + 1000. Paging may be applied before or after --filter and --limit + depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the monitoring/v3 API. The full documentation for this + API can be found at: https://cloud.google.com/monitoring/api/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha monitoring alerts list + diff --git a/gcloud/beta/monitoring/help b/gcloud/beta/monitoring/help index 86b48e296..87eaef368 100644 --- a/gcloud/beta/monitoring/help +++ b/gcloud/beta/monitoring/help @@ -21,6 +21,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + alerts + (BETA) Manage Cloud Monitoring alerts. + channel-descriptors (BETA) Read Cloud Monitoring notification channel descriptors. diff --git a/gcloud/beta/netapp/help b/gcloud/beta/netapp/help index d8de85bfc..f6725bac9 100644 --- a/gcloud/beta/netapp/help +++ b/gcloud/beta/netapp/help @@ -35,6 +35,9 @@ GROUPS backup-vaults (BETA) Create and manage Cloud NetApp Backup Vaults. + host-groups + (BETA) Create and manage Cloud NetApp Host Groups. + kms-configs (BETA) Create and manage Cloud NetApp Volumes KMS Configs. diff --git a/gcloud/beta/netapp/host-groups/create b/gcloud/beta/netapp/host-groups/create new file mode 100644 index 000000000..b6d52fe9b --- /dev/null +++ b/gcloud/beta/netapp/host-groups/create @@ -0,0 +1,99 @@ +NAME + gcloud beta netapp host-groups create - create a Cloud NetApp Host Group + +SYNOPSIS + gcloud beta netapp host-groups create (HOST_GROUP : --location=LOCATION) + --hosts=HOST,[HOST,...] --os-type=OS_TYPE --type=TYPE [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a Cloud NetApp Host Group. + +EXAMPLES + The following command creates a Host Group named NAME using the required + arguments: + + $ gcloud beta netapp host-groups create NAME \ + --location=us-central1 --type=ISCSI_INITIATOR \ + --hosts=host1,host2 --os-type=LINUX + +POSITIONAL ARGUMENTS + Host group resource - The Host Group to create. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument host_group 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. + + HOST_GROUP + ID of the host_group or fully qualified identifier for the + host_group. + + To set the host_group attribute: + ▸ provide the argument host_group 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 host_group. + + To set the location attribute: + ▸ provide the argument host_group on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +REQUIRED FLAGS + --hosts=HOST,[HOST,...] + List of hosts in the host group. + + --os-type=OS_TYPE + String indicating the OS type of the hosts in the host group. The + supported values are: 'LINUX', 'WINDOWS', 'ESXI'. OS_TYPE must be one + of: LINUX, WINDOWS, ESXI. + + --type=TYPE + String indicating the type of host group. The supported values are: + 'ISCSI_INITIATOR'. TYPE must be (only one value is supported): + ISCSI_INITIATOR. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A description of the Cloud NetApp Host Group + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud netapp host-groups create + + $ gcloud alpha netapp host-groups create + diff --git a/gcloud/beta/netapp/host-groups/delete b/gcloud/beta/netapp/host-groups/delete new file mode 100644 index 000000000..1c83df60b --- /dev/null +++ b/gcloud/beta/netapp/host-groups/delete @@ -0,0 +1,75 @@ +NAME + gcloud beta netapp host-groups delete - delete a Cloud NetApp Host Group + +SYNOPSIS + gcloud beta netapp host-groups delete (HOST_GROUP : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Cloud NetApp Host Group. + +EXAMPLES + The following command deletes a Host Group named NAME: + + $ gcloud beta netapp host-groups delete NAME --location=us-central1 + + To delete a Host Group named NAME asynchronously, run the following + command: + + $ gcloud beta netapp host-groups delete NAME \ + --location=us-central1 --async + +POSITIONAL ARGUMENTS + Host group resource - The Host Group 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 host_group 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. + + HOST_GROUP + ID of the host_group or fully qualified identifier for the + host_group. + + To set the host_group attribute: + ▸ provide the argument host_group 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 host_group. + + To set the location attribute: + ▸ provide the argument host_group on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud netapp host-groups delete + + $ gcloud alpha netapp host-groups delete + diff --git a/gcloud/beta/netapp/host-groups/describe b/gcloud/beta/netapp/host-groups/describe new file mode 100644 index 000000000..bd0bf1006 --- /dev/null +++ b/gcloud/beta/netapp/host-groups/describe @@ -0,0 +1,66 @@ +NAME + gcloud beta netapp host-groups describe - describe a Cloud NetApp Host + Group + +SYNOPSIS + gcloud beta netapp host-groups describe (HOST_GROUP : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a Cloud NetApp Host Group. + +EXAMPLES + The following command describes a Host Group named NAME in the given + location: + + $ gcloud beta netapp host-groups describe NAME --location=us-central1 + +POSITIONAL ARGUMENTS + Host group resource - The Host Group 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 host_group 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. + + HOST_GROUP + ID of the host_group or fully qualified identifier for the + host_group. + + To set the host_group attribute: + ▸ provide the argument host_group 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 host_group. + + To set the location attribute: + ▸ provide the argument host_group on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud netapp host-groups describe + + $ gcloud alpha netapp host-groups describe + diff --git a/gcloud/beta/netapp/host-groups/help b/gcloud/beta/netapp/host-groups/help new file mode 100644 index 000000000..2a242ace2 --- /dev/null +++ b/gcloud/beta/netapp/host-groups/help @@ -0,0 +1,40 @@ +NAME + gcloud beta netapp host-groups - create and manage Cloud NetApp Host Groups + +SYNOPSIS + gcloud beta netapp host-groups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create and manage Cloud NetApp Host Groups. + +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 Cloud NetApp Host Group. + + delete + (BETA) Delete a Cloud NetApp Host Group. + + describe + (BETA) Describe a Cloud NetApp Host Group. + + list + (BETA) List Cloud NetApp Host Groups. + + update + (BETA) Update a Cloud NetApp Host Group. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud netapp host-groups + + $ gcloud alpha netapp host-groups + diff --git a/gcloud/beta/netapp/host-groups/list b/gcloud/beta/netapp/host-groups/list new file mode 100644 index 000000000..2874259a5 --- /dev/null +++ b/gcloud/beta/netapp/host-groups/list @@ -0,0 +1,85 @@ +NAME + gcloud beta netapp host-groups list - list Cloud NetApp Host Groups + +SYNOPSIS + gcloud beta netapp host-groups list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Lists Cloud NetApp Host Groups. + +EXAMPLES + The following command lists all Host Groups in the given location: + + $ gcloud beta netapp host-groups list --location=us-central1 + +FLAGS + Location resource - The location in which to list Host Groups. 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; + ◆ uses all locations by default. with a fully specified name; + ◆ set the property netapp/location 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; + ▸ uses all locations by default.; + ▸ set the property netapp/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud netapp host-groups list + + $ gcloud alpha netapp host-groups list + diff --git a/gcloud/beta/netapp/host-groups/update b/gcloud/beta/netapp/host-groups/update new file mode 100644 index 000000000..87f6cd736 --- /dev/null +++ b/gcloud/beta/netapp/host-groups/update @@ -0,0 +1,109 @@ +NAME + gcloud beta netapp host-groups update - update a Cloud NetApp Host Group + +SYNOPSIS + gcloud beta netapp host-groups update (HOST_GROUP : --location=LOCATION) + [--async] [--description=DESCRIPTION] [--hosts=HOST,[HOST,...]] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a Cloud NetApp Host Group and its specified parameters. + +EXAMPLES + The following command updates a Host Group named NAME and its specified + parameters: + + $ gcloud beta netapp host-groups update NAME \ + --location=us-central1 --description="new description" \ + --hosts="host3,host4" --update-labels=key2=val2 + +POSITIONAL ARGUMENTS + Host group resource - The Host Group 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 host_group 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. + + HOST_GROUP + ID of the host_group or fully qualified identifier for the + host_group. + + To set the host_group attribute: + ▸ provide the argument host_group 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 host_group. + + To set the location attribute: + ▸ provide the argument host_group on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A description of the Cloud NetApp Host Group + + --hosts=HOST,[HOST,...] + List of hosts in the host group. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta netapp host-groups update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta netapp host-groups update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud netapp host-groups update + + $ gcloud alpha netapp host-groups update + diff --git a/gcloud/beta/netapp/storage-pools/create b/gcloud/beta/netapp/storage-pools/create index c6327639b..2b29c1c35 100644 --- a/gcloud/beta/netapp/storage-pools/create +++ b/gcloud/beta/netapp/storage-pools/create @@ -15,7 +15,7 @@ SYNOPSIS [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] [--qos-type=QOS_TYPE] [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] [--total-throughput=TOTAL_THROUGHPUT] - [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--type=TYPE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates a Storage Pool to contain Volumes with a specified Service @@ -214,6 +214,16 @@ OPTIONAL FLAGS The total throughput of the Storage Pool in MiB/s or GiB/s units. If no throughput unit is specified, MiB/s is assumed. + --type=TYPE + The type of the Storage Pool. FILE pools support file-based volumes + only. UNIFIED pools support both file and block volumes. TYPE must be + one of: + + file + File-based volumes only (default). + unified + Both file and block volumes. + --zone=ZONE String indicating active zone of the Storage Pool diff --git a/gcloud/beta/netapp/volumes/create b/gcloud/beta/netapp/volumes/create index 01cdb8ebf..9583280ad 100644 --- a/gcloud/beta/netapp/volumes/create +++ b/gcloud/beta/netapp/volumes/create @@ -8,6 +8,8 @@ SYNOPSIS [--backup-config=[backup-policies=BACKUP-POLICIES], [backup-vault=BACKUP-VAULT], [enable-scheduled-backups=ENABLE-SCHEDULED-BACKUPS]] + [--block-devices=[host-groups=HOST-GROUPS], + [name=NAME],[os-type=OS-TYPE],[size-gib=SIZE-GIB]] [--cache-parameters=[cache-config=CACHE-CONFIG], [enable-global-file-lock=ENABLE-GLOBAL-FILE-LOCK], [peer-cluster-name=PEER-CLUSTER-NAME], @@ -158,6 +160,24 @@ OPTIONAL FLAGS enable-scheduled-backups is a Boolean value indicating whether or not scheduled backups are enabled on the volume. + --block-devices=[host-groups=HOST-GROUPS],[name=NAME],[os-type=OS-TYPE],[size-gib=SIZE-GIB] + A block device to be created with the volume. + + This flag can be repeated to specify multiple block devices. + + The following keys are available: + name + A user-defined name for the block device. + host-groups + A comma-separated list of host groups that can mount the block + volume. + os-type + The OS type of the volume. Allowed values are OS_TYPE_UNSPECIFIED, + LINUX, WINDOWS. + size-gib + The size of the block device in GiB. Note that this value is + ignored during volume creation and is system-managed. + --cache-parameters=[cache-config=CACHE-CONFIG],[enable-global-file-lock=ENABLE-GLOBAL-FILE-LOCK],[peer-cluster-name=PEER-CLUSTER-NAME],[peer-ip-addresses=PEER-IP-ADDRESSES],[peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME] Cache Parameters contains cache parameters of a volume. diff --git a/gcloud/beta/netapp/volumes/update b/gcloud/beta/netapp/volumes/update index 967e76717..3ef766938 100644 --- a/gcloud/beta/netapp/volumes/update +++ b/gcloud/beta/netapp/volumes/update @@ -6,6 +6,8 @@ SYNOPSIS [--backup-config=[backup-policies=BACKUP-POLICIES], [backup-vault=BACKUP-VAULT], [enable-scheduled-backups=ENABLE-SCHEDULED-BACKUPS]] + [--block-devices=[host-groups=HOST-GROUPS], + [name=NAME],[os-type=OS-TYPE],[size-gib=SIZE-GIB]] [--cache-parameters=[cache-config=CACHE-CONFIG], [enable-global-file-lock=ENABLE-GLOBAL-FILE-LOCK], [peer-cluster-name=PEER-CLUSTER-NAME], @@ -105,6 +107,24 @@ FLAGS enable-scheduled-backups is a Boolean value indicating whether or not scheduled backups are enabled on the volume. + --block-devices=[host-groups=HOST-GROUPS],[name=NAME],[os-type=OS-TYPE],[size-gib=SIZE-GIB] + A block device to be created with the volume. + + This flag can be repeated to specify multiple block devices. + + The following keys are available: + name + A user-defined name for the block device. + host-groups + A comma-separated list of host groups that can mount the block + volume. + os-type + The OS type of the volume. Allowed values are OS_TYPE_UNSPECIFIED, + LINUX, WINDOWS. + size-gib + The size of the block device in GiB. Note that this value is + ignored during volume creation and is system-managed. + --cache-parameters=[cache-config=CACHE-CONFIG],[enable-global-file-lock=ENABLE-GLOBAL-FILE-LOCK],[peer-cluster-name=PEER-CLUSTER-NAME],[peer-ip-addresses=PEER-IP-ADDRESSES],[peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME] Cache Parameters contains cache parameters of a volume. diff --git a/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/create b/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/create index dc01c2752..8de43d06c 100644 --- a/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/create +++ b/gcloud/beta/network-connectivity/spokes/linked-producer-vpc-network/create @@ -17,10 +17,10 @@ EXAMPLES $ gcloud beta network-connectivity spokes \ linked-producer-vpc-network create myspoke \ - --hub="https://www.googleapis.com/networkconnectivity/v1/project\ - s/my-project/locations/global/hubs/my-hub" --global \ - --network="https://www.googleapis.com/compute/v1/projects/my-pro\ - ject/global/networks/my-vpc" --peering="my-peering-name" \ + --hub=https://www.googleapis.com/networkconnectivity/v1/\ + projects/my-project/locations/global/hubs/my-hub --global \ + --network=https://www.googleapis.com/compute/v1/projects/\ + my-project/global/networks/my-vpc --peering=my-peering-name POSITIONAL ARGUMENTS Spoke resource - Name of the spoke to create. This represents a Cloud diff --git a/gcloud/beta/network-connectivity/spokes/linked-vpc-network/create b/gcloud/beta/network-connectivity/spokes/linked-vpc-network/create index e28e6db77..79972f327 100644 --- a/gcloud/beta/network-connectivity/spokes/linked-vpc-network/create +++ b/gcloud/beta/network-connectivity/spokes/linked-vpc-network/create @@ -17,10 +17,10 @@ EXAMPLES $ gcloud beta network-connectivity spokes linked-vpc-network \ create myspoke \ - --hub="https://www.googleapis.com/networkconnectivity/v1/project\ - s/my-project/locations/global/hubs/my-hub" --global \ - --vpc-network="https://www.googleapis.com/compute/v1/projects/my\ - -project/global/networks/my-vpc" + --hub=https://www.googleapis.com/networkconnectivity/v1/\ + projects/my-project/locations/global/hubs/my-hub --global \ + --vpc-network=https://www.googleapis.com/compute/v1/projects/\ + my-project/global/networks/my-vpc POSITIONAL ARGUMENTS Spoke resource - Name of the spoke to create. This represents a Cloud diff --git a/gcloud/beta/network-management/help b/gcloud/beta/network-management/help index 3090a462b..ea640b47e 100644 --- a/gcloud/beta/network-management/help +++ b/gcloud/beta/network-management/help @@ -25,10 +25,8 @@ GROUPS (BETA) Manage the VPC Flow Logs configurations. NOTES - This command is currently in beta and might change without notice. These - variants are also available: + This command is currently in beta and might change without notice. This + variant is also available: $ gcloud network-management - $ gcloud alpha network-management - diff --git a/gcloud/beta/network-security/intercept-endpoint-groups/create b/gcloud/beta/network-security/intercept-endpoint-groups/create index 9c8e0c98d..099362537 100644 --- a/gcloud/beta/network-security/intercept-endpoint-groups/create +++ b/gcloud/beta/network-security/intercept-endpoint-groups/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta network-security intercept-endpoint-groups create (INTERCEPT_ENDPOINT_GROUP : --location=LOCATION) (--intercept-deployment-group=INTERCEPT_DEPLOYMENT_GROUP - : --intercept-deployment-group-location=INTERCEPT_DEPLOYMENT_GROUP_LOCATION) + : --intercept-deployment-group-location=INTERCEPT_DEPLOYMENT_GROUP_LOCATION --intercept-deployment-group-project=INTERCEPT_DEPLOYMENT_GROUP_PROJECT) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] @@ -83,14 +83,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Intercept deployment group resource - Intercept Deployment Group. 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 --intercept-deployment-group on the command line - with a fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. + resource. This must be specified. @@ -117,6 +110,19 @@ REQUIRED FLAGS ▸ provide the argument INTERCEPT_ENDPOINT_GROUP on the command line with a fully specified name. + --intercept-deployment-group-project=INTERCEPT_DEPLOYMENT_GROUP_PROJECT + Project of the intercept deployment group. + + To set the project attribute: + ▸ provide the argument --intercept-deployment-group on the command + line with a fully specified name; + ▸ provide the argument --intercept-deployment-group-project on the + command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project; + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP on the command line + with a fully specified name. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/beta/network-security/mirroring-endpoint-groups/create b/gcloud/beta/network-security/mirroring-endpoint-groups/create index eec9c5e87..fa9db5751 100644 --- a/gcloud/beta/network-security/mirroring-endpoint-groups/create +++ b/gcloud/beta/network-security/mirroring-endpoint-groups/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud beta network-security mirroring-endpoint-groups create (MIRRORING_ENDPOINT_GROUP : --location=LOCATION) ([--mirroring-deployment-group=MIRRORING_DEPLOYMENT_GROUP - : --mirroring-deployment-group-location=MIRRORING_DEPLOYMENT_GROUP_LOCATION]) + : --mirroring-deployment-group-location=MIRRORING_DEPLOYMENT_GROUP_LOCATION --mirroring-deployment-group-project=MIRRORING_DEPLOYMENT_GROUP_PROJECT]) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] @@ -85,14 +85,7 @@ REQUIRED FLAGS Mirroring deployment group resource - Mirroring Deployment Group. 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 --mirroring-deployment-group on the command - line with a fully specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. + resource. --mirroring-deployment-group=MIRRORING_DEPLOYMENT_GROUP ID of the mirroring deployment group or fully qualified identifier @@ -117,6 +110,19 @@ REQUIRED FLAGS ▫ provide the argument MIRRORING_ENDPOINT_GROUP on the command line with a fully specified name. + --mirroring-deployment-group-project=MIRRORING_DEPLOYMENT_GROUP_PROJECT + Project of the mirroring deployment group. + + To set the project attribute: + ▫ provide the argument --mirroring-deployment-group on the + command line with a fully specified name; + ▫ provide the argument --mirroring-deployment-group-project on + the command line; + ▫ provide the argument --project on the command line; + ▫ set the property core/project; + ▫ provide the argument MIRRORING_ENDPOINT_GROUP on the command + line with a fully specified name. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/beta/network-services/multicast-domain-activations/create b/gcloud/beta/network-services/multicast-domain-activations/create index d5825b61d..20c026697 100644 --- a/gcloud/beta/network-services/multicast-domain-activations/create +++ b/gcloud/beta/network-services/multicast-domain-activations/create @@ -6,7 +6,8 @@ SYNOPSIS gcloud beta network-services multicast-domain-activations create (MULTICAST_DOMAIN_ACTIVATION : --location=LOCATION) --multicast-domain=MULTICAST_DOMAIN [--async] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--disable-placement-policy] + [--labels=[KEY=VALUE,...]] [--aggr-egress-pps=AGGR_EGRESS_PPS : --aggr-ingress-pps=AGGR_INGRESS_PPS --avg-packet-size=AVG_PACKET_SIZE @@ -24,12 +25,12 @@ EXAMPLES location 'zone'. $ gcloud beta network-services multicast-domain-activations create \ - my-multicast-group-definition --multicast-domain=path-to-md \ + my-multicast-domain-activation --multicast-domain=path-to-md \ --location=zone POSITIONAL ARGUMENTS - Multicast domain activation resource - Name of the multicast group - definition to be created. The arguments in this group can be used to + Multicast domain activation resource - Name of the multicast domain + activation to be created. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -72,6 +73,10 @@ OPTIONAL FLAGS --description=DESCRIPTION The description for the multicast domain activation. + --disable-placement-policy + True to disable the use of the placement policy for this multicast + domain activation. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/beta/pubsub/snapshots/create b/gcloud/beta/pubsub/snapshots/create index 1bc22855d..9fc9cce77 100644 --- a/gcloud/beta/pubsub/snapshots/create +++ b/gcloud/beta/pubsub/snapshots/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud beta pubsub snapshots create SNAPSHOT [SNAPSHOT ...] --subscription=SUBSCRIPTION [--labels=[KEY=VALUE,...]] - [--subscription-project=SUBSCRIPTION_PROJECT] [GCLOUD_WIDE_FLAG ...] + [--subscription-project=SUBSCRIPTION_PROJECT] [--tags=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Creates one or more Cloud Pub/Sub snapshots. @@ -36,6 +37,11 @@ OPTIONAL FLAGS The name of the project the provided subscription belongs to. If not set, it defaults to the currently selected cloud project. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. Example: + 123/environment=production,123/costCenter=marketing + 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/pubsub/subscriptions/create b/gcloud/beta/pubsub/subscriptions/create index 4231b9787..32b28462e 100644 --- a/gcloud/beta/pubsub/subscriptions/create +++ b/gcloud/beta/pubsub/subscriptions/create @@ -10,7 +10,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--message-filter=MESSAGE_FILTER] [--message-retention-duration=MESSAGE_RETENTION_DURATION] [--message-transforms-file=MESSAGE_TRANSFORMS_FILE] - [--retain-acked-messages] + [--retain-acked-messages] [--tags=[KEY=VALUE,...]] [[--bigquery-table=BIGQUERY_TABLE : --bigquery-service-account-email=BIGQUERY_SERVICE_ACCOUNT_EMAIL --drop-unknown-fields --write-metadata --use-table-schema @@ -139,6 +139,11 @@ OPTIONAL FLAGS retained by default. Use --no-retain-acked-messages to disable this flag. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. Example: + 123/environment=production,123/costCenter=marketing + At most one of these can be specified: BigQuery Config Options. The Cloud Pub/Sub service account associated diff --git a/gcloud/beta/pubsub/topics/create b/gcloud/beta/pubsub/topics/create index 4d88185b9..a6bf78cb3 100644 --- a/gcloud/beta/pubsub/topics/create +++ b/gcloud/beta/pubsub/topics/create @@ -6,6 +6,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--message-retention-duration=MESSAGE_RETENTION_DURATION] [--message-transforms-file=MESSAGE_TRANSFORMS_FILE] + [--tags=[KEY=VALUE,...]] [--ingestion-log-severity=INGESTION_LOG_SEVERITY --aws-msk-ingestion-aws-role-arn=AWS_MSK_INGESTION_AWS_ROLE_ARN --aws-msk-ingestion-cluster-arn=AWS_MSK_INGESTION_CLUSTER_ARN @@ -75,6 +76,11 @@ FLAGS --message-transforms-file=MESSAGE_TRANSFORMS_FILE Path to YAML or JSON file containing message transforms. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. Example: + 123/environment=production,123/costCenter=marketing + Following flags are for specifying the data source settings for an import topic diff --git a/gcloud/beta/run/compose/help b/gcloud/beta/run/compose/help new file mode 100644 index 000000000..9e513d2a3 --- /dev/null +++ b/gcloud/beta/run/compose/help @@ -0,0 +1,26 @@ +NAME + gcloud beta run compose - support Docker Compose workflows on Cloud Run + +SYNOPSIS + gcloud beta run compose COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command group provides tools for Docker Compose developers to + deploy services to Cloud Run using compose.yaml as the input source. + +EXAMPLES + To bring up a Docker Compose service on Cloud Run, run: + + $ gcloud beta run compose up compose.yaml + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run compose + diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index dae51b474..7ffe32aab 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -733,13 +733,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. + Clears all existing network tags from the Cloud Run service. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + service. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/beta/run/help b/gcloud/beta/run/help index 1241b2fa5..69630ff93 100644 --- a/gcloud/beta/run/help +++ b/gcloud/beta/run/help @@ -23,6 +23,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + compose + (BETA) Support Docker Compose workflows on Cloud Run. + domain-mappings (BETA) View and manage your Cloud Run domain mappings. diff --git a/gcloud/beta/run/jobs/create b/gcloud/beta/run/jobs/create index 68ae6ae08..36397ee5c 100644 --- a/gcloud/beta/run/jobs/create +++ b/gcloud/beta/run/jobs/create @@ -347,8 +347,8 @@ FLAGS network settings, use --clear-network. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the Cloud - Run job. To clear existing tags, use --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + job. To clear existing tags, use --clear-network-tags. --subnet=SUBNET The VPC subnetwork that the Cloud Run job will get IPs from. The diff --git a/gcloud/beta/run/jobs/deploy b/gcloud/beta/run/jobs/deploy index 6dcdb7149..f6ca17e73 100644 --- a/gcloud/beta/run/jobs/deploy +++ b/gcloud/beta/run/jobs/deploy @@ -387,11 +387,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run job. + Clears all existing network tags from the Cloud Run job. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run job. To clear existing tags, use --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + job. To clear existing tags, use --clear-network-tags. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/jobs/update b/gcloud/beta/run/jobs/update index 51e100d90..eedde27d2 100644 --- a/gcloud/beta/run/jobs/update +++ b/gcloud/beta/run/jobs/update @@ -420,11 +420,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run job. + Clears all existing network tags from the Cloud Run job. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run job. To clear existing tags, use --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + job. To clear existing tags, use --clear-network-tags. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/run/multi-region-services/update b/gcloud/beta/run/multi-region-services/update index 2911898af..170e600da 100644 --- a/gcloud/beta/run/multi-region-services/update +++ b/gcloud/beta/run/multi-region-services/update @@ -581,13 +581,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. + Clears all existing network tags from the Cloud Run service. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + service. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 051a568cd..31c5be17b 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -607,13 +607,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. + Clears all existing network tags from the Cloud Run service. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + service. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/beta/run/worker-pools/deploy b/gcloud/beta/run/worker-pools/deploy index da153caa7..18f230d7c 100644 --- a/gcloud/beta/run/worker-pools/deploy +++ b/gcloud/beta/run/worker-pools/deploy @@ -438,13 +438,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - worker. + Clears all existing network tags from the Cloud Run worker. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run worker. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + worker. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/beta/run/worker-pools/update b/gcloud/beta/run/worker-pools/update index 760229485..91be80c27 100644 --- a/gcloud/beta/run/worker-pools/update +++ b/gcloud/beta/run/worker-pools/update @@ -416,13 +416,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - worker. + Clears all existing network tags from the Cloud Run worker. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run worker. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + worker. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/beta/service-extensions/lb-edge-extensions/delete b/gcloud/beta/service-extensions/lb-edge-extensions/delete index 70db4a122..02f02404f 100644 --- a/gcloud/beta/service-extensions/lb-edge-extensions/delete +++ b/gcloud/beta/service-extensions/lb-edge-extensions/delete @@ -66,5 +66,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud service-extensions lb-edge-extensions delete diff --git a/gcloud/beta/service-extensions/lb-edge-extensions/describe b/gcloud/beta/service-extensions/lb-edge-extensions/describe index b2e949630..45f9b42f4 100644 --- a/gcloud/beta/service-extensions/lb-edge-extensions/describe +++ b/gcloud/beta/service-extensions/lb-edge-extensions/describe @@ -61,5 +61,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud service-extensions lb-edge-extensions describe diff --git a/gcloud/beta/service-extensions/lb-edge-extensions/help b/gcloud/beta/service-extensions/lb-edge-extensions/help index a891a7662..64ee2834b 100644 --- a/gcloud/beta/service-extensions/lb-edge-extensions/help +++ b/gcloud/beta/service-extensions/lb-edge-extensions/help @@ -30,5 +30,8 @@ COMMANDS (BETA) List LbEdgeExtension resources. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud service-extensions lb-edge-extensions diff --git a/gcloud/beta/service-extensions/lb-edge-extensions/import b/gcloud/beta/service-extensions/lb-edge-extensions/import index ebaf5f3de..7a4e440c5 100644 --- a/gcloud/beta/service-extensions/lb-edge-extensions/import +++ b/gcloud/beta/service-extensions/lb-edge-extensions/import @@ -78,5 +78,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud service-extensions lb-edge-extensions import diff --git a/gcloud/beta/service-extensions/lb-edge-extensions/list b/gcloud/beta/service-extensions/lb-edge-extensions/list index 5e8f6b17f..7d1a0e28d 100644 --- a/gcloud/beta/service-extensions/lb-edge-extensions/list +++ b/gcloud/beta/service-extensions/lb-edge-extensions/list @@ -81,5 +81,8 @@ API REFERENCE for this API can be found at: https://cloud.google.com/networking NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud service-extensions lb-edge-extensions list diff --git a/gcloud/beta/services/disable b/gcloud/beta/services/disable index 35617e3b6..15685705f 100644 --- a/gcloud/beta/services/disable +++ b/gcloud/beta/services/disable @@ -1,10 +1,13 @@ NAME gcloud beta services disable - disable a service for consumption for a - project + project, folder or organization SYNOPSIS - gcloud beta services disable [SERVICE ...] [--async] [--force] - [GCLOUD_WIDE_FLAG ...] + gcloud beta services disable [SERVICE ...] [--async] + [--bypass-api-usage-check] [--force] [--validate-only] + [--bypass-dependency-service-check | --disable-dependency-services] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command disables one or more previously-enabled services for @@ -19,11 +22,28 @@ DESCRIPTION a service at: https://cloud.google.com/service-usage/docs/enable-disable EXAMPLES - To disable a service called my-consumed-service for the active project, + To disable a service called my-consumed-service for the current project, run: $ gcloud beta services disable my-consumed-service + To disable a service called my-consumed-service for the project my-project, + run: + + $ gcloud beta services disable my-consumed-service \ + --project=my-project + + To disable a service called my-consumed-service for the folder my-folder, + run: + + $ gcloud beta services disable my-consumed-service --folder=my-folder + + To disable a service called my-consumed-service for the organization + my-organization, run: + + $ gcloud beta services disable my-consumed-service \ + --organization=my-organization + To run the same command asynchronously (non-blocking), run: $ gcloud beta services disable my-consumed-service --async @@ -37,12 +57,54 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --bypass-api-usage-check + If specified, the system will bypass usage checks for services that are + being removed. Otherwise, the system will check if the service to be + removed was used in the last 30 days or enabled in the last 3 days. If + so, the system will return an error. + --force If specified, the disable call will proceed even if there are enabled - services which depend on the service to be disabled or disable the - service used in last 30 days or was enabled in recent 3 days. Forcing - the call means that the services which depend on the service to be - disabled will also be disabled. + services which depend on the service to be disabled, or the service to + be disabled was used in the last 30 days, or the service to be disabled + was enabled in the last 3 days. Forcing the call means that the + services which depend on the service to be disabled will also be + disabled. (Note): If --bypass-api-usage-check, + --bypass-dependency-service-check, or --disable-dependency-services + flags are used, they will take precedence over --force. + + --validate-only + Validate the disable action, but don't actually perform it + + At most one of these can be specified: + + --bypass-dependency-service-check + If specified, the disable call will bypass the check for dependencies + and the dependencies will remain enabled. + + --disable-dependency-services + If specified, the disable call will proceed disabling the service and + all the enabled services depend on the service to be disabled + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/services/enable b/gcloud/beta/services/enable index 9ffa3d76b..94a21aa28 100644 --- a/gcloud/beta/services/enable +++ b/gcloud/beta/services/enable @@ -1,12 +1,16 @@ NAME gcloud beta services enable - enables a service for consumption for a - project + project, folder or organization SYNOPSIS - gcloud beta services enable [SERVICE ...] [--async] [GCLOUD_WIDE_FLAG ...] + gcloud beta services enable [SERVICE ...] [--async] [--skip-dependency] + [--validate-only] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command enables a service for consumption for a project. + (BETA) This command enables a service for consumption for a project, folder + or organization. To see a list of available services for a project, run: @@ -21,6 +25,23 @@ EXAMPLES $ gcloud beta services enable my-consumed-service + To enable a service called my-consumed-service on the project my-project, + run: + + $ gcloud beta services enable my-consumed-service \ + --project=my-project + + To enable a service called my-consumed-service on the folder my-folder, + run: + + $ gcloud beta services enable my-consumed-service --folder=my-folder + + To enable a service called my-consumed-service on the organization + my-organization, run: + + $ gcloud beta services enable my-consumed-service \ + --organization=my-organization + To run the same command asynchronously (non-blocking), run: $ gcloud beta services enable my-consumed-service --async @@ -39,6 +60,33 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --skip-dependency + If set, the dependencies of the service to be enabled will not be + enabled. + + --validate-only + Validate the enable action, but don't actually perform it + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/services/groups/help b/gcloud/beta/services/groups/help index d80d6ed54..9b7fddb2d 100644 --- a/gcloud/beta/services/groups/help +++ b/gcloud/beta/services/groups/help @@ -12,6 +12,15 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +COMMANDS + COMMAND is one of the following: + + list-expanded-members + (BETA) List expanded members of a specific service and group. + + list-members + (BETA) List members of a specific service and group. + NOTES This command is currently in beta and might change without notice. This variant is also available: diff --git a/gcloud/beta/services/groups/list-expanded-members b/gcloud/beta/services/groups/list-expanded-members new file mode 100644 index 000000000..bcf8eb393 --- /dev/null +++ b/gcloud/beta/services/groups/list-expanded-members @@ -0,0 +1,93 @@ +NAME + gcloud beta services groups list-expanded-members - list expanded members + of a specific service and group + +SYNOPSIS + gcloud beta services groups list-expanded-members SERVICE GROUP + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE; default=50] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List expanded members of a specific service and group. + +EXAMPLES + List expanded members of service my-service and group my-group: + + $ gcloud beta services groups list-expanded-members my-service \ + my-group + + List expanded members of service my-service and group my-group for a + specific project '12345678': + + $ gcloud beta services groups list-expanded-members my-service \ + my-group --project=12345678 + +POSITIONAL ARGUMENTS + SERVICE + Name of the service. + + GROUP + Service group name, for example "dependencies". + +FLAGS + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE; default=50 + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is 50. + 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. This + variant is also available: + + $ gcloud alpha services groups list-expanded-members + diff --git a/gcloud/beta/services/groups/list-members b/gcloud/beta/services/groups/list-members new file mode 100644 index 000000000..46e96865d --- /dev/null +++ b/gcloud/beta/services/groups/list-members @@ -0,0 +1,92 @@ +NAME + gcloud beta services groups list-members - list members of a specific + service and group + +SYNOPSIS + gcloud beta services groups list-members SERVICE GROUP + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE; default=50] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List members of a specific service and group. + +EXAMPLES + List members of service my-service and group my-group: + + $ gcloud beta services groups list-members my-service my-group + + List members of service my-service and group my-group for a specific + project '12345678': + + $ gcloud beta services groups list-members my-service my-group \ + --project=12345678 + +POSITIONAL ARGUMENTS + SERVICE + Name of the service. + + GROUP + Service group name, for example "dependencies". + +FLAGS + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE; default=50 + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is 50. + 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. This + variant is also available: + + $ gcloud alpha services groups list-members + diff --git a/gcloud/beta/services/help b/gcloud/beta/services/help index ceb749104..f8347660b 100644 --- a/gcloud/beta/services/help +++ b/gcloud/beta/services/help @@ -38,6 +38,9 @@ GROUPS identity (BETA) Manage service identity. + mcp + (BETA) List, enable and disable MCP endpoints. + operations (BETA) Manage Operation for various services. @@ -54,13 +57,15 @@ COMMANDS COMMAND is one of the following: disable - (BETA) Disable a service for consumption for a project. + (BETA) Disable a service for consumption for a project, folder or + organization. enable - (BETA) Enables a service for consumption for a project. + (BETA) Enables a service for consumption for a project, folder or + organization. list - (BETA) List services for a project. + (BETA) List services for a project, folder or organization. NOTES This command is currently in beta and might change without notice. These diff --git a/gcloud/beta/services/list b/gcloud/beta/services/list index 892937665..1036ae9eb 100644 --- a/gcloud/beta/services/list +++ b/gcloud/beta/services/list @@ -1,47 +1,61 @@ NAME - gcloud beta services list - list services for a project + gcloud beta services list - list services for a project, folder or + organization SYNOPSIS - gcloud beta services list [--available | --enabled] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE; default=200] - [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + gcloud beta services list [--available | --enabled] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE; default=1000] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command lists the services that are enabled or available to be - enabled by a project. You can choose the mode in which the command will - list services by using exactly one of the --enabled or --available flags. - --enabled is the default. + enabled by a project, folder or organization. Service enablement and + availability can be inherited from resource ancestors. A resource's enabled + services include services that are enabled on the resource itself and + enabled on all resource ancestors. services by using exactly one of the + --enabled or --available flags. --enabled is the default. EXAMPLES - To list the services for the current project has enabled for consumption, - run: + To list the services the current project has enabled for consumption, run: $ gcloud beta services list --enabled - To list the services for the current project can enable for consumption, - run: + To list the services the current project can enable for consumption, run: $ gcloud beta services list --available - To list the services for project my-project has enabled for consumption, - run: - - $ gcloud beta services list --enabled --project=my-project - - To list the services the project my-project can enable for consumption, - run: - - $ gcloud beta services list --available --project=my-project - FLAGS At most one of these can be specified: --available - Return the services available to the project to enable. This list - will include any services that the project has already enabled. + Return the services available to the project, folder or organization + to enable. --enabled - (DEFAULT) Return the services which the project has enabled. + (DEFAULT) Return the services which the project, folder or + organization has enabled. + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. LIST COMMAND FLAGS --filter=EXPRESSION @@ -56,11 +70,11 @@ LIST COMMAND FLAGS flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - --page-size=PAGE_SIZE; default=200 + --page-size=PAGE_SIZE; default=1000 Some services group resource list output into pages. This flag - specifies the maximum number of resources per page. The default is 200. - Paging may be applied before or after --filter and --limit depending on - the service. + specifies the maximum number of resources per page. The default is + 1000. 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 diff --git a/gcloud/beta/services/mcp/content-security/add b/gcloud/beta/services/mcp/content-security/add new file mode 100644 index 000000000..3cc5e0782 --- /dev/null +++ b/gcloud/beta/services/mcp/content-security/add @@ -0,0 +1,40 @@ +NAME + gcloud beta services mcp content-security add - add MCP content security + provider of a project + +SYNOPSIS + gcloud beta services mcp content-security add MCP_CONTENT_SECURITY_PROVIDER + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Add MCP content security provider of a project. + +EXAMPLES + Add MCP content security provider of a project: + + $ gcloud beta services mcp content-security add \ + my-mcp-content-security-provider + + Add MCP content security provider of a project my-project: + + $ gcloud beta services mcp content-security add \ + my-mcp-content-security-provider --project=my-project + +POSITIONAL ARGUMENTS + MCP_CONTENT_SECURITY_PROVIDER + The MCP content security provider to add. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp content-security add + diff --git a/gcloud/beta/services/mcp/content-security/get b/gcloud/beta/services/mcp/content-security/get new file mode 100644 index 000000000..77f9afa23 --- /dev/null +++ b/gcloud/beta/services/mcp/content-security/get @@ -0,0 +1,33 @@ +NAME + gcloud beta services mcp content-security get - get MCP content security + providers for a project + +SYNOPSIS + gcloud beta services mcp content-security get [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get MCP content security providers for a project. + +EXAMPLES + Get MCP content security providers for a project: + + $ gcloud beta services mcp content-security get + + Get MCP content security providers for a project my-project: + + $ gcloud beta services mcp content-security get --project=my-project + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp content-security get + diff --git a/gcloud/beta/services/mcp/content-security/help b/gcloud/beta/services/mcp/content-security/help new file mode 100644 index 000000000..8f79a2872 --- /dev/null +++ b/gcloud/beta/services/mcp/content-security/help @@ -0,0 +1,33 @@ +NAME + gcloud beta services mcp content-security - get/add/remove MCP content + security + +SYNOPSIS + gcloud beta services mcp content-security COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get/add/remove MCP content security. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add + (BETA) Add MCP content security provider of a project. + + get + (BETA) Get MCP content security providers for a project. + + remove + (BETA) Remove MCP content security provider of a project. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp content-security + diff --git a/gcloud/beta/services/mcp/content-security/remove b/gcloud/beta/services/mcp/content-security/remove new file mode 100644 index 000000000..eec8566d3 --- /dev/null +++ b/gcloud/beta/services/mcp/content-security/remove @@ -0,0 +1,40 @@ +NAME + gcloud beta services mcp content-security remove - remove MCP content + security provider of a project + +SYNOPSIS + gcloud beta services mcp content-security remove + MCP_CONTENT_SECURITY_PROVIDER [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Remove MCP content security provider of a project. + +EXAMPLES + Remove MCP content security provider of a project: + + $ gcloud beta services mcp content-security remove \ + my-mcp-content-security-provider + + Remove MCP content security provider of a project my-project: + + $ gcloud beta services mcp content-security remove \ + my-mcp-content-security-provider --project=my-project + +POSITIONAL ARGUMENTS + MCP_CONTENT_SECURITY_PROVIDER + The MCP content security provider to remove. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp content-security remove + diff --git a/gcloud/beta/services/mcp/disable b/gcloud/beta/services/mcp/disable new file mode 100644 index 000000000..f368ac286 --- /dev/null +++ b/gcloud/beta/services/mcp/disable @@ -0,0 +1,80 @@ +NAME + gcloud beta services mcp disable - disable a service for MCP on a project, + folder or organization + +SYNOPSIS + gcloud beta services mcp disable SERVICE [--async] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Disable a service for MCP on a project, folder or organization + +EXAMPLES + To disable a service for MCP called my-service on the current project, run: + + $ gcloud beta services mcp disable my-service + + To disable a service for MCP called my-service on the project my-project, + run: + + $ gcloud beta services mcp disable my-service --project=my-project + + To disable a service for MCP called my-service on the folder my-folder, + run: + + $ gcloud beta services mcp disable my-service --folder=my-folder + + To disable a service for MCP called my-service on the organization + my-organization, run: + + $ gcloud beta services mcp disable my-service \ + --organization=my-organization + + To run the same command asynchronously (non-blocking), run: + + $ gcloud beta services mcp disable my-service --async + +POSITIONAL ARGUMENTS + SERVICE + The name of the service to disable MCP. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp disable + diff --git a/gcloud/beta/services/mcp/enable b/gcloud/beta/services/mcp/enable new file mode 100644 index 000000000..d3ec2e84a --- /dev/null +++ b/gcloud/beta/services/mcp/enable @@ -0,0 +1,84 @@ +NAME + gcloud beta services mcp enable - enable a service for MCP on a project, + folder or organization + +SYNOPSIS + gcloud beta services mcp enable SERVICE [--async] + [--skip-mcp-endpoint-check] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Enable a service for MCP on a project, folder or organization + +EXAMPLES + To enable a service for MCP called my-service on the current project, run: + + $ gcloud beta services mcp enable my-service + + To enable a service for MCP called my-service on the project my-project, + run: + + $ gcloud beta services mcp enable my-service --project=my-project + + To enable a service for MCP called my-service on the folder my-folder, run: + + $ gcloud beta services mcp enable my-service --folder=my-folder + + To enable a service for MCP called my-service on the organization + my-organization, run: + + $ gcloud beta services mcp enable my-service \ + --organization=my-organization + + To run the same command asynchronously (non-blocking), run: + + $ gcloud beta services mcp enable my-service --async + +POSITIONAL ARGUMENTS + SERVICE + The name of the service to enable MCP. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --skip-mcp-endpoint-check + If true, the system will bypass the check for MCP endpoint while + enabling a service. + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp enable + diff --git a/gcloud/beta/services/mcp/help b/gcloud/beta/services/mcp/help new file mode 100644 index 000000000..d43fa8518 --- /dev/null +++ b/gcloud/beta/services/mcp/help @@ -0,0 +1,38 @@ +NAME + gcloud beta services mcp - list, enable and disable MCP endpoints + +SYNOPSIS + gcloud beta services mcp GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List, enable and disable MCP endpoints. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + content-security + (BETA) Get/add/remove MCP content security. + +COMMANDS + COMMAND is one of the following: + + disable + (BETA) Disable a service for MCP on a project, folder or organization. + + enable + (BETA) Enable a service for MCP on a project, folder or organization. + + list + (BETA) List MCP services for a project, folder or organization. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services mcp + diff --git a/gcloud/beta/services/mcp/list b/gcloud/beta/services/mcp/list new file mode 100644 index 000000000..322d22b10 --- /dev/null +++ b/gcloud/beta/services/mcp/list @@ -0,0 +1,95 @@ +NAME + gcloud beta services mcp list - list MCP services for a project, folder or + organization + +SYNOPSIS + gcloud beta services mcp list [--available | --enabled] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE; default=1000] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command lists the MCP services that are enabled or available + (with MCP endpoints) to be MCP enabled by a project, folder or + organization. + +EXAMPLES + To list the services the current project has enabled for MCP, run: + + $ gcloud beta services mcp list --enabled + + To list the services the current project can enable for MCP, run: + + $ gcloud beta services mcp list --available + +FLAGS + At most one of these can be specified: + + --available + Return the services available to the project, folder or organization + to enable for MCP. + + --enabled + (DEFAULT) Return the MCP services which the project, folder or + organization has enabled. + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE; default=1000 + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + 1000. 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. This + variant is also available: + + $ gcloud alpha services mcp list + diff --git a/gcloud/beta/services/policies/get b/gcloud/beta/services/policies/get new file mode 100644 index 000000000..3297e70cc --- /dev/null +++ b/gcloud/beta/services/policies/get @@ -0,0 +1,68 @@ +NAME + gcloud beta services policies get - get consumer policy for a project, + folder or organization + +SYNOPSIS + gcloud beta services policies get [--output-file=OUTPUT_FILE] + [--policy-name=POLICY_NAME; default="default"] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get consumer policy for a project, folder or organization. + +EXAMPLES + Get consumer policy for default policy on current project: + + $ gcloud beta services policies get OR $ gcloud beta services \ + policies get --policy-name=default + + Get consumer policy for default policy on current project and save the + content in an output file: + + $ gcloud beta services policies get \ + --output-file=/path/to/the/file.yaml OR $ gcloud beta services \ + policies get --output-file=/path/to/the/file.json + +FLAGS + --output-file=OUTPUT_FILE + Path to the file to write policy contents to. Supported format:.yaml or + .json. + + --policy-name=POLICY_NAME; default="default" + Name of the consumer policy. Currently only "default" is supported. + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services policies get + diff --git a/gcloud/beta/services/policies/get-effective b/gcloud/beta/services/policies/get-effective new file mode 100644 index 000000000..40709d5d2 --- /dev/null +++ b/gcloud/beta/services/policies/get-effective @@ -0,0 +1,61 @@ +NAME + gcloud beta services policies get-effective - get effective policy for a + project, folder or organization + +SYNOPSIS + gcloud beta services policies get-effective [--view=VIEW; default="BASIC"] + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get effective policy for a project, folder or organization. + +EXAMPLES + Get effective policy for the current project: + + $ gcloud beta services policies get-effective + + Get effective policy for project my-project: + + $ gcloud beta services policies get-effective --project=my-project + +FLAGS + --view=VIEW; default="BASIC" + The view of the effective policy. BASIC includes basic metadata about + the effective policy. FULL includes every information related to + effective policy. VIEW must be one of: BASIC, FULL. + + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services policies get-effective + diff --git a/gcloud/beta/services/policies/help b/gcloud/beta/services/policies/help index b5f08e20d..42b1d7395 100644 --- a/gcloud/beta/services/policies/help +++ b/gcloud/beta/services/policies/help @@ -13,6 +13,22 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +COMMANDS + COMMAND is one of the following: + + get + (BETA) Get consumer policy for a project, folder or organization. + + get-effective + (BETA) Get effective policy for a project, folder or organization. + + test-enabled + (BETA) Test a value against the result of merging consumer policies in + the resource hierarchy. + + update + (BETA) Update consumer policy for a project, folder or organization. + NOTES This command is currently in beta and might change without notice. This variant is also available: diff --git a/gcloud/beta/services/policies/test-enabled b/gcloud/beta/services/policies/test-enabled new file mode 100644 index 000000000..0f3cbe1ce --- /dev/null +++ b/gcloud/beta/services/policies/test-enabled @@ -0,0 +1,62 @@ +NAME + gcloud beta services policies test-enabled - test a value against the + result of merging consumer policies in the resource hierarchy + +SYNOPSIS + gcloud beta services policies test-enabled SERVICE + [--folder=FOLDER_ID | --organization=ORGANIZATION_ID + | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Test a value against the result of merging consumer policies in the + resource hierarchy. + +EXAMPLES + Test for service my-service for current project: + + $ gcloud beta services policies test-enabled my-service + + Test for service my-service for project my-project: + + $ gcloud beta services policies test-enabled my-service \ + --project=my-project + +POSITIONAL ARGUMENTS + SERVICE + Name of the service. + +FLAGS + At most one of these can be specified: + + --folder=FOLDER_ID + The Google Cloud Platform folder ID to use for this invocation. + + --organization=ORGANIZATION_ID + The Google Cloud Platform organization ID to use for this invocation. + + --project=PROJECT_ID + The Google Cloud project ID to use for this invocation. If omitted, + then the current project is assumed; the current project can be + listed using gcloud config list --format='text(core.project)' and can + be set using gcloud config set project PROJECTID. + + --project and its fallback core/project property play two roles in + the invocation. It specifies the project of the resource to operate + on. It also specifies the project for API enablement check, quota, + and billing. To specify a different project for quota and billing, + use --billing-project or billing/quota_project property. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services policies test-enabled + diff --git a/gcloud/beta/services/policies/update b/gcloud/beta/services/policies/update new file mode 100644 index 000000000..3a55acfdb --- /dev/null +++ b/gcloud/beta/services/policies/update @@ -0,0 +1,72 @@ +NAME + gcloud beta services policies update - update consumer policy for a + project, folder or organization + +SYNOPSIS + gcloud beta services policies update + --consumer-policy-file=CONSUMER_POLICY_FILE [--bypass-api-usage-check] + [--bypass-dependency-check] [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update consumer policy for a project, folder or organization. + +EXAMPLES + Update consumer policy + + $ gcloud beta services policies update \ + --consumer-policy-file=/path/to/the/file.yaml + + Validate the update action on the policy: + + $ gcloud beta services policies update \ + --consumer-policy-file=/path/to/the/file.yaml --validate-only + + Update consumer policy and bypass dependency check: + + $ gcloud beta services policies update \ + --consumer-policy-file=/path/to/the/file.yaml \ + --bypass-dependency-check + + Update consumer policy and bypass api usage check: + + $ gcloud beta services policies update \ + --consumer-policy-file=/path/to/the/file.yaml \ + --bypass-api-usage-check + +REQUIRED FLAGS + --consumer-policy-file=CONSUMER_POLICY_FILE + Path to the file that contains the consumer policy in the YAML format. + +OPTIONAL FLAGS + --bypass-api-usage-check + If true, the system will bypass usage checks for services that are + being removed. If false, the system will check if the service to be + removed was used in the last 30 days or enabled in the last 3 days. If + so, an error will be returned. + + --bypass-dependency-check + This flag controls dependency management within the consumer policy. If + false, dependencies are enforced. When adding a new service, it + verifies that all the services dependencies are already present in the + policy. When removing a service, the system will ensure that no other + services in the policy depend on it. If the policy lacks any required + dependencies, the update will not succeed, and an error will be + returned. + + --validate-only + Validate the to update action, but don't actually perform it + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha services policies update + diff --git a/gcloud/beta/sql/backups/restore b/gcloud/beta/sql/backups/restore index d51e79e68..d68631ee3 100644 --- a/gcloud/beta/sql/backups/restore +++ b/gcloud/beta/sql/backups/restore @@ -374,8 +374,8 @@ OPTIONAL FLAGS here: https://cloud.google.com/sql/docs/quotas#storage_limits --storage-type=STORAGE_TYPE - The storage type for the instance. The default is SSD. STORAGE_TYPE - must be one of: SSD, HDD, HYPERDISK_BALANCED. + The storage type for the instance, determined by the selected machine + type. STORAGE_TYPE must be one of: SSD, HDD, HYPERDISK_BALANCED. --tier=TIER, -t TIER Machine type for a shared-core instance e.g. db-g1-small. For all other diff --git a/gcloud/beta/sql/connect b/gcloud/beta/sql/connect index 445ef047e..fbe03bc88 100644 --- a/gcloud/beta/sql/connect +++ b/gcloud/beta/sql/connect @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud beta sql connect INSTANCE [--database=DATABASE, -d DATABASE] - [--port=PORT; default=9470] [--user=USER, -u USER] - [GCLOUD_WIDE_FLAG ...] + [--debug-logs] [--port=PORT; default=9470] [--run-connection-test] + [--skip-ssl] [--auto-iam-authn | --user=USER, -u USER] + [--auto-ip | --private-ip | --psc] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Connects to a Cloud SQL instance. @@ -22,12 +23,42 @@ FLAGS --database=DATABASE, -d DATABASE The PostgreSQL or SQL Server database to connect to. + --debug-logs + Enable verbose debug logs for Cloud SQL Proxy. + --port=PORT; default=9470 Port number that gcloud will use to connect to the Cloud SQL Proxy through localhost. - --user=USER, -u USER - Cloud SQL instance user to connect as. + --run-connection-test + Run connection test for Cloud SQL Proxy. + + --skip-ssl + Skip SSL certificate verification for MySQL instances. + + User selection settings for Cloud SQL Proxy connection. + + At most one of these can be specified: + + --auto-iam-authn + Enables IAM database authentication for connections to MySQL and + Postgres instances. + + --user=USER, -u USER + Cloud SQL instance user to connect as. + + IP address selection settings for Cloud SQL Proxy connection. + + At most one of these can be specified: + + --auto-ip + Connect to the Cloud SQL instance with auto IP detection. + + --private-ip + Connect to the Cloud SQL instance using private IP. + + --psc + Connect to the Cloud SQL instance using Private Service Connect. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/sql/import/bak b/gcloud/beta/sql/import/bak index 6bca2879b..d2565664d 100644 --- a/gcloud/beta/sql/import/bak +++ b/gcloud/beta/sql/import/bak @@ -60,7 +60,7 @@ OPTIONAL FLAGS Whether or not to decrypt the imported encrypted BAK file. --no-recovery - Whether or not the SQL Server import is execueted with NORECOVERY + Whether or not the SQL Server import is executed with NORECOVERY keyword. --recovery-only diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index 033027c35..8eb1dc132 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -21,6 +21,7 @@ SYNOPSIS [--connection-pool-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] [--custom-subject-alternative-names=DNS,[DNS,[DNS]]] + [--data-api-access=DATA_API_ACCESS] [--database-flags=FLAG=VALUE,[FLAG=VALUE,...]] [--database-version=DATABASE_VERSION; default="MYSQL_8_0"] [--[no-]deletion-protection] @@ -267,6 +268,19 @@ FLAGS update an instance, you can add a comma-separated list of up to three DNS names to the server certificate of your instance. + --data-api-access=DATA_API_ACCESS + Controls connectivity to the instance using ExecuteSql API. + DATA_API_ACCESS must be one of: + + ALLOW_DATA_API + Allow using ExecuteSql API to connect to the instance. For Private + IP instances, this will allow authorized users to access the + instance from the public internet using ExecuteSql API. + DATA_API_ACCESS_UNSPECIFIED + Unspecified mode, effectively the same as DISALLOW_DATA_API. + DISALLOW_DATA_API + Disallow using ExecuteSql API to connect to the instance. + --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an equals sign to separate flag name and value. Flags without values, like @@ -620,8 +634,8 @@ FLAGS here: https://cloud.google.com/sql/docs/quotas#storage_limits --storage-type=STORAGE_TYPE - The storage type for the instance. The default is SSD. STORAGE_TYPE - must be one of: SSD, HDD, HYPERDISK_BALANCED. + The storage type for the instance, determined by the selected machine + type. STORAGE_TYPE must be one of: SSD, HDD, HYPERDISK_BALANCED. --tags=TAG=VALUE,[TAG=VALUE,...] Comma-separated list of tags to set on the instance. Use an equals diff --git a/gcloud/beta/sql/instances/help b/gcloud/beta/sql/instances/help index 0cbe80884..744218a61 100644 --- a/gcloud/beta/sql/instances/help +++ b/gcloud/beta/sql/instances/help @@ -54,7 +54,7 @@ COMMANDS point-in-time-restore (BETA) Performs a point in time restore for a Cloud SQL instance - managed by Google Cloud Backup and Disaster Recovery. + managed by Google Cloud Backup and Disaster Recovery (DR) Service. promote-replica (BETA) Promotes Cloud SQL read replica to a stand-alone instance. diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index fdc88c4d9..c822b6364 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -18,6 +18,7 @@ SYNOPSIS [--clear-active-directory-dns-servers] [--clear-failover-dr-replica-name] [--clear-password-policy] [--connector-enforcement=CONNECTOR_ENFORCEMENT] [--cpu=CPU] + [--data-api-access=DATA_API_ACCESS] [--database-version=DATABASE_VERSION] [--[no-]deletion-protection] [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] @@ -64,7 +65,7 @@ SYNOPSIS [--storage-auto-increase-limit=STORAGE_AUTO_INCREASE_LIMIT] [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] [--storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT] - [--storage-size=STORAGE_SIZE] + [--storage-size=STORAGE_SIZE] [--storage-type=STORAGE_TYPE] [--switch-transaction-logs-to-cloud-storage] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] [--time-zone=TIME_ZONE] [--update-labels=[KEY=VALUE,...]] @@ -212,6 +213,19 @@ FLAGS should not be used when creating an Enterprise Plus edition, as the machine configuration is determined by the --tier flag instead. + --data-api-access=DATA_API_ACCESS + Controls connectivity to the instance using ExecuteSql API. + DATA_API_ACCESS must be one of: + + ALLOW_DATA_API + Allow using ExecuteSql API to connect to the instance. For Private + IP instances, this will allow authorized users to access the + instance from the public internet using ExecuteSql API. + DATA_API_ACCESS_UNSPECIFIED + Unspecified mode, effectively the same as DISALLOW_DATA_API. + DISALLOW_DATA_API + Disallow using ExecuteSql API to connect to the instance. + --database-version=DATABASE_VERSION The database engine type and versions. If left unspecified, no changes occur. See the list of database versions at @@ -551,6 +565,10 @@ FLAGS of GB. The default is 10GB. Information on storage limits can be found here: https://cloud.google.com/sql/docs/quotas#storage_limits + --storage-type=STORAGE_TYPE + The storage type for the instance, determined by the selected machine + type. STORAGE_TYPE must be one of: SSD, HDD, HYPERDISK_BALANCED. + --switch-transaction-logs-to-cloud-storage Switches the location of the transaction logs used for PITR from disk to Cloud Storage. diff --git a/gcloud/beta/sql/instances/point-in-time-restore b/gcloud/beta/sql/instances/point-in-time-restore index 909db94bf..3450c9bdf 100644 --- a/gcloud/beta/sql/instances/point-in-time-restore +++ b/gcloud/beta/sql/instances/point-in-time-restore @@ -1,7 +1,7 @@ NAME gcloud beta sql instances point-in-time-restore - performs a point in time restore for a Cloud SQL instance managed by Google Cloud Backup and - Disaster Recovery + Disaster Recovery Service SYNOPSIS gcloud beta sql instances point-in-time-restore DATASOURCE TARGET @@ -14,7 +14,7 @@ SYNOPSIS DESCRIPTION (BETA) gcloud beta sql instances point-in-time-restore performs a point in time restore for a Cloud SQL instance managed by Google Cloud Backup and - Disaster Recovery. + Disaster Recovery (DR) Service. EXAMPLES To perform a point in time restore from an earlier point in time: @@ -24,8 +24,8 @@ EXAMPLES POSITIONAL ARGUMENTS DATASOURCE - The Google Cloud Backup and Disaster Recovery Datasource URI, of the - form projects/{project}/locations/{region}/backupVaults/ + The Google Cloud Backup and Disaster Recovery (DR) Service Datasource + URI, of the form projects/{project}/locations/{region}/backupVaults/ {backupvault}/dataSources/{datasource}. TARGET @@ -75,8 +75,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 sql instances point-in-time-restore $ gcloud alpha sql instances point-in-time-restore diff --git a/gcloud/beta/workstations/configs/create b/gcloud/beta/workstations/configs/create index c01100621..6bdf5b845 100644 --- a/gcloud/beta/workstations/configs/create +++ b/gcloud/beta/workstations/configs/create @@ -30,7 +30,8 @@ SYNOPSIS [--service-account=SERVICE_ACCOUNT] [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--vm-tags=[VM_TAGS,...]] + [--shielded-vtpm] [--startup-script-uri=STARTUP_SCRIPT_URI] + [--vm-tags=[VM_TAGS,...]] [--accelerator-count=ACCELERATOR_COUNT : --accelerator-type=ACCELERATOR_TYPE] [--container-custom-image=CONTAINER_CUSTOM_IMAGE @@ -429,6 +430,15 @@ FLAGS --shielded-vtpm Default value is false. If set, instances will have vTPM enabled. + --startup-script-uri=STARTUP_SCRIPT_URI + Link to the startup script stored in Cloud Storage. The script is + executed on the workstation VM after it is booted. + + Example: + + $ gcloud beta workstations configs create \ + --startup-script-uri gs://{bucket-name}/{object-name} + --vm-tags=[VM_TAGS,...] Resource manager tags to be bound to the instance. Tag keys and values have the same definition as diff --git a/gcloud/beta/workstations/configs/update b/gcloud/beta/workstations/configs/update index c84c48b6c..15f65f5d5 100644 --- a/gcloud/beta/workstations/configs/update +++ b/gcloud/beta/workstations/configs/update @@ -23,7 +23,8 @@ SYNOPSIS [--running-timeout=RUNNING_TIMEOUT] [--service-account=SERVICE_ACCOUNT] [--service-account-scopes=[SERVICE_ACCOUNT_SCOPES,...]] [--shielded-integrity-monitoring] [--shielded-secure-boot] - [--shielded-vtpm] [--vm-tags=[VM_TAGS,...]] + [--shielded-vtpm] [--startup-script-uri=STARTUP_SCRIPT_URI] + [--vm-tags=[VM_TAGS,...]] [--accelerator-count=ACCELERATOR_COUNT : --accelerator-type=ACCELERATOR_TYPE] [--allow-unauthenticated-cors-preflight-requests @@ -345,6 +346,15 @@ FLAGS --shielded-vtpm Default value is false. If set, instances will have vTPM enabled. + --startup-script-uri=STARTUP_SCRIPT_URI + Link to the startup script stored in Cloud Storage. The script is + executed on the workstation VM after it is booted. + + Example: + + $ gcloud beta workstations configs update \ + --startup-script-uri gs://{bucket-name}/{object-name} + --vm-tags=[VM_TAGS,...] Resource manager tags to be bound to the instance. Tag keys and values have the same definition as diff --git a/gcloud/bigtable/help b/gcloud/bigtable/help index 79a6be93a..6f626df14 100644 --- a/gcloud/bigtable/help +++ b/gcloud/bigtable/help @@ -42,6 +42,9 @@ GROUPS operations Manage Cloud Bigtable operations. + schema-bundles + Manage Bigtable schema bundles. + tables Query Cloud Bigtable tables. diff --git a/gcloud/bigtable/schema-bundles/add-iam-policy-binding b/gcloud/bigtable/schema-bundles/add-iam-policy-binding new file mode 100644 index 000000000..4fae1e73e --- /dev/null +++ b/gcloud/bigtable/schema-bundles/add-iam-policy-binding @@ -0,0 +1,159 @@ +NAME + gcloud bigtable schema-bundles add-iam-policy-binding - add an IAM policy + binding to a Bigtable schema bundle + +SYNOPSIS + gcloud bigtable schema-bundles add-iam-policy-binding + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) --member=PRINCIPAL + --role=ROLE + [--condition=[KEY=VALUE,...] | --condition-from-file=PATH_TO_FILE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add an IAM policy binding to a Bigtable schema bundle. One binding consists + of a member, a role, and an optional condition. + +EXAMPLES + To add an IAM policy binding for the role of roles/editor for the user + 222larabrown@gmail.com with schema bundle my-schema-bundle in instance + my-instance and table my-table, run: + + $ gcloud bigtable schema-bundles add-iam-policy-binding \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + --member=`user:222larabrown@gmail.com` --role=`roles/editor` + + To add an IAM policy binding which expires at the end of the year 2025 for + the role of roles/bigtable.admin and the user 222larabrown@gmail.com with + schema bundle my-schema-bundle in instance my-instance and table my-table, + run: + + $ gcloud bigtable schema-bundles add-iam-policy-binding \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + --member=`user:222larabrown@gmail.com` \ + --role=`roles/bigtable.admin` \ + --condition=`expression=request.time < \ + timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,\ + description=Expires at midnight on 2020-12-31` + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to add the IAM policy + binding to. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=PATH_TO_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. Use a full or + relative path to a local file containing the value of condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable schema-bundles add-iam-policy-binding + + $ gcloud beta bigtable schema-bundles add-iam-policy-binding + diff --git a/gcloud/bigtable/schema-bundles/create b/gcloud/bigtable/schema-bundles/create new file mode 100644 index 000000000..71506d032 --- /dev/null +++ b/gcloud/bigtable/schema-bundles/create @@ -0,0 +1,98 @@ +NAME + gcloud bigtable schema-bundles create - create a new Bigtable schema bundle + +SYNOPSIS + gcloud bigtable schema-bundles create + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + --proto-descriptors-file=PROTO_DESCRIPTORS_FILE [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new Bigtable schema bundle. + +EXAMPLES + To create a schema bundle my-schema-bundle in instance my-instance and + table my-table, using the descriptor file my-descriptor-file.pb: + + $ gcloud bigtable schema-bundles create my-schema-bundle \ + --instance=test-instance --table=test-table \ + --proto-descriptors-file=my-descriptor-file.pb + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to create. The arguments + in this group can be used to specify the attributes of this resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +REQUIRED FLAGS + --proto-descriptors-file=PROTO_DESCRIPTORS_FILE + Path of a file that contains a protobuf-serialized + google.protobuf.FileDescriptorSet message. If specified, the schema + bundle contains the protobuf schema. To generate the file, install and + run protoc with the following command: + + protoc --proto_path=IMPORT_PATH --include_imports --descriptor_set_out=DESCRIPTOR_OUTPUT_LOCATION path/to/file.proto + + where the --proto_path option specificies where to look for .proto + files when resolving import directives (the current directory is used + if you do not provide a value), and the --descriptor_set_out option + specifies where you want the generated FileDescriptorSet to be written. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable schema-bundles create + + $ gcloud beta bigtable schema-bundles create + diff --git a/gcloud/bigtable/schema-bundles/delete b/gcloud/bigtable/schema-bundles/delete new file mode 100644 index 000000000..bc555752f --- /dev/null +++ b/gcloud/bigtable/schema-bundles/delete @@ -0,0 +1,77 @@ +NAME + gcloud bigtable schema-bundles delete - delete a Bigtable schema bundle + +SYNOPSIS + gcloud bigtable schema-bundles delete + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Bigtable schema bundle. + +EXAMPLES + To delete the schema bundle my-schema-bundle in instance my-instance and + table my-table: + + $ gcloud bigtable schema-bundles delete my-schema-bundle \ + --instance=test-instance --table=test-table + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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 bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable schema-bundles delete + + $ gcloud beta bigtable schema-bundles delete + diff --git a/gcloud/bigtable/schema-bundles/describe b/gcloud/bigtable/schema-bundles/describe new file mode 100644 index 000000000..4e3e2fa2b --- /dev/null +++ b/gcloud/bigtable/schema-bundles/describe @@ -0,0 +1,77 @@ +NAME + gcloud bigtable schema-bundles describe - describe a Bigtable schema bundle + +SYNOPSIS + gcloud bigtable schema-bundles describe + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Bigtable schema bundle. + +EXAMPLES + To describe the schema bundle my-schema-bundle in instance my-instance and + table my-table: + + $ gcloud bigtable schema-bundles describe my-schema-bundle \ + --instance=test-instance --table=test-table + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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 bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable schema-bundles describe + + $ gcloud beta bigtable schema-bundles describe + diff --git a/gcloud/bigtable/schema-bundles/get-iam-policy b/gcloud/bigtable/schema-bundles/get-iam-policy new file mode 100644 index 000000000..7449ff1ac --- /dev/null +++ b/gcloud/bigtable/schema-bundles/get-iam-policy @@ -0,0 +1,108 @@ +NAME + gcloud bigtable schema-bundles get-iam-policy - get an IAM policy on a + Bigtable schema bundle + +SYNOPSIS + gcloud bigtable schema-bundles get-iam-policy + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get an IAM policy on a Bigtable schema bundle. + +EXAMPLES + To get the IAM policy on the schema bundle my-schema-bundle in instance + my-instance and table my-table, run: + + $ gcloud bigtable schema-bundles get-iam-policy my-schema-bundle \ + --instance=`my-instance` --table=`my-table` + + See https://cloud.google.com/iam/docs/managing-policies for more + information. + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to get the IAM policy for. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable schema-bundles get-iam-policy + + $ gcloud beta bigtable schema-bundles get-iam-policy + diff --git a/gcloud/bigtable/schema-bundles/help b/gcloud/bigtable/schema-bundles/help new file mode 100644 index 000000000..d4d7a688f --- /dev/null +++ b/gcloud/bigtable/schema-bundles/help @@ -0,0 +1,51 @@ +NAME + gcloud bigtable schema-bundles - manage Bigtable schema bundles + +SYNOPSIS + gcloud bigtable schema-bundles COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Bigtable schema bundles. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + Add an IAM policy binding to a Bigtable schema bundle. + + create + Create a new Bigtable schema bundle. + + delete + Delete a Bigtable schema bundle. + + describe + Describe a Bigtable schema bundle. + + get-iam-policy + Get an IAM policy on a Bigtable schema bundle. + + list + List all schema bundles of a Bigtable table. + + remove-iam-policy-binding + Remove an IAM policy binding from a Bigtable schema bundle. + + set-iam-policy + Set an IAM policy on a Bigtable schema bundle. + + update + Update an existing Bigtable schema bundle. + +NOTES + These variants are also available: + + $ gcloud alpha bigtable schema-bundles + + $ gcloud beta bigtable schema-bundles + diff --git a/gcloud/bigtable/schema-bundles/list b/gcloud/bigtable/schema-bundles/list new file mode 100644 index 000000000..96452f0a8 --- /dev/null +++ b/gcloud/bigtable/schema-bundles/list @@ -0,0 +1,105 @@ +NAME + gcloud bigtable schema-bundles list - list all schema bundles of a Bigtable + table + +SYNOPSIS + gcloud bigtable schema-bundles list (--table=TABLE : --instance=INSTANCE) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all schema bundles of a Bigtable table. + +EXAMPLES + To list the schema bundles in instance my-instance and table my-table: + + $ gcloud bigtable schema-bundles list --instance=my-instance \ + --table=my-table + + To list all schema bundles that match the given filter: + + $ gcloud bigtable schema-bundles list --instance=my-instance \ + --table=my-table --filter="name=( `NAME` ... )" + +REQUIRED FLAGS + Table resource - Bigtable table for which to list all schema bundles. 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 --table 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. + + --table=TABLE + ID of the table or fully qualified identifier for the table. + + To set the table attribute: + ▸ provide the argument --table on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument --table on the command line with a fully + specified name; + ▸ provide the argument --instance 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 bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable schema-bundles list + + $ gcloud beta bigtable schema-bundles list + diff --git a/gcloud/bigtable/schema-bundles/remove-iam-policy-binding b/gcloud/bigtable/schema-bundles/remove-iam-policy-binding new file mode 100644 index 000000000..5f81dbdb8 --- /dev/null +++ b/gcloud/bigtable/schema-bundles/remove-iam-policy-binding @@ -0,0 +1,164 @@ +NAME + gcloud bigtable schema-bundles remove-iam-policy-binding - remove an IAM + policy binding from a Bigtable schema bundle + +SYNOPSIS + gcloud bigtable schema-bundles remove-iam-policy-binding + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) --member=PRINCIPAL + --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=PATH_TO_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove an IAM policy binding from a Bigtable schema bundle. One binding + consists of a member, a role, and an optional condition. + +EXAMPLES + To remove an IAM policy binding for the role of roles/editor for the user + 222larabrown@gmail.com with schema bundle my-schema-bundle in instance + my-instance and table my-table, run: + + $ gcloud bigtable schema-bundles remove-iam-policy-binding \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + --member=`user:222larabrown@gmail.com` --role=`roles/editor` + + To remove an IAM policy binding which expires at the end of the year 2025 + for the role of roles/bigtable.admin and the user 222larabrown@gmail.com + with schema bundle my-schema-bundle in instance my-instance and table + my-table, run: + + $ gcloud bigtable schema-bundles remove-iam-policy-binding \ + my-schema-bundle --instance=`my-instance` --table=`my-table` \ + --member=`user:222larabrown@gmail.com` \ + --role=`roles/bigtable.admin` \ + --condition=`expression=request.time < \ + timestamp("2021-01-01T00:00:00Z"),title=expires_end_of_2020,\ + description=Expires at midnight on 2020-12-31` + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to remove the IAM policy + binding 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=PATH_TO_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. Use a full or + relative path to a local file containing the value of condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable schema-bundles remove-iam-policy-binding + + $ gcloud beta bigtable schema-bundles remove-iam-policy-binding + diff --git a/gcloud/bigtable/schema-bundles/set-iam-policy b/gcloud/bigtable/schema-bundles/set-iam-policy new file mode 100644 index 000000000..5a7892681 --- /dev/null +++ b/gcloud/bigtable/schema-bundles/set-iam-policy @@ -0,0 +1,88 @@ +NAME + gcloud bigtable schema-bundles set-iam-policy - set an IAM policy on a + Bigtable schema bundle + +SYNOPSIS + gcloud bigtable schema-bundles set-iam-policy + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Set an IAM policy on a Bigtable schema bundle. + +EXAMPLES + To set the IAM policy from file my-policy on the schema bundle + my-schema-bundle in instance my-instance and table my-table, run: + + $ gcloud bigtable schema-bundles set-iam-policy my-schema-bundle \ + --instance=`my-instance` --table=`my-table` my-policy + + See https://cloud.google.com/iam/docs/managing-policies for more + information. + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle to set the IAM policy on. + 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table 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. + +API REFERENCE + This command uses the bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable schema-bundles set-iam-policy + + $ gcloud beta bigtable schema-bundles set-iam-policy + diff --git a/gcloud/bigtable/schema-bundles/update b/gcloud/bigtable/schema-bundles/update new file mode 100644 index 000000000..30fcfb17c --- /dev/null +++ b/gcloud/bigtable/schema-bundles/update @@ -0,0 +1,102 @@ +NAME + gcloud bigtable schema-bundles update - update an existing Bigtable schema + bundle + +SYNOPSIS + gcloud bigtable schema-bundles update + (SCHEMA_BUNDLE : --instance=INSTANCE --table=TABLE) + --proto-descriptors-file=PROTO_DESCRIPTORS_FILE [--async] + [--ignore-warnings] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an existing Bigtable schema bundle. + +EXAMPLES + To update a schema bundle my-schema-bundle in instance my-instance and + table my-table, using the descriptor file my-descriptor-file.pb: + + $ gcloud bigtable schema-bundles update my-schema-bundle \ + --instance=my-instance --table=my-table \ + --proto-descriptors-file=my-descriptor-file.pb + +POSITIONAL ARGUMENTS + Schema bundle resource - Bigtable schema bundle 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 schema_bundle 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. + + SCHEMA_BUNDLE + ID of the schema-bundle or fully qualified identifier for the + schema-bundle. + + To set the schema_bundle attribute: + ▸ provide the argument schema_bundle on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --instance=INSTANCE + Name of the Bigtable instance. + + To set the instance attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --instance on the command line. + + --table=TABLE + Name of the Bigtable table. + + To set the table attribute: + ▸ provide the argument schema_bundle on the command line with a + fully specified name; + ▸ provide the argument --table on the command line. + +REQUIRED FLAGS + --proto-descriptors-file=PROTO_DESCRIPTORS_FILE + Path of a file that contains a protobuf-serialized + google.protobuf.FileDescriptorSet message. If specified, the schema + bundle contains the protobuf schema. To generate the file, install and + run protoc with the following command: + + protoc --proto_path=IMPORT_PATH --include_imports --descriptor_set_out=DESCRIPTOR_OUTPUT_LOCATION path/to/file.proto + + where the --proto_path option specificies where to look for .proto + files when resolving import directives (the current directory is used + if you do not provide a value), and the --descriptor_set_out option + specifies where you want the generated FileDescriptorSet to be written. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --ignore-warnings + If true, backwards incompatible changes will be allowed. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 bigtableadmin/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/bigtable/ + +NOTES + These variants are also available: + + $ gcloud alpha bigtable schema-bundles update + + $ gcloud beta bigtable schema-bundles update + diff --git a/gcloud/compute/commitments/create b/gcloud/compute/commitments/create index d160d33d4..a9a40a81e 100644 --- a/gcloud/compute/commitments/create +++ b/gcloud/compute/commitments/create @@ -108,9 +108,10 @@ OPTIONAL FLAGS compute-optimized-c3d, compute-optimized-h3, compute-optimized-h4d, general-purpose, general-purpose-c4, general-purpose-c4a, general-purpose-c4d, general-purpose-e2, general-purpose-n2, - general-purpose-n2d, general-purpose-n4, general-purpose-t2d, - graphics-optimized, memory-optimized, memory-optimized-m3, - memory-optimized-m4, memory-optimized-m4-6tb, memory-optimized-x4-16tb, + general-purpose-n2d, general-purpose-n4, general-purpose-n4d, + general-purpose-t2d, graphics-optimized, graphics-optimized-g4, + memory-optimized, memory-optimized-m3, memory-optimized-m4, + memory-optimized-m4-6tb, memory-optimized-x4-16tb, memory-optimized-x4-24tb, memory-optimized-x4-32tb, storage-optimized-z3. diff --git a/gcloud/compute/health-checks/create/grpc-with-tls b/gcloud/compute/health-checks/create/grpc-with-tls new file mode 100644 index 000000000..9c1f714b7 --- /dev/null +++ b/gcloud/compute/health-checks/create/grpc-with-tls @@ -0,0 +1,119 @@ +NAME + gcloud compute health-checks create grpc-with-tls - create a gRPC with TLS + health check to monitor load balanced instances + +SYNOPSIS + gcloud compute health-checks create grpc-with-tls NAME + [--check-interval=CHECK_INTERVAL; default="5s"] + [--description=DESCRIPTION] [--enable-logging] + [--grpc-service-name=GRPC_SERVICE_NAME] + [--healthy-threshold=HEALTHY_THRESHOLD; default=2] + [--timeout=TIMEOUT; default="5s"] + [--unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2] + [--global | --region=REGION] [--port=PORT --use-serving-port] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute health-checks create grpc-with-tls is used to create a + non-legacy health check using the gRPC with TLS protocol. You can use this + health check for Google Cloud load balancers or for managed instance group + autohealing. For more information, see the health checks overview at: + https://cloud.google.com/load-balancing/docs/health-check-concepts + +POSITIONAL ARGUMENTS + NAME + Name of the gRPC with TLS health check to create. + +FLAGS + --check-interval=CHECK_INTERVAL; default="5s" + How often to perform a health check for an instance. For example, + specifying 10s will run the check every 10 seconds. The default value + is 5s. See $ gcloud topic datetimes for information on duration + formats. + + --description=DESCRIPTION + An optional string description for the gRPC with TLS health check. + + --enable-logging + Enable logging of health check probe results to Stackdriver. Logging is + disabled by default. + + Use --no-enable-logging to disable logging. + + --grpc-service-name=GRPC_SERVICE_NAME + An optional gRPC service name string of up to 1024 characters to + include in the gRPC health check request. Only ASCII characters are + allowed. + + --healthy-threshold=HEALTHY_THRESHOLD; default=2 + The number of consecutive successful health checks before an unhealthy + instance is marked as healthy. The default is 2. + + --timeout=TIMEOUT; default="5s" + If Google Compute Engine doesn't receive a healthy response from the + instance by the time specified by the value of this flag, the health + check request is considered a failure. For example, specifying 10s will + cause the check to wait for 10 seconds before considering the request a + failure. The default value is 5s. See $ gcloud topic datetimes for + information on duration formats. + + --unhealthy-threshold=UNHEALTHY_THRESHOLD; default=2 + The number of consecutive health check failures before a healthy + instance is marked as unhealthy. The default is 2. + + At most one of these can be specified: + + --global + If set, the gRPC with TLS health check is global. + + --region=REGION + Region of the gRPC with TLS health check to create. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + These flags configure the port that the health check monitors. + + --port=PORT + The TCP port number that this health check monitors. + + --use-serving-port + If given, use the "serving port" for health checks: + + ▸ When health checking network endpoints in a Network Endpoint + Group, use the port specified with each endpoint. + --use-serving-port must be used when using a Network Endpoint Group + as a backend as this flag specifies the portSpecification option + for a Health Check object. + ▸ When health checking other backends, use the port of the backend + service. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 health-checks create grpc-with-tls + + $ gcloud beta compute health-checks create grpc-with-tls + diff --git a/gcloud/compute/health-checks/create/help b/gcloud/compute/health-checks/create/help index b2886d218..0761592bd 100644 --- a/gcloud/compute/health-checks/create/help +++ b/gcloud/compute/health-checks/create/help @@ -19,6 +19,9 @@ COMMANDS grpc Create a gRPC health check to monitor load balanced instances. + grpc-with-tls + Create a gRPC with TLS health check to monitor load balanced instances. + http Create a HTTP health check to monitor load balanced instances. diff --git a/gcloud/compute/health-checks/update/grpc-with-tls b/gcloud/compute/health-checks/update/grpc-with-tls new file mode 100644 index 000000000..1fe6048b7 --- /dev/null +++ b/gcloud/compute/health-checks/update/grpc-with-tls @@ -0,0 +1,115 @@ +NAME + gcloud compute health-checks update grpc-with-tls - update a gRPC with TLS + health check + +SYNOPSIS + gcloud compute health-checks update grpc-with-tls NAME + [--check-interval=CHECK_INTERVAL] [--description=DESCRIPTION] + [--enable-logging] [--grpc-service-name=GRPC_SERVICE_NAME] + [--healthy-threshold=HEALTHY_THRESHOLD] [--timeout=TIMEOUT] + [--unhealthy-threshold=UNHEALTHY_THRESHOLD] + [--global | --region=REGION] [--port=PORT --use-serving-port] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute health-checks update grpc-with-tls is used to update an + existing gRPC with TLS health check. Only arguments passed in will be + updated on the health check. Other attributes will remain unaffected. + +POSITIONAL ARGUMENTS + NAME + Name of the gRPC with TLS health check to update. + +FLAGS + --check-interval=CHECK_INTERVAL + How often to perform a health check for an instance. For example, + specifying 10s will run the check every 10 seconds. See $ gcloud topic + datetimes for information on duration formats. + + --description=DESCRIPTION + A textual description for the gRPC with TLS health check. Pass in an + empty string to unset. + + --enable-logging + Enable logging of health check probe results to Stackdriver. Logging is + disabled by default. + + Use --no-enable-logging to disable logging. + + --grpc-service-name=GRPC_SERVICE_NAME + An optional gRPC service name string of up to 1024 characters to + include in the gRPC health check request. Pass in an empty string to + unset. Only ASCII characters are allowed. + + --healthy-threshold=HEALTHY_THRESHOLD + The number of consecutive successful health checks before an unhealthy + instance is marked as healthy. + + --timeout=TIMEOUT + If Google Compute Engine doesn't receive a healthy response from the + instance by the time specified by the value of this flag, the health + check request is considered a failure. For example, specifying 10s will + cause the check to wait for 10 seconds before considering the request a + failure. See $ gcloud topic datetimes for information on duration + formats. + + --unhealthy-threshold=UNHEALTHY_THRESHOLD + The number of consecutive health check failures before a healthy + instance is marked as unhealthy. + + At most one of these can be specified: + + --global + If set, the gRPC with TLS health check is global. + + --region=REGION + Region of the gRPC with TLS health check to update. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + These flags configure the port that the health check monitors. + + --port=PORT + The TCP port number that this health check monitors. + + --use-serving-port + If given, use the "serving port" for health checks: + + ▸ When health checking network endpoints in a Network Endpoint + Group, use the port specified with each endpoint. + --use-serving-port must be used when using a Network Endpoint Group + as a backend as this flag specifies the portSpecification option + for a Health Check object. + ▸ When health checking other backends, use the port of the backend + service. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 health-checks update grpc-with-tls + + $ gcloud beta compute health-checks update grpc-with-tls + diff --git a/gcloud/compute/health-checks/update/help b/gcloud/compute/health-checks/update/help index 772309805..1dcd81e61 100644 --- a/gcloud/compute/health-checks/update/help +++ b/gcloud/compute/health-checks/update/help @@ -19,6 +19,9 @@ COMMANDS grpc Update a gRPC health check. + grpc-with-tls + Update a gRPC with TLS health check. + http Update a HTTP health check. diff --git a/gcloud/compute/interconnects/attachments/dedicated/create b/gcloud/compute/interconnects/attachments/dedicated/create index e466a58fb..3f5120feb 100644 --- a/gcloud/compute/interconnects/attachments/dedicated/create +++ b/gcloud/compute/interconnects/attachments/dedicated/create @@ -11,8 +11,8 @@ SYNOPSIS [--customer-router-ipv6-interface-id=PEER_INTERFACE_ID] [--description=DESCRIPTION] [--enable-admin] [--encryption=ENCRYPTION] [--ipsec-internal-addresses=[ADDRESSES]] [--mtu=MTU] [--region=REGION] - [--stack-type=STACK_TYPE] [--subnet-length=SUBNET_LENGTH] [--vlan=VLAN] - [GCLOUD_WIDE_FLAG ...] + [--resource-manager-tags=[KEY=VALUE,...]] [--stack-type=STACK_TYPE] + [--subnet-length=SUBNET_LENGTH] [--vlan=VLAN] [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute interconnects attachments dedicated create is used to create @@ -147,6 +147,10 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the + interconnect. + --stack-type=STACK_TYPE Stack type of the protocol(s) enabled on this interconnect attachment. STACK_TYPE must be one of: diff --git a/gcloud/compute/interconnects/attachments/help b/gcloud/compute/interconnects/attachments/help index 57bf023d1..db0c5974d 100644 --- a/gcloud/compute/interconnects/attachments/help +++ b/gcloud/compute/interconnects/attachments/help @@ -23,6 +23,9 @@ GROUPS groups Create or manipulate interconnect attachment groups. + l2-forwarding + Create or manipulate dedicated interconnect attachments. + partner Create or manipulate partner interconnect attachments. diff --git a/gcloud/compute/interconnects/attachments/l2-forwarding/add-mapping b/gcloud/compute/interconnects/attachments/l2-forwarding/add-mapping new file mode 100644 index 000000000..bf3aac83f --- /dev/null +++ b/gcloud/compute/interconnects/attachments/l2-forwarding/add-mapping @@ -0,0 +1,76 @@ +NAME + gcloud compute interconnects attachments l2-forwarding add-mapping - add + new vlan to ip mapping rule to an L2-forwarding attachment + +SYNOPSIS + gcloud compute interconnects attachments l2-forwarding add-mapping NAME + --vlan-key=VLAN_KEY [--appliance-ip-address=ADDRESSES] + [--appliance-name=APPLIANCE_NAME] + [--inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS], + [innerVlanTags=INNERVLANTAGS]] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects attachments l2-forwarding add-mapping add new + vlan to ip mapping rule to an L2-forwarding attachment. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to patch. + +REQUIRED FLAGS + --vlan-key=VLAN_KEY + Desired VLAN key for L2 forwarding mapping for the attachment. If not + supplied, all mappings will be displayed. + +OPTIONAL FLAGS + --appliance-ip-address=ADDRESSES + A single IPv4 or IPv6 address used as the destination IP address for + ingress packets that match on a VLAN tag, but do not match a more + specific inner VLAN tag. + + --appliance-name=APPLIANCE_NAME + The name of the L2 appliance mapping rule. + + --inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS],[innerVlanTags=INNERVLANTAGS] + A list of mapping rules from inner VLAN tags to IP addresses. If the + inner VLAN is not explicitly mapped to an IP address range, the + applianceIpAddress is used. + + --region=REGION + Region of the interconnect attachment to patch. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 interconnects attachments l2-forwarding \ + add-mapping + + $ gcloud beta compute interconnects attachments l2-forwarding \ + add-mapping + diff --git a/gcloud/compute/interconnects/attachments/l2-forwarding/create b/gcloud/compute/interconnects/attachments/l2-forwarding/create new file mode 100644 index 000000000..df27dcc31 --- /dev/null +++ b/gcloud/compute/interconnects/attachments/l2-forwarding/create @@ -0,0 +1,131 @@ +NAME + gcloud compute interconnects attachments l2-forwarding create - create a + Compute Engine L2 forwarding interconnect attachment + +SYNOPSIS + gcloud compute interconnects attachments l2-forwarding create NAME + --geneve-vni=GENEVE_HEADER --interconnect=INTERCONNECT + --network=NETWORK + --tunnel-endpoint-ip-address=TUNNEL_ENDPOINT_IP_ADDRESS + [--bandwidth=BANDWIDTH] + [--default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS] + [--description=DESCRIPTION] [--enable-admin] [--mtu=MTU] + [--region=REGION] [--resource-manager-tags=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects attachments l2-forwarding create is used to + create a L2 forwarding interconnect attachments. An interconnect attachment + is what binds the underlying connectivity of an interconnect to a path into + and out of the customer's cloud network. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to create. + +REQUIRED FLAGS + --geneve-vni=GENEVE_HEADER + A VNI identier for Geneve header, as defined in + https://datatracker.ietf.org/doc/html/rfc8926, used for L2 forwarding. + + --interconnect=INTERCONNECT + The interconnect for the interconnect attachment + + --network=NETWORK + The Google Network to use for L2 forwarding. + + --tunnel-endpoint-ip-address=TUNNEL_ENDPOINT_IP_ADDRESS + A single IPv4 or IPv6 address. This address will be used as the source + IP address for L2 forwarding packets sent to the appliances, and must + be used as the destination IP address for packets that should be sent + out through this attachment. + +OPTIONAL FLAGS + --bandwidth=BANDWIDTH + Provisioned capacity of the attachment. BANDWIDTH must be one of: + + 50m + 50 Mbit/s + 100m + 100 Mbit/s + 200m + 200 Mbit/s + 300m + 300 Mbit/s + 400m + 400 Mbit/s + 500m + 500 Mbit/s + 1g + 1 Gbit/s + 2g + 2 Gbit/s + 5g + 5 Gbit/s + 10g + 10 Gbit/s + 20g + 20 Gbit/s + 50g + 50 Gbit/s + 100g + 100 Gbit/s + + --default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS + A single IPv4 or IPv6 address used as the default destination IP when + there is no VLAN mapping result found for L2 forwarding. Unset field + indicates the unmatched packet should be dropped. + + --description=DESCRIPTION + Human-readable plain-text description of attachment. + + --enable-admin + Administrative status of the interconnect attachment. If not provided + on creation, defaults to enabled. When this is enabled, the attachment + is operational and will carry traffic. Use --no-enable-admin to disable + it. + + --mtu=MTU + Maximum transmission unit (MTU) is the size of the largest IP packet + passing through this interconnect attachment. Must be one of 1440, + 1460, 1500, or 8896. If not specified, the value will default to 1440. + + --region=REGION + Region of the interconnect attachment to create. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the + interconnect. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 interconnects attachments l2-forwarding create + + $ gcloud beta compute interconnects attachments l2-forwarding create + diff --git a/gcloud/compute/interconnects/attachments/l2-forwarding/describe-mapping b/gcloud/compute/interconnects/attachments/l2-forwarding/describe-mapping new file mode 100644 index 000000000..980018ec2 --- /dev/null +++ b/gcloud/compute/interconnects/attachments/l2-forwarding/describe-mapping @@ -0,0 +1,60 @@ +NAME + gcloud compute interconnects attachments l2-forwarding describe-mapping - + describe a Compute Engine L2 forwarding interconnect attachment + +SYNOPSIS + gcloud compute interconnects attachments l2-forwarding describe-mapping + NAME --vlan-key=VLAN_KEY [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects attachments l2-forwarding describe-mapping + displays all data associated with Compute Engine interconnect attachment in + a project. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to describe. + +REQUIRED FLAGS + --vlan-key=VLAN_KEY + Desired VLAN key for L2 forwarding mapping for the attachment. If not + supplied, all mappings will be displayed. + +OPTIONAL FLAGS + --region=REGION + Region of the interconnect attachment to describe. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 interconnects attachments l2-forwarding \ + describe-mapping + + $ gcloud beta compute interconnects attachments l2-forwarding \ + describe-mapping + diff --git a/gcloud/compute/interconnects/attachments/l2-forwarding/help b/gcloud/compute/interconnects/attachments/l2-forwarding/help new file mode 100644 index 000000000..f898c96fd --- /dev/null +++ b/gcloud/compute/interconnects/attachments/l2-forwarding/help @@ -0,0 +1,55 @@ +NAME + gcloud compute interconnects attachments l2-forwarding - create or + manipulate dedicated interconnect attachments + +SYNOPSIS + gcloud compute interconnects attachments l2-forwarding COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create or manipulate L2 Forwarding Interconnect attachments. + + For more information about about interconnect attachments for L2 Forwaring + Interconnect, see the documentation for L2 Forwarding interconnect + attachments + (https://cloud.google.com/network-connectivity/docs/interconnect/how-to/l2-forwarding/creating-l2-attachments). + + See also: Interconnect attachments API + (https://cloud.google.com/compute/docs/reference/rest/v1/interconnectAttachments). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-mapping + Add new vlan to ip mapping rule to an L2-forwarding attachment. + + create + Create a Compute Engine L2 forwarding interconnect attachment. + + describe-mapping + Describe a Compute Engine L2 forwarding interconnect attachment. + + list-mapping + List Google Compute Engine interconnect attachments. + + remove-mapping + Remove vlan to ip mapping rule to an L2-forwarding attachment. + + update + Update a Compute Engine L2 forwarding interconnect attachment. + + update-mapping + Update vlan to ip mapping rule to an L2-forwarding attachment. + +NOTES + These variants are also available: + + $ gcloud alpha compute interconnects attachments l2-forwarding + + $ gcloud beta compute interconnects attachments l2-forwarding + diff --git a/gcloud/compute/interconnects/attachments/l2-forwarding/list-mapping b/gcloud/compute/interconnects/attachments/l2-forwarding/list-mapping new file mode 100644 index 000000000..750c3fe0c --- /dev/null +++ b/gcloud/compute/interconnects/attachments/l2-forwarding/list-mapping @@ -0,0 +1,108 @@ +NAME + gcloud compute interconnects attachments l2-forwarding list-mapping - list + Google Compute Engine interconnect attachments + +SYNOPSIS + gcloud compute interconnects attachments l2-forwarding list-mapping NAME + [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects attachments l2-forwarding list-mapping + displays all Google Compute Engine interconnect attachments in a project. + + By default, interconnect attachments from all regions are listed. The + results can be narrowed down using a filter: --filter="region:( REGION ... + )". + +EXAMPLES + To list all interconnect attachments in a project in table form, run: + + $ gcloud compute interconnects attachments l2-forwarding list-mapping + + To list the URIs of all interconnect attachments in a project, run: + + $ gcloud compute interconnects attachments l2-forwarding \ + list-mapping --uri + + To list all interconnect attachments in the us-central1 and europe-west1 + regions, run: + + $ gcloud compute interconnects attachments l2-forwarding \ + list-mapping --filter="region:( us-central1 europe-west1 )" + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to describe. + +FLAGS + --region=REGION + Region of the interconnect attachment to describe. If not specified, + you might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +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 interconnects attachments l2-forwarding \ + list-mapping + + $ gcloud beta compute interconnects attachments l2-forwarding \ + list-mapping + diff --git a/gcloud/compute/interconnects/attachments/l2-forwarding/remove-mapping b/gcloud/compute/interconnects/attachments/l2-forwarding/remove-mapping new file mode 100644 index 000000000..29ba35d69 --- /dev/null +++ b/gcloud/compute/interconnects/attachments/l2-forwarding/remove-mapping @@ -0,0 +1,59 @@ +NAME + gcloud compute interconnects attachments l2-forwarding remove-mapping - + remove vlan to ip mapping rule to an L2-forwarding attachment + +SYNOPSIS + gcloud compute interconnects attachments l2-forwarding remove-mapping NAME + --vlan-key=VLAN_KEY [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects attachments l2-forwarding remove-mapping + remove vlan to ip mapping rule to an L2-forwarding attachment. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to create. + +REQUIRED FLAGS + --vlan-key=VLAN_KEY + Desired VLAN key for L2 forwarding mapping for the attachment. If not + supplied, all mappings will be displayed. + +OPTIONAL FLAGS + --region=REGION + Region of the interconnect attachment to create. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 interconnects attachments l2-forwarding \ + remove-mapping + + $ gcloud beta compute interconnects attachments l2-forwarding \ + remove-mapping + diff --git a/gcloud/compute/interconnects/attachments/l2-forwarding/update b/gcloud/compute/interconnects/attachments/l2-forwarding/update new file mode 100644 index 000000000..07cbeef57 --- /dev/null +++ b/gcloud/compute/interconnects/attachments/l2-forwarding/update @@ -0,0 +1,111 @@ +NAME + gcloud compute interconnects attachments l2-forwarding update - update a + Compute Engine L2 forwarding interconnect attachment + +SYNOPSIS + gcloud compute interconnects attachments l2-forwarding update NAME + [--bandwidth=BANDWIDTH] + [--default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS] + [--description=DESCRIPTION] [--enable-admin] + [--geneve-vni=GENEVE_HEADER] [--mtu=MTU] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects attachments l2-forwarding update is used to + update interconnect attachments. An interconnect attachment is what binds + the underlying connectivity of an interconnect to a path into and out of + the customer's cloud network. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to patch. + +FLAGS + --bandwidth=BANDWIDTH + Provisioned capacity of the attachment. BANDWIDTH must be one of: + + 50m + 50 Mbit/s + 100m + 100 Mbit/s + 200m + 200 Mbit/s + 300m + 300 Mbit/s + 400m + 400 Mbit/s + 500m + 500 Mbit/s + 1g + 1 Gbit/s + 2g + 2 Gbit/s + 5g + 5 Gbit/s + 10g + 10 Gbit/s + 20g + 20 Gbit/s + 50g + 50 Gbit/s + 100g + 100 Gbit/s + + --default-appliance-ip-address=DEFAULT_APPLIANCE_IP_ADDRESS + A single IPv4 or IPv6 address used as the default destination IP when + there is no VLAN mapping result found for L2 forwarding. Unset field + indicates the unmatched packet should be dropped. + + --description=DESCRIPTION + Human-readable plain-text description of attachment. + + --enable-admin + Administrative status of the interconnect attachment. If not provided + on creation, defaults to enabled. When this is enabled, the attachment + is operational and will carry traffic. Use --no-enable-admin to disable + it. + + --geneve-vni=GENEVE_HEADER + A VNI identier for Geneve header, as defined in + https://datatracker.ietf.org/doc/html/rfc8926, used for L2 forwarding. + + --mtu=MTU + Maximum transmission unit (MTU) is the size of the largest IP packet + passing through this interconnect attachment. Must be one of 1440, + 1460, 1500, or 8896. If not specified, the value will default to 1440. + + --region=REGION + Region of the interconnect attachment to patch. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 interconnects attachments l2-forwarding update + + $ gcloud beta compute interconnects attachments l2-forwarding update + diff --git a/gcloud/compute/interconnects/attachments/l2-forwarding/update-mapping b/gcloud/compute/interconnects/attachments/l2-forwarding/update-mapping new file mode 100644 index 000000000..1feed8a6b --- /dev/null +++ b/gcloud/compute/interconnects/attachments/l2-forwarding/update-mapping @@ -0,0 +1,76 @@ +NAME + gcloud compute interconnects attachments l2-forwarding update-mapping - + update vlan to ip mapping rule to an L2-forwarding attachment + +SYNOPSIS + gcloud compute interconnects attachments l2-forwarding update-mapping NAME + --vlan-key=VLAN_KEY [--appliance-ip-address=ADDRESSES] + [--appliance-name=APPLIANCE_NAME] + [--inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS], + [innerVlanTags=INNERVLANTAGS]] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud compute interconnects attachments l2-forwarding update-mapping + update vlan to ip mapping rule to an L2-forwarding attachment. + +POSITIONAL ARGUMENTS + NAME + Name of the interconnect attachment to create. + +REQUIRED FLAGS + --vlan-key=VLAN_KEY + Desired VLAN key for L2 forwarding mapping for the attachment. If not + supplied, all mappings will be displayed. + +OPTIONAL FLAGS + --appliance-ip-address=ADDRESSES + A single IPv4 or IPv6 address used as the destination IP address for + ingress packets that match on a VLAN tag, but do not match a more + specific inner VLAN tag. + + --appliance-name=APPLIANCE_NAME + The name of the L2 appliance mapping rule. + + --inner-vlan-to-appliance-mappings=[innerApplianceIpAddress=INNERAPPLIANCEIPADDRESS],[innerVlanTags=INNERVLANTAGS] + A list of mapping rules from inner VLAN tags to IP addresses. If the + inner VLAN is not explicitly mapped to an IP address range, the + applianceIpAddress is used. + + --region=REGION + Region of the interconnect attachment to create. If not specified, you + might be prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 interconnects attachments l2-forwarding \ + update-mapping + + $ gcloud beta compute interconnects attachments l2-forwarding \ + update-mapping + diff --git a/gcloud/compute/interconnects/attachments/partner/create b/gcloud/compute/interconnects/attachments/partner/create index 648711118..ff833236f 100644 --- a/gcloud/compute/interconnects/attachments/partner/create +++ b/gcloud/compute/interconnects/attachments/partner/create @@ -7,7 +7,8 @@ SYNOPSIS --edge-availability-domain=AVAILABILITY_DOMAIN --router=ROUTER [--description=DESCRIPTION] [--enable-admin] [--encryption=ENCRYPTION] [--ipsec-internal-addresses=[ADDRESSES]] [--mtu=MTU] [--region=REGION] - [--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...] + [--resource-manager-tags=[KEY=VALUE,...]] [--stack-type=STACK_TYPE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION gcloud compute interconnects attachments partner create is used to create @@ -111,6 +112,10 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the + interconnect. + --stack-type=STACK_TYPE Stack type of the protocol(s) enabled on this interconnect attachment. STACK_TYPE must be one of: diff --git a/gcloud/compute/interconnects/create b/gcloud/compute/interconnects/create index 049fd7164..635bff832 100644 --- a/gcloud/compute/interconnects/create +++ b/gcloud/compute/interconnects/create @@ -8,7 +8,8 @@ SYNOPSIS [--admin-enabled] [--customer-name=CUSTOMER_NAME] [--description=DESCRIPTION] [--noc-contact-email=NOC_CONTACT_EMAIL] [--remote-location=REMOTE_LOCATION] - [--requested-features=[FEATURES,...]] [--subzone=SUBZONE] + [--requested-features=[FEATURES,...]] + [--resource-manager-tags=[KEY=VALUE,...]] [--subzone=SUBZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -115,6 +116,10 @@ OPTIONAL FLAGS only be provided during interconnect INSERT and cannot be changed using interconnect PATCH. + --resource-manager-tags=[KEY=VALUE,...] + A comma-separated list of Resource Manager tags to apply to the + interconnect. + --subzone=SUBZONE Subzone in the LOCATION specified by the --location flag. SUBZONE must be one of: diff --git a/gcloud/compute/networks/subnets/create b/gcloud/compute/networks/subnets/create index 057218ffa..e0e06e610 100644 --- a/gcloud/compute/networks/subnets/create +++ b/gcloud/compute/networks/subnets/create @@ -7,6 +7,7 @@ SYNOPSIS [--description=DESCRIPTION] [--enable-flow-logs] [--enable-private-ip-google-access] [--external-ipv6-prefix=EXTERNAL_IPV6_PREFIX] + [--internal-ipv6-prefix=INTERNAL_IPV6_PREFIX] [--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] @@ -62,10 +63,20 @@ OPTIONAL FLAGS For example, --external-ipv6-prefix=2600:1901:0:0:0:0:0:0/64 + --internal-ipv6-prefix=INTERNAL_IPV6_PREFIX + The /64 internal IPv6 CIDR range to assign to this subnet. The range + must be associated with an IPv6 BYOIP sub-prefix that is defined by the + --ip-collection flag. If you specify --ip-collection but not + --internal-ipv6-prefix, a random /64 range is allocated from the + sub-prefix. + + For example, --internal-ipv6-prefix 2600:1901:0:0:0:0:0:0/64 + --ip-collection=IP_COLLECTION Resource reference to a public delegated prefix. The PublicDelegatedPrefix must be a sub-prefix in - EXTERNAL_IPV6_SUBNETWORK_CREATION mode. + EXTERNAL_IPV6_SUBNETWORK_CREATION or INTERNAL_IPV6_SUBNETWORK_CREATION + mode. --ipv6-access-type=IPV6_ACCESS_TYPE IPv6 access type can be specified only when the subnet is created, or diff --git a/gcloud/compute/networks/subnets/update b/gcloud/compute/networks/subnets/update index dd6ba83c3..235bd9af4 100644 --- a/gcloud/compute/networks/subnets/update +++ b/gcloud/compute/networks/subnets/update @@ -7,6 +7,7 @@ SYNOPSIS [--add-secondary-ranges-with-reserved-internal-range=RANGE_NAME=INTERNAL_RANGE_URL, [...]] [--drain-timeout=DRAIN_TIMEOUT; default="0s"] [--external-ipv6-prefix=EXTERNAL_IPV6_PREFIX] + [--internal-ipv6-prefix=INTERNAL_IPV6_PREFIX] [--ip-collection=IP_COLLECTION] [--ipv6-access-type=IPV6_ACCESS_TYPE] [--logging-aggregation-interval=LOGGING_AGGREGATION_INTERVAL] [--logging-filter-expr=LOGGING_FILTER_EXPR] @@ -66,10 +67,20 @@ FLAGS For example, --external-ipv6-prefix=2600:1901:0:0:0:0:0:0/64 + --internal-ipv6-prefix=INTERNAL_IPV6_PREFIX + The /64 internal IPv6 CIDR range to assign to this subnet. The range + must be associated with an IPv6 BYOIP sub-prefix that is defined by the + --ip-collection flag. If you specify --ip-collection but not + --internal-ipv6-prefix, a random /64 range is allocated from the + sub-prefix. + + For example, --internal-ipv6-prefix 2600:1901:0:0:0:0:0:0/64 + --ip-collection=IP_COLLECTION Resource reference to a public delegated prefix. The PublicDelegatedPrefix must be a sub-prefix in - EXTERNAL_IPV6_SUBNETWORK_CREATION mode. + EXTERNAL_IPV6_SUBNETWORK_CREATION or INTERNAL_IPV6_SUBNETWORK_CREATION + mode. --ipv6-access-type=IPV6_ACCESS_TYPE IPv6 access type can be specified only when the subnet is created, or diff --git a/gcloud/compute/public-advertised-prefixes/create b/gcloud/compute/public-advertised-prefixes/create index b85599baa..8647ffe71 100644 --- a/gcloud/compute/public-advertised-prefixes/create +++ b/gcloud/compute/public-advertised-prefixes/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud compute public-advertised-prefixes create NAME --range=RANGE [--description=DESCRIPTION] [--dns-verification-ip=DNS_VERIFICATION_IP] - [--pdp-scope=PDP_SCOPE] [GCLOUD_WIDE_FLAG ...] + [--ipv6-access-type=IPV6_ACCESS_TYPE] [--pdp-scope=PDP_SCOPE] + [GCLOUD_WIDE_FLAG ...] EXAMPLES To create a public advertised prefix: @@ -36,6 +37,10 @@ OPTIONAL FLAGS IP address to use for verification. It must be within the IP range specified in --range. + --ipv6-access-type=IPV6_ACCESS_TYPE + Specifies the IPv6 access type of the public advertised prefix. + IPV6_ACCESS_TYPE must be one of: internal, external. + --pdp-scope=PDP_SCOPE Specifies how child public delegated prefix will be scoped. PDP_SCOPE must be one of: GLOBAL, REGIONAL. diff --git a/gcloud/compute/public-delegated-prefixes/create b/gcloud/compute/public-delegated-prefixes/create index 78fac71c8..1cfe3664b 100644 --- a/gcloud/compute/public-delegated-prefixes/create +++ b/gcloud/compute/public-delegated-prefixes/create @@ -49,7 +49,7 @@ OPTIONAL FLAGS --mode=MODE Specifies the mode of this IPv6 PDP. MODE must be one of: delegation, external-ipv6-forwarding-rule-creation, - external-ipv6-subnetwork-creation. + external-ipv6-subnetwork-creation, internal-ipv6-subnetwork-creation. At most one of these can be specified: diff --git a/gcloud/compute/public-delegated-prefixes/delegated-sub-prefixes/create b/gcloud/compute/public-delegated-prefixes/delegated-sub-prefixes/create index 7bf88a3b6..9d1e12a65 100644 --- a/gcloud/compute/public-delegated-prefixes/delegated-sub-prefixes/create +++ b/gcloud/compute/public-delegated-prefixes/delegated-sub-prefixes/create @@ -57,7 +57,7 @@ OPTIONAL FLAGS --mode=MODE Specifies the mode of this IPv6 PDP. MODE must be one of: delegation, external-ipv6-forwarding-rule-creation, - external-ipv6-subnetwork-creation. + external-ipv6-subnetwork-creation, internal-ipv6-subnetwork-creation. --range=RANGE IPv4 range from this public delegated prefix that should be delegated, diff --git a/gcloud/container/operations/cancel b/gcloud/container/operations/cancel index 8ad4d2919..45015a20b 100644 --- a/gcloud/container/operations/cancel +++ b/gcloud/container/operations/cancel @@ -17,6 +17,8 @@ DESCRIPTION would be if all the nodes have been upgraded but the operation hasn't been marked as complete. + Only node pool upgrade operations support cancellation. + EXAMPLES To cancel an operation, run: diff --git a/gcloud/database-migration/connection-profiles/create/postgresql b/gcloud/database-migration/connection-profiles/create/postgresql index 89bfe5f31..61bdbf1a5 100644 --- a/gcloud/database-migration/connection-profiles/create/postgresql +++ b/gcloud/database-migration/connection-profiles/create/postgresql @@ -10,8 +10,9 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--role=ROLE] [--ca-certificate=CA_CERTIFICATE : --ssl-type=SSL_TYPE --client-certificate=CLIENT_CERTIFICATE --private-key=PRIVATE_KEY] - [--host=HOST --port=PORT --username=USERNAME (--password=PASSWORD - | --prompt-for-password) : --database=DATABASE] + [--host=HOST --port=PORT + : --database=DATABASE --username=USERNAME (--password=PASSWORD + | --prompt-for-password)] [--psc-service-attachment=PSC_SERVICE_ATTACHMENT | --static-ip-connectivity] [GCLOUD_WIDE_FLAG ...] @@ -132,23 +133,30 @@ FLAGS --port=PORT Network port of the database. - --username=USERNAME - Username that Database Migration Service uses to connect to the - database. Database Migration Service encrypts the value when storing - it. - --database=DATABASE The name of the specific database within the host. - Exactly one of these must be specified: + Authentication method. - --password=PASSWORD - Password for the user that Database Migration Service uses to connect - to the database. Database Migration Service encrypts the value when - storing it, and the field is not returned on request. + At most one of these can be specified: - --prompt-for-password - Prompt for the password used to connect to the database. + --username=USERNAME + Username that Database Migration Service uses to connect to the + database. Database Migration Service encrypts the value when storing + it. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + Exactly one of these must be specified: + + --password=PASSWORD + Password for the user that Database Migration Service uses to + connect to the database. Database Migration Service encrypts the + value when storing it, and the field is not returned on request. + + --prompt-for-password + Prompt for the password used to connect to the database. At most one of these can be specified: diff --git a/gcloud/dataflow/flex-template/build b/gcloud/dataflow/flex-template/build index ef3967225..50c4188ab 100644 --- a/gcloud/dataflow/flex-template/build +++ b/gcloud/dataflow/flex-template/build @@ -88,12 +88,11 @@ REQUIRED FLAGS --flex-template-base-image=FLEX_TEMPLATE_BASE_IMAGE Flex template base image to be used while building the container - image. Allowed choices are allowed labels (JAVA11, JAVA17, JAVA21, - PYTHON3, GO), supported distroless images (JAVA11_DISTROLESS, - JAVA17_DISTROLESS, JAVA21_DISTROLESS, GO_DISTROLESS), or full gcr.io - path of the specific version of the base image. For labels, we use - the latest base image version to build the container. You can also - provide a specific version from this link + image. Allowed choices are allowed labels (JAVA11/17/21/25, PYTHON3, + GO), supported distroless images (JAVA11/17/21/25_DISTROLESS, + GO_DISTROLESS), or full gcr.io path of the specific version of the + base image. For labels, we use the latest base image version to build + the container. You can also provide a specific version from this link https://gcr.io/dataflow-templates-base/ This flag argument must be specified if any of the other arguments in diff --git a/gcloud/emulators/spanner/help b/gcloud/emulators/spanner/help index 76bdff055..2718a0367 100644 --- a/gcloud/emulators/spanner/help +++ b/gcloud/emulators/spanner/help @@ -23,6 +23,9 @@ COMMANDS env-init Print the commands required to export Spanner emulator's env variables. + notices + Print third-party notices for the local Cloud Spanner emulator. + start Start a local Cloud Spanner emulator. diff --git a/gcloud/emulators/spanner/notices b/gcloud/emulators/spanner/notices new file mode 100644 index 000000000..5b86abf99 --- /dev/null +++ b/gcloud/emulators/spanner/notices @@ -0,0 +1,37 @@ +NAME + gcloud emulators spanner notices - print third-party notices for the local + Cloud Spanner emulator + +SYNOPSIS + gcloud emulators spanner notices [--use-docker] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Print third-party notices for the local Cloud Spanner emulator. + +EXAMPLES + To print third-party notices for the local Cloud Spanner emulator, run: + + $ gcloud emulators spanner notices + +FLAGS + --use-docker + Use the Cloud Spanner emulator docker image even if the platform has a + native binary available in the gcloud CLI. Currently we only provide a + native binary for Linux. For other systems, you must install Docker for + your platform before starting the emulator. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 emulators spanner notices + + $ gcloud beta emulators spanner notices + diff --git a/gcloud/filestore/instances/create b/gcloud/filestore/instances/create index fd410804d..8f1579e35 100644 --- a/gcloud/filestore/instances/create +++ b/gcloud/filestore/instances/create @@ -5,9 +5,10 @@ SYNOPSIS gcloud filestore instances create (INSTANCE : --zone=ZONE) --file-share=[capacity=CAPACITY],[name=NAME], [nfs-export-options=NFS-EXPORT-OPTIONS],[source-backup=SOURCE-BACKUP], - [source-backup-region=SOURCE-BACKUP-REGION] - --network=[connect-mode=CONNECT-MODE],[name=NAME], - [psc-endpoint-project=PSC-ENDPOINT-PROJECT], + [source-backup-region=SOURCE-BACKUP-REGION], + [source-backupdr-backup=SOURCE-BACKUPDR-BACKUP] + --network=[address-mode=ADDRESS-MODE],[connect-mode=CONNECT-MODE], + [name=NAME],[psc-endpoint-project=PSC-ENDPOINT-PROJECT], [reserved-ip-range=RESERVED-IP-RANGE] [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--location=LOCATION] @@ -25,30 +26,29 @@ DESCRIPTION Create a Filestore instance. EXAMPLES - The following command creates a Filestore instance named NAME with a single - volume. + To create a Basic HDD instance named my-instance in zone us-central1-c with + a 1TB volume named my_vol on the default network, run: - $ gcloud filestore instances create NAME --description=DESCRIPTION \ - --tier=TIER --protocol=PROTOCOL \ - --file-share=name=VOLUME_NAME,capacity=CAPACITY \ - --network=name=NETWORK_NAME,\ - reserved-ip-range=RESERVED_IP_RANGE,connect-mode=CONNECT_MODE,\ - psc-endpoint-project=PSC_ENDPOINT_PROJECT --zone=ZONE \ - --performance=max-iops-per-tb=MAX-IOPS-PER-TB \ - --kms-key=KMS-KEY --kms-keyring=KMS_KEYRING \ - --kms-location=KMS_LOCATION --kms-project=KMS_PROJECT \ - --flags-file=FLAGS_FILE --source-instance=SOURCE_INSTANCE + $ gcloud filestore instances create my-instance \ + --zone=us-central1-c --tier=BASIC_HDD \ + --file-share=name=my_vol,capacity=1TB --network=name=default - Example json configuration file: - { "--file-share": { "capacity": "61440", + To create an Enterprise instance named `my-ent-instance` in region `us-central1` with a 2TB volume named `my_vol` on network `my-network`, run: + + $ gcloud filestore instances create my-ent-instance \ + --zone=us-central1 --tier=ENTERPRISE \ + --file-share=name=my_vol,capacity=2TB --network=name=my-network + + To create an instance with specific NFS export options, you can use a JSON configuration file with `--flags-file`. For example, create a file named `config.json` with the following content: + { "--file-share": { "capacity": "1024", "name": "my_vol", "nfs-export-options": [ { "access-mode": "READ_WRITE", "ip-ranges": [ - "10.0.0.0/8", + "10.0.0.0/8" ], - "squash-mode": "NO_ROOT_SQUASH", + "squash-mode": "NO_ROOT_SQUASH" }, { "access-mode": "READ_ONLY", @@ -62,6 +62,11 @@ EXAMPLES ] } } + To create a Basic SSD instance named `my-nfs-instance` using the above configuration file, run: + $ gcloud filestore instances create my-nfs-instance \ + --zone=us-central1-c --tier=BASIC_SSD --network=name=default \ + --flags-file=config.json + POSITIONAL ARGUMENTS Instance resource - The instance to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -99,7 +104,7 @@ POSITIONAL ARGUMENTS ▸ set the property filestore/location. REQUIRED FLAGS - --file-share=[capacity=CAPACITY],[name=NAME],[nfs-export-options=NFS-EXPORT-OPTIONS],[source-backup=SOURCE-BACKUP],[source-backup-region=SOURCE-BACKUP-REGION] + --file-share=[capacity=CAPACITY],[name=NAME],[nfs-export-options=NFS-EXPORT-OPTIONS],[source-backup=SOURCE-BACKUP],[source-backup-region=SOURCE-BACKUP-REGION],[source-backupdr-backup=SOURCE-BACKUPDR-BACKUP] File share configuration for an instance. Specifying both name and capacity is required. @@ -169,9 +174,9 @@ REQUIRED FLAGS source-backup-region The region of the source backup. - --network=[connect-mode=CONNECT-MODE],[name=NAME],[psc-endpoint-project=PSC-ENDPOINT-PROJECT],[reserved-ip-range=RESERVED-IP-RANGE] + --network=[address-mode=ADDRESS-MODE],[connect-mode=CONNECT-MODE],[name=NAME],[psc-endpoint-project=PSC-ENDPOINT-PROJECT],[reserved-ip-range=RESERVED-IP-RANGE] Network configuration for a Cloud Filestore instance. Specifying - reserved-ip-range and connect-mode is optional. + reserved-ip-range, address-mode and connect-mode is optional. name The name of the Google Compute Engine VPC network to which the instance is connected. @@ -196,6 +201,9 @@ REQUIRED FLAGS Network connection mode used by instances. CONNECT_MODE must be one of: DIRECT_PEERING, PRIVATE_SERVICE_ACCESS or PRIVATE_SERVICE_CONNECT. + address-mode + Internet protocol version for which the instance has IP address + assigned. psc-endpoint-project Consumer service project in which the psc endpoint would be set up. This is optional, and only relevant in case the network is a shared diff --git a/gcloud/firestore/databases/clone b/gcloud/firestore/databases/clone new file mode 100644 index 000000000..c1aadc843 --- /dev/null +++ b/gcloud/firestore/databases/clone @@ -0,0 +1,138 @@ +NAME + gcloud firestore databases clone - clone a Google Cloud Firestore database + from another + +SYNOPSIS + gcloud firestore databases clone + --destination-database=DESTINATION_DATABASE + --snapshot-time=SNAPSHOT_TIME --source-database=SOURCE_DATABASE + [--tags=[KEY=VALUE,...]] + [--encryption-type=ENCRYPTION_TYPE : --kms-key-name=KMS_KEY_NAME] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To clone a database from another: + + $ gcloud firestore databases clone \ + --source-database=projects/PROJECT_ID/databases/\ + SOURCE_DATABASE --snapshot-time=2025-05-26T10:20:00.00Z \ + --destination-database=DATABASE_ID + + To clone to a CMEK-enabled database: + + $ gcloud firestore databases clone \ + --source-database=projects/PROJECT_ID/databases/\ + SOURCE_DATABASE --snapshot-time=2025-05-26T10:20:00.00Z \ + --destination-database=DATABASE_ID \ + --encryption-type=customer-managed-encryption \ + --kms-key-name=projects/PROJECT_ID/locations/LOCATION_ID/\ + keyRings/KEY_RING_ID/cryptoKeys/CRYPTO_KEY_ID + +REQUIRED FLAGS + --destination-database=DESTINATION_DATABASE + Destination database to clone to. Destination database will be created + in the same location as the source database. + + This value should be 4-63 characters. Valid characters are + /[a-z][0-9]-/ with first character a letter and the last a letter or a + number. Must not be UUID-like /[0-9a-f]8(-[0-9a-f]4)3-[0-9a-f]12/. + + Using "(default)" database ID is also allowed. + + For example, to clone to database testdb: + + $ gcloud firestore databases clone --destination-database=testdb + + --snapshot-time=SNAPSHOT_TIME + Snapshot time at which to clone. This must be a whole minute, in the + past, and not earlier than the source database's earliest_version_time. + Additionally, if older than one hour in the past, PITR must be enabled + on the source database. + + For example, to restore from snapshot 2025-05-26T10:20:00.00Z of source + database source-db: + + $ gcloud firestore databases clone \ + --source-database=projects/PROJECT_ID/databases/source-db \ + --snapshot-time=2025-05-26T10:20:00.00Z + + --source-database=SOURCE_DATABASE + The source database to clone from. + + For example, to clone from database source-db: + + $ gcloud firestore databases clone \ + --source-database=projects/PROJECT_ID/databases/source-db + +OPTIONAL FLAGS + --tags=[KEY=VALUE,...] + Tags to attach to the destination database. Example: + --tags=key1=value1,key2=value2 + + For example, to attach tags to a database: + + $ --tags=key1=value1,key2=value2 + + The encryption configuration of the new database being created from the + database. If not specified, the same encryption settings as the database + will be used. + + To create a CMEK-enabled database: + + $ gcloud firestore databases clone \ + --encryption-type=customer-managed-encryption \ + --kms-key-name=projects/PROJECT_ID/locations/LOCATION_ID/\ + keyRings/KEY_RING_ID/cryptoKeys/CRYPTO_KEY_ID + + To create a Google-default-encrypted database: + + $ gcloud firestore databases clone \ + --encryption-type=google-default-encryption + + To create a database using the same encryption settings as the database: + + $ gcloud firestore databases clone \ + --encryption-type=use-source-encryption + + --encryption-type=ENCRYPTION_TYPE + The encryption type of the destination database. ENCRYPTION_TYPE must + be one of: use-source-encryption, customer-managed-encryption, + google-default-encryption. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --kms-key-name=KMS_KEY_NAME + The resource ID of a Cloud KMS key. If set, the database created will + be a Customer-Managed Encryption Key (CMEK) database encrypted with + this key. This feature is allowlist only in initial launch. + + Only a key in the same location as this database is allowed to be + used for encryption. For Firestore's nam5 multi-region, this + corresponds to Cloud KMS location us. For Firestore's eur3 + multi-region, this corresponds to Cloud KMS location europe. See + https://cloud.google.com/kms/docs/locations. + + This value should be the KMS key resource ID in the format of + projects/{project_id}/locations/{kms_location}/keyRings/{key_ring}/cryptoKeys/{crypto_key}. + How to retrieve this resource ID is listed at + https://cloud.google.com/kms/docs/getting-resource-ids#getting_the_id_for_a_key_and_version. + + This flag must only be specified when encryption-type is + customer-managed-encryption. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 firestore databases clone + + $ gcloud beta firestore databases clone + diff --git a/gcloud/firestore/databases/help b/gcloud/firestore/databases/help index 78de077b8..8173fe0b7 100644 --- a/gcloud/firestore/databases/help +++ b/gcloud/firestore/databases/help @@ -16,6 +16,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + clone + Clone a Google Cloud Firestore database from another. + connection-string Prints the mongo connection string for the given Firestore database. diff --git a/gcloud/iam/workforce-pools/providers/keys/create b/gcloud/iam/workforce-pools/providers/keys/create index 7244bcf69..defe9947e 100644 --- a/gcloud/iam/workforce-pools/providers/keys/create +++ b/gcloud/iam/workforce-pools/providers/keys/create @@ -76,7 +76,7 @@ REQUIRED FLAGS --use=USE The purpose of the key. USE must be one of: encryption, - key-use-unspecified. + key-use-unspecified, signing. OPTIONAL FLAGS --async diff --git a/gcloud/looker/instances/update b/gcloud/looker/instances/update index 5547fd5d5..0dc8a1908 100644 --- a/gcloud/looker/instances/update +++ b/gcloud/looker/instances/update @@ -16,6 +16,8 @@ SYNOPSIS [domain=DOMAIN],[multiple-domains=MULTIPLE-DOMAINS]] [--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] + [--egress-enabled + --egress-fqdns=[EGRESS_FQDNS,...] --marketplace-enabled] [--maintenance-window-day=MAINTENANCE_WINDOW_DAY --maintenance-window-time=MAINTENANCE_WINDOW_TIME] [--oauth-client-id=OAUTH_CLIENT_ID @@ -178,6 +180,24 @@ FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + Controlled Egress - Controlled egress allows you to egress data from a + Looker (Google Cloud core) instance to a third party service provider. + + --egress-enabled + This specifies whether controlled egress is enabled on the Looker + instance. To disable controlled egress, use the --no-egress-enabled + flag. + + --egress-fqdns=[EGRESS_FQDNS,...] + List of FQDNs that are allowed to egress from the Looker instance. + Example: --egress-fqdns="github.com,my.salesforce.com". To clear all + egress FQDNs, use --egress-fqdns="". + + --marketplace-enabled + This specifies whether marketplace is enabled for controlled egress + on the Looker instance. To disable marketplace for controlled egress, + use the --no-marketplace-enabled flag. + Maintenance Window - Maintenance typically only takes place once every few months, and requires your instance to be restarted while updates are made, which disrupts service briefly. diff --git a/gcloud/lustre/instances/create b/gcloud/lustre/instances/create index 12e56f76f..2ce712b27 100644 --- a/gcloud/lustre/instances/create +++ b/gcloud/lustre/instances/create @@ -5,7 +5,7 @@ SYNOPSIS gcloud lustre instances create (INSTANCE : --location=LOCATION) --capacity-gib=CAPACITY_GIB --filesystem=FILESYSTEM --network=NETWORK --per-unit-storage-throughput=PER_UNIT_STORAGE_THROUGHPUT [--async] - [--description=DESCRIPTION] [--gke-support-enabled] + [--description=DESCRIPTION] [--gke-support-enabled] [--kms-key=KMS_KEY] [--labels=[LABELS,...]] [--placement-policy=PLACEMENT_POLICY] [--request-id=REQUEST_ID] [[--default-squash-mode=DEFAULT_SQUASH_MODE @@ -110,6 +110,13 @@ OPTIONAL FLAGS default, GKE clients are not supported. Deprecated. No longer required for GKE instance creation. + --kms-key=KMS_KEY + The Cloud KMS key name to use for data encryption. If not set, the + instance will use Google-managed encryption keys. If set, the instance + will use customer-managed encryption keys. The key must be in the same + region as the instance. The key format is: + projects/{project}/locations/{location}/keyRings/{key_ring}/cryptoKeys/{key} + --labels=[LABELS,...] Labels as key value pairs. diff --git a/gcloud/netapp/help b/gcloud/netapp/help index 795b0ea89..4ced79b18 100644 --- a/gcloud/netapp/help +++ b/gcloud/netapp/help @@ -34,6 +34,9 @@ GROUPS backup-vaults Create and manage Cloud NetApp Backup Vaults. + host-groups + Create and manage Cloud NetApp Host Groups. + kms-configs Create and manage Cloud NetApp Volumes KMS Configs. diff --git a/gcloud/netapp/host-groups/create b/gcloud/netapp/host-groups/create new file mode 100644 index 000000000..81c4daa93 --- /dev/null +++ b/gcloud/netapp/host-groups/create @@ -0,0 +1,97 @@ +NAME + gcloud netapp host-groups create - create a Cloud NetApp Host Group + +SYNOPSIS + gcloud netapp host-groups create (HOST_GROUP : --location=LOCATION) + --hosts=HOST,[HOST,...] --os-type=OS_TYPE --type=TYPE [--async] + [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Cloud NetApp Host Group. + +EXAMPLES + The following command creates a Host Group named NAME using the required + arguments: + + $ gcloud netapp host-groups create NAME --location=us-central1 \ + --type=ISCSI_INITIATOR --hosts=host1,host2 --os-type=LINUX + +POSITIONAL ARGUMENTS + Host group resource - The Host Group to create. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument host_group 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. + + HOST_GROUP + ID of the host_group or fully qualified identifier for the + host_group. + + To set the host_group attribute: + ▸ provide the argument host_group 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 host_group. + + To set the location attribute: + ▸ provide the argument host_group on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +REQUIRED FLAGS + --hosts=HOST,[HOST,...] + List of hosts in the host group. + + --os-type=OS_TYPE + String indicating the OS type of the hosts in the host group. The + supported values are: 'LINUX', 'WINDOWS', 'ESXI'. OS_TYPE must be one + of: LINUX, WINDOWS, ESXI. + + --type=TYPE + String indicating the type of host group. The supported values are: + 'ISCSI_INITIATOR'. TYPE must be (only one value is supported): + ISCSI_INITIATOR. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A description of the Cloud NetApp Host Group + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha netapp host-groups create + + $ gcloud beta netapp host-groups create + diff --git a/gcloud/netapp/host-groups/delete b/gcloud/netapp/host-groups/delete new file mode 100644 index 000000000..f5e88d8aa --- /dev/null +++ b/gcloud/netapp/host-groups/delete @@ -0,0 +1,74 @@ +NAME + gcloud netapp host-groups delete - delete a Cloud NetApp Host Group + +SYNOPSIS + gcloud netapp host-groups delete (HOST_GROUP : --location=LOCATION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Cloud NetApp Host Group. + +EXAMPLES + The following command deletes a Host Group named NAME: + + $ gcloud netapp host-groups delete NAME --location=us-central1 + + To delete a Host Group named NAME asynchronously, run the following + command: + + $ gcloud netapp host-groups delete NAME --location=us-central1 \ + --async + +POSITIONAL ARGUMENTS + Host group resource - The Host Group 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 host_group 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. + + HOST_GROUP + ID of the host_group or fully qualified identifier for the + host_group. + + To set the host_group attribute: + ▸ provide the argument host_group 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 host_group. + + To set the location attribute: + ▸ provide the argument host_group on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha netapp host-groups delete + + $ gcloud beta netapp host-groups delete + diff --git a/gcloud/netapp/host-groups/describe b/gcloud/netapp/host-groups/describe new file mode 100644 index 000000000..2160d6495 --- /dev/null +++ b/gcloud/netapp/host-groups/describe @@ -0,0 +1,64 @@ +NAME + gcloud netapp host-groups describe - describe a Cloud NetApp Host Group + +SYNOPSIS + gcloud netapp host-groups describe (HOST_GROUP : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Cloud NetApp Host Group. + +EXAMPLES + The following command describes a Host Group named NAME in the given + location: + + $ gcloud netapp host-groups describe NAME --location=us-central1 + +POSITIONAL ARGUMENTS + Host group resource - The Host Group 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 host_group 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. + + HOST_GROUP + ID of the host_group or fully qualified identifier for the + host_group. + + To set the host_group attribute: + ▸ provide the argument host_group 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 host_group. + + To set the location attribute: + ▸ provide the argument host_group on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha netapp host-groups describe + + $ gcloud beta netapp host-groups describe + diff --git a/gcloud/netapp/host-groups/help b/gcloud/netapp/host-groups/help new file mode 100644 index 000000000..456c0a7e4 --- /dev/null +++ b/gcloud/netapp/host-groups/help @@ -0,0 +1,39 @@ +NAME + gcloud netapp host-groups - create and manage Cloud NetApp Host Groups + +SYNOPSIS + gcloud netapp host-groups COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create and manage Cloud NetApp Host Groups. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Cloud NetApp Host Group. + + delete + Delete a Cloud NetApp Host Group. + + describe + Describe a Cloud NetApp Host Group. + + list + List Cloud NetApp Host Groups. + + update + Update a Cloud NetApp Host Group. + +NOTES + These variants are also available: + + $ gcloud alpha netapp host-groups + + $ gcloud beta netapp host-groups + diff --git a/gcloud/netapp/host-groups/list b/gcloud/netapp/host-groups/list new file mode 100644 index 000000000..490612c22 --- /dev/null +++ b/gcloud/netapp/host-groups/list @@ -0,0 +1,84 @@ +NAME + gcloud netapp host-groups list - list Cloud NetApp Host Groups + +SYNOPSIS + gcloud netapp host-groups list [--location=LOCATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Lists Cloud NetApp Host Groups. + +EXAMPLES + The following command lists all Host Groups in the given location: + + $ gcloud netapp host-groups list --location=us-central1 + +FLAGS + Location resource - The location in which to list Host Groups. 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; + ◆ uses all locations by default. with a fully specified name; + ◆ set the property netapp/location 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; + ▸ uses all locations by default.; + ▸ set the property netapp/location. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha netapp host-groups list + + $ gcloud beta netapp host-groups list + diff --git a/gcloud/netapp/host-groups/update b/gcloud/netapp/host-groups/update new file mode 100644 index 000000000..60f40dd6b --- /dev/null +++ b/gcloud/netapp/host-groups/update @@ -0,0 +1,108 @@ +NAME + gcloud netapp host-groups update - update a Cloud NetApp Host Group + +SYNOPSIS + gcloud netapp host-groups update (HOST_GROUP : --location=LOCATION) + [--async] [--description=DESCRIPTION] [--hosts=HOST,[HOST,...]] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Cloud NetApp Host Group and its specified parameters. + +EXAMPLES + The following command updates a Host Group named NAME and its specified + parameters: + + $ gcloud netapp host-groups update NAME --location=us-central1 \ + --description="new description" --hosts="host3,host4" \ + --update-labels=key2=val2 + +POSITIONAL ARGUMENTS + Host group resource - The Host Group 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 host_group 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. + + HOST_GROUP + ID of the host_group or fully qualified identifier for the + host_group. + + To set the host_group attribute: + ▸ provide the argument host_group 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 host_group. + + To set the location attribute: + ▸ provide the argument host_group on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property netapp/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + A description of the Cloud NetApp Host Group + + --hosts=HOST,[HOST,...] + List of hosts in the host group. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud netapp host-groups update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud netapp host-groups update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha netapp host-groups update + + $ gcloud beta netapp host-groups update + diff --git a/gcloud/netapp/storage-pools/create b/gcloud/netapp/storage-pools/create index e7184da6a..81abe398f 100644 --- a/gcloud/netapp/storage-pools/create +++ b/gcloud/netapp/storage-pools/create @@ -11,7 +11,7 @@ SYNOPSIS [--kms-config=KMS_CONFIG] [--labels=[KEY=VALUE,...]] [--qos-type=QOS_TYPE] [--replica-zone=REPLICA_ZONE] [--total-iops=TOTAL_IOPS] [--total-throughput=TOTAL_THROUGHPUT] - [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] + [--type=TYPE] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Creates a Storage Pool to contain Volumes with a specified Service Level @@ -201,6 +201,16 @@ OPTIONAL FLAGS The total throughput of the Storage Pool in MiB/s or GiB/s units. If no throughput unit is specified, MiB/s is assumed. + --type=TYPE + The type of the Storage Pool. FILE pools support file-based volumes + only. UNIFIED pools support both file and block volumes. TYPE must be + one of: + + file + File-based volumes only (default). + unified + Both file and block volumes. + --zone=ZONE String indicating active zone of the Storage Pool diff --git a/gcloud/netapp/volumes/create b/gcloud/netapp/volumes/create index 5111bef78..1968be663 100644 --- a/gcloud/netapp/volumes/create +++ b/gcloud/netapp/volumes/create @@ -8,6 +8,8 @@ SYNOPSIS [--backup-config=[backup-policies=BACKUP-POLICIES], [backup-vault=BACKUP-VAULT], [enable-scheduled-backups=ENABLE-SCHEDULED-BACKUPS]] + [--block-devices=[host-groups=HOST-GROUPS], + [name=NAME],[os-type=OS-TYPE],[size-gib=SIZE-GIB]] [--cache-parameters=[cache-config=CACHE-CONFIG], [enable-global-file-lock=ENABLE-GLOBAL-FILE-LOCK], [peer-cluster-name=PEER-CLUSTER-NAME], @@ -158,6 +160,24 @@ OPTIONAL FLAGS enable-scheduled-backups is a Boolean value indicating whether or not scheduled backups are enabled on the volume. + --block-devices=[host-groups=HOST-GROUPS],[name=NAME],[os-type=OS-TYPE],[size-gib=SIZE-GIB] + A block device to be created with the volume. + + This flag can be repeated to specify multiple block devices. + + The following keys are available: + name + A user-defined name for the block device. + host-groups + A comma-separated list of host groups that can mount the block + volume. + os-type + The OS type of the volume. Allowed values are OS_TYPE_UNSPECIFIED, + LINUX, WINDOWS. + size-gib + The size of the block device in GiB. Note that this value is + ignored during volume creation and is system-managed. + --cache-parameters=[cache-config=CACHE-CONFIG],[enable-global-file-lock=ENABLE-GLOBAL-FILE-LOCK],[peer-cluster-name=PEER-CLUSTER-NAME],[peer-ip-addresses=PEER-IP-ADDRESSES],[peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME] Cache Parameters contains cache parameters of a volume. diff --git a/gcloud/netapp/volumes/update b/gcloud/netapp/volumes/update index 83d78a98a..b480cf2d7 100644 --- a/gcloud/netapp/volumes/update +++ b/gcloud/netapp/volumes/update @@ -6,6 +6,8 @@ SYNOPSIS [--backup-config=[backup-policies=BACKUP-POLICIES], [backup-vault=BACKUP-VAULT], [enable-scheduled-backups=ENABLE-SCHEDULED-BACKUPS]] + [--block-devices=[host-groups=HOST-GROUPS], + [name=NAME],[os-type=OS-TYPE],[size-gib=SIZE-GIB]] [--cache-parameters=[cache-config=CACHE-CONFIG], [enable-global-file-lock=ENABLE-GLOBAL-FILE-LOCK], [peer-cluster-name=PEER-CLUSTER-NAME], @@ -105,6 +107,24 @@ FLAGS enable-scheduled-backups is a Boolean value indicating whether or not scheduled backups are enabled on the volume. + --block-devices=[host-groups=HOST-GROUPS],[name=NAME],[os-type=OS-TYPE],[size-gib=SIZE-GIB] + A block device to be created with the volume. + + This flag can be repeated to specify multiple block devices. + + The following keys are available: + name + A user-defined name for the block device. + host-groups + A comma-separated list of host groups that can mount the block + volume. + os-type + The OS type of the volume. Allowed values are OS_TYPE_UNSPECIFIED, + LINUX, WINDOWS. + size-gib + The size of the block device in GiB. Note that this value is + ignored during volume creation and is system-managed. + --cache-parameters=[cache-config=CACHE-CONFIG],[enable-global-file-lock=ENABLE-GLOBAL-FILE-LOCK],[peer-cluster-name=PEER-CLUSTER-NAME],[peer-ip-addresses=PEER-IP-ADDRESSES],[peer-svm-name=PEER-SVM-NAME],[peer-volume-name=PEER-VOLUME-NAME] Cache Parameters contains cache parameters of a volume. diff --git a/gcloud/network-connectivity/spokes/linked-producer-vpc-network/create b/gcloud/network-connectivity/spokes/linked-producer-vpc-network/create index 8d983fb10..69bfd02d5 100644 --- a/gcloud/network-connectivity/spokes/linked-producer-vpc-network/create +++ b/gcloud/network-connectivity/spokes/linked-producer-vpc-network/create @@ -17,10 +17,10 @@ EXAMPLES $ gcloud network-connectivity spokes linked-producer-vpc-network \ create myspoke \ - --hub="https://www.googleapis.com/networkconnectivity/v1/project\ - s/my-project/locations/global/hubs/my-hub" --global \ - --network="https://www.googleapis.com/compute/v1/projects/my-pro\ - ject/global/networks/my-vpc" --peering="my-peering-name" \ + --hub=https://www.googleapis.com/networkconnectivity/v1/\ + projects/my-project/locations/global/hubs/my-hub --global \ + --network=https://www.googleapis.com/compute/v1/projects/\ + my-project/global/networks/my-vpc --peering=my-peering-name POSITIONAL ARGUMENTS Spoke resource - Name of the spoke to create. This represents a Cloud diff --git a/gcloud/network-connectivity/spokes/linked-vpc-network/create b/gcloud/network-connectivity/spokes/linked-vpc-network/create index 10fc6768a..e18f4b870 100644 --- a/gcloud/network-connectivity/spokes/linked-vpc-network/create +++ b/gcloud/network-connectivity/spokes/linked-vpc-network/create @@ -17,10 +17,10 @@ EXAMPLES $ gcloud network-connectivity spokes linked-vpc-network create \ myspoke \ - --hub="https://www.googleapis.com/networkconnectivity/v1/project\ - s/my-project/locations/global/hubs/my-hub" --global \ - --vpc-network="https://www.googleapis.com/compute/v1/projects/my\ - -project/global/networks/my-vpc" + --hub=https://www.googleapis.com/networkconnectivity/v1/\ + projects/my-project/locations/global/hubs/my-hub --global \ + --vpc-network=https://www.googleapis.com/compute/v1/projects/\ + my-project/global/networks/my-vpc POSITIONAL ARGUMENTS Spoke resource - Name of the spoke to create. This represents a Cloud diff --git a/gcloud/network-management/help b/gcloud/network-management/help index 0ecf4f322..f86fe6c94 100644 --- a/gcloud/network-management/help +++ b/gcloud/network-management/help @@ -25,9 +25,7 @@ GROUPS Manage the VPC Flow Logs configurations. NOTES - These variants are also available: - - $ gcloud alpha network-management + This variant is also available: $ gcloud beta network-management diff --git a/gcloud/network-security/intercept-endpoint-groups/create b/gcloud/network-security/intercept-endpoint-groups/create index a96899252..53e52e731 100644 --- a/gcloud/network-security/intercept-endpoint-groups/create +++ b/gcloud/network-security/intercept-endpoint-groups/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud network-security intercept-endpoint-groups create (INTERCEPT_ENDPOINT_GROUP : --location=LOCATION) (--intercept-deployment-group=INTERCEPT_DEPLOYMENT_GROUP - : --intercept-deployment-group-location=INTERCEPT_DEPLOYMENT_GROUP_LOCATION) + : --intercept-deployment-group-location=INTERCEPT_DEPLOYMENT_GROUP_LOCATION --intercept-deployment-group-project=INTERCEPT_DEPLOYMENT_GROUP_PROJECT) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] @@ -83,14 +83,7 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Intercept deployment group resource - Intercept Deployment Group. 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 --intercept-deployment-group on the command line - with a fully specified name; - ◆ provide the argument --project on the command line; - ◆ set the property core/project. + resource. This must be specified. @@ -117,6 +110,19 @@ REQUIRED FLAGS ▸ provide the argument INTERCEPT_ENDPOINT_GROUP on the command line with a fully specified name. + --intercept-deployment-group-project=INTERCEPT_DEPLOYMENT_GROUP_PROJECT + Project of the intercept deployment group. + + To set the project attribute: + ▸ provide the argument --intercept-deployment-group on the command + line with a fully specified name; + ▸ provide the argument --intercept-deployment-group-project on the + command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project; + ▸ provide the argument INTERCEPT_ENDPOINT_GROUP on the command line + with a fully specified name. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/network-security/mirroring-endpoint-groups/create b/gcloud/network-security/mirroring-endpoint-groups/create index d2482a1fe..c2fe5e8a6 100644 --- a/gcloud/network-security/mirroring-endpoint-groups/create +++ b/gcloud/network-security/mirroring-endpoint-groups/create @@ -6,7 +6,7 @@ SYNOPSIS gcloud network-security mirroring-endpoint-groups create (MIRRORING_ENDPOINT_GROUP : --location=LOCATION) ([--mirroring-deployment-group=MIRRORING_DEPLOYMENT_GROUP - : --mirroring-deployment-group-location=MIRRORING_DEPLOYMENT_GROUP_LOCATION]) + : --mirroring-deployment-group-location=MIRRORING_DEPLOYMENT_GROUP_LOCATION --mirroring-deployment-group-project=MIRRORING_DEPLOYMENT_GROUP_PROJECT]) [--async] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--max-wait=MAX_WAIT; default="20m"] [GCLOUD_WIDE_FLAG ...] @@ -85,14 +85,7 @@ REQUIRED FLAGS Mirroring deployment group resource - Mirroring Deployment Group. 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 --mirroring-deployment-group on the command - line with a fully specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. + resource. --mirroring-deployment-group=MIRRORING_DEPLOYMENT_GROUP ID of the mirroring deployment group or fully qualified identifier @@ -117,6 +110,19 @@ REQUIRED FLAGS ▫ provide the argument MIRRORING_ENDPOINT_GROUP on the command line with a fully specified name. + --mirroring-deployment-group-project=MIRRORING_DEPLOYMENT_GROUP_PROJECT + Project of the mirroring deployment group. + + To set the project attribute: + ▫ provide the argument --mirroring-deployment-group on the + command line with a fully specified name; + ▫ provide the argument --mirroring-deployment-group-project on + the command line; + ▫ provide the argument --project on the command line; + ▫ set the property core/project; + ▫ provide the argument MIRRORING_ENDPOINT_GROUP on the command + line with a fully specified name. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/network-services/multicast-domain-activations/create b/gcloud/network-services/multicast-domain-activations/create index 80882ecc3..f31a07538 100644 --- a/gcloud/network-services/multicast-domain-activations/create +++ b/gcloud/network-services/multicast-domain-activations/create @@ -6,7 +6,8 @@ SYNOPSIS gcloud network-services multicast-domain-activations create (MULTICAST_DOMAIN_ACTIVATION : --location=LOCATION) --multicast-domain=MULTICAST_DOMAIN [--async] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] + [--description=DESCRIPTION] [--disable-placement-policy] + [--labels=[KEY=VALUE,...]] [--aggr-egress-pps=AGGR_EGRESS_PPS : --aggr-ingress-pps=AGGR_INGRESS_PPS --avg-packet-size=AVG_PACKET_SIZE @@ -24,12 +25,12 @@ EXAMPLES location 'zone'. $ gcloud network-services multicast-domain-activations create \ - my-multicast-group-definition --multicast-domain=path-to-md \ + my-multicast-domain-activation --multicast-domain=path-to-md \ --location=zone POSITIONAL ARGUMENTS - Multicast domain activation resource - Name of the multicast group - definition to be created. The arguments in this group can be used to + Multicast domain activation resource - Name of the multicast domain + activation to be created. The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways. @@ -72,6 +73,10 @@ OPTIONAL FLAGS --description=DESCRIPTION The description for the multicast domain activation. + --disable-placement-policy + True to disable the use of the placement policy for this multicast + domain activation. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/pubsub/snapshots/create b/gcloud/pubsub/snapshots/create index 9f15ad7fc..9c6c591c5 100644 --- a/gcloud/pubsub/snapshots/create +++ b/gcloud/pubsub/snapshots/create @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud pubsub snapshots create SNAPSHOT [SNAPSHOT ...] --subscription=SUBSCRIPTION [--labels=[KEY=VALUE,...]] - [--subscription-project=SUBSCRIPTION_PROJECT] [GCLOUD_WIDE_FLAG ...] + [--subscription-project=SUBSCRIPTION_PROJECT] [--tags=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Creates one or more Cloud Pub/Sub snapshots. @@ -36,6 +37,11 @@ OPTIONAL FLAGS The name of the project the provided subscription belongs to. If not set, it defaults to the currently selected cloud project. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. Example: + 123/environment=production,123/costCenter=marketing + 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/pubsub/subscriptions/create b/gcloud/pubsub/subscriptions/create index c39209f2a..c7bb7f6e1 100644 --- a/gcloud/pubsub/subscriptions/create +++ b/gcloud/pubsub/subscriptions/create @@ -10,7 +10,7 @@ SYNOPSIS [--labels=[KEY=VALUE,...]] [--message-filter=MESSAGE_FILTER] [--message-retention-duration=MESSAGE_RETENTION_DURATION] [--message-transforms-file=MESSAGE_TRANSFORMS_FILE] - [--retain-acked-messages] + [--retain-acked-messages] [--tags=[KEY=VALUE,...]] [[--bigquery-table=BIGQUERY_TABLE : --bigquery-service-account-email=BIGQUERY_SERVICE_ACCOUNT_EMAIL --drop-unknown-fields --write-metadata --use-table-schema @@ -139,6 +139,11 @@ OPTIONAL FLAGS retained by default. Use --no-retain-acked-messages to disable this flag. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. Example: + 123/environment=production,123/costCenter=marketing + At most one of these can be specified: BigQuery Config Options. The Cloud Pub/Sub service account associated diff --git a/gcloud/pubsub/topics/create b/gcloud/pubsub/topics/create index b21d7775b..cd0003db2 100644 --- a/gcloud/pubsub/topics/create +++ b/gcloud/pubsub/topics/create @@ -5,6 +5,7 @@ SYNOPSIS gcloud pubsub topics create TOPIC [TOPIC ...] [--labels=[KEY=VALUE,...]] [--message-retention-duration=MESSAGE_RETENTION_DURATION] [--message-transforms-file=MESSAGE_TRANSFORMS_FILE] + [--tags=[KEY=VALUE,...]] [--ingestion-log-severity=INGESTION_LOG_SEVERITY --aws-msk-ingestion-aws-role-arn=AWS_MSK_INGESTION_AWS_ROLE_ARN --aws-msk-ingestion-cluster-arn=AWS_MSK_INGESTION_CLUSTER_ARN @@ -74,6 +75,11 @@ FLAGS --message-transforms-file=MESSAGE_TRANSFORMS_FILE Path to YAML or JSON file containing message transforms. + --tags=[KEY=VALUE,...] + List of tags KEY=VALUE pairs to bind. Each item must be expressed as + =. Example: + 123/environment=production,123/costCenter=marketing + Following flags are for specifying the data source settings for an import topic diff --git a/gcloud/run/deploy b/gcloud/run/deploy index d1b653839..9e597a0df 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -721,13 +721,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. + Clears all existing network tags from the Cloud Run service. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + service. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/run/jobs/create b/gcloud/run/jobs/create index 50c3b29d5..b0c3f4c57 100644 --- a/gcloud/run/jobs/create +++ b/gcloud/run/jobs/create @@ -347,8 +347,8 @@ FLAGS network settings, use --clear-network. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the Cloud - Run job. To clear existing tags, use --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + job. To clear existing tags, use --clear-network-tags. --subnet=SUBNET The VPC subnetwork that the Cloud Run job will get IPs from. The diff --git a/gcloud/run/jobs/deploy b/gcloud/run/jobs/deploy index d9a0a3a75..876dc7e01 100644 --- a/gcloud/run/jobs/deploy +++ b/gcloud/run/jobs/deploy @@ -387,11 +387,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run job. + Clears all existing network tags from the Cloud Run job. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run job. To clear existing tags, use --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + job. To clear existing tags, use --clear-network-tags. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/run/jobs/update b/gcloud/run/jobs/update index 5b26e0353..2a8ac8e8b 100644 --- a/gcloud/run/jobs/update +++ b/gcloud/run/jobs/update @@ -420,11 +420,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run job. + Clears all existing network tags from the Cloud Run job. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run job. To clear existing tags, use --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + job. To clear existing tags, use --clear-network-tags. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/run/multi-region-services/update b/gcloud/run/multi-region-services/update index ad50e29c2..faa7ae0a4 100644 --- a/gcloud/run/multi-region-services/update +++ b/gcloud/run/multi-region-services/update @@ -569,13 +569,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. + Clears all existing network tags from the Cloud Run service. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + service. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/run/services/update b/gcloud/run/services/update index 7504e98b9..9bae0ac1b 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -595,13 +595,11 @@ FLAGS At most one of these can be specified: --clear-network-tags - Clears all existing Compute Engine tags from the Cloud Run - service. + Clears all existing network tags from the Cloud Run service. --network-tags=[TAG,...] - Applies the given Compute Engine tags (comma separated) to the - Cloud Run service. To clear existing tags, use - --clear-network-tags. + Applies the given network tags (comma separated) to the Cloud Run + service. To clear existing tags, use --clear-network-tags. At most one of these can be specified: diff --git a/gcloud/service-extensions/help b/gcloud/service-extensions/help index 7bbd261f6..dc1163b43 100644 --- a/gcloud/service-extensions/help +++ b/gcloud/service-extensions/help @@ -18,6 +18,9 @@ GROUPS authz-extensions Manage Service Extensions AuthzExtension resources. + lb-edge-extensions + Manage Service Extensions LbEdgeExtension resources. + lb-route-extensions Manage Service Extensions LbRouteExtension resources. diff --git a/gcloud/service-extensions/lb-edge-extensions/delete b/gcloud/service-extensions/lb-edge-extensions/delete new file mode 100644 index 000000000..ecb88a2f5 --- /dev/null +++ b/gcloud/service-extensions/lb-edge-extensions/delete @@ -0,0 +1,72 @@ +NAME + gcloud service-extensions lb-edge-extensions delete - delete an + LbEdgeExtension resource + +SYNOPSIS + gcloud service-extensions lb-edge-extensions delete + (LB_EDGE_EXTENSION : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete the specified LbEdgeExtension resource. + +EXAMPLES + To delete a global LbEdgeExtension resource named my-edge-extension, run: + + $ gcloud service-extensions lb-edge-extensions delete \ + my-edge-extension --location=global + +POSITIONAL ARGUMENTS + LbEdgeExtension resource - The ID of the deleted LbEdgeExtension resource. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument lb_edge_extension on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + LB_EDGE_EXTENSION + ID of the LbEdgeExtension or fully qualified identifier for the + LbEdgeExtension. + + To set the lb_edge_extension attribute: + ▸ provide the argument lb_edge_extension on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Cloud region in which the resource is located. + + To set the location attribute: + ▸ provide the argument lb_edge_extension on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + This variant is also available: + + $ gcloud beta service-extensions lb-edge-extensions delete + diff --git a/gcloud/service-extensions/lb-edge-extensions/describe b/gcloud/service-extensions/lb-edge-extensions/describe new file mode 100644 index 000000000..8aecb14f9 --- /dev/null +++ b/gcloud/service-extensions/lb-edge-extensions/describe @@ -0,0 +1,67 @@ +NAME + gcloud service-extensions lb-edge-extensions describe - describe an + LbEdgeExtension resource + +SYNOPSIS + gcloud service-extensions lb-edge-extensions describe + (LB_EDGE_EXTENSION : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details about an LbEdgeExtension resource. + +EXAMPLES + To show details about the global LbEdgeExtension resource named + my-edge-extension. + + $ gcloud service-extensions lb-edge-extensions describe \ + my-edge-extension --location=global + +POSITIONAL ARGUMENTS + LbEdgeExtension resource - The ID of the LbEdgeExtension resource. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument lb_edge_extension on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + LB_EDGE_EXTENSION + ID of the LbEdgeExtension or fully qualified identifier for the + LbEdgeExtension. + + To set the lb_edge_extension attribute: + ▸ provide the argument lb_edge_extension on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Cloud region in which the resource is located. + + To set the location attribute: + ▸ provide the argument lb_edge_extension on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + This variant is also available: + + $ gcloud beta service-extensions lb-edge-extensions describe + diff --git a/gcloud/service-extensions/lb-edge-extensions/help b/gcloud/service-extensions/lb-edge-extensions/help new file mode 100644 index 000000000..5c37c8edd --- /dev/null +++ b/gcloud/service-extensions/lb-edge-extensions/help @@ -0,0 +1,35 @@ +NAME + gcloud service-extensions lb-edge-extensions - manage Service Extensions + LbEdgeExtension resources + +SYNOPSIS + gcloud service-extensions lb-edge-extensions COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Service Extensions LbEdgeExtension resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + Delete an LbEdgeExtension resource. + + describe + Describe an LbEdgeExtension resource. + + import + Import an LbEdgeExtension resource. + + list + List LbEdgeExtension resources. + +NOTES + This variant is also available: + + $ gcloud beta service-extensions lb-edge-extensions + diff --git a/gcloud/service-extensions/lb-edge-extensions/import b/gcloud/service-extensions/lb-edge-extensions/import new file mode 100644 index 000000000..1e93622fa --- /dev/null +++ b/gcloud/service-extensions/lb-edge-extensions/import @@ -0,0 +1,84 @@ +NAME + gcloud service-extensions lb-edge-extensions import - import an + LbEdgeExtension resource + +SYNOPSIS + gcloud service-extensions lb-edge-extensions import + (LB_EDGE_EXTENSION : --location=LOCATION) [--async] [--source=SOURCE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Import an LbEdgeExtension resource defined in a YAML file. + +EXAMPLES + To import a global LbEdgeExtension resource named my-edge-extension from a + YAML file, run: + + $ gcloud service-extensions lb-edge-extensions import \ + my-edge-extension --source=my-edge-extension.yaml \ + --location=global + +POSITIONAL ARGUMENTS + LbEdgeExtension resource - The ID of the new or updated LbEdgeExtension + resource. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument lb_edge_extension on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + LB_EDGE_EXTENSION + ID of the LbEdgeExtension or fully qualified identifier for the + LbEdgeExtension. + + To set the lb_edge_extension attribute: + ▸ provide the argument lb_edge_extension on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Cloud region in which the resource is located. + + To set the location attribute: + ▸ provide the argument lb_edge_extension on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --source=SOURCE + Path to a YAML file containing the configuration export data. The YAML + file must not contain any output-only fields. Alternatively, you may + omit this flag to read from standard input. For a schema describing the + export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + + $CLOUDSDKROOT is can be obtained with the following command: + + $ gcloud info --format='value(installation.sdk_root)' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + This variant is also available: + + $ gcloud beta service-extensions lb-edge-extensions import + diff --git a/gcloud/service-extensions/lb-edge-extensions/list b/gcloud/service-extensions/lb-edge-extensions/list new file mode 100644 index 000000000..8459bb4d8 --- /dev/null +++ b/gcloud/service-extensions/lb-edge-extensions/list @@ -0,0 +1,86 @@ +NAME + gcloud service-extensions lb-edge-extensions list - list LbEdgeExtension + resources + +SYNOPSIS + gcloud service-extensions lb-edge-extensions list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all LbEdgeExtension resources in the specified location of the current + project. + +EXAMPLES + To list all global LbEdgeExtension resources in the current project, run: + + $ gcloud service-extensions lb-edge-extensions list --location=global + +REQUIRED FLAGS + Location resource - The parent location. This represents a Cloud resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/networking + +NOTES + This variant is also available: + + $ gcloud beta service-extensions lb-edge-extensions list + diff --git a/gcloud/sql/backups/restore b/gcloud/sql/backups/restore index 5f544ef56..6a7af01e8 100644 --- a/gcloud/sql/backups/restore +++ b/gcloud/sql/backups/restore @@ -374,8 +374,8 @@ OPTIONAL FLAGS here: https://cloud.google.com/sql/docs/quotas#storage_limits --storage-type=STORAGE_TYPE - The storage type for the instance. The default is SSD. STORAGE_TYPE - must be one of: SSD, HDD, HYPERDISK_BALANCED. + The storage type for the instance, determined by the selected machine + type. STORAGE_TYPE must be one of: SSD, HDD, HYPERDISK_BALANCED. --tier=TIER, -t TIER Machine type for a shared-core instance e.g. db-g1-small. For all other diff --git a/gcloud/sql/import/bak b/gcloud/sql/import/bak index 8f83360c4..5ba623a10 100644 --- a/gcloud/sql/import/bak +++ b/gcloud/sql/import/bak @@ -59,7 +59,7 @@ OPTIONAL FLAGS Whether or not to decrypt the imported encrypted BAK file. --no-recovery - Whether or not the SQL Server import is execueted with NORECOVERY + Whether or not the SQL Server import is executed with NORECOVERY keyword. --recovery-only diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index 03a5856f7..73344ba69 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -593,8 +593,8 @@ FLAGS here: https://cloud.google.com/sql/docs/quotas#storage_limits --storage-type=STORAGE_TYPE - The storage type for the instance. The default is SSD. STORAGE_TYPE - must be one of: SSD, HDD, HYPERDISK_BALANCED. + The storage type for the instance, determined by the selected machine + type. STORAGE_TYPE must be one of: SSD, HDD, HYPERDISK_BALANCED. --tags=TAG=VALUE,[TAG=VALUE,...] Comma-separated list of tags to set on the instance. Use an equals diff --git a/gcloud/sql/instances/help b/gcloud/sql/instances/help index c4f91ef04..80242bd74 100644 --- a/gcloud/sql/instances/help +++ b/gcloud/sql/instances/help @@ -51,6 +51,10 @@ COMMANDS patch Updates the settings of a Cloud SQL instance. + point-in-time-restore + Performs a point in time restore for a Cloud SQL instance managed by + Google Cloud Backup and Disaster Recovery (DR) Service. + pre-check-major-version-upgrade Performs pre-checks for a major version upgrade of a Cloud SQL instance. diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index 1e3fd135e..a92923096 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -58,7 +58,7 @@ SYNOPSIS [--[no-]storage-auto-increase] [--storage-provisioned-iops=STORAGE_PROVISIONED_IOPS] [--storage-provisioned-throughput=STORAGE_PROVISIONED_THROUGHPUT] - [--storage-size=STORAGE_SIZE] + [--storage-size=STORAGE_SIZE] [--storage-type=STORAGE_TYPE] [--switch-transaction-logs-to-cloud-storage] [--threads-per-core=THREADS_PER_CORE] [--tier=TIER, -t TIER] [--time-zone=TIME_ZONE] [--upgrade-sql-network-architecture] @@ -529,6 +529,10 @@ FLAGS of GB. The default is 10GB. Information on storage limits can be found here: https://cloud.google.com/sql/docs/quotas#storage_limits + --storage-type=STORAGE_TYPE + The storage type for the instance, determined by the selected machine + type. STORAGE_TYPE must be one of: SSD, HDD, HYPERDISK_BALANCED. + --switch-transaction-logs-to-cloud-storage Switches the location of the transaction logs used for PITR from disk to Cloud Storage. diff --git a/gcloud/sql/instances/point-in-time-restore b/gcloud/sql/instances/point-in-time-restore new file mode 100644 index 000000000..aa6e3134d --- /dev/null +++ b/gcloud/sql/instances/point-in-time-restore @@ -0,0 +1,83 @@ +NAME + gcloud sql instances point-in-time-restore - performs a point in time + restore for a Cloud SQL instance managed by Google Cloud Backup and + Disaster Recovery Service + +SYNOPSIS + gcloud sql instances point-in-time-restore DATASOURCE TARGET POINT_IN_TIME + [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] [--async] + [--preferred-secondary-zone=PREFERRED_SECONDARY_ZONE] + [--preferred-zone=PREFERRED_ZONE] [--private-network=PRIVATE_NETWORK] + [--restore-database-names=RESTORE_DATABASE_NAMES] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud sql instances point-in-time-restore performs a point in time restore + for a Cloud SQL instance managed by Google Cloud Backup and Disaster + Recovery (DR) Service. + +EXAMPLES + To perform a point in time restore from an earlier point in time: + + $ gcloud sql instances point-in-time-restore datasource \ + target-instance '2012-11-15T16:19:00.094Z' + +POSITIONAL ARGUMENTS + DATASOURCE + The Google Cloud Backup and Disaster Recovery (DR) Service Datasource + URI, of the form projects/{project}/locations/{region}/backupVaults/ + {backupvault}/dataSources/{datasource}. + + TARGET + Cloud SQL instance ID of the target instance. + + POINT_IN_TIME + The point in time in which to restore the instance to. Uses RFC 3339 + format in UTC timezone. For example, '2012-11-15T16:19:00.094Z'. + +FLAGS + --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME + The name of the IP range allocated for the target instance with private + network connectivity. For example: 'google-managed-services-default'. + If set, the target instance IP is created in the allocated range + represented by this name. Reserved for future use. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --preferred-secondary-zone=PREFERRED_SECONDARY_ZONE + The preferred secondary zone for the cloned regional instance. If you + specify a value for this flag, then the target instance uses the value + as the secondary zone. The secondary zone can't be the same as the + primary zone. + + --preferred-zone=PREFERRED_ZONE + The preferred zone for the target instance. If you specify a value for + this flag, then the target instance uses the value as the primary zone. + + --private-network=PRIVATE_NETWORK + The resource link for the VPC network from which the Cloud SQL instance + is accessible for private IP. For example, + '/projects/myProject/global/networks/default'. + + --restore-database-names=RESTORE_DATABASE_NAMES + The name of the databases to be restored for a point-in-time restore. + If set, the destination instance will only restore the specified + databases. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 sql instances point-in-time-restore + + $ gcloud beta sql instances point-in-time-restore + diff --git a/gcloud/storage/batch-operations/jobs/create b/gcloud/storage/batch-operations/jobs/create index 6c684a16f..87ff6e749 100644 --- a/gcloud/storage/batch-operations/jobs/create +++ b/gcloud/storage/batch-operations/jobs/create @@ -28,13 +28,14 @@ EXAMPLES --manifest-location=gs://my-bucket/manifest.csv --delete-object To create a batch job with the name my-job to update object metadata - Content-Disposition to inline and Content-Language to en on bucket - my-bucket where you want to match objects with the prefix prefix1 or - prefix2: + Content-Disposition to inline, Content-Language to en, and set object + retention mode to locked on bucket my-bucket where you want to match + objects with prefixes prefix1 or prefix2: $ gcloud storage batch-operations jobs create my-job \ --bucket=my-bucket --included-object-prefixes=prefix1,prefix2 \ - --put-metadata=Content-Disposition=inline,Content-Language=en + --put-metadata=Content-Disposition=inline,Content-Language=en,\ + Retain-Until=2025-01-01T00:00:00Z,Retention-Mode=locked To create a batch job with the name my-job to put object event based hold on objects in bucket my-bucket with logging config enabled for @@ -106,12 +107,15 @@ REQUIRED FLAGS Content-Type={VALUE}. To set how caches should handle requests and responses, specify the key-value pair Cache-Control={VALUE}. To set custom time for Cloud Storage objects in RFC 3339 format, specify the - key-value pair Custom-Time={VALUE}. To set custom metadata on + key-value pair Custom-Time={VALUE}. To set object retention, specify + Retain-Until={TIMESTAMP} in RFC 3339 format and Retention-Mode={MODE} + where mode can be Locked or Unlocked. To set custom metadata on objects, specify key-value pairs {CUSTOM-KEY}:{VALUE}. Note that all predefined keys (e.g. Content-Disposition) are case-insensitive. Any other key that is not specified above will be treated as a custom - key. Multiple key-value pairs can be specified by separating them - with commas. For example, + key. To clear a field, provide the key with an empty value (e.g. + Content-Disposition=). Multiple key-value pairs can be specified by + separating them with commas. For example, --put-metadata=Content-Disposition=inline,Content-Encoding=gzip --rewrite-object=KEY=VALUE,[KEY=VALUE,...] diff --git a/gcloud/storage/cp b/gcloud/storage/cp index fc9d9f936..b778f87d7 100644 --- a/gcloud/storage/cp +++ b/gcloud/storage/cp @@ -36,6 +36,10 @@ DESCRIPTION Copy data between your local file system and the cloud, within the cloud, and between cloud storage providers. + Please Note - By default, the cp command does not follow directory + symlinks. You can use the --preserve-symlinks flag to follow directory + symlinks. + EXAMPLES The following command uploads all text files from the local directory to a bucket: diff --git a/gcloud/storage/objects/list b/gcloud/storage/objects/list index 44e1bd92c..4484c5ecb 100644 --- a/gcloud/storage/objects/list +++ b/gcloud/storage/objects/list @@ -26,12 +26,13 @@ EXAMPLES $ gcloud storage objects list gs://my-bucket/** - List all objects in bucket beginning with ``o'': + List all objects in bucket beginning with ``o'', including objects across + nested directories: - $ gcloud storage objects list gs://my-bucket/o* + $ gcloud storage objects list gs://my-bucket/**/o* - List all objects in bucket with JSON formatting, only returning the value - of the name metadata field: + List all objects within current directory of bucket with JSON formatting, + only returning the value of the name metadata field: $ gcloud storage objects list gs://my-bucket --format="json(name)" diff --git a/gcloud/storage/objects/update b/gcloud/storage/objects/update index 7864e08d5..f499b234f 100644 --- a/gcloud/storage/objects/update +++ b/gcloud/storage/objects/update @@ -38,16 +38,17 @@ EXAMPLES $ gcloud storage objects update gs://bucket/my-object \ --custom-metadata=key1=value1,key2=value2 - One can use wildcards (https://cloud.google.com/storage/docs/wildcards) to - update multiple objects in a single command. for instance to update all + You can use wildcards (https://cloud.google.com/storage/docs/wildcards) to + update multiple objects in a single command. For instance to update all objects to have a custom-metadata key: $ gcloud storage objects update gs://bucket/** \ --custom-metadata=key1=value1,key2=value2 - Rewrite all JPEG images to the NEARLINE storage class: + Rewrite all JPEG images to the NEARLINE storage class, including objects + across nested directories: - $ gcloud storage objects update gs://bucket/*.jpg \ + $ gcloud storage objects update gs://bucket/**/*.jpg \ --storage-class=NEARLINE You can also provide a precondition on an object's metageneration in order diff --git a/gcloud/storage/sign-url b/gcloud/storage/sign-url index 02cad0215..b2ab71e35 100644 --- a/gcloud/storage/sign-url +++ b/gcloud/storage/sign-url @@ -6,7 +6,7 @@ SYNOPSIS gcloud storage sign-url URL [URL ...] [--duration=DURATION, -d DURATION; default=3600] [--headers=[KEY=VALUE,...]] - [--http-verb=HTTP_VERB, -m HTTP_VERB; default="GET"] + [--http-verb=HTTP_VERB, -m HTTP_VERB; default="GET"] [--path-style-url] [--private-key-file=PRIVATE_KEY_FILE] [--private-key-password=PRIVATE_KEY_PASSWORD, -p PRIVATE_KEY_PASSWORD] [--query-params=[KEY=VALUE,...]] [--region=REGION, -r REGION] @@ -85,6 +85,17 @@ FLAGS session, you will need to specify the x-goog-resumable:start header in the request or else signature validation will fail. + --path-style-url + Generate path-style signed URL. + + By default, virtual hosted-style signed URL is generated, except for + domain-named buckets + (https://cloud.google.com/storage/docs/domain-name-verification). Use + this flag to force the generation of path-style signed URL. Signed URL + generated for domain-named buckets is always path-style. Learn more + about the two URL styles here + (https://cloud.google.com/storage/docs/request-endpoints#xml-api). + --private-key-file=PRIVATE_KEY_FILE The service account private key used to generate the cryptographic signature for the generated URL. Must be in PKCS12 or JSON format. If