diff --git a/gcloud/_version b/gcloud/_version index 69fad260e..cc5760919 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 429.0.0 -alpha 2023.04.28 -beta 2023.04.28 +Google Cloud SDK 430.0.0 +alpha 2023.05.09 +beta 2023.05.09 bq 2.0.92 bundled-python3-unix 3.9.16 -core 2023.04.28 +core 2023.05.09 gcloud-crc32c 1.0.0 gsutil 5.23 diff --git a/gcloud/alloydb/help b/gcloud/alloydb/help index 1fdabe532..7ae7086fe 100644 --- a/gcloud/alloydb/help +++ b/gcloud/alloydb/help @@ -34,6 +34,9 @@ GROUPS operations Provide commands for managing AlloyDB operations. + users + Provide commands for managing AlloyDB users. + NOTES These variants are also available: diff --git a/gcloud/alloydb/users/create b/gcloud/alloydb/users/create new file mode 100644 index 000000000..d8aa29e3e --- /dev/null +++ b/gcloud/alloydb/users/create @@ -0,0 +1,66 @@ +NAME + gcloud alloydb users create - creates a user in a given cluster + +SYNOPSIS + gcloud alloydb users create USERNAME --cluster=CLUSTER --region=REGION + [--db-roles=[ROLE,...]] [--password=PASSWORD] [--superuser=SUPERUSER] + [--type=TYPE; default="BUILT_IN"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Creates a user in a given cluster with specified username, cluster, region, + type, and password. + +EXAMPLES + To create a new user, run: + + $ gcloud alloydb users create my-username --cluster=my-cluster \ + --region=us-central1 --password=postgres + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --db-roles=[ROLE,...] + Comma separated list of database roles this new user will be granted + upon creation. + + --password=PASSWORD + Password for this database user. + + --superuser=SUPERUSER + If true, new user will have AlloyDB superuser privileges. Default value + is false. + + --type=TYPE; default="BUILT_IN" + Type corresponds to the user type. TYPE must be one of: + + BUILT_IN + This database user can authenticate via password-based + authentication + IAM_BASED + This database user can authenticate via IAM-based authentication + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 alloydb users create + + $ gcloud beta alloydb users create + diff --git a/gcloud/alloydb/users/delete b/gcloud/alloydb/users/delete new file mode 100644 index 000000000..751a45040 --- /dev/null +++ b/gcloud/alloydb/users/delete @@ -0,0 +1,43 @@ +NAME + gcloud alloydb users delete - deletes an AlloyDB user in a given cluster + +SYNOPSIS + gcloud alloydb users delete USERNAME --cluster=CLUSTER --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Deletes an AlloyDB user in a given cluster. + +EXAMPLES + To delete an user, run: + + $ gcloud alloydb users delete my-username --cluster=my-cluster \ + --region=us-central1 + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha alloydb users delete + + $ gcloud beta alloydb users delete + diff --git a/gcloud/alloydb/users/help b/gcloud/alloydb/users/help new file mode 100644 index 000000000..c272b0caa --- /dev/null +++ b/gcloud/alloydb/users/help @@ -0,0 +1,45 @@ +NAME + gcloud alloydb users - provide commands for managing AlloyDB users + +SYNOPSIS + gcloud alloydb users COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Provide commands for managing AlloyDB users including creating, + configuring, getting, listing, and deleting users. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Creates a user in a given cluster. + + delete + Deletes an AlloyDB user in a given cluster. + + list + Lists AlloyDB users in a given cluster. + + set-password + Update an AlloyDB user's password within a given cluster and region. + + set-roles + Update an AlloyDB user's database roles within a given cluster and + region. + + set-superuser + Update an AlloyDB user's superuser role within a given cluster and + region. + +NOTES + These variants are also available: + + $ gcloud alpha alloydb users + + $ gcloud beta alloydb users + diff --git a/gcloud/alloydb/users/list b/gcloud/alloydb/users/list new file mode 100644 index 000000000..741c853ea --- /dev/null +++ b/gcloud/alloydb/users/list @@ -0,0 +1,71 @@ +NAME + gcloud alloydb users list - lists AlloyDB users in a given cluster + +SYNOPSIS + gcloud alloydb users list --cluster=CLUSTER --region=REGION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Lists AlloyDB users in a given cluster. + +EXAMPLES + To list users, run: + + $ gcloud alloydb users list --cluster=my-cluster --region=us-central1 + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +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 alloydb users list + + $ gcloud beta alloydb users list + diff --git a/gcloud/alloydb/users/set-password b/gcloud/alloydb/users/set-password new file mode 100644 index 000000000..644825b9a --- /dev/null +++ b/gcloud/alloydb/users/set-password @@ -0,0 +1,47 @@ +NAME + gcloud alloydb users set-password - update an AlloyDB user's password + within a given cluster and region + +SYNOPSIS + gcloud alloydb users set-password USERNAME --cluster=CLUSTER + --password=PASSWORD --region=REGION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an AlloyDB user's password within a given cluster and region. + +EXAMPLES + To update a user's password, run: + + $ gcloud alloydb users set-password my-username \ + --cluster=my-cluster --region=us-central1 --password=postgres + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --password=PASSWORD + Password for this database user. + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha alloydb users set-password + + $ gcloud beta alloydb users set-password + diff --git a/gcloud/alloydb/users/set-roles b/gcloud/alloydb/users/set-roles new file mode 100644 index 000000000..ebb1a7a65 --- /dev/null +++ b/gcloud/alloydb/users/set-roles @@ -0,0 +1,48 @@ +NAME + gcloud alloydb users set-roles - update an AlloyDB user's database roles + within a given cluster and region + +SYNOPSIS + gcloud alloydb users set-roles USERNAME --cluster=CLUSTER + --db-roles=[ROLE,...] --region=REGION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an AlloyDB user's database roles within a given cluster and region. + +EXAMPLES + To update a user's database roles, run: + + $ gcloud alloydb users set-roles my-username --cluster=my-cluster \ + --region=us-central1 --db-roles=role1,role2 + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --db-roles=[ROLE,...] + Comma separated list of database roles this new user will be granted + upon creation. + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 alloydb users set-roles + + $ gcloud beta alloydb users set-roles + diff --git a/gcloud/alloydb/users/set-superuser b/gcloud/alloydb/users/set-superuser new file mode 100644 index 000000000..743bab519 --- /dev/null +++ b/gcloud/alloydb/users/set-superuser @@ -0,0 +1,47 @@ +NAME + gcloud alloydb users set-superuser - update an AlloyDB user's superuser + role within a given cluster and region + +SYNOPSIS + gcloud alloydb users set-superuser USERNAME --cluster=CLUSTER + --region=REGION --superuser=SUPERUSER [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an AlloyDB user's superuser role within a given cluster and region. + +EXAMPLES + To update a user's superuser role, run: + + $ gcloud alloydb users set-superuser my-username \ + --cluster=my-cluster --region=us-central1 --superuser=true/false + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + + --superuser=SUPERUSER + If true, user will have AlloyDB superuser privileges + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 alloydb users set-superuser + + $ gcloud beta alloydb users set-superuser + diff --git a/gcloud/alpha/alloydb/help b/gcloud/alpha/alloydb/help index 5bbbefdb2..233355ba0 100644 --- a/gcloud/alpha/alloydb/help +++ b/gcloud/alpha/alloydb/help @@ -34,6 +34,9 @@ GROUPS operations (ALPHA) Provide commands for managing AlloyDB operations. + users + (ALPHA) Provide commands for managing AlloyDB users. + 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/alloydb/users/create b/gcloud/alpha/alloydb/users/create new file mode 100644 index 000000000..19f3ac1ce --- /dev/null +++ b/gcloud/alpha/alloydb/users/create @@ -0,0 +1,70 @@ +NAME + gcloud alpha alloydb users create - creates a user in a given cluster + +SYNOPSIS + gcloud alpha alloydb users create USERNAME --cluster=CLUSTER + --region=REGION [--db-roles=[ROLE,...]] [--password=PASSWORD] + [--superuser=SUPERUSER] [--type=TYPE; default="BUILT_IN"] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Creates a user in a given cluster with specified username, cluster, + region, type, and password. + +EXAMPLES + To create a new user, run: + + $ gcloud alpha alloydb users create my-username \ + --cluster=my-cluster --region=us-central1 --password=postgres + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --db-roles=[ROLE,...] + Comma separated list of database roles this new user will be granted + upon creation. + + --password=PASSWORD + Password for this database user. + + --superuser=SUPERUSER + If true, new user will have AlloyDB superuser privileges. Default value + is false. + + --type=TYPE; default="BUILT_IN" + Type corresponds to the user type. TYPE must be one of: + + BUILT_IN + This database user can authenticate via password-based + authentication + IAM_BASED + This database user can authenticate via IAM-based authentication + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 alloydb users create + + $ gcloud beta alloydb users create + diff --git a/gcloud/alpha/alloydb/users/delete b/gcloud/alpha/alloydb/users/delete new file mode 100644 index 000000000..3dd552dd7 --- /dev/null +++ b/gcloud/alpha/alloydb/users/delete @@ -0,0 +1,47 @@ +NAME + gcloud alpha alloydb users delete - deletes an AlloyDB user in a given + cluster + +SYNOPSIS + gcloud alpha alloydb users delete USERNAME --cluster=CLUSTER + --region=REGION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deletes an AlloyDB user in a given cluster. + +EXAMPLES + To delete an user, run: + + $ gcloud alpha alloydb users delete my-username \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud alloydb users delete + + $ gcloud beta alloydb users delete + diff --git a/gcloud/alpha/alloydb/users/help b/gcloud/alpha/alloydb/users/help new file mode 100644 index 000000000..5ffcfac20 --- /dev/null +++ b/gcloud/alpha/alloydb/users/help @@ -0,0 +1,49 @@ +NAME + gcloud alpha alloydb users - provide commands for managing AlloyDB users + +SYNOPSIS + gcloud alpha alloydb users COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Provide commands for managing AlloyDB users including creating, + configuring, getting, listing, and deleting users. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Creates a user in a given cluster. + + delete + (ALPHA) Deletes an AlloyDB user in a given cluster. + + list + (ALPHA) Lists AlloyDB users in a given cluster. + + set-password + (ALPHA) Update an AlloyDB user's password within a given cluster and + region. + + set-roles + (ALPHA) Update an AlloyDB user's database roles within a given cluster + and region. + + set-superuser + (ALPHA) Update an AlloyDB user's superuser role within a given cluster + and region. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud alloydb users + + $ gcloud beta alloydb users + diff --git a/gcloud/alpha/alloydb/users/list b/gcloud/alpha/alloydb/users/list new file mode 100644 index 000000000..a8adb9b35 --- /dev/null +++ b/gcloud/alpha/alloydb/users/list @@ -0,0 +1,75 @@ +NAME + gcloud alpha alloydb users list - lists AlloyDB users in a given cluster + +SYNOPSIS + gcloud alpha alloydb users list --cluster=CLUSTER --region=REGION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Lists AlloyDB users in a given cluster. + +EXAMPLES + To list users, run: + + $ gcloud alpha alloydb users list --cluster=my-cluster \ + --region=us-central1 + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +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 alloydb users list + + $ gcloud beta alloydb users list + diff --git a/gcloud/alpha/alloydb/users/set-password b/gcloud/alpha/alloydb/users/set-password new file mode 100644 index 000000000..2106fba4a --- /dev/null +++ b/gcloud/alpha/alloydb/users/set-password @@ -0,0 +1,51 @@ +NAME + gcloud alpha alloydb users set-password - update an AlloyDB user's password + within a given cluster and region + +SYNOPSIS + gcloud alpha alloydb users set-password USERNAME --cluster=CLUSTER + --password=PASSWORD --region=REGION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an AlloyDB user's password within a given cluster and + region. + +EXAMPLES + To update a user's password, run: + + $ gcloud alpha alloydb users set-password my-username \ + --cluster=my-cluster --region=us-central1 --password=postgres + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --password=PASSWORD + Password for this database user. + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud alloydb users set-password + + $ gcloud beta alloydb users set-password + diff --git a/gcloud/alpha/alloydb/users/set-roles b/gcloud/alpha/alloydb/users/set-roles new file mode 100644 index 000000000..48af79eb6 --- /dev/null +++ b/gcloud/alpha/alloydb/users/set-roles @@ -0,0 +1,52 @@ +NAME + gcloud alpha alloydb users set-roles - update an AlloyDB user's database + roles within a given cluster and region + +SYNOPSIS + gcloud alpha alloydb users set-roles USERNAME --cluster=CLUSTER + --db-roles=[ROLE,...] --region=REGION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an AlloyDB user's database roles within a given cluster and + region. + +EXAMPLES + To update a user's database roles, run: + + $ gcloud alpha alloydb users set-roles my-username \ + --cluster=my-cluster --region=us-central1 --db-roles=role1,role2 + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --db-roles=[ROLE,...] + Comma separated list of database roles this new user will be granted + upon creation. + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 alloydb users set-roles + + $ gcloud beta alloydb users set-roles + diff --git a/gcloud/alpha/alloydb/users/set-superuser b/gcloud/alpha/alloydb/users/set-superuser new file mode 100644 index 000000000..11ce19f7d --- /dev/null +++ b/gcloud/alpha/alloydb/users/set-superuser @@ -0,0 +1,51 @@ +NAME + gcloud alpha alloydb users set-superuser - update an AlloyDB user's + superuser role within a given cluster and region + +SYNOPSIS + gcloud alpha alloydb users set-superuser USERNAME --cluster=CLUSTER + --region=REGION --superuser=SUPERUSER [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an AlloyDB user's superuser role within a given cluster and + region. + +EXAMPLES + To update a user's superuser role, run: + + $ gcloud alpha alloydb users set-superuser my-username \ + --cluster=my-cluster --region=us-central1 --superuser=true/false + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + + --superuser=SUPERUSER + If true, user will have AlloyDB superuser privileges + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 alloydb users set-superuser + + $ gcloud beta alloydb users set-superuser + diff --git a/gcloud/alpha/blockchain-node-engine/locations/describe b/gcloud/alpha/blockchain-node-engine/locations/describe index 122f0ef94..af90ed792 100644 --- a/gcloud/alpha/blockchain-node-engine/locations/describe +++ b/gcloud/alpha/blockchain-node-engine/locations/describe @@ -48,7 +48,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the blockchainnodeengine/v1alpha1 API. The full - documentation for this API can be found at: https://cloud.google.com/web3 + documentation for this API can be found at: + https://cloud.google.com/blockchain-node-engine NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/blockchain-node-engine/locations/list b/gcloud/alpha/blockchain-node-engine/locations/list index 471c9effb..c21f8747c 100644 --- a/gcloud/alpha/blockchain-node-engine/locations/list +++ b/gcloud/alpha/blockchain-node-engine/locations/list @@ -52,7 +52,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the blockchainnodeengine/v1alpha1 API. The full - documentation for this API can be found at: https://cloud.google.com/web3 + documentation for this API can be found at: + https://cloud.google.com/blockchain-node-engine NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/blockchain-node-engine/nodes/create b/gcloud/alpha/blockchain-node-engine/nodes/create index ad5d267be..684ea0b8d 100644 --- a/gcloud/alpha/blockchain-node-engine/nodes/create +++ b/gcloud/alpha/blockchain-node-engine/nodes/create @@ -112,7 +112,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the blockchainnodeengine/v1alpha1 API. The full - documentation for this API can be found at: https://cloud.google.com/web3 + documentation for this API can be found at: + https://cloud.google.com/blockchain-node-engine NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/blockchain-node-engine/nodes/delete b/gcloud/alpha/blockchain-node-engine/nodes/delete index 2e22a3936..330880074 100644 --- a/gcloud/alpha/blockchain-node-engine/nodes/delete +++ b/gcloud/alpha/blockchain-node-engine/nodes/delete @@ -67,7 +67,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the blockchainnodeengine/v1alpha1 API. The full - documentation for this API can be found at: https://cloud.google.com/web3 + documentation for this API can be found at: + https://cloud.google.com/blockchain-node-engine NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/blockchain-node-engine/nodes/describe b/gcloud/alpha/blockchain-node-engine/nodes/describe index bd12c2ef7..09b98e7cc 100644 --- a/gcloud/alpha/blockchain-node-engine/nodes/describe +++ b/gcloud/alpha/blockchain-node-engine/nodes/describe @@ -56,7 +56,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the blockchainnodeengine/v1alpha1 API. The full - documentation for this API can be found at: https://cloud.google.com/web3 + documentation for this API can be found at: + https://cloud.google.com/blockchain-node-engine NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/blockchain-node-engine/nodes/list b/gcloud/alpha/blockchain-node-engine/nodes/list index 65dd32262..2b746c793 100644 --- a/gcloud/alpha/blockchain-node-engine/nodes/list +++ b/gcloud/alpha/blockchain-node-engine/nodes/list @@ -81,7 +81,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the blockchainnodeengine/v1alpha1 API. The full - documentation for this API can be found at: https://cloud.google.com/web3 + documentation for this API can be found at: + https://cloud.google.com/blockchain-node-engine NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/blockchain-node-engine/operations/describe b/gcloud/alpha/blockchain-node-engine/operations/describe index e1e66f342..1bf27574e 100644 --- a/gcloud/alpha/blockchain-node-engine/operations/describe +++ b/gcloud/alpha/blockchain-node-engine/operations/describe @@ -57,7 +57,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the blockchainnodeengine/v1alpha1 API. The full - documentation for this API can be found at: https://cloud.google.com/web3 + documentation for this API can be found at: + https://cloud.google.com/blockchain-node-engine NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/blockchain-node-engine/operations/list b/gcloud/alpha/blockchain-node-engine/operations/list index 8028417e7..682d5bd80 100644 --- a/gcloud/alpha/blockchain-node-engine/operations/list +++ b/gcloud/alpha/blockchain-node-engine/operations/list @@ -76,7 +76,8 @@ GCLOUD WIDE FLAGS API REFERENCE This command uses the blockchainnodeengine/v1alpha1 API. The full - documentation for this API can be found at: https://cloud.google.com/web3 + documentation for this API can be found at: + https://cloud.google.com/blockchain-node-engine NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/bms/instances/rename b/gcloud/alpha/bms/instances/rename index a56698d67..13120f10d 100644 --- a/gcloud/alpha/bms/instances/rename +++ b/gcloud/alpha/bms/instances/rename @@ -62,5 +62,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 bms instances rename diff --git a/gcloud/alpha/bms/networks/rename b/gcloud/alpha/bms/networks/rename index 4543c35b6..460021f7e 100644 --- a/gcloud/alpha/bms/networks/rename +++ b/gcloud/alpha/bms/networks/rename @@ -62,5 +62,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 bms networks rename diff --git a/gcloud/alpha/bms/nfs-shares/rename b/gcloud/alpha/bms/nfs-shares/rename index 9146931ce..42d597356 100644 --- a/gcloud/alpha/bms/nfs-shares/rename +++ b/gcloud/alpha/bms/nfs-shares/rename @@ -62,5 +62,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 bms nfs-shares rename diff --git a/gcloud/alpha/bms/volumes/rename b/gcloud/alpha/bms/volumes/rename index 5cbebb285..ba06be025 100644 --- a/gcloud/alpha/bms/volumes/rename +++ b/gcloud/alpha/bms/volumes/rename @@ -62,5 +62,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 bms volumes rename diff --git a/gcloud/alpha/builds/submit b/gcloud/alpha/builds/submit index 319566f19..8f2613788 100644 --- a/gcloud/alpha/builds/submit +++ b/gcloud/alpha/builds/submit @@ -6,9 +6,11 @@ SYNOPSIS [--default-buckets-behavior=DEFAULT_BUCKETS_BEHAVIOR] [--disk-size=DISK_SIZE] [--gcs-log-dir=GCS_LOG_DIR] [--gcs-source-staging-dir=GCS_SOURCE_STAGING_DIR] - [--ignore-file=IGNORE_FILE] [--machine-type=MACHINE_TYPE] - [--region=REGION] [--substitutions=[KEY=VALUE,...]] [--suppress-logs] - [--timeout=TIMEOUT] [--worker-pool=WORKER_POOL] + [--git-source-dir=GIT_SOURCE_DIR] + [--git-source-revision=GIT_SOURCE_REVISION] [--ignore-file=IGNORE_FILE] + [--machine-type=MACHINE_TYPE] [--region=REGION] + [--substitutions=[KEY=VALUE,...]] [--suppress-logs] [--timeout=TIMEOUT] + [--worker-pool=WORKER_POOL] [--config=CONFIG; default="cloudbuild.yaml" | --pack=[builder=BUILDER],[env=ENV],[image=IMAGE] | --tag=TAG, -t TAG] [GCLOUD_WIDE_FLAG ...] @@ -45,15 +47,15 @@ POSITIONAL ARGUMENTS [SOURCE] The location of the source to build. The location can be a directory - on a local disk or a gzipped archive file (.tar.gz) in Google Cloud - Storage. If the source is a local directory, this command skips the - files specified in the --ignore-file. If --ignore-file is not - specified, use.gcloudignore file. If a .gcloudignore file is absent - and a .gitignore file is present in the local source directory, - gcloud will use a generated Git-compatible .gcloudignore file that - respects your .gitignored files. The global .gitignore is not - respected. For more information on .gcloudignore, see gcloud topic - gcloudignore. + on a local disk, a gzipped archive file (.tar.gz) in Google Cloud + Storage, or a Git repo url starting with http:// or https://. If the + source is a local directory, this command skips the files specified + in the --ignore-file. If --ignore-file is not specified, + use.gcloudignore file. If a .gcloudignore file is absent and a + .gitignore file is present in the local source directory, gcloud will + use a generated Git-compatible .gcloudignore file that respects your + .gitignored files. The global .gitignore is not respected. For more + information on .gcloudignore, see gcloud topic gcloudignore. --no-source Specify that no source should be uploaded with this build. @@ -95,6 +97,22 @@ FLAGS set --default-buckets-behavior to REGIONAL_USER_OWNED_BUCKET and builds/region is not global. + --git-source-dir=GIT_SOURCE_DIR + Directory, relative to the source root, in which to run the build. This + must be a relative path. If a step's dir is specified and is an + absolute path, this value is ignored for that step's execution. + + --git-source-revision=GIT_SOURCE_REVISION + Revision to fetch from the Git repository such as a branch, a tag, a + commit SHA, or any Git ref to run the build. + + Cloud Build uses git fetch to fetch the revision from the Git + repository; therefore make sure that the string you provide for + revision is parsable by the command. For information on string values + accepted by git fetch, see + https://git-scm.com/docs/gitrevisions#_specifying_revisions. For + information on git fetch, see https://git-scm.com/docs/git-fetch. + --ignore-file=IGNORE_FILE Override the .gcloudignore file and use the specified file instead. diff --git a/gcloud/alpha/compute/addresses/move b/gcloud/alpha/compute/addresses/move index 356a67f4f..572beb0f4 100644 --- a/gcloud/alpha/compute/addresses/move +++ b/gcloud/alpha/compute/addresses/move @@ -6,8 +6,13 @@ SYNOPSIS [--description=DESCRIPTION] [--new-name=NEW_NAME] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] -DESCRIPTION - (ALPHA) Move an address to another project. +EXAMPLES + The following command moves address external-ip1 in region us-central1 to + project test-playground with new address name test-ip1: + + $ gcloud alpha compute addresses move external-ip1 \ + --new-name=test-ip1 --target-project=test-playground \ + --region=us-central1 POSITIONAL ARGUMENTS NAME @@ -15,8 +20,9 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --target-project=TARGET_PROJECT - The target project to move address in. It can be either project name or - project numerical ID. It must not be the same as the current project. + The target project to move address to. It can be either a project name + or a project numerical ID. It must not be the same as the current + project. OPTIONAL FLAGS --description=DESCRIPTION @@ -47,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 addresses move diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index 8227b5914..b3ee5ba15 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -9,6 +9,7 @@ SYNOPSIS [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] [--can-ip-forward] [--confidential-compute] + [--confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] [--configure-disk=[PROPERTY=VALUE,...]] [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] [--disk=[auto-delete=AUTO-DELETE], @@ -145,6 +146,18 @@ FLAGS Computing is based on Secure Encrypted Virtualization (SEV), an AMD virtualization feature for running confidential instances. + --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE + The instance boots with Confidential Computing enabled. Confidential + Computing can be based on Secure Encrypted Virtualization (SEV) or + Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both + of which are AMD virtualization features for running confidential + instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + + SEV + Secure Encrypted Virtualization + SEV_SNP + Secure Encrypted Virtualization - Secure Nested Paging + --configure-disk=[PROPERTY=VALUE,...] This option has effect only when used with --source-instance. It allows you to override how the source-instance's disks are defined in the diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index f6af4cba0..34c70b072 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -11,7 +11,8 @@ SYNOPSIS [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] - [--can-ip-forward] [--confidential-compute] [--count=COUNT] + [--can-ip-forward] [--confidential-compute] + [--confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] [--count=COUNT] [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] [--disk=[boot=BOOT], [device-name=DEVICE-NAME],[name=NAME],[scope=SCOPE]] @@ -188,6 +189,18 @@ OPTIONAL FLAGS Computing is based on Secure Encrypted Virtualization (SEV), an AMD virtualization feature for running confidential instances. + --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE + The instance boots with Confidential Computing enabled. Confidential + Computing can be based on Secure Encrypted Virtualization (SEV) or + Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both + of which are AMD virtualization features for running confidential + instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + + SEV + Secure Encrypted Virtualization + SEV_SNP + Secure Encrypted Virtualization - Secure Nested Paging + --count=COUNT Number of Compute Engine virtual machines to create. If specified, and --predefined-names is specified, count must equal the amount of names diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 0e1562d53..d14d946c0 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -10,6 +10,7 @@ SYNOPSIS [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] [--can-ip-forward] [--confidential-compute] + [--confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] [--create-disk=[PROPERTY=VALUE,...]] [--csek-key-file=FILE] [--deletion-protection] [--description=DESCRIPTION] [--disk=[auto-delete=AUTO-DELETE],[boot=BOOT], @@ -200,6 +201,18 @@ FLAGS Computing is based on Secure Encrypted Virtualization (SEV), an AMD virtualization feature for running confidential instances. + --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE + The instance boots with Confidential Computing enabled. Confidential + Computing can be based on Secure Encrypted Virtualization (SEV) or + Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both + of which are AMD virtualization features for running confidential + instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + + SEV + Secure Encrypted Virtualization + SEV_SNP + Secure Encrypted Virtualization - Secure Nested Paging + --create-disk=[PROPERTY=VALUE,...] Creates and attaches persistent disks to the instances. diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index c662015c0..442cc1468 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -10,6 +10,7 @@ SYNOPSIS [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] [--can-ip-forward] [--confidential-compute] + [--confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] [--container-arg=CONTAINER_ARG] [--container-command=CONTAINER_COMMAND] [--container-env=[KEY=VALUE, ...,...]] [--container-env-file=CONTAINER_ENV_FILE] @@ -152,6 +153,18 @@ FLAGS Computing is based on Secure Encrypted Virtualization (SEV), an AMD virtualization feature for running confidential instances. + --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE + The instance boots with Confidential Computing enabled. Confidential + Computing can be based on Secure Encrypted Virtualization (SEV) or + Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both + of which are AMD virtualization features for running confidential + instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + + SEV + Secure Encrypted Virtualization + SEV_SNP + Secure Encrypted Virtualization - Secure Nested Paging + --container-arg=CONTAINER_ARG Argument to append to container entrypoint or to override container CMD. Each argument must have a separate flag. Arguments are appended in diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 0b94831bf..978f807e0 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -12,7 +12,8 @@ SYNOPSIS [--boot-disk-device-name=BOOT_DISK_DEVICE_NAME] [--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS] [--boot-disk-size=BOOT_DISK_SIZE] [--boot-disk-type=BOOT_DISK_TYPE] - [--can-ip-forward] [--confidential-compute] [--count=COUNT] + [--can-ip-forward] [--confidential-compute] + [--confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE] [--count=COUNT] [--create-disk=[PROPERTY=VALUE,...]] [--description=DESCRIPTION] [--disk=[boot=BOOT], [device-name=DEVICE-NAME],[name=NAME],[scope=SCOPE]] @@ -172,6 +173,18 @@ OPTIONAL FLAGS Computing is based on Secure Encrypted Virtualization (SEV), an AMD virtualization feature for running confidential instances. + --confidential-compute-type=CONFIDENTIAL_COMPUTE_TYPE + The instance boots with Confidential Computing enabled. Confidential + Computing can be based on Secure Encrypted Virtualization (SEV) or + Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both + of which are AMD virtualization features for running confidential + instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + + SEV + Secure Encrypted Virtualization + SEV_SNP + Secure Encrypted Virtualization - Secure Nested Paging + --count=COUNT Number of Compute Engine virtual machines to create. If specified, and --predefined-names is specified, count must equal the amount of names diff --git a/gcloud/alpha/compute/routers/add-bgp-peer b/gcloud/alpha/compute/routers/add-bgp-peer index 16d853e1e..128d6fda8 100644 --- a/gcloud/alpha/compute/routers/add-bgp-peer +++ b/gcloud/alpha/compute/routers/add-bgp-peer @@ -6,7 +6,8 @@ SYNOPSIS gcloud alpha compute routers add-bgp-peer NAME --interface=INTERFACE --peer-asn=PEER_ASN --peer-name=PEER_NAME [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] - [--advertisement-mode=MODE] [--async] [--[no-]enable-ipv6] + [--advertisement-mode=MODE] [--async] + [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv6] [--[no-]enabled] [--instance=INSTANCE] [--instance-zone=INSTANCE_ZONE] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] @@ -14,6 +15,7 @@ SYNOPSIS [--peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] + [--set-custom-learned-route-ranges=[CIDR_RANGE,...]] [--bfd-min-receive-interval=BFD_MIN_RECEIVE_INTERVAL --bfd-min-transmit-interval=BFD_MIN_TRANSMIT_INTERVAL --bfd-multiplier=BFD_MULTIPLIER @@ -58,6 +60,12 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --custom-learned-route-priority=PRIORITY + An integral value 0 <= priority <= 65535, to be applied to all custom + learned route IP address ranges for this peer. If not specified, a + Google-managed priority value of 100 is used. The routes with the + lowest priority value win. + --[no-]enable-ipv6 If IPv6 is enabled, the peer connection can be established with IPv6 route exchange. If disabled, no IPv6 route exchange is allowed on any @@ -155,6 +163,14 @@ OPTIONAL FLAGS the range, use --set-advertisement-ranges=192.168.10.0/24=my-networks. This list can only be specified in custom advertisement mode. + --set-custom-learned-route-ranges=[CIDR_RANGE,...] + The list of user-defined custom learned route IP address ranges for + this peer. This list is a comma separated IP address ranges such as + 1.2.3.4,6.7.0.0/16,2001:db8:abcd:12::/64 where each IP address range + must be a valid CIDR-formatted prefix. If an IP address is provided + without a subnet mask, it is interpreted as a /32 singular IP address + range for IPv4, and /128 for IPv6. + Arguments to configure BFD (Bidirectional Forwarding Detection) settings: --bfd-min-receive-interval=BFD_MIN_RECEIVE_INTERVAL diff --git a/gcloud/alpha/compute/routers/update-bgp-peer b/gcloud/alpha/compute/routers/update-bgp-peer index 00deab55b..f0f77991a 100644 --- a/gcloud/alpha/compute/routers/update-bgp-peer +++ b/gcloud/alpha/compute/routers/update-bgp-peer @@ -6,17 +6,21 @@ SYNOPSIS gcloud alpha compute routers update-bgp-peer NAME --peer-name=PEER_NAME [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] [--advertisement-mode=MODE] [--async] [--clear-md5-authentication-key] - [--[no-]enable-ipv6] [--[no-]enabled] [--interface=INTERFACE] - [--ip-address=IP_ADDRESS] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] + [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv6] + [--[no-]enabled] [--interface=INTERFACE] [--ip-address=IP_ADDRESS] + [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] [--peer-asn=PEER_ASN] [--peer-ip-address=PEER_IP_ADDRESS] [--peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] + [--set-custom-learned-route-ranges=[CIDR_RANGE,...]] [--add-advertisement-groups=[GROUP,...] | --add-advertisement-ranges=[CIDR_RANGE=DESC,...] | --remove-advertisement-groups=[GROUP,...] | --remove-advertisement-ranges=[CIDR_RANGE,...]] + [--add-custom-learned-route-ranges=[CIDR_RANGE,...] + | --remove-custom-learned-route-ranges=[CIDR_RANGE,...]] [--bfd-min-receive-interval=BFD_MIN_RECEIVE_INTERVAL --bfd-min-transmit-interval=BFD_MIN_TRANSMIT_INTERVAL --bfd-multiplier=BFD_MULTIPLIER @@ -57,6 +61,12 @@ OPTIONAL FLAGS --clear-md5-authentication-key If specified, remove MD5 authentication from the BGP peer. + --custom-learned-route-priority=PRIORITY + An integral value 0 <= priority <= 65535, to be applied to all custom + learned route IP address ranges for this peer. If not specified, a + Google-managed priority value of 100 is used. The routes with the + lowest priority value win. + --[no-]enable-ipv6 If IPv6 is enabled, the peer connection can be established with IPv6 route exchange. If disabled, no IPv6 route exchange is allowed on any @@ -141,6 +151,14 @@ OPTIONAL FLAGS the range, use --set-advertisement-ranges=192.168.10.0/24=my-networks. This list can only be specified in custom advertisement mode. + --set-custom-learned-route-ranges=[CIDR_RANGE,...] + The list of user-defined custom learned route IP address ranges for + this peer. This list is a comma separated IP address ranges such as + 1.2.3.4,6.7.0.0/16,2001:db8:abcd:12::/64 where each IP address range + must be a valid CIDR-formatted prefix. If an IP address is provided + without a subnet mask, it is interpreted as a /32 singular IP address + range for IPv4, and /128 for IPv6. + At most one of these can be specified: --add-advertisement-groups=[GROUP,...] @@ -181,6 +199,24 @@ OPTIONAL FLAGS exist in the current set of custom advertisements. This field can only be specified in custom advertisement mode. + At most one of these can be specified: + + --add-custom-learned-route-ranges=[CIDR_RANGE,...] + A list of user-defined custom learned route IP address ranges to be + added to this peer. This list is a comma separated IP address ranges + such as 1.2.3.4,6.7.0.0/16,2001:db8:abcd:12::/64 where each IP + address range must be a valid CIDR-formatted prefix. If an IP address + is provided without a subnet mask, it is interpreted as a /32 + singular IP address range for IPv4, and /128 for IPv6. + + --remove-custom-learned-route-ranges=[CIDR_RANGE,...] + A list of user-defined custom learned route IP address ranges to be + removed from this peer. This list is a comma separated IP address + ranges such as 1.2.3.4,6.7.0.0/16,2001:db8:abcd:12::/64 where each IP + address range must be a valid CIDR-formatted prefix. If an IP address + is provided without a subnet mask, it is interpreted as a /32 + singular IP address range for IPv4, and /128 for IPv6. + Arguments to update BFD (Bidirectional Forwarding Detection) settings: --bfd-min-receive-interval=BFD_MIN_RECEIVE_INTERVAL diff --git a/gcloud/alpha/compute/security-policies/update b/gcloud/alpha/compute/security-policies/update index 7e440f47c..3f43c7a25 100644 --- a/gcloud/alpha/compute/security-policies/update +++ b/gcloud/alpha/compute/security-policies/update @@ -16,6 +16,7 @@ SYNOPSIS [--log-level=LOG_LEVEL] [--network-ddos-protection=NETWORK_DDOS_PROTECTION] [--recaptcha-redirect-site-key=RECAPTCHA_REDIRECT_SITE_KEY] + [--user-ip-request-headers=[USER_IP_REQUEST_HEADER,...]] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -91,6 +92,10 @@ FLAGS The reCAPTCHA site key to be used for rules using the redirect action and the google-recaptcha redirect type under the security policy. + --user-ip-request-headers=[USER_IP_REQUEST_HEADER,...] + A comma-separated list of request header names to use for resolving the + caller's user IP address. + At most one of these can be specified: --global diff --git a/gcloud/alpha/container/clusters/create-auto b/gcloud/alpha/container/clusters/create-auto index bba903215..f9607a2ad 100644 --- a/gcloud/alpha/container/clusters/create-auto +++ b/gcloud/alpha/container/clusters/create-auto @@ -13,10 +13,11 @@ SYNOPSIS [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--enable-fleet] [--enable-google-cloud-access] [--enable-kubernetes-unstable-apis=API,[API,...]] - [--fleet-project=PROJECT_ID_OR_NUMBER] [--network=NETWORK] - [--private-endpoint-subnetwork=NAME] [--release-channel=CHANNEL] - [--security-group=SECURITY_GROUP] [--services-ipv4-cidr=CIDR] - [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] + [--enable-master-global-access] [--fleet-project=PROJECT_ID_OR_NUMBER] + [--network=NETWORK] [--private-endpoint-subnetwork=NAME] + [--release-channel=CHANNEL] [--security-group=SECURITY_GROUP] + [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] + [--subnetwork=SUBNETWORK] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE --binauthz-policy=BINAUTHZ_POLICY] [--enable-master-authorized-networks @@ -167,6 +168,14 @@ FLAGS expected to be production ready and should be avoided in production-grade environments. + --enable-master-global-access + Use with private clusters to allow access to the master's private + endpoint from any Google Cloud region or on-premises environment + regardless of the private cluster's region. + + Must be used in conjunction with '--enable-ip-alias' and + '--enable-private-nodes'. + --fleet-project=PROJECT_ID_OR_NUMBER Sets fleet host project for the cluster. If specified, the current cluster will be registered as a fleet membership under the fleet host diff --git a/gcloud/alpha/database-migration/migration-jobs/create b/gcloud/alpha/database-migration/migration-jobs/create index dc0567b83..4fb6ac16d 100644 --- a/gcloud/alpha/database-migration/migration-jobs/create +++ b/gcloud/alpha/database-migration/migration-jobs/create @@ -16,9 +16,9 @@ DESCRIPTION steps before creating the migration job: ▪ Create a source connection profile. See prerequisites here (https://cloud.google.com/database-migration/docs/mysql/configure-source-database). - ▪ Create a destination connection profile. For MySQL and PostgreSQL - migrations, use the cloudsql connection profile for DMS to create the - CloudSQL replica for you. + ▪ Create a destination connection profile. For migrating to Cloud SQL + for MySQL or Cloud SQL for PostgreSQL, use the cloudsql connection + profile for DMS to create the CloudSQL replica for you. ▪ Configure the connectivity method. See prerequisites here (https://cloud.google.com/database-migration/docs/mysql/configure-connectivity). diff --git a/gcloud/alpha/dataplex/datascan/help b/gcloud/alpha/dataplex/datascan/help index 891241b8f..19749e685 100644 --- a/gcloud/alpha/dataplex/datascan/help +++ b/gcloud/alpha/dataplex/datascan/help @@ -33,6 +33,9 @@ COMMANDS list (ALPHA) List Dataplex Datascan resources under a project. + run + (ALPHA) Run a Dataplex DataScan 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 diff --git a/gcloud/alpha/dataplex/datascan/jobs/describe b/gcloud/alpha/dataplex/datascan/jobs/describe index aa3946ccd..13b679600 100644 --- a/gcloud/alpha/dataplex/datascan/jobs/describe +++ b/gcloud/alpha/dataplex/datascan/jobs/describe @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha dataplex datascan jobs describe - (JOB : --datascan=DATASCAN --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + (JOB : --datascan=DATASCAN --location=LOCATION) [--view=VIEW] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Describe a Dataplex job running a particular datascan. @@ -12,12 +13,18 @@ DESCRIPTION Displays all details of a Dataplex job given a valid job ID. EXAMPLES - To describe a Dataplex job test-job running a datascan test-task in + To describe a Dataplex job test-job running a datascan test-datascan in location us-central1, run: $ gcloud alpha dataplex datascan jobs describe test-job \ --location=us-central1 --datascan=test-datascan + To describe the details of Dataplex job test-job running a datascan + test-datascan in location us-central1, run: + + $ gcloud alpha dataplex datascan jobs describe test-job \ + --location=us-central1 --datascan=test-datascan --view=FULL + POSITIONAL ARGUMENTS Job resource - Arguments and flags that define the Dataplex Job running a particular Datascan you want to retrieve. The arguments in this group can @@ -58,6 +65,17 @@ POSITIONAL ARGUMENTS ▸ provide the argument --location on the command line; ▸ set the property dataplex/location. +FLAGS + --view=VIEW + There are two possible views: 'basic' and 'full'. The default view is + 'basic'. VIEW must be one of: + + basic + Does not include spec and result data in response. + + full + Includes spec and result data in response. + 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/dataplex/datascan/run b/gcloud/alpha/dataplex/datascan/run new file mode 100644 index 000000000..0684c7d12 --- /dev/null +++ b/gcloud/alpha/dataplex/datascan/run @@ -0,0 +1,66 @@ +NAME + gcloud alpha dataplex datascan run - run a Dataplex DataScan resource + +SYNOPSIS + gcloud alpha dataplex datascan run (DATASCAN : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Run a Dataplex Datascan resource given a valid Datascan ID. + +EXAMPLES + To run a Dataplex Datascan test-datascan in location us-central1 , run: + + $ gcloud alpha dataplex datascan run test-datascan \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Datascan resource - Arguments and flags that define the Dataplex Datascan + you want to run. 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; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + DATASCAN + ID of the datascan or fully qualified identifier for the datascan. + + To set the datascan 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 + 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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 dataplex/v1 API. The full documentation for this API + can be found at: https://cloud.google.com/dataplex/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/firestore/databases/update b/gcloud/alpha/firestore/databases/update index 02683ecda..4502af501 100644 --- a/gcloud/alpha/firestore/databases/update +++ b/gcloud/alpha/firestore/databases/update @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha firestore databases update [--async] [--database=DATABASE] - [--type=TYPE] [GCLOUD_WIDE_FLAG ...] + [--delete-protection] [--type=TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update the database configuration of a Cloud Firestore database. @@ -39,6 +39,12 @@ FLAGS ▸ provide the argument --database on the command line; ▸ the default value of argument [--database] is (default). + --delete-protection + If set to true, the firestore database will be updated to have database + delete protection enabled. A database with delete protection enabled + cannot be deleted. You can disable the delete protection via + --no-delete-protection. + --type=TYPE The database type. TYPE must be one of: datastore-mode, firestore-native. diff --git a/gcloud/alpha/firestore/locations/help b/gcloud/alpha/firestore/locations/help index dd25f2a6d..ab99a13e1 100644 --- a/gcloud/alpha/firestore/locations/help +++ b/gcloud/alpha/firestore/locations/help @@ -23,5 +23,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 firestore locations diff --git a/gcloud/alpha/firestore/locations/list b/gcloud/alpha/firestore/locations/list index da87368eb..66f6e259d 100644 --- a/gcloud/alpha/firestore/locations/list +++ b/gcloud/alpha/firestore/locations/list @@ -3,10 +3,52 @@ NAME Cloud Firestore SYNOPSIS - gcloud alpha firestore locations list [GCLOUD_WIDE_FLAG ...] + gcloud alpha firestore locations list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] -DESCRIPTION - (ALPHA) List locations available to Google Cloud Firestore. +EXAMPLES + To list all Firestore locations with table. + + $ gcloud alpha firestore locations list \ + --format="table(locationId, displayName)" + + To list Firestore locations with a filter. + + $ gcloud alpha firestore locations list \ + --filter="locationId:us-west1" + +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, @@ -20,5 +62,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 firestore locations list diff --git a/gcloud/alpha/iam/workforce-pools/providers/create-oidc b/gcloud/alpha/iam/workforce-pools/providers/create-oidc index 2a3a50d1b..0c599ef41 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/create-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/create-oidc @@ -8,7 +8,9 @@ SYNOPSIS --attribute-mapping=[ATTRIBUTE_MAPPING,...] --client-id=CLIENT_ID --issuer-uri=ISSUER_URI [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + [--disabled] [--display-name=DISPLAY_NAME] + [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] + [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new OIDC workforce pool provider. @@ -25,7 +27,9 @@ EXAMPLES --description="My workforce pool provider description." \ --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" --client-id="client-id" \ - --issuer-uri="https://test-idp.com" + --issuer-uri="https://test-idp.com" \ + --web-sso-response-type=id-token \ + --web-sso-assertion-claims-behavior=only-id-token-claims POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to create. @@ -187,6 +191,20 @@ OPTIONAL FLAGS A display name for the workforce pool provider. Cannot exceed 32 characters in length. + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR + The behavior for how OIDC Claims are included in the assertion object + used for attribute mapping and attribute condition. Use + only-id-token-claims to include only ID token claims. + WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be one of: + assertion-claims-behavior-unspecified, only-id-token-claims. + + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE + Response Type to request for in the OIDC Authorization Request for web + sign-in. Use id-token to select the implicit flow + (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). + WEB_SSO_RESPONSE_TYPE must be one of: id-token, + response-type-unspecified. + 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/iam/workforce-pools/providers/update-oidc b/gcloud/alpha/iam/workforce-pools/providers/update-oidc index 1ccf436f4..da21d0a3c 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/update-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/update-oidc @@ -8,7 +8,9 @@ SYNOPSIS [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] [--client-id=CLIENT_ID] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] - [--issuer-uri=ISSUER_URI] [GCLOUD_WIDE_FLAG ...] + [--issuer-uri=ISSUER_URI] + [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] + [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update an OIDC workforce pool provider. @@ -25,7 +27,9 @@ EXAMPLES --description="My workforce pool provider description." \ --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" --client-id="client-id" \ - --issuer-uri="https://test-idp.com" + --issuer-uri="https://test-idp.com" \ + --web-sso-response-type=id-token \ + --web-sso-assertion-claims-behavior=only-id-token-claims POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to update. @@ -186,6 +190,20 @@ FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR + The behavior for how OIDC Claims are included in the assertion object + used for attribute mapping and attribute condition. Use + only-id-token-claims to include only ID token claims. + WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be one of: + assertion-claims-behavior-unspecified, only-id-token-claims. + + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE + Response Type to request for in the OIDC Authorization Request for web + sign-in. Use id-token to select the implicit flow + (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). + WEB_SSO_RESPONSE_TYPE must be one of: id-token, + response-type-unspecified. + 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/looker/help b/gcloud/alpha/looker/help new file mode 100644 index 000000000..a11a59896 --- /dev/null +++ b/gcloud/alpha/looker/help @@ -0,0 +1,31 @@ +NAME + gcloud alpha looker - manage Looker resources + +SYNOPSIS + gcloud alpha looker GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Looker resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + instances + (ALPHA) Manage Looker instances. + + operations + (ALPHA) Manage Looker operations. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker + diff --git a/gcloud/alpha/looker/instances/create b/gcloud/alpha/looker/instances/create new file mode 100644 index 000000000..3eba18746 --- /dev/null +++ b/gcloud/alpha/looker/instances/create @@ -0,0 +1,222 @@ +NAME + gcloud alpha looker instances create - create a Looker instance + +SYNOPSIS + gcloud alpha looker instances create (INSTANCE : --region=REGION) + --edition=EDITION --oauth-client-id=OAUTH_CLIENT_ID + --oauth-client-secret=OAUTH_CLIENT_SECRET [--async] + [--no-enable-public-ip] [--kms-key=KMS_KEY] + [--consumer-network=CONSUMER_NETWORK --enable-private-ip + : --reserved-range=RESERVED_RANGE] + [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE + --deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] + [--maintenance-window-day=MAINTENANCE_WINDOW_DAY + --maintenance-window-time=MAINTENANCE_WINDOW_TIME] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new Looker instance. + + This command can fail for the following reasons: + ▪ An instance with the same name already exists. + ▪ The active account does not have permission to create instances. + ▪ --async flag is not passed + +EXAMPLES + To create a basic tier instance with the name my-looker-instance in region + us-central-1 with an edition of "LOOKER_CORE_STANDARD", run: + + $ gcloud alpha looker instances create my-looker-instance \ + --region=us-central1 --edition="core-standard" \ + --oauth-client-id='looker' --oauth-client-secret='looker' \ + --async + + Note: It is recommended that the --async argument is provided when creating + a Looker instance. + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to create. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the instance. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +REQUIRED FLAGS + --edition=EDITION + The edition of the Looker instance. EDITION must be one of: + + advanced + This edition provides a full-feature edition for product + exploration and development. Scales as your organization and data + add complexity. + + core-trial + Trial edition of Looker. + + elite + This edition provides a full-feature edition for product + exploration and development. Drive your business through + operational analytics. + + looker-modeler + Standalone Model Service. + + standard + This edition provides a full-feature edition for product + exploration and development. Exceptional for all your Analytics. + + --oauth-client-id=OAUTH_CLIENT_ID + The client ID from an external OAuth application. + + OAuth Application Credentials - Looker Instance OAuth login settings. + Setup an OAuth app that will allow users to authenticate and access the + instance. For more information see: + https://developers.google.com/identity/protocols/oauth2/web-server#creatingcred + + --oauth-client-secret=OAUTH_CLIENT_SECRET + The client secret from an external OAuth application. + + OAuth Application Credentials - Looker Instance OAuth login settings. + Setup an OAuth app that will allow users to authenticate and access the + instance. For more information see: + https://developers.google.com/identity/protocols/oauth2/web-server#creatingcred + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --enable-public-ip + This specifies whether public IP is enabled on the Looker instance. + Enabled by default, use --no-enable-public-ip to disable. + + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the Looker instance and backups. The 'Looker Service + Agent' service account must hold permission 'Cloud KMS CryptoKey + Encrypter/Decrypter'. The arguments in this group can be used to specify + the attributes of this resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. To set the + kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + Private IP - Assigns an internal, Google-hosted VPC IP address. Private IP + connectivity requires additional APIs and permissions. Private IP cannot + be disabled once it has been enabled. If enabled, consumer-network must be + assigned. + + --consumer-network=CONSUMER_NETWORK + The network name within the consumer project. This MUST be delared if + enabling private IP. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --enable-private-ip + This specifies whether private IP is enabled on the Looker instance. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --reserved-range=RESERVED_RANGE + The name of a reserved IP address range within the consumer network + to be used for private service access connection. + + Deny Maintanence Period - You must allow at least 48 hours of maintenance + availability in a 60-day rolling window. Only contiguous availability + windows of at least two hours are considered. When setting a maintenance + exclusion please be aware that excluding application upgrades cannot + exceed 60-days and excluding infrastructure upgrades cannot exceed + 90-days. + + --deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE + End date of the deny maintenance period in format: YYYY-MM-DD + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE + Start date of the deny maintenance period in format: YYYY-MM-DD + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME + Time in UTC when the period starts and ends. A valid time of day must + be specified in 24hr format (ex: 13:00, 17:30, 23:45). + + This flag argument must be specified if any of the other arguments in + this group are specified. + + 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. + + --maintenance-window-day=MAINTENANCE_WINDOW_DAY + Day of week for maintenance window, in UTC time zone. To set the + maintenance-window-day attribute: + ▸ provide the argument --maintenance-window-day on the command + line. MAINTENANCE_WINDOW_DAY must be one of: friday, monday, + saturday, sunday, thursday, tuesday, wednesday. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --maintenance-window-time=MAINTENANCE_WINDOW_TIME + Hour of day for maintenance window, in UTC time zone. A valid time of + day must be specified in 24hr format (ex: 13:00, 17:30, 23:45). + Maintenance will be scheduled within 60 minutes. To set the + maintenance-window-time attribute: + ▸ provide the argument --maintenance-window-time on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1alpha1 API. The full documentation for this + API can be found at: https://looker.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker instances create + diff --git a/gcloud/alpha/looker/instances/delete b/gcloud/alpha/looker/instances/delete new file mode 100644 index 000000000..2054a1c77 --- /dev/null +++ b/gcloud/alpha/looker/instances/delete @@ -0,0 +1,82 @@ +NAME + gcloud alpha looker instances delete - delete a Looker instance + +SYNOPSIS + gcloud alpha looker instances delete (INSTANCE : --region=REGION) [--async] + [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Looker instance. + + This command can fail for the following reasons: + ▪ The instance specified does not exist. + ▪ The active account does not have permission to access the given + instance. + +EXAMPLES + To delete an instance with the name my-looker-instance in your default + region, run: + + $ gcloud alpha looker instances delete my-looker-instance --async + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to delete. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the instance. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --force + Force delete an instance. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 looker/v1alpha1 API. The full documentation for this + API can be found at: https://looker.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker instances delete + diff --git a/gcloud/alpha/looker/instances/describe b/gcloud/alpha/looker/instances/describe new file mode 100644 index 000000000..ba32a7bcb --- /dev/null +++ b/gcloud/alpha/looker/instances/describe @@ -0,0 +1,77 @@ +NAME + gcloud alpha looker instances describe - show metadata for a Looker + +SYNOPSIS + gcloud alpha looker instances describe (INSTANCE : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show metadata for a Looker instance. + + Displays all metadata associated with a Looker instance given a valid + instance name. + + This command can fail for the following reasons: + ▪ The instance specified does not exist. + ▪ The active account does not have permission to access the given + instance. + +EXAMPLES + To display the metadata for an instance with the name my-looker-instance in + the default region, run: + + $ gcloud alpha looker instances describe my-looker-instance + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to describe. The arguments in this group can be used to specify + the attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the instance. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1alpha1 API. The full documentation for this + API can be found at: https://looker.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker instances describe + diff --git a/gcloud/alpha/looker/instances/export b/gcloud/alpha/looker/instances/export new file mode 100644 index 000000000..25b664322 --- /dev/null +++ b/gcloud/alpha/looker/instances/export @@ -0,0 +1,94 @@ +NAME + gcloud alpha looker instances export - export a Looker instance + +SYNOPSIS + gcloud alpha looker instances export (INSTANCE : --region=REGION) + --kms-key=KMS_KEY --target-gcs-uri=TARGET_GCS_URI + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The instance specified does not exist. + ▪ The active account does not have permission to access the given + instance. + ▪ The Google Cloud Storage bucket does not exist. + +EXAMPLES + To export an instance with the name my-looker-instance in the default + region, run: + + $ gcloud alpha looker instances export my-looker-instance \ + --target-gcs-uri='gs://bucketName/folderName' \ + --kms-key='projects/my-project/locations/us-central1/keyRings/my\ + -key-ring/cryptoKeys/my-key' + + Note that the kms-key flag should be the full name of the kms key. + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to export. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The region of the instance. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the Looker instance and backups. The 'Looker Service + Agent' service account must hold role 'Cloud KMS CryptoKey Encrypter'. The + arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + --kms-key=KMS_KEY + Fully qualified identifier (name) for the key. + + Export Destination - The path and storage where the export will be stored. + + This must be specified. + + --target-gcs-uri=TARGET_GCS_URI + The path to the folder in Google Cloud Storage where the export will + be stored. The URI is in the form gs://bucketName/folderName. The + Looker Service Agent should have the role Storage Object Creator. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 looker instances export + diff --git a/gcloud/alpha/looker/instances/help b/gcloud/alpha/looker/instances/help new file mode 100644 index 000000000..fb4398599 --- /dev/null +++ b/gcloud/alpha/looker/instances/help @@ -0,0 +1,89 @@ +NAME + gcloud alpha looker instances - manage Looker instances + +SYNOPSIS + gcloud alpha looker instances COMMAND [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To create an instance with the name my-looker-instance, with an edition of + "LOOKER_CORE_STANDARD", run: + + $ gcloud alpha looker instances create my-looker-instance \ + --oauth-client-id='looker' --oauth-client-secret='looker' \ + --edition="core-standard" --async + + Note: It is recommended that the --async argument is provided when creating + a Looker instance. + + To delete an instance with the name my-looker-instance, run: + + $ gcloud alpha looker instances delete my-looker-instance --async + + To display the details for an instance with name my-looker-instance, run: + + $ gcloud alpha looker instances describe my-looker-instance + + To restart an instance with the name my-looker-instance, run: + + $ gcloud alpha looker instances restart my-looker-instance --async + + To update an instance with the name my-looker-instance, run: + + $ gcloud alpha looker instances update my-looker-instance --async + + To export an instance with the name my-looker-instance, run: + + $ gcloud alpha looker instances export my-looker-instance \ + --target-gcs-uri='gs://bucketName/folderName' \ + --kms-key='projects/my-project/locations/us-central1/keyRings/my\ + -key-ring/cryptoKeys/my-key' + + To import an instance with the name my-looker-instance, run: + + $ gcloud alpha looker instances import my-looker-instance \ + --source-gcs-uri='gs://bucketName/folderName' + + To list all the instances, run: + + $ gcloud alpha looker instances list + +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 Looker instance. + + delete + (ALPHA) Delete a Looker instance. + + describe + (ALPHA) Show metadata for a Looker. + + export + (ALPHA) Export a Looker instance. + + import + (ALPHA) Import a Looker instance. + + list + (ALPHA) List Looker instances. + + restart + (ALPHA) Restart a Looker instance. + + update + (ALPHA) Update a Looker instance. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker instances + diff --git a/gcloud/alpha/looker/instances/import b/gcloud/alpha/looker/instances/import new file mode 100644 index 000000000..1cd557772 --- /dev/null +++ b/gcloud/alpha/looker/instances/import @@ -0,0 +1,78 @@ +NAME + gcloud alpha looker instances import - import a Looker instance + +SYNOPSIS + gcloud alpha looker instances import (INSTANCE : --region=REGION) + --source-gcs-uri=SOURCE_GCS_URI [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command can fail for the following reasons: + ▪ The instance specified does not exist. + ▪ The active account does not have permission to access the given + instance. + ▪ The Google Cloud Storage bucket does not exist. + +EXAMPLES + To import an instance with the name my-looker-instance in the default + region, run: + + $ gcloud alpha looker instances import my-looker-instance \ + --source-gcs-uri='gs://bucketName/folderName' + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to import. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The region of the instance. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + Import Destination - The path and storage where the import will be + retrieved from. + + This must be specified. + + --source-gcs-uri=SOURCE_GCS_URI + The path to the folder in Google Cloud Storage where the import will + be retrieved from. The URI is in the form gs://bucketName/folderName. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 looker instances import + diff --git a/gcloud/alpha/looker/instances/list b/gcloud/alpha/looker/instances/list new file mode 100644 index 000000000..ff3162955 --- /dev/null +++ b/gcloud/alpha/looker/instances/list @@ -0,0 +1,89 @@ +NAME + gcloud alpha looker instances list - list Looker instances + +SYNOPSIS + gcloud alpha looker instances list [--region=REGION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all Looker instances under the specified project and region. + + To specify the maximum number of instances to list, use the --limit flag. + +EXAMPLES + To list up to five instances, run: + + $ gcloud alpha looker instances list --limit=5 + +FLAGS + Region resource - The region of the instances to display. 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 --region on the command line with a fully + specified name; + ◆ set the property looker/region with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1alpha1 API. The full documentation for this + API can be found at: https://looker.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker instances list + diff --git a/gcloud/alpha/looker/instances/restart b/gcloud/alpha/looker/instances/restart new file mode 100644 index 000000000..bc7b0c8ea --- /dev/null +++ b/gcloud/alpha/looker/instances/restart @@ -0,0 +1,79 @@ +NAME + gcloud alpha looker instances restart - restart a Looker instance + +SYNOPSIS + gcloud alpha looker instances restart (INSTANCE : --region=REGION) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Restart for a Looker instance. + + This command can fail for the following reasons: + ▪ The instance specified does not exist. + ▪ The active account does not have permission to access the given + instance. + +EXAMPLES + To restart an instance with the name my-looker-instance in the default + region, run: + + $ gcloud alpha looker instances restart my-looker-instance --async + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to describe. The arguments in this group can be used to specify + the attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the instance. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +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 looker/v1alpha1 API. The full documentation for this + API can be found at: https://looker.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker instances restart + diff --git a/gcloud/alpha/looker/instances/update b/gcloud/alpha/looker/instances/update new file mode 100644 index 000000000..b947f6be8 --- /dev/null +++ b/gcloud/alpha/looker/instances/update @@ -0,0 +1,198 @@ +NAME + gcloud alpha looker instances update - update a Looker instance + +SYNOPSIS + gcloud alpha looker instances update (INSTANCE : --region=REGION) + [--allowed-email-domains=[ALLOWED_EMAIL_DOMAINS,...]] [--async] + [--custom-domain=CUSTOM_DOMAIN] [--enable-public-ip] + [--add-developer-users=ADD_DEVELOPER_USERS + --add-standard-users=ADD_STANDARD_USERS + --add-viewer-users=ADD_VIEWER_USERS] + [--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] + [--maintenance-window-day=MAINTENANCE_WINDOW_DAY + --maintenance-window-time=MAINTENANCE_WINDOW_TIME] + [--oauth-client-id=OAUTH_CLIENT_ID + --oauth-client-secret=OAUTH_CLIENT_SECRET] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update the metadata and/or configuration parameters of a Looker + instance. + + This command can fail for the following reasons: + ▪ The instance specified does not exist. + ▪ The active account does not have permission to update the given + instance. + +EXAMPLES + To update the maintenance window to Sunday at 11:00 PM for a Looker + instance with the name my-looker-instance, run: + + $ gcloud alpha looker instances update my-looker-instance \ + --maintenance-window-day=sunday \ + --maintenance-window-time='23:00' --async + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to update. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the instance. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +FLAGS + Email Domain Allowlist for Scheduled Content - Define the email domains to + which your users can deliver Looker (Google Cloud core) content. + + --allowed-email-domains=[ALLOWED_EMAIL_DOMAINS,...] + This specifies the entire allowed email domain list. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + Custom Domains - Looker (Google Cloud core) lets you serve your + application through a custom domain. If you use a custom domain, Google + will provide a managed auto-renewing SSL certificate for security. + + DNS changes can take up to 24 hours to take effect. Your SSL certificate + will take several minutes to activate. Note that you must get the Type A + DNS Record from the Google Cloud Console and update with your domain + registrar for your custom domain to work properly. + + --custom-domain=CUSTOM_DOMAIN + Domain name wanted to serve the Looker instance. + + --enable-public-ip + This specifies whether public IP is enabled on the Looker instance. + + User Allocations - There are ten Standard and two Developer users included + in the cost of the product. You can allocate additional Standard, Viewer, + and Developer users for this instance. It is an optional step and can be + modified later. + + With the Standard edition of Looker (Google Cloud core), you can provision + up to 50 total users, distributed across Viewer, Standard, and Developer. + + --add-developer-users=ADD_DEVELOPER_USERS + Number of additional Developer Users to allocate to the Looker + Instance. + + --add-standard-users=ADD_STANDARD_USERS + Number of additional Standard Users to allocate to the Looker + Instance. + + --add-viewer-users=ADD_VIEWER_USERS + Number of additional Viewer Users to allocate to the Looker Instance. + + Deny Maintanence Period - You must allow at least 48 hours of maintenance + availability in a 60-day rolling window. Only contiguous availability + windows of at least two hours are considered. When setting a maintenance + exclusion please be aware that excluding application upgrades cannot + exceed 60-days and excluding infrastructure upgrades cannot exceed + 90-days. + + --deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE + End date of the deny maintenance period in format: YYYY-MM-DD + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE + Start date of the deny maintenance period in format: YYYY-MM-DD + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME + Time in UTC when the period starts and ends. A valid time of day must + be specified in 24hr format (ex: 13:00, 17:30, 23:45). + + This flag argument must be specified if any of the other arguments in + this group are specified. + + 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. + + --maintenance-window-day=MAINTENANCE_WINDOW_DAY + Day of the week for the maintenance window, in UTC time zone. + MAINTENANCE_WINDOW_DAY must be one of: friday, monday, saturday, + sunday, thursday, tuesday, wednesday. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --maintenance-window-time=MAINTENANCE_WINDOW_TIME + Hour of day for maintenance window, in UTC time zone. A valid time of + day must be specified in 24hr format (ex: 13:00, 17:30, 23:45). + Maintenance will be scheduled within 60 minutes. To set the + maintenance-window-time attribute: + ▸ provide the argument --maintenance-window-time on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + OAuth Application Credentials - Looker Instance OAuth login settings. + Setup an OAuth app that will allow users to authenticate and access the + instance. For more information see: + https://developers.google.com/identity/protocols/oauth2/web-server#creatingcred + + --oauth-client-id=OAUTH_CLIENT_ID + The client ID from an external OAuth application. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --oauth-client-secret=OAUTH_CLIENT_SECRET + The client secret from an external OAuth application. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1alpha1 API. The full documentation for this + API can be found at: https://looker.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker instances update + diff --git a/gcloud/alpha/looker/operations/cancel b/gcloud/alpha/looker/operations/cancel new file mode 100644 index 000000000..ff0f73dd2 --- /dev/null +++ b/gcloud/alpha/looker/operations/cancel @@ -0,0 +1,70 @@ +NAME + gcloud alpha looker operations cancel - cancel a Looker import or export + operation + +SYNOPSIS + gcloud alpha looker operations cancel (OPERATION : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancel a Looker import or export operation. + +EXAMPLES + To cancel an operation named my-looker-operation in the default region, + run: + + $ gcloud alpha looker operations cancel my-looker-operation + +POSITIONAL ARGUMENTS + Operation resource - Arguments and flags that specify the Looker operation + you want to describe. The arguments in this group can be used to specify + the attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument operation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the operation. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1alpha1 API. The full documentation for this + API can be found at: https://looker.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker operations cancel + diff --git a/gcloud/alpha/looker/operations/describe b/gcloud/alpha/looker/operations/describe new file mode 100644 index 000000000..97cd4fc06 --- /dev/null +++ b/gcloud/alpha/looker/operations/describe @@ -0,0 +1,76 @@ +NAME + gcloud alpha looker operations describe - show metadata for a Looker + operation + +SYNOPSIS + gcloud alpha looker operations describe (OPERATION : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Display all metadata associated with a Looker operation given a + valid operation name. + + This command can fail for the following reasons: + ▪ The operation specified does not exist. + ▪ The active account does not have permission to access the given + operation. + +EXAMPLES + To display the metadata for an operation named my-looker-operation in the + default region, run: + + $ gcloud alpha looker operations describe my-looker-operation + +POSITIONAL ARGUMENTS + Operation resource - Arguments and flags that specify the Looker operation + you want to describe. The arguments in this group can be used to specify + the attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument operation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the operation. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1alpha1 API. The full documentation for this + API can be found at: https://looker.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker operations describe + diff --git a/gcloud/alpha/looker/operations/help b/gcloud/alpha/looker/operations/help new file mode 100644 index 000000000..5c4b4f751 --- /dev/null +++ b/gcloud/alpha/looker/operations/help @@ -0,0 +1,40 @@ +NAME + gcloud alpha looker operations - manage Looker operations + +SYNOPSIS + gcloud alpha looker operations COMMAND [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To display the details for an operation with name my-looker-op, run: + + $ gcloud alpha looker operations describe my-looker-op + + To list all the operations, run: + + $ gcloud alpha looker operations list + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + (ALPHA) Cancel a Looker import or export operation. + + describe + (ALPHA) Show metadata for a Looker operation. + + list + (ALPHA) List Looker operations. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker operations + diff --git a/gcloud/alpha/looker/operations/list b/gcloud/alpha/looker/operations/list new file mode 100644 index 000000000..0694e2149 --- /dev/null +++ b/gcloud/alpha/looker/operations/list @@ -0,0 +1,89 @@ +NAME + gcloud alpha looker operations list - list Looker operations + +SYNOPSIS + gcloud alpha looker operations list [--region=REGION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all Looker operations under the specified project and region. + + To specify the maximum number of operations to list, use the --limit flag. + +EXAMPLES + To list up to five operations, run: + + $ gcloud alpha looker operations list --limit=5 + +FLAGS + Region resource - The region of the operations to display. 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 --region on the command line with a fully + specified name; + ◆ set the property looker/region with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1alpha1 API. The full documentation for this + API can be found at: https://looker.com/ + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud looker operations list + diff --git a/gcloud/alpha/metastore/operations/cancel b/gcloud/alpha/metastore/operations/cancel new file mode 100644 index 000000000..4ef528161 --- /dev/null +++ b/gcloud/alpha/metastore/operations/cancel @@ -0,0 +1,63 @@ +NAME + gcloud alpha metastore operations cancel - cancel a Dataproc Metastore + operation + +SYNOPSIS + gcloud alpha metastore operations cancel (OPERATION : --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancel a Dataproc Metastore operation. + +EXAMPLES + To cancel an active Dataproc Metastore operation with the name operation-1 + in location us-central1, run: + + $ gcloud alpha metastore operations cancel operation-1 \ + --location=us-central1 + +POSITIONAL ARGUMENTS + Operation resource - The operation cancel. The arguments in this group can + be used to specify the attributes of this resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument operation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location to which the operation belongs. + + To set the location attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property metastore/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. + diff --git a/gcloud/alpha/metastore/operations/help b/gcloud/alpha/metastore/operations/help index b8df0d956..8c5c6ea03 100644 --- a/gcloud/alpha/metastore/operations/help +++ b/gcloud/alpha/metastore/operations/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + cancel + (ALPHA) Cancel a Dataproc Metastore operation. + delete (ALPHA) Delete one or more completed Dataproc Metastore operations. diff --git a/gcloud/alpha/pubsub/subscriptions/pull b/gcloud/alpha/pubsub/subscriptions/pull index cc6694c07..e99634c37 100644 --- a/gcloud/alpha/pubsub/subscriptions/pull +++ b/gcloud/alpha/pubsub/subscriptions/pull @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha pubsub subscriptions pull SUBSCRIPTION [--auto-ack] - [--max-messages=MAX_MESSAGES; default=1] [--wait] [--filter=EXPRESSION] + [--max-messages=MAX_MESSAGES; default=1] + [--return-immediately | --no-wait] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -49,9 +50,24 @@ FLAGS --max-messages is deprecated. Please use --limit instead. - --wait - Wait (for a bounded amount of time) for new messages from the - subscription, if there are none. + Pull timeout behavior. + + At most one of these can be specified: + + --return-immediately + If this flag is set, the system responds immediately with any + messages readily available in memory buffers. If no messages are + available in the buffers, returns an empty list of messages as + response, even if having messages in the backlog. Do not set this + flag as it adversely impacts the performance of pull. + + --wait + (DEPRECATED) Wait (for a bounded amount of time) for new messages + from the subscription, if there are none. + + --wait is deprecated. This flag is non-operational, as the wait + behavior is now the default. Enabled by default, use --no-wait to + disable. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index bcefc808a..4689e273c 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -176,7 +176,9 @@ FLAGS --port=PORT Container port to receive requests at. Also sets the $PORT environment variable. Must be a number between 1 and 65535, inclusive. To unset - this field, pass the special value "default". + this field, pass the special value "default". If updating an existing + service with a TCP startup probe pointing to the previous container + port, this will also update the probe port. --service-account=SERVICE_ACCOUNT Service account associated with the revision of the service. The diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 83a5573a8..e4bcbb420 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -170,7 +170,9 @@ FLAGS --port=PORT Container port to receive requests at. Also sets the $PORT environment variable. Must be a number between 1 and 65535, inclusive. To unset - this field, pass the special value "default". + this field, pass the special value "default". If updating an existing + service with a TCP startup probe pointing to the previous container + port, this will also update the probe port. --service-account=SERVICE_ACCOUNT Service account associated with the revision of the service. The diff --git a/gcloud/alpha/sql/import/sql b/gcloud/alpha/sql/import/sql index 04743088e..b82c82dfb 100644 --- a/gcloud/alpha/sql/import/sql +++ b/gcloud/alpha/sql/import/sql @@ -40,10 +40,10 @@ FLAGS complete. --database=DATABASE, -d DATABASE - Database to which the import is made. If not set, it is assumed that - the database is specified in the file to be imported. If your SQL dump - file includes a database statement, it will override the database set - in this flag. + Database to which the import is made. The database needs to be created + before importing. If not set, it is assumed that the database is + specified in the file to be imported. If your SQL dump file includes a + database statement, it will override the database set in this flag. --user=USER PostgreSQL user for this import operation. diff --git a/gcloud/alpha/sql/instances/import b/gcloud/alpha/sql/instances/import index 964d0f2b7..bbba9f4d2 100644 --- a/gcloud/alpha/sql/instances/import +++ b/gcloud/alpha/sql/instances/import @@ -37,10 +37,10 @@ FLAGS complete. --database=DATABASE, -d DATABASE - Database to which the import is made. If not set, it is assumed that - the database is specified in the file to be imported. If your SQL dump - file includes a database statement, it will override the database set - in this flag. + Database to which the import is made. The database needs to be created + before importing. If not set, it is assumed that the database is + specified in the file to be imported. If your SQL dump file includes a + database statement, it will override the database set in this flag. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/alloydb/help b/gcloud/beta/alloydb/help index 2e6923769..157abb4b7 100644 --- a/gcloud/beta/alloydb/help +++ b/gcloud/beta/alloydb/help @@ -34,6 +34,9 @@ GROUPS operations (BETA) Provide commands for managing AlloyDB operations. + users + (BETA) Provide commands for managing AlloyDB users. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/alloydb/users/create b/gcloud/beta/alloydb/users/create new file mode 100644 index 000000000..6ad209569 --- /dev/null +++ b/gcloud/beta/alloydb/users/create @@ -0,0 +1,67 @@ +NAME + gcloud beta alloydb users create - creates a user in a given cluster + +SYNOPSIS + gcloud beta alloydb users create USERNAME --cluster=CLUSTER --region=REGION + [--db-roles=[ROLE,...]] [--password=PASSWORD] [--superuser=SUPERUSER] + [--type=TYPE; default="BUILT_IN"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Creates a user in a given cluster with specified username, cluster, + region, type, and password. + +EXAMPLES + To create a new user, run: + + $ gcloud beta alloydb users create my-username \ + --cluster=my-cluster --region=us-central1 --password=postgres + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +OPTIONAL FLAGS + --db-roles=[ROLE,...] + Comma separated list of database roles this new user will be granted + upon creation. + + --password=PASSWORD + Password for this database user. + + --superuser=SUPERUSER + If true, new user will have AlloyDB superuser privileges. Default value + is false. + + --type=TYPE; default="BUILT_IN" + Type corresponds to the user type. TYPE must be one of: + + BUILT_IN + This database user can authenticate via password-based + authentication + IAM_BASED + This database user can authenticate via IAM-based authentication + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 alloydb users create + + $ gcloud alpha alloydb users create + diff --git a/gcloud/beta/alloydb/users/delete b/gcloud/beta/alloydb/users/delete new file mode 100644 index 000000000..22bf0681b --- /dev/null +++ b/gcloud/beta/alloydb/users/delete @@ -0,0 +1,45 @@ +NAME + gcloud beta alloydb users delete - deletes an AlloyDB user in a given + cluster + +SYNOPSIS + gcloud beta alloydb users delete USERNAME --cluster=CLUSTER --region=REGION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes an AlloyDB user in a given cluster. + +EXAMPLES + To delete an user, run: + + $ gcloud beta alloydb users delete my-username \ + --cluster=my-cluster --region=us-central1 + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud alloydb users delete + + $ gcloud alpha alloydb users delete + diff --git a/gcloud/beta/alloydb/users/help b/gcloud/beta/alloydb/users/help new file mode 100644 index 000000000..ec22febe6 --- /dev/null +++ b/gcloud/beta/alloydb/users/help @@ -0,0 +1,47 @@ +NAME + gcloud beta alloydb users - provide commands for managing AlloyDB users + +SYNOPSIS + gcloud beta alloydb users COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Provide commands for managing AlloyDB users including creating, + configuring, getting, listing, and deleting users. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Creates a user in a given cluster. + + delete + (BETA) Deletes an AlloyDB user in a given cluster. + + list + (BETA) Lists AlloyDB users in a given cluster. + + set-password + (BETA) Update an AlloyDB user's password within a given cluster and + region. + + set-roles + (BETA) Update an AlloyDB user's database roles within a given cluster + and region. + + set-superuser + (BETA) Update an AlloyDB user's superuser role within a given cluster + and region. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud alloydb users + + $ gcloud alpha alloydb users + diff --git a/gcloud/beta/alloydb/users/list b/gcloud/beta/alloydb/users/list new file mode 100644 index 000000000..0be677568 --- /dev/null +++ b/gcloud/beta/alloydb/users/list @@ -0,0 +1,73 @@ +NAME + gcloud beta alloydb users list - lists AlloyDB users in a given cluster + +SYNOPSIS + gcloud beta alloydb users list --cluster=CLUSTER --region=REGION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Lists AlloyDB users in a given cluster. + +EXAMPLES + To list users, run: + + $ gcloud beta alloydb users list --cluster=my-cluster \ + --region=us-central1 + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +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 alloydb users list + + $ gcloud alpha alloydb users list + diff --git a/gcloud/beta/alloydb/users/set-password b/gcloud/beta/alloydb/users/set-password new file mode 100644 index 000000000..f32a34739 --- /dev/null +++ b/gcloud/beta/alloydb/users/set-password @@ -0,0 +1,48 @@ +NAME + gcloud beta alloydb users set-password - update an AlloyDB user's password + within a given cluster and region + +SYNOPSIS + gcloud beta alloydb users set-password USERNAME --cluster=CLUSTER + --password=PASSWORD --region=REGION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an AlloyDB user's password within a given cluster and region. + +EXAMPLES + To update a user's password, run: + + $ gcloud beta alloydb users set-password my-username \ + --cluster=my-cluster --region=us-central1 --password=postgres + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --password=PASSWORD + Password for this database user. + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud alloydb users set-password + + $ gcloud alpha alloydb users set-password + diff --git a/gcloud/beta/alloydb/users/set-roles b/gcloud/beta/alloydb/users/set-roles new file mode 100644 index 000000000..07ddb62d9 --- /dev/null +++ b/gcloud/beta/alloydb/users/set-roles @@ -0,0 +1,50 @@ +NAME + gcloud beta alloydb users set-roles - update an AlloyDB user's database + roles within a given cluster and region + +SYNOPSIS + gcloud beta alloydb users set-roles USERNAME --cluster=CLUSTER + --db-roles=[ROLE,...] --region=REGION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an AlloyDB user's database roles within a given cluster and + region. + +EXAMPLES + To update a user's database roles, run: + + $ gcloud beta alloydb users set-roles my-username \ + --cluster=my-cluster --region=us-central1 --db-roles=role1,role2 + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --db-roles=[ROLE,...] + Comma separated list of database roles this new user will be granted + upon creation. + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 alloydb users set-roles + + $ gcloud alpha alloydb users set-roles + diff --git a/gcloud/beta/alloydb/users/set-superuser b/gcloud/beta/alloydb/users/set-superuser new file mode 100644 index 000000000..00d38369f --- /dev/null +++ b/gcloud/beta/alloydb/users/set-superuser @@ -0,0 +1,49 @@ +NAME + gcloud beta alloydb users set-superuser - update an AlloyDB user's + superuser role within a given cluster and region + +SYNOPSIS + gcloud beta alloydb users set-superuser USERNAME --cluster=CLUSTER + --region=REGION --superuser=SUPERUSER [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an AlloyDB user's superuser role within a given cluster and + region. + +EXAMPLES + To update a user's superuser role, run: + + $ gcloud beta alloydb users set-superuser my-username \ + --cluster=my-cluster --region=us-central1 --superuser=true/false + +POSITIONAL ARGUMENTS + USERNAME + AlloyDB username + +REQUIRED FLAGS + --cluster=CLUSTER + AlloyDB cluster ID + + --region=REGION + Regional location (e.g. asia-east1, us-east1). See the full list of + regions at https://cloud.google.com/sql/docs/instance-locations. + + --superuser=SUPERUSER + If true, user will have AlloyDB superuser privileges + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 alloydb users set-superuser + + $ gcloud alpha alloydb users set-superuser + diff --git a/gcloud/beta/builds/submit b/gcloud/beta/builds/submit index 5fb2e9657..3b42351dd 100644 --- a/gcloud/beta/builds/submit +++ b/gcloud/beta/builds/submit @@ -6,9 +6,11 @@ SYNOPSIS [--default-buckets-behavior=DEFAULT_BUCKETS_BEHAVIOR] [--disk-size=DISK_SIZE] [--gcs-log-dir=GCS_LOG_DIR] [--gcs-source-staging-dir=GCS_SOURCE_STAGING_DIR] - [--ignore-file=IGNORE_FILE] [--machine-type=MACHINE_TYPE] - [--region=REGION] [--substitutions=[KEY=VALUE,...]] [--suppress-logs] - [--timeout=TIMEOUT] [--worker-pool=WORKER_POOL] + [--git-source-dir=GIT_SOURCE_DIR] + [--git-source-revision=GIT_SOURCE_REVISION] [--ignore-file=IGNORE_FILE] + [--machine-type=MACHINE_TYPE] [--region=REGION] + [--substitutions=[KEY=VALUE,...]] [--suppress-logs] [--timeout=TIMEOUT] + [--worker-pool=WORKER_POOL] [--config=CONFIG; default="cloudbuild.yaml" | --pack=[builder=BUILDER],[env=ENV],[image=IMAGE] | --tag=TAG, -t TAG] [GCLOUD_WIDE_FLAG ...] @@ -45,15 +47,15 @@ POSITIONAL ARGUMENTS [SOURCE] The location of the source to build. The location can be a directory - on a local disk or a gzipped archive file (.tar.gz) in Google Cloud - Storage. If the source is a local directory, this command skips the - files specified in the --ignore-file. If --ignore-file is not - specified, use.gcloudignore file. If a .gcloudignore file is absent - and a .gitignore file is present in the local source directory, - gcloud will use a generated Git-compatible .gcloudignore file that - respects your .gitignored files. The global .gitignore is not - respected. For more information on .gcloudignore, see gcloud topic - gcloudignore. + on a local disk, a gzipped archive file (.tar.gz) in Google Cloud + Storage, or a Git repo url starting with http:// or https://. If the + source is a local directory, this command skips the files specified + in the --ignore-file. If --ignore-file is not specified, + use.gcloudignore file. If a .gcloudignore file is absent and a + .gitignore file is present in the local source directory, gcloud will + use a generated Git-compatible .gcloudignore file that respects your + .gitignored files. The global .gitignore is not respected. For more + information on .gcloudignore, see gcloud topic gcloudignore. --no-source Specify that no source should be uploaded with this build. @@ -95,6 +97,22 @@ FLAGS set --default-buckets-behavior to REGIONAL_USER_OWNED_BUCKET and builds/region is not global. + --git-source-dir=GIT_SOURCE_DIR + Directory, relative to the source root, in which to run the build. This + must be a relative path. If a step's dir is specified and is an + absolute path, this value is ignored for that step's execution. + + --git-source-revision=GIT_SOURCE_REVISION + Revision to fetch from the Git repository such as a branch, a tag, a + commit SHA, or any Git ref to run the build. + + Cloud Build uses git fetch to fetch the revision from the Git + repository; therefore make sure that the string you provide for + revision is parsable by the command. For information on string values + accepted by git fetch, see + https://git-scm.com/docs/gitrevisions#_specifying_revisions. For + information on git fetch, see https://git-scm.com/docs/git-fetch. + --ignore-file=IGNORE_FILE Override the .gcloudignore file and use the specified file instead. diff --git a/gcloud/beta/compute/addresses/help b/gcloud/beta/compute/addresses/help index 84c188819..f4b1da1fc 100644 --- a/gcloud/beta/compute/addresses/help +++ b/gcloud/beta/compute/addresses/help @@ -34,6 +34,9 @@ COMMANDS list (BETA) List addresses. + move + (BETA) Move an address to another project. + update (BETA) Update a Compute Engine address. diff --git a/gcloud/beta/compute/addresses/move b/gcloud/beta/compute/addresses/move new file mode 100644 index 000000000..a2a33e9c9 --- /dev/null +++ b/gcloud/beta/compute/addresses/move @@ -0,0 +1,57 @@ +NAME + gcloud beta compute addresses move - move an address to another project + +SYNOPSIS + gcloud beta compute addresses move NAME --target-project=TARGET_PROJECT + [--description=DESCRIPTION] [--new-name=NEW_NAME] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + The following command moves address external-ip1 in region us-central1 to + project test-playground with new address name test-ip1: + + $ gcloud beta compute addresses move external-ip1 \ + --new-name=test-ip1 --target-project=test-playground \ + --region=us-central1 + +POSITIONAL ARGUMENTS + NAME + Name of the address to operate on. + +REQUIRED FLAGS + --target-project=TARGET_PROJECT + The target project to move address to. It can be either a project name + or a project numerical ID. It must not be the same as the current + project. + +OPTIONAL FLAGS + --description=DESCRIPTION + Description of moved new address. + + --new-name=NEW_NAME + Name of moved new address. If not specified, current address's name is + used. + + At most one of these can be specified: + + --global + If set, the address is global. + + --region=REGION + Region of the address to operate on. Overrides the default + compute/region property value for this command invocation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha compute addresses move + diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 7a497f087..aca078607 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -343,6 +343,13 @@ FLAGS among other restrictions. For more information, see https://cloud.google.com/compute/docs/disks/sharing-disks-between-vms. + replica-zones + Required for each regional disk associated with the instance. + Specify the URLs of the zones where the disk should be replicated + to. You must provide exactly two replica zones, and one zone must + be the same as the instance zone. You can't use this option with + boot disks. + --csek-key-file=FILE Path to a Customer-Supplied Encryption Key (CSEK) key file that maps Compute Engine resources to user managed keys to be used when creating, diff --git a/gcloud/beta/compute/routers/add-bgp-peer b/gcloud/beta/compute/routers/add-bgp-peer index 15b33c0b8..54e398c83 100644 --- a/gcloud/beta/compute/routers/add-bgp-peer +++ b/gcloud/beta/compute/routers/add-bgp-peer @@ -6,7 +6,8 @@ SYNOPSIS gcloud beta compute routers add-bgp-peer NAME --interface=INTERFACE --peer-asn=PEER_ASN --peer-name=PEER_NAME [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] - [--advertisement-mode=MODE] [--async] [--[no-]enable-ipv6] + [--advertisement-mode=MODE] [--async] + [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv6] [--[no-]enabled] [--instance=INSTANCE] [--instance-zone=INSTANCE_ZONE] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] @@ -14,6 +15,7 @@ SYNOPSIS [--peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] + [--set-custom-learned-route-ranges=[CIDR_RANGE,...]] [--bfd-min-receive-interval=BFD_MIN_RECEIVE_INTERVAL --bfd-min-transmit-interval=BFD_MIN_TRANSMIT_INTERVAL --bfd-multiplier=BFD_MULTIPLIER @@ -58,6 +60,12 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --custom-learned-route-priority=PRIORITY + An integral value 0 <= priority <= 65535, to be applied to all custom + learned route IP address ranges for this peer. If not specified, a + Google-managed priority value of 100 is used. The routes with the + lowest priority value win. + --[no-]enable-ipv6 If IPv6 is enabled, the peer connection can be established with IPv6 route exchange. If disabled, no IPv6 route exchange is allowed on any @@ -155,6 +163,14 @@ OPTIONAL FLAGS the range, use --set-advertisement-ranges=192.168.10.0/24=my-networks. This list can only be specified in custom advertisement mode. + --set-custom-learned-route-ranges=[CIDR_RANGE,...] + The list of user-defined custom learned route IP address ranges for + this peer. This list is a comma separated IP address ranges such as + 1.2.3.4,6.7.0.0/16,2001:db8:abcd:12::/64 where each IP address range + must be a valid CIDR-formatted prefix. If an IP address is provided + without a subnet mask, it is interpreted as a /32 singular IP address + range for IPv4, and /128 for IPv6. + Arguments to configure BFD (Bidirectional Forwarding Detection) settings: --bfd-min-receive-interval=BFD_MIN_RECEIVE_INTERVAL diff --git a/gcloud/beta/compute/routers/update-bgp-peer b/gcloud/beta/compute/routers/update-bgp-peer index 468e86d8f..387f1a7c0 100644 --- a/gcloud/beta/compute/routers/update-bgp-peer +++ b/gcloud/beta/compute/routers/update-bgp-peer @@ -6,17 +6,21 @@ SYNOPSIS gcloud beta compute routers update-bgp-peer NAME --peer-name=PEER_NAME [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] [--advertisement-mode=MODE] [--async] [--clear-md5-authentication-key] - [--[no-]enable-ipv6] [--[no-]enabled] [--interface=INTERFACE] - [--ip-address=IP_ADDRESS] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] + [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv6] + [--[no-]enabled] [--interface=INTERFACE] [--ip-address=IP_ADDRESS] + [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] [--peer-asn=PEER_ASN] [--peer-ip-address=PEER_IP_ADDRESS] [--peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] + [--set-custom-learned-route-ranges=[CIDR_RANGE,...]] [--add-advertisement-groups=[GROUP,...] | --add-advertisement-ranges=[CIDR_RANGE=DESC,...] | --remove-advertisement-groups=[GROUP,...] | --remove-advertisement-ranges=[CIDR_RANGE,...]] + [--add-custom-learned-route-ranges=[CIDR_RANGE,...] + | --remove-custom-learned-route-ranges=[CIDR_RANGE,...]] [--bfd-min-receive-interval=BFD_MIN_RECEIVE_INTERVAL --bfd-min-transmit-interval=BFD_MIN_TRANSMIT_INTERVAL --bfd-multiplier=BFD_MULTIPLIER @@ -57,6 +61,12 @@ OPTIONAL FLAGS --clear-md5-authentication-key If specified, remove MD5 authentication from the BGP peer. + --custom-learned-route-priority=PRIORITY + An integral value 0 <= priority <= 65535, to be applied to all custom + learned route IP address ranges for this peer. If not specified, a + Google-managed priority value of 100 is used. The routes with the + lowest priority value win. + --[no-]enable-ipv6 If IPv6 is enabled, the peer connection can be established with IPv6 route exchange. If disabled, no IPv6 route exchange is allowed on any @@ -141,6 +151,14 @@ OPTIONAL FLAGS the range, use --set-advertisement-ranges=192.168.10.0/24=my-networks. This list can only be specified in custom advertisement mode. + --set-custom-learned-route-ranges=[CIDR_RANGE,...] + The list of user-defined custom learned route IP address ranges for + this peer. This list is a comma separated IP address ranges such as + 1.2.3.4,6.7.0.0/16,2001:db8:abcd:12::/64 where each IP address range + must be a valid CIDR-formatted prefix. If an IP address is provided + without a subnet mask, it is interpreted as a /32 singular IP address + range for IPv4, and /128 for IPv6. + At most one of these can be specified: --add-advertisement-groups=[GROUP,...] @@ -181,6 +199,24 @@ OPTIONAL FLAGS exist in the current set of custom advertisements. This field can only be specified in custom advertisement mode. + At most one of these can be specified: + + --add-custom-learned-route-ranges=[CIDR_RANGE,...] + A list of user-defined custom learned route IP address ranges to be + added to this peer. This list is a comma separated IP address ranges + such as 1.2.3.4,6.7.0.0/16,2001:db8:abcd:12::/64 where each IP + address range must be a valid CIDR-formatted prefix. If an IP address + is provided without a subnet mask, it is interpreted as a /32 + singular IP address range for IPv4, and /128 for IPv6. + + --remove-custom-learned-route-ranges=[CIDR_RANGE,...] + A list of user-defined custom learned route IP address ranges to be + removed from this peer. This list is a comma separated IP address + ranges such as 1.2.3.4,6.7.0.0/16,2001:db8:abcd:12::/64 where each IP + address range must be a valid CIDR-formatted prefix. If an IP address + is provided without a subnet mask, it is interpreted as a /32 + singular IP address range for IPv4, and /128 for IPv6. + Arguments to update BFD (Bidirectional Forwarding Detection) settings: --bfd-min-receive-interval=BFD_MIN_RECEIVE_INTERVAL diff --git a/gcloud/beta/compute/security-policies/update b/gcloud/beta/compute/security-policies/update index c9adf9349..4e54ceef5 100644 --- a/gcloud/beta/compute/security-policies/update +++ b/gcloud/beta/compute/security-policies/update @@ -15,6 +15,7 @@ SYNOPSIS [--log-level=LOG_LEVEL] [--network-ddos-protection=NETWORK_DDOS_PROTECTION] [--recaptcha-redirect-site-key=RECAPTCHA_REDIRECT_SITE_KEY] + [--user-ip-request-headers=[USER_IP_REQUEST_HEADER,...]] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -82,6 +83,10 @@ FLAGS The reCAPTCHA site key to be used for rules using the redirect action and the google-recaptcha redirect type under the security policy. + --user-ip-request-headers=[USER_IP_REQUEST_HEADER,...] + A comma-separated list of request header names to use for resolving the + caller's user IP address. + At most one of these can be specified: --global diff --git a/gcloud/beta/container/clusters/create-auto b/gcloud/beta/container/clusters/create-auto index 0e99e3370..5877df1e8 100644 --- a/gcloud/beta/container/clusters/create-auto +++ b/gcloud/beta/container/clusters/create-auto @@ -13,10 +13,11 @@ SYNOPSIS [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--enable-fleet] [--enable-google-cloud-access] [--enable-kubernetes-unstable-apis=API,[API,...]] - [--fleet-project=PROJECT_ID_OR_NUMBER] [--network=NETWORK] - [--private-endpoint-subnetwork=NAME] [--release-channel=CHANNEL] - [--security-group=SECURITY_GROUP] [--services-ipv4-cidr=CIDR] - [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] + [--enable-master-global-access] [--fleet-project=PROJECT_ID_OR_NUMBER] + [--network=NETWORK] [--private-endpoint-subnetwork=NAME] + [--release-channel=CHANNEL] [--security-group=SECURITY_GROUP] + [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] + [--subnetwork=SUBNETWORK] [--binauthz-evaluation-mode=BINAUTHZ_EVALUATION_MODE --binauthz-policy=BINAUTHZ_POLICY] [--enable-master-authorized-networks @@ -167,6 +168,14 @@ FLAGS expected to be production ready and should be avoided in production-grade environments. + --enable-master-global-access + Use with private clusters to allow access to the master's private + endpoint from any Google Cloud region or on-premises environment + regardless of the private cluster's region. + + Must be used in conjunction with '--enable-ip-alias' and + '--enable-private-nodes'. + --fleet-project=PROJECT_ID_OR_NUMBER Sets fleet host project for the cluster. If specified, the current cluster will be registered as a fleet membership under the fleet host diff --git a/gcloud/beta/dataflow/flex-template/build b/gcloud/beta/dataflow/flex-template/build index 505e722fc..fdac6cb71 100644 --- a/gcloud/beta/dataflow/flex-template/build +++ b/gcloud/beta/dataflow/flex-template/build @@ -50,7 +50,7 @@ EXAMPLES $ gcloud beta dataflow flex-template build \ gs://template-file-gcs-path \ - --image-gcr-path=gcr://path-tos-tore-image \ + --image-gcr-path=gcr://path-to-store-image \ --jar=path/to/pipeline.jar --jar=path/to/dependency.jar \ --env=FLEX_TEMPLATE_JAVA_MAIN_CLASS=classpath \ --flex-template-base-image=JAVA11 \ diff --git a/gcloud/beta/firestore/help b/gcloud/beta/firestore/help index 2806eb6da..aa6ff9f4a 100644 --- a/gcloud/beta/firestore/help +++ b/gcloud/beta/firestore/help @@ -30,6 +30,9 @@ GROUPS indexes (BETA) Manage indexes for Cloud Firestore. + locations + (BETA) The set of commands to manage Locations for Cloud Firestore. + operations (BETA) Manage Long Running Operations for Cloud Firestore. diff --git a/gcloud/beta/firestore/locations/help b/gcloud/beta/firestore/locations/help new file mode 100644 index 000000000..bd143520b --- /dev/null +++ b/gcloud/beta/firestore/locations/help @@ -0,0 +1,27 @@ +NAME + gcloud beta firestore locations - the set of commands to manage Locations + for Cloud Firestore + +SYNOPSIS + gcloud beta firestore locations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The set of commands to manage Locations for Cloud Firestore. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (BETA) List locations available to Google Cloud Firestore. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha firestore locations + diff --git a/gcloud/beta/firestore/locations/list b/gcloud/beta/firestore/locations/list new file mode 100644 index 000000000..618cec684 --- /dev/null +++ b/gcloud/beta/firestore/locations/list @@ -0,0 +1,65 @@ +NAME + gcloud beta firestore locations list - list locations available to Google + Cloud Firestore + +SYNOPSIS + gcloud beta firestore locations list [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all Firestore locations with table. + + $ gcloud beta firestore locations list \ + --format="table(locationId, displayName)" + + To list Firestore locations with a filter. + + $ gcloud beta firestore locations list --filter="locationId:us-west1" + +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 firestore locations list + diff --git a/gcloud/beta/iam/workforce-pools/providers/create-oidc b/gcloud/beta/iam/workforce-pools/providers/create-oidc index 0aa8fa0e1..2456d361a 100644 --- a/gcloud/beta/iam/workforce-pools/providers/create-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/create-oidc @@ -8,7 +8,9 @@ SYNOPSIS --attribute-mapping=[ATTRIBUTE_MAPPING,...] --client-id=CLIENT_ID --issuer-uri=ISSUER_URI [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + [--disabled] [--display-name=DISPLAY_NAME] + [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] + [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a new OIDC workforce pool provider. @@ -25,7 +27,9 @@ EXAMPLES --description="My workforce pool provider description." \ --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" --client-id="client-id" \ - --issuer-uri="https://test-idp.com" + --issuer-uri="https://test-idp.com" \ + --web-sso-response-type=id-token \ + --web-sso-assertion-claims-behavior=only-id-token-claims POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to create. @@ -187,6 +191,20 @@ OPTIONAL FLAGS A display name for the workforce pool provider. Cannot exceed 32 characters in length. + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR + The behavior for how OIDC Claims are included in the assertion object + used for attribute mapping and attribute condition. Use + only-id-token-claims to include only ID token claims. + WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be one of: + assertion-claims-behavior-unspecified, only-id-token-claims. + + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE + Response Type to request for in the OIDC Authorization Request for web + sign-in. Use id-token to select the implicit flow + (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). + WEB_SSO_RESPONSE_TYPE must be one of: id-token, + response-type-unspecified. + 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/iam/workforce-pools/providers/update-oidc b/gcloud/beta/iam/workforce-pools/providers/update-oidc index e903f5699..3cee8708a 100644 --- a/gcloud/beta/iam/workforce-pools/providers/update-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/update-oidc @@ -8,7 +8,9 @@ SYNOPSIS [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] [--client-id=CLIENT_ID] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] - [--issuer-uri=ISSUER_URI] [GCLOUD_WIDE_FLAG ...] + [--issuer-uri=ISSUER_URI] + [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] + [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update an OIDC workforce pool provider. @@ -25,7 +27,9 @@ EXAMPLES --description="My workforce pool provider description." \ --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" --client-id="client-id" \ - --issuer-uri="https://test-idp.com" + --issuer-uri="https://test-idp.com" \ + --web-sso-response-type=id-token \ + --web-sso-assertion-claims-behavior=only-id-token-claims POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to update. @@ -186,6 +190,20 @@ FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR + The behavior for how OIDC Claims are included in the assertion object + used for attribute mapping and attribute condition. Use + only-id-token-claims to include only ID token claims. + WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be one of: + assertion-claims-behavior-unspecified, only-id-token-claims. + + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE + Response Type to request for in the OIDC Authorization Request for web + sign-in. Use id-token to select the implicit flow + (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). + WEB_SSO_RESPONSE_TYPE must be one of: id-token, + response-type-unspecified. + 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/pull b/gcloud/beta/pubsub/subscriptions/pull index be37cb3b6..138f00b8b 100644 --- a/gcloud/beta/pubsub/subscriptions/pull +++ b/gcloud/beta/pubsub/subscriptions/pull @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta pubsub subscriptions pull SUBSCRIPTION [--auto-ack] - [--max-messages=MAX_MESSAGES; default=1] [--wait] [--filter=EXPRESSION] + [--max-messages=MAX_MESSAGES; default=1] + [--return-immediately | --no-wait] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] @@ -49,9 +50,24 @@ FLAGS --max-messages is deprecated. Please use --limit instead. - --wait - Wait (for a bounded amount of time) for new messages from the - subscription, if there are none. + Pull timeout behavior. + + At most one of these can be specified: + + --return-immediately + If this flag is set, the system responds immediately with any + messages readily available in memory buffers. If no messages are + available in the buffers, returns an empty list of messages as + response, even if having messages in the backlog. Do not set this + flag as it adversely impacts the performance of pull. + + --wait + (DEPRECATED) Wait (for a bounded amount of time) for new messages + from the subscription, if there are none. + + --wait is deprecated. This flag is non-operational, as the wait + behavior is now the default. Enabled by default, use --no-wait to + disable. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 0e637e3c6..05042e1e7 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -176,7 +176,9 @@ FLAGS --port=PORT Container port to receive requests at. Also sets the $PORT environment variable. Must be a number between 1 and 65535, inclusive. To unset - this field, pass the special value "default". + this field, pass the special value "default". If updating an existing + service with a TCP startup probe pointing to the previous container + port, this will also update the probe port. --service-account=SERVICE_ACCOUNT Service account associated with the revision of the service. The diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 12dde3793..2a0ef08a0 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -169,7 +169,9 @@ FLAGS --port=PORT Container port to receive requests at. Also sets the $PORT environment variable. Must be a number between 1 and 65535, inclusive. To unset - this field, pass the special value "default". + this field, pass the special value "default". If updating an existing + service with a TCP startup probe pointing to the previous container + port, this will also update the probe port. --service-account=SERVICE_ACCOUNT Service account associated with the revision of the service. The diff --git a/gcloud/beta/sql/import/sql b/gcloud/beta/sql/import/sql index f2ac482e5..bf1d8d327 100644 --- a/gcloud/beta/sql/import/sql +++ b/gcloud/beta/sql/import/sql @@ -40,10 +40,10 @@ FLAGS complete. --database=DATABASE, -d DATABASE - Database to which the import is made. If not set, it is assumed that - the database is specified in the file to be imported. If your SQL dump - file includes a database statement, it will override the database set - in this flag. + Database to which the import is made. The database needs to be created + before importing. If not set, it is assumed that the database is + specified in the file to be imported. If your SQL dump file includes a + database statement, it will override the database set in this flag. --user=USER PostgreSQL user for this import operation. diff --git a/gcloud/beta/sql/instances/import b/gcloud/beta/sql/instances/import index b8505cee0..b5044756c 100644 --- a/gcloud/beta/sql/instances/import +++ b/gcloud/beta/sql/instances/import @@ -37,10 +37,10 @@ FLAGS complete. --database=DATABASE, -d DATABASE - Database to which the import is made. If not set, it is assumed that - the database is specified in the file to be imported. If your SQL dump - file includes a database statement, it will override the database set - in this flag. + Database to which the import is made. The database needs to be created + before importing. If not set, it is assumed that the database is + specified in the file to be imported. If your SQL dump file includes a + database statement, it will override the database set in this flag. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/bms/instances/help b/gcloud/bms/instances/help index 45cb90c45..10eededf1 100644 --- a/gcloud/bms/instances/help +++ b/gcloud/bms/instances/help @@ -27,6 +27,9 @@ COMMANDS list List Bare Metal Solution instances in a project. + rename + Rename a Bare Metal Solution instance. + reset Reset a Bare Metal Solution instance. diff --git a/gcloud/bms/instances/rename b/gcloud/bms/instances/rename new file mode 100644 index 000000000..8cb8edd80 --- /dev/null +++ b/gcloud/bms/instances/rename @@ -0,0 +1,65 @@ +NAME + gcloud bms instances rename - rename a Bare Metal Solution instance + +SYNOPSIS + gcloud bms instances rename (INSTANCE : --region=REGION) + --new-name=NEW_NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Rename a Bare Metal Solution instance. + +EXAMPLES + To rename an instance my-instance to my-new-instance-name in region + us-central1, run: + + $ gcloud bms instances rename my-instance \ + --new-name=my-new-instance-name --region=us-central1 \ + --project=bms-example-project + +POSITIONAL ARGUMENTS + Instance resource - instance. The arguments in this group can be used to + specify the attributes of this resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Region of the resource. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + --new-name=NEW_NAME + New instance name for renaming an already existing instance. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha bms instances rename + diff --git a/gcloud/bms/networks/help b/gcloud/bms/networks/help index 282faed1a..8bee26fa5 100644 --- a/gcloud/bms/networks/help +++ b/gcloud/bms/networks/help @@ -25,6 +25,9 @@ COMMANDS List IP range reservations for Bare Metal Solution networks in a project. + rename + Rename a Bare Metal Solution network. + update Update a Bare Metal Solution network. diff --git a/gcloud/bms/networks/rename b/gcloud/bms/networks/rename new file mode 100644 index 000000000..0e60fd212 --- /dev/null +++ b/gcloud/bms/networks/rename @@ -0,0 +1,65 @@ +NAME + gcloud bms networks rename - rename a Bare Metal Solution network + +SYNOPSIS + gcloud bms networks rename (NETWORK : --region=REGION) --new-name=NEW_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Rename a Bare Metal Solution network. + +EXAMPLES + To rename a network my-network to my-new-network-name in region + us-central1, run: + + $ gcloud bms networks rename my-network \ + --new-name=my-new-network-name --region=us-central1 \ + --project=bms-example-project + +POSITIONAL ARGUMENTS + Network resource - network. 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 network on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NETWORK + ID of the network or fully qualified identifier for the network. + + To set the network attribute: + ▸ provide the argument network on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Region of the resource. + + To set the region attribute: + ▸ provide the argument network on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + --new-name=NEW_NAME + New network name for renaming an already existing network. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha bms networks rename + diff --git a/gcloud/bms/nfs-shares/help b/gcloud/bms/nfs-shares/help index 4d0c7d809..89815950b 100644 --- a/gcloud/bms/nfs-shares/help +++ b/gcloud/bms/nfs-shares/help @@ -27,6 +27,9 @@ COMMANDS list List Bare Metal Solution NFS shares in a project. + rename + Rename a Bare Metal Solution nfs-share. + update Update a Bare Metal Solution NFS share. diff --git a/gcloud/bms/nfs-shares/rename b/gcloud/bms/nfs-shares/rename new file mode 100644 index 000000000..c52d1694f --- /dev/null +++ b/gcloud/bms/nfs-shares/rename @@ -0,0 +1,65 @@ +NAME + gcloud bms nfs-shares rename - rename a Bare Metal Solution nfs-share + +SYNOPSIS + gcloud bms nfs-shares rename (NFS_SHARE : --region=REGION) + --new-name=NEW_NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Rename a Bare Metal Solution nfs-share. + +EXAMPLES + To rename a nfs-share my-nfs-share to my-new-nfs-share-name in region + us-central1, run: + + $ gcloud bms nfs-shares rename my-nfs-share \ + --new-name=my-new-nfs-share-name --region=us-central1 \ + --project=bms-example-project + +POSITIONAL ARGUMENTS + Nfs share resource - nfs_share. 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 nfs_share on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + NFS_SHARE + ID of the nfs_share or fully qualified identifier for the nfs_share. + + To set the nfs_share attribute: + ▸ provide the argument nfs_share on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Region of the resource. + + To set the region attribute: + ▸ provide the argument nfs_share on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + --new-name=NEW_NAME + New nfs-share name for renaming an already existing nfs-share. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha bms nfs-shares rename + diff --git a/gcloud/bms/volumes/help b/gcloud/bms/volumes/help index 808ccd3b8..94cd1440d 100644 --- a/gcloud/bms/volumes/help +++ b/gcloud/bms/volumes/help @@ -30,6 +30,9 @@ COMMANDS list List Bare Metal Solution volumes in a project. + rename + Rename a Bare Metal Solution volume. + restore Restore a Bare Metal Solution boot volume from an existing snapshot. diff --git a/gcloud/bms/volumes/rename b/gcloud/bms/volumes/rename new file mode 100644 index 000000000..1a20bd003 --- /dev/null +++ b/gcloud/bms/volumes/rename @@ -0,0 +1,65 @@ +NAME + gcloud bms volumes rename - rename a Bare Metal Solution volume + +SYNOPSIS + gcloud bms volumes rename (VOLUME : --region=REGION) --new-name=NEW_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Rename a Bare Metal Solution volume. + +EXAMPLES + To rename a volume my-volume to my-new-volume-name in region us-central1, + run: + + $ gcloud bms volumes rename my-volume \ + --new-name=my-new-volume-name --region=us-central1 \ + --project=bms-example-project + +POSITIONAL ARGUMENTS + Volume resource - volume. 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 volume on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + VOLUME + ID of the volume or fully qualified identifier for the volume. + + To set the volume attribute: + ▸ provide the argument volume on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + Region of the resource. + + To set the region attribute: + ▸ provide the argument volume on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + --new-name=NEW_NAME + New volume name for renaming an already existing volume. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha bms volumes rename + diff --git a/gcloud/builds/submit b/gcloud/builds/submit index 0f6714056..f77d74b17 100644 --- a/gcloud/builds/submit +++ b/gcloud/builds/submit @@ -6,9 +6,11 @@ SYNOPSIS [--default-buckets-behavior=DEFAULT_BUCKETS_BEHAVIOR] [--disk-size=DISK_SIZE] [--gcs-log-dir=GCS_LOG_DIR] [--gcs-source-staging-dir=GCS_SOURCE_STAGING_DIR] - [--ignore-file=IGNORE_FILE] [--machine-type=MACHINE_TYPE] - [--region=REGION] [--substitutions=[KEY=VALUE,...]] [--suppress-logs] - [--timeout=TIMEOUT] [--worker-pool=WORKER_POOL] + [--git-source-dir=GIT_SOURCE_DIR] + [--git-source-revision=GIT_SOURCE_REVISION] [--ignore-file=IGNORE_FILE] + [--machine-type=MACHINE_TYPE] [--region=REGION] + [--substitutions=[KEY=VALUE,...]] [--suppress-logs] [--timeout=TIMEOUT] + [--worker-pool=WORKER_POOL] [--config=CONFIG; default="cloudbuild.yaml" | --pack=[builder=BUILDER],[env=ENV],[image=IMAGE] | --tag=TAG, -t TAG] [GCLOUD_WIDE_FLAG ...] @@ -45,15 +47,15 @@ POSITIONAL ARGUMENTS [SOURCE] The location of the source to build. The location can be a directory - on a local disk or a gzipped archive file (.tar.gz) in Google Cloud - Storage. If the source is a local directory, this command skips the - files specified in the --ignore-file. If --ignore-file is not - specified, use.gcloudignore file. If a .gcloudignore file is absent - and a .gitignore file is present in the local source directory, - gcloud will use a generated Git-compatible .gcloudignore file that - respects your .gitignored files. The global .gitignore is not - respected. For more information on .gcloudignore, see gcloud topic - gcloudignore. + on a local disk, a gzipped archive file (.tar.gz) in Google Cloud + Storage, or a Git repo url starting with http:// or https://. If the + source is a local directory, this command skips the files specified + in the --ignore-file. If --ignore-file is not specified, + use.gcloudignore file. If a .gcloudignore file is absent and a + .gitignore file is present in the local source directory, gcloud will + use a generated Git-compatible .gcloudignore file that respects your + .gitignored files. The global .gitignore is not respected. For more + information on .gcloudignore, see gcloud topic gcloudignore. --no-source Specify that no source should be uploaded with this build. @@ -95,6 +97,22 @@ FLAGS set --default-buckets-behavior to REGIONAL_USER_OWNED_BUCKET and builds/region is not global. + --git-source-dir=GIT_SOURCE_DIR + Directory, relative to the source root, in which to run the build. This + must be a relative path. If a step's dir is specified and is an + absolute path, this value is ignored for that step's execution. + + --git-source-revision=GIT_SOURCE_REVISION + Revision to fetch from the Git repository such as a branch, a tag, a + commit SHA, or any Git ref to run the build. + + Cloud Build uses git fetch to fetch the revision from the Git + repository; therefore make sure that the string you provide for + revision is parsable by the command. For information on string values + accepted by git fetch, see + https://git-scm.com/docs/gitrevisions#_specifying_revisions. For + information on git fetch, see https://git-scm.com/docs/git-fetch. + --ignore-file=IGNORE_FILE Override the .gcloudignore file and use the specified file instead. diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index 6d24a5565..33f5ee394 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -333,6 +333,13 @@ FLAGS ▸ https://compute.googleapis.com/compute/v1/projects/myproject/global/snapshots/snapshot ▸ snapshot + replica-zones + Required for each regional disk associated with the instance. + Specify the URLs of the zones where the disk should be replicated + to. You must provide exactly two replica zones, and one zone must + be the same as the instance zone. You can't use this option with + boot disks. + --csek-key-file=FILE Path to a Customer-Supplied Encryption Key (CSEK) key file that maps Compute Engine resources to user managed keys to be used when creating, diff --git a/gcloud/container/clusters/create-auto b/gcloud/container/clusters/create-auto index a2ca05b23..2c5eaeb79 100644 --- a/gcloud/container/clusters/create-auto +++ b/gcloud/container/clusters/create-auto @@ -13,7 +13,8 @@ SYNOPSIS [--create-subnetwork=[KEY=VALUE,...]] [--database-encryption-key=DATABASE_ENCRYPTION_KEY] [--enable-google-cloud-access] - [--enable-kubernetes-unstable-apis=API,[API,...]] [--network=NETWORK] + [--enable-kubernetes-unstable-apis=API,[API,...]] + [--enable-master-global-access] [--network=NETWORK] [--private-endpoint-subnetwork=NAME] [--release-channel=CHANNEL] [--security-group=SECURITY_GROUP] [--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME] [--subnetwork=SUBNETWORK] @@ -166,6 +167,14 @@ FLAGS expected to be production ready and should be avoided in production-grade environments. + --enable-master-global-access + Use with private clusters to allow access to the master's private + endpoint from any Google Cloud region or on-premises environment + regardless of the private cluster's region. + + Must be used in conjunction with '--enable-ip-alias' and + '--enable-private-nodes'. + --network=NETWORK The Compute Engine Network that the cluster will connect to. Google Kubernetes Engine will use this network when creating routes and diff --git a/gcloud/database-migration/connection-profiles/create/help b/gcloud/database-migration/connection-profiles/create/help index e7eee96a7..4f8b659be 100644 --- a/gcloud/database-migration/connection-profiles/create/help +++ b/gcloud/database-migration/connection-profiles/create/help @@ -31,6 +31,9 @@ COMMANDS mysql Create a Database Migration Service connection profile for MySQL. + oracle + Create a Database Migration Service connection profile for Oracle. + postgresql Create a Database Migration Service connection profile for PostgreSQL. diff --git a/gcloud/database-migration/connection-profiles/create/oracle b/gcloud/database-migration/connection-profiles/create/oracle new file mode 100644 index 000000000..0dead8ad5 --- /dev/null +++ b/gcloud/database-migration/connection-profiles/create/oracle @@ -0,0 +1,159 @@ +NAME + gcloud database-migration connection-profiles create oracle - create a + Database Migration Service connection profile for Oracle + +SYNOPSIS + gcloud database-migration connection-profiles create oracle + (CONNECTION_PROFILE : --region=REGION) + --database-service=DATABASE_SERVICE --host=HOST --port=PORT + --username=USERNAME (--password=PASSWORD | --prompt-for-password) + [--no-async] [--display-name=DISPLAY_NAME] [--labels=[KEY=VALUE,...]] + [--private-connection=PRIVATE_CONNECTION | --static-ip-connectivity + | [--forward-ssh-hostname=FORWARD_SSH_HOSTNAME + --forward-ssh-username=FORWARD_SSH_USERNAME + (--forward-ssh-password=FORWARD_SSH_PASSWORD + | --forward-ssh-private-key=FORWARD_SSH_PRIVATE_KEY) + : --forward-ssh-port=FORWARD_SSH_PORT; default=22]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Database Migration Service connection profile for Oracle. + +EXAMPLES + To create a connection profile my-profile for Oracle: + + $ gcloud database-migration connection-profiles create oracle \ + my-profile --region=us-central1 --password=123456 \ + --username=my-user --host=1.2.3.4 --port=5432 + +POSITIONAL ARGUMENTS + Connection profile resource - The connection profile 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 connection_profile 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. + + CONNECTION_PROFILE + ID of the connection_profile or fully qualified identifier for the + connection_profile. + + To set the connection_profile attribute: + ▸ provide the argument connection_profile on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the connection_profile. + + To set the region attribute: + ▸ provide the argument connection_profile on the command line with + a fully specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + --database-service=DATABASE_SERVICE + database service for the oracle connection profile. + + --host=HOST + IP or hostname of the source database. + + --port=PORT + Network port of the source database. + + --username=USERNAME + Username that Database Migration Service uses to connect to the + database. Database Migration Service encrypts the value when storing + it. + + Exactly one of these must be specified: + + --password=PASSWORD + Password for the user that Database Migration Service uses to connect + to the source 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. + +OPTIONAL FLAGS + --no-async + Waits for the operation in progress to complete before returning. + + --display-name=DISPLAY_NAME + A user-friendly name for the connection profile. The display name can + include letters, numbers, spaces, and hyphens, and must start with a + letter. + + --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 these can be specified: + + Private connection resource - Resource ID of the private connection. + 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 --private-connection 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 region attribute: + ▸ provide the argument --private-connection on the command line with + a fully specified name; + ▸ provide the argument --region on the command line. + + --private-connection=PRIVATE_CONNECTION + ID of the private_connection or fully qualified identifier for the + private_connection. + + To set the private_connection attribute: + ▫ provide the argument --private-connection on the command line. + + --static-ip-connectivity + use static ip connectivity + + --forward-ssh-hostname=FORWARD_SSH_HOSTNAME + Hostname for the SSH tunnel. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --forward-ssh-username=FORWARD_SSH_USERNAME + Username for the SSH tunnel. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --forward-ssh-port=FORWARD_SSH_PORT; default=22 + Port for the SSH tunnel, default value is 22. + + Exactly one of these must be specified: + + --forward-ssh-password=FORWARD_SSH_PASSWORD + SSH password. + + --forward-ssh-private-key=FORWARD_SSH_PRIVATE_KEY + SSH private key.. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/database-migration/connection-profiles/create/postgresql b/gcloud/database-migration/connection-profiles/create/postgresql index eb3d969b3..9dea40f3d 100644 --- a/gcloud/database-migration/connection-profiles/create/postgresql +++ b/gcloud/database-migration/connection-profiles/create/postgresql @@ -10,13 +10,15 @@ SYNOPSIS [--ca-certificate=CA_CERTIFICATE : --client-certificate=CLIENT_CERTIFICATE --private-key=PRIVATE_KEY] [--host=HOST --port=PORT --username=USERNAME (--password=PASSWORD - | --prompt-for-password)] [GCLOUD_WIDE_FLAG ...] + | --prompt-for-password)] + [--psc-service-attachment=PSC_SERVICE_ATTACHMENT + | --static-ip-connectivity] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a Database Migration Service connection profile for PostgreSQL. EXAMPLES - To create a connection profile for PostgreSQL: + To create a connection profile my-profile for PostgreSQL: $ gcloud database-migration connection-profiles create postgresql \ my-profile --region=us-central1 --password=123456 \ @@ -119,6 +121,34 @@ FLAGS --prompt-for-password Prompt for the password used to connect to the database. + At most one of these can be specified: + + Service attachment resource - Resource ID of the service attachment. + 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 --psc-service-attachment 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 region attribute: + ▸ provide the argument --psc-service-attachment on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + + --psc-service-attachment=PSC_SERVICE_ATTACHMENT + ID of the service_attachment or fully qualified identifier for the + service_attachment. + + To set the service_attachment attribute: + ▫ provide the argument --psc-service-attachment on the command + line. + + --static-ip-connectivity + use static ip connectivity + 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/database-migration/conversion-workspaces/apply b/gcloud/database-migration/conversion-workspaces/apply new file mode 100644 index 000000000..a6bfb39d4 --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/apply @@ -0,0 +1,98 @@ +NAME + gcloud database-migration conversion-workspaces apply - apply a Database + Migration Service conversion workspace + +SYNOPSIS + gcloud database-migration conversion-workspaces apply + (CONVERSION_WORKSPACE : --region=REGION) + --destination-connection-profile=DESTINATION_CONNECTION_PROFILE + [--no-async] [--filter=FILTER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Apply Database Migration Service conversion workspace onto the destination + database. + +EXAMPLES + To apply a conversion workspace: + + $ gcloud database-migration conversion-workspaces apply \ + my-conversion-workspace --region=us-central1 \ + --destination-connection-profile=projects/$$PROJECT_ID$$/\ + locations/us-central1/connectionProfiles/\ + destination-connection-profile-name + +POSITIONAL ARGUMENTS + Conversion workspace resource - The conversion workspace to apply. 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 conversion_workspace 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. + + CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument conversion_workspace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the conversion_workspace. + + To set the region attribute: + ▸ provide the argument conversion_workspace on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + Connection profile resource - The connection profile to apply to. 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 --destination-connection-profile 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 region attribute: + ◆ provide the argument --destination-connection-profile on the command + line with a fully specified name; + ◆ provide the argument --region on the command line. + + This must be specified. + + --destination-connection-profile=DESTINATION_CONNECTION_PROFILE + ID of the connection_profile or fully qualified identifier for the + connection_profile. + + To set the connection_profile attribute: + ▸ provide the argument --destination-connection-profile on the + command line. + +OPTIONAL FLAGS + --no-async + Waits for the operation in progress to complete before returning. + + --filter=FILTER + Filter the entities based on (AIP-160)[https://google.aip.dev/160] + standard. Example: to filter all tables whose name start with + "Employee" and are present under schema "Company", use filter as + "parent = Company and TABLE=Employee" + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/database-migration/conversion-workspaces/commit b/gcloud/database-migration/conversion-workspaces/commit new file mode 100644 index 000000000..c8d071940 --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/commit @@ -0,0 +1,67 @@ +NAME + gcloud database-migration conversion-workspaces commit - commit a Database + Migration Service conversion workspace + +SYNOPSIS + gcloud database-migration conversion-workspaces commit + (CONVERSION_WORKSPACE : --region=REGION) [--no-async] + [--commit-name=COMMIT_NAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commit a Database Migration Service conversion workspace. + +EXAMPLES + To commit a version of conversion workspace called my-conversion-workspace: + + $ gcloud database-migration conversion-workspaces commit \ + my-conversion-workspace --region=us-central1 \ + --commit-name=my-commit + +POSITIONAL ARGUMENTS + Conversion workspace resource - The conversion workspace to commit. 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 conversion_workspace 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. + + CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument conversion_workspace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the conversion_workspace. + + To set the region attribute: + ▸ provide the argument conversion_workspace on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + +FLAGS + --no-async + Waits for the operation in progress to complete before returning. + + --commit-name=COMMIT_NAME + A user-friendly name for the conversion workspace commit. The commit + name can include letters, numbers, spaces, and hyphens, and must start + with a letter. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/database-migration/conversion-workspaces/convert b/gcloud/database-migration/conversion-workspaces/convert new file mode 100644 index 000000000..b45d24018 --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/convert @@ -0,0 +1,70 @@ +NAME + gcloud database-migration conversion-workspaces convert - convert a + Database Migration Service conversion workspace + +SYNOPSIS + gcloud database-migration conversion-workspaces convert + (CONVERSION_WORKSPACE : --region=REGION) [--no-async] [--auto-commit] + [--filter=FILTER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Convert a Database Migration Service conversion workspace. + +EXAMPLES + To convert a conversion workspace: + + $ gcloud database-migration conversion-workspaces convert \ + my-conversion-workspace --region=us-central1 + +POSITIONAL ARGUMENTS + Conversion workspace resource - The conversion workspace to convert. 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 conversion_workspace 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. + + CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument conversion_workspace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the conversion_workspace. + + To set the region attribute: + ▸ provide the argument conversion_workspace on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + +FLAGS + --no-async + Waits for the operation in progress to complete before returning. + + --auto-commit + Auto commits the conversion workspace. + + --filter=FILTER + Filter the entities based on (AIP-160)[https://google.aip.dev/160] + standard. Example: to filter all tables whose name start with + "Employee" and are present under schema "Company", use filter as + "parent = Company and TABLE=Employee" + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/database-migration/conversion-workspaces/create b/gcloud/database-migration/conversion-workspaces/create new file mode 100644 index 000000000..52abccc04 --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/create @@ -0,0 +1,100 @@ +NAME + gcloud database-migration conversion-workspaces create - create a Database + Migration Service conversion workspace + +SYNOPSIS + gcloud database-migration conversion-workspaces create + (CONVERSION_WORKSPACE : --region=REGION) + --destination-database-engine=DESTINATION_DATABASE_ENGINE + --destination-database-version=DESTINATION_DATABASE_VERSION + --source-database-engine=SOURCE_DATABASE_ENGINE + --source-database-version=SOURCE_DATABASE_VERSION [--no-async] + [--display-name=DISPLAY_NAME] [--global-settings=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Database Migration Service conversion workspace. + +EXAMPLES + To create a conversion workspace: + + $ gcloud database-migration conversion-workspaces create \ + my-conversion-workspace --region=us-central1 \ + --display-name=cw1 --source-database-engine=ORACLE \ + --source-database-version=11 \ + --destination-database-engine=POSTGRESQL \ + --destination-database-version=8 + +POSITIONAL ARGUMENTS + Conversion workspace resource - The conversion workspace 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 conversion_workspace 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. + + CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument conversion_workspace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the conversion_workspace. + + To set the region attribute: + ▸ provide the argument conversion_workspace on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + --destination-database-engine=DESTINATION_DATABASE_ENGINE + Database engine type. DESTINATION_DATABASE_ENGINE must be (only one + value is supported): POSTGRESQL. + + --destination-database-version=DESTINATION_DATABASE_VERSION + Version number for the database engine. The version number must contain + numbers and letters only. Example for Oracle 21c, version number will + be 21c. + + --source-database-engine=SOURCE_DATABASE_ENGINE + Database engine type. SOURCE_DATABASE_ENGINE must be (only one value is + supported): ORACLE. + + --source-database-version=SOURCE_DATABASE_VERSION + Version number for the database engine. The version number must contain + numbers and letters only. Example for Oracle 21c, version number will + be 21c. + +OPTIONAL FLAGS + --no-async + Waits for the operation in progress to complete before returning. + + --display-name=DISPLAY_NAME + A user-friendly name for the conversion workspace. The display name can + include letters, numbers, spaces, and hyphens, and must start with a + letter. The maximum length allowed is 60 characters. + + --global-settings=[KEY=VALUE,...] + A generic list of settings for the workspace. The settings are database + pair dependant and can indicate default behavior for the mapping rules + engine or turn on or off specific features. An object containing a list + of "key": "value" pairs. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/database-migration/conversion-workspaces/delete b/gcloud/database-migration/conversion-workspaces/delete new file mode 100644 index 000000000..b92b1eb10 --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/delete @@ -0,0 +1,61 @@ +NAME + gcloud database-migration conversion-workspaces delete - delete a Database + Migration conversion workspace + +SYNOPSIS + gcloud database-migration conversion-workspaces delete + (CONVERSION_WORKSPACE : --region=REGION) [--no-async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Database Migration conversion workspace + +EXAMPLES + To delete a conversion workspace called 'my-conversion-workspace', run: + + $ gcloud database-migration conversion-workspaces delete \ + my-conversion-workspace --region=us-central1 + +POSITIONAL ARGUMENTS + Conversion workspace resource - The conversion workspace 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 conversion_workspace 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. + + CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument conversion_workspace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the conversion_workspace. + + To set the region attribute: + ▸ provide the argument conversion_workspace on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + +FLAGS + --no-async + Waits for the operation in progress to complete before returning. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/database-migration/conversion-workspaces/describe b/gcloud/database-migration/conversion-workspaces/describe new file mode 100644 index 000000000..d5ddba395 --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/describe @@ -0,0 +1,60 @@ +NAME + gcloud database-migration conversion-workspaces describe - show details + about a database migration conversion workspace + +SYNOPSIS + gcloud database-migration conversion-workspaces describe + (CONVERSION_WORKSPACE : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details about a conversion workspace. + +EXAMPLES + To show details about a conversion workspace, run: + + $ gcloud database-migration conversion-workspaces describe \ + my-conversion-workspace --region=us-central1 + +POSITIONAL ARGUMENTS + Conversion workspace resource - The conversion workspace you want to get + the details of. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument conversion_workspace 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. + + CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument conversion_workspace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the region. + + To set the region attribute: + ▸ provide the argument conversion_workspace on the command line + with a fully specified name; + ▸ provide the argument --region 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 datamigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/database-migration/ diff --git a/gcloud/database-migration/conversion-workspaces/describe-entities b/gcloud/database-migration/conversion-workspaces/describe-entities new file mode 100644 index 000000000..3003eb637 --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/describe-entities @@ -0,0 +1,81 @@ +NAME + gcloud database-migration conversion-workspaces describe-entities - + describe database entities in a Database Migration conversion workspace + +SYNOPSIS + gcloud database-migration conversion-workspaces describe-entities + (CONVERSION_WORKSPACE : --region=REGION) --tree-type=TREE_TYPE + [--commit-id=COMMIT_ID] [--filter=FILTER] [--uncommitted] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe database entities in a Database Migration conversion workspace. + +EXAMPLES + To describe the database entities of the source tree in a conversion + workspace in a project and location us-central1, run: + + $ gcloud database-migration conversion-workspaces \ + describe-entities my-conversion-workspace --region=us-central1 \ + --tree-type=SOURCE + +POSITIONAL ARGUMENTS + Conversion workspace resource - The conversion workspace describe + entities. 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 conversion_workspace 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. + + CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument conversion_workspace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the conversion_workspace. + + To set the region attribute: + ▸ provide the argument conversion_workspace on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + --tree-type=TREE_TYPE + Tree type for database entities. TREE_TYPE must be one of: SOURCE, + DRAFT. + +OPTIONAL FLAGS + --commit-id=COMMIT_ID + Request a specific commit id. If not specified, the entities from the + latest commit are returned. + + --filter=FILTER + Filter the entities based on (AIP-160)[https://google.aip.dev/160] + standard. Example: to filter all tables whose name start with + "Employee" and are present under schema "Company", use filter as + "parent = Company and TABLE=Employee" + + --uncommitted + Whether to retrieve the latest committed version of the entities or the + latest version. This field is ignored if a specific commit_id is + specified. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/database-migration/conversion-workspaces/help b/gcloud/database-migration/conversion-workspaces/help new file mode 100644 index 000000000..8b97fdc82 --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/help @@ -0,0 +1,59 @@ +NAME + gcloud database-migration conversion-workspaces - manage Database Migration + Service conversion workspaces + +SYNOPSIS + gcloud database-migration conversion-workspaces COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing Database Migration Service conversion workspaces. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + apply + Apply a Database Migration Service conversion workspace. + + commit + Commit a Database Migration Service conversion workspace. + + convert + Convert a Database Migration Service conversion workspace. + + create + Create a Database Migration Service conversion workspace. + + delete + Delete a Database Migration conversion workspace. + + describe + Show details about a database migration conversion workspace. + + describe-entities + Describe database entities in a Database Migration conversion + workspace. + + import-rules + Import mapping rules in a Database Migration Service conversion + workspace. + + list + List conversion workspaces. + + list-background-jobs + List background jobs in the conversion workspaces. + + rollback + Rollback a Database Migration Service conversion workspace. + + seed + Seed a Database Migration Service conversion workspace. + + update + Update a Database Migration Service conversion workspace. diff --git a/gcloud/database-migration/conversion-workspaces/import-rules b/gcloud/database-migration/conversion-workspaces/import-rules new file mode 100644 index 000000000..3400c79f1 --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/import-rules @@ -0,0 +1,76 @@ +NAME + gcloud database-migration conversion-workspaces import-rules - import + mapping rules in a Database Migration Service conversion workspace + +SYNOPSIS + gcloud database-migration conversion-workspaces import-rules + (CONVERSION_WORKSPACE : --region=REGION) + --config-files=CONGIF_FILE,[CONGIF_FILE,...] --file-format=FILE_FORMAT + [--auto-commit] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Import mapping rules in a Database Migration Service conversion workspace + from a configuration file. For example, for Oracle to PostgreSQL migrations + that could be an Ora2Pg config file. + +EXAMPLES + To import rules in a conversion workspace: + + $ gcloud database-migration conversion-workspaces import-rules \ + my-conversion-workspace --region=us-central1 \ + --file-format=ORA2PG \ + --config-files=PATH1/config1.conf,PATH2/config2.conf + +POSITIONAL ARGUMENTS + Conversion workspace resource - The conversion workspace to import rules. + 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 conversion_workspace 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. + + CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument conversion_workspace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the conversion_workspace. + + To set the region attribute: + ▸ provide the argument conversion_workspace on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + --config-files=CONGIF_FILE,[CONGIF_FILE,...] + A list of files to import rules from. Either provide a single file path + or if multiple files are to be provided, each file should correspond to + one schema. Provide file paths as a comma separated list. + + --file-format=FILE_FORMAT + File format type to import rules from. FILE_FORMAT must be (only one + value is supported): ORA2PG. + +OPTIONAL FLAGS + --auto-commit + Auto commits the conversion workspace. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/database-migration/conversion-workspaces/list b/gcloud/database-migration/conversion-workspaces/list new file mode 100644 index 000000000..d4b4aa3b4 --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/list @@ -0,0 +1,81 @@ +NAME + gcloud database-migration conversion-workspaces list - list conversion + workspaces + +SYNOPSIS + gcloud database-migration conversion-workspaces list --region=REGION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List conversion workspaces. + +EXAMPLES + To list all conversion workspaces in a project and location us-central1, + run: + + $ gcloud database-migration conversion-workspaces list \ + --region=us-central1 + +REQUIRED FLAGS + Region resource - The region you want to list the conversion workspaces + for. 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 --region 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. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --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 datamigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/database-migration/ diff --git a/gcloud/database-migration/conversion-workspaces/list-background-jobs b/gcloud/database-migration/conversion-workspaces/list-background-jobs new file mode 100644 index 000000000..2220e8817 --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/list-background-jobs @@ -0,0 +1,72 @@ +NAME + gcloud database-migration conversion-workspaces list-background-jobs - list + background jobs in the conversion workspaces + +SYNOPSIS + gcloud database-migration conversion-workspaces list-background-jobs + (CONVERSION_WORKSPACE : --region=REGION) [--max-size=MAX_SIZE] + [--most-recent-per-job-type] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List background jobs in the conversion workspaces. + +EXAMPLES + To list the background jobs in a conversion workspaces in a project and + location us-central1, run: + + $ gcloud database-migration conversion-workspaces \ + list-background-jobs my-conversion-workspace \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Conversion workspace resource - The conversion workspace you want to get + the details of. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument conversion_workspace 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. + + CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument conversion_workspace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the region. + + To set the region attribute: + ▸ provide the argument conversion_workspace on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + +FLAGS + --max-size=MAX_SIZE + The maximum number of jobs to return. The service may return fewer than + this value. If unspecified, at most 100 jobs will be returned. The + maximum value is 100; values above 100 will be coerced to 100. + + --most-recent-per-job-type + Returns only the most recent job per job type. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 datamigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/database-migration/ diff --git a/gcloud/database-migration/conversion-workspaces/rollback b/gcloud/database-migration/conversion-workspaces/rollback new file mode 100644 index 000000000..e5e21df3b --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/rollback @@ -0,0 +1,62 @@ +NAME + gcloud database-migration conversion-workspaces rollback - rollback a + Database Migration Service conversion workspace + +SYNOPSIS + gcloud database-migration conversion-workspaces rollback + (CONVERSION_WORKSPACE : --region=REGION) [--no-async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Rollback a Database Migration Service conversion workspace to the last + committed snapshot. + +EXAMPLES + To rollback a conversion workspace to the last committed snapshot: + + $ gcloud database-migration conversion-workspaces rollback \ + my-conversion-workspace --region=us-central1 + +POSITIONAL ARGUMENTS + Conversion workspace resource - The conversion workspace to rollback. 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 conversion_workspace 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. + + CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument conversion_workspace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the conversion_workspace. + + To set the region attribute: + ▸ provide the argument conversion_workspace on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + +FLAGS + --no-async + Waits for the operation in progress to complete before returning. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/database-migration/conversion-workspaces/seed b/gcloud/database-migration/conversion-workspaces/seed new file mode 100644 index 000000000..ce0514066 --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/seed @@ -0,0 +1,116 @@ +NAME + gcloud database-migration conversion-workspaces seed - seed a Database + Migration Service conversion workspace + +SYNOPSIS + gcloud database-migration conversion-workspaces seed + (CONVERSION_WORKSPACE : --region=REGION) + (--destination-connection-profile=DESTINATION_CONNECTION_PROFILE + | --source-connection-profile=SOURCE_CONNECTION_PROFILE) [--no-async] + [--auto-commit] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Seed a Database Migration Service conversion workspace. + +EXAMPLES + To seed a conversion workspace: + + $ gcloud database-migration conversion-workspaces seed \ + my-conversion-workspace --region=us-central1 \ + --source-connection-profile=cp1 + +POSITIONAL ARGUMENTS + Conversion workspace resource - The conversion workspace to seed. 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 conversion_workspace 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. + + CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument conversion_workspace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the conversion_workspace. + + To set the region attribute: + ▸ provide the argument conversion_workspace on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + Exactly one of these must be specified: + + Connection profile resource - The connection profile to seed from. 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 --destination-connection-profile 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 region attribute: + ▸ provide the argument --destination-connection-profile on the + command line with a fully specified name; + ▸ provide the argument --region on the command line. + + --destination-connection-profile=DESTINATION_CONNECTION_PROFILE + ID of the connection_profile or fully qualified identifier for the + connection_profile. + + To set the connection_profile attribute: + ▫ provide the argument --destination-connection-profile on the + command line. + + Connection profile resource - The connection profile to seed from. 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 --source-connection-profile 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 region attribute: + ▸ provide the argument --source-connection-profile on the command + line with a fully specified name; + ▸ provide the argument --region on the command line. + + --source-connection-profile=SOURCE_CONNECTION_PROFILE + ID of the connection_profile or fully qualified identifier for the + connection_profile. + + To set the connection_profile attribute: + ▫ provide the argument --source-connection-profile on the command + line. + +OPTIONAL FLAGS + --no-async + Waits for the operation in progress to complete before returning. + + --auto-commit + Auto commits the conversion workspace. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/database-migration/conversion-workspaces/update b/gcloud/database-migration/conversion-workspaces/update new file mode 100644 index 000000000..6671e89ea --- /dev/null +++ b/gcloud/database-migration/conversion-workspaces/update @@ -0,0 +1,67 @@ +NAME + gcloud database-migration conversion-workspaces update - update a Database + Migration Service conversion workspace + +SYNOPSIS + gcloud database-migration conversion-workspaces update + (CONVERSION_WORKSPACE : --region=REGION) [--no-async] + [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Database Migration Service conversion workspace. + +EXAMPLES + To update a conversion workspace: + + $ gcloud database-migration conversion-workspaces update \ + my-conversion-workspace --region=us-central1 \ + --display-name=new-display-name + +POSITIONAL ARGUMENTS + Conversion workspace resource - The conversion workspace 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 conversion_workspace 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. + + CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument conversion_workspace on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the conversion_workspace. + + To set the region attribute: + ▸ provide the argument conversion_workspace on the command line + with a fully specified name; + ▸ provide the argument --region on the command line. + +FLAGS + --no-async + Waits for the operation in progress to complete before returning. + + --display-name=DISPLAY_NAME + A user-friendly name for the conversion workspace. The display name can + include letters, numbers, spaces, and hyphens, and must start with a + letter. The maximum length allowed is 60 characters. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/database-migration/help b/gcloud/database-migration/help index ca24c3fef..ba0e60610 100644 --- a/gcloud/database-migration/help +++ b/gcloud/database-migration/help @@ -18,12 +18,18 @@ GROUPS connection-profiles Manage Database Migration Service connection profiles. + conversion-workspaces + Manage Database Migration Service conversion workspaces. + migration-jobs Manage Database Migration Service migration jobs. operations Manage Database Migration Service operations. + private-connections + Manage Database Migration Service private connections. + NOTES This variant is also available: diff --git a/gcloud/database-migration/migration-jobs/create b/gcloud/database-migration/migration-jobs/create index ca2e3b328..3c60dd5e8 100644 --- a/gcloud/database-migration/migration-jobs/create +++ b/gcloud/database-migration/migration-jobs/create @@ -5,8 +5,10 @@ NAME SYNOPSIS gcloud database-migration migration-jobs create (MIGRATION_JOB : --region=REGION) --destination=DESTINATION - --source=SOURCE --type=TYPE [--no-async] [--display-name=DISPLAY_NAME] - [--dump-path=DUMP_PATH] [--labels=[KEY=VALUE,...]] + --source=SOURCE --type=TYPE [--no-async] [--commit-id=COMMIT_ID] + [--conversion-workspace=CONVERSION_WORKSPACE] + [--display-name=DISPLAY_NAME] [--dump-path=DUMP_PATH] [--filter=FILTER] + [--labels=[KEY=VALUE,...]] [--peer-vpc=PEER_VPC | --static-ip | [--vm-ip=VM_IP --vm-port=VM_PORT --vpc=VPC : --vm=VM]] [GCLOUD_WIDE_FLAG ...] @@ -16,11 +18,12 @@ DESCRIPTION creating the migration job: ▪ Create a source connection profile. See prerequisites here (https://cloud.google.com/database-migration/docs/mysql/configure-source-database). - ▪ Create a destination connection profile. For MySQL and PostgreSQL - migrations, use the cloudsql connection profile for DMS to create the - CloudSQL replica for you. + ▪ Create a destination connection profile. For migrating to Cloud SQL + for MySQL or Cloud SQL for PostgreSQL, use the cloudsql connection + profile for DMS to create the CloudSQL replica for you. ▪ Configure the connectivity method. See prerequisites here (https://cloud.google.com/database-migration/docs/mysql/configure-connectivity). + ▪ [Heterogeneous migrations only] Create a conversion workspace. EXAMPLES To create a continuous migration job with IP allowlist connectivity: @@ -43,6 +46,12 @@ EXAMPLES --destination=cp2 --vm=vm1 --vm-ip=1.1.1.1 --vm-port=1111 \ --vpc=projects/my-project/global/networks/my-network + To create a heterogeneous continuous migration job: + + $ gcloud database-migration migration-jobs create my-migration-job \ + --region=us-central1 --type=CONTINUOUS --source=cp1 \ + --destination=cp2 --conversion-workspace=cw + POSITIONAL ARGUMENTS Migration job resource - The migration job to create. The arguments in this group can be used to specify the attributes of this resource. (NOTE) @@ -133,6 +142,34 @@ OPTIONAL FLAGS --no-async Waits for the operation in progress to complete before returning. + --commit-id=COMMIT_ID + Commit id for the conversion workspace to use for creating the + migration job. If not specified, the latest commit id will be used by + default. + + Conversion workspace resource - Name of the conversion workspaces to be + used for the migration job 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 --conversion-workspace 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 region attribute: + ◆ provide the argument --conversion-workspace on the command line with + a fully specified name; + ◆ provide the argument --region on the command line. + + --conversion-workspace=CONVERSION_WORKSPACE + ID of the conversion_workspace or fully qualified identifier for the + conversion_workspace. + + To set the conversion_workspace attribute: + ▸ provide the argument --conversion-workspace on the command line. + --display-name=DISPLAY_NAME A user-friendly name for the migration job. The display name can include letters, numbers, spaces, and hyphens, and must start with a @@ -142,6 +179,12 @@ OPTIONAL FLAGS Path to the dump file in Google Cloud Storage, in the format: gs://[BUCKET_NAME]/[OBJECT_NAME]. + --filter=FILTER + Filter the entities based on (AIP-160)[https://google.aip.dev/160] + standard. Example: to filter all tables whose name start with + "Employee" and are present under schema "Company", use filter as + "parent = Company and TABLE=Employee" + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/database-migration/private-connections/create b/gcloud/database-migration/private-connections/create new file mode 100644 index 000000000..3ec3137cf --- /dev/null +++ b/gcloud/database-migration/private-connections/create @@ -0,0 +1,106 @@ +NAME + gcloud database-migration private-connections create - create a Database + Migration private connection + +SYNOPSIS + gcloud database-migration private-connections create + (PRIVATE_CONNECTION : --region=REGION) --display-name=DISPLAY_NAME + (--subnet=SUBNET --vpc=VPC) [--no-async] [--labels=[KEY=VALUE,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Database Migration private connection + +EXAMPLES + To create a private connection called 'my-private-connection', run: + + $ gcloud database-migration private-connections create \ + my-private-connection --region=us-central1 \ + --display-name=my-private-connection --vpc=vpc-example \ + --subnet=10.0.0.0/29 + + To use a private connection, all migrations and connection profiles that use this configuration must be in the same region. + +POSITIONAL ARGUMENTS + Private connection resource - The private connection 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 private_connection 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. + + PRIVATE_CONNECTION + ID of the private_connection or fully qualified identifier for the + private_connection. + + To set the private_connection attribute: + ▸ provide the argument private_connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the private_connection. + + To set the region attribute: + ▸ provide the argument private_connection on the command line with + a fully specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + --display-name=DISPLAY_NAME + A user-friendly name for the private connection. The display name can + include letters, numbers, spaces, and hyphens, and must start with a + letter. The maximum length allowed is 60 characters. + + This must be specified. + + --subnet=SUBNET + A free subnet for peering. (CIDR of /29). + + This flag argument must be specified if any of the other arguments in + this group are specified. + + Vpc resource - Resource name of the private connection. 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 --vpc 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. + + --vpc=VPC + ID of the vpc or fully qualified identifier for the vpc. + + To set the vpc attribute: + ▫ provide the argument --vpc on the command line. + +OPTIONAL FLAGS + --no-async + Waits for the operation in progress to complete before returning. + + --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. diff --git a/gcloud/database-migration/private-connections/delete b/gcloud/database-migration/private-connections/delete new file mode 100644 index 000000000..1c6c14ac8 --- /dev/null +++ b/gcloud/database-migration/private-connections/delete @@ -0,0 +1,61 @@ +NAME + gcloud database-migration private-connections delete - delete a Database + Migration private connection + +SYNOPSIS + gcloud database-migration private-connections delete + (PRIVATE_CONNECTION : --region=REGION) [--no-async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Database Migration private connection + +EXAMPLES + To delete a private connection called 'my-private-connection', run: + + $ gcloud database-migration private-connections delete \ + my-private-connection --region=us-central1 + +POSITIONAL ARGUMENTS + Private connection resource - The private connection 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 private_connection 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. + + PRIVATE_CONNECTION + ID of the private_connection or fully qualified identifier for the + private_connection. + + To set the private_connection attribute: + ▸ provide the argument private_connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Cloud region for the private_connection. + + To set the region attribute: + ▸ provide the argument private_connection on the command line with + a fully specified name; + ▸ provide the argument --region on the command line. + +FLAGS + --no-async + Waits for the operation in progress to complete before returning. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. diff --git a/gcloud/database-migration/private-connections/describe b/gcloud/database-migration/private-connections/describe new file mode 100644 index 000000000..2c993fb97 --- /dev/null +++ b/gcloud/database-migration/private-connections/describe @@ -0,0 +1,61 @@ +NAME + gcloud database-migration private-connections describe - show details about + a database migration private connection + +SYNOPSIS + gcloud database-migration private-connections describe + (PRIVATE_CONNECTION : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show details about a private connection. + +EXAMPLES + To show details about a private connection called 'my-private-connection', + run: + + $ gcloud database-migration private-connections describe \ + my-private-connection --region=us-central1 + +POSITIONAL ARGUMENTS + Private connection resource - The private connection you want to get the + details of. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument private_connection 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. + + PRIVATE_CONNECTION + ID of the private_connection or fully qualified identifier for the + private_connection. + + To set the private_connection attribute: + ▸ provide the argument private_connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the region. + + To set the region attribute: + ▸ provide the argument private_connection on the command line with + a fully specified name; + ▸ provide the argument --region 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 datamigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/database-migration/ diff --git a/gcloud/database-migration/private-connections/help b/gcloud/database-migration/private-connections/help new file mode 100644 index 000000000..02b77f750 --- /dev/null +++ b/gcloud/database-migration/private-connections/help @@ -0,0 +1,30 @@ +NAME + gcloud database-migration private-connections - manage Database Migration + Service private connections + +SYNOPSIS + gcloud database-migration private-connections COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Commands for managing Database Migration Service private connections. + +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 Database Migration private connection. + + delete + Delete a Database Migration private connection. + + describe + Show details about a database migration private connection. + + list + List private connections. diff --git a/gcloud/database-migration/private-connections/list b/gcloud/database-migration/private-connections/list new file mode 100644 index 000000000..8f3758c4c --- /dev/null +++ b/gcloud/database-migration/private-connections/list @@ -0,0 +1,81 @@ +NAME + gcloud database-migration private-connections list - list private + connections + +SYNOPSIS + gcloud database-migration private-connections list --region=REGION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List private connections. + +EXAMPLES + To list all private connections in the current project and location + 'us-central1', run: + + $ gcloud database-migration private-connections list \ + --region=us-central1 + +REQUIRED FLAGS + Region resource - The region you want to list the private connections for. + 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 --region 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. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --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 datamigration/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/database-migration/ diff --git a/gcloud/dataflow/flex-template/build b/gcloud/dataflow/flex-template/build index 839d5b33d..be2a629ea 100644 --- a/gcloud/dataflow/flex-template/build +++ b/gcloud/dataflow/flex-template/build @@ -48,7 +48,7 @@ EXAMPLES To build the template image and flex template json file, run: $ gcloud dataflow flex-template build gs://template-file-gcs-path \ - --image-gcr-path=gcr://path-tos-tore-image \ + --image-gcr-path=gcr://path-to-store-image \ --jar=path/to/pipeline.jar --jar=path/to/dependency.jar \ --env=FLEX_TEMPLATE_JAVA_MAIN_CLASS=classpath \ --flex-template-base-image=JAVA11 \ diff --git a/gcloud/iam/workforce-pools/providers/create-oidc b/gcloud/iam/workforce-pools/providers/create-oidc index 848664447..6a5156691 100644 --- a/gcloud/iam/workforce-pools/providers/create-oidc +++ b/gcloud/iam/workforce-pools/providers/create-oidc @@ -8,7 +8,9 @@ SYNOPSIS --attribute-mapping=[ATTRIBUTE_MAPPING,...] --client-id=CLIENT_ID --issuer-uri=ISSUER_URI [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] + [--disabled] [--display-name=DISPLAY_NAME] + [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] + [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a new OIDC workforce pool provider. @@ -25,7 +27,9 @@ EXAMPLES --description="My workforce pool provider description." \ --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" --client-id="client-id" \ - --issuer-uri="https://test-idp.com" + --issuer-uri="https://test-idp.com" \ + --web-sso-response-type=id-token \ + --web-sso-assertion-claims-behavior=only-id-token-claims POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to create. @@ -187,6 +191,20 @@ OPTIONAL FLAGS A display name for the workforce pool provider. Cannot exceed 32 characters in length. + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR + The behavior for how OIDC Claims are included in the assertion object + used for attribute mapping and attribute condition. Use + only-id-token-claims to include only ID token claims. + WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be one of: + assertion-claims-behavior-unspecified, only-id-token-claims. + + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE + Response Type to request for in the OIDC Authorization Request for web + sign-in. Use id-token to select the implicit flow + (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). + WEB_SSO_RESPONSE_TYPE must be one of: id-token, + response-type-unspecified. + 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/iam/workforce-pools/providers/update-oidc b/gcloud/iam/workforce-pools/providers/update-oidc index 660385d32..b08ae3e31 100644 --- a/gcloud/iam/workforce-pools/providers/update-oidc +++ b/gcloud/iam/workforce-pools/providers/update-oidc @@ -8,7 +8,9 @@ SYNOPSIS [--async] [--attribute-condition=ATTRIBUTE_CONDITION] [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] [--client-id=CLIENT_ID] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] - [--issuer-uri=ISSUER_URI] [GCLOUD_WIDE_FLAG ...] + [--issuer-uri=ISSUER_URI] + [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] + [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Update an OIDC workforce pool provider. @@ -25,7 +27,9 @@ EXAMPLES --description="My workforce pool provider description." \ --disabled --attribute-mapping="google.subject=assertion.sub" \ --attribute-condition="true" --client-id="client-id" \ - --issuer-uri="https://test-idp.com" + --issuer-uri="https://test-idp.com" \ + --web-sso-response-type=id-token \ + --web-sso-assertion-claims-behavior=only-id-token-claims POSITIONAL ARGUMENTS Workforce pool provider resource - The workforce pool provider to update. @@ -186,6 +190,20 @@ FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR + The behavior for how OIDC Claims are included in the assertion object + used for attribute mapping and attribute condition. Use + only-id-token-claims to include only ID token claims. + WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be one of: + assertion-claims-behavior-unspecified, only-id-token-claims. + + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE + Response Type to request for in the OIDC Authorization Request for web + sign-in. Use id-token to select the implicit flow + (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). + WEB_SSO_RESPONSE_TYPE must be one of: id-token, + response-type-unspecified. + 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/looker/help b/gcloud/looker/help new file mode 100644 index 000000000..e494d005b --- /dev/null +++ b/gcloud/looker/help @@ -0,0 +1,28 @@ +NAME + gcloud looker - manage Looker resources + +SYNOPSIS + gcloud looker GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Looker resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + instances + Manage Looker instances. + + operations + Manage Looker operations. + +NOTES + This variant is also available: + + $ gcloud alpha looker + diff --git a/gcloud/looker/instances/create b/gcloud/looker/instances/create new file mode 100644 index 000000000..9f09a8b7d --- /dev/null +++ b/gcloud/looker/instances/create @@ -0,0 +1,222 @@ +NAME + gcloud looker instances create - create a Looker instance + +SYNOPSIS + gcloud looker instances create (INSTANCE : --region=REGION) + --edition=EDITION --oauth-client-id=OAUTH_CLIENT_ID + --oauth-client-secret=OAUTH_CLIENT_SECRET [--async] [--kms-key=KMS_KEY] + [--no-public-ip-enabled] + [--consumer-network=CONSUMER_NETWORK --private-ip-enabled + : --reserved-range=RESERVED_RANGE] + [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE + --deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] + [--maintenance-window-day=MAINTENANCE_WINDOW_DAY + --maintenance-window-time=MAINTENANCE_WINDOW_TIME] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new Looker instance. + + This command can fail for the following reasons: + ▪ An instance with the same name already exists. + ▪ The active account does not have permission to create instances. + ▪ --async flag is not passed + +EXAMPLES + To create a basic tier instance with the name my-looker-instance in region + us-central-1 with an edition of "LOOKER_CORE_STANDARD", run: + + $ gcloud looker instances create my-looker-instance \ + --region=us-central1 --edition="core-standard" \ + --oauth-client-id='looker' --oauth-client-secret='looker' \ + --async + + Note: It is recommended that the --async argument is provided when creating + a Looker instance. + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to create. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the instance. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +REQUIRED FLAGS + --edition=EDITION + The edition of the Looker instance. EDITION must be one of: + + core-embed-annual + A Looker (Google Cloud core) product for deploying and maintaining + external analytics and custom applications at scale. This can be + purchased via an annual contract. + + core-enterprise-annual + A Looker (Google Cloud core) product with enhanced security + features for a wide variety of internal BI and analytics use cases. + This can be purchased via an annual contract. + + core-standard + A Looker (Google Cloud core) product for small organizations or + teams with fewer than 50 users. This will be billed monthly while + the instance is active. + + core-standard-annual + A Looker (Google Cloud core) product for small organizations or + teams with fewer than 50 users. This can be purchased via an annual + contract. + + core-trial + Trial edition of Looker. + + --oauth-client-id=OAUTH_CLIENT_ID + The client ID from an external OAuth application. + + OAuth Application Credentials - Looker Instance OAuth login settings. + Setup an OAuth app that will allow users to authenticate and access the + instance. For more information see: + https://developers.google.com/identity/protocols/oauth2/web-server#creatingcred + + --oauth-client-secret=OAUTH_CLIENT_SECRET + The client secret from an external OAuth application. + + OAuth Application Credentials - Looker Instance OAuth login settings. + Setup an OAuth app that will allow users to authenticate and access the + instance. For more information see: + https://developers.google.com/identity/protocols/oauth2/web-server#creatingcred + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the Looker instance and backups. The 'Looker Service + Agent' service account must hold permission 'Cloud KMS CryptoKey + Encrypter/Decrypter'. The arguments in this group can be used to specify + the attributes of this resource. + + --kms-key=KMS_KEY + ID of the key or fully qualified identifier for the key. To set the + kms-key attribute: + ▸ provide the argument --kms-key on the command line. + + --public-ip-enabled + This specifies whether public IP is enabled on the Looker instance. + Enabled by default, use --no-public-ip-enabled to disable. + + Private IP - Assigns an internal, Google-hosted VPC IP address. Private IP + connectivity requires additional APIs and permissions. Private IP cannot + be disabled once it has been enabled. If enabled, consumer-network must be + assigned. + + --consumer-network=CONSUMER_NETWORK + The network name within the consumer project. This MUST be delared if + enabling private IP. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --private-ip-enabled + This specifies whether private IP is enabled on the Looker instance. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --reserved-range=RESERVED_RANGE + The name of a reserved IP address range within the consumer network + to be used for private service access connection. + + Deny Maintanence Period - You must allow at least 48 hours of maintenance + availability in a 60-day rolling window. Only contiguous availability + windows of at least two hours are considered. When setting a maintenance + exclusion please be aware that excluding application upgrades cannot + exceed 60-days and excluding infrastructure upgrades cannot exceed + 90-days. + + --deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE + End date of the deny maintenance period in format: YYYY-MM-DD + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE + Start date of the deny maintenance period in format: YYYY-MM-DD + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME + Time in UTC when the period starts and ends. A valid time of day must + be specified in 24hr format (ex: 13:00, 17:30, 23:45). + + This flag argument must be specified if any of the other arguments in + this group are specified. + + 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. + + --maintenance-window-day=MAINTENANCE_WINDOW_DAY + Day of week for maintenance window, in UTC time zone. To set the + maintenance-window-day attribute: + ▸ provide the argument --maintenance-window-day on the command + line. MAINTENANCE_WINDOW_DAY must be one of: friday, monday, + saturday, sunday, thursday, tuesday, wednesday. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --maintenance-window-time=MAINTENANCE_WINDOW_TIME + Hour of day for maintenance window, in UTC time zone. A valid time of + day must be specified in 24hr format (ex: 13:00, 17:30, 23:45). + Maintenance will be scheduled within 60 minutes. To set the + maintenance-window-time attribute: + ▸ provide the argument --maintenance-window-time on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1 API. The full documentation for this API + can be found at: https://looker.com/ + +NOTES + This variant is also available: + + $ gcloud alpha looker instances create + diff --git a/gcloud/looker/instances/delete b/gcloud/looker/instances/delete new file mode 100644 index 000000000..926279014 --- /dev/null +++ b/gcloud/looker/instances/delete @@ -0,0 +1,79 @@ +NAME + gcloud looker instances delete - delete a Looker instance + +SYNOPSIS + gcloud looker instances delete (INSTANCE : --region=REGION) [--async] + [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Looker instance. + + This command can fail for the following reasons: + ▪ The instance specified does not exist. + ▪ The active account does not have permission to access the given + instance. + +EXAMPLES + To delete an instance with the name my-looker-instance in your default + region, run: + + $ gcloud looker instances delete my-looker-instance --async + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to delete. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the instance. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --force + Force delete an instance. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 looker/v1 API. The full documentation for this API + can be found at: https://looker.com/ + +NOTES + This variant is also available: + + $ gcloud alpha looker instances delete + diff --git a/gcloud/looker/instances/describe b/gcloud/looker/instances/describe new file mode 100644 index 000000000..669a2280c --- /dev/null +++ b/gcloud/looker/instances/describe @@ -0,0 +1,74 @@ +NAME + gcloud looker instances describe - show metadata for a Looker + +SYNOPSIS + gcloud looker instances describe (INSTANCE : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Show metadata for a Looker instance. + + Displays all metadata associated with a Looker instance given a valid + instance name. + + This command can fail for the following reasons: + ▪ The instance specified does not exist. + ▪ The active account does not have permission to access the given + instance. + +EXAMPLES + To display the metadata for an instance with the name my-looker-instance in + the default region, run: + + $ gcloud looker instances describe my-looker-instance + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to describe. The arguments in this group can be used to specify + the attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the instance. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1 API. The full documentation for this API + can be found at: https://looker.com/ + +NOTES + This variant is also available: + + $ gcloud alpha looker instances describe + diff --git a/gcloud/looker/instances/export b/gcloud/looker/instances/export new file mode 100644 index 000000000..aa9a02593 --- /dev/null +++ b/gcloud/looker/instances/export @@ -0,0 +1,91 @@ +NAME + gcloud looker instances export - export a Looker instance + +SYNOPSIS + gcloud looker instances export (INSTANCE : --region=REGION) + --kms-key=KMS_KEY --target-gcs-uri=TARGET_GCS_URI + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command can fail for the following reasons: + ▪ The instance specified does not exist. + ▪ The active account does not have permission to access the given + instance. + ▪ The Google Cloud Storage bucket does not exist. + +EXAMPLES + To export an instance with the name my-looker-instance in the default + region, run: + + $ gcloud looker instances export my-looker-instance \ + --target-gcs-uri='gs://bucketName/folderName' \ + --kms-key='projects/my-project/locations/us-central1/keyRings/my\ + -key-ring/cryptoKeys/my-key' + + Note that the kms-key flag should be the full name of the kms key. + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to export. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The region of the instance. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the Looker instance and backups. The 'Looker Service + Agent' service account must hold role 'Cloud KMS CryptoKey Encrypter'. The + arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + --kms-key=KMS_KEY + Fully qualified identifier (name) for the key. + + Export Destination - The path and storage where the export will be stored. + + This must be specified. + + --target-gcs-uri=TARGET_GCS_URI + The path to the folder in Google Cloud Storage where the export will + be stored. The URI is in the form gs://bucketName/folderName. The + Looker Service Agent should have the role Storage Object Creator. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha looker instances export + diff --git a/gcloud/looker/instances/help b/gcloud/looker/instances/help new file mode 100644 index 000000000..5ffcdfc88 --- /dev/null +++ b/gcloud/looker/instances/help @@ -0,0 +1,86 @@ +NAME + gcloud looker instances - manage Looker instances + +SYNOPSIS + gcloud looker instances COMMAND [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To create an instance with the name my-looker-instance, with an edition of + "LOOKER_CORE_STANDARD", run: + + $ gcloud looker instances create my-looker-instance \ + --oauth-client-id='looker' --oauth-client-secret='looker' \ + --edition="core-standard" --async + + Note: It is recommended that the --async argument is provided when creating + a Looker instance. + + To delete an instance with the name my-looker-instance, run: + + $ gcloud looker instances delete my-looker-instance --async + + To display the details for an instance with name my-looker-instance, run: + + $ gcloud looker instances describe my-looker-instance + + To restart an instance with the name my-looker-instance, run: + + $ gcloud looker instances restart my-looker-instance --async + + To update an instance with the name my-looker-instance, run: + + $ gcloud looker instances update my-looker-instance --async + + To export an instance with the name my-looker-instance, run: + + $ gcloud looker instances export my-looker-instance \ + --target-gcs-uri='gs://bucketName/folderName' \ + --kms-key='projects/my-project/locations/us-central1/keyRings/my\ + -key-ring/cryptoKeys/my-key' + + To import an instance with the name my-looker-instance, run: + + $ gcloud looker instances import my-looker-instance \ + --source-gcs-uri='gs://bucketName/folderName' + + To list all the instances, run: + + $ gcloud looker instances list + +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 Looker instance. + + delete + Delete a Looker instance. + + describe + Show metadata for a Looker. + + export + Export a Looker instance. + + import + Import a Looker instance. + + list + List Looker instances. + + restart + Restart a Looker instance. + + update + Update a Looker instance. + +NOTES + This variant is also available: + + $ gcloud alpha looker instances + diff --git a/gcloud/looker/instances/import b/gcloud/looker/instances/import new file mode 100644 index 000000000..559ee262f --- /dev/null +++ b/gcloud/looker/instances/import @@ -0,0 +1,75 @@ +NAME + gcloud looker instances import - import a Looker instance + +SYNOPSIS + gcloud looker instances import (INSTANCE : --region=REGION) + --source-gcs-uri=SOURCE_GCS_URI [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command can fail for the following reasons: + ▪ The instance specified does not exist. + ▪ The active account does not have permission to access the given + instance. + ▪ The Google Cloud Storage bucket does not exist. + +EXAMPLES + To import an instance with the name my-looker-instance in the default + region, run: + + $ gcloud looker instances import my-looker-instance \ + --source-gcs-uri='gs://bucketName/folderName' + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to import. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The region of the instance. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + Import Destination - The path and storage where the import will be + retrieved from. + + This must be specified. + + --source-gcs-uri=SOURCE_GCS_URI + The path to the folder in Google Cloud Storage where the import will + be retrieved from. The URI is in the form gs://bucketName/folderName. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This variant is also available: + + $ gcloud alpha looker instances import + diff --git a/gcloud/looker/instances/list b/gcloud/looker/instances/list new file mode 100644 index 000000000..0d07a28d9 --- /dev/null +++ b/gcloud/looker/instances/list @@ -0,0 +1,86 @@ +NAME + gcloud looker instances list - list Looker instances + +SYNOPSIS + gcloud looker instances list [--region=REGION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all Looker instances under the specified project and region. + + To specify the maximum number of instances to list, use the --limit flag. + +EXAMPLES + To list up to five instances, run: + + $ gcloud looker instances list --limit=5 + +FLAGS + Region resource - The region of the instances to display. 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 --region on the command line with a fully + specified name; + ◆ set the property looker/region with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1 API. The full documentation for this API + can be found at: https://looker.com/ + +NOTES + This variant is also available: + + $ gcloud alpha looker instances list + diff --git a/gcloud/looker/instances/restart b/gcloud/looker/instances/restart new file mode 100644 index 000000000..9715a58f5 --- /dev/null +++ b/gcloud/looker/instances/restart @@ -0,0 +1,76 @@ +NAME + gcloud looker instances restart - restart a Looker instance + +SYNOPSIS + gcloud looker instances restart (INSTANCE : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Restart for a Looker instance. + + This command can fail for the following reasons: + ▪ The instance specified does not exist. + ▪ The active account does not have permission to access the given + instance. + +EXAMPLES + To restart an instance with the name my-looker-instance in the default + region, run: + + $ gcloud looker instances restart my-looker-instance --async + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to describe. The arguments in this group can be used to specify + the attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the instance. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +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 looker/v1 API. The full documentation for this API + can be found at: https://looker.com/ + +NOTES + This variant is also available: + + $ gcloud alpha looker instances restart + diff --git a/gcloud/looker/instances/update b/gcloud/looker/instances/update new file mode 100644 index 000000000..0a6c0a072 --- /dev/null +++ b/gcloud/looker/instances/update @@ -0,0 +1,194 @@ +NAME + gcloud looker instances update - update a Looker instance + +SYNOPSIS + gcloud looker instances update (INSTANCE : --region=REGION) + [--allowed-email-domains=[ALLOWED_EMAIL_DOMAINS,...]] [--async] + [--custom-domain=CUSTOM_DOMAIN] [--public-ip-enabled] + [--add-developer-users=ADD_DEVELOPER_USERS + --add-standard-users=ADD_STANDARD_USERS + --add-viewer-users=ADD_VIEWER_USERS] + [--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] + [--maintenance-window-day=MAINTENANCE_WINDOW_DAY + --maintenance-window-time=MAINTENANCE_WINDOW_TIME] + [--oauth-client-id=OAUTH_CLIENT_ID + --oauth-client-secret=OAUTH_CLIENT_SECRET] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update the metadata and/or configuration parameters of a Looker instance. + + This command can fail for the following reasons: + ▪ The instance specified does not exist. + ▪ The active account does not have permission to update the given + instance. + +EXAMPLES + To update the maintenance window to Sunday at 11:00 PM for a Looker + instance with the name my-looker-instance, run: + + $ gcloud looker instances update my-looker-instance \ + --maintenance-window-day=sunday \ + --maintenance-window-time='23:00' --async + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Looker instance + you want to update. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument instance on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. + + To set the instance attribute: + ▸ provide the argument instance on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the instance. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +FLAGS + Email Domain Allowlist for Scheduled Content - Define the email domains to + which your users can deliver Looker (Google Cloud core) content. + + --allowed-email-domains=[ALLOWED_EMAIL_DOMAINS,...] + This specifies the entire allowed email domain list. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + Custom Domains - Looker (Google Cloud core) lets you serve your + application through a custom domain. If you use a custom domain, Google + will provide a managed auto-renewing SSL certificate for security. + + DNS changes can take up to 24 hours to take effect. Your SSL certificate + will take several minutes to activate. Note that you must get the Type A + DNS Record from the Google Cloud Console and update with your domain + registrar for your custom domain to work properly. + + --custom-domain=CUSTOM_DOMAIN + Domain name wanted to serve the Looker instance. + + --public-ip-enabled + This specifies whether public IP is enabled on the Looker instance. + + User Allocations - There are ten Standard and two Developer users included + in the cost of the product. You can allocate additional Standard, Viewer, + and Developer users for this instance. It is an optional step and can be + modified later. + + With the Standard edition of Looker (Google Cloud core), you can provision + up to 50 total users, distributed across Viewer, Standard, and Developer. + + --add-developer-users=ADD_DEVELOPER_USERS + Number of additional Developer Users to allocate to the Looker + Instance. + + --add-standard-users=ADD_STANDARD_USERS + Number of additional Standard Users to allocate to the Looker + Instance. + + --add-viewer-users=ADD_VIEWER_USERS + Number of additional Viewer Users to allocate to the Looker Instance. + + Deny Maintanence Period - You must allow at least 48 hours of maintenance + availability in a 60-day rolling window. Only contiguous availability + windows of at least two hours are considered. When setting a maintenance + exclusion please be aware that excluding application upgrades cannot + exceed 60-days and excluding infrastructure upgrades cannot exceed + 90-days. + + --deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE + End date of the deny maintenance period in format: YYYY-MM-DD + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE + Start date of the deny maintenance period in format: YYYY-MM-DD + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME + Time in UTC when the period starts and ends. A valid time of day must + be specified in 24hr format (ex: 13:00, 17:30, 23:45). + + This flag argument must be specified if any of the other arguments in + this group are specified. + + 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. + + --maintenance-window-day=MAINTENANCE_WINDOW_DAY + Day of the week for the maintenance window, in UTC time zone. + MAINTENANCE_WINDOW_DAY must be one of: friday, monday, saturday, + sunday, thursday, tuesday, wednesday. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --maintenance-window-time=MAINTENANCE_WINDOW_TIME + Hour of day for maintenance window, in UTC time zone. A valid time of + day must be specified in 24hr format (ex: 13:00, 17:30, 23:45). + Maintenance will be scheduled within 60 minutes. To set the + maintenance-window-time attribute: + ▸ provide the argument --maintenance-window-time on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + OAuth Application Credentials - Looker Instance OAuth login settings. + Setup an OAuth app that will allow users to authenticate and access the + instance. For more information see: + https://developers.google.com/identity/protocols/oauth2/web-server#creatingcred + + --oauth-client-id=OAUTH_CLIENT_ID + The client ID from an external OAuth application. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --oauth-client-secret=OAUTH_CLIENT_SECRET + The client secret from an external OAuth application. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1 API. The full documentation for this API + can be found at: https://looker.com/ + +NOTES + This variant is also available: + + $ gcloud alpha looker instances update + diff --git a/gcloud/looker/operations/cancel b/gcloud/looker/operations/cancel new file mode 100644 index 000000000..5d5fbbd26 --- /dev/null +++ b/gcloud/looker/operations/cancel @@ -0,0 +1,67 @@ +NAME + gcloud looker operations cancel - cancel a Looker import or export + operation + +SYNOPSIS + gcloud looker operations cancel (OPERATION : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Cancel a Looker import or export operation. + +EXAMPLES + To cancel an operation named my-looker-operation in the default region, + run: + + $ gcloud looker operations cancel my-looker-operation + +POSITIONAL ARGUMENTS + Operation resource - Arguments and flags that specify the Looker operation + you want to describe. The arguments in this group can be used to specify + the attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument operation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the operation. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1 API. The full documentation for this API + can be found at: https://looker.com/ + +NOTES + This variant is also available: + + $ gcloud alpha looker operations cancel + diff --git a/gcloud/looker/operations/describe b/gcloud/looker/operations/describe new file mode 100644 index 000000000..a409068cf --- /dev/null +++ b/gcloud/looker/operations/describe @@ -0,0 +1,72 @@ +NAME + gcloud looker operations describe - show metadata for a Looker operation + +SYNOPSIS + gcloud looker operations describe (OPERATION : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Display all metadata associated with a Looker operation given a valid + operation name. + + This command can fail for the following reasons: + ▪ The operation specified does not exist. + ▪ The active account does not have permission to access the given + operation. + +EXAMPLES + To display the metadata for an operation named my-looker-operation in the + default region, run: + + $ gcloud looker operations describe my-looker-operation + +POSITIONAL ARGUMENTS + Operation resource - Arguments and flags that specify the Looker operation + you want to describe. The arguments in this group can be used to specify + the attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument operation on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + OPERATION + ID of the operation or fully qualified identifier for the operation. + + To set the operation attribute: + ▸ provide the argument operation on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Looker region of the operation. Overrides the default + looker/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument operation on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1 API. The full documentation for this API + can be found at: https://looker.com/ + +NOTES + This variant is also available: + + $ gcloud alpha looker operations describe + diff --git a/gcloud/looker/operations/help b/gcloud/looker/operations/help new file mode 100644 index 000000000..bc3714c01 --- /dev/null +++ b/gcloud/looker/operations/help @@ -0,0 +1,37 @@ +NAME + gcloud looker operations - manage Looker operations + +SYNOPSIS + gcloud looker operations COMMAND [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To display the details for an operation with name my-looker-op, run: + + $ gcloud looker operations describe my-looker-op + + To list all the operations, run: + + $ gcloud looker operations list + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + cancel + Cancel a Looker import or export operation. + + describe + Show metadata for a Looker operation. + + list + List Looker operations. + +NOTES + This variant is also available: + + $ gcloud alpha looker operations + diff --git a/gcloud/looker/operations/list b/gcloud/looker/operations/list new file mode 100644 index 000000000..9b38c53cd --- /dev/null +++ b/gcloud/looker/operations/list @@ -0,0 +1,86 @@ +NAME + gcloud looker operations list - list Looker operations + +SYNOPSIS + gcloud looker operations list [--region=REGION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all Looker operations under the specified project and region. + + To specify the maximum number of operations to list, use the --limit flag. + +EXAMPLES + To list up to five operations, run: + + $ gcloud looker operations list --limit=5 + +FLAGS + Region resource - The region of the operations to display. 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 --region on the command line with a fully + specified name; + ◆ set the property looker/region with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property looker/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the looker/v1 API. The full documentation for this API + can be found at: https://looker.com/ + +NOTES + This variant is also available: + + $ gcloud alpha looker operations list + diff --git a/gcloud/network-connectivity/service-connection-policies/create b/gcloud/network-connectivity/service-connection-policies/create index 6c40a0f42..22ec439eb 100644 --- a/gcloud/network-connectivity/service-connection-policies/create +++ b/gcloud/network-connectivity/service-connection-policies/create @@ -4,11 +4,11 @@ NAME SYNOPSIS gcloud network-connectivity service-connection-policies create - (SERVICE_CONNECTION_POLICY : --region=REGION) --network=NETWORK + SERVICE_CONNECTION_POLICY --network=NETWORK --service-class=SERVICE_CLASS (--subnets=[SUBNETS,...] : --psc-connection-limit=PSC_CONNECTION_LIMIT) [--async] [--description=DESCRIPTION] [--labels=KEY=VALUE] - [GCLOUD_WIDE_FLAG ...] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a new Service Connection Policy with the given name. @@ -25,9 +25,8 @@ EXAMPLES POSITIONAL ARGUMENTS Service connection policy resource - Name of the Service Connection Policy - to be created. The arguments in this group can be used to specify the - attributes of this resource. (NOTE) Some attributes are not given - arguments in this group but can be set in other ways. + to be created. This represents a Cloud resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. To set the project attribute: ◆ provide the argument service_connection_policy on the command line @@ -35,6 +34,11 @@ POSITIONAL ARGUMENTS ◆ set the property core/project; ◆ provide the argument --project on the command line. + To set the region attribute: + ◆ provide the argument service_connection_policy on the command line + with a fully specified name; + ◆ provide the argument --region on the command line. + This must be specified. SERVICE_CONNECTION_POLICY @@ -45,17 +49,6 @@ POSITIONAL ARGUMENTS ▸ provide the argument service_connection_policy on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. - - --region=REGION - The location Id. - - To set the region attribute: - ▸ provide the argument service_connection_policy on the command - line with a fully specified name; - ▸ provide the argument --region on the command line. - REQUIRED FLAGS Network resource - Network that this service connection policy applies to. E.g. projects/my-project/global/networks/net1 This represents a Cloud @@ -82,11 +75,29 @@ REQUIRED FLAGS This must be specified. - --subnets=[SUBNETS,...] - Subnetwork to use for IP address management. + Subnetwork resource - Subnetwork to use for IP address management. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. - This flag argument must be specified if any of the other arguments in - this group are specified. + To set the project attribute: + ▸ provide the argument --subnets on the command line with a fully + specified name; + ▸ set the property core/project; + ▸ provide the argument --project on the command line. + + To set the region attribute: + ▸ provide the argument --subnets on the command line with a fully + specified name; + ▸ provide the argument --region on the command line. + + This must be specified. + + --subnets=[SUBNETS,...] + IDs of the subnetworks or fully qualified identifiers for the + subnetworks. + + To set the subnetwork attribute: + ▫ provide the argument --subnets on the command line. --psc-connection-limit=PSC_CONNECTION_LIMIT Max number of PSC connections for this policy. @@ -102,6 +113,11 @@ OPTIONAL FLAGS --labels=KEY=VALUE List of label KEY=VALUE pairs to add. + --region=REGION + For resources [service connection policy, subnetwork], provides + fallback value for resource region attribute. When the resource's full + URI path is not provided, region will fallback to this flag value. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/run/deploy b/gcloud/run/deploy index aeb7b7b62..f197a93e4 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -172,7 +172,9 @@ FLAGS --port=PORT Container port to receive requests at. Also sets the $PORT environment variable. Must be a number between 1 and 65535, inclusive. To unset - this field, pass the special value "default". + this field, pass the special value "default". If updating an existing + service with a TCP startup probe pointing to the previous container + port, this will also update the probe port. --service-account=SERVICE_ACCOUNT Service account associated with the revision of the service. The diff --git a/gcloud/run/services/update b/gcloud/run/services/update index 7c3175840..e07528258 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -164,7 +164,9 @@ FLAGS --port=PORT Container port to receive requests at. Also sets the $PORT environment variable. Must be a number between 1 and 65535, inclusive. To unset - this field, pass the special value "default". + this field, pass the special value "default". If updating an existing + service with a TCP startup probe pointing to the previous container + port, this will also update the probe port. --service-account=SERVICE_ACCOUNT Service account associated with the revision of the service. The diff --git a/gcloud/sql/import/sql b/gcloud/sql/import/sql index e4823c3f2..eac5f3347 100644 --- a/gcloud/sql/import/sql +++ b/gcloud/sql/import/sql @@ -40,10 +40,10 @@ FLAGS complete. --database=DATABASE, -d DATABASE - Database to which the import is made. If not set, it is assumed that - the database is specified in the file to be imported. If your SQL dump - file includes a database statement, it will override the database set - in this flag. + Database to which the import is made. The database needs to be created + before importing. If not set, it is assumed that the database is + specified in the file to be imported. If your SQL dump file includes a + database statement, it will override the database set in this flag. --user=USER PostgreSQL user for this import operation. diff --git a/gcloud/sql/instances/import b/gcloud/sql/instances/import index 6f98899b1..bff8ce9f2 100644 --- a/gcloud/sql/instances/import +++ b/gcloud/sql/instances/import @@ -37,10 +37,10 @@ FLAGS complete. --database=DATABASE, -d DATABASE - Database to which the import is made. If not set, it is assumed that - the database is specified in the file to be imported. If your SQL dump - file includes a database statement, it will override the database set - in this flag. + Database to which the import is made. The database needs to be created + before importing. If not set, it is assumed that the database is + specified in the file to be imported. If your SQL dump file includes a + database statement, it will override the database set in this flag. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account,