diff --git a/gcloud/_version b/gcloud/_version index 0c0dc1d53..5bba4a41f 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,6 +1,6 @@ -Google Cloud SDK 383.0.1 -alpha 2022.04.26 -beta 2022.04.26 +Google Cloud SDK 384.0.0 +alpha 2022.05.02 +beta 2022.05.02 bq 2.0.74 -core 2022.04.26 -gsutil 5.9 +core 2022.05.02 +gsutil 5.10 diff --git a/gcloud/active-directory/peerings/create b/gcloud/active-directory/peerings/create index 2c2c1b3ab..e4799d5a4 100644 --- a/gcloud/active-directory/peerings/create +++ b/gcloud/active-directory/peerings/create @@ -48,7 +48,9 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --authorized-network=AUTHORIZED_NETWORK - Name of the managed Managed Microsoft AD domain you want to peer to. + Name of the Network that is authorized to communicate with Managed + Microsoft AD domain. This is usually the full path name of the network + in the peer project. --domain=DOMAIN Name of the managed Managed Microsoft AD domain you want to peer to. diff --git a/gcloud/alpha/active-directory/peerings/create b/gcloud/alpha/active-directory/peerings/create index f6ed5970d..149ac9cf4 100644 --- a/gcloud/alpha/active-directory/peerings/create +++ b/gcloud/alpha/active-directory/peerings/create @@ -48,7 +48,9 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --authorized-network=AUTHORIZED_NETWORK - Name of the managed Managed Microsoft AD domain you want to peer to. + Name of the Network that is authorized to communicate with Managed + Microsoft AD domain. This is usually the full path name of the network + in the peer project. --domain=DOMAIN Name of the managed Managed Microsoft AD domain you want to peer to. diff --git a/gcloud/alpha/auth/login b/gcloud/alpha/auth/login index 921fa85d1..b317c9e96 100644 --- a/gcloud/alpha/auth/login +++ b/gcloud/alpha/auth/login @@ -30,9 +30,9 @@ DESCRIPTION For authorization with external accounts (workload identity pools) or service accounts, the --cred-file flag must be specified with the path to the workload identity credential configuration file or service account key - file (JSON). Login with workload identity federation is not yet supported - in other Google Cloud CLIs (e.g. gsutil and bq) and is only applicable to - gcloud commands. For more information on workload identity federation, see: + file (JSON). Login with workload identity federation is also supported in + gsutil and this command is the recommended way of using external accounts. + For more information on workload identity federation, see: https://cloud.google.com/iam/docs/workload-identity-federation. For more information on authorization and credential types, see: diff --git a/gcloud/alpha/builds/enterprise-config/gitlab/create b/gcloud/alpha/builds/enterprise-config/gitlab/create new file mode 100644 index 000000000..4420740dd --- /dev/null +++ b/gcloud/alpha/builds/enterprise-config/gitlab/create @@ -0,0 +1,77 @@ +NAME + gcloud alpha builds enterprise-config gitlab create - create a GitLab + Enterprise config for use by Google Cloud Build + +SYNOPSIS + gcloud alpha builds enterprise-config gitlab create + --api-access-token-secret-version=API_ACCESS_TOKEN_SECRET_VERSION + --api-key-secret-version=API_KEY_SECRET_VERSION --host-uri=HOST_URI + --name=NAME + --read-access-token-secret-version=READ_ACCESS_TOKEN_SECRET_VERSION + --region=REGION --user-name=USER_NAME + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + [--service-directory-service=SERVICE_DIRECTORY_SERVICE] + [--ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a GitLab Enterprise config for use by Google Cloud Build. + +REQUIRED FLAGS + --api-access-token-secret-version=API_ACCESS_TOKEN_SECRET_VERSION + Secret Manager resource containing the API access token. The secret is + specified in resource URL format + projects/{secret_project}/secrets/{secret_name}/versions/{secret_version}. + + --api-key-secret-version=API_KEY_SECRET_VERSION + Secret Manager resource containing the Cloud Build API key that should + be associated with this config. The secret is specified in resource URL + format + projects/{secret_project}/secrets/{secret_name}/versions/{secret_version}. + + --host-uri=HOST_URI + The host uri of the GitLab Enterprise instance. + + --name=NAME + The name of the GitLab config. + + --read-access-token-secret-version=READ_ACCESS_TOKEN_SECRET_VERSION + Secret Manager resource containing the read access token. The secret is + specified in resource URL format + projects/{secret_project}/secrets/{secret_name}/versions/{secret_version}. + + --region=REGION + The Cloud location of the GitLab config. + + --user-name=USER_NAME + The GitLab user name that should be associated with this config. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret Manager resource containing the webhook secret. The secret is + specified in resource URL format + projects/{secret_project}/secrets/{secret_name}/versions/{secret_version}. + +OPTIONAL FLAGS + --service-directory-service=SERVICE_DIRECTORY_SERVICE + Service Directory service that should be used when making calls to the + GitLab Enterprise instance. + + If not specified, calls will be made over the public internet. + + --ssl-ca-file=SSL_CA_FILE + Path to a local file that contains SSL certificate to use for requests + to GitLab Enterprise. The certificate should be in PEM format. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/builds/enterprise-config/gitlab/delete b/gcloud/alpha/builds/enterprise-config/gitlab/delete index 944c85793..0d8ccac8d 100644 --- a/gcloud/alpha/builds/enterprise-config/gitlab/delete +++ b/gcloud/alpha/builds/enterprise-config/gitlab/delete @@ -3,15 +3,38 @@ NAME Enterprise config from Google Cloud Build SYNOPSIS - gcloud alpha builds enterprise-config gitlab delete CONFIG - [GCLOUD_WIDE_FLAG ...] + gcloud alpha builds enterprise-config gitlab delete + (CONFIG : --region=REGION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Delete a GitLab Enterprise config from Google Cloud Build. POSITIONAL ARGUMENTS - CONFIG - The id of the GitLab Enterprise config + GitLabConfig resource - GitLab Enterprise config. 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 CONFIG 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. + + CONFIG + ID of the gitLabConfig or fully qualified identifier for the + gitLabConfig. To set the config attribute: + ▸ provide the argument CONFIG on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --region=REGION + The Cloud location for the gitLabConfig. To set the region attribute: + ▸ provide the argument CONFIG on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/builds/enterprise-config/gitlab/describe b/gcloud/alpha/builds/enterprise-config/gitlab/describe index c44d0cf5d..6bc240fed 100644 --- a/gcloud/alpha/builds/enterprise-config/gitlab/describe +++ b/gcloud/alpha/builds/enterprise-config/gitlab/describe @@ -3,15 +3,38 @@ NAME Enterprise config in a Google Cloud project SYNOPSIS - gcloud alpha builds enterprise-config gitlab describe CONFIG - [GCLOUD_WIDE_FLAG ...] + gcloud alpha builds enterprise-config gitlab describe + (CONFIG : --region=REGION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Describe a GitLab Enterprise config in a Google Cloud project. POSITIONAL ARGUMENTS - CONFIG - The id of the GitLab Enterprise Config + GitLabConfig resource - GitLab Enterprise config. 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 CONFIG 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. + + CONFIG + ID of the gitLabConfig or fully qualified identifier for the + gitLabConfig. To set the config attribute: + ▸ provide the argument CONFIG on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --region=REGION + The Cloud location for the gitLabConfig. To set the region attribute: + ▸ provide the argument CONFIG on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/builds/enterprise-config/gitlab/help b/gcloud/alpha/builds/enterprise-config/gitlab/help index b42558735..3dfb8ca11 100644 --- a/gcloud/alpha/builds/enterprise-config/gitlab/help +++ b/gcloud/alpha/builds/enterprise-config/gitlab/help @@ -16,6 +16,10 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + create + (ALPHA) Create a GitLab Enterprise config for use by Google Cloud + Build. + delete (ALPHA) Delete a GitLab Enterprise config from Google Cloud Build. @@ -25,6 +29,10 @@ COMMANDS list (ALPHA) List all GitLab Enterprise configs in a Google Cloud project. + update + (ALPHA) Update a GitLab Enterprise config for use by Google Cloud + Build. + 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/builds/enterprise-config/gitlab/list b/gcloud/alpha/builds/enterprise-config/gitlab/list index 3dc349284..441d6b187 100644 --- a/gcloud/alpha/builds/enterprise-config/gitlab/list +++ b/gcloud/alpha/builds/enterprise-config/gitlab/list @@ -3,13 +3,29 @@ NAME Enterprise configs in a Google Cloud project SYNOPSIS - gcloud alpha builds enterprise-config gitlab list [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] - [GCLOUD_WIDE_FLAG ...] + gcloud alpha builds enterprise-config gitlab list [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) List all GitLab Enterprise configs in a Google Cloud project. +FLAGS + Region resource - Region for Cloud Build. 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 builds/region with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --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 builds/region. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/builds/enterprise-config/gitlab/update b/gcloud/alpha/builds/enterprise-config/gitlab/update new file mode 100644 index 000000000..edc779ce4 --- /dev/null +++ b/gcloud/alpha/builds/enterprise-config/gitlab/update @@ -0,0 +1,97 @@ +NAME + gcloud alpha builds enterprise-config gitlab update - update a GitLab + Enterprise config for use by Google Cloud Build + +SYNOPSIS + gcloud alpha builds enterprise-config gitlab update + (CONFIG : --region=REGION) + [--api-access-token-secret-version=API_ACCESS_TOKEN_SECRET_VERSION] + [--api-key-secret-version=API_KEY_SECRET_VERSION] [--host-uri=HOST_URI] + [--read-access-token-secret-version=READ_ACCESS_TOKEN_SECRET_VERSION] + [--service-directory-service=SERVICE_DIRECTORY_SERVICE] + [--ssl-ca-file=SSL_CA_FILE] [--user-name=USER_NAME] + [--webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a GitLab Enterprise config for use by Google Cloud Build. + +POSITIONAL ARGUMENTS + GitLabConfig resource - GitLab Enterprise config. 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 CONFIG 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. + + CONFIG + ID of the gitLabConfig or fully qualified identifier for the + gitLabConfig. To set the config attribute: + ▸ provide the argument CONFIG on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --region=REGION + The Cloud location for the gitLabConfig. To set the region attribute: + ▸ provide the argument CONFIG on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --api-access-token-secret-version=API_ACCESS_TOKEN_SECRET_VERSION + Secret Manager resource containing the API access token. The secret is + specified in resource URL format + projects/{secret_project}/secrets/{secret_name}/versions/{secret_version}. + + --api-key-secret-version=API_KEY_SECRET_VERSION + Secret Manager resource containing the Cloud Build API key that should + be associated with this config. The secret is specified in resource URL + format + projects/{secret_project}/secrets/{secret_name}/versions/{secret_version}. + + --host-uri=HOST_URI + The host uri of the GitLab Enterprise instance. + + --read-access-token-secret-version=READ_ACCESS_TOKEN_SECRET_VERSION + Secret Manager resource containing the read access token. The secret is + specified in resource URL format + projects/{secret_project}/secrets/{secret_name}/versions/{secret_version}. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + Service Directory service that should be used when making calls to the + GitLab Enterprise instance. + + If not specified, calls will be made over the public internet. + + --ssl-ca-file=SSL_CA_FILE + Path to a local file that contains SSL certificate to use for requests + to GitLab Enterprise. The certificate should be in PEM format. + + --user-name=USER_NAME + The GitLab user name that should be associated with this config. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret Manager resource containing the webhook secret. The secret is + specified in resource URL format + projects/{secret_project}/secrets/{secret_name}/versions/{secret_version}. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/builds/triggers/create/gitlab-enterprise b/gcloud/alpha/builds/triggers/create/gitlab-enterprise new file mode 100644 index 000000000..91bedf000 --- /dev/null +++ b/gcloud/alpha/builds/triggers/create/gitlab-enterprise @@ -0,0 +1,219 @@ +NAME + gcloud alpha builds triggers create gitlab-enterprise - create a build + trigger for a GitLab Enterprise repository + +SYNOPSIS + gcloud alpha builds triggers create gitlab-enterprise + (--trigger-config=PATH + | [--gitlab-config-resource=GITLAB_CONFIG_RESOURCE + --project-namespace=PROJECT_NAMESPACE + --region=REGION (--branch-pattern=REGEX | --tag-pattern=REGEX + | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; + default=CommentControlValueValuesEnum(COMMENTS_ENABLED, + 1)]) (--build-config=PATH | --inline-config=PATH + | --dockerfile=DOCKERFILE --dockerfile-dir=DOCKERFILE_DIR; + default="/" --dockerfile-image=DOCKERFILE_IMAGE) + : --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --name=NAME --require-approval + --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a build trigger for a GitLab Enterprise repository. + +EXAMPLES + To create a push trigger for all branches: + + $ gcloud alpha builds triggers create gitlab-enterprise \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --project-namespace="cloud-builders" \ + --gitlab-config-resource="projects/1234/locations/global/gitLabC\ + onfigs/5678" --branch-pattern=".*" --build-config="cloudbuild.yaml" + + To create a pull request trigger for main: + + $ gcloud alpha builds triggers create gitlab-enterprise \ + --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --project-namespace="cloud-builders" \ + --gitlab-config-resource="projects/1234/locations/global/gitLabC\ + onfigs/5678" --pull-request-pattern="^main$" \ + --build-config="cloudbuild.yaml" + +REQUIRED FLAGS + Exactly one of these must be specified: + + --trigger-config=PATH + Path to Build Trigger config file (JSON or YAML format). For more + details, see + https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.triggers#BuildTrigger + + Flag based trigger configuration + + --gitlab-config-resource=GITLAB_CONFIG_RESOURCE + GitLab config resource name. + + This flag must be specified if any of the other arguments in this + group are specified. + + --project-namespace=PROJECT_NAMESPACE + GitLab project namespace. + + This flag must be specified if any of the other arguments in this + group are specified. + + --region=REGION + The region of the Cloud Build Service to use. Must be set to a + supported region name (e.g. us-central1). If unset, the global + service region is used. This field is restricted. + + This flag must be specified if any of the other arguments in this + group are specified. + + --description=DESCRIPTION + Build trigger description. + + --ignored-files=[GLOB,...] + Glob filter. Changes only affecting ignored files won't trigger + builds. + + --included-files=[GLOB,...] + Glob filter. Changes affecting at least one included file will + trigger builds. + + --name=NAME + Build trigger name. + + --require-approval + Require manual approval for triggered builds. + + --service-account=SERVICE_ACCOUNT + The service account used for all user-controlled operations + including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and + CancelBuild. If no service account is set, then the standard Cloud + Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is + used instead. Format: + projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. + + --substitutions=[KEY=VALUE,...] + Parameters to be substituted in the build specification. + + For example (using some nonsensical substitution keys; all keys + must begin with an underscore): + + $ gcloud builds triggers create ... --config config.yaml + --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10 + + This will result in a build where every occurrence of + ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and + similarly for ${_NUM_CANDIES} and "10". + + Only the following built-in variables can be specified with the + --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME, + REVISION_ID, COMMIT_SHA, SHORT_SHA. + + For more details, see: + https://cloud.google.com/cloud-build/docs/api/build-requests#substitutions + + Exactly one of these must be specified: + + --branch-pattern=REGEX + A regular expression specifying which git branches to match. + + This pattern is used as a regex search for any incoming pushes. + For example, --branch-pattern=foo will match "foo", "foobar", and + "barfoo". Events on a branch that does not match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + --tag-pattern=REGEX + A regular expression specifying which git tags to match. + + This pattern is used as a regex search for any incoming pushes. + For example, --tag-pattern=foo will match "foo", "foobar", and + "barfoo". Events on a tag that does not match will be ignored. + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + Pull Request settings + + --pull-request-pattern=REGEX + Regular expression specifying which base git branch to match + for pull request events. + + This pattern is used as a regex search for the base branch (the + branch you are trying to merge into) for pull request updates. + For example, --pull-request-pattern=foo will match "foo", + "foobar", and "barfoo". + + The syntax of the regular expressions accepted is the syntax + accepted by RE2 and described at + https://github.com/google/re2/wiki/Syntax. + + This flag must be specified if any of the other arguments in + this group are specified. + + --comment-control=COMMENT_CONTROL; default=CommentControlValueValuesEnum(COMMENTS_ENABLED, 1) + Require a repository collaborator or owner to comment '/gcbrun' + on a pull request before running the build. + + Exactly one of these must be specified: + + --build-config=PATH + Path to a YAML or JSON file containing the build configuration in + the repository. + + For more details, see: + https://cloud.google.com/cloud-build/docs/build-config + + --inline-config=PATH + Local path to a YAML or JSON file containing a build + configuration. + + Dockerfile build configuration flags + + --dockerfile=DOCKERFILE + Path of Dockerfile to use for builds in the repository. + + If specified, a build config will be generated to run docker + build using the specified file. + + The filename is relative to the Dockerfile directory. + + --dockerfile-dir=DOCKERFILE_DIR; default="/" + Location of the directory containing the Dockerfile in the + repository. + + The directory will also be used as the Docker build context. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + If not specified, + gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will + be used. + + Use a build configuration (cloudbuild.yaml) file for building + multiple images in a single trigger. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/builds/triggers/create/help b/gcloud/alpha/builds/triggers/create/help index a1157570d..a1d3da85e 100644 --- a/gcloud/alpha/builds/triggers/create/help +++ b/gcloud/alpha/builds/triggers/create/help @@ -25,6 +25,9 @@ COMMANDS github (ALPHA) Create a build trigger for a GitHub repository. + gitlab-enterprise + (ALPHA) Create a build trigger for a GitLab Enterprise repository. + manual (ALPHA) Create a build trigger with a manual trigger event. diff --git a/gcloud/alpha/compute/backend-buckets/create b/gcloud/alpha/compute/backend-buckets/create index 82286ddb8..98784bc95 100644 --- a/gcloud/alpha/compute/backend-buckets/create +++ b/gcloud/alpha/compute/backend-buckets/create @@ -100,7 +100,7 @@ OPTIONAL FLAGS down to the client TTL value if necessary; an Expires header will be replaced with a suitable max-age directive. - The maximum allowed value is 86400s (1 day). + The maximum allowed value is 31,622,400s (1 year). When creating a new backend with CACHE_ALL_STATIC and the field is unset, or when switching to that mode and the field is unset, a default diff --git a/gcloud/alpha/compute/backend-buckets/update b/gcloud/alpha/compute/backend-buckets/update index 80c94774a..d4b2b293d 100644 --- a/gcloud/alpha/compute/backend-buckets/update +++ b/gcloud/alpha/compute/backend-buckets/update @@ -163,7 +163,7 @@ FLAGS down to the client TTL value if necessary; an Expires header will be replaced with a suitable max-age directive. - The maximum allowed value is 86400s (1 day). + The maximum allowed value is 31,622,400s (1 year). When creating a new backend with CACHE_ALL_STATIC and the field is unset, or when switching to that mode and the field is unset, a diff --git a/gcloud/alpha/compute/backend-services/create b/gcloud/alpha/compute/backend-services/create index 97a16cbfc..9bede59d3 100644 --- a/gcloud/alpha/compute/backend-services/create +++ b/gcloud/alpha/compute/backend-services/create @@ -158,7 +158,7 @@ FLAGS down to the client TTL value if necessary; an Expires header will be replaced with a suitable max-age directive. - The maximum allowed value is 86400s (1 day). + The maximum allowed value is 31,622,400s (1 year). When creating a new backend with CACHE_ALL_STATIC and the field is unset, or when switching to that mode and the field is unset, a default diff --git a/gcloud/alpha/compute/backend-services/update b/gcloud/alpha/compute/backend-services/update index 515bd90fb..dfb461d70 100644 --- a/gcloud/alpha/compute/backend-services/update +++ b/gcloud/alpha/compute/backend-services/update @@ -505,7 +505,7 @@ FLAGS down to the client TTL value if necessary; an Expires header will be replaced with a suitable max-age directive. - The maximum allowed value is 86400s (1 day). + The maximum allowed value is 31,622,400s (1 year). When creating a new backend with CACHE_ALL_STATIC and the field is unset, or when switching to that mode and the field is unset, a diff --git a/gcloud/alpha/compute/firewall-rules/migrate b/gcloud/alpha/compute/firewall-rules/migrate index 2ae28ee27..0538d733c 100644 --- a/gcloud/alpha/compute/firewall-rules/migrate +++ b/gcloud/alpha/compute/firewall-rules/migrate @@ -3,8 +3,8 @@ NAME Policy and move all customer defined firewall rules there SYNOPSIS - gcloud alpha compute firewall-rules migrate FIREWALL_POLICY - --network=NETWORK [GCLOUD_WIDE_FLAG ...] + gcloud alpha compute firewall-rules migrate --source-network=SOURCE_NETWORK + --target-firewall-policy=TARGET_FIREWALL_POLICY [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute firewall-rules migrate is used to create a new @@ -16,18 +16,17 @@ EXAMPLES To execute the migration for VPC Network 'my-network' which stores the result in 'my-policy' Network Firewall Policy, run: - $ gcloud alpha compute firewall-rules migrate my-policy \ - --network=my-network - -POSITIONAL ARGUMENTS - FIREWALL_POLICY - Name of the new Network Firewall Policy used to store the migration - result. + $ gcloud alpha compute firewall-rules migrate \ + --source-network=my-network --target-firewall-policy=my-policy REQUIRED FLAGS - --network=NETWORK + --source-network=SOURCE_NETWORK The VPC Network for which the migration should be performed. + --target-firewall-policy=TARGET_FIREWALL_POLICY + Name of the new Network Firewall Policy used to store the migration + result. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/public-advertised-prefixes/update b/gcloud/alpha/compute/public-advertised-prefixes/update index 616301ca7..23a9f2a0d 100644 --- a/gcloud/alpha/compute/public-advertised-prefixes/update +++ b/gcloud/alpha/compute/public-advertised-prefixes/update @@ -3,7 +3,8 @@ NAME Engine public advertised prefix SYNOPSIS - gcloud alpha compute public-advertised-prefixes update NAME --status=STATUS + gcloud alpha compute public-advertised-prefixes update NAME + (--announce-prefix | --status=STATUS | --withdraw-prefix) [GCLOUD_WIDE_FLAG ...] EXAMPLES @@ -12,14 +13,32 @@ EXAMPLES $ gcloud alpha compute public-advertised-prefixes update my-pap \ --status=ptr-configured + To announce a public advertised prefix: + + $ gcloud alpha compute public-advertised-prefixes update my-pap \ + --announce-prefix + + To withdraw a public advertised prefix: + + $ gcloud alpha compute public-advertised-prefixes update my-pap \ + --withdraw-prefix + POSITIONAL ARGUMENTS NAME Name of the public advertised prefix to operate on. REQUIRED FLAGS - --status=STATUS - The status of public advertised prefix. STATUS must be (currently only - one value is supported): ptr-configured. + Exactly one of these must be specified: + + --announce-prefix + Specify if the prefix will be announced. Default is false. + + --status=STATUS + The status of public advertised prefix. STATUS must be (currently + only one value is supported): ptr-configured. + + --withdraw-prefix + Specify if the prefix will be withdrawn. Default is false. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/public-delegated-prefixes/help b/gcloud/alpha/compute/public-delegated-prefixes/help index a5cc66113..e8520d964 100644 --- a/gcloud/alpha/compute/public-delegated-prefixes/help +++ b/gcloud/alpha/compute/public-delegated-prefixes/help @@ -35,6 +35,9 @@ COMMANDS list (ALPHA) List Google Compute Engine public delegated prefixes. + update + (ALPHA) Updates a Compute Engine public delegated prefix. + 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/compute/public-delegated-prefixes/update b/gcloud/alpha/compute/public-delegated-prefixes/update new file mode 100644 index 000000000..e7827e8b0 --- /dev/null +++ b/gcloud/alpha/compute/public-delegated-prefixes/update @@ -0,0 +1,52 @@ +NAME + gcloud alpha compute public-delegated-prefixes update - updates a Compute + Engine public delegated prefix + +SYNOPSIS + gcloud alpha compute public-delegated-prefixes update NAME + (--announce-prefix | --withdraw-prefix) [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To announce a regional v2 public delegated prefix: + + $ gcloud alpha compute public-delegated-prefixes update my-pdp \ + --announce-prefix --region=us-central1 + + To withdraw a regional v2 public delegated prefix: + + $ gcloud alpha compute public-delegated-prefixes update my-pdp \ + --withdraw-prefix --region=us-central1 + +POSITIONAL ARGUMENTS + NAME + Name of the public delegated prefix to operate on. + +REQUIRED FLAGS + Exactly one of these must be specified: + + --announce-prefix + Specify if the prefix will be announced. Default is false. + + --withdraw-prefix + Specify if the prefix will be withdrawn. Default is false. + +OPTIONAL FLAGS + --region=REGION + Region of the public delegated prefix 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 alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. + diff --git a/gcloud/alpha/compute/resource-policies/create/group-placement b/gcloud/alpha/compute/resource-policies/create/group-placement index 3aa6b3f6e..2056aa048 100644 --- a/gcloud/alpha/compute/resource-policies/create/group-placement +++ b/gcloud/alpha/compute/resource-policies/create/group-placement @@ -74,7 +74,10 @@ FLAGS share power, host and networking. --vm-count=VM_COUNT - Number of instances targeted by the group placement policy. + Number of instances targeted by the group placement policy. Google does + not recommend that you use this flag unless you use a compact policy + and you want your policy to work only if it contains this exact number + of VMs. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/compute/routers/update-bgp-peer b/gcloud/alpha/compute/routers/update-bgp-peer index 9833e0268..dd41660d4 100644 --- a/gcloud/alpha/compute/routers/update-bgp-peer +++ b/gcloud/alpha/compute/routers/update-bgp-peer @@ -5,10 +5,9 @@ NAME SYNOPSIS gcloud alpha compute routers update-bgp-peer NAME --peer-name=PEER_NAME [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] - [--advertisement-mode=MODE] [--async] - [--[no-]clear-md5-authentication-key] [--[no-]enable-ipv6] - [--[no-]enabled] [--interface=INTERFACE] [--ip-address=IP_ADDRESS] - [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] + [--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] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] [--peer-asn=PEER_ASN] [--peer-ip-address=PEER_IP_ADDRESS] [--peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS] @@ -55,10 +54,8 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. - --[no-]clear-md5-authentication-key - Remove MD5 authentication from the BGP peer. Use - --clear-md5-authentication-key to enable and - --no-clear-md5-authentication-key to disable. + --clear-md5-authentication-key + If specified, remove MD5 authentication from the BGP peer. --[no-]enable-ipv6 If IPv6 is enabled, the peer connection can be established with IPv6 diff --git a/gcloud/alpha/compute/snapshots/create b/gcloud/alpha/compute/snapshots/create index d5405a05a..75ba9f5a6 100644 --- a/gcloud/alpha/compute/snapshots/create +++ b/gcloud/alpha/compute/snapshots/create @@ -5,7 +5,8 @@ SYNOPSIS gcloud alpha compute snapshots create NAME [--async] [--chain-name=CHAIN_NAME] [--csek-key-file=FILE] [--description=DESCRIPTION] [--guest-flush] [--labels=[KEY=VALUE,...]] - [--source-disk=SOURCE_DISK] [--source-disk-key-file=FILE] + [--snapshot-type=SNAPSHOT_TYPE] [--source-disk=SOURCE_DISK] + [--source-disk-key-file=FILE] [--source-instant-snapshot=SOURCE_INSTANT_SNAPSHOT] [--storage-location=LOCATION] [--source-disk-region=SOURCE_DISK_REGION @@ -69,6 +70,11 @@ FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --snapshot-type=SNAPSHOT_TYPE + Type of snapshot. If a snapshot type is not specified, a STANDARD + snapshot will be created. SNAPSHOT_TYPE must be one of: ARCHIVE, + STANDARD. + --source-disk=SOURCE_DISK Source disk used to create the snapshot. To create a snapshot from a source disk in a different project, specify the full path to the source diff --git a/gcloud/alpha/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create index e5a36a54e..641c9175c 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/create +++ b/gcloud/alpha/compute/tpus/queued-resources/create @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha compute tpus queued-resources create - (QUEUED_RESOURCE : --zone=ZONE) [--accelerator-type=ACCELERATOR_TYPE] - [--async] [--node-id=NODE_ID] [--runtime-version=RUNTIME_VERSION] + (QUEUED_RESOURCE : --zone=ZONE) --accelerator-type=ACCELERATOR_TYPE + --node-id=NODE_ID --runtime-version=RUNTIME_VERSION [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -51,14 +51,10 @@ POSITIONAL ARGUMENTS ▸ provide the argument --zone on the command line; ▸ set the property compute/zone. -FLAGS +REQUIRED FLAGS --accelerator-type=ACCELERATOR_TYPE Accelerator type for the TPU. - --async - Return immediately, without waiting for the operation in progress to - complete. - --node-id=NODE_ID The unqualified Node identifier, used to identify the TPU in the Nodes collection once provisioned. @@ -66,6 +62,11 @@ FLAGS --runtime-version=RUNTIME_VERSION Runtime version for the TPU, such as 2.3. +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/container/fleet/mesh/update b/gcloud/alpha/container/fleet/mesh/update index 53b52524a..7777df376 100644 --- a/gcloud/alpha/container/fleet/mesh/update +++ b/gcloud/alpha/container/fleet/mesh/update @@ -4,16 +4,18 @@ NAME SYNOPSIS gcloud alpha container fleet mesh update --control-plane=CONTROL_PLANE - [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + [--membership=MEMBERSHIP | --memberships=MEMBERSHIPS] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update the Service Mesh Feature Spec of a Membership. EXAMPLES - To update the control plane management of a Membership named MEMBERSHIP, - run: + To update the control plane management of comma separated Memberships like + membership1,membership2, run: - $ gcloud alpha container fleet mesh update --membership=MEMBERSHIP \ + $ gcloud alpha container fleet mesh update \ + --memberships=membership1,membership2 \ --control-plane=CONTROL_PLANE REQUIRED FLAGS @@ -22,8 +24,17 @@ REQUIRED FLAGS of: automatic, manual. OPTIONAL FLAGS - --membership=MEMBERSHIP - The Membership name to update. + At most one of these can be specified: + + --membership=MEMBERSHIP + (DEPRECATED) Membership name to update. + + The --membership flag is now deprecated. Please use --memberships + instead. + + --memberships=MEMBERSHIPS + Membership names to update, separated by commas if multiple are + supplied. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -37,5 +48,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 container fleet mesh update diff --git a/gcloud/alpha/container/hub/mesh/update b/gcloud/alpha/container/hub/mesh/update index fc58434b0..a45e93d58 100644 --- a/gcloud/alpha/container/hub/mesh/update +++ b/gcloud/alpha/container/hub/mesh/update @@ -4,16 +4,18 @@ NAME SYNOPSIS gcloud alpha container hub mesh update --control-plane=CONTROL_PLANE - [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + [--membership=MEMBERSHIP | --memberships=MEMBERSHIPS] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update the Service Mesh Feature Spec of a Membership. EXAMPLES - To update the control plane management of a Membership named MEMBERSHIP, - run: + To update the control plane management of comma separated Memberships like + membership1,membership2, run: - $ gcloud alpha container hub mesh update --membership=MEMBERSHIP \ + $ gcloud alpha container hub mesh update \ + --memberships=membership1,membership2 \ --control-plane=CONTROL_PLANE REQUIRED FLAGS @@ -22,8 +24,17 @@ REQUIRED FLAGS of: automatic, manual. OPTIONAL FLAGS - --membership=MEMBERSHIP - The Membership name to update. + At most one of these can be specified: + + --membership=MEMBERSHIP + (DEPRECATED) Membership name to update. + + The --membership flag is now deprecated. Please use --memberships + instead. + + --memberships=MEMBERSHIPS + Membership names to update, separated by commas if multiple are + supplied. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -37,5 +48,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 container hub mesh update diff --git a/gcloud/alpha/deploy/releases/create b/gcloud/alpha/deploy/releases/create index 5aef23f9a..a39831b03 100644 --- a/gcloud/alpha/deploy/releases/create +++ b/gcloud/alpha/deploy/releases/create @@ -38,11 +38,12 @@ EXAMPLES $ gcloud alpha deploy releases create 'my-release-$DATE-$TIME' \ --delivery-pipeline=my-pipeline --region=us-central1 - If the current UTC date and time is set to 2021-12-21 12:02, then the created release - will have its name set as my-release-20211221-1202. + If the current UTC date and time is set to 2021-12-21 12:02, then the + created release will have its name set as my-release-20211221-1202. - When using these parameters, please be sure to wrap the release name in single quotes - or else the template parameters will be overriden by environment variables. + When using these parameters, please be sure to wrap the release name in + single quotes or else the template parameters will be overridden by + environment variables. POSITIONAL ARGUMENTS Release resource - The name of the Release. The arguments in this group diff --git a/gcloud/alpha/emulators/datastore/start b/gcloud/alpha/emulators/datastore/start index b5df30175..c6842b040 100644 --- a/gcloud/alpha/emulators/datastore/start +++ b/gcloud/alpha/emulators/datastore/start @@ -2,9 +2,10 @@ NAME gcloud alpha emulators datastore start - start a local datastore emulator SYNOPSIS - gcloud alpha emulators datastore start - [--consistency=CONSISTENCY; default=0.9] [--data-dir=DATA_DIR] - [--host-port=HOST_PORT] [--no-store-on-disk] [GCLOUD_WIDE_FLAG ...] + gcloud alpha emulators datastore start [--data-dir=DATA_DIR] + [--host-port=HOST_PORT] [--no-store-on-disk] + [--consistency=CONSISTENCY; default=0.9 + | --use-firestore-in-datastore-mode] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command starts a local datastore emulator. @@ -15,12 +16,6 @@ EXAMPLES $ gcloud alpha emulators datastore start --data-dir=DATA-DIR FLAGS - --consistency=CONSISTENCY; default=0.9 - Fraction of eventually consistent operations that should succeed - immediately. Setting to 1.0 can be useful for unit tests, but may mask - incorrect assumptions about non-ancestor queries which are eventually - consistent. - --data-dir=DATA_DIR The directory to be used to store/retrieve data/config for an emulator run. The default value is /emulators/datastore. The @@ -44,6 +39,19 @@ FLAGS Whether data should be persisted to disk. Enabled by default, use --no-store-on-disk to disable. + At most one of these can be specified: + + --consistency=CONSISTENCY; default=0.9 + Fraction of eventually consistent operations that should succeed + immediately. Setting to 1.0 can be useful for unit tests, but may + mask incorrect assumptions about non-ancestor queries which are + eventually consistent. + + --use-firestore-in-datastore-mode + Runs the emulator in Cloud Firestore in Datastore Mode. Reads are + always strongly consistent and --consistency flag may not be + specified. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index 7e072ab21..e5d061c6b 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -186,7 +186,7 @@ FLAGS ◆ dotnet3: .NET Framework 3 ◆ ruby26: Ruby 2.6 ◆ ruby27: Ruby 2.7 - ◆ ruby30: Ruby 3.0 (preview) + ◆ ruby30: Ruby 3.0 ◆ nodejs6: Node.js 6 (deprecated) ◆ nodejs8: Node.js 8 (deprecated) diff --git a/gcloud/alpha/resource-manager/tags/bindings/create b/gcloud/alpha/resource-manager/tags/bindings/create index b5c2f434e..490301685 100644 --- a/gcloud/alpha/resource-manager/tags/bindings/create +++ b/gcloud/alpha/resource-manager/tags/bindings/create @@ -64,5 +64,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags bindings create + + $ gcloud beta resource-manager tags bindings create diff --git a/gcloud/alpha/resource-manager/tags/bindings/delete b/gcloud/alpha/resource-manager/tags/bindings/delete index 65ea8efe3..5aafc427b 100644 --- a/gcloud/alpha/resource-manager/tags/bindings/delete +++ b/gcloud/alpha/resource-manager/tags/bindings/delete @@ -64,5 +64,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags bindings delete + + $ gcloud beta resource-manager tags bindings delete diff --git a/gcloud/alpha/resource-manager/tags/bindings/help b/gcloud/alpha/resource-manager/tags/bindings/help index 2f5d74dcc..ff0349abd 100644 --- a/gcloud/alpha/resource-manager/tags/bindings/help +++ b/gcloud/alpha/resource-manager/tags/bindings/help @@ -33,5 +33,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags bindings + + $ gcloud beta resource-manager tags bindings diff --git a/gcloud/alpha/resource-manager/tags/bindings/list b/gcloud/alpha/resource-manager/tags/bindings/list index 8e5bfdd8e..a4614c54a 100644 --- a/gcloud/alpha/resource-manager/tags/bindings/list +++ b/gcloud/alpha/resource-manager/tags/bindings/list @@ -78,5 +78,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags bindings list + + $ gcloud beta resource-manager tags bindings list diff --git a/gcloud/alpha/resource-manager/tags/help b/gcloud/alpha/resource-manager/tags/help index acd834872..8ae7fac47 100644 --- a/gcloud/alpha/resource-manager/tags/help +++ b/gcloud/alpha/resource-manager/tags/help @@ -35,5 +35,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags + + $ gcloud beta resource-manager tags diff --git a/gcloud/alpha/resource-manager/tags/holds/create b/gcloud/alpha/resource-manager/tags/holds/create index e9e3f9ceb..bf419728c 100644 --- a/gcloud/alpha/resource-manager/tags/holds/create +++ b/gcloud/alpha/resource-manager/tags/holds/create @@ -61,5 +61,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags holds create + + $ gcloud beta resource-manager tags holds create diff --git a/gcloud/alpha/resource-manager/tags/holds/delete b/gcloud/alpha/resource-manager/tags/holds/delete index 54744873f..7ca77e6db 100644 --- a/gcloud/alpha/resource-manager/tags/holds/delete +++ b/gcloud/alpha/resource-manager/tags/holds/delete @@ -39,5 +39,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags holds delete + + $ gcloud beta resource-manager tags holds delete diff --git a/gcloud/alpha/resource-manager/tags/holds/help b/gcloud/alpha/resource-manager/tags/holds/help index 11fc38a2d..b89160b86 100644 --- a/gcloud/alpha/resource-manager/tags/holds/help +++ b/gcloud/alpha/resource-manager/tags/holds/help @@ -31,5 +31,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags holds + + $ gcloud beta resource-manager tags holds diff --git a/gcloud/alpha/resource-manager/tags/holds/list b/gcloud/alpha/resource-manager/tags/holds/list index 5d9811c22..a3dc55f66 100644 --- a/gcloud/alpha/resource-manager/tags/holds/list +++ b/gcloud/alpha/resource-manager/tags/holds/list @@ -92,5 +92,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags holds list + + $ gcloud beta resource-manager tags holds list diff --git a/gcloud/alpha/resource-manager/tags/keys/add-iam-policy-binding b/gcloud/alpha/resource-manager/tags/keys/add-iam-policy-binding index b951b7133..8b0758d6a 100644 --- a/gcloud/alpha/resource-manager/tags/keys/add-iam-policy-binding +++ b/gcloud/alpha/resource-manager/tags/keys/add-iam-policy-binding @@ -111,5 +111,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags keys add-iam-policy-binding + + $ gcloud beta resource-manager tags keys add-iam-policy-binding diff --git a/gcloud/alpha/resource-manager/tags/keys/create b/gcloud/alpha/resource-manager/tags/keys/create index 5f3ebf367..87ff64505 100644 --- a/gcloud/alpha/resource-manager/tags/keys/create +++ b/gcloud/alpha/resource-manager/tags/keys/create @@ -65,5 +65,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags keys create + + $ gcloud beta resource-manager tags keys create diff --git a/gcloud/alpha/resource-manager/tags/keys/delete b/gcloud/alpha/resource-manager/tags/keys/delete index 067850e13..f91904b0d 100644 --- a/gcloud/alpha/resource-manager/tags/keys/delete +++ b/gcloud/alpha/resource-manager/tags/keys/delete @@ -44,5 +44,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags keys delete + + $ gcloud beta resource-manager tags keys delete diff --git a/gcloud/alpha/resource-manager/tags/keys/describe b/gcloud/alpha/resource-manager/tags/keys/describe index 480357283..c568e1dc9 100644 --- a/gcloud/alpha/resource-manager/tags/keys/describe +++ b/gcloud/alpha/resource-manager/tags/keys/describe @@ -39,5 +39,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags keys describe + + $ gcloud beta resource-manager tags keys describe diff --git a/gcloud/alpha/resource-manager/tags/keys/get-iam-policy b/gcloud/alpha/resource-manager/tags/keys/get-iam-policy index 3cb2693a5..26a91fbf7 100644 --- a/gcloud/alpha/resource-manager/tags/keys/get-iam-policy +++ b/gcloud/alpha/resource-manager/tags/keys/get-iam-policy @@ -40,5 +40,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags keys get-iam-policy + + $ gcloud beta resource-manager tags keys get-iam-policy diff --git a/gcloud/alpha/resource-manager/tags/keys/help b/gcloud/alpha/resource-manager/tags/keys/help index 5a5a54d1d..ed1bf3c54 100644 --- a/gcloud/alpha/resource-manager/tags/keys/help +++ b/gcloud/alpha/resource-manager/tags/keys/help @@ -49,5 +49,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags keys + + $ gcloud beta resource-manager tags keys diff --git a/gcloud/alpha/resource-manager/tags/keys/list b/gcloud/alpha/resource-manager/tags/keys/list index 731ae6533..21cc0c2f0 100644 --- a/gcloud/alpha/resource-manager/tags/keys/list +++ b/gcloud/alpha/resource-manager/tags/keys/list @@ -61,5 +61,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags keys list + + $ gcloud beta resource-manager tags keys list diff --git a/gcloud/alpha/resource-manager/tags/keys/remove-iam-policy-binding b/gcloud/alpha/resource-manager/tags/keys/remove-iam-policy-binding index 2b730e1ef..0242da7ea 100644 --- a/gcloud/alpha/resource-manager/tags/keys/remove-iam-policy-binding +++ b/gcloud/alpha/resource-manager/tags/keys/remove-iam-policy-binding @@ -118,5 +118,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags keys remove-iam-policy-binding + + $ gcloud beta resource-manager tags keys remove-iam-policy-binding diff --git a/gcloud/alpha/resource-manager/tags/keys/set-iam-policy b/gcloud/alpha/resource-manager/tags/keys/set-iam-policy index ef7fdc778..e729959b2 100644 --- a/gcloud/alpha/resource-manager/tags/keys/set-iam-policy +++ b/gcloud/alpha/resource-manager/tags/keys/set-iam-policy @@ -51,5 +51,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags keys set-iam-policy + + $ gcloud beta resource-manager tags keys set-iam-policy diff --git a/gcloud/alpha/resource-manager/tags/keys/update b/gcloud/alpha/resource-manager/tags/keys/update index 5196a6994..7b6b8f91b 100644 --- a/gcloud/alpha/resource-manager/tags/keys/update +++ b/gcloud/alpha/resource-manager/tags/keys/update @@ -16,7 +16,7 @@ EXAMPLES $ gcloud alpha resource-manager tags keys update tagKeys/123 \ --description=foobar - To update a TagKey named ``env" under organization 456, run: + To update a TagKey named env under organization 456, run: $ gcloud alpha resource-manager tags keys update 456/env \ --description=foobar @@ -50,5 +50,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags keys update + + $ gcloud beta resource-manager tags keys update diff --git a/gcloud/alpha/resource-manager/tags/values/add-iam-policy-binding b/gcloud/alpha/resource-manager/tags/values/add-iam-policy-binding index 0a143ff5c..37192b892 100644 --- a/gcloud/alpha/resource-manager/tags/values/add-iam-policy-binding +++ b/gcloud/alpha/resource-manager/tags/values/add-iam-policy-binding @@ -112,5 +112,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags values add-iam-policy-binding + + $ gcloud beta resource-manager tags values add-iam-policy-binding diff --git a/gcloud/alpha/resource-manager/tags/values/create b/gcloud/alpha/resource-manager/tags/values/create index 85124347f..b5c62853f 100644 --- a/gcloud/alpha/resource-manager/tags/values/create +++ b/gcloud/alpha/resource-manager/tags/values/create @@ -69,5 +69,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags values create + + $ gcloud beta resource-manager tags values create diff --git a/gcloud/alpha/resource-manager/tags/values/delete b/gcloud/alpha/resource-manager/tags/values/delete index 4f92029b4..cd08a7d2c 100644 --- a/gcloud/alpha/resource-manager/tags/values/delete +++ b/gcloud/alpha/resource-manager/tags/values/delete @@ -44,5 +44,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags values delete + + $ gcloud beta resource-manager tags values delete diff --git a/gcloud/alpha/resource-manager/tags/values/describe b/gcloud/alpha/resource-manager/tags/values/describe index cb2b80a4b..660759501 100644 --- a/gcloud/alpha/resource-manager/tags/values/describe +++ b/gcloud/alpha/resource-manager/tags/values/describe @@ -11,12 +11,12 @@ DESCRIPTION name or namespaced name. EXAMPLES - To describe a TagValue with id ``123", run: + To describe a TagValue with id 123, run: $ gcloud alpha resource-manager tags values describe tagValues/123 - To describe a TagValue with name ``dev" with the tagKey ``env" under ' - 'organizations ``456", run: + To describe a TagValue with name dev with the tagKey env under + organizations 456, run: $ gcloud alpha resource-manager tags values describe 456/env/dev @@ -40,5 +40,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags values describe + + $ gcloud beta resource-manager tags values describe diff --git a/gcloud/alpha/resource-manager/tags/values/get-iam-policy b/gcloud/alpha/resource-manager/tags/values/get-iam-policy index 62b121449..611f0f79d 100644 --- a/gcloud/alpha/resource-manager/tags/values/get-iam-policy +++ b/gcloud/alpha/resource-manager/tags/values/get-iam-policy @@ -42,5 +42,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags values get-iam-policy + + $ gcloud beta resource-manager tags values get-iam-policy diff --git a/gcloud/alpha/resource-manager/tags/values/help b/gcloud/alpha/resource-manager/tags/values/help index fda63a782..541a66206 100644 --- a/gcloud/alpha/resource-manager/tags/values/help +++ b/gcloud/alpha/resource-manager/tags/values/help @@ -49,5 +49,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags values + + $ gcloud beta resource-manager tags values diff --git a/gcloud/alpha/resource-manager/tags/values/list b/gcloud/alpha/resource-manager/tags/values/list index 341536edf..b4c58eaac 100644 --- a/gcloud/alpha/resource-manager/tags/values/list +++ b/gcloud/alpha/resource-manager/tags/values/list @@ -8,7 +8,7 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] EXAMPLES - To list all the TagValues under ``organizations/123/env", run: + To list all the TagValues under organizations/123/env, run: $ gcloud alpha resource-manager tags values list --parent=123/env @@ -61,5 +61,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags values list + + $ gcloud beta resource-manager tags values list diff --git a/gcloud/alpha/resource-manager/tags/values/remove-iam-policy-binding b/gcloud/alpha/resource-manager/tags/values/remove-iam-policy-binding index ce862a49e..ba316ab29 100644 --- a/gcloud/alpha/resource-manager/tags/values/remove-iam-policy-binding +++ b/gcloud/alpha/resource-manager/tags/values/remove-iam-policy-binding @@ -118,5 +118,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags values remove-iam-policy-binding + + $ gcloud beta resource-manager tags values remove-iam-policy-binding diff --git a/gcloud/alpha/resource-manager/tags/values/set-iam-policy b/gcloud/alpha/resource-manager/tags/values/set-iam-policy index 6561e9b23..00edf43ed 100644 --- a/gcloud/alpha/resource-manager/tags/values/set-iam-policy +++ b/gcloud/alpha/resource-manager/tags/values/set-iam-policy @@ -51,5 +51,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags values set-iam-policy + + $ gcloud beta resource-manager tags values set-iam-policy diff --git a/gcloud/alpha/resource-manager/tags/values/update b/gcloud/alpha/resource-manager/tags/values/update index 582eacd93..e426fbcb6 100644 --- a/gcloud/alpha/resource-manager/tags/values/update +++ b/gcloud/alpha/resource-manager/tags/values/update @@ -52,5 +52,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. These variants are also available: + + $ gcloud resource-manager tags values update + + $ gcloud beta resource-manager tags values update diff --git a/gcloud/alpha/run/jobs/describe b/gcloud/alpha/run/jobs/describe index dca2c25a4..127da4dd2 100644 --- a/gcloud/alpha/run/jobs/describe +++ b/gcloud/alpha/run/jobs/describe @@ -45,5 +45,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run jobs describe diff --git a/gcloud/alpha/run/jobs/executions/describe b/gcloud/alpha/run/jobs/executions/describe index 1f8f414ba..a82b54106 100644 --- a/gcloud/alpha/run/jobs/executions/describe +++ b/gcloud/alpha/run/jobs/executions/describe @@ -46,5 +46,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run jobs executions describe diff --git a/gcloud/alpha/run/jobs/executions/help b/gcloud/alpha/run/jobs/executions/help index 456d38950..208e9b7fb 100644 --- a/gcloud/alpha/run/jobs/executions/help +++ b/gcloud/alpha/run/jobs/executions/help @@ -47,5 +47,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run jobs executions diff --git a/gcloud/alpha/run/jobs/executions/tasks/describe b/gcloud/alpha/run/jobs/executions/tasks/describe index 4c5b740ed..4a7431d07 100644 --- a/gcloud/alpha/run/jobs/executions/tasks/describe +++ b/gcloud/alpha/run/jobs/executions/tasks/describe @@ -47,5 +47,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run jobs executions tasks describe diff --git a/gcloud/alpha/run/jobs/executions/tasks/help b/gcloud/alpha/run/jobs/executions/tasks/help index 2cfaef8fb..60c51ec5f 100644 --- a/gcloud/alpha/run/jobs/executions/tasks/help +++ b/gcloud/alpha/run/jobs/executions/tasks/help @@ -39,5 +39,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run jobs executions tasks diff --git a/gcloud/alpha/run/jobs/get-iam-policy b/gcloud/alpha/run/jobs/get-iam-policy index 8d6b6c2f0..7ebeed3ad 100644 --- a/gcloud/alpha/run/jobs/get-iam-policy +++ b/gcloud/alpha/run/jobs/get-iam-policy @@ -89,5 +89,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run jobs get-iam-policy diff --git a/gcloud/alpha/run/jobs/help b/gcloud/alpha/run/jobs/help index f36a05914..2879a7972 100644 --- a/gcloud/alpha/run/jobs/help +++ b/gcloud/alpha/run/jobs/help @@ -67,5 +67,7 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. + access allowlist. This variant is also available: + + $ gcloud beta run jobs diff --git a/gcloud/auth/login b/gcloud/auth/login index f8bd6ca88..1e802b6cc 100644 --- a/gcloud/auth/login +++ b/gcloud/auth/login @@ -30,9 +30,9 @@ DESCRIPTION For authorization with external accounts (workload identity pools) or service accounts, the --cred-file flag must be specified with the path to the workload identity credential configuration file or service account key - file (JSON). Login with workload identity federation is not yet supported - in other Google Cloud CLIs (e.g. gsutil and bq) and is only applicable to - gcloud commands. For more information on workload identity federation, see: + file (JSON). Login with workload identity federation is also supported in + gsutil and this command is the recommended way of using external accounts. + For more information on workload identity federation, see: https://cloud.google.com/iam/docs/workload-identity-federation. For more information on authorization and credential types, see: diff --git a/gcloud/beta/active-directory/peerings/create b/gcloud/beta/active-directory/peerings/create index ff49cf3a3..5721c61f1 100644 --- a/gcloud/beta/active-directory/peerings/create +++ b/gcloud/beta/active-directory/peerings/create @@ -48,7 +48,9 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS --authorized-network=AUTHORIZED_NETWORK - Name of the managed Managed Microsoft AD domain you want to peer to. + Name of the Network that is authorized to communicate with Managed + Microsoft AD domain. This is usually the full path name of the network + in the peer project. --domain=DOMAIN Name of the managed Managed Microsoft AD domain you want to peer to. diff --git a/gcloud/beta/auth/login b/gcloud/beta/auth/login index ec59030c1..467e83d86 100644 --- a/gcloud/beta/auth/login +++ b/gcloud/beta/auth/login @@ -30,9 +30,9 @@ DESCRIPTION For authorization with external accounts (workload identity pools) or service accounts, the --cred-file flag must be specified with the path to the workload identity credential configuration file or service account key - file (JSON). Login with workload identity federation is not yet supported - in other Google Cloud CLIs (e.g. gsutil and bq) and is only applicable to - gcloud commands. For more information on workload identity federation, see: + file (JSON). Login with workload identity federation is also supported in + gsutil and this command is the recommended way of using external accounts. + For more information on workload identity federation, see: https://cloud.google.com/iam/docs/workload-identity-federation. For more information on authorization and credential types, see: diff --git a/gcloud/beta/compute/backend-buckets/create b/gcloud/beta/compute/backend-buckets/create index 172235dce..8af9ed059 100644 --- a/gcloud/beta/compute/backend-buckets/create +++ b/gcloud/beta/compute/backend-buckets/create @@ -99,7 +99,7 @@ OPTIONAL FLAGS down to the client TTL value if necessary; an Expires header will be replaced with a suitable max-age directive. - The maximum allowed value is 86400s (1 day). + The maximum allowed value is 31,622,400s (1 year). When creating a new backend with CACHE_ALL_STATIC and the field is unset, or when switching to that mode and the field is unset, a default diff --git a/gcloud/beta/compute/backend-buckets/update b/gcloud/beta/compute/backend-buckets/update index 39000c257..41989e194 100644 --- a/gcloud/beta/compute/backend-buckets/update +++ b/gcloud/beta/compute/backend-buckets/update @@ -163,7 +163,7 @@ FLAGS down to the client TTL value if necessary; an Expires header will be replaced with a suitable max-age directive. - The maximum allowed value is 86400s (1 day). + The maximum allowed value is 31,622,400s (1 year). When creating a new backend with CACHE_ALL_STATIC and the field is unset, or when switching to that mode and the field is unset, a diff --git a/gcloud/beta/compute/backend-services/create b/gcloud/beta/compute/backend-services/create index 9beae17b3..b2d26572b 100644 --- a/gcloud/beta/compute/backend-services/create +++ b/gcloud/beta/compute/backend-services/create @@ -157,7 +157,7 @@ FLAGS down to the client TTL value if necessary; an Expires header will be replaced with a suitable max-age directive. - The maximum allowed value is 86400s (1 day). + The maximum allowed value is 31,622,400s (1 year). When creating a new backend with CACHE_ALL_STATIC and the field is unset, or when switching to that mode and the field is unset, a default diff --git a/gcloud/beta/compute/backend-services/update b/gcloud/beta/compute/backend-services/update index 4874d11a0..922984547 100644 --- a/gcloud/beta/compute/backend-services/update +++ b/gcloud/beta/compute/backend-services/update @@ -504,7 +504,7 @@ FLAGS down to the client TTL value if necessary; an Expires header will be replaced with a suitable max-age directive. - The maximum allowed value is 86400s (1 day). + The maximum allowed value is 31,622,400s (1 year). When creating a new backend with CACHE_ALL_STATIC and the field is unset, or when switching to that mode and the field is unset, a diff --git a/gcloud/beta/compute/instances/create b/gcloud/beta/compute/instances/create index 991dd4040..ea861a2e8 100644 --- a/gcloud/beta/compute/instances/create +++ b/gcloud/beta/compute/instances/create @@ -21,7 +21,7 @@ SYNOPSIS [--instance-termination-action=INSTANCE_TERMINATION_ACTION] [--ipv6-network-tier=IPV6_NETWORK_TIER] [--ipv6-public-ptr-domain=IPV6_PUBLIC_PTR_DOMAIN] - [--labels=[KEY=VALUE,...]] + [--key-revocation-action-type=POLICY] [--labels=[KEY=VALUE,...]] [--local-ssd=[device-name=DEVICE-NAME],[interface=INTERFACE]] [--machine-type=MACHINE_TYPE] [--maintenance-policy=MAINTENANCE_POLICY] [--metadata=KEY=VALUE,[KEY=VALUE,...]] @@ -437,6 +437,16 @@ FLAGS PTR record will be used. This option can only be specified for the default network interface, nic0. + --key-revocation-action-type=POLICY + Specifies the behavior of the instance when the KMS key of one of its + attached disks is revoked. The default is none. POLICY must be one of: + + none + No operation is performed. + stop + The instance is stopped when the KMS key of one of its attached + disks is revoked. + --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/beta/compute/resource-policies/create/group-placement b/gcloud/beta/compute/resource-policies/create/group-placement index 945e7e5d5..dba277a0a 100644 --- a/gcloud/beta/compute/resource-policies/create/group-placement +++ b/gcloud/beta/compute/resource-policies/create/group-placement @@ -59,7 +59,10 @@ FLAGS CLOUDSDK_COMPUTE_REGION. --vm-count=VM_COUNT - Number of instances targeted by the group placement policy. + Number of instances targeted by the group placement policy. Google does + not recommend that you use this flag unless you use a compact policy + and you want your policy to work only if it contains this exact number + of VMs. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/compute/routers/add-bgp-peer b/gcloud/beta/compute/routers/add-bgp-peer index f04bf209b..ed5b8f043 100644 --- a/gcloud/beta/compute/routers/add-bgp-peer +++ b/gcloud/beta/compute/routers/add-bgp-peer @@ -9,6 +9,7 @@ SYNOPSIS [--advertisement-mode=MODE] [--async] [--[no-]enable-ipv6] [--[no-]enabled] [--instance=INSTANCE] [--instance-zone=INSTANCE_ZONE] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] + [--md5-authentication-key=MD5_AUTHENTICATION_KEY] [--peer-ip-address=PEER_IP_ADDRESS] [--peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] @@ -102,6 +103,10 @@ OPTIONAL FLAGS the range 2600:2d00:0:2:0:0:0:0/64 or 2600:2d00:0:3:0:0:0:0/64 and must belong to same subnet as the interface address of the peer router. + --md5-authentication-key=MD5_AUTHENTICATION_KEY + The MD5 authentication key for this BGP peer. Maximum length is 80 + characters. Can contain only printable ASCII characters. + --peer-ip-address=PEER_IP_ADDRESS The link-local address of the peer router. Must be a link-local IPv4 address belonging to the range 169.254.0.0/16. diff --git a/gcloud/beta/compute/routers/update-bgp-peer b/gcloud/beta/compute/routers/update-bgp-peer index 467ffb804..8464a76dc 100644 --- a/gcloud/beta/compute/routers/update-bgp-peer +++ b/gcloud/beta/compute/routers/update-bgp-peer @@ -5,9 +5,10 @@ NAME SYNOPSIS gcloud beta compute routers update-bgp-peer NAME --peer-name=PEER_NAME [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] - [--advertisement-mode=MODE] [--async] [--[no-]enable-ipv6] - [--[no-]enabled] [--interface=INTERFACE] [--ip-address=IP_ADDRESS] - [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--peer-asn=PEER_ASN] + [--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] + [--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,...]] @@ -53,6 +54,9 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --clear-md5-authentication-key + If specified, remove MD5 authentication from the BGP peer. + --[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 @@ -80,6 +84,10 @@ OPTIONAL FLAGS the range 2600:2d00:0:2:0:0:0:0/64 or 2600:2d00:0:3:0:0:0:0/64 and must belong to same subnet as the interface address of the peer router. + --md5-authentication-key=MD5_AUTHENTICATION_KEY + The MD5 authentication key for this BGP peer. Maximum length is 80 + characters. Can contain only printable ASCII characters. + --peer-asn=PEER_ASN The BGP autonomous system number (ASN) for this BGP peer. Must be a 16-bit or 32-bit private ASN as defined in diff --git a/gcloud/beta/datastream/streams/create b/gcloud/beta/datastream/streams/create index 82994eaab..cc4d77c6f 100644 --- a/gcloud/beta/datastream/streams/create +++ b/gcloud/beta/datastream/streams/create @@ -21,7 +21,7 @@ DESCRIPTION Create a Datastream stream EXAMPLES - To create a stream with an Oracle source and Google Cloud Storage + To create a stream with an Oracle source and a Google Cloud Storage destination: $ gcloud beta datastream streams create STREAM \ @@ -30,8 +30,8 @@ EXAMPLES --destination-name=destination \ --gcs-destination-config=destination_config.json --backfill-none - To create a connection profile for Mysql with a backfill all strategy that - contains some excluded objects: + To create a stream with a MySQL source and a Cloud Storage destination and + that excludes some objects from being backfilled: $ gcloud beta datastream streams create STREAM \ --location=us-central1 --display-name=my-stream \ diff --git a/gcloud/beta/deploy/releases/create b/gcloud/beta/deploy/releases/create index 7ae138636..28c667dd8 100644 --- a/gcloud/beta/deploy/releases/create +++ b/gcloud/beta/deploy/releases/create @@ -38,11 +38,12 @@ EXAMPLES $ gcloud beta deploy releases create 'my-release-$DATE-$TIME' \ --delivery-pipeline=my-pipeline --region=us-central1 - If the current UTC date and time is set to 2021-12-21 12:02, then the created release - will have its name set as my-release-20211221-1202. + If the current UTC date and time is set to 2021-12-21 12:02, then the + created release will have its name set as my-release-20211221-1202. - When using these parameters, please be sure to wrap the release name in single quotes - or else the template parameters will be overriden by environment variables. + When using these parameters, please be sure to wrap the release name in + single quotes or else the template parameters will be overridden by + environment variables. POSITIONAL ARGUMENTS Release resource - The name of the Release. The arguments in this group diff --git a/gcloud/beta/emulators/datastore/start b/gcloud/beta/emulators/datastore/start index 6465aae59..2053e5108 100644 --- a/gcloud/beta/emulators/datastore/start +++ b/gcloud/beta/emulators/datastore/start @@ -2,9 +2,10 @@ NAME gcloud beta emulators datastore start - start a local datastore emulator SYNOPSIS - gcloud beta emulators datastore start - [--consistency=CONSISTENCY; default=0.9] [--data-dir=DATA_DIR] - [--host-port=HOST_PORT] [--no-store-on-disk] [GCLOUD_WIDE_FLAG ...] + gcloud beta emulators datastore start [--data-dir=DATA_DIR] + [--host-port=HOST_PORT] [--no-store-on-disk] + [--consistency=CONSISTENCY; default=0.9 + | --use-firestore-in-datastore-mode] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command starts a local datastore emulator. @@ -15,12 +16,6 @@ EXAMPLES $ gcloud beta emulators datastore start --data-dir=DATA-DIR FLAGS - --consistency=CONSISTENCY; default=0.9 - Fraction of eventually consistent operations that should succeed - immediately. Setting to 1.0 can be useful for unit tests, but may mask - incorrect assumptions about non-ancestor queries which are eventually - consistent. - --data-dir=DATA_DIR The directory to be used to store/retrieve data/config for an emulator run. The default value is /emulators/datastore. The @@ -44,6 +39,19 @@ FLAGS Whether data should be persisted to disk. Enabled by default, use --no-store-on-disk to disable. + At most one of these can be specified: + + --consistency=CONSISTENCY; default=0.9 + Fraction of eventually consistent operations that should succeed + immediately. Setting to 1.0 can be useful for unit tests, but may + mask incorrect assumptions about non-ancestor queries which are + eventually consistent. + + --use-firestore-in-datastore-mode + Runs the emulator in Cloud Firestore in Datastore Mode. Reads are + always strongly consistent and --consistency flag may not be + specified. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/functions/deploy b/gcloud/beta/functions/deploy index 9d00ecddf..442d241ba 100644 --- a/gcloud/beta/functions/deploy +++ b/gcloud/beta/functions/deploy @@ -179,7 +179,7 @@ FLAGS ◆ dotnet3: .NET Framework 3 ◆ ruby26: Ruby 2.6 ◆ ruby27: Ruby 2.7 - ◆ ruby30: Ruby 3.0 (preview) + ◆ ruby30: Ruby 3.0 ◆ nodejs6: Node.js 6 (deprecated) ◆ nodejs8: Node.js 8 (deprecated) diff --git a/gcloud/beta/resource-manager/help b/gcloud/beta/resource-manager/help index 5618cb5ae..5e2eb1765 100644 --- a/gcloud/beta/resource-manager/help +++ b/gcloud/beta/resource-manager/help @@ -22,6 +22,9 @@ GROUPS org-policies (BETA) Manage Org Policies. + tags + (BETA) Create and manipulate tag keys, values and bindings. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/resource-manager/tags/bindings/create b/gcloud/beta/resource-manager/tags/bindings/create new file mode 100644 index 000000000..cddbd8c08 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/bindings/create @@ -0,0 +1,70 @@ +NAME + gcloud beta resource-manager tags bindings create - creates a TagBinding + resource + +SYNOPSIS + gcloud beta resource-manager tags bindings create --parent=PARENT + --tag-value=TAG_VALUE [--async] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Creates a TagBinding given the TagValue and the parent cloud + resource the TagValue will be attached to. The TagValue can be represented + with its numeric id or its namespaced name of + organizations/{org_id}/{tag_key_short_name}. The parent resource should be + represented with its full resource name. See: + https://cloud.google.com/apis/design/resource_names#full_resource_name. + +EXAMPLES + To create a TagBinding between tagValues/123 and Project with name + //cloudresourcemanager.googleapis.com/projects/1234 run: + + $ gcloud beta resource-manager tags bindings create \ + --tag-value=tagValues/123 \ + --parent=//cloudresourcemanager.googleapis.com/projects/1234 + + To create a TagBinding between TagValue test under TagKey env and Project + with name //cloudresourcemanager.googleapis.com/projects/1234 run: + + $ gcloud beta resource-manager tags bindings create \ + --tag-value=789/env/test \ + --parent=//cloudresourcemanager.googleapis.com/projects/1234 + +REQUIRED FLAGS + --parent=PARENT + Full resource name of the resource to attach to the tagValue. + + --tag-value=TAG_VALUE + Tag value name or namespaced name. The name should be in the form + tagValues/{numeric_id}. The namespaced name should be in the form + {org_id}/{tag_key_short_name}/{short_name} where short_name must be + 1-63 characters, beginning and ending with an alphanumeric character + ([a-z0-9A-Z]) with dashes (-), underscores (), dots (.), and + alphanumerics between. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --location=LOCATION + Region or zone of the resource to bind to the TagValue. This field is + not required if the resource is a global resource like projects, + folders and organizations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags bindings create + + $ gcloud alpha resource-manager tags bindings create + diff --git a/gcloud/beta/resource-manager/tags/bindings/delete b/gcloud/beta/resource-manager/tags/bindings/delete new file mode 100644 index 000000000..5a91b3ea6 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/bindings/delete @@ -0,0 +1,70 @@ +NAME + gcloud beta resource-manager tags bindings delete - deletes a TagBinding + +SYNOPSIS + gcloud beta resource-manager tags bindings delete --parent=PARENT + --tag-value=TAG_VALUE [--async] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes a TagBinding given the TagValue and the parent resource that + the TagValue is attached to. The parent must be given as the full resource + name. See: + https://cloud.google.com/apis/design/resource_names#full_resource_name. The + TagValue can be represented with its numeric id or its namespaced name of + {org_id}/{tag_key_short_name}. + +EXAMPLES + To delete a TagBinding between tagValue/111 and Project with name + //cloudresourcemanager.googleapis.com/projects/1234 run: + + $ gcloud beta resource-manager tags bindings delete \ + --tag-value=tagValue/123 \ + --parent=//cloudresourcemanager.googleapis.com/projects/1234 + + To delete a binding between TagValue test under TagKey env that lives under + organizations/789 and Project with name + //cloudresourcemanager.googleapis.com/projects/1234 run: + + $ gcloud beta resource-manager tags bindings delete \ + --tag-value=789/env/test \ + --parent=//cloudresourcemanager.googleapis.com/projects/1234 + +REQUIRED FLAGS + --parent=PARENT + Full resource name of the resource attached to the tagValue. + + --tag-value=TAG_VALUE + Tag value name or namespaced name. The name should be in the form + tagValues/{numeric_id}. The namespaced name should be in the form + {org_id}/{tag_key_short_name}/{short_name} where short_name must be + 1-63 characters, beginning and ending with an alphanumeric character + ([a-z0-9A-Z]) with dashes (-), underscores (), dots (.), and + alphanumerics between. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --location=LOCATION + Region or zone of the resource to unbind from the TagValue. This field + is not required if the resource is a global resource like projects, + folders and organizations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags bindings delete + + $ gcloud alpha resource-manager tags bindings delete + diff --git a/gcloud/beta/resource-manager/tags/bindings/help b/gcloud/beta/resource-manager/tags/bindings/help new file mode 100644 index 000000000..40a0df3b0 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/bindings/help @@ -0,0 +1,39 @@ +NAME + gcloud beta resource-manager tags bindings - create and manipulate + TagBindings + +SYNOPSIS + gcloud beta resource-manager tags bindings COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The Resource Manager Service gives you centralized and programmatic + control over your organization's Tags. As the tag administrator, you will + be able to create and configure restrictions across the tags in the org. As + the tag user, you will be able to attach TagValues to different resources + as a TagBinding. + +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 TagBinding resource. + + delete + (BETA) Deletes a TagBinding. + + list + (BETA) Lists TagBindings bound to the specified resource. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags bindings + + $ gcloud alpha resource-manager tags bindings + diff --git a/gcloud/beta/resource-manager/tags/bindings/list b/gcloud/beta/resource-manager/tags/bindings/list new file mode 100644 index 000000000..5859a2e60 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/bindings/list @@ -0,0 +1,84 @@ +NAME + gcloud beta resource-manager tags bindings list - lists TagBindings bound + to the specified resource + +SYNOPSIS + gcloud beta resource-manager tags bindings list --parent=PARENT + [--effective] [--location=LOCATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) When specifying a parent resource, the full name of the parent + resource must be used. See: + https://cloud.google.com/apis/design/resource_names#full_resource_name. + +EXAMPLES + To list TagBindings for + '//cloudresourcemanager.googleapis.com/projects/123' run: + + $ gcloud beta resource-manager tags bindings list \ + --parent=//cloudresourcemanager.googleapis.com/projects/123 + +REQUIRED FLAGS + --parent=PARENT + Full resource name attached to the binding + +FLAGS + --effective + Show all effective TagBindings on the resource. TagBindings applied at + a higher level will be inherited to all descendants. + + --location=LOCATION + Region or zone of the resource for listing TagBindings. This field + should not be set if the resource is a global resource like projects, + folders and organizations. + +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 resource-manager tags bindings list + + $ gcloud alpha resource-manager tags bindings list + diff --git a/gcloud/beta/resource-manager/tags/help b/gcloud/beta/resource-manager/tags/help new file mode 100644 index 000000000..ee463400a --- /dev/null +++ b/gcloud/beta/resource-manager/tags/help @@ -0,0 +1,41 @@ +NAME + gcloud beta resource-manager tags - create and manipulate tag keys, values + and bindings + +SYNOPSIS + gcloud beta resource-manager tags GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The Tags Service gives you centralized and programmatic control over + your organization's tags. As the tag administrator, you will be able to + create and configure restrictions across the tags in the org. As the tag + user, you will be able to attach tags values to different resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + bindings + (BETA) Create and manipulate TagBindings. + + holds + (BETA) Create and manipulate TagHolds. + + keys + (BETA) Create and manipulate TagKeys. + + values + (BETA) Create and manipulate TagValues. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags + + $ gcloud alpha resource-manager tags + diff --git a/gcloud/beta/resource-manager/tags/holds/create b/gcloud/beta/resource-manager/tags/holds/create new file mode 100644 index 000000000..1c8573247 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/holds/create @@ -0,0 +1,67 @@ +NAME + gcloud beta resource-manager tags holds create - create a TagHold resource + +SYNOPSIS + gcloud beta resource-manager tags holds create PARENT --holder=HOLDER + [--help-link=HELP_LINK] [--location=LOCATION] [--origin=ORIGIN] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a TagHold under a TagValue, indicating that the TagValue is + being used by a holder (cloud resource) from an (optional) origin. The + TagValue can be represented with its numeric id or its namespaced name of + {org_id}/{tag_key_short_name}/{tag_value_short_name}. + +EXAMPLES + To create a TagHold on tagValues/123, with holder cloud-resource-holder, + origin creator-origin, in region us-central1-a, with help link + www.example.help.link.com, run: + + $ gcloud beta resource-manager tags holds create tagValues/123 \ + --holder=cloud-resource-holder --origin=creator-origin \ + --help-link=www.example.help.link.com --location=us-central1-a + + To create a TagHold under TagValue test under TagKey env in organization id + 789, with holder cloud-resource-holder, run: + + $ gcloud beta resource-manager tags holds create 789/env/test \ + --holder=cloud-resource-holder + +POSITIONAL ARGUMENTS + PARENT + Tag value name or namespaced name. + +REQUIRED FLAGS + --holder=HOLDER + The name of the resource where the TagValue is being used. Must be less + than 200 characters. + +OPTIONAL FLAGS + --help-link=HELP_LINK + A URL where an end user can learn more about removing this hold. + + --location=LOCATION + Region or zone where the TagHold will be stored. If not provided, the + TagHold will be stored in a "global" region. + + --origin=ORIGIN + An optional string representing the origin of this request. This field + should include human-understandable information to distinguish origins + from each other. Must be less than 200 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. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags holds create + + $ gcloud alpha resource-manager tags holds create + diff --git a/gcloud/beta/resource-manager/tags/holds/delete b/gcloud/beta/resource-manager/tags/holds/delete new file mode 100644 index 000000000..be178e02f --- /dev/null +++ b/gcloud/beta/resource-manager/tags/holds/delete @@ -0,0 +1,45 @@ +NAME + gcloud beta resource-manager tags holds delete - delete a TagHold + +SYNOPSIS + gcloud beta resource-manager tags holds delete TAG_HOLD_NAME + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a TagHold given its full name, specified as + tagValues/{tag_value_id}/tagHolds/{tag_hold_id}. + +EXAMPLES + To delete a TagHold under tagValue/111 with id abc-123-def in region + us-central1-a, run: + + $ gcloud beta resource-manager tags holds delete \ + tagValue/111/tagHolds/abc-123-def --location=us-central1-a + +POSITIONAL ARGUMENTS + TAG_HOLD_NAME + TagHold given its full name, specified as + tagValues/{tag_value_id}/tagHolds/{tag_hold_id} + +FLAGS + --location=LOCATION + Region where the TagHold is stored. If not provided, the API will + attempt to find and delete the specified TagHold from the "global" + region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags holds delete + + $ gcloud alpha resource-manager tags holds delete + diff --git a/gcloud/beta/resource-manager/tags/holds/help b/gcloud/beta/resource-manager/tags/holds/help new file mode 100644 index 000000000..e8f4824fc --- /dev/null +++ b/gcloud/beta/resource-manager/tags/holds/help @@ -0,0 +1,37 @@ +NAME + gcloud beta resource-manager tags holds - create and manipulate TagHolds + +SYNOPSIS + gcloud beta resource-manager tags holds COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The Resource Manager Service gives you centralized and programmatic + control over your organization's Tags. As the tag administrator, you will + be able to create and configure restrictions across the tags in the org, + and you will be able to indicate the use of a TagValue as a TagHold. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a TagHold resource. + + delete + (BETA) Delete a TagHold. + + list + (BETA) List TagHolds under the specified TagValue. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags holds + + $ gcloud alpha resource-manager tags holds + diff --git a/gcloud/beta/resource-manager/tags/holds/list b/gcloud/beta/resource-manager/tags/holds/list new file mode 100644 index 000000000..42794585d --- /dev/null +++ b/gcloud/beta/resource-manager/tags/holds/list @@ -0,0 +1,98 @@ +NAME + gcloud beta resource-manager tags holds list - list TagHolds under the + specified TagValue + +SYNOPSIS + gcloud beta resource-manager tags holds list PARENT [--holder=HOLDER] + [--location=LOCATION] [--origin=ORIGIN] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List TagHolds under a TagValue. The TagValue can be represented with + its numeric id or its namespaced name of + {org_id}/{tag_key_short_name}/{tag_value_short_name}. Limited to TagHolds + stored in a single --location: if none is provided, the API will assume the + "global" location. Optional filters are --holder and --origin: if provided, + returned TagHolds' holder and origin fields must match the exact flag + value. + +EXAMPLES + To list TagHolds for tagValues/456 in us-central1-a, run: + + $ gcloud beta resource-manager tags holds list tagValues/456 \ + --location=us-central1-a + + To list TagHolds for tagValues/456, with holder cloud-holder-resource and + origin creator-origin, run: + + $ gcloud beta resource-manager tags holds list tagValues/456 \ + --holder=cloud-holder-resource --origin=creator-origin + +POSITIONAL ARGUMENTS + PARENT + TagValue resource name or namespaced name to list TagHolds for. This + field should be in the form tagValues/ or + //. + +FLAGS + --holder=HOLDER + The holder field of the TagHold to match exactly. If not provided, the + API will return all matching TagHolds disregarding the holder field. + + --location=LOCATION + Region where the matching TagHolds are stored. If not provided, the API + will attempt to retrieve matching TagHolds from the "global" region. + + --origin=ORIGIN + The origin field of the TagHold to match exactly. If not provided, the + API will return all matching TagHolds disregarding the origin field. + +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 resource-manager tags holds list + + $ gcloud alpha resource-manager tags holds list + diff --git a/gcloud/beta/resource-manager/tags/keys/add-iam-policy-binding b/gcloud/beta/resource-manager/tags/keys/add-iam-policy-binding new file mode 100644 index 000000000..298c61dd4 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/keys/add-iam-policy-binding @@ -0,0 +1,117 @@ +NAME + gcloud beta resource-manager tags keys add-iam-policy-binding - adds a + policy binding to the IAM policy of a TagKey + +SYNOPSIS + gcloud beta resource-manager tags keys add-iam-policy-binding RESOURCE_NAME + --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Adds the IAM policy binding for a TagKey resource given the binding + and an identifier for the TagKey. The identifier can be the TagKey's + parent/short name or the TagKey's ID in the form: tagKeys/{numeric_id}. + +EXAMPLES + To add an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' on the Tag Key 'tagKeys/123', run: + + $ gcloud beta resource-manager tags keys add-iam-policy-binding \ + tagKeys/123 --member='user:test-user@gmail.com' \ + --role='roles/editor' + + To add an IAM policy binding for a Tag Key with the name 'env' under + 'organization/456' for the role of 'roles/resourcemanager.tagUser' for the + user 'test-user@gmail.com', run: + + $ gcloud beta resource-manager tags keys add-iam-policy-binding \ + 456/env --member='user:test-user@gmail.com' \ + --role='roles/resourcemanager.tagUser' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags keys add-iam-policy-binding + + $ gcloud alpha resource-manager tags keys add-iam-policy-binding + diff --git a/gcloud/beta/resource-manager/tags/keys/create b/gcloud/beta/resource-manager/tags/keys/create new file mode 100644 index 000000000..8fa67e2fb --- /dev/null +++ b/gcloud/beta/resource-manager/tags/keys/create @@ -0,0 +1,71 @@ +NAME + gcloud beta resource-manager tags keys create - creates a TagKey resource + under the specified tag parent + +SYNOPSIS + gcloud beta resource-manager tags keys create (SHORT_NAME --parent=PARENT) + [--async] [--description=DESCRIPTION] [--purpose=PURPOSE] + [--purpose-data=[network=NETWORK]] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To create a TagKey with the name env under 'organizations/123' with + description 'description', run: + + $ gcloud beta resource-manager tags keys create env \ + --parent=organizations/123 --description=description + +POSITIONAL ARGUMENTS + TagKey. + + This must be specified. + + SHORT_NAME + User specified, friendly name of the TagKey or TagValue. The field + must be 1-63 characters, beginning and ending with an alphanumeric + character ([a-z0-9A-Z]) with dashes (-), underscores ( _ ), dots (.), + and alphanumerics between. + + This positional must be specified if any of the other arguments in + this group are specified. + + --parent=PARENT + Parent of the TagKey in the form of organizations/{org_id}. + + This flag must be specified if any of the other arguments in this + group are specified. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + User-assigned description of the TagKey or TagValue. Must not exceed + 256 characters. + + --purpose=PURPOSE + Purpose specifier of the TagKey that can only be set on creation. + Specifying this field adds additional validation from the policy system + that corresponds to the purpose. PURPOSE must be (currently only one + value is supported): GCE_FIREWALL. + + --purpose-data=[network=NETWORK] + Purpose data of the TagKey that can only be set on creation. This data + is validated by the policy system that corresponds to the purpose. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags keys create + + $ gcloud alpha resource-manager tags keys create + diff --git a/gcloud/beta/resource-manager/tags/keys/delete b/gcloud/beta/resource-manager/tags/keys/delete new file mode 100644 index 000000000..3f485ddc0 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/keys/delete @@ -0,0 +1,50 @@ +NAME + gcloud beta resource-manager tags keys delete - deletes the specified + TagKey resource + +SYNOPSIS + gcloud beta resource-manager tags keys delete RESOURCE_NAME [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes the TagKey resource given the TagKey's parent and short name + or the TagKey's numeric id. + +EXAMPLES + To delete a TagKey with id 123, run: + + $ gcloud beta resource-manager tags keys delete tagKeys/123 + + To delete a TagKey named env under organization 456, run: + + $ gcloud beta resource-manager tags keys delete 456/env + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags keys delete + + $ gcloud alpha resource-manager tags keys delete + diff --git a/gcloud/beta/resource-manager/tags/keys/describe b/gcloud/beta/resource-manager/tags/keys/describe new file mode 100644 index 000000000..ec86f4754 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/keys/describe @@ -0,0 +1,45 @@ +NAME + gcloud beta resource-manager tags keys describe - describes a TagKey + resource + +SYNOPSIS + gcloud beta resource-manager tags keys describe RESOURCE_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Gets metadata for a TagKey resource given the TagKey's resource name + or namespaced name. + +EXAMPLES + To describe a TagKey with id '123', run: + + $ gcloud beta resource-manager tags keys describe tagkeys/123 + + To describe a TagKey with the name 'env' under organizations '456', run: + + $ gcloud beta resource-manager tags keys describe 456/env + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags keys describe + + $ gcloud alpha resource-manager tags keys describe + diff --git a/gcloud/beta/resource-manager/tags/keys/get-iam-policy b/gcloud/beta/resource-manager/tags/keys/get-iam-policy new file mode 100644 index 000000000..5fc2799b0 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/keys/get-iam-policy @@ -0,0 +1,46 @@ +NAME + gcloud beta resource-manager tags keys get-iam-policy - gets the IAM policy + for a TagKey resource + +SYNOPSIS + gcloud beta resource-manager tags keys get-iam-policy RESOURCE_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Returns the IAM policy for a TagKey resource given the TagKey's + display name and parent or the TagKey's numeric id. + +EXAMPLES + To get the IAM policy for a TagKey with id '123', run: + + $ gcloud beta resource-manager tags keys get-iam-policy tagKeys/123 + + To get the IAM policy for a TagKey with the name 'env' under + 'organizations/456', run: + + $ gcloud beta resource-manager tags keys get-iam-policy 456/env + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags keys get-iam-policy + + $ gcloud alpha resource-manager tags keys get-iam-policy + diff --git a/gcloud/beta/resource-manager/tags/keys/help b/gcloud/beta/resource-manager/tags/keys/help new file mode 100644 index 000000000..068bfe082 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/keys/help @@ -0,0 +1,55 @@ +NAME + gcloud beta resource-manager tags keys - create and manipulate TagKeys + +SYNOPSIS + gcloud beta resource-manager tags keys COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The Resource Manager Service gives you centralized and programmatic + control over your organization's Tags. As the tag administrator, you will + be able to create and configure restrictions across the tags in the org. As + the tag user, you will be able to attach TagValues to different resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + (BETA) Adds a policy binding to the IAM policy of a TagKey. + + create + (BETA) Creates a TagKey resource under the specified tag parent. + + delete + (BETA) Deletes the specified TagKey resource. + + describe + (BETA) Describes a TagKey resource. + + get-iam-policy + (BETA) Gets the IAM policy for a TagKey resource. + + list + (BETA) Lists TagKeys under the specified parent resource. + + remove-iam-policy-binding + (BETA) Removes a policy binding from the IAM policy of a TagKey. + + set-iam-policy + (BETA) Sets IAM policy for a TagKey resource. + + update + (BETA) Updates the specified TagKey resource's description. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags keys + + $ gcloud alpha resource-manager tags keys + diff --git a/gcloud/beta/resource-manager/tags/keys/list b/gcloud/beta/resource-manager/tags/keys/list new file mode 100644 index 000000000..afae52002 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/keys/list @@ -0,0 +1,67 @@ +NAME + gcloud beta resource-manager tags keys list - lists TagKeys under the + specified parent resource + +SYNOPSIS + gcloud beta resource-manager tags keys list --parent=PARENT + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all the TagKeys under 'organizations/123', run: + + $ gcloud beta resource-manager tags keys list \ + --parent='organizations/123' + +REQUIRED FLAGS + --parent=PARENT + Parent of the TagKey in the form of organizations/{org_id}. + +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 resource-manager tags keys list + + $ gcloud alpha resource-manager tags keys list + diff --git a/gcloud/beta/resource-manager/tags/keys/remove-iam-policy-binding b/gcloud/beta/resource-manager/tags/keys/remove-iam-policy-binding new file mode 100644 index 000000000..92a304421 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/keys/remove-iam-policy-binding @@ -0,0 +1,123 @@ +NAME + gcloud beta resource-manager tags keys remove-iam-policy-binding - removes + a policy binding from the IAM policy of a TagKey + +SYNOPSIS + gcloud beta resource-manager tags keys remove-iam-policy-binding + RESOURCE_NAME --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Removes an IAM policy binding for a TagKey resource given the + binding and an identifier for the TagKey. The identifier can be the + TagKey's parent/short name or the TagKey's ID in the form: + tagKeys/{numeric_id}. + +EXAMPLES + To remove an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' on the tagKey 'tagKeys/123', run: + + $ gcloud beta resource-manager tags keys remove-iam-policy-binding \ + tagKeys/123 --member='user:test-user@gmail.com' \ + --role='roles/editor' + + To remove an IAM policy binding for a TagKey with the name 'env' under + 'organization/456' for the role of 'roles/resourcemanager.tagUser' for the + user 'test-user@gmail.com', run: + + $ gcloud beta resource-manager tags keys remove-iam-policy-binding \ + 456/env --member='user:test-user@gmail.com' \ + --role='roles/resourcemanager.tagUser' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags keys remove-iam-policy-binding + + $ gcloud alpha resource-manager tags keys remove-iam-policy-binding + diff --git a/gcloud/beta/resource-manager/tags/keys/set-iam-policy b/gcloud/beta/resource-manager/tags/keys/set-iam-policy new file mode 100644 index 000000000..b82b579d8 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/keys/set-iam-policy @@ -0,0 +1,57 @@ +NAME + gcloud beta resource-manager tags keys set-iam-policy - sets IAM policy for + a TagKey resource + +SYNOPSIS + gcloud beta resource-manager tags keys set-iam-policy RESOURCE_NAME + POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Sets the IAM policy for a TagKey resource given the TagKey's display + name and parent or the TagKey's numeric id and a file encoded in JSON or + YAML that contains the IAM policy. + +EXAMPLES + To set the IAM policy for a TagKey with id '123' and IAM policy defined in + a YAML file '/path/to/my_policy.yaml', run: + + $ gcloud beta resource-manager tags keys set-iam-policy \ + tagKeys/123 /path/to/my_policy.yaml + + To set the IAM policy for a tagKey with the short_name 'env' under + 'organization/456' and IAM policy defined in a JSON file + '/path/to/my_policy.json', run: + + $ gcloud beta resource-manager tags keys set-iam-policy 456/env \ + /path/to/my_policy.json + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags keys set-iam-policy + + $ gcloud alpha resource-manager tags keys set-iam-policy + diff --git a/gcloud/beta/resource-manager/tags/keys/update b/gcloud/beta/resource-manager/tags/keys/update new file mode 100644 index 000000000..da9524171 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/keys/update @@ -0,0 +1,56 @@ +NAME + gcloud beta resource-manager tags keys update - updates the specified + TagKey resource's description + +SYNOPSIS + gcloud beta resource-manager tags keys update RESOURCE_NAME [--async] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates the TagKey's description given the TagKey's parent and short + name or the TagKey's numeric id. + +EXAMPLES + To update a TagKey with id 123, run: + + $ gcloud beta resource-manager tags keys update tagKeys/123 \ + --description=foobar + + To update a TagKey named env under organization 456, run: + + $ gcloud beta resource-manager tags keys update 456/env \ + --description=foobar + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + User-assigned description of the TagKey or TagValue. Must not exceed + 256 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. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags keys update + + $ gcloud alpha resource-manager tags keys update + diff --git a/gcloud/beta/resource-manager/tags/values/add-iam-policy-binding b/gcloud/beta/resource-manager/tags/values/add-iam-policy-binding new file mode 100644 index 000000000..238a79b99 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/values/add-iam-policy-binding @@ -0,0 +1,118 @@ +NAME + gcloud beta resource-manager tags values add-iam-policy-binding - adds a + policy binding to the IAM policy of a TagValue + +SYNOPSIS + gcloud beta resource-manager tags values add-iam-policy-binding + RESOURCE_NAME --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Adds the IAM policy binding for a TagValue resource given the + binding and an identifier for the TagValue. The identifier can be the + TagValue's // or + the TagValue's ID in the form: tagValues/{numeric_id}. + +EXAMPLES + To add an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' on the Tag Value 'tagValues/111', run: + + $ gcloud beta resource-manager tags values add-iam-policy-binding \ + tagValues/111 --member='user:test-user@gmail.com' \ + --role='roles/editor' + + To add an IAM policy binding for a Tag Value with the name 'dev' under + 'organization/456/env' for the role of 'roles/resourcemanager.tagUser' for + the user 'test-user@gmail.com', run: + + $ gcloud beta resource-manager tags values add-iam-policy-binding \ + 456/env/dev --member='user:test-user@gmail.com' \ + --role='roles/resourcemanager.tagUser' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags values add-iam-policy-binding + + $ gcloud alpha resource-manager tags values add-iam-policy-binding + diff --git a/gcloud/beta/resource-manager/tags/values/create b/gcloud/beta/resource-manager/tags/values/create new file mode 100644 index 000000000..00f92546c --- /dev/null +++ b/gcloud/beta/resource-manager/tags/values/create @@ -0,0 +1,75 @@ +NAME + gcloud beta resource-manager tags values create - creates a TagValue + resource + +SYNOPSIS + gcloud beta resource-manager tags values create + (SHORT_NAME --parent=PARENT) [--async] [--description=DESCRIPTION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Creates a TagValue resource given the short_name and description + (optional) as well as the parent, the of the TagValue. The parent of the + TagValue is always a TagKey and the TagKey's details can be passed as a + numeric id or the namespaced name. + +EXAMPLES + To create a TagValue with the short name 'test' and the description + 'description' under a TagKey with a short name 'env' under + 'organizations/123', run: + + $ gcloud beta resource-manager tags values create test \ + --parent=123/env --description=description + + To create a TagValue with the short name 'test' under TagKey with id '456', + run: + + $ gcloud beta resource-manager tags values create test \ + --parent=tagKeys/456 --description=description + +POSITIONAL ARGUMENTS + TagValue. + + This must be specified. + + SHORT_NAME + User specified, friendly name of the TagKey or TagValue. The field + must be 1-63 characters, beginning and ending with an alphanumeric + character ([a-z0-9A-Z]) with dashes (-), underscores ( _ ), dots (.), + and alphanumerics between. + + This positional must be specified if any of the other arguments in + this group are specified. + + --parent=PARENT + Parent of the TagValue in either in the form of tagKeys/{id} or + {org_id}/{tagkey_short_name} + + This flag must be specified if any of the other arguments in this + group are specified. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + User-assigned description of the TagKey or TagValue. Must not exceed + 256 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. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags values create + + $ gcloud alpha resource-manager tags values create + diff --git a/gcloud/beta/resource-manager/tags/values/delete b/gcloud/beta/resource-manager/tags/values/delete new file mode 100644 index 000000000..e0a78f28b --- /dev/null +++ b/gcloud/beta/resource-manager/tags/values/delete @@ -0,0 +1,50 @@ +NAME + gcloud beta resource-manager tags values delete - deletes the specified + TagValue resource + +SYNOPSIS + gcloud beta resource-manager tags values delete RESOURCE_NAME [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deletes the TagValue resource given the TagValue's parent and short + name or the TagValue's numeric id. + +EXAMPLES + To delete a TagValue with id 123, run: + + $ gcloud beta resource-manager tags values delete tagValues/123 + + To delete a TagValue named dev with tagKey env under organization 456, run: + + $ gcloud beta resource-manager tags values delete 456/env/dev + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags values delete + + $ gcloud alpha resource-manager tags values delete + diff --git a/gcloud/beta/resource-manager/tags/values/describe b/gcloud/beta/resource-manager/tags/values/describe new file mode 100644 index 000000000..b210d7561 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/values/describe @@ -0,0 +1,46 @@ +NAME + gcloud beta resource-manager tags values describe - describes a TagValue + resource + +SYNOPSIS + gcloud beta resource-manager tags values describe RESOURCE_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Gets metadata for a TagValue resource given the TagValue's resource + name or namespaced name. + +EXAMPLES + To describe a TagValue with id 123, run: + + $ gcloud beta resource-manager tags values describe tagValues/123 + + To describe a TagValue with name dev with the tagKey env under + organizations 456, run: + + $ gcloud beta resource-manager tags values describe 456/env/dev + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags values describe + + $ gcloud alpha resource-manager tags values describe + diff --git a/gcloud/beta/resource-manager/tags/values/get-iam-policy b/gcloud/beta/resource-manager/tags/values/get-iam-policy new file mode 100644 index 000000000..9cd8daf6a --- /dev/null +++ b/gcloud/beta/resource-manager/tags/values/get-iam-policy @@ -0,0 +1,47 @@ +NAME + gcloud beta resource-manager tags values get-iam-policy - gets the IAM + policy for a TagValue resource + +SYNOPSIS + gcloud beta resource-manager tags values get-iam-policy RESOURCE_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Returns the IAM policy for a TagValue resource given the TagValue's + short name and parent or the TagValue's numeric id. + +EXAMPLES + To get the IAM policy for a TagValue with id '123', run: + + $ gcloud beta resource-manager tags values get-iam-policy \ + tagValues/123 + + To get the IAM policy for a TagValue with the name 'dev' under + 'organizations/456' and tagKey parent 'env', run: + + $ gcloud beta resource-manager tags values get-iam-policy 456/env/dev + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags values get-iam-policy + + $ gcloud alpha resource-manager tags values get-iam-policy + diff --git a/gcloud/beta/resource-manager/tags/values/help b/gcloud/beta/resource-manager/tags/values/help new file mode 100644 index 000000000..fc6a4a318 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/values/help @@ -0,0 +1,55 @@ +NAME + gcloud beta resource-manager tags values - create and manipulate TagValues + +SYNOPSIS + gcloud beta resource-manager tags values COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The Resource Manager Service gives you centralized and programmatic + control over your organization's Tags. As the tag administrator, you will + be able to create and configure restrictions across the tags in the org. As + the tag user, you will be able to attach TagValues to different resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + (BETA) Adds a policy binding to the IAM policy of a TagValue. + + create + (BETA) Creates a TagValue resource. + + delete + (BETA) Deletes the specified TagValue resource. + + describe + (BETA) Describes a TagValue resource. + + get-iam-policy + (BETA) Gets the IAM policy for a TagValue resource. + + list + (BETA) Lists TagValues under the specified parent resource. + + remove-iam-policy-binding + (BETA) Removes a policy binding from the IAM policy of a TagValue. + + set-iam-policy + (BETA) Sets IAM policy for a TagValue resource. + + update + (BETA) Updates the specified TagValue resource's description. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags values + + $ gcloud alpha resource-manager tags values + diff --git a/gcloud/beta/resource-manager/tags/values/list b/gcloud/beta/resource-manager/tags/values/list new file mode 100644 index 000000000..254abe86f --- /dev/null +++ b/gcloud/beta/resource-manager/tags/values/list @@ -0,0 +1,67 @@ +NAME + gcloud beta resource-manager tags values list - lists TagValues under the + specified parent resource + +SYNOPSIS + gcloud beta resource-manager tags values list --parent=PARENT + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all the TagValues under organizations/123/env, run: + + $ gcloud beta resource-manager tags values list --parent=123/env + +REQUIRED FLAGS + --parent=PARENT + Parent of the TagValue in either in the form of tagKeys/{id} or + {org_id}/{tagkey_short_name} + +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 resource-manager tags values list + + $ gcloud alpha resource-manager tags values list + diff --git a/gcloud/beta/resource-manager/tags/values/remove-iam-policy-binding b/gcloud/beta/resource-manager/tags/values/remove-iam-policy-binding new file mode 100644 index 000000000..3aa3e53f7 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/values/remove-iam-policy-binding @@ -0,0 +1,124 @@ +NAME + gcloud beta resource-manager tags values remove-iam-policy-binding - + removes a policy binding from the IAM policy of a TagValue + +SYNOPSIS + gcloud beta resource-manager tags values remove-iam-policy-binding + RESOURCE_NAME --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Removes an IAM policy binding for a TagValue resource given the + binding and an identifier for the TagValue. The identifier can be the + TagValue's // or + the TagValue's ID in the form: tagValues/{numeric_id}. + +EXAMPLES + To remove an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' on the tagValue 'tagValues/111', run: + + $ gcloud beta resource-manager tags values \ + remove-iam-policy-binding tagValues/111 \ + --member='user:test-user@gmail.com' --role='roles/editor' + + To remove an IAM policy binding for a TagValue with the name 'dev' under + 'organization/456/env' for the role of 'roles/resourcemanager.tagUser' for + the user 'test-user@gmail.com', run: + + $ gcloud beta resource-manager tags values \ + remove-iam-policy-binding 456/env/dev \ + --member='user:test-user@gmail.com' \ + --role='roles/resourcemanager.tagUser' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags values remove-iam-policy-binding + + $ gcloud alpha resource-manager tags values remove-iam-policy-binding + diff --git a/gcloud/beta/resource-manager/tags/values/set-iam-policy b/gcloud/beta/resource-manager/tags/values/set-iam-policy new file mode 100644 index 000000000..83fbe6a44 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/values/set-iam-policy @@ -0,0 +1,57 @@ +NAME + gcloud beta resource-manager tags values set-iam-policy - sets IAM policy + for a TagValue resource + +SYNOPSIS + gcloud beta resource-manager tags values set-iam-policy RESOURCE_NAME + POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Sets the IAM policy for a TagValue resource given the TagValue's + short name name and parent or the TagValue's numeric id and a file encoded + in JSON or YAML that contains the IAM policy. + +EXAMPLES + To set the IAM policy for a TagValue with id '111' and IAM policy defined + in a YAML file '/path/to/my_policy.yaml', run: + + $ gcloud beta resource-manager tags values set-iam-policy \ + tagValues/111 /path/to/my_policy.yaml + + To set the IAM policy for a tagValue with the short_name 'dev' under + 'organization/456' and tag key short name 'env' and IAM policy defined in a + JSON file '/path/to/my_policy.json', run: + + $ gcloud beta resource-manager tags values set-iam-policy \ + 456/env/dev /path/to/my_policy.json + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags values set-iam-policy + + $ gcloud alpha resource-manager tags values set-iam-policy + diff --git a/gcloud/beta/resource-manager/tags/values/update b/gcloud/beta/resource-manager/tags/values/update new file mode 100644 index 000000000..70c280948 --- /dev/null +++ b/gcloud/beta/resource-manager/tags/values/update @@ -0,0 +1,58 @@ +NAME + gcloud beta resource-manager tags values update - updates the specified + TagValue resource's description + +SYNOPSIS + gcloud beta resource-manager tags values update RESOURCE_NAME [--async] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Updates the TagValue's description given the TagValue's + // or the TagValue's + numeric id tagValues/ + +EXAMPLES + To update a TagValue with id 123, run: + + $ gcloud beta resource-manager tags values update tagValues/123 \ + --description="foobar" + + To update a TagValue named dev with the tagKey env under organization 456, + run: + + $ gcloud beta resource-manager tags values update 465/env/dev \ + --description="foobar" + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + User-assigned description of the TagKey or TagValue. Must not exceed + 256 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. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud resource-manager tags values update + + $ gcloud alpha resource-manager tags values update + diff --git a/gcloud/beta/run/help b/gcloud/beta/run/help index a5f94e96b..ab6b1b2a9 100644 --- a/gcloud/beta/run/help +++ b/gcloud/beta/run/help @@ -26,6 +26,9 @@ GROUPS domain-mappings (BETA) View and manage your Cloud Run domain mappings. + jobs + (BETA) View and manage your Cloud Run jobs. + regions (BETA) View available Cloud Run (fully managed) regions. diff --git a/gcloud/beta/run/jobs/describe b/gcloud/beta/run/jobs/describe new file mode 100644 index 000000000..66a6ce78b --- /dev/null +++ b/gcloud/beta/run/jobs/describe @@ -0,0 +1,49 @@ +NAME + gcloud beta run jobs describe - obtain details about jobs + +SYNOPSIS + gcloud beta run jobs describe JOB [--region=REGION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Obtain details about jobs. + +EXAMPLES + To describe a job: + + $ gcloud beta run jobs describe my-job + +POSITIONAL ARGUMENTS + Job resource - Job to describe. This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. To set the project attribute: + ◆ provide the argument JOB 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. + + JOB + ID of the Job or fully qualified identifier for the Job. To set the + jobs attribute: + ▸ provide the argument JOB on the command line. + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run jobs describe + diff --git a/gcloud/beta/run/jobs/executions/describe b/gcloud/beta/run/jobs/executions/describe new file mode 100644 index 000000000..97370ea5f --- /dev/null +++ b/gcloud/beta/run/jobs/executions/describe @@ -0,0 +1,50 @@ +NAME + gcloud beta run jobs executions describe - obtain details about executions + +SYNOPSIS + gcloud beta run jobs executions describe EXECUTION [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Obtain details about executions. + +EXAMPLES + To describe an execution: + + $ gcloud beta run jobs executions describe my-execution + +POSITIONAL ARGUMENTS + Execution resource - Execution to describe. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: + ◆ provide the argument EXECUTION 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. + + EXECUTION + ID of the Execution or fully qualified identifier for the Execution. + To set the executions attribute: + ▸ provide the argument EXECUTION on the command line. + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run jobs executions describe + diff --git a/gcloud/beta/run/jobs/executions/help b/gcloud/beta/run/jobs/executions/help new file mode 100644 index 000000000..cdecd9601 --- /dev/null +++ b/gcloud/beta/run/jobs/executions/help @@ -0,0 +1,45 @@ +NAME + gcloud beta run jobs executions - view and manage your Cloud Run jobs + executions + +SYNOPSIS + gcloud beta run jobs executions GROUP | COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This set of commands can be used to view and manage your Cloud Run + jobs executions. + +EXAMPLES + To list your executions for a job, run: + + $ gcloud beta run jobs executions list --job=my-job + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + tasks + (BETA) View and manage your Cloud Run jobs tasks. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Obtain details about executions. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run jobs executions + diff --git a/gcloud/beta/run/jobs/executions/tasks/describe b/gcloud/beta/run/jobs/executions/tasks/describe new file mode 100644 index 000000000..f6329243e --- /dev/null +++ b/gcloud/beta/run/jobs/executions/tasks/describe @@ -0,0 +1,50 @@ +NAME + gcloud beta run jobs executions tasks describe - obtain details about tasks + +SYNOPSIS + gcloud beta run jobs executions tasks describe TASK [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Obtain details about tasks. + +EXAMPLES + To describe a task: + + $ gcloud beta run jobs executions tasks describe my-task + +POSITIONAL ARGUMENTS + Task resource - Task to describe. This represents a Cloud resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. To set the project attribute: + ◆ provide the argument TASK 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. + + TASK + ID of the Task or fully qualified identifier for the Task. To set the + tasks attribute: + ▸ provide the argument TASK on the command line. + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run jobs executions tasks describe + diff --git a/gcloud/beta/run/jobs/executions/tasks/help b/gcloud/beta/run/jobs/executions/tasks/help new file mode 100644 index 000000000..3b197e7eb --- /dev/null +++ b/gcloud/beta/run/jobs/executions/tasks/help @@ -0,0 +1,39 @@ +NAME + gcloud beta run jobs executions tasks - view and manage your Cloud Run jobs + tasks + +SYNOPSIS + gcloud beta run jobs executions tasks COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This set of commands can be used to view and manage your Cloud Run + jobs tasks. + +EXAMPLES + To list your existing tasks for an execution, run: + + $ gcloud beta run jobs executions tasks list --execution my_execution + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Obtain details about tasks. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run jobs executions tasks + diff --git a/gcloud/beta/run/jobs/get-iam-policy b/gcloud/beta/run/jobs/get-iam-policy new file mode 100644 index 000000000..a9621d3fb --- /dev/null +++ b/gcloud/beta/run/jobs/get-iam-policy @@ -0,0 +1,93 @@ +NAME + gcloud beta run jobs get-iam-policy - get the IAM policy for a Cloud Run + job + +SYNOPSIS + gcloud beta run jobs get-iam-policy JOB [--region=REGION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command gets the IAM policy for a job. If formatted as JSON, + the output can be edited and used as a policy file for set-iam-policy. The + output includes an "etag" field identifying the version emitted and + allowing detection of concurrent policy updates; see $ gcloud alpha run + registries set-iam-policy for additional details. + +EXAMPLES + To print the IAM policy for a given job, run: + + $ gcloud beta run jobs get-iam-policy --region=us-central1 my-job + +POSITIONAL ARGUMENTS + Job resource - The job for which to display the IAM policy. 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 job 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 job on the command line with a fully specified + name; + ◆ provide the argument --region on the command line; + ◆ set the property run/region; + ◆ specify from a list of available regions in a prompt. + + This must be specified. + + JOB + ID of the job or fully qualified identifier for the job. To set the + job attribute: + ▸ provide the argument job on the command line. + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 run/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/run/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run jobs get-iam-policy + diff --git a/gcloud/beta/run/jobs/help b/gcloud/beta/run/jobs/help new file mode 100644 index 000000000..cbbf54b2e --- /dev/null +++ b/gcloud/beta/run/jobs/help @@ -0,0 +1,47 @@ +NAME + gcloud beta run jobs - view and manage your Cloud Run jobs + +SYNOPSIS + gcloud beta run jobs GROUP | COMMAND [--region=REGION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This set of commands can be used to view and manage your Cloud Run + jobs. + +EXAMPLES + To list your existing jobs, run: + + $ gcloud beta run jobs list + +FLAGS + --region=REGION + Region in which the resource can be found. Alternatively, set the + property [run/region]. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + executions + (BETA) View and manage your Cloud Run jobs executions. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Obtain details about jobs. + + get-iam-policy + (BETA) Get the IAM policy for a Cloud Run job. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha run jobs + diff --git a/gcloud/compute/backend-buckets/create b/gcloud/compute/backend-buckets/create index 75726ab83..e040fbd3d 100644 --- a/gcloud/compute/backend-buckets/create +++ b/gcloud/compute/backend-buckets/create @@ -98,7 +98,7 @@ OPTIONAL FLAGS down to the client TTL value if necessary; an Expires header will be replaced with a suitable max-age directive. - The maximum allowed value is 86400s (1 day). + The maximum allowed value is 31,622,400s (1 year). When creating a new backend with CACHE_ALL_STATIC and the field is unset, or when switching to that mode and the field is unset, a default diff --git a/gcloud/compute/backend-buckets/update b/gcloud/compute/backend-buckets/update index 3c6840144..bb3d45484 100644 --- a/gcloud/compute/backend-buckets/update +++ b/gcloud/compute/backend-buckets/update @@ -151,7 +151,7 @@ FLAGS down to the client TTL value if necessary; an Expires header will be replaced with a suitable max-age directive. - The maximum allowed value is 86400s (1 day). + The maximum allowed value is 31,622,400s (1 year). When creating a new backend with CACHE_ALL_STATIC and the field is unset, or when switching to that mode and the field is unset, a diff --git a/gcloud/compute/backend-services/create b/gcloud/compute/backend-services/create index d47a77c66..66f13220a 100644 --- a/gcloud/compute/backend-services/create +++ b/gcloud/compute/backend-services/create @@ -151,7 +151,7 @@ FLAGS down to the client TTL value if necessary; an Expires header will be replaced with a suitable max-age directive. - The maximum allowed value is 86400s (1 day). + The maximum allowed value is 31,622,400s (1 year). When creating a new backend with CACHE_ALL_STATIC and the field is unset, or when switching to that mode and the field is unset, a default diff --git a/gcloud/compute/backend-services/update b/gcloud/compute/backend-services/update index 05ac49f5f..d2a0e59e7 100644 --- a/gcloud/compute/backend-services/update +++ b/gcloud/compute/backend-services/update @@ -470,7 +470,7 @@ FLAGS down to the client TTL value if necessary; an Expires header will be replaced with a suitable max-age directive. - The maximum allowed value is 86400s (1 day). + The maximum allowed value is 31,622,400s (1 year). When creating a new backend with CACHE_ALL_STATIC and the field is unset, or when switching to that mode and the field is unset, a diff --git a/gcloud/compute/resource-policies/create/group-placement b/gcloud/compute/resource-policies/create/group-placement index 2e0244768..2fe859252 100644 --- a/gcloud/compute/resource-policies/create/group-placement +++ b/gcloud/compute/resource-policies/create/group-placement @@ -59,7 +59,10 @@ FLAGS CLOUDSDK_COMPUTE_REGION. --vm-count=VM_COUNT - Number of instances targeted by the group placement policy. + Number of instances targeted by the group placement policy. Google does + not recommend that you use this flag unless you use a compact policy + and you want your policy to work only if it contains this exact number + of VMs. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/container/fleet/mesh/help b/gcloud/container/fleet/mesh/help index 7b3588cb5..52d35286d 100644 --- a/gcloud/container/fleet/mesh/help +++ b/gcloud/container/fleet/mesh/help @@ -24,6 +24,9 @@ COMMANDS enable Enable Service Mesh Feature. + update + Update the configuration of the Service Mesh Feature. + NOTES These variants are also available: diff --git a/gcloud/container/fleet/mesh/update b/gcloud/container/fleet/mesh/update new file mode 100644 index 000000000..ee6b1bec8 --- /dev/null +++ b/gcloud/container/fleet/mesh/update @@ -0,0 +1,42 @@ +NAME + gcloud container fleet mesh update - update the configuration of the + Service Mesh Feature + +SYNOPSIS + gcloud container fleet mesh update --control-plane=CONTROL_PLANE + [--memberships=MEMBERSHIPS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update the Service Mesh Feature Spec of a Membership. + +EXAMPLES + To update the control plane management of comma separated Memberships like + membership1,membership2, run: + + $ gcloud container fleet mesh update \ + --memberships=membership1,membership2 \ + --control-plane=CONTROL_PLANE + +REQUIRED FLAGS + --control-plane=CONTROL_PLANE + Control plane management to update to. CONTROL_PLANE must be one of: + automatic, manual. + +OPTIONAL FLAGS + --memberships=MEMBERSHIPS + Membership names to update, separated by commas if multiple are + supplied. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 container fleet mesh update + diff --git a/gcloud/container/hub/mesh/help b/gcloud/container/hub/mesh/help index b094cf8f8..62858194e 100644 --- a/gcloud/container/hub/mesh/help +++ b/gcloud/container/hub/mesh/help @@ -24,6 +24,9 @@ COMMANDS enable Enable Service Mesh Feature. + update + Update the configuration of the Service Mesh Feature. + NOTES These variants are also available: diff --git a/gcloud/container/hub/mesh/update b/gcloud/container/hub/mesh/update new file mode 100644 index 000000000..2480bcc9e --- /dev/null +++ b/gcloud/container/hub/mesh/update @@ -0,0 +1,42 @@ +NAME + gcloud container hub mesh update - update the configuration of the Service + Mesh Feature + +SYNOPSIS + gcloud container hub mesh update --control-plane=CONTROL_PLANE + [--memberships=MEMBERSHIPS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update the Service Mesh Feature Spec of a Membership. + +EXAMPLES + To update the control plane management of comma separated Memberships like + membership1,membership2, run: + + $ gcloud container hub mesh update \ + --memberships=membership1,membership2 \ + --control-plane=CONTROL_PLANE + +REQUIRED FLAGS + --control-plane=CONTROL_PLANE + Control plane management to update to. CONTROL_PLANE must be one of: + automatic, manual. + +OPTIONAL FLAGS + --memberships=MEMBERSHIPS + Membership names to update, separated by commas if multiple are + supplied. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 container hub mesh update + diff --git a/gcloud/datastream/streams/create b/gcloud/datastream/streams/create index 0600cbd9a..33c6757dd 100644 --- a/gcloud/datastream/streams/create +++ b/gcloud/datastream/streams/create @@ -18,7 +18,7 @@ DESCRIPTION Create a Datastream stream EXAMPLES - To create a stream with an Oracle source and Google Cloud Storage + To create a stream with an Oracle source and a Google Cloud Storage destination: $ gcloud datastream streams create STREAM --location=us-central1 \ @@ -27,8 +27,8 @@ EXAMPLES --destination=destination \ --gcs-destination-config=destination_config.json --backfill-none - To create a connection profile for Mysql with a backfill all strategy that - contains some excluded objects: + To create a stream with a MySQL source and a Cloud Storage destination and + that excludes some objects from being backfilled: $ gcloud datastream streams create STREAM --location=us-central1 \ --display-name=my-stream --source=source \ diff --git a/gcloud/deploy/releases/create b/gcloud/deploy/releases/create index 66351008a..0f6d42274 100644 --- a/gcloud/deploy/releases/create +++ b/gcloud/deploy/releases/create @@ -38,11 +38,12 @@ EXAMPLES $ gcloud deploy releases create 'my-release-$DATE-$TIME' \ --delivery-pipeline=my-pipeline --region=us-central1 - If the current UTC date and time is set to 2021-12-21 12:02, then the created release - will have its name set as my-release-20211221-1202. + If the current UTC date and time is set to 2021-12-21 12:02, then the + created release will have its name set as my-release-20211221-1202. - When using these parameters, please be sure to wrap the release name in single quotes - or else the template parameters will be overriden by environment variables. + When using these parameters, please be sure to wrap the release name in + single quotes or else the template parameters will be overridden by + environment variables. POSITIONAL ARGUMENTS Release resource - The name of the Release. The arguments in this group diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index 8631d63b7..218c5e097 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -146,7 +146,7 @@ FLAGS ◆ dotnet3: .NET Framework 3 ◆ ruby26: Ruby 2.6 ◆ ruby27: Ruby 2.7 - ◆ ruby30: Ruby 3.0 (preview) + ◆ ruby30: Ruby 3.0 ◆ nodejs6: Node.js 6 (deprecated) ◆ nodejs8: Node.js 8 (deprecated) diff --git a/gcloud/resource-manager/help b/gcloud/resource-manager/help index 6f3eb419f..0a71c8d12 100644 --- a/gcloud/resource-manager/help +++ b/gcloud/resource-manager/help @@ -22,6 +22,9 @@ GROUPS org-policies Manage Org Policies. + tags + Create and manipulate tag keys, values and bindings. + NOTES These variants are also available: diff --git a/gcloud/resource-manager/tags/bindings/create b/gcloud/resource-manager/tags/bindings/create new file mode 100644 index 000000000..fd95014e2 --- /dev/null +++ b/gcloud/resource-manager/tags/bindings/create @@ -0,0 +1,69 @@ +NAME + gcloud resource-manager tags bindings create - creates a TagBinding + resource + +SYNOPSIS + gcloud resource-manager tags bindings create --parent=PARENT + --tag-value=TAG_VALUE [--async] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Creates a TagBinding given the TagValue and the parent cloud resource the + TagValue will be attached to. The TagValue can be represented with its + numeric id or its namespaced name of + organizations/{org_id}/{tag_key_short_name}. The parent resource should be + represented with its full resource name. See: + https://cloud.google.com/apis/design/resource_names#full_resource_name. + +EXAMPLES + To create a TagBinding between tagValues/123 and Project with name + //cloudresourcemanager.googleapis.com/projects/1234 run: + + $ gcloud resource-manager tags bindings create \ + --tag-value=tagValues/123 \ + --parent=//cloudresourcemanager.googleapis.com/projects/1234 + + To create a TagBinding between TagValue test under TagKey env and Project + with name //cloudresourcemanager.googleapis.com/projects/1234 run: + + $ gcloud resource-manager tags bindings create \ + --tag-value=789/env/test \ + --parent=//cloudresourcemanager.googleapis.com/projects/1234 + +REQUIRED FLAGS + --parent=PARENT + Full resource name of the resource to attach to the tagValue. + + --tag-value=TAG_VALUE + Tag value name or namespaced name. The name should be in the form + tagValues/{numeric_id}. The namespaced name should be in the form + {org_id}/{tag_key_short_name}/{short_name} where short_name must be + 1-63 characters, beginning and ending with an alphanumeric character + ([a-z0-9A-Z]) with dashes (-), underscores (), dots (.), and + alphanumerics between. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --location=LOCATION + Region or zone of the resource to bind to the TagValue. This field is + not required if the resource is a global resource like projects, + folders and organizations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags bindings create + + $ gcloud beta resource-manager tags bindings create + diff --git a/gcloud/resource-manager/tags/bindings/delete b/gcloud/resource-manager/tags/bindings/delete new file mode 100644 index 000000000..d9f357354 --- /dev/null +++ b/gcloud/resource-manager/tags/bindings/delete @@ -0,0 +1,69 @@ +NAME + gcloud resource-manager tags bindings delete - deletes a TagBinding + +SYNOPSIS + gcloud resource-manager tags bindings delete --parent=PARENT + --tag-value=TAG_VALUE [--async] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Deletes a TagBinding given the TagValue and the parent resource that the + TagValue is attached to. The parent must be given as the full resource + name. See: + https://cloud.google.com/apis/design/resource_names#full_resource_name. The + TagValue can be represented with its numeric id or its namespaced name of + {org_id}/{tag_key_short_name}. + +EXAMPLES + To delete a TagBinding between tagValue/111 and Project with name + //cloudresourcemanager.googleapis.com/projects/1234 run: + + $ gcloud resource-manager tags bindings delete \ + --tag-value=tagValue/123 \ + --parent=//cloudresourcemanager.googleapis.com/projects/1234 + + To delete a binding between TagValue test under TagKey env that lives under + organizations/789 and Project with name + //cloudresourcemanager.googleapis.com/projects/1234 run: + + $ gcloud resource-manager tags bindings delete \ + --tag-value=789/env/test \ + --parent=//cloudresourcemanager.googleapis.com/projects/1234 + +REQUIRED FLAGS + --parent=PARENT + Full resource name of the resource attached to the tagValue. + + --tag-value=TAG_VALUE + Tag value name or namespaced name. The name should be in the form + tagValues/{numeric_id}. The namespaced name should be in the form + {org_id}/{tag_key_short_name}/{short_name} where short_name must be + 1-63 characters, beginning and ending with an alphanumeric character + ([a-z0-9A-Z]) with dashes (-), underscores (), dots (.), and + alphanumerics between. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --location=LOCATION + Region or zone of the resource to unbind from the TagValue. This field + is not required if the resource is a global resource like projects, + folders and organizations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags bindings delete + + $ gcloud beta resource-manager tags bindings delete + diff --git a/gcloud/resource-manager/tags/bindings/help b/gcloud/resource-manager/tags/bindings/help new file mode 100644 index 000000000..7f04aeb87 --- /dev/null +++ b/gcloud/resource-manager/tags/bindings/help @@ -0,0 +1,37 @@ +NAME + gcloud resource-manager tags bindings - create and manipulate TagBindings + +SYNOPSIS + gcloud resource-manager tags bindings COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The Resource Manager Service gives you centralized and programmatic control + over your organization's Tags. As the tag administrator, you will be able + to create and configure restrictions across the tags in the org. As the tag + user, you will be able to attach TagValues to different resources as a + TagBinding. + +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 TagBinding resource. + + delete + Deletes a TagBinding. + + list + Lists TagBindings bound to the specified resource. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags bindings + + $ gcloud beta resource-manager tags bindings + diff --git a/gcloud/resource-manager/tags/bindings/list b/gcloud/resource-manager/tags/bindings/list new file mode 100644 index 000000000..2f8794c09 --- /dev/null +++ b/gcloud/resource-manager/tags/bindings/list @@ -0,0 +1,83 @@ +NAME + gcloud resource-manager tags bindings list - lists TagBindings bound to the + specified resource + +SYNOPSIS + gcloud resource-manager tags bindings list --parent=PARENT [--effective] + [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + When specifying a parent resource, the full name of the parent resource + must be used. See: + https://cloud.google.com/apis/design/resource_names#full_resource_name. + +EXAMPLES + To list TagBindings for + '//cloudresourcemanager.googleapis.com/projects/123' run: + + $ gcloud resource-manager tags bindings list \ + --parent=//cloudresourcemanager.googleapis.com/projects/123 + +REQUIRED FLAGS + --parent=PARENT + Full resource name attached to the binding + +FLAGS + --effective + Show all effective TagBindings on the resource. TagBindings applied at + a higher level will be inherited to all descendants. + + --location=LOCATION + Region or zone of the resource for listing TagBindings. This field + should not be set if the resource is a global resource like projects, + folders and organizations. + +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 resource-manager tags bindings list + + $ gcloud beta resource-manager tags bindings list + diff --git a/gcloud/resource-manager/tags/help b/gcloud/resource-manager/tags/help new file mode 100644 index 000000000..49dfcd42e --- /dev/null +++ b/gcloud/resource-manager/tags/help @@ -0,0 +1,40 @@ +NAME + gcloud resource-manager tags - create and manipulate tag keys, values and + bindings + +SYNOPSIS + gcloud resource-manager tags GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The Tags Service gives you centralized and programmatic control over your + organization's tags. As the tag administrator, you will be able to create + and configure restrictions across the tags in the org. As the tag user, you + will be able to attach tags values to different resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + bindings + Create and manipulate TagBindings. + + holds + Create and manipulate TagHolds. + + keys + Create and manipulate TagKeys. + + values + Create and manipulate TagValues. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags + + $ gcloud beta resource-manager tags + diff --git a/gcloud/resource-manager/tags/holds/create b/gcloud/resource-manager/tags/holds/create new file mode 100644 index 000000000..bb4e2be42 --- /dev/null +++ b/gcloud/resource-manager/tags/holds/create @@ -0,0 +1,66 @@ +NAME + gcloud resource-manager tags holds create - create a TagHold resource + +SYNOPSIS + gcloud resource-manager tags holds create PARENT --holder=HOLDER + [--help-link=HELP_LINK] [--location=LOCATION] [--origin=ORIGIN] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a TagHold under a TagValue, indicating that the TagValue is being + used by a holder (cloud resource) from an (optional) origin. The TagValue + can be represented with its numeric id or its namespaced name of + {org_id}/{tag_key_short_name}/{tag_value_short_name}. + +EXAMPLES + To create a TagHold on tagValues/123, with holder cloud-resource-holder, + origin creator-origin, in region us-central1-a, with help link + www.example.help.link.com, run: + + $ gcloud resource-manager tags holds create tagValues/123 \ + --holder=cloud-resource-holder --origin=creator-origin \ + --help-link=www.example.help.link.com --location=us-central1-a + + To create a TagHold under TagValue test under TagKey env in organization id + 789, with holder cloud-resource-holder, run: + + $ gcloud resource-manager tags holds create 789/env/test \ + --holder=cloud-resource-holder + +POSITIONAL ARGUMENTS + PARENT + Tag value name or namespaced name. + +REQUIRED FLAGS + --holder=HOLDER + The name of the resource where the TagValue is being used. Must be less + than 200 characters. + +OPTIONAL FLAGS + --help-link=HELP_LINK + A URL where an end user can learn more about removing this hold. + + --location=LOCATION + Region or zone where the TagHold will be stored. If not provided, the + TagHold will be stored in a "global" region. + + --origin=ORIGIN + An optional string representing the origin of this request. This field + should include human-understandable information to distinguish origins + from each other. Must be less than 200 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. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags holds create + + $ gcloud beta resource-manager tags holds create + diff --git a/gcloud/resource-manager/tags/holds/delete b/gcloud/resource-manager/tags/holds/delete new file mode 100644 index 000000000..a7e088458 --- /dev/null +++ b/gcloud/resource-manager/tags/holds/delete @@ -0,0 +1,44 @@ +NAME + gcloud resource-manager tags holds delete - delete a TagHold + +SYNOPSIS + gcloud resource-manager tags holds delete TAG_HOLD_NAME + [--location=LOCATION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a TagHold given its full name, specified as + tagValues/{tag_value_id}/tagHolds/{tag_hold_id}. + +EXAMPLES + To delete a TagHold under tagValue/111 with id abc-123-def in region + us-central1-a, run: + + $ gcloud resource-manager tags holds delete \ + tagValue/111/tagHolds/abc-123-def --location=us-central1-a + +POSITIONAL ARGUMENTS + TAG_HOLD_NAME + TagHold given its full name, specified as + tagValues/{tag_value_id}/tagHolds/{tag_hold_id} + +FLAGS + --location=LOCATION + Region where the TagHold is stored. If not provided, the API will + attempt to find and delete the specified TagHold from the "global" + region. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags holds delete + + $ gcloud beta resource-manager tags holds delete + diff --git a/gcloud/resource-manager/tags/holds/help b/gcloud/resource-manager/tags/holds/help new file mode 100644 index 000000000..f4e9a8608 --- /dev/null +++ b/gcloud/resource-manager/tags/holds/help @@ -0,0 +1,36 @@ +NAME + gcloud resource-manager tags holds - create and manipulate TagHolds + +SYNOPSIS + gcloud resource-manager tags holds COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The Resource Manager Service gives you centralized and programmatic control + over your organization's Tags. As the tag administrator, you will be able + to create and configure restrictions across the tags in the org, and you + will be able to indicate the use of a TagValue as a TagHold. + +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 TagHold resource. + + delete + Delete a TagHold. + + list + List TagHolds under the specified TagValue. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags holds + + $ gcloud beta resource-manager tags holds + diff --git a/gcloud/resource-manager/tags/holds/list b/gcloud/resource-manager/tags/holds/list new file mode 100644 index 000000000..a0496ba82 --- /dev/null +++ b/gcloud/resource-manager/tags/holds/list @@ -0,0 +1,97 @@ +NAME + gcloud resource-manager tags holds list - list TagHolds under the specified + TagValue + +SYNOPSIS + gcloud resource-manager tags holds list PARENT [--holder=HOLDER] + [--location=LOCATION] [--origin=ORIGIN] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List TagHolds under a TagValue. The TagValue can be represented with its + numeric id or its namespaced name of + {org_id}/{tag_key_short_name}/{tag_value_short_name}. Limited to TagHolds + stored in a single --location: if none is provided, the API will assume the + "global" location. Optional filters are --holder and --origin: if provided, + returned TagHolds' holder and origin fields must match the exact flag + value. + +EXAMPLES + To list TagHolds for tagValues/456 in us-central1-a, run: + + $ gcloud resource-manager tags holds list tagValues/456 \ + --location=us-central1-a + + To list TagHolds for tagValues/456, with holder cloud-holder-resource and + origin creator-origin, run: + + $ gcloud resource-manager tags holds list tagValues/456 \ + --holder=cloud-holder-resource --origin=creator-origin + +POSITIONAL ARGUMENTS + PARENT + TagValue resource name or namespaced name to list TagHolds for. This + field should be in the form tagValues/ or + //. + +FLAGS + --holder=HOLDER + The holder field of the TagHold to match exactly. If not provided, the + API will return all matching TagHolds disregarding the holder field. + + --location=LOCATION + Region where the matching TagHolds are stored. If not provided, the API + will attempt to retrieve matching TagHolds from the "global" region. + + --origin=ORIGIN + The origin field of the TagHold to match exactly. If not provided, the + API will return all matching TagHolds disregarding the origin field. + +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 resource-manager tags holds list + + $ gcloud beta resource-manager tags holds list + diff --git a/gcloud/resource-manager/tags/keys/add-iam-policy-binding b/gcloud/resource-manager/tags/keys/add-iam-policy-binding new file mode 100644 index 000000000..1f4b51ea0 --- /dev/null +++ b/gcloud/resource-manager/tags/keys/add-iam-policy-binding @@ -0,0 +1,116 @@ +NAME + gcloud resource-manager tags keys add-iam-policy-binding - adds a policy + binding to the IAM policy of a TagKey + +SYNOPSIS + gcloud resource-manager tags keys add-iam-policy-binding RESOURCE_NAME + --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Adds the IAM policy binding for a TagKey resource given the binding and an + identifier for the TagKey. The identifier can be the TagKey's parent/short + name or the TagKey's ID in the form: tagKeys/{numeric_id}. + +EXAMPLES + To add an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' on the Tag Key 'tagKeys/123', run: + + $ gcloud resource-manager tags keys add-iam-policy-binding \ + tagKeys/123 --member='user:test-user@gmail.com' \ + --role='roles/editor' + + To add an IAM policy binding for a Tag Key with the name 'env' under + 'organization/456' for the role of 'roles/resourcemanager.tagUser' for the + user 'test-user@gmail.com', run: + + $ gcloud resource-manager tags keys add-iam-policy-binding 456/env \ + --member='user:test-user@gmail.com' \ + --role='roles/resourcemanager.tagUser' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags keys add-iam-policy-binding + + $ gcloud beta resource-manager tags keys add-iam-policy-binding + diff --git a/gcloud/resource-manager/tags/keys/create b/gcloud/resource-manager/tags/keys/create new file mode 100644 index 000000000..ffa24d5d4 --- /dev/null +++ b/gcloud/resource-manager/tags/keys/create @@ -0,0 +1,70 @@ +NAME + gcloud resource-manager tags keys create - creates a TagKey resource under + the specified tag parent + +SYNOPSIS + gcloud resource-manager tags keys create (SHORT_NAME --parent=PARENT) + [--async] [--description=DESCRIPTION] [--purpose=PURPOSE] + [--purpose-data=[network=NETWORK]] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To create a TagKey with the name env under 'organizations/123' with + description 'description', run: + + $ gcloud resource-manager tags keys create env \ + --parent=organizations/123 --description=description + +POSITIONAL ARGUMENTS + TagKey. + + This must be specified. + + SHORT_NAME + User specified, friendly name of the TagKey or TagValue. The field + must be 1-63 characters, beginning and ending with an alphanumeric + character ([a-z0-9A-Z]) with dashes (-), underscores ( _ ), dots (.), + and alphanumerics between. + + This positional must be specified if any of the other arguments in + this group are specified. + + --parent=PARENT + Parent of the TagKey in the form of organizations/{org_id}. + + This flag must be specified if any of the other arguments in this + group are specified. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + User-assigned description of the TagKey or TagValue. Must not exceed + 256 characters. + + --purpose=PURPOSE + Purpose specifier of the TagKey that can only be set on creation. + Specifying this field adds additional validation from the policy system + that corresponds to the purpose. PURPOSE must be (currently only one + value is supported): GCE_FIREWALL. + + --purpose-data=[network=NETWORK] + Purpose data of the TagKey that can only be set on creation. This data + is validated by the policy system that corresponds to the purpose. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags keys create + + $ gcloud beta resource-manager tags keys create + diff --git a/gcloud/resource-manager/tags/keys/delete b/gcloud/resource-manager/tags/keys/delete new file mode 100644 index 000000000..4106146d0 --- /dev/null +++ b/gcloud/resource-manager/tags/keys/delete @@ -0,0 +1,49 @@ +NAME + gcloud resource-manager tags keys delete - deletes the specified TagKey + resource + +SYNOPSIS + gcloud resource-manager tags keys delete RESOURCE_NAME [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Deletes the TagKey resource given the TagKey's parent and short name or the + TagKey's numeric id. + +EXAMPLES + To delete a TagKey with id 123, run: + + $ gcloud resource-manager tags keys delete tagKeys/123 + + To delete a TagKey named env under organization 456, run: + + $ gcloud resource-manager tags keys delete 456/env + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags keys delete + + $ gcloud beta resource-manager tags keys delete + diff --git a/gcloud/resource-manager/tags/keys/describe b/gcloud/resource-manager/tags/keys/describe new file mode 100644 index 000000000..bb9e2c856 --- /dev/null +++ b/gcloud/resource-manager/tags/keys/describe @@ -0,0 +1,43 @@ +NAME + gcloud resource-manager tags keys describe - describes a TagKey resource + +SYNOPSIS + gcloud resource-manager tags keys describe RESOURCE_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Gets metadata for a TagKey resource given the TagKey's resource name or + namespaced name. + +EXAMPLES + To describe a TagKey with id '123', run: + + $ gcloud resource-manager tags keys describe tagkeys/123 + + To describe a TagKey with the name 'env' under organizations '456', run: + + $ gcloud resource-manager tags keys describe 456/env + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags keys describe + + $ gcloud beta resource-manager tags keys describe + diff --git a/gcloud/resource-manager/tags/keys/get-iam-policy b/gcloud/resource-manager/tags/keys/get-iam-policy new file mode 100644 index 000000000..9df07db8d --- /dev/null +++ b/gcloud/resource-manager/tags/keys/get-iam-policy @@ -0,0 +1,45 @@ +NAME + gcloud resource-manager tags keys get-iam-policy - gets the IAM policy for + a TagKey resource + +SYNOPSIS + gcloud resource-manager tags keys get-iam-policy RESOURCE_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Returns the IAM policy for a TagKey resource given the TagKey's display + name and parent or the TagKey's numeric id. + +EXAMPLES + To get the IAM policy for a TagKey with id '123', run: + + $ gcloud resource-manager tags keys get-iam-policy tagKeys/123 + + To get the IAM policy for a TagKey with the name 'env' under + 'organizations/456', run: + + $ gcloud resource-manager tags keys get-iam-policy 456/env + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags keys get-iam-policy + + $ gcloud beta resource-manager tags keys get-iam-policy + diff --git a/gcloud/resource-manager/tags/keys/help b/gcloud/resource-manager/tags/keys/help new file mode 100644 index 000000000..0f51b8c69 --- /dev/null +++ b/gcloud/resource-manager/tags/keys/help @@ -0,0 +1,54 @@ +NAME + gcloud resource-manager tags keys - create and manipulate TagKeys + +SYNOPSIS + gcloud resource-manager tags keys COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The Resource Manager Service gives you centralized and programmatic control + over your organization's Tags. As the tag administrator, you will be able + to create and configure restrictions across the tags in the org. As the tag + user, you will be able to attach TagValues to different resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + Adds a policy binding to the IAM policy of a TagKey. + + create + Creates a TagKey resource under the specified tag parent. + + delete + Deletes the specified TagKey resource. + + describe + Describes a TagKey resource. + + get-iam-policy + Gets the IAM policy for a TagKey resource. + + list + Lists TagKeys under the specified parent resource. + + remove-iam-policy-binding + Removes a policy binding from the IAM policy of a TagKey. + + set-iam-policy + Sets IAM policy for a TagKey resource. + + update + Updates the specified TagKey resource's description. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags keys + + $ gcloud beta resource-manager tags keys + diff --git a/gcloud/resource-manager/tags/keys/list b/gcloud/resource-manager/tags/keys/list new file mode 100644 index 000000000..23a07040c --- /dev/null +++ b/gcloud/resource-manager/tags/keys/list @@ -0,0 +1,65 @@ +NAME + gcloud resource-manager tags keys list - lists TagKeys under the specified + parent resource + +SYNOPSIS + gcloud resource-manager tags keys list --parent=PARENT + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all the TagKeys under 'organizations/123', run: + + $ gcloud resource-manager tags keys list --parent='organizations/123' + +REQUIRED FLAGS + --parent=PARENT + Parent of the TagKey in the form of organizations/{org_id}. + +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 resource-manager tags keys list + + $ gcloud beta resource-manager tags keys list + diff --git a/gcloud/resource-manager/tags/keys/remove-iam-policy-binding b/gcloud/resource-manager/tags/keys/remove-iam-policy-binding new file mode 100644 index 000000000..f93faf8d1 --- /dev/null +++ b/gcloud/resource-manager/tags/keys/remove-iam-policy-binding @@ -0,0 +1,121 @@ +NAME + gcloud resource-manager tags keys remove-iam-policy-binding - removes a + policy binding from the IAM policy of a TagKey + +SYNOPSIS + gcloud resource-manager tags keys remove-iam-policy-binding RESOURCE_NAME + --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Removes an IAM policy binding for a TagKey resource given the binding and + an identifier for the TagKey. The identifier can be the TagKey's + parent/short name or the TagKey's ID in the form: tagKeys/{numeric_id}. + +EXAMPLES + To remove an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' on the tagKey 'tagKeys/123', run: + + $ gcloud resource-manager tags keys remove-iam-policy-binding \ + tagKeys/123 --member='user:test-user@gmail.com' \ + --role='roles/editor' + + To remove an IAM policy binding for a TagKey with the name 'env' under + 'organization/456' for the role of 'roles/resourcemanager.tagUser' for the + user 'test-user@gmail.com', run: + + $ gcloud resource-manager tags keys remove-iam-policy-binding \ + 456/env --member='user:test-user@gmail.com' \ + --role='roles/resourcemanager.tagUser' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags keys remove-iam-policy-binding + + $ gcloud beta resource-manager tags keys remove-iam-policy-binding + diff --git a/gcloud/resource-manager/tags/keys/set-iam-policy b/gcloud/resource-manager/tags/keys/set-iam-policy new file mode 100644 index 000000000..f960ca48f --- /dev/null +++ b/gcloud/resource-manager/tags/keys/set-iam-policy @@ -0,0 +1,56 @@ +NAME + gcloud resource-manager tags keys set-iam-policy - sets IAM policy for a + TagKey resource + +SYNOPSIS + gcloud resource-manager tags keys set-iam-policy RESOURCE_NAME POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Sets the IAM policy for a TagKey resource given the TagKey's display name + and parent or the TagKey's numeric id and a file encoded in JSON or YAML + that contains the IAM policy. + +EXAMPLES + To set the IAM policy for a TagKey with id '123' and IAM policy defined in + a YAML file '/path/to/my_policy.yaml', run: + + $ gcloud resource-manager tags keys set-iam-policy tagKeys/123 \ + /path/to/my_policy.yaml + + To set the IAM policy for a tagKey with the short_name 'env' under + 'organization/456' and IAM policy defined in a JSON file + '/path/to/my_policy.json', run: + + $ gcloud resource-manager tags keys set-iam-policy 456/env \ + /path/to/my_policy.json + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags keys set-iam-policy + + $ gcloud beta resource-manager tags keys set-iam-policy + diff --git a/gcloud/resource-manager/tags/keys/update b/gcloud/resource-manager/tags/keys/update new file mode 100644 index 000000000..94ac2d4ec --- /dev/null +++ b/gcloud/resource-manager/tags/keys/update @@ -0,0 +1,55 @@ +NAME + gcloud resource-manager tags keys update - updates the specified TagKey + resource's description + +SYNOPSIS + gcloud resource-manager tags keys update RESOURCE_NAME [--async] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates the TagKey's description given the TagKey's parent and short name + or the TagKey's numeric id. + +EXAMPLES + To update a TagKey with id 123, run: + + $ gcloud resource-manager tags keys update tagKeys/123 \ + --description=foobar + + To update a TagKey named env under organization 456, run: + + $ gcloud resource-manager tags keys update 456/env \ + --description=foobar + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + User-assigned description of the TagKey or TagValue. Must not exceed + 256 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. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags keys update + + $ gcloud beta resource-manager tags keys update + diff --git a/gcloud/resource-manager/tags/values/add-iam-policy-binding b/gcloud/resource-manager/tags/values/add-iam-policy-binding new file mode 100644 index 000000000..803e2e857 --- /dev/null +++ b/gcloud/resource-manager/tags/values/add-iam-policy-binding @@ -0,0 +1,117 @@ +NAME + gcloud resource-manager tags values add-iam-policy-binding - adds a policy + binding to the IAM policy of a TagValue + +SYNOPSIS + gcloud resource-manager tags values add-iam-policy-binding RESOURCE_NAME + --member=PRINCIPAL --role=ROLE + [--condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Adds the IAM policy binding for a TagValue resource given the binding and + an identifier for the TagValue. The identifier can be the TagValue's + // or the + TagValue's ID in the form: tagValues/{numeric_id}. + +EXAMPLES + To add an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' on the Tag Value 'tagValues/111', run: + + $ gcloud resource-manager tags values add-iam-policy-binding \ + tagValues/111 --member='user:test-user@gmail.com' \ + --role='roles/editor' + + To add an IAM policy binding for a Tag Value with the name 'dev' under + 'organization/456/env' for the role of 'roles/resourcemanager.tagUser' for + the user 'test-user@gmail.com', run: + + $ gcloud resource-manager tags values add-iam-policy-binding \ + 456/env/dev --member='user:test-user@gmail.com' \ + --role='roles/resourcemanager.tagUser' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +OPTIONAL FLAGS + At most one of these can be specified: + + --condition=[KEY=VALUE,...] + A condition to include in the binding. When the condition is + explicitly specified as None (--condition=None), a binding without a + condition is added. When the condition is specified and is not None, + --role cannot be a basic role. Basic roles are roles/editor, + roles/owner, and roles/viewer. For more on conditions, refer to the + conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags values add-iam-policy-binding + + $ gcloud beta resource-manager tags values add-iam-policy-binding + diff --git a/gcloud/resource-manager/tags/values/create b/gcloud/resource-manager/tags/values/create new file mode 100644 index 000000000..ae1bd381e --- /dev/null +++ b/gcloud/resource-manager/tags/values/create @@ -0,0 +1,72 @@ +NAME + gcloud resource-manager tags values create - creates a TagValue resource + +SYNOPSIS + gcloud resource-manager tags values create (SHORT_NAME --parent=PARENT) + [--async] [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Creates a TagValue resource given the short_name and description (optional) + as well as the parent, the of the TagValue. The parent of the TagValue is + always a TagKey and the TagKey's details can be passed as a numeric id or + the namespaced name. + +EXAMPLES + To create a TagValue with the short name 'test' and the description + 'description' under a TagKey with a short name 'env' under + 'organizations/123', run: + + $ gcloud resource-manager tags values create test --parent=123/env \ + --description=description + + To create a TagValue with the short name 'test' under TagKey with id '456', + run: + + $ gcloud resource-manager tags values create test \ + --parent=tagKeys/456 --description=description + +POSITIONAL ARGUMENTS + TagValue. + + This must be specified. + + SHORT_NAME + User specified, friendly name of the TagKey or TagValue. The field + must be 1-63 characters, beginning and ending with an alphanumeric + character ([a-z0-9A-Z]) with dashes (-), underscores ( _ ), dots (.), + and alphanumerics between. + + This positional must be specified if any of the other arguments in + this group are specified. + + --parent=PARENT + Parent of the TagValue in either in the form of tagKeys/{id} or + {org_id}/{tagkey_short_name} + + This flag must be specified if any of the other arguments in this + group are specified. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + User-assigned description of the TagKey or TagValue. Must not exceed + 256 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. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags values create + + $ gcloud beta resource-manager tags values create + diff --git a/gcloud/resource-manager/tags/values/delete b/gcloud/resource-manager/tags/values/delete new file mode 100644 index 000000000..6a413ce29 --- /dev/null +++ b/gcloud/resource-manager/tags/values/delete @@ -0,0 +1,49 @@ +NAME + gcloud resource-manager tags values delete - deletes the specified TagValue + resource + +SYNOPSIS + gcloud resource-manager tags values delete RESOURCE_NAME [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Deletes the TagValue resource given the TagValue's parent and short name or + the TagValue's numeric id. + +EXAMPLES + To delete a TagValue with id 123, run: + + $ gcloud resource-manager tags values delete tagValues/123 + + To delete a TagValue named dev with tagKey env under organization 456, run: + + $ gcloud resource-manager tags values delete 456/env/dev + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags values delete + + $ gcloud beta resource-manager tags values delete + diff --git a/gcloud/resource-manager/tags/values/describe b/gcloud/resource-manager/tags/values/describe new file mode 100644 index 000000000..732a3cdfc --- /dev/null +++ b/gcloud/resource-manager/tags/values/describe @@ -0,0 +1,45 @@ +NAME + gcloud resource-manager tags values describe - describes a TagValue + resource + +SYNOPSIS + gcloud resource-manager tags values describe RESOURCE_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Gets metadata for a TagValue resource given the TagValue's resource name or + namespaced name. + +EXAMPLES + To describe a TagValue with id 123, run: + + $ gcloud resource-manager tags values describe tagValues/123 + + To describe a TagValue with name dev with the tagKey env under + organizations 456, run: + + $ gcloud resource-manager tags values describe 456/env/dev + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags values describe + + $ gcloud beta resource-manager tags values describe + diff --git a/gcloud/resource-manager/tags/values/get-iam-policy b/gcloud/resource-manager/tags/values/get-iam-policy new file mode 100644 index 000000000..16502de41 --- /dev/null +++ b/gcloud/resource-manager/tags/values/get-iam-policy @@ -0,0 +1,45 @@ +NAME + gcloud resource-manager tags values get-iam-policy - gets the IAM policy + for a TagValue resource + +SYNOPSIS + gcloud resource-manager tags values get-iam-policy RESOURCE_NAME + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Returns the IAM policy for a TagValue resource given the TagValue's short + name and parent or the TagValue's numeric id. + +EXAMPLES + To get the IAM policy for a TagValue with id '123', run: + + $ gcloud resource-manager tags values get-iam-policy tagValues/123 + + To get the IAM policy for a TagValue with the name 'dev' under + 'organizations/456' and tagKey parent 'env', run: + + $ gcloud resource-manager tags values get-iam-policy 456/env/dev + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 resource-manager tags values get-iam-policy + + $ gcloud beta resource-manager tags values get-iam-policy + diff --git a/gcloud/resource-manager/tags/values/help b/gcloud/resource-manager/tags/values/help new file mode 100644 index 000000000..16852db5c --- /dev/null +++ b/gcloud/resource-manager/tags/values/help @@ -0,0 +1,54 @@ +NAME + gcloud resource-manager tags values - create and manipulate TagValues + +SYNOPSIS + gcloud resource-manager tags values COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The Resource Manager Service gives you centralized and programmatic control + over your organization's Tags. As the tag administrator, you will be able + to create and configure restrictions across the tags in the org. As the tag + user, you will be able to attach TagValues to different resources. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + Adds a policy binding to the IAM policy of a TagValue. + + create + Creates a TagValue resource. + + delete + Deletes the specified TagValue resource. + + describe + Describes a TagValue resource. + + get-iam-policy + Gets the IAM policy for a TagValue resource. + + list + Lists TagValues under the specified parent resource. + + remove-iam-policy-binding + Removes a policy binding from the IAM policy of a TagValue. + + set-iam-policy + Sets IAM policy for a TagValue resource. + + update + Updates the specified TagValue resource's description. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags values + + $ gcloud beta resource-manager tags values + diff --git a/gcloud/resource-manager/tags/values/list b/gcloud/resource-manager/tags/values/list new file mode 100644 index 000000000..3a0abdd7d --- /dev/null +++ b/gcloud/resource-manager/tags/values/list @@ -0,0 +1,66 @@ +NAME + gcloud resource-manager tags values list - lists TagValues under the + specified parent resource + +SYNOPSIS + gcloud resource-manager tags values list --parent=PARENT + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list all the TagValues under organizations/123/env, run: + + $ gcloud resource-manager tags values list --parent=123/env + +REQUIRED FLAGS + --parent=PARENT + Parent of the TagValue in either in the form of tagKeys/{id} or + {org_id}/{tagkey_short_name} + +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 resource-manager tags values list + + $ gcloud beta resource-manager tags values list + diff --git a/gcloud/resource-manager/tags/values/remove-iam-policy-binding b/gcloud/resource-manager/tags/values/remove-iam-policy-binding new file mode 100644 index 000000000..2904a4087 --- /dev/null +++ b/gcloud/resource-manager/tags/values/remove-iam-policy-binding @@ -0,0 +1,122 @@ +NAME + gcloud resource-manager tags values remove-iam-policy-binding - removes a + policy binding from the IAM policy of a TagValue + +SYNOPSIS + gcloud resource-manager tags values remove-iam-policy-binding RESOURCE_NAME + --member=PRINCIPAL --role=ROLE + [--all | --condition=[KEY=VALUE,...] + | --condition-from-file=CONDITION_FROM_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Removes an IAM policy binding for a TagValue resource given the binding and + an identifier for the TagValue. The identifier can be the TagValue's + // or the + TagValue's ID in the form: tagValues/{numeric_id}. + +EXAMPLES + To remove an IAM policy binding for the role of 'roles/editor' for the user + 'test-user@gmail.com' on the tagValue 'tagValues/111', run: + + $ gcloud resource-manager tags values remove-iam-policy-binding \ + tagValues/111 --member='user:test-user@gmail.com' \ + --role='roles/editor' + + To remove an IAM policy binding for a TagValue with the name 'dev' under + 'organization/456/env' for the role of 'roles/resourcemanager.tagUser' for + the user 'test-user@gmail.com', run: + + $ gcloud resource-manager tags values remove-iam-policy-binding \ + 456/env/dev --member='user:test-user@gmail.com' \ + --role='roles/resourcemanager.tagUser' + + See https://cloud.google.com/iam/docs/managing-policies for details of + policy role and member types. + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +OPTIONAL FLAGS + At most one of these can be specified: + + --all + Remove all bindings with this role and principal, irrespective of any + conditions. + + --condition=[KEY=VALUE,...] + The condition of the binding that you want to remove. When the + condition is explicitly specified as None (--condition=None), a + binding without a condition is removed. Otherwise, only a binding + with a condition that exactly matches the specified condition + (including the optional description) is removed. For more on + conditions, refer to the conditions overview guide: + https://cloud.google.com/iam/docs/conditions-overview + + When using the --condition flag, include the following key-value + pairs: + + expression + (Required) Condition expression that evaluates to True or False. + This uses a subset of Common Expression Language syntax. + + If the condition expression includes a comma, use a different + delimiter to separate the key-value pairs. Specify the delimiter + before listing the key-value pairs. For example, to specify a + colon (:) as the delimiter, do the following: + --condition=^:^title=TITLE:expression=EXPRESSION. For more + information, see + https://cloud.google.com/sdk/gcloud/reference/topic/escaping. + + title + (Required) A short string describing the purpose of the + expression. + + description + (Optional) Additional description for the expression. + + --condition-from-file=CONDITION_FROM_FILE + Path to a local JSON or YAML file that defines the condition. To see + available fields, see the help for --condition. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags values remove-iam-policy-binding + + $ gcloud beta resource-manager tags values remove-iam-policy-binding + diff --git a/gcloud/resource-manager/tags/values/set-iam-policy b/gcloud/resource-manager/tags/values/set-iam-policy new file mode 100644 index 000000000..9d743cb78 --- /dev/null +++ b/gcloud/resource-manager/tags/values/set-iam-policy @@ -0,0 +1,56 @@ +NAME + gcloud resource-manager tags values set-iam-policy - sets IAM policy for a + TagValue resource + +SYNOPSIS + gcloud resource-manager tags values set-iam-policy RESOURCE_NAME + POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Sets the IAM policy for a TagValue resource given the TagValue's short name + name and parent or the TagValue's numeric id and a file encoded in JSON or + YAML that contains the IAM policy. + +EXAMPLES + To set the IAM policy for a TagValue with id '111' and IAM policy defined + in a YAML file '/path/to/my_policy.yaml', run: + + $ gcloud resource-manager tags values set-iam-policy tagValues/111 \ + /path/to/my_policy.yaml + + To set the IAM policy for a tagValue with the short_name 'dev' under + 'organization/456' and tag key short name 'env' and IAM policy defined in a + JSON file '/path/to/my_policy.json', run: + + $ gcloud resource-manager tags values set-iam-policy 456/env/dev \ + /path/to/my_policy.json + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags values set-iam-policy + + $ gcloud beta resource-manager tags values set-iam-policy + diff --git a/gcloud/resource-manager/tags/values/update b/gcloud/resource-manager/tags/values/update new file mode 100644 index 000000000..fdab2c8dc --- /dev/null +++ b/gcloud/resource-manager/tags/values/update @@ -0,0 +1,57 @@ +NAME + gcloud resource-manager tags values update - updates the specified TagValue + resource's description + +SYNOPSIS + gcloud resource-manager tags values update RESOURCE_NAME [--async] + [--description=DESCRIPTION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Updates the TagValue's description given the TagValue's + // or the TagValue's + numeric id tagValues/ + +EXAMPLES + To update a TagValue with id 123, run: + + $ gcloud resource-manager tags values update tagValues/123 \ + --description="foobar" + + To update a TagValue named dev with the tagKey env under organization 456, + run: + + $ gcloud resource-manager tags values update 465/env/dev \ + --description="foobar" + +POSITIONAL ARGUMENTS + RESOURCE_NAME + Resource name or namespaced name. The resource name should be in the + form {resource_type}/{numeric_id}. The namespaced name should be in the + form {org_id}/{short_name} where short_name must be 1-63 characters, + beginning and ending with an alphanumeric character ([a-z0-9A-Z]) with + dashes (-), underscores ( _ ), dots (.), and alphanumerics between. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + User-assigned description of the TagKey or TagValue. Must not exceed + 256 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. + +NOTES + These variants are also available: + + $ gcloud alpha resource-manager tags values update + + $ gcloud beta resource-manager tags values update +