diff --git a/gcloud/_version b/gcloud/_version index eb1c1280a..aae989eac 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 437.0.1 -alpha 2023.06.30 -beta 2023.06.30 +Google Cloud SDK 438.0.0 +alpha 2023.07.07 +beta 2023.07.07 bq 2.0.93 bundled-python3-unix 3.9.16 -core 2023.06.30 +core 2023.07.07 gcloud-crc32c 1.0.0 -gsutil 5.24 +gsutil 5.25 diff --git a/gcloud/alpha/ai/endpoints/deploy-model b/gcloud/alpha/ai/endpoints/deploy-model index ac2909e61..96f5471f4 100644 --- a/gcloud/alpha/ai/endpoints/deploy-model +++ b/gcloud/alpha/ai/endpoints/deploy-model @@ -73,9 +73,9 @@ OPTIONAL FLAGS type The type of the accelerator. Choices are 'nvidia-a100-80gb', - 'nvidia-l4', 'nvidia-tesla-a100', 'nvidia-tesla-k80', - 'nvidia-tesla-p100', 'nvidia-tesla-p4', 'nvidia-tesla-t4', - 'nvidia-tesla-v100'. + 'nvidia-h100-80gb', 'nvidia-l4', 'nvidia-tesla-a100', + 'nvidia-tesla-k80', 'nvidia-tesla-p100', 'nvidia-tesla-p4', + 'nvidia-tesla-t4', 'nvidia-tesla-v100'. count The number of accelerators to attach to each machine running the diff --git a/gcloud/alpha/anthos/config/controller/update b/gcloud/alpha/anthos/config/controller/update index dac73bfba..b699ddd63 100644 --- a/gcloud/alpha/anthos/config/controller/update +++ b/gcloud/alpha/anthos/config/controller/update @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha anthos config controller update (NAME : --location=LOCATION) - [--async] [--man-block=MAN_BLOCK] [GCLOUD_WIDE_FLAG ...] + [--async] [--experimental-features=[FEATURE,...]] + [--man-block=MAN_BLOCK] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update an Anthos Config Controller instance. @@ -56,6 +57,9 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --experimental-features=[FEATURE,...] + Enable experimental features. It can only be enabled in ALPHA version. + --man-block=MAN_BLOCK Master Authorized Network. Allows access to the Kubernetes control plane from this block. Defaults to '0.0.0.0/0' if flag is not provided. diff --git a/gcloud/alpha/artifacts/docker/tags/help b/gcloud/alpha/artifacts/docker/tags/help index af1131c5e..7fdd4bfe6 100644 --- a/gcloud/alpha/artifacts/docker/tags/help +++ b/gcloud/alpha/artifacts/docker/tags/help @@ -9,29 +9,31 @@ DESCRIPTION (ALPHA) To add tag my-tag to image busy-box referenced by digest abcxyz in us-west1: - $ gcloud alpha artifacts docker tags - us-west1-docker.pkg.dev/my-project/my-repository/busy-box@sha256:abcxyz - us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag + $ gcloud alpha artifacts docker tags add \ + us-west1-docker.pkg.dev/my-project/my-repository/\ + busy-box@sha256:abcxyz \ + us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag To add tag my-tag to image busy-box referenced by tag latest in us-west1: - $ gcloud alpha artifacts docker tags \ - us-west1-docker.pkg.dev/my-project/my-repository/busy-box:latest - us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag + $ gcloud alpha artifacts docker tags add \ + us-west1-docker.pkg.dev/my-project/my-repository/\ + busy-box:latest \ + us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag To delete tag my-tag from image busy-box in us-west1: - $ gcloud alpha artifacts docker tags \ + $ gcloud alpha artifacts docker tags delete \ us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag To list all tags in repository my-repository in us-west1: - $ gcloud alpha artifacts docker tags \ + $ gcloud alpha artifacts docker tags list \ us-west1-docker.pkg.dev/my-project/my-repository To list tags for image busy-box in us-west1: - $ gcloud alpha artifacts docker tags \ + $ gcloud alpha artifacts docker tags list \ us-west1-docker.pkg.dev/my-project/my-repository/busy-box GCLOUD WIDE FLAGS diff --git a/gcloud/alpha/builds/connections/add-iam-policy-binding b/gcloud/alpha/builds/connections/add-iam-policy-binding index aef11cabb..e1a9d960e 100644 --- a/gcloud/alpha/builds/connections/add-iam-policy-binding +++ b/gcloud/alpha/builds/connections/add-iam-policy-binding @@ -90,7 +90,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections add-iam-policy-binding $ gcloud beta builds connections add-iam-policy-binding diff --git a/gcloud/alpha/builds/connections/create/github b/gcloud/alpha/builds/connections/create/github index 43fa03310..098779ae5 100644 --- a/gcloud/alpha/builds/connections/create/github +++ b/gcloud/alpha/builds/connections/create/github @@ -114,7 +114,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections create github $ gcloud beta builds connections create github diff --git a/gcloud/alpha/builds/connections/create/github-enterprise b/gcloud/alpha/builds/connections/create/github-enterprise index 9adcf48df..406ddd2e3 100644 --- a/gcloud/alpha/builds/connections/create/github-enterprise +++ b/gcloud/alpha/builds/connections/create/github-enterprise @@ -168,7 +168,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections create github-enterprise $ gcloud beta builds connections create github-enterprise diff --git a/gcloud/alpha/builds/connections/create/gitlab b/gcloud/alpha/builds/connections/create/gitlab index e23983934..a1c0f0a70 100644 --- a/gcloud/alpha/builds/connections/create/gitlab +++ b/gcloud/alpha/builds/connections/create/gitlab @@ -147,7 +147,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections create gitlab $ gcloud beta builds connections create gitlab diff --git a/gcloud/alpha/builds/connections/create/help b/gcloud/alpha/builds/connections/create/help index 8f74bd355..c5827bdbc 100644 --- a/gcloud/alpha/builds/connections/create/help +++ b/gcloud/alpha/builds/connections/create/help @@ -30,7 +30,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections create $ gcloud beta builds connections create diff --git a/gcloud/alpha/builds/connections/delete b/gcloud/alpha/builds/connections/delete index a7ed4a21a..a4fe89f10 100644 --- a/gcloud/alpha/builds/connections/delete +++ b/gcloud/alpha/builds/connections/delete @@ -68,7 +68,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections delete $ gcloud beta builds connections delete diff --git a/gcloud/alpha/builds/connections/describe b/gcloud/alpha/builds/connections/describe index 71e0c49f0..675ca1640 100644 --- a/gcloud/alpha/builds/connections/describe +++ b/gcloud/alpha/builds/connections/describe @@ -65,7 +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. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections describe $ gcloud beta builds connections describe diff --git a/gcloud/alpha/builds/connections/get-iam-policy b/gcloud/alpha/builds/connections/get-iam-policy index ec63ab2ef..4811d6809 100644 --- a/gcloud/alpha/builds/connections/get-iam-policy +++ b/gcloud/alpha/builds/connections/get-iam-policy @@ -92,7 +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. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections get-iam-policy $ gcloud beta builds connections get-iam-policy diff --git a/gcloud/alpha/builds/connections/help b/gcloud/alpha/builds/connections/help index 1a27ebc7e..6fde444e6 100644 --- a/gcloud/alpha/builds/connections/help +++ b/gcloud/alpha/builds/connections/help @@ -46,7 +46,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections $ gcloud beta builds connections diff --git a/gcloud/alpha/builds/connections/list b/gcloud/alpha/builds/connections/list index 2bcc73046..2192ddf92 100644 --- a/gcloud/alpha/builds/connections/list +++ b/gcloud/alpha/builds/connections/list @@ -83,7 +83,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections list $ gcloud beta builds connections list diff --git a/gcloud/alpha/builds/connections/set-iam-policy b/gcloud/alpha/builds/connections/set-iam-policy index e0fe1ff14..27425c9dc 100644 --- a/gcloud/alpha/builds/connections/set-iam-policy +++ b/gcloud/alpha/builds/connections/set-iam-policy @@ -76,7 +76,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections set-iam-policy $ gcloud beta builds connections set-iam-policy diff --git a/gcloud/alpha/builds/connections/update/github b/gcloud/alpha/builds/connections/update/github index 572ea456e..7df892f06 100644 --- a/gcloud/alpha/builds/connections/update/github +++ b/gcloud/alpha/builds/connections/update/github @@ -87,7 +87,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections update github $ gcloud beta builds connections update github diff --git a/gcloud/alpha/builds/connections/update/github-enterprise b/gcloud/alpha/builds/connections/update/github-enterprise index ddeaa01ab..1bbc5c329 100644 --- a/gcloud/alpha/builds/connections/update/github-enterprise +++ b/gcloud/alpha/builds/connections/update/github-enterprise @@ -112,7 +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. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections update github-enterprise $ gcloud beta builds connections update github-enterprise diff --git a/gcloud/alpha/builds/connections/update/gitlab b/gcloud/alpha/builds/connections/update/gitlab index 39949df1b..534a2c1d7 100644 --- a/gcloud/alpha/builds/connections/update/gitlab +++ b/gcloud/alpha/builds/connections/update/gitlab @@ -101,7 +101,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections update gitlab $ gcloud beta builds connections update gitlab diff --git a/gcloud/alpha/builds/connections/update/help b/gcloud/alpha/builds/connections/update/help index 51333a224..e9d72fc2f 100644 --- a/gcloud/alpha/builds/connections/update/help +++ b/gcloud/alpha/builds/connections/update/help @@ -30,7 +30,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds connections update $ gcloud beta builds connections update diff --git a/gcloud/alpha/builds/repositories/create b/gcloud/alpha/builds/repositories/create index a2d0980c0..95cb85d5e 100644 --- a/gcloud/alpha/builds/repositories/create +++ b/gcloud/alpha/builds/repositories/create @@ -83,7 +83,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds repositories create $ gcloud beta builds repositories create diff --git a/gcloud/alpha/builds/repositories/delete b/gcloud/alpha/builds/repositories/delete index 3e0c12972..9b526e384 100644 --- a/gcloud/alpha/builds/repositories/delete +++ b/gcloud/alpha/builds/repositories/delete @@ -78,7 +78,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds repositories delete $ gcloud beta builds repositories delete diff --git a/gcloud/alpha/builds/repositories/describe b/gcloud/alpha/builds/repositories/describe index cfbfbe380..b2b51295a 100644 --- a/gcloud/alpha/builds/repositories/describe +++ b/gcloud/alpha/builds/repositories/describe @@ -73,7 +73,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds repositories describe $ gcloud beta builds repositories describe diff --git a/gcloud/alpha/builds/repositories/help b/gcloud/alpha/builds/repositories/help index 9ceaa59c5..1273711e0 100644 --- a/gcloud/alpha/builds/repositories/help +++ b/gcloud/alpha/builds/repositories/help @@ -32,7 +32,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds repositories $ gcloud beta builds repositories diff --git a/gcloud/alpha/builds/repositories/list b/gcloud/alpha/builds/repositories/list index 867902529..6c1bb14d0 100644 --- a/gcloud/alpha/builds/repositories/list +++ b/gcloud/alpha/builds/repositories/list @@ -99,7 +99,9 @@ NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early - access allowlist. This variant is also available: + access allowlist. These variants are also available: + + $ gcloud builds repositories list $ gcloud beta builds repositories list diff --git a/gcloud/alpha/builds/submit b/gcloud/alpha/builds/submit index 8f2613788..a62523e85 100644 --- a/gcloud/alpha/builds/submit +++ b/gcloud/alpha/builds/submit @@ -118,7 +118,7 @@ FLAGS --machine-type=MACHINE_TYPE Machine type used to run the build. MACHINE_TYPE must be one of: - e2-highcpu-32, e2-highcpu-8, n1-highcpu-32, n1-highcpu-8. + e2-highcpu-32, e2-highcpu-8, e2-medium, n1-highcpu-32, n1-highcpu-8. --region=REGION The region of the Cloud Build Service to use. Must be set to a diff --git a/gcloud/alpha/builds/triggers/create/bitbucketserver b/gcloud/alpha/builds/triggers/create/bitbucketserver index b139bbe01..5d4f4fbe9 100644 --- a/gcloud/alpha/builds/triggers/create/bitbucketserver +++ b/gcloud/alpha/builds/triggers/create/bitbucketserver @@ -105,24 +105,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud alpha builds triggers create bitbucketserver ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/alpha/builds/triggers/create/cloud-source-repositories b/gcloud/alpha/builds/triggers/create/cloud-source-repositories index 70e645103..b1a95facb 100644 --- a/gcloud/alpha/builds/triggers/create/cloud-source-repositories +++ b/gcloud/alpha/builds/triggers/create/cloud-source-repositories @@ -87,24 +87,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - 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 + $ gcloud alpha builds triggers create cloud-source-repositories \ + ... --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/alpha/builds/triggers/create/github b/gcloud/alpha/builds/triggers/create/github index 1615db25f..f343de573 100644 --- a/gcloud/alpha/builds/triggers/create/github +++ b/gcloud/alpha/builds/triggers/create/github @@ -96,24 +96,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud alpha builds triggers create github ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/alpha/builds/triggers/create/gitlab b/gcloud/alpha/builds/triggers/create/gitlab new file mode 100644 index 000000000..d62c61338 --- /dev/null +++ b/gcloud/alpha/builds/triggers/create/gitlab @@ -0,0 +1,209 @@ +NAME + gcloud alpha builds triggers create gitlab - create a build trigger for a + 2nd-gen GitLab repository + +SYNOPSIS + gcloud alpha builds triggers create gitlab + (--trigger-config=PATH | [(--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-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) + : --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --name=NAME --region=REGION + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a build trigger for a 2nd-gen GitLab repository. + +EXAMPLES + To create a push trigger with a 2nd-gen repository for all branches: + + $ gcloud alpha builds triggers create gitlab --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/global/connections/myconn/\ + repositories/myrepo" --branch-pattern=".*" \ + --build-config="cloudbuild.yaml" + + To create a pull request trigger with a 1st-gen repository for main: + + $ gcloud alpha builds triggers create gitlab --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/global/connections/myconn/\ + repositories/myrepo" --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 + + --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. + + --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, builds/region, + which is the default region to use when working with Cloud Build + resources, is used. If builds/region is unset, region is set to + global. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --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: + + $ gcloud alpha builds triggers create gitlab ... \ + --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". + + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, + SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values + + 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 regular expression 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 regular expression 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 argument 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. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud builds triggers create gitlab + + $ gcloud beta builds triggers create gitlab + diff --git a/gcloud/alpha/builds/triggers/create/gitlab-enterprise b/gcloud/alpha/builds/triggers/create/gitlab-enterprise index d9594d766..14158cd9b 100644 --- a/gcloud/alpha/builds/triggers/create/gitlab-enterprise +++ b/gcloud/alpha/builds/triggers/create/gitlab-enterprise @@ -86,24 +86,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud alpha builds triggers create gitlab-enterprise ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/alpha/builds/triggers/create/help b/gcloud/alpha/builds/triggers/create/help index 5f77113f1..8368b7ea3 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 + (ALPHA) Create a build trigger for a 2nd-gen GitLab repository. + gitlab-enterprise (ALPHA) Create a build trigger for a GitLab Enterprise repository. diff --git a/gcloud/alpha/builds/triggers/create/manual b/gcloud/alpha/builds/triggers/create/manual index b336e320c..265f9b3c3 100644 --- a/gcloud/alpha/builds/triggers/create/manual +++ b/gcloud/alpha/builds/triggers/create/manual @@ -71,24 +71,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud alpha builds triggers create manual ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/alpha/builds/triggers/create/pubsub b/gcloud/alpha/builds/triggers/create/pubsub index b8f8675f3..c67eb0f2f 100644 --- a/gcloud/alpha/builds/triggers/create/pubsub +++ b/gcloud/alpha/builds/triggers/create/pubsub @@ -89,24 +89,23 @@ REQUIRED FLAGS for more details. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud alpha builds triggers create pubsub ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/alpha/builds/triggers/create/webhook b/gcloud/alpha/builds/triggers/create/webhook index 865ea61e4..80e461619 100644 --- a/gcloud/alpha/builds/triggers/create/webhook +++ b/gcloud/alpha/builds/triggers/create/webhook @@ -95,24 +95,23 @@ REQUIRED FLAGS for more details. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud alpha builds triggers create webhook ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/alpha/builds/triggers/run b/gcloud/alpha/builds/triggers/run index ad4cdc0b6..b0cd50fcd 100644 --- a/gcloud/alpha/builds/triggers/run +++ b/gcloud/alpha/builds/triggers/run @@ -47,24 +47,21 @@ POSITIONAL ARGUMENTS FLAGS --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For example: - For example (using some nonsensical substitution keys; all keys must - begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud alpha builds triggers run ... \ --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. + Substitutions can be applied to user-defined variables (starting with + an underscore) and to the following built-in variables: 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values At most one of these can be specified: diff --git a/gcloud/alpha/compute/backend-services/add-backend b/gcloud/alpha/compute/backend-services/add-backend index d7f7d8c68..ab4514b8d 100644 --- a/gcloud/alpha/compute/backend-services/add-backend +++ b/gcloud/alpha/compute/backend-services/add-backend @@ -234,20 +234,21 @@ OPTIONAL FLAGS (https://cloud.google.com/load-balancing/docs/backend-service#balancing-mode-combos). --preference=PREFERENCE - Defines whether this backend should be fully utilized before sending - traffic to backends with default preference. This cannot be used with - regional managed instance groups and when the endpoint type of an - attached network endpoint group is INTERNET_IP_PORT, + Defines whether a backend should be fully utilized before sending + traffic to backends with default preference. This parameter cannot be + used with regional managed instance groups and when the endpoint type + of an attached network endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or SERVERLESS. PREFERENCE must be one of: DEFAULT - If preferred backends don't have enough capacity, backends in this - layer would be used and traffic would be assigned based on the load - balancing algorithm you use. This is the default. + This is the default setting. If the designated preferred backends + don't have enough capacity, backends in the default category are + used. Traffic is distributed between default backends based on the + load balancing algorithm you use. PREFERRED - Backends with this preference level will be filled up to their - capacity limits first, based on RTT. + Backends with this preference setting are used up to their capacity + limits first, while optimizing overall network latency. At most one of these can be specified: diff --git a/gcloud/alpha/compute/backend-services/update-backend b/gcloud/alpha/compute/backend-services/update-backend index b5b205fcd..c94a379f3 100644 --- a/gcloud/alpha/compute/backend-services/update-backend +++ b/gcloud/alpha/compute/backend-services/update-backend @@ -203,20 +203,21 @@ OPTIONAL FLAGS (https://cloud.google.com/load-balancing/docs/backend-service#balancing-mode-combos). --preference=PREFERENCE - Defines whether this backend should be fully utilized before sending - traffic to backends with default preference. This cannot be used with - regional managed instance groups and when the endpoint type of an - attached network endpoint group is INTERNET_IP_PORT, + Defines whether a backend should be fully utilized before sending + traffic to backends with default preference. This parameter cannot be + used with regional managed instance groups and when the endpoint type + of an attached network endpoint group is INTERNET_IP_PORT, INTERNET_FQDN_PORT, or SERVERLESS. PREFERENCE must be one of: DEFAULT - If preferred backends don't have enough capacity, backends in this - layer would be used and traffic would be assigned based on the load - balancing algorithm you use. This is the default. + This is the default setting. If the designated preferred backends + don't have enough capacity, backends in the default category are + used. Traffic is distributed between default backends based on the + load balancing algorithm you use. PREFERRED - Backends with this preference level will be filled up to their - capacity limits first, based on RTT. + Backends with this preference setting are used up to their capacity + limits first, while optimizing overall network latency. At most one of these can be specified: diff --git a/gcloud/alpha/compute/disks/create b/gcloud/alpha/compute/disks/create index abad1a533..28f9118db 100644 --- a/gcloud/alpha/compute/disks/create +++ b/gcloud/alpha/compute/disks/create @@ -94,8 +94,9 @@ FLAGS their boot disks. See the descriptions of supported features at: https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features. GUEST_OS_FEATURE must be one of: BARE_METAL_LINUX_COMPATIBLE, GVNIC, - MULTI_IP_SUBNET, SEV_CAPABLE, SEV_LIVE_MIGRATABLE, SEV_SNP_CAPABLE, - TDX_CAPABLE, UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, WINDOWS. + IDPF, MULTI_IP_SUBNET, SEV_CAPABLE, SEV_LIVE_MIGRATABLE, + SEV_SNP_CAPABLE, TDX_CAPABLE, UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, + WINDOWS. --interface=INTERFACE Specifies the disk interface to use for attaching this disk. Valid diff --git a/gcloud/alpha/compute/firewall-policies/rules/create b/gcloud/alpha/compute/firewall-policies/rules/create index 035d8741f..4a74424da 100644 --- a/gcloud/alpha/compute/firewall-policies/rules/create +++ b/gcloud/alpha/compute/firewall-policies/rules/create @@ -94,14 +94,15 @@ OPTIONAL FLAGS --security-profile-group=SECURITY_PROFILE_GROUP An org-based security profile group to be used with - apply_security_profile_group action.Allowed formats are:a) - http(s):////organizations//locations/global/securityProfileGroups/b) - (//)/organizations//locations/global/securityProfileGroups/c) - In case 'c' gCloud CLI will create a reference matching format - 'a',but to make it work CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSERVICES - property must be set.In order to set this property, please run the - command 'gcloud config set api_endpoint_overrides/networkservices - https:///' + apply_security_profile_group action. Allowed formats are: a) + http(s):////organizations//locations/global/securityProfileGroups/ + b) + (//)/organizations//locations/global/securityProfileGroups/ + c) . In case "c" gCloud CLI will create a reference matching + format "a", but to make it work + CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSECURITY property must be set. + In order to set this property, please run the command gcloud config set + api_endpoint_overrides/networksecurity https:///. --src-address-groups=[SOURCE_ADDRESS_GROUPS,...] Source address groups to match for this rule. Can only be specified if diff --git a/gcloud/alpha/compute/firewall-policies/rules/update b/gcloud/alpha/compute/firewall-policies/rules/update index 00f49044a..11e5033b4 100644 --- a/gcloud/alpha/compute/firewall-policies/rules/update +++ b/gcloud/alpha/compute/firewall-policies/rules/update @@ -99,14 +99,15 @@ OPTIONAL FLAGS --security-profile-group=SECURITY_PROFILE_GROUP An org-based security profile group to be used with - apply_security_profile_group action.Allowed formats are:a) - http(s):////organizations//locations/global/securityProfileGroups/b) - (//)/organizations//locations/global/securityProfileGroups/c) - In case 'c' gCloud CLI will create a reference matching format - 'a',but to make it work CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSERVICES - property must be set.In order to set this property, please run the - command 'gcloud config set api_endpoint_overrides/networkservices - https:///' + apply_security_profile_group action. Allowed formats are: a) + http(s):////organizations//locations/global/securityProfileGroups/ + b) + (//)/organizations//locations/global/securityProfileGroups/ + c) . In case "c" gCloud CLI will create a reference matching + format "a", but to make it work + CLOUDSDK_API_ENDPOINT_OVERRIDES_NETWORKSECURITY property must be set. + In order to set this property, please run the command gcloud config set + api_endpoint_overrides/networksecurity https:///. --src-address-groups=[SOURCE_ADDRESS_GROUPS,...] Source address groups to match for this rule. Can only be specified if diff --git a/gcloud/alpha/compute/future-reservations/update b/gcloud/alpha/compute/future-reservations/update index d95e051b6..871455473 100644 --- a/gcloud/alpha/compute/future-reservations/update +++ b/gcloud/alpha/compute/future-reservations/update @@ -4,15 +4,17 @@ NAME SYNOPSIS gcloud alpha compute future-reservations update FUTURE_RESERVATION + [--description=DESCRIPTION] [--name-prefix=NAME_PREFIX] [--planning-status=PLANNING_STATUS] [--total-count=TOTAL_COUNT] [--zone=ZONE] - [--accelerator=[count=COUNT],[type=TYPE] - --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE] - --machine-type=MACHINE_TYPE - --maintenance-interval=MAINTENANCE_INTERVAL - --min-cpu-platform=MIN_CPU_PLATFORM] [--clear-share-settings | --share-setting=SHARE_SETTING --share-with=PROJECT,[PROJECT,...]] + [--machine-type=MACHINE_TYPE + --maintenance-interval=MAINTENANCE_INTERVAL + --min-cpu-platform=MIN_CPU_PLATFORM + --accelerator=[count=COUNT],[type=TYPE] + | --clear-accelerator --clear-local-ssd + | --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE]] [--start-time=START_TIME --duration=DURATION | --end-time=END_TIME] [GCLOUD_WIDE_FLAG ...] @@ -33,6 +35,13 @@ POSITIONAL ARGUMENTS Name of the future reservation to update. FLAGS + --description=DESCRIPTION + An optional description of the reservation to create. + + --name-prefix=NAME_PREFIX + User provided name prefix for system generated reservations when + capacity is delivered at start time. + --planning-status=PLANNING_STATUS The planning status of the future reservation. The default value is DRAFT. While in DRAFT, any changes to the future reservation's @@ -72,34 +81,29 @@ FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. + Manage the properties of a shared future reservation. + + At most one of these can be specified: + + --clear-share-settings + Clear share settings on future reservation. This will result in + non-shared future reservation. + + Manage the share settings of a future reservation. + + --share-setting=SHARE_SETTING + Specify if this future reservation is shared, and if so, the type + of sharing. If you omit this flag, this value is local (not shared) + by default. SHARE_SETTING must be one of: local, projects. + + --share-with=PROJECT,[PROJECT,...] + If this future reservation is shared (--share-setting is not + local), provide a list of all of the specific projects that this + future reservation is shared with. List must contain project IDs or + project numbers. + Manage the specific SKU reservation properties. - --accelerator=[count=COUNT],[type=TYPE] - Manage the configuration of the type and number of accelerator cards - attached. - count - The number of accelerators to attach to each instance in the - reservation. - type - The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) of - accelerator to attach to instances in the reservation. Use gcloud - compute accelerator-types list to learn about all available - accelerator types. - - --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE] - Manage the size and the interface of local SSD to use. See - https://cloud.google.com/compute/docs/disks/local-ssd for more - information. - interface - The kind of disk interface exposed to the VM for this SSD. Valid - values are scsi and nvme. SCSI is the default and is supported by - more guest operating systems. NVME may provide higher - performance. - size - The size of the local SSD in base-2 GB. - count - The number of local SSD to use per VM. Default value is 1. - --machine-type=MACHINE_TYPE The type of machine (name only) that has a fixed number of vCPUs and a fixed amount of memory. You can also specify a custom machine type @@ -127,26 +131,45 @@ FLAGS --min-cpu-platform=MIN_CPU_PLATFORM Optional minimum CPU platform of the reservation to create. - Manage the properties of a shared future reservation. + Manage the accelerators of a future reservation. - At most one of these can be specified: + At most one of these can be specified: - --clear-share-settings - Clear share settings on future reservation. This will result in - non-shared future reservation. + --accelerator=[count=COUNT],[type=TYPE] + Manage the configuration of the type and number of accelerator + cards attached. + count + The number of accelerators to attach to each instance in the + reservation. + type + The specific type (e.g. nvidia-tesla-k80 for nVidia Tesla K80) + of accelerator to attach to instances in the reservation. Use + gcloud compute accelerator-types list to learn about all + available accelerator types. - Manage the share settings of a future reservation. + --clear-accelerator + Remove all accelerators from the future reservation. - --share-setting=SHARE_SETTING - Specify if this future reservation is shared, and if so, the type - of sharing. If you omit this flag, this value is local (not shared) - by default. SHARE_SETTING must be one of: local, projects. + Manage the local ssd of a future reservation. - --share-with=PROJECT,[PROJECT,...] - If this future reservation is shared (--share-setting is not - local), provide a list of all of the specific projects that this - future reservation is shared with. List must contain project IDs or - project numbers. + At most one of these can be specified: + + --clear-local-ssd + Remove all local ssd information on the future reservation. + + --local-ssd=[count=COUNT],[interface=INTERFACE],[size=SIZE] + Manage the size and the interface of local SSD to use. See + https://cloud.google.com/compute/docs/disks/local-ssd for more + information. + interface + The kind of disk interface exposed to the VM for this SSD. + Valid values are scsi and nvme. SCSI is the default and is + supported by more guest operating systems. NVME may provide + higher performance. + size + The size of the local SSD in base-2 GB. + count + The number of local SSD to use per VM. Default value is 1. Manage the time specific properties for requesting future capacity diff --git a/gcloud/alpha/compute/images/create b/gcloud/alpha/compute/images/create index 7bd80ef48..bfd06b592 100644 --- a/gcloud/alpha/compute/images/create +++ b/gcloud/alpha/compute/images/create @@ -152,8 +152,9 @@ OPTIONAL FLAGS their boot disks. See the descriptions of supported features at: https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#guest-os-features. GUEST_OS_FEATURE must be one of: BARE_METAL_LINUX_COMPATIBLE, GVNIC, - MULTI_IP_SUBNET, SEV_CAPABLE, SEV_LIVE_MIGRATABLE, SEV_SNP_CAPABLE, - TDX_CAPABLE, UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, WINDOWS. + IDPF, MULTI_IP_SUBNET, SEV_CAPABLE, SEV_LIVE_MIGRATABLE, + SEV_SNP_CAPABLE, TDX_CAPABLE, UEFI_COMPATIBLE, VIRTIO_SCSI_MULTIQUEUE, + WINDOWS. --key-exchange-key-file=[KEK_VALUE,...] Comma-separated list of file paths that point to X.509 certificates in diff --git a/gcloud/alpha/compute/instance-templates/create b/gcloud/alpha/compute/instance-templates/create index 862ac422d..f5e8b766c 100644 --- a/gcloud/alpha/compute/instance-templates/create +++ b/gcloud/alpha/compute/instance-templates/create @@ -37,6 +37,8 @@ SYNOPSIS [--network=NETWORK] [--network-interface=[PROPERTY=VALUE,...]] [--network-performance-configs=[PROPERTY=VALUE,...]] [--network-tier=NETWORK_TIER] [--numa-node-count=NUMA_NODE_COUNT] + [--partner-metadata=[KEY=VALUE,...]] + [--partner-metadata-from-file=LOCAL_FILE_PATH] [--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT] [--post-key-revocation-action-type=POLICY] [--preemptible] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] @@ -150,12 +152,16 @@ FLAGS Computing can be based on Secure Encrypted Virtualization (SEV) or Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both of which are AMD virtualization features for running confidential - instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + instances. Trust Domain eXtension based on Intel virtualization + features for running confidential instances is also supported. + CONFIDENTIAL_COMPUTE_TYPE must be one of: SEV Secure Encrypted Virtualization SEV_SNP Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension --configure-disk=[PROPERTY=VALUE,...] This option has effect only when used with --source-instance. It allows @@ -716,6 +722,14 @@ FLAGS 1, 2, 4 or 8. Setting NUMA node count to 0 means using the default setting. + --partner-metadata=[KEY=VALUE,...] + Partner Metadata assigned to the instance. A map from a + subdomain(namespace) to entries map. + + --partner-metadata-from-file=LOCAL_FILE_PATH + path to json local file which including the definintion of partner + metadata. + --performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT The set of performance measurement counters to enable for the instance. PERFORMANCE_MONITORING_UNIT must be one of: diff --git a/gcloud/alpha/compute/instance-templates/describe b/gcloud/alpha/compute/instance-templates/describe index 7a368ca5c..fb4d4831c 100644 --- a/gcloud/alpha/compute/instance-templates/describe +++ b/gcloud/alpha/compute/instance-templates/describe @@ -3,7 +3,7 @@ NAME machine instance template SYNOPSIS - gcloud alpha compute instance-templates describe NAME + gcloud alpha compute instance-templates describe NAME [--view=VIEW] [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -20,6 +20,15 @@ POSITIONAL ARGUMENTS Name of the instance template to describe. FLAGS + --view=VIEW + specify Instance view. VIEW must be one of: + + BASIC + Default view of instance, Including everything except Partner + Metadata. + FULL + Include everything in instance + At most one of these can be specified: --global diff --git a/gcloud/alpha/compute/instances/bulk/create b/gcloud/alpha/compute/instances/bulk/create index 727ee9e5d..17ac92254 100644 --- a/gcloud/alpha/compute/instances/bulk/create +++ b/gcloud/alpha/compute/instances/bulk/create @@ -194,12 +194,16 @@ OPTIONAL FLAGS Computing can be based on Secure Encrypted Virtualization (SEV) or Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both of which are AMD virtualization features for running confidential - instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + instances. Trust Domain eXtension based on Intel virtualization + features for running confidential instances is also supported. + CONFIDENTIAL_COMPUTE_TYPE must be one of: SEV Secure Encrypted Virtualization SEV_SNP Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension --count=COUNT Number of Compute Engine virtual machines to create. If specified, and diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 4bc2c4d81..c96e8c3dd 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -43,6 +43,8 @@ SYNOPSIS [--network-performance-configs=[PROPERTY=VALUE,...]] [--network-tier=NETWORK_TIER] [--node-project=NODE_PROJECT] [--numa-node-count=NUMA_NODE_COUNT] + [--partner-metadata=[KEY=VALUE,...]] + [--partner-metadata-from-file=LOCAL_FILE_PATH] [--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT] [--post-key-revocation-action-type=POLICY] [--preemptible] [--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE] @@ -207,12 +209,16 @@ FLAGS Computing can be based on Secure Encrypted Virtualization (SEV) or Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both of which are AMD virtualization features for running confidential - instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + instances. Trust Domain eXtension based on Intel virtualization + features for running confidential instances is also supported. + CONFIDENTIAL_COMPUTE_TYPE must be one of: SEV Secure Encrypted Virtualization SEV_SNP Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension --create-disk=[PROPERTY=VALUE,...] Creates and attaches persistent disks to the instances. @@ -756,6 +762,14 @@ FLAGS 1, 2, 4 or 8. Setting NUMA node count to 0 means using the default setting. + --partner-metadata=[KEY=VALUE,...] + Partner Metadata assigned to the instance. A map from a + subdomain(namespace) to entries map. + + --partner-metadata-from-file=LOCAL_FILE_PATH + path to json local file which including the definintion of partner + metadata. + --performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT The set of performance measurement counters to enable for the instance. PERFORMANCE_MONITORING_UNIT must be one of: diff --git a/gcloud/alpha/compute/instances/create-with-container b/gcloud/alpha/compute/instances/create-with-container index f7ee46dd4..9a0ffbff3 100644 --- a/gcloud/alpha/compute/instances/create-with-container +++ b/gcloud/alpha/compute/instances/create-with-container @@ -156,12 +156,16 @@ FLAGS Computing can be based on Secure Encrypted Virtualization (SEV) or Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both of which are AMD virtualization features for running confidential - instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + instances. Trust Domain eXtension based on Intel virtualization + features for running confidential instances is also supported. + CONFIDENTIAL_COMPUTE_TYPE must be one of: SEV Secure Encrypted Virtualization SEV_SNP Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension --container-arg=CONTAINER_ARG Argument to append to container entrypoint or to override container diff --git a/gcloud/alpha/compute/instances/describe b/gcloud/alpha/compute/instances/describe index 8baa54a9f..9c2c2b13c 100644 --- a/gcloud/alpha/compute/instances/describe +++ b/gcloud/alpha/compute/instances/describe @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha compute instances describe INSTANCE_NAME - [--guest-attributes=[GUEST_ATTRIBUTE_KEY,...]] [--zone=ZONE] - [GCLOUD_WIDE_FLAG ...] + [--guest-attributes=[GUEST_ATTRIBUTE_KEY,...]] [--view=VIEW] + [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute instances describe displays all data @@ -37,6 +37,15 @@ FLAGS Instead of instance resource display guest attributes of the instance stored with the given keys. + --view=VIEW + specify Instance view. VIEW must be one of: + + BASIC + Default view of instance, Including everything except Partner + Metadata. + FULL + Include everything in instance + --zone=ZONE Zone of the instance to describe. If not specified, you might be prompted to select a zone (interactive mode only). gcloud attempts to diff --git a/gcloud/alpha/compute/instances/ops-agents/policies/create b/gcloud/alpha/compute/instances/ops-agents/policies/create index 337a73e83..28168bd2b 100644 --- a/gcloud/alpha/compute/instances/ops-agents/policies/create +++ b/gcloud/alpha/compute/instances/ops-agents/policies/create @@ -245,6 +245,7 @@ REQUIRED FLAGS ubuntu 21.04 ubuntu 21.10 ubuntu 22.04 + ubuntu 23.04 windows 10.* windows 6.* diff --git a/gcloud/alpha/compute/instances/ops-agents/policies/update b/gcloud/alpha/compute/instances/ops-agents/policies/update index e3f1477cb..0a39d3975 100644 --- a/gcloud/alpha/compute/instances/ops-agents/policies/update +++ b/gcloud/alpha/compute/instances/ops-agents/policies/update @@ -282,6 +282,7 @@ FLAGS ubuntu 21.04 ubuntu 21.10 ubuntu 22.04 + ubuntu 23.04 windows 10.* windows 6.* diff --git a/gcloud/alpha/compute/instances/update b/gcloud/alpha/compute/instances/update index 798a6c15a..e30074d3d 100644 --- a/gcloud/alpha/compute/instances/update +++ b/gcloud/alpha/compute/instances/update @@ -5,7 +5,9 @@ NAME SYNOPSIS gcloud alpha compute instances update INSTANCE_NAME [--[no-]deletion-protection] [--[no-]enable-display-device] - [--min-cpu-platform=PLATFORM] [--[no-]shielded-integrity-monitoring] + [--min-cpu-platform=PLATFORM] [--partner-metadata=[KEY=VALUE,...]] + [--partner-metadata-from-file=LOCAL_FILE_PATH] + [--[no-]shielded-integrity-monitoring] [--shielded-learn-integrity-policy] [--[no-]shielded-secure-boot] [--[no-]shielded-vtpm] [--update-labels=[KEY=VALUE,...]] [--zone=ZONE] [--clear-labels | --remove-labels=[KEY,...]] @@ -67,6 +69,14 @@ FLAGS You can find more information on-line: https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform + --partner-metadata=[KEY=VALUE,...] + Partner Metadata assigned to the instance. A map from a + subdomain(namespace) to entries map. + + --partner-metadata-from-file=LOCAL_FILE_PATH + path to json local file which including the definintion of partner + metadata. + --[no-]shielded-integrity-monitoring Enables monitoring and attestation of the boot integrity of the instance. The attestation is performed against the integrity policy diff --git a/gcloud/alpha/compute/networks/subnets/update b/gcloud/alpha/compute/networks/subnets/update index e34e1e9e1..12d94979d 100644 --- a/gcloud/alpha/compute/networks/subnets/update +++ b/gcloud/alpha/compute/networks/subnets/update @@ -15,7 +15,8 @@ SYNOPSIS [--logging-metadata=LOGGING_METADATA] [--logging-metadata-fields=[METADATA_FIELD,...]] [--metadata=METADATA] [--region=REGION] [--stack-type=STACK_TYPE] - [--add-secondary-ranges=PROPERTY=VALUE,[...] | --[no-]enable-flow-logs + [--add-secondary-ranges=PROPERTY=VALUE,[...] + | --[no-]allow-cidr-routes-overlap | --[no-]enable-flow-logs | --[no-]enable-private-ip-google-access | --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE | --purpose=PURPOSE | --remove-secondary-ranges=PROPERTY=VALUE,[...] @@ -167,6 +168,11 @@ FLAGS ▸ RANGE_NAME - Name of the secondary range. ▸ RANGE - IP range in CIDR format. + --[no-]allow-cidr-routes-overlap + Allow/disallow this subnetwork's IP address ranges to conflict with + existing static routes. Use --allow-cidr-routes-overlap to enable and + --no-allow-cidr-routes-overlap to disable. + --[no-]enable-flow-logs Enable/disable VPC Flow Logs for this subnet. If the subnet does not support VPC Flow Logs, this flag has no effect. For more information, diff --git a/gcloud/alpha/compute/queued-resources/create b/gcloud/alpha/compute/queued-resources/create index 18f0e8ced..b8c2fa3ca 100644 --- a/gcloud/alpha/compute/queued-resources/create +++ b/gcloud/alpha/compute/queued-resources/create @@ -178,12 +178,16 @@ OPTIONAL FLAGS Computing can be based on Secure Encrypted Virtualization (SEV) or Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP), both of which are AMD virtualization features for running confidential - instances. CONFIDENTIAL_COMPUTE_TYPE must be one of: + instances. Trust Domain eXtension based on Intel virtualization + features for running confidential instances is also supported. + CONFIDENTIAL_COMPUTE_TYPE must be one of: SEV Secure Encrypted Virtualization SEV_SNP Secure Encrypted Virtualization - Secure Nested Paging + TDX + Trust Domain eXtension --count=COUNT Number of Compute Engine virtual machines to create. If specified, and diff --git a/gcloud/alpha/compute/routers/add-bgp-peer b/gcloud/alpha/compute/routers/add-bgp-peer index 128d6fda8..846a2e8cd 100644 --- a/gcloud/alpha/compute/routers/add-bgp-peer +++ b/gcloud/alpha/compute/routers/add-bgp-peer @@ -7,11 +7,14 @@ SYNOPSIS --peer-asn=PEER_ASN --peer-name=PEER_NAME [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] [--advertisement-mode=MODE] [--async] - [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv6] - [--[no-]enabled] [--instance=INSTANCE] [--instance-zone=INSTANCE_ZONE] + [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv4] + [--[no-]enable-ipv6] [--[no-]enabled] [--instance=INSTANCE] + [--instance-zone=INSTANCE_ZONE] + [--ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] [--peer-ip-address=PEER_IP_ADDRESS] + [--peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS] [--peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] @@ -66,6 +69,12 @@ OPTIONAL FLAGS Google-managed priority value of 100 is used. The routes with the lowest priority value win. + --[no-]enable-ipv4 + If IPv4 is enabled, the peer connection can be established with IPv4 + route exchange. If disabled, no IPv4 route exchange is allowed on any + active session. By default enabled for IPv4-based BGP sessions. Use + --enable-ipv4 to enable and --no-enable-ipv4 to disable. + --[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 @@ -105,22 +114,37 @@ OPTIONAL FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. + --ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS + If IPv4 route exchange is enabled for IPv6-based BGP, the IPv4 next hop + address of the Cloud Router interface for this BGP peer. Ignored + otherwise. Must be a Google owned link-local IPv4 address in the range + 169.254.0.0/16 and must belong to the same subnet as the interface + address of the peer router. + --ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS - The IPv6 next hop address of the Cloud Router interface for this BGP - peer. Must be a Google owned global unicast IPv6 address belonging to - 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. + If IPv6 route exchange is enabled for IPv4-based BGP, the IPv6 next hop + address of the Cloud Router interface for this BGP peer. Ignored + otherwise. Must be a Google owned global unicast IPv6 address belonging + to 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. + The address of the peer router. Must be a link-local IPv4 address in + the the range 169.254.0.0/16 or an ULA IPv6 address in the range + fdff:1::/64. + + --peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS + If IPv4 route exchange is enabled for IPv6-based BGP, the IPv4 next hop + address of the peer router. Ignored otherwise. Must be a Google owned + link-local IPv4 address in the range 169.254.0.0/16. --peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS - The IPv6 next hop address of the peer router. Must be a Google owned + If IPv6 route exchange is enabled for IPv4-based BGP, the IPv6 next hop + address of the peer router. Ignored otherwise. Must be a Google owned global unicast IPv6 address belonging to the range 2600:2d00:0:2:0:0:0:0/64 or 2600:2d00:0:3:0:0:0:0/64. diff --git a/gcloud/alpha/compute/routers/add-interface b/gcloud/alpha/compute/routers/add-interface index e73eaa249..46114ba5f 100644 --- a/gcloud/alpha/compute/routers/add-interface +++ b/gcloud/alpha/compute/routers/add-interface @@ -9,9 +9,9 @@ SYNOPSIS --interconnect-attachment-region=INTERCONNECT_ATTACHMENT_REGION | --subnetwork=SUBNETWORK --subnetwork-region=SUBNETWORK_REGION | --vpn-tunnel=VPN_TUNNEL --vpn-tunnel-region=VPN_TUNNEL_REGION) - [--ip-address=IP_ADDRESS] [--mask-length=MASK_LENGTH] - [--redundant-interface=REDUNDANT_INTERFACE] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + [--ip-address=IP_ADDRESS] [--ip-version=IP_VERSION] + [--mask-length=MASK_LENGTH] [--redundant-interface=REDUNDANT_INTERFACE] + [--region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute routers add-interface is used to add an @@ -59,12 +59,22 @@ REQUIRED FLAGS OPTIONAL FLAGS --ip-address=IP_ADDRESS - The link local address of the router for this interface. + The link local (IPv4) or ULA (IPv6) address of the router for this + interface. + + --ip-version=IP_VERSION + IP version of the interface. Possible values are IPV4 and IPV6. + Defaults to IPV4. IP_VERSION must be one of: + + IPV4 + Interface with IPv4-based BGP. + IPV6 + Interface with IPv6-based BGP. --mask-length=MASK_LENGTH - The subnet mask for the link-local IP range of the interface. The - interface IP address and BGP peer IP address must be selected from the - subnet defined by this link-local range. + The subnet mask for the IP range of the interface. The interface IP + address and BGP peer IP address must be selected from the subnet + defined by this range. --redundant-interface=REDUNDANT_INTERFACE The interface that is redundant to the current interface. diff --git a/gcloud/alpha/compute/routers/create b/gcloud/alpha/compute/routers/create index 1822fa953..06a5c74f6 100644 --- a/gcloud/alpha/compute/routers/create +++ b/gcloud/alpha/compute/routers/create @@ -4,6 +4,7 @@ NAME SYNOPSIS gcloud alpha compute routers create NAME --network=NETWORK [--advertisement-mode=MODE] [--asn=ASN] [--async] + [--bgp-identifier-range=BGP_IDENTIFIER_RANGE] [--description=DESCRIPTION] [--encrypted-interconnect-router] [--keepalive-interval=KEEPALIVE_INTERVAL] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] @@ -40,6 +41,12 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --bgp-identifier-range=BGP_IDENTIFIER_RANGE + Range of valid BGP Identifiers for this Router. Must be a link-local + IPv4 range from 169.254.0.0/16, of size at least /30, even if the BGP + sessions are over IPv6. It must not overlap with any IPv4 BGP session + ranges. This is commonly called "router ID" by other vendors. + --description=DESCRIPTION An optional description of this router. diff --git a/gcloud/alpha/compute/routers/update b/gcloud/alpha/compute/routers/update index 6ada818d8..b82d5683e 100644 --- a/gcloud/alpha/compute/routers/update +++ b/gcloud/alpha/compute/routers/update @@ -3,8 +3,9 @@ NAME SYNOPSIS gcloud alpha compute routers update NAME [--advertisement-mode=MODE] - [--asn=ASN] [--async] [--keepalive-interval=KEEPALIVE_INTERVAL] - [--region=REGION] [--set-advertisement-groups=[GROUP,...]] + [--asn=ASN] [--async] [--bgp-identifier-range=BGP_IDENTIFIER_RANGE] + [--keepalive-interval=KEEPALIVE_INTERVAL] [--region=REGION] + [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] [--add-advertisement-groups=[GROUP,...] | --add-advertisement-ranges=[CIDR_RANGE=DESC,...] @@ -38,6 +39,12 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --bgp-identifier-range=BGP_IDENTIFIER_RANGE + Range of valid BGP Identifiers for this Router. Must be a link-local + IPv4 range from 169.254.0.0/16, of size at least /30, even if the BGP + sessions are over IPv6. It must not overlap with any IPv4 BGP session + ranges. This is commonly called "router ID" by other vendors. + --keepalive-interval=KEEPALIVE_INTERVAL The interval between BGP keepalive messages that are sent to the peer. If set, this value must be between 20 and 60 seconds. The default is 20 diff --git a/gcloud/alpha/compute/routers/update-bgp-peer b/gcloud/alpha/compute/routers/update-bgp-peer index f0f77991a..5e3d7987c 100644 --- a/gcloud/alpha/compute/routers/update-bgp-peer +++ b/gcloud/alpha/compute/routers/update-bgp-peer @@ -6,11 +6,13 @@ SYNOPSIS gcloud alpha compute routers update-bgp-peer NAME --peer-name=PEER_NAME [--advertised-route-priority=ADVERTISED_ROUTE_PRIORITY] [--advertisement-mode=MODE] [--async] [--clear-md5-authentication-key] - [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv6] - [--[no-]enabled] [--interface=INTERFACE] [--ip-address=IP_ADDRESS] + [--custom-learned-route-priority=PRIORITY] [--[no-]enable-ipv4] + [--[no-]enable-ipv6] [--[no-]enabled] [--interface=INTERFACE] + [--ip-address=IP_ADDRESS] [--ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS] [--ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS] [--md5-authentication-key=MD5_AUTHENTICATION_KEY] [--peer-asn=PEER_ASN] [--peer-ip-address=PEER_IP_ADDRESS] + [--peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS] [--peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS] [--region=REGION] [--set-advertisement-groups=[GROUP,...]] [--set-advertisement-ranges=[CIDR_RANGE=DESC,...]] @@ -67,6 +69,12 @@ OPTIONAL FLAGS Google-managed priority value of 100 is used. The routes with the lowest priority value win. + --[no-]enable-ipv4 + If IPv4 is enabled, the peer connection can be established with IPv4 + route exchange. If disabled, no IPv4 route exchange is allowed on any + active session. Use --enable-ipv4 to enable and --no-enable-ipv4 to + disable. + --[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 @@ -83,16 +91,24 @@ OPTIONAL FLAGS The name of the interface for this BGP peer. --ip-address=IP_ADDRESS - The link-local address of the Cloud Router interface for this BGP peer. - Must be a link-local IPv4 address belonging to the range 169.254.0.0/16 - and must belong to same subnet as the interface address of the peer - router. + The address of the Cloud Router interface for this BGP peer. Must be a + link-local IPv4 address in the range 169.254.0.0/16 or an ULA IPv6 + address in the range fdff:1::/64. It must also be in the same subnet as + the interface address of the peer router. + + --ipv4-nexthop-address=IPV4_NEXTHOP_ADDRESS + If IPv4 route exchange is enabled for IPv6-based BGP, the IPv4 next hop + address of the Cloud Router interface for this BGP peer. Ignored + otherwise. Must be a Google owned link-local IPv4 address in the range + 169.254.0.0/16 and must belong to the same subnet as the interface + address of the peer router. --ipv6-nexthop-address=IPV6_NEXTHOP_ADDRESS - The IPv6 next hop address of the Cloud Router interface for this BGP - peer. Must be a Google owned global unicast IPv6 address belonging to - 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. + If IPv6 route exchange is enabled for IPv4-based BGP, the IPv6 next hop + address of the Cloud Router interface for this BGP peer. Ignored + otherwise. Must be a Google owned global unicast IPv6 address belonging + to 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 @@ -104,11 +120,18 @@ OPTIONAL FLAGS https://tools.ietf.org/html/rfc6996, for example --asn=64512. --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. + The address of the peer router. Must be a link-local IPv4 address in + the the range 169.254.0.0/16 or an ULA IPv6 address in the range + fdff:1::/64. + + --peer-ipv4-nexthop-address=PEER_IPV4_NEXTHOP_ADDRESS + If IPv4 route exchange is enabled for IPv6-based BGP, the IPv4 next hop + address of the peer router. Ignored otherwise. Must be a Google owned + link-local IPv4 address in the range 169.254.0.0/16. --peer-ipv6-nexthop-address=PEER_IPV6_NEXTHOP_ADDRESS - The IPv6 next hop address of the peer router. Must be a Google owned + If IPv6 route exchange is enabled for IPv4-based BGP, the IPv6 next hop + address of the peer router. Ignored otherwise. Must be a Google owned global unicast IPv6 address belonging to the range 2600:2d00:0:2:0:0:0:0/64 or 2600:2d00:0:3:0:0:0:0/64. diff --git a/gcloud/alpha/compute/routers/update-interface b/gcloud/alpha/compute/routers/update-interface index 66cc5517f..67b7fcbf8 100644 --- a/gcloud/alpha/compute/routers/update-interface +++ b/gcloud/alpha/compute/routers/update-interface @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha compute routers update-interface NAME --interface-name=INTERFACE_NAME [--ip-address=IP_ADDRESS] - [--mask-length=MASK_LENGTH] [--region=REGION] + [--ip-version=IP_VERSION] [--mask-length=MASK_LENGTH] [--region=REGION] [--interconnect-attachment=INTERCONNECT_ATTACHMENT | --interconnect-attachment-region=INTERCONNECT_ATTACHMENT_REGION | --vpn-tunnel=VPN_TUNNEL | --vpn-tunnel-region=VPN_TUNNEL_REGION] @@ -25,12 +25,22 @@ REQUIRED FLAGS OPTIONAL FLAGS --ip-address=IP_ADDRESS - The link local address of the router for this interface. + The link local (IPv4) or ULA (IPv6) address of the router for this + interface. + + --ip-version=IP_VERSION + IP version of the interface. Possible values are IPV4 and IPV6. + Defaults to IPV4. IP_VERSION must be one of: + + IPV4 + Interface with IPv4-based BGP. + IPV6 + Interface with IPv6-based BGP. --mask-length=MASK_LENGTH - The subnet mask for the link-local IP range of the interface. The - interface IP address and BGP peer IP address must be selected from the - subnet defined by this link-local range. + The subnet mask for the IP range of the interface. The interface IP + address and BGP peer IP address must be selected from the subnet + defined by this range. --region=REGION Region of the router to update. If not specified, you might be prompted diff --git a/gcloud/alpha/compute/tpus/tpu-vm/update b/gcloud/alpha/compute/tpus/tpu-vm/update index 3f825b532..40345e255 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/update +++ b/gcloud/alpha/compute/tpus/tpu-vm/update @@ -3,9 +3,13 @@ NAME SYNOPSIS gcloud alpha compute tpus tpu-vm update (TPU : --zone=ZONE) - [--add-tags=[TAGS,...]] [--async] [--update-labels=[KEY=VALUE,...]] + [--add-tags=[TAGS,...]] [--async] [--description=DESCRIPTION] + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] - [--clear-tags | --remove-tags=[TAG,...]] [GCLOUD_WIDE_FLAG ...] + [--clear-tags | --remove-tags=[TAG,...]] + [--metadata-from-file=[METADATA_FROM_FILE,...] + | --update-metadata=[KEY=VALUE,...] --clear-metadata + | --remove-metadata=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a Cloud TPU VM node. @@ -75,6 +79,9 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --description=DESCRIPTION + Text description of the TPU. + --update-labels=[KEY=VALUE,...] Resource labels to update that represent user-provided metadata. If a label exists, its value is modified. Otherwise, a new label is created. @@ -122,6 +129,38 @@ FLAGS ignored. If --add-tags is also specified then --add-tags is applied first. + At most one of these can be specified: + + --metadata-from-file=[METADATA_FROM_FILE,...] + Same as --metadata except the value for the entry will be read from a + local file. Example: --metadata-from-file='key1=value1.txt' + + --update-metadata=[KEY=VALUE,...] + List of comma-separated metadata key-value pairs for the Cloud TPU VM + node. If a key exists, its value is modified. Otherwise, a new + key-value pair is created. + + At most one of these can be specified: + + --clear-metadata + Remove all metadata. If --update-metadata is also specified then + --clear-metadata is applied first. + + For example, to remove all metadata: + + $ gcloud alpha compute tpus tpu-vm update --clear-metadata + + To remove all existing metadata and create two new metadata + key-value pairs, 'foo=bar' and 'baz=qux': + + $ gcloud alpha compute tpus tpu-vm update --clear-metadata \ + --update-metadata foo=bar,baz=qux + + --remove-metadata=[KEY,...] + List of comma-separated metadata keys to remove. If a key does not + exist it is silently ignored. If --update-metadata is also + specified then --update-metadata is applied first. + 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/backup-restore/restore-plans/create b/gcloud/alpha/container/backup-restore/restore-plans/create index 925991e00..f38d472f9 100644 --- a/gcloud/alpha/container/backup-restore/restore-plans/create +++ b/gcloud/alpha/container/backup-restore/restore-plans/create @@ -7,14 +7,18 @@ SYNOPSIS (RESTORE_PLAN : --location=LOCATION) --backup-plan=BACKUP_PLAN --cluster=CLUSTER --namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE - (--all-namespaces | --selected-applications=SELECTED_APPLICATIONS + (--all-namespaces | --excluded-namespaces=[EXCLUDED_NAMESPACES,...] + | --no-namespaces | --selected-applications=SELECTED_APPLICATIONS | --selected-namespaces=[SELECTED_NAMESPACES,...]) [--async] + [--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--substitution-rules-file=SUBSTITUTION_RULES_FILE] [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; default="no-volume-data-restoration"] - [--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY - --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE, + [--cluster-resource-scope-all-group-kinds + | --cluster-resource-scope-excluded-group-kinds=[CLUSTER_RESOURCE_SCOPE_EXCLUDED_GROUP_KINDS, + ...] | --cluster-resource-scope-no-group-kinds + | --cluster-resource-scope-selected-group-kinds=[CLUSTER_RESOURCE_SCOPE_SELECTED_GROUP_KINDS, ...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -110,11 +114,20 @@ REQUIRED FLAGS out of band process creates conflicting resources), a conflict will be reported. + The scope of namespaced resources to restore. + Exactly one of these must be specified: --all-namespaces If true, restore all namespaced resources in the backup. + --excluded-namespaces=[EXCLUDED_NAMESPACES,...] + List of selected namespaces to skip. All namespaced resources in all + namespaces excluding selected namespaces are restored. + + --no-namespaces + If true, do not restore any namespaced resources in the backup. + --selected-applications=SELECTED_APPLICATIONS List of selected applications to restore. Only those namespaced resources which belong to one of the selected applications are @@ -129,6 +142,24 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY + Define how to handle restore-time conflicts for cluster-scoped + resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: + + use-backup-version + Selecting 'use-existing-version' means deleting the existing + version of the conflicting resources before re-creating them from + the Backup. + + Note that this is a dangerous option which could cause + unintentional data loss if used inappropriately. For example, + deleting a CRD will cause Kubernetes to delete all CRs of that + type. + + use-existing-version + Selecting 'use-existing-version' means no conflicting resources + will be restored. + --description=DESCRIPTION The description of the restore plan. @@ -166,29 +197,29 @@ OPTIONAL FLAGS pre-provisioned using the volume handle of the original PV in the Backup. - --cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY - Define how to handle restore-time conflicts for cluster-scoped - resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: + The scope of cluster-scoped resources to restore. - use-backup-version - Selecting 'use-existing-version' means deleting the existing - version of the conflicting resources before re-creating them from - the Backup. + At most one of these can be specified: - Note that this is a dangerous option which could cause - unintentional data loss if used inappropriately. For example, - deleting a CRD will cause Kubernetes to delete all CRs of that - type. + --cluster-resource-scope-all-group-kinds + If true, all valid cluster-scoped resources will be restored. - use-existing-version - Selecting 'use-existing-version' means no conflicting resources - will be restored. + --cluster-resource-scope-excluded-group-kinds=[CLUSTER_RESOURCE_SCOPE_EXCLUDED_GROUP_KINDS,...] + List of cluster-scoped resource group kinds to NOT restore from the + backup. If specified, all valid cluster-scoped resources will be + restored except for those specified in the list. The format of a + resource is "/", e.g. storage.k8s.io/StorageClass for + StorageClass. Use an empty string for core API group. - --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE,...] - List of cluster-scoped resource types to be restored. Not specifying - this means NO cluster resource will be restored. The format of a - resource is "/", e.g. storage.k8s.io/StorageClass for - StorageClass. Use an empty string for core API group. + --cluster-resource-scope-no-group-kinds + If true, no cluster-scoped resources will be restored. + + --cluster-resource-scope-selected-group-kinds=[CLUSTER_RESOURCE_SCOPE_SELECTED_GROUP_KINDS,...] + List of cluster-scoped resource group kinds to restore from the + backup. If specified, only the selected resources will be restored. + The format of a resource is "/", e.g. + storage.k8s.io/StorageClass for StorageClass. Use an empty string for + core API group. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/backup-restore/restore-plans/update b/gcloud/alpha/container/backup-restore/restore-plans/update index 6e5060c04..c496480a4 100644 --- a/gcloud/alpha/container/backup-restore/restore-plans/update +++ b/gcloud/alpha/container/backup-restore/restore-plans/update @@ -5,17 +5,21 @@ NAME SYNOPSIS gcloud alpha container backup-restore restore-plans update (RESTORE_PLAN : --location=LOCATION) [--async] + [--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY] [--description=DESCRIPTION] [--etag=ETAG] [--namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE] [--substitution-rules-file=SUBSTITUTION_RULES_FILE] [--update-labels=[KEY=VALUE,...]] [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; default="no-volume-data-restoration"] - [--all-namespaces | --selected-applications=SELECTED_APPLICATIONS + [--all-namespaces | --excluded-namespaces=[EXCLUDED_NAMESPACES,...] + | --no-namespaces | --selected-applications=SELECTED_APPLICATIONS | --selected-namespaces=[SELECTED_NAMESPACES,...]] [--clear-labels | --remove-labels=[KEY,...]] - [--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY - --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE, + [--cluster-resource-scope-all-group-kinds + | --cluster-resource-scope-excluded-group-kinds=[CLUSTER_RESOURCE_SCOPE_EXCLUDED_GROUP_KINDS, + ...] | --cluster-resource-scope-no-group-kinds + | --cluster-resource-scope-selected-group-kinds=[CLUSTER_RESOURCE_SCOPE_SELECTED_GROUP_KINDS, ...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -71,6 +75,24 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY + Define how to handle restore-time conflicts for cluster-scoped + resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: + + use-backup-version + Selecting 'use-existing-version' means deleting the existing + version of the conflicting resources before re-creating them from + the Backup. + + Note that this is a dangerous option which could cause + unintentional data loss if used inappropriately. For example, + deleting a CRD will cause Kubernetes to delete all CRs of that + type. + + use-existing-version + Selecting 'use-existing-version' means no conflicting resources + will be restored. + --description=DESCRIPTION The description of the restore plan. @@ -136,11 +158,20 @@ FLAGS pre-provisioned using the volume handle of the original PV in the Backup. + The scope of namespaced resources to restore. + At most one of these can be specified: --all-namespaces If true, restore all namespaced resources in the backup. + --excluded-namespaces=[EXCLUDED_NAMESPACES,...] + List of selected namespaces to skip. All namespaced resources in all + namespaces excluding selected namespaces are restored. + + --no-namespaces + If true, do not restore any namespaced resources in the backup. + --selected-applications=SELECTED_APPLICATIONS List of selected applications to restore. Only those namespaced resources which belong to one of the selected applications are @@ -171,29 +202,29 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. - --cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY - Define how to handle restore-time conflicts for cluster-scoped - resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: + The scope of cluster-scoped resources to restore. - use-backup-version - Selecting 'use-existing-version' means deleting the existing - version of the conflicting resources before re-creating them from - the Backup. + At most one of these can be specified: - Note that this is a dangerous option which could cause - unintentional data loss if used inappropriately. For example, - deleting a CRD will cause Kubernetes to delete all CRs of that - type. + --cluster-resource-scope-all-group-kinds + If true, all valid cluster-scoped resources will be restored. - use-existing-version - Selecting 'use-existing-version' means no conflicting resources - will be restored. + --cluster-resource-scope-excluded-group-kinds=[CLUSTER_RESOURCE_SCOPE_EXCLUDED_GROUP_KINDS,...] + List of cluster-scoped resource group kinds to NOT restore from the + backup. If specified, all valid cluster-scoped resources will be + restored except for those specified in the list. The format of a + resource is "/", e.g. storage.k8s.io/StorageClass for + StorageClass. Use an empty string for core API group. - --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE,...] - List of cluster-scoped resource types to be restored. Not specifying - this means NO cluster resource will be restored. The format of a - resource is "/", e.g. storage.k8s.io/StorageClass for - StorageClass. Use an empty string for core API group. + --cluster-resource-scope-no-group-kinds + If true, no cluster-scoped resources will be restored. + + --cluster-resource-scope-selected-group-kinds=[CLUSTER_RESOURCE_SCOPE_SELECTED_GROUP_KINDS,...] + List of cluster-scoped resource group kinds to restore from the + backup. If specified, only the selected resources will be restored. + The format of a resource is "/", e.g. + storage.k8s.io/StorageClass for StorageClass. Use an empty string for + core API group. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 852a3d2c2..15578f111 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -190,7 +190,7 @@ FLAGS ADDON must be one of: HttpLoadBalancing, HorizontalPodAutoscaling, KubernetesDashboard, NetworkPolicy, NodeLocalDNS, ConfigConnector, GcePersistentDiskCsiDriver, GcpFilestoreCsiDriver, BackupRestore, - Istio, GcsFuseCsiDriver, CloudBuild, CloudRun. + GcsFuseCsiDriver, Istio, CloudBuild, CloudRun. --allow-route-overlap Allows the provided cluster CIDRs to overlap with existing routes that @@ -1273,6 +1273,8 @@ FLAGS Selects Cloud DNS as the DNS provider for the cluster. default Selects the default DNS provider (kube-dns) for the cluster. + kubedns + Selects Kube DNS as the DNS provider for the cluster. --cluster-dns-domain=CLUSTER_DNS_DOMAIN DNS domain for this cluster. The default value is cluster.local. This diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index f6e94b147..e85bed33e 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -866,6 +866,8 @@ REQUIRED FLAGS Selects Cloud DNS as the DNS provider for the cluster. default Selects the default DNS provider (kube-dns) for the cluster. + kubedns + Selects Kube DNS as the DNS provider for the cluster. --cluster-dns-domain=CLUSTER_DNS_DOMAIN DNS domain for this cluster. The default value is cluster.local. diff --git a/gcloud/alpha/container/fleet/memberships/register b/gcloud/alpha/container/fleet/memberships/register index 34b4d203f..c6cac2330 100644 --- a/gcloud/alpha/container/fleet/memberships/register +++ b/gcloud/alpha/container/fleet/memberships/register @@ -28,6 +28,8 @@ DESCRIPTION To register a GKE cluster, use --gke-cluster or --gke-uri flag (no --kubeconfig flag is required). Connect agent will not be installed by default for GKE clusters. To install it, specify --install-connect-agent. + The default value for --location is the same as the cluster's region or + zone, can be specified as global. Anthos clusters on VMware, bare metal, AWS, and Azure are registered with a fleet when the clusters are created. To register Amazon EKS clusters, see @@ -77,7 +79,7 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json Register a non-GKE cluster and output a manifest that can be used to - install the Connect agent: + install the Connect agent by kubectl: $ gcloud alpha container fleet memberships register my-cluster \ --context=my-cluster-context \ @@ -96,6 +98,14 @@ EXAMPLES --gke-uri=my-cluster-gke-uri --install-connect-agent \ --service-account-key-file=/tmp/keyfile.json + Register a GKE cluster and output a manifest that can be used to install + the Connect agent by kubectl: + + $ gcloud alpha container fleet memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri --enable-workload-identity \ + --install-connect-agent \ + --manifest-output-file=/tmp/manifest.yaml + Register a GKE cluster first, and install the Connect agent later. $ gcloud alpha container fleet memberships register my-cluster \ diff --git a/gcloud/alpha/container/hub/memberships/register b/gcloud/alpha/container/hub/memberships/register index c9ba9e0c7..a76c1603f 100644 --- a/gcloud/alpha/container/hub/memberships/register +++ b/gcloud/alpha/container/hub/memberships/register @@ -28,6 +28,8 @@ DESCRIPTION To register a GKE cluster, use --gke-cluster or --gke-uri flag (no --kubeconfig flag is required). Connect agent will not be installed by default for GKE clusters. To install it, specify --install-connect-agent. + The default value for --location is the same as the cluster's region or + zone, can be specified as global. Anthos clusters on VMware, bare metal, AWS, and Azure are registered with a fleet when the clusters are created. To register Amazon EKS clusters, see @@ -77,7 +79,7 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json Register a non-GKE cluster and output a manifest that can be used to - install the Connect agent: + install the Connect agent by kubectl: $ gcloud alpha container hub memberships register my-cluster \ --context=my-cluster-context \ @@ -96,6 +98,14 @@ EXAMPLES --gke-uri=my-cluster-gke-uri --install-connect-agent \ --service-account-key-file=/tmp/keyfile.json + Register a GKE cluster and output a manifest that can be used to install + the Connect agent by kubectl: + + $ gcloud alpha container hub memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri --enable-workload-identity \ + --install-connect-agent \ + --manifest-output-file=/tmp/manifest.yaml + Register a GKE cluster first, and install the Connect agent later. $ gcloud alpha container hub memberships register my-cluster \ diff --git a/gcloud/alpha/functions/help b/gcloud/alpha/functions/help index 32c0942f1..5294f3832 100644 --- a/gcloud/alpha/functions/help +++ b/gcloud/alpha/functions/help @@ -19,6 +19,9 @@ GROUPS (ALPHA) List types of events that can be a trigger for a Google Cloud Function. + local + (ALPHA) Manage local instances of Google Cloud Functions. + logs (ALPHA) Display log entries produced by Google Cloud Functions. diff --git a/gcloud/alpha/functions/local/call b/gcloud/alpha/functions/local/call new file mode 100644 index 000000000..57dc69610 --- /dev/null +++ b/gcloud/alpha/functions/local/call @@ -0,0 +1,46 @@ +NAME + gcloud alpha functions local call - call a locally deployed Google Cloud + Function + +SYNOPSIS + gcloud alpha functions local call NAME + [--cloud-event=CLOUD_EVENT | --data=DATA] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha functions local call Call a locally deployed Google + Cloud Function. + +POSITIONAL ARGUMENTS + NAME + Name of the locally deployed Google Cloud function. + +FLAGS + At most one of these can be specified: + + --cloud-event=CLOUD_EVENT + JSON encoded string with a CloudEvent in structured content mode. + + Mutually exclusive with --data flag. + + Use for Cloud Functions 2nd Gen CloudEvent functions. The CloudEvent + object will be sent to your function as a binary content mode message + with the top-level 'data' field set as the HTTP body and all other + JSON fields sent as HTTP headers. + + --data=DATA + JSON string with data that will be passed to the function. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/functions/local/delete b/gcloud/alpha/functions/local/delete new file mode 100644 index 000000000..57b66f9a2 --- /dev/null +++ b/gcloud/alpha/functions/local/delete @@ -0,0 +1,29 @@ +NAME + gcloud alpha functions local delete - delete a locally deployed Google + Cloud Function + +SYNOPSIS + gcloud alpha functions local delete NAME [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha functions local delete Delete a locally deployed + Google Cloud Function. + +POSITIONAL ARGUMENTS + NAME + Name of the locally deployed Google Cloud function. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/functions/local/deploy b/gcloud/alpha/functions/local/deploy new file mode 100644 index 000000000..691dead84 --- /dev/null +++ b/gcloud/alpha/functions/local/deploy @@ -0,0 +1,54 @@ +NAME + gcloud alpha functions local deploy - deploy a Google Cloud Function + locally + +SYNOPSIS + gcloud alpha functions local deploy NAME [--builder=BUILDER] + [--entry-point=ENTRY_POINT] [--port=PORT; default=8080] + [--runtime=RUNTIME] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha functions local deploy Deploy a Google Cloud Function + locally. + +POSITIONAL ARGUMENTS + NAME + Name of the locally deployed Google Cloud function. + +FLAGS + --builder=BUILDER + Name of the builder to use for pack, e.g. + gcr.io/gae-runtimes/buildpacks/google-gae-22/go/builder. + + --entry-point=ENTRY_POINT + Name of a Google Cloud Function (as defined in source code) that will + be executed. Defaults to the resource name suffix (ID of the function), + if not specified. + + --port=PORT; default=8080 + Port for the deployment to run on. + + --runtime=RUNTIME + Runtime in which to run the function. + + Required when deploying a new function; optional when updating an + existing function. + + For a list of available runtimes, run gcloud functions runtimes list. + + RUNTIME must be one of: python, go, java, nodejs, php, ruby, dotnet. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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/functions/local/help b/gcloud/alpha/functions/local/help new file mode 100644 index 000000000..d731fea83 --- /dev/null +++ b/gcloud/alpha/functions/local/help @@ -0,0 +1,33 @@ +NAME + gcloud alpha functions local - manage local instances of Google Cloud + Functions + +SYNOPSIS + gcloud alpha functions local COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage local instances of Google Cloud Functions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + call + (ALPHA) Call a locally deployed Google Cloud Function. + + delete + (ALPHA) Delete a locally deployed Google Cloud Function. + + deploy + (ALPHA) Deploy a Google Cloud Function locally. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails 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/healthcare/dicom-stores/create b/gcloud/alpha/healthcare/dicom-stores/create index 9eadddaf0..3fd7e6635 100644 --- a/gcloud/alpha/healthcare/dicom-stores/create +++ b/gcloud/alpha/healthcare/dicom-stores/create @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud alpha healthcare dicom-stores create (DICOM_STORE : --dataset=DATASET --location=LOCATION) - [--pubsub-topic=PUBSUB_TOPIC : --send-for-bulk-import] - [GCLOUD_WIDE_FLAG ...] + [--pubsub-topic=PUBSUB_TOPIC] [--send-for-bulk-import] + [--stream-configs=STREAM_CONFIGS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a Cloud Healthcare API DICOM store. @@ -77,6 +77,13 @@ FLAGS Indicates whether or not to send Cloud Pub/Sub notifications on bulk import. Only supported for DICOM imports. + --stream-configs=STREAM_CONFIGS + The configuration that indicates the BigQuery destinations for + streaming instances of a DICOM store. To specify StreamConfigs, list + all BigQuery destinations into one string separated by comma. (e.g., + --stream-configs + bq://{bigqueryProjectId1}.{bigqueryDatasetId1}.{bigqueryTableId1},bq://{bigqueryProjectId2}.{bigqueryDatasetId2}.{bigqueryTableId2}). + 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/healthcare/dicom-stores/update b/gcloud/alpha/healthcare/dicom-stores/update index 17c14eed2..cddbb140e 100644 --- a/gcloud/alpha/healthcare/dicom-stores/update +++ b/gcloud/alpha/healthcare/dicom-stores/update @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud alpha healthcare dicom-stores update (DICOM_STORE : --dataset=DATASET --location=LOCATION) - [--pubsub-topic=PUBSUB_TOPIC : --send-for-bulk-import] - [GCLOUD_WIDE_FLAG ...] + [--pubsub-topic=PUBSUB_TOPIC] [--send-for-bulk-import] + [--stream-configs=STREAM_CONFIGS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Update a Cloud Healthcare API DICOM store. @@ -71,6 +71,13 @@ FLAGS Indicates whether or not to send Cloud Pub/Sub notifications on bulk import. Only supported for DICOM imports. + --stream-configs=STREAM_CONFIGS + The configuration that indicates the BigQuery destinations for + streaming instances of a DICOM store. To specify StreamConfigs, list + all BigQuery destinations into one string separated by comma. (e.g., + --stream-configs + bq://{bigqueryProjectId1}.{bigqueryDatasetId1}.{bigqueryTableId1},bq://{bigqueryProjectId2}.{bigqueryDatasetId2}.{bigqueryTableId2}). + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/iam/workforce-pools/providers/create-oidc b/gcloud/alpha/iam/workforce-pools/providers/create-oidc index f02350ff2..d28d57c95 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/create-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/create-oidc @@ -6,12 +6,12 @@ SYNOPSIS gcloud alpha iam workforce-pools providers create-oidc (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL) --attribute-mapping=[ATTRIBUTE_MAPPING,...] --client-id=CLIENT_ID - --issuer-uri=ISSUER_URI [--async] - [--attribute-condition=ATTRIBUTE_CONDITION] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] - [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR, - [...]] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] - [GCLOUD_WIDE_FLAG ...] + --issuer-uri=ISSUER_URI + (--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE) [--async] + [--attribute-condition=ATTRIBUTE_CONDITION] + [--client-secret-value=CLIENT_SECRET_VALUE] [--description=DESCRIPTION] + [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new OIDC workforce pool provider. @@ -146,6 +146,42 @@ REQUIRED FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. + This must be specified. + + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR + The behavior for how OIDC Claims are included in the assertion object + used for attribute mapping and attribute condition. + + Use merge-user-info-over-id-token-claims to merge the UserInfo + Endpoint Claims with ID Token Claims, preferring UserInfo Claim + Values for the same Claim Name. Currently this option is only + available for Authorization Code flow. + + Use only-id-token-claims to include only ID token claims. + + WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be one of: + assertion-claims-behavior-unspecified, + merge-user-info-over-id-token-claims, only-id-token-claims. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE + Response Type to request for in the OIDC Authorization Request for + web sign-in. + + Use code to select the authorization code flow + (https://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth) + + Use id-token to select the implicit flow + (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). + + WEB_SSO_RESPONSE_TYPE must be one of: code, id-token, + response-type-unspecified. + + This flag argument must be specified if any of the other arguments in + this group are specified. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to @@ -178,6 +214,10 @@ OPTIONAL FLAGS "'admins' in google.groups" + --client-secret-value=CLIENT_SECRET_VALUE + The OIDC client secret. Required to enable Authorization Code flow for + web sign-in. + --description=DESCRIPTION A description for the workforce pool provider. Cannot exceed 256 characters in length. @@ -192,19 +232,6 @@ OPTIONAL FLAGS A display name for the workforce pool provider. Cannot exceed 32 characters in length. - --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR,[...] - The behavior for how OIDC Claims are included in the assertion object - used for attribute mapping and attribute condition. Use - only-id-token-claims to include only ID token claims. - WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be (only one value is - supported): only-id-token-claims. - - --web-sso-response-type=WEB_SSO_RESPONSE_TYPE - Response Type to request for in the OIDC Authorization Request for web - sign-in. Use id-token to select the implicit flow - (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). - WEB_SSO_RESPONSE_TYPE must be (only one value is supported): id-token. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/iam/workforce-pools/providers/update-oidc b/gcloud/alpha/iam/workforce-pools/providers/update-oidc index 6ad4f0fe4..5ed1b5780 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/update-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/update-oidc @@ -9,8 +9,9 @@ SYNOPSIS [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] [--client-id=CLIENT_ID] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] [--issuer-uri=ISSUER_URI] - [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR, - [...]] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] + [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] + [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] + [--clear-client-secret | --client-secret-value=CLIENT_SECRET_VALUE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -191,18 +192,34 @@ FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. - --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR,[...] + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR The behavior for how OIDC Claims are included in the assertion object used for attribute mapping and attribute condition. Use - only-id-token-claims to include only ID token claims. - WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be (only one value is - supported): only-id-token-claims. + merge-user-info-over-id-token-claims to merge the UserInfo Endpoint + Claims with ID Token Claims, preferring UserInfo Claim Values for the + same Claim Name. Currently this option is only available for + Authorization Code flow. Use only-id-token-claims to include only ID + token claims. WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be one of: + assertion-claims-behavior-unspecified, + merge-user-info-over-id-token-claims, only-id-token-claims. --web-sso-response-type=WEB_SSO_RESPONSE_TYPE Response Type to request for in the OIDC Authorization Request for web - sign-in. Use id-token to select the implicit flow + sign-in. Use code to select the authorization code flow + (https://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth) + Use id-token to select the implicit flow (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). - WEB_SSO_RESPONSE_TYPE must be (only one value is supported): id-token. + WEB_SSO_RESPONSE_TYPE must be one of: code, id-token, + response-type-unspecified. + + At most one of these can be specified: + + --clear-client-secret + Clear the OIDC client secret. + + --client-secret-value=CLIENT_SECRET_VALUE + The OIDC client secret. Required to enable Authorization Code flow + for web sign-in. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/network-security/firewall-endpoint-associations/help b/gcloud/alpha/network-security/firewall-endpoint-associations/help index 29399d142..044b2796e 100644 --- a/gcloud/alpha/network-security/firewall-endpoint-associations/help +++ b/gcloud/alpha/network-security/firewall-endpoint-associations/help @@ -29,6 +29,9 @@ COMMANDS list (ALPHA) List Firewall Plus endpoint associations. + update + (ALPHA) Update a Firewall Plus endpoint association. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/network-security/firewall-endpoint-associations/update b/gcloud/alpha/network-security/firewall-endpoint-associations/update new file mode 100644 index 000000000..c70b7023c --- /dev/null +++ b/gcloud/alpha/network-security/firewall-endpoint-associations/update @@ -0,0 +1,175 @@ +NAME + gcloud alpha network-security firewall-endpoint-associations update - + update a Firewall Plus endpoint association + +SYNOPSIS + gcloud alpha network-security firewall-endpoint-associations update + (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--async] + [--max-wait=MAX_WAIT; default="60m"] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] + [--no-tls-inspection-policy + | [--tls-inspection-policy=TLS_INSPECTION_POLICY + : --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT + --tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a firewall endpoint association. Check the progress of + association update by using gcloud network-security + firewall-endpoint-associations describe. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To update labels k1 and k2, run: + + $ gcloud alpha network-security firewall-endpoint-associations \ + update my-assoc --zone=us-central1-a --project=my-proj \ + --update-labels=k1=v1,k2=v2 + + To remove labels k3 and k4, run: + + $ gcloud alpha network-security firewall-endpoint-associations \ + update my-assoc --zone=us-central1-a --project=my-proj \ + --remove-labels=k3,k4 + + To clear all labels from the firewall endpoint association, run: + + $ gcloud alpha network-security firewall-endpoint-associations \ + update my-assoc --zone=us-central1-a --project=my-proj \ + --clear-labels + +POSITIONAL ARGUMENTS + Firewall endpoint association resource - Firewall Plus. 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 FIREWALL_ENDPOINT_ASSOCIATION on the command + line with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + FIREWALL_ENDPOINT_ASSOCIATION + ID of the firewall endpoint association or fully qualified identifier + for the firewall endpoint association. + + To set the association-name attribute: + ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --zone=ZONE + Zone of the firewall endpoint association. + + To set the zone attribute: + ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command + line with a fully specified name; + ▸ provide the argument --zone on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --max-wait=MAX_WAIT; default="60m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha network-security firewall-endpoint-associations \ + update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha network-security firewall-endpoint-associations \ + update --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + + At most one of these can be specified: + + --no-tls-inspection-policy + Remove TLS inspection policy from this association. + + TLS Inspection Policy resource - Path to TLS Inspection Policy + configuration to use for intercepting TLS-encrypted traffic in this + network. The arguments in this group can be used to specify the + attributes of this resource. + + --tls-inspection-policy=TLS_INSPECTION_POLICY + ID of the TLS Inspection Policy or fully qualified identifier for + the TLS Inspection Policy. + + To set the tls_inspection_policy attribute: + ▫ provide the argument --tls-inspection-policy on the command + line. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --tls-inspection-policy-project=TLS_INSPECTION_POLICY_PROJECT + Project of the TLS Inspection Policy. + + To set the tls-inspection-policy-project attribute: + ▫ provide the argument --tls-inspection-policy on the command + line with a fully specified name; + ▫ provide the argument --tls-inspection-policy-project on the + command line; + ▫ provide the argument --project on the command line; + ▫ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the + command line with a fully specified name. + + --tls-inspection-policy-region=TLS_INSPECTION_POLICY_REGION + Region of the TLS Inspection Policy. NOTE: TLS Inspection Policy + needs to be in the same region as Firewall Plus endpoint resource. + + To set the tls-inspection-policy-region attribute: + ▫ provide the argument --tls-inspection-policy on the command + line with a fully specified name; + ▫ provide the argument --tls-inspection-policy-region on the + command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta network-security firewall-endpoint-associations update + diff --git a/gcloud/alpha/network-services/help b/gcloud/alpha/network-services/help index d5eaff835..23df3e513 100644 --- a/gcloud/alpha/network-services/help +++ b/gcloud/alpha/network-services/help @@ -39,6 +39,9 @@ GROUPS service-bindings (ALPHA) Manage Network Services Bindings. + service-lb-policies + (ALPHA) Manage Network Services ServiceLbPolicies. + tcp-routes (ALPHA) Manage Network Services TcpRoutes. diff --git a/gcloud/alpha/network-services/service-lb-policies/create b/gcloud/alpha/network-services/service-lb-policies/create new file mode 100644 index 000000000..b96939d0f --- /dev/null +++ b/gcloud/alpha/network-services/service-lb-policies/create @@ -0,0 +1,110 @@ +NAME + gcloud alpha network-services service-lb-policies create - create a service + LB policy + +SYNOPSIS + gcloud alpha network-services service-lb-policies create + (SERVICE_LB_POLICY : --location=LOCATION) [--async] + [--auto-capacity-drain] [--description=DESCRIPTION] + [--load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; + default="waterfall-by-region"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new service LB policy with the given name. + +EXAMPLES + Create a service LB policy with the name 'my-service-lb-policy', load + balancing algorithm 'waterfall-by-region', and location 'global'. + + $ gcloud alpha network-services service-lb-policies create \ + my-service-lb-policy \ + --load-balancing-algorithm=waterfall-by-region \ + --location="global" + +POSITIONAL ARGUMENTS + Service lb policy resource - Name of the service LB policy to be created. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument service_lb_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_LB_POLICY + ID of the service lb policy or fully qualified identifier for the + service lb policy. + + To set the service_lb_policy attribute: + ▸ provide the argument service_lb_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument service_lb_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --auto-capacity-drain + If specified, an unhealthy MIG/NEG will be removed from Global load + balancing and traffic routing for the service. A MIG/NEG is considered + to be unhealthy if less than 25% of the instance/endpoints in the + MIG/NEG are healthy. autoCapacityDrain will never drain more than 50% + of the configured MIGs/NEGs of a Backend Service. + + --description=DESCRIPTION + The description for the service LB policy. + + --load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region" + The global load balancing algorithm to be used. + LOAD_BALANCING_ALGORITHM must be one of: + + spray-to-region + Spread the traffic from each client to all the MIGs/NEGs in a + region. + + spray-to-world + Balance traffic across all backends across the world proportionally + based on capacity. + + waterfall-by-region + Direct traffic to the nearest region with endpoints and capacity + before spilling over to other regions. + + waterfall-by-zone + Attempt to keep traffic in a single zone closest to the client, + before spilling over to other zones. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta network-services service-lb-policies create + diff --git a/gcloud/alpha/network-services/service-lb-policies/delete b/gcloud/alpha/network-services/service-lb-policies/delete new file mode 100644 index 000000000..944ea6323 --- /dev/null +++ b/gcloud/alpha/network-services/service-lb-policies/delete @@ -0,0 +1,75 @@ +NAME + gcloud alpha network-services service-lb-policies delete - delete service + LB policy + +SYNOPSIS + gcloud alpha network-services service-lb-policies delete + (SERVICE_LB_POLICY : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete the specified service LB policy. + +EXAMPLES + To delete a service LB policy named my-service-lb-policy, run: + + $ gcloud alpha network-services service-lb-policies delete \ + my-service-lb-policy --location=global + +POSITIONAL ARGUMENTS + Service lb policy resource - Name of the service LB policy you want to + delete. The arguments in this group can be used to specify the attributes + of this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument service_lb_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_LB_POLICY + ID of the service lb policy or fully qualified identifier for the + service lb policy. + + To set the service_lb_policy attribute: + ▸ provide the argument service_lb_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument service_lb_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta network-services service-lb-policies delete + diff --git a/gcloud/alpha/network-services/service-lb-policies/describe b/gcloud/alpha/network-services/service-lb-policies/describe new file mode 100644 index 000000000..a0c8f0fb8 --- /dev/null +++ b/gcloud/alpha/network-services/service-lb-policies/describe @@ -0,0 +1,69 @@ +NAME + gcloud alpha network-services service-lb-policies describe - describe a + service LB policy + +SYNOPSIS + gcloud alpha network-services service-lb-policies describe + (SERVICE_LB_POLICY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show details of a service LB policy. + +EXAMPLES + Show details about a service LB policy named 'my-service-lb-policy'. + + $ gcloud alpha network-services service-lb-policies describe \ + my-service-lb-policy --location=global + +POSITIONAL ARGUMENTS + Service lb policy resource - Name of the service LB policy to be + described. 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 service_lb_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_LB_POLICY + ID of the service lb policy or fully qualified identifier for the + service lb policy. + + To set the service_lb_policy attribute: + ▸ provide the argument service_lb_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument service_lb_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta network-services service-lb-policies describe + diff --git a/gcloud/alpha/network-services/service-lb-policies/export b/gcloud/alpha/network-services/service-lb-policies/export new file mode 100644 index 000000000..d9ff256a9 --- /dev/null +++ b/gcloud/alpha/network-services/service-lb-policies/export @@ -0,0 +1,80 @@ +NAME + gcloud alpha network-services service-lb-policies export - export service + LB policy + +SYNOPSIS + gcloud alpha network-services service-lb-policies export + (SERVICE_LB_POLICY : --location=LOCATION) [--destination=DESTINATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Export a service LB policy. + +EXAMPLES + To export a service LB policy named my-service-lb-policy to a YAML file, + run: + + $ gcloud alpha network-services service-lb-policies export \ + my-service-lb-policy --destination=my-service-lb-policy.yaml \ + --location=global + +POSITIONAL ARGUMENTS + Service lb policy resource - Name of the service LB policy to export. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument service_lb_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_LB_POLICY + ID of the service lb policy or fully qualified identifier for the + service lb policy. + + To set the service_lb_policy attribute: + ▸ provide the argument service_lb_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument service_lb_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. The + exported data will not contain any output-only fields. Alternatively, + you may omit this flag to write to standard output. For a schema + describing the export/import format, see + $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta network-services service-lb-policies export + diff --git a/gcloud/alpha/network-services/service-lb-policies/help b/gcloud/alpha/network-services/service-lb-policies/help new file mode 100644 index 000000000..258ee47a9 --- /dev/null +++ b/gcloud/alpha/network-services/service-lb-policies/help @@ -0,0 +1,48 @@ +NAME + gcloud alpha network-services service-lb-policies - manage Network Services + ServiceLbPolicies + +SYNOPSIS + gcloud alpha network-services service-lb-policies COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Network Services ServiceLbPolicies. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a service LB policy. + + delete + (ALPHA) Delete service LB policy. + + describe + (ALPHA) Describe a service LB policy. + + export + (ALPHA) Export service LB policy. + + import + (ALPHA) Import service LB policy. + + list + (ALPHA) List ServiceLbPolicies. + + update + (ALPHA) Update a service LB policy. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta network-services service-lb-policies + diff --git a/gcloud/alpha/network-services/service-lb-policies/import b/gcloud/alpha/network-services/service-lb-policies/import new file mode 100644 index 000000000..86905f293 --- /dev/null +++ b/gcloud/alpha/network-services/service-lb-policies/import @@ -0,0 +1,87 @@ +NAME + gcloud alpha network-services service-lb-policies import - import service + LB policy + +SYNOPSIS + gcloud alpha network-services service-lb-policies import + (SERVICE_LB_POLICY : --location=LOCATION) [--async] [--source=SOURCE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Import a service LB policy. + +EXAMPLES + To import a service LB policy named my-service-lb-policy from a YAML file, + run: + + $ gcloud alpha network-services service-lb-policies import \ + my-service-lb-policy --source=my-service-lb-policy.yaml \ + --location=global + +POSITIONAL ARGUMENTS + Service lb policy resource - Name of the service LB policy to import. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument service_lb_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_LB_POLICY + ID of the service lb policy or fully qualified identifier for the + service lb policy. + + To set the service_lb_policy attribute: + ▸ provide the argument service_lb_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument service_lb_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --source=SOURCE + Path to a YAML file containing the configuration export data. The YAML + file must not contain any output-only fields. Alternatively, you may + omit this flag to read from standard input. For a schema describing the + export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + + $CLOUDSDKROOT is can be obtained with the following command: + + $ gcloud info --format='value(installation.sdk_root)' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta network-services service-lb-policies import + diff --git a/gcloud/alpha/network-services/service-lb-policies/list b/gcloud/alpha/network-services/service-lb-policies/list new file mode 100644 index 000000000..fa77580f2 --- /dev/null +++ b/gcloud/alpha/network-services/service-lb-policies/list @@ -0,0 +1,90 @@ +NAME + gcloud alpha network-services service-lb-policies list - list + ServiceLbPolicies + +SYNOPSIS + gcloud alpha network-services service-lb-policies list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all ServiceLbPolicies in the specified location of the current + project. + +EXAMPLES + To list service lb policies in the current project, run: + + $ gcloud alpha network-services service-lb-policies list \ + --location=global + +REQUIRED FLAGS + Location resource - The project of the service LB policies to display. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta network-services service-lb-policies list + diff --git a/gcloud/alpha/network-services/service-lb-policies/update b/gcloud/alpha/network-services/service-lb-policies/update new file mode 100644 index 000000000..620b985b7 --- /dev/null +++ b/gcloud/alpha/network-services/service-lb-policies/update @@ -0,0 +1,109 @@ +NAME + gcloud alpha network-services service-lb-policies update - update a service + LB policy + +SYNOPSIS + gcloud alpha network-services service-lb-policies update + (SERVICE_LB_POLICY : --location=LOCATION) [--async] + [--auto-capacity-drain] [--description=DESCRIPTION] + [--load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; + default="waterfall-by-region"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update the detail of a service LB Policy. + +EXAMPLES + Update load-balancing-algorithm of a service LB policy named + my-service-lb-policy: + + $ gcloud alpha network-services service-lb-policies update \ + my-service-lb-policy \ + --load-balancing-algorithm=waterfall-by-zone + +POSITIONAL ARGUMENTS + Service lb policy resource - Name of the service LB policy to be updated. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument service_lb_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_LB_POLICY + ID of the service lb policy or fully qualified identifier for the + service lb policy. + + To set the service_lb_policy attribute: + ▸ provide the argument service_lb_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument service_lb_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --auto-capacity-drain + If specified, an unhealthy MIG/NEG will be removed from Global load + balancing and traffic routing for the service. A MIG/NEG is considered + to be unhealthy if less than 25% of the instance/endpoints in the + MIG/NEG are healthy. autoCapacityDrain will never drain more than 50% + of the configured MIGs/NEGs of a Backend Service. + + --description=DESCRIPTION + The description for the service LB policy. + + --load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region" + The global load balancing algorithm to be used. + LOAD_BALANCING_ALGORITHM must be one of: + + spray-to-region + Spread the traffic from each client to all the MIGs/NEGs in a + region. + + spray-to-world + Balance traffic across all backends across the world proportionally + based on capacity. + + waterfall-by-region + Direct traffic to the nearest region with endpoints and capacity + before spilling over to other regions. + + waterfall-by-zone + Attempt to keep traffic in a single zone closest to the client, + before spilling over to other zones. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1alpha1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta network-services service-lb-policies update + diff --git a/gcloud/alpha/recaptcha/keys/migrate b/gcloud/alpha/recaptcha/keys/migrate index 3ccc569a3..b384432b3 100644 --- a/gcloud/alpha/recaptcha/keys/migrate +++ b/gcloud/alpha/recaptcha/keys/migrate @@ -2,7 +2,8 @@ NAME gcloud alpha recaptcha keys migrate - migrate a key to reCAPTCHA Enterprise SYNOPSIS - gcloud alpha recaptcha keys migrate KEY [GCLOUD_WIDE_FLAG ...] + gcloud alpha recaptcha keys migrate KEY [--skip-billing-check] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Migrate a key from reCAPTCHA to reCAPTCHA Enterprise. @@ -31,6 +32,11 @@ POSITIONAL ARGUMENTS To set the key attribute: ▸ provide the argument key on the command line. +FLAGS + --skip-billing-check + If true, skips the billing check. If your usage of reCAPTCHA is under + the free quota, you can safely skip the billing check. + 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/recommender/insights/list b/gcloud/alpha/recommender/insights/list index 65fdd9793..5ee88c4c8 100644 --- a/gcloud/alpha/recommender/insights/list +++ b/gcloud/alpha/recommender/insights/list @@ -10,8 +10,8 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command will list all insights for a given cloud entity, - location and insight type. Supported insight-types can be found here: + (ALPHA) This command lists all insights for a given cloud entity, location + and insight type. Supported insight-types can be found here: https://cloud.google.com/recommender/docs/insights/insight-types. Currently the following cloud_entity_types are supported: project, billing_account, folder and organization. diff --git a/gcloud/alpha/recommender/recommendations/list b/gcloud/alpha/recommender/recommendations/list index 1d39e688d..ffb5ac386 100644 --- a/gcloud/alpha/recommender/recommendations/list +++ b/gcloud/alpha/recommender/recommendations/list @@ -11,11 +11,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command will list all recommendations for a given - cloud_entity_id, location and recommender. Supported recommenders can be - found here: https://cloud.google.com/recommender/docs/recommenders. - Currently the following cloud_entity_types are supported: project, - billing_account, folder and organization. + (ALPHA) This command lists all recommendations for a given cloud_entity_id, + location and recommender. Supported recommenders can be found here: + https://cloud.google.com/recommender/docs/recommenders. Currently the + following cloud_entity_types are supported: project, billing_account, + folder and organization. EXAMPLES Lists recommendations for a Cloud project. $ gcloud alpha recommender recommendations list \ diff --git a/gcloud/alpha/redis/instances/update b/gcloud/alpha/redis/instances/update index b86e41208..2bca83b93 100644 --- a/gcloud/alpha/redis/instances/update +++ b/gcloud/alpha/redis/instances/update @@ -175,6 +175,9 @@ FLAGS Redis version 5.0 and newer: stream-node-max-bytes, stream-node-max-entries. + Redis version 7.0 and newer: maxmemory-clients, lazyfree-lazy-eviction, + lazyfree-lazy-expire, lazyfree-lazy-user-del, lazyfree-lazy-user-flush. + At most one of these can be specified: --clear-labels diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index 4689e273c..dddf8a6f0 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -153,8 +153,8 @@ FLAGS Set a memory limit. Ex: 1024Mi, 4Gi. --min-instances=MIN_INSTANCES - The minimum number of container instances of the Service to run or - 'default' to remove any minimum. + The minimum number of container instances for this Revision of the + Service to run or 'default' to remove any minimum. --platform=PLATFORM; default="managed" Target platform for running commands. Alternatively, set the property diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index e4bcbb420..d7ba2cf47 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -147,8 +147,8 @@ FLAGS Set a memory limit. Ex: 1024Mi, 4Gi. --min-instances=MIN_INSTANCES - The minimum number of container instances of the Service to run or - 'default' to remove any minimum. + The minimum number of container instances for this Revision of the + Service to run or 'default' to remove any minimum. --platform=PLATFORM; default="managed" Target platform for running commands. Alternatively, set the property diff --git a/gcloud/alpha/scc/findings/create b/gcloud/alpha/scc/findings/create index b12b2809a..0907461f2 100644 --- a/gcloud/alpha/scc/findings/create +++ b/gcloud/alpha/scc/findings/create @@ -14,31 +14,31 @@ DESCRIPTION (ALPHA) Create a Cloud Security Command Center finding. EXAMPLES - Create an ACTIVE my-finding with category: XSS_SCRIPTING attached to + Create an ACTIVE myFinding with category: XSS_SCRIPTING attached to example-project under organization 123456 and source 5678: - $ gcloud alpha scc findings create my-finding \ + $ gcloud alpha scc findings create `myFinding` \ --organization=123456 --source=5678 --state=ACTIVE \ --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' - Create an ACTIVE my-finding attached to example-project under project + Create an ACTIVE myFinding attached to example-project under project example-project and source 5678: $ gcloud alpha scc findings create \ - projects/example-project/sources/5678/findings/my-finding \ + projects/example-project/sources/5678/findings/myFinding \ --state=ACTIVE --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' - Create an ACTIVE my-finding attached to example-project under folder 456 - and source 5678: + Create an ACTIVE myFinding attached to example-project under folder 456 and + source 5678: $ gcloud alpha scc findings create \ - folders/456/sources/5678/findings/my-finding --state=ACTIVE \ + folders/456/sources/5678/findings/myFinding --state=ACTIVE \ --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ diff --git a/gcloud/alpha/scc/findings/list-marks b/gcloud/alpha/scc/findings/list-marks index 1109c2087..52467d2c6 100644 --- a/gcloud/alpha/scc/findings/list-marks +++ b/gcloud/alpha/scc/findings/list-marks @@ -12,22 +12,22 @@ DESCRIPTION (ALPHA) List a finding's security marks. EXAMPLES - List all security marks for my-finding under organization 123456 and source + List all security marks for myFinding under organization 123456 and source 5678: - $ gcloud alpha scc findings list-marks my-finding \ + $ gcloud alpha scc findings list-marks `myFinding` \ --organization=123456 --source=5678 - List all security marks for my-finding under project example-project and + List all security marks for myFinding under project example-project and source 5678: $ gcloud alpha scc findings list-marks \ - projects/example-project/sources/5678/findings/my-finding + projects/example-project/sources/5678/findings/myFinding - List all security marks for my-finding under folder 456 and source 5678: + List all security marks for myFinding under folder 456 and source 5678: $ gcloud alpha scc findings list-marks \ - folders/456/sources/5678/findings/my-finding + folders/456/sources/5678/findings/myFinding POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command diff --git a/gcloud/alpha/scc/findings/update b/gcloud/alpha/scc/findings/update index cdfc1b16f..41432d401 100644 --- a/gcloud/alpha/scc/findings/update +++ b/gcloud/alpha/scc/findings/update @@ -13,32 +13,32 @@ DESCRIPTION (ALPHA) Update a Cloud Security Command Center finding. EXAMPLES - Update my-finding's state from ACTIVE to INACTIVE: + Update myFinding's state from ACTIVE to INACTIVE: - $ gcloud alpha scc findings update my-finding \ + $ gcloud alpha scc findings update `myFinding` \ --organization=123456 --source=5678 --state=INACTIVE - Update my-finding's state from ACTIVE to INACTIVE using project name for + Update myFinding's state from ACTIVE to INACTIVE using project name for example-project: $ gcloud alpha scc findings update \ - projects/example-project/sources/5678/findings/my-finding \ + projects/example-project/sources/5678/findings/myFinding \ --state=INACTIVE - Update my-finding's state from ACTIVE to INACTIVE using folder name 456: + Update myFinding's state from ACTIVE to INACTIVE using folder name 456: $ gcloud alpha scc findings update \ - folders/456/sources/5678/findings/my-finding --state=INACTIVE + folders/456/sources/5678/findings/myFinding --state=INACTIVE - Override all source properties on my-finding: + Override all source properties on myFinding: - $ gcloud alpha scc findings update my-finding \ + $ gcloud alpha scc findings update `myFinding` \ --organization=123456 --source=5678 \ --source-properties="propKey1=propVal1,propKey2=propVal2" - Selectively update a specific source property on my-finding: + Selectively update a specific source property on myFinding: - $ gcloud alpha scc findings update my-finding \ + $ gcloud alpha scc findings update `myFinding` \ --organization=123456 --source=5678 \ --source-properties="propKey1=propVal1,propKey2=propVal2" \ --update-mask="source_properties.propKey1" diff --git a/gcloud/alpha/scc/findings/update-marks b/gcloud/alpha/scc/findings/update-marks index f55e8edad..f74e11915 100644 --- a/gcloud/alpha/scc/findings/update-marks +++ b/gcloud/alpha/scc/findings/update-marks @@ -12,36 +12,36 @@ DESCRIPTION (ALPHA) Update Cloud Security Command Center finding's security marks. EXAMPLES - Selectively update security mark (Key1) with value (v1) on my-finding. Note - that other security marks on my-finding are untouched: + Selectively update security mark (Key1) with value (v1) on myFinding. Note + that other security marks on myFinding are untouched: - $ gcloud alpha scc findings update-marks my-finding \ + $ gcloud alpha scc findings update-marks `myFinding` \ --organization=123456 --source=5678 --security-marks="key1=v1" \ --update-mask="marks.markKey1" - Update all security marks on my-finding, under project example-project and + Update all security marks on myFinding, under project example-project and source 5678: $ gcloud alpha scc findings update-marks \ - projects/example-project/sources/5678/findings/my-finding \ + projects/example-project/sources/5678/findings/myFinding \ --security-marks="key1=v1,key2=v2" - Update all security marks on my-finding, under folder 456 and source 5678: + Update all security marks on myFinding, under folder 456 and source 5678: $ gcloud alpha scc findings update-marks \ - folders/456/sources/5678/findings/my-finding \ + folders/456/sources/5678/findings/myFinding \ --security-marks="key1=v1,key2=v2" - Update all security marks on my-finding, under organization 123456 and + Update all security marks on myFinding, under organization 123456 and source 5678: - $ gcloud alpha scc findings update-marks my-finding \ + $ gcloud alpha scc findings update-marks `myFinding` \ --organization=123456 --source=5678 \ --security-marks="key1=v1,key2=v2" - Delete all security marks on my-finding: + Delete all security marks on myFinding: - $ gcloud alpha scc findings update-marks my-finding \ + $ gcloud alpha scc findings update-marks `myFinding` \ --organization=123456 --source=5678 --security-marks="" POSITIONAL ARGUMENTS diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index dfdd7f886..46a18614a 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -20,8 +20,9 @@ SYNOPSIS [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] - [--enable-bin-log] [--enable-google-private-path] - [--enable-password-policy] [--enable-point-in-time-recovery] + [--edition=EDITION] [--enable-bin-log] [--enable-data-cache] + [--enable-google-private-path] [--enable-password-policy] + [--enable-point-in-time-recovery] [--failover-replica-name=FAILOVER_REPLICA_NAME] [--[no-]insights-config-query-insights-enabled] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -35,6 +36,7 @@ SYNOPSIS [--master-instance-name=MASTER_INSTANCE_NAME] [--memory=MEMORY] [--network=NETWORK] [--password-policy-complexity=PASSWORD_POLICY_COMPLEXITY] + [--[no-]password-policy-disallow-compromised-credentials] [--[no-]password-policy-disallow-username-substring] [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] @@ -214,11 +216,19 @@ FLAGS --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME Time when the deny maintenance period starts or ends, that is 05:00:00. + --edition=EDITION + Specifies the edition of Cloud SQL instance. EDITION must be one of: + enterprise, enterprise-plus. + --enable-bin-log Allows for data recovery from a specific point in time, down to a fraction of a second. Must have automatic backups enabled to use. Make sure storage can support at least 7 days of logs. + --enable-data-cache + Enable use of data cache for accelerated read performance. This flag is + only available for Enterprise_Plus edition instances. + --enable-google-private-path Enable a private path for Google Cloud services. This flag specifies whether the instance is accessible to internal Google Cloud services @@ -327,6 +337,11 @@ FLAGS The default value if COMPLEXITY_DEFAULT is not specified. It implies that complexity check is not enabled. + --[no-]password-policy-disallow-compromised-credentials + Disallow credentials that have been compromised by a data breach. Use + --password-policy-disallow-compromised-credentials to enable and + --no-password-policy-disallow-compromised-credentials to disable. + --[no-]password-policy-disallow-username-substring Disallow username as a part of the password. Use --password-policy-disallow-username-substring to enable and @@ -357,16 +372,20 @@ FLAGS Specified if users connecting over IP must use SSL. --retained-backups-count=RETAINED_BACKUPS_COUNT - How many backups to keep. The valid range is between 1 and 365. The - default value is 7 if not specified. Applicable only if --no-backups is - not specified. + How many backups to keep. The valid range is between 1 and 365. Default + value is 7 for Enterprise edition instances. For Enterprise_Plus + Postgres and MySQL instances, default values are 15 and 8 respectively. + Applicable only if --no-backups is not specified. --retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS How many days of transaction logs to keep. The valid range is between 1 - and 35. The default value is 7. The 35 days log retention feature is - only enabled for specific customer. Only use this option when - point-in-time recovery is enabled. Storage size for transaction logs - increases when the number of days for log retention increases. + and 35. Only use this option when point-in-time recovery is enabled. If + logs are stored on disk, storage size for transaction logs could + increase when the number of days for log retention increases. For + Enterprise, default and max retention values are 7 and 7 respectively. + For MySQL Enterprise_Plus, default and max retention values are 7 and + 7. For Postgres Enterprise_Plus, default and max retention values are + 14 and 35. --root-password=ROOT_PASSWORD Root Cloud SQL user's password. diff --git a/gcloud/alpha/sql/instances/list b/gcloud/alpha/sql/instances/list index e8f5e0848..4af9d16ab 100644 --- a/gcloud/alpha/sql/instances/list +++ b/gcloud/alpha/sql/instances/list @@ -3,14 +3,18 @@ NAME project SYNOPSIS - gcloud alpha sql instances list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud alpha sql instances list [--show-edition] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Lists Cloud SQL instances in a given project in the alphabetical order of the instance name. +FLAGS + --show-edition + Show the edition field. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index b9ee154ec..6fc4f9445 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -16,7 +16,8 @@ SYNOPSIS [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--diff] - [--[no-]enable-bin-log] [--[no-]enable-database-replication] + [--edition=EDITION] [--[no-]enable-bin-log] [--enable-data-cache] + [--[no-]enable-database-replication] [--[no-]enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] [--follow-gae-app=FOLLOW_GAE_APP] [--[no-]insights-config-query-insights-enabled] @@ -30,6 +31,7 @@ SYNOPSIS [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [--memory=MEMORY] [--network=NETWORK] [--password-policy-complexity=PASSWORD_POLICY_COMPLEXITY] + [--[no-]password-policy-disallow-compromised-credentials] [--[no-]password-policy-disallow-username-substring] [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] @@ -157,12 +159,20 @@ FLAGS --diff Show what changed as a result of the update. + --edition=EDITION + Specifies the edition of Cloud SQL instance. EDITION must be one of: + enterprise, enterprise-plus. + --[no-]enable-bin-log Allows for data recovery from a specific point in time, down to a fraction of a second. Must have automatic backups enabled to use. Make sure storage can support at least 7 days of logs. Use --enable-bin-log to enable and --no-enable-bin-log to disable. + --enable-data-cache + Enable use of data cache for accelerated read performance. This flag is + only available for Enterprise_Plus edition instances. + --[no-]enable-database-replication Enable database replication. Applicable only for read replica instance(s). WARNING: Instance will be restarted. Use @@ -273,6 +283,11 @@ FLAGS The default value if COMPLEXITY_DEFAULT is not specified. It implies that complexity check is not enabled. + --[no-]password-policy-disallow-compromised-credentials + Disallow credentials that have been compromised by a data breach. Use + --password-policy-disallow-compromised-credentials to enable and + --no-password-policy-disallow-compromised-credentials to disable. + --[no-]password-policy-disallow-username-substring Disallow username as a part of the password. Use --password-policy-disallow-username-substring to enable and @@ -440,16 +455,20 @@ FLAGS UTC timezone. --retained-backups-count=RETAINED_BACKUPS_COUNT - How many backups to keep. The valid range is between 1 and 365. The - default value is 7 if not specified. Applicable only if --no-backups - is not specified. + How many backups to keep. The valid range is between 1 and 365. + Default value is 7 for Enterprise edition instances. For + Enterprise_Plus Postgres and MySQL instances, default values are 15 + and 8 respectively. Applicable only if --no-backups is not specified. --retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS How many days of transaction logs to keep. The valid range is between - 1 and 35. The default value is 7. The 35 days log retention feature - is only enabled for specific customer. Only use this option when - point-in-time recovery is enabled. Storage size for transaction logs - increases when the number of days for log retention increases. + 1 and 35. Only use this option when point-in-time recovery is + enabled. If logs are stored on disk, storage size for transaction + logs could increase when the number of days for log retention + increases. For Enterprise, default and max retention values are 7 and + 7 respectively. For MySQL Enterprise_Plus, default and max retention + values are 7 and 7. For Postgres Enterprise_Plus, default and max + retention values are 14 and 35. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/sql/operations/cancel b/gcloud/alpha/sql/operations/cancel new file mode 100644 index 000000000..1dc610902 --- /dev/null +++ b/gcloud/alpha/sql/operations/cancel @@ -0,0 +1,37 @@ +NAME + gcloud alpha sql operations cancel - cancels a Cloud SQL instance operation + +SYNOPSIS + gcloud alpha sql operations cancel OPERATION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Cancels a Cloud SQL instance operation. + +EXAMPLES + To cancel an operation with the id "prod-operation-id", like + "acb40108-a483-4a8b-8a5c-e27100000032", run: + + $ gcloud alpha sql operations cancel prod-operation-id + +POSITIONAL ARGUMENTS + OPERATION + Name that uniquely identifies the operation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. These variants are also available: + + $ gcloud sql operations cancel + + $ gcloud beta sql operations cancel + diff --git a/gcloud/alpha/sql/operations/help b/gcloud/alpha/sql/operations/help index 4ac962c01..5f7405956 100644 --- a/gcloud/alpha/sql/operations/help +++ b/gcloud/alpha/sql/operations/help @@ -18,6 +18,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + cancel + (ALPHA) Cancels a Cloud SQL instance operation. + describe (ALPHA) Retrieves information about a Cloud SQL instance operation. diff --git a/gcloud/alpha/sql/tiers/list b/gcloud/alpha/sql/tiers/list index 87c63411f..5aaf3879b 100644 --- a/gcloud/alpha/sql/tiers/list +++ b/gcloud/alpha/sql/tiers/list @@ -3,13 +3,17 @@ NAME Cloud SQL SYNOPSIS - gcloud alpha sql tiers list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud alpha sql tiers list [--show-edition] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Lists all available service tiers for Google Cloud SQL. +FLAGS + --show-edition + Show the edition field. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/alpha/storage/cp b/gcloud/alpha/storage/cp index b12054a20..4830955b6 100644 --- a/gcloud/alpha/storage/cp +++ b/gcloud/alpha/storage/cp @@ -220,7 +220,7 @@ FLAGS Content-Encoding metadata is set to gzip and the Cache-Control metadata set to no-transform. The data remains compressed on Cloud Storage servers and will not be decompressed on download by gcloud - stroage because of the no-transform field. + storage because of the no-transform field. Since the local gzip option compresses data prior to upload, it is not subject to the same compression buffer bottleneck of the diff --git a/gcloud/alpha/storage/mv b/gcloud/alpha/storage/mv index 34d673d1f..9df2e52d4 100644 --- a/gcloud/alpha/storage/mv +++ b/gcloud/alpha/storage/mv @@ -227,7 +227,7 @@ FLAGS Content-Encoding metadata is set to gzip and the Cache-Control metadata set to no-transform. The data remains compressed on Cloud Storage servers and will not be decompressed on download by gcloud - stroage because of the no-transform field. + storage because of the no-transform field. Since the local gzip option compresses data prior to upload, it is not subject to the same compression buffer bottleneck of the diff --git a/gcloud/alpha/workstations/clusters/create b/gcloud/alpha/workstations/clusters/create index 64a44c804..15e786666 100644 --- a/gcloud/alpha/workstations/clusters/create +++ b/gcloud/alpha/workstations/clusters/create @@ -69,12 +69,10 @@ FLAGS Compute Engine resources. --network=NETWORK - The network that instances created under the cluster will be associated - with. + Fully specified network path for instances created in this cluster. --subnetwork=SUBNETWORK - The subnetwork that instances created under the cluster will be - associated with. + Fully specified subnetwork path for instances created in this cluster. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/workstations/configs/create b/gcloud/alpha/workstations/configs/create index d8239c13e..fc9ff16a5 100644 --- a/gcloud/alpha/workstations/configs/create +++ b/gcloud/alpha/workstations/configs/create @@ -155,10 +155,7 @@ FLAGS --machine-type=MACHINE_TYPE; default="e2-standard-4" Machine type determines the specifications of the Compute Engine machines that the workstations created under this configuration will - run on. MACHINE_TYPE must be one of: e2-standard-2, e2-standard-4, - e2-standard-8, e2-standard-16, e2-standard-32, n2-standard-8, - n1-standard-4, t2d-standard-6, n2d-standard-2, n2d-standard-4, - n2d-standard-8, n2d-standard-16, n2d-standard-32. + run on. --network-tags=[NETWORK_TAGS,...] Network tags to add to the Google Compute Engine machines backing the diff --git a/gcloud/alpha/workstations/configs/update b/gcloud/alpha/workstations/configs/update index ab183013d..26b77aeca 100644 --- a/gcloud/alpha/workstations/configs/update +++ b/gcloud/alpha/workstations/configs/update @@ -141,10 +141,7 @@ FLAGS --machine-type=MACHINE_TYPE Machine type determines the specifications of the Compute Engine machines that the workstations created under this configuration will - run on. MACHINE_TYPE must be one of: e2-standard-2, e2-standard-4, - e2-standard-8, e2-standard-16, e2-standard-32, n2-standard-8, - n1-standard-4, t2d-standard-6, n2d-standard-2, n2d-standard-4, - n2d-standard-8, n2d-standard-16, n2d-standard-32. + run on. --network-tags=[NETWORK_TAGS,...] Network tags to add to the Google Compute Engine machines backing the diff --git a/gcloud/artifacts/docker/tags/help b/gcloud/artifacts/docker/tags/help index d510fda4b..bdb363461 100644 --- a/gcloud/artifacts/docker/tags/help +++ b/gcloud/artifacts/docker/tags/help @@ -9,29 +9,31 @@ DESCRIPTION To add tag my-tag to image busy-box referenced by digest abcxyz in us-west1: - $ gcloud artifacts docker tags - us-west1-docker.pkg.dev/my-project/my-repository/busy-box@sha256:abcxyz - us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag + $ gcloud artifacts docker tags add \ + us-west1-docker.pkg.dev/my-project/my-repository/\ + busy-box@sha256:abcxyz \ + us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag To add tag my-tag to image busy-box referenced by tag latest in us-west1: - $ gcloud artifacts docker tags \ - us-west1-docker.pkg.dev/my-project/my-repository/busy-box:latest - us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag + $ gcloud artifacts docker tags add \ + us-west1-docker.pkg.dev/my-project/my-repository/\ + busy-box:latest \ + us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag To delete tag my-tag from image busy-box in us-west1: - $ gcloud artifacts docker tags \ + $ gcloud artifacts docker tags delete \ us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag To list all tags in repository my-repository in us-west1: - $ gcloud artifacts docker tags \ + $ gcloud artifacts docker tags list \ us-west1-docker.pkg.dev/my-project/my-repository To list tags for image busy-box in us-west1: - $ gcloud artifacts docker tags \ + $ gcloud artifacts docker tags list \ us-west1-docker.pkg.dev/my-project/my-repository/busy-box GCLOUD WIDE FLAGS diff --git a/gcloud/artifacts/repositories/delete-cleanup-policies b/gcloud/artifacts/repositories/delete-cleanup-policies new file mode 100644 index 000000000..708e61788 --- /dev/null +++ b/gcloud/artifacts/repositories/delete-cleanup-policies @@ -0,0 +1,72 @@ +NAME + gcloud artifacts repositories delete-cleanup-policies - delete cleanup + policies from an Artifact Registry repository + +SYNOPSIS + gcloud artifacts repositories delete-cleanup-policies + (REPOSITORY : --location=LOCATION) --policynames=POLICYNAMES + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete cleanup policies from an Artifact Registry repository. + + This command can fail for the following reasons: + ▪ The given repository does not exist. + ▪ The active account does not have permission to update repositories. + +EXAMPLES + To delete a cleanup policy named policy_a from the repository my-repo, run: + + $ gcloud artifacts repositories delete-cleanup-policies my-repo \ + --policynames=policy_a + +POSITIONAL ARGUMENTS + Repository resource - The Artifact Registry repository to update. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument repository on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + REPOSITORY + ID of the repository or fully qualified identifier for the + repository. + + To set the repository attribute: + ▸ provide the argument repository on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the repository. Overrides the default artifacts/location + property value for this command invocation. To configure the default + location, use the command: gcloud config set artifacts/location. + + To set the location attribute: + ▸ provide the argument repository on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + +REQUIRED FLAGS + --policynames=POLICYNAMES + Comma-separated list of cleanup policy names to delete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/artifacts/repositories/help b/gcloud/artifacts/repositories/help index 810151566..60bf3866f 100644 --- a/gcloud/artifacts/repositories/help +++ b/gcloud/artifacts/repositories/help @@ -59,6 +59,9 @@ COMMANDS delete Delete an Artifact Registry repository. + delete-cleanup-policies + Delete cleanup policies from an Artifact Registry repository. + describe Describe an Artifact Registry repository. @@ -68,10 +71,16 @@ COMMANDS list List repositories in the specified project. + list-cleanup-policies + List cleanup policies of an Artifact Registry repository. + remove-iam-policy-binding Remove an IAM policy binding from the IAM policy of an Artifact Registry repository. + set-cleanup-policies + Set or update cleanup policies for an Artifact Registry repository. + set-iam-policy Set the IAM policy for an Artifact Registry repository. diff --git a/gcloud/artifacts/repositories/list-cleanup-policies b/gcloud/artifacts/repositories/list-cleanup-policies new file mode 100644 index 000000000..15d127e86 --- /dev/null +++ b/gcloud/artifacts/repositories/list-cleanup-policies @@ -0,0 +1,66 @@ +NAME + gcloud artifacts repositories list-cleanup-policies - list cleanup policies + of an Artifact Registry repository + +SYNOPSIS + gcloud artifacts repositories list-cleanup-policies + (REPOSITORY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List cleanup policies of an Artifact Registry repository. + + This command can fail for the following reasons: + ▪ The specified repository does not exist. + ▪ The active account does not have permission to list cleanup policies. + +EXAMPLES + To list cleanup policies for the repository my-repo, run: + + $ gcloud artifacts repositories list-cleanup-policies my-repo + +POSITIONAL ARGUMENTS + Repository resource - The parent Artifact Registry repository for the list + of cleanup policies. 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 repository on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + REPOSITORY + ID of the repository or fully qualified identifier for the + repository. + + To set the repository attribute: + ▸ provide the argument repository on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the repository. Overrides the default artifacts/location + property value for this command invocation. To configure the default + location, use the command: gcloud config set artifacts/location. + + To set the location attribute: + ▸ provide the argument repository on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/artifacts/repositories/set-cleanup-policies b/gcloud/artifacts/repositories/set-cleanup-policies new file mode 100644 index 000000000..f120e2fb3 --- /dev/null +++ b/gcloud/artifacts/repositories/set-cleanup-policies @@ -0,0 +1,94 @@ +NAME + gcloud artifacts repositories set-cleanup-policies - set or update cleanup + policies for an Artifact Registry repository + +SYNOPSIS + gcloud artifacts repositories set-cleanup-policies + (REPOSITORY : --location=LOCATION) + (--dry-run [--policy=POLICY : --overwrite]) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Set or update cleanup policies for an Artifact Registry repository. + + This command can fail for the following reasons: + ▪ The given repository does not exist. + ▪ The active account does not have permission to update repositories. + ▪ A valid cleanup policy format was not provided. + ▪ The repository exceeds the maximum number of cleanup policies. + + See + https://cloud.google.com/artifact-registry/docs/repositories/cleanup-policy + for details of the cleanup policy file format and contents. + +EXAMPLES + To create a cleanup policy from a file with the name policy.json in the + repository my-repo, run: + + $ gcloud artifacts repositories set-cleanup-policies my-repo \ + --policy=policy.json + +POSITIONAL ARGUMENTS + Repository resource - The parent Artifact Registry repository for the list + of cleanup policies. 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 repository on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + REPOSITORY + ID of the repository or fully qualified identifier for the + repository. + + To set the repository attribute: + ▸ provide the argument repository on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Location of the repository. Overrides the default artifacts/location + property value for this command invocation. To configure the default + location, use the command: gcloud config set artifacts/location. + + To set the location attribute: + ▸ provide the argument repository on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property artifacts/location. + +REQUIRED FLAGS + At least one of these must be specified: + + --dry-run + Disable deleting images according to cleanup policies. + + Setting Policies + + --policy=POLICY + Path to a local JSON formatted file containing valid cleanup + policies. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --overwrite + Delete existing policies and replace with the specified set of + policies. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 artifactregistry/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/artifacts/docs/ diff --git a/gcloud/beta/ai/endpoints/deploy-model b/gcloud/beta/ai/endpoints/deploy-model index 0628e26b1..2b9c95c8c 100644 --- a/gcloud/beta/ai/endpoints/deploy-model +++ b/gcloud/beta/ai/endpoints/deploy-model @@ -73,9 +73,9 @@ OPTIONAL FLAGS type The type of the accelerator. Choices are 'nvidia-a100-80gb', - 'nvidia-l4', 'nvidia-tesla-a100', 'nvidia-tesla-k80', - 'nvidia-tesla-p100', 'nvidia-tesla-p4', 'nvidia-tesla-t4', - 'nvidia-tesla-v100'. + 'nvidia-h100-80gb', 'nvidia-l4', 'nvidia-tesla-a100', + 'nvidia-tesla-k80', 'nvidia-tesla-p100', 'nvidia-tesla-p4', + 'nvidia-tesla-t4', 'nvidia-tesla-v100'. count The number of accelerators to attach to each machine running the diff --git a/gcloud/beta/artifacts/docker/tags/help b/gcloud/beta/artifacts/docker/tags/help index 16365b896..1b867a4ea 100644 --- a/gcloud/beta/artifacts/docker/tags/help +++ b/gcloud/beta/artifacts/docker/tags/help @@ -9,29 +9,31 @@ DESCRIPTION (BETA) To add tag my-tag to image busy-box referenced by digest abcxyz in us-west1: - $ gcloud beta artifacts docker tags - us-west1-docker.pkg.dev/my-project/my-repository/busy-box@sha256:abcxyz - us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag + $ gcloud beta artifacts docker tags add \ + us-west1-docker.pkg.dev/my-project/my-repository/\ + busy-box@sha256:abcxyz \ + us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag To add tag my-tag to image busy-box referenced by tag latest in us-west1: - $ gcloud beta artifacts docker tags \ - us-west1-docker.pkg.dev/my-project/my-repository/busy-box:latest - us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag + $ gcloud beta artifacts docker tags add \ + us-west1-docker.pkg.dev/my-project/my-repository/\ + busy-box:latest \ + us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag To delete tag my-tag from image busy-box in us-west1: - $ gcloud beta artifacts docker tags \ + $ gcloud beta artifacts docker tags delete \ us-west1-docker.pkg.dev/my-project/my-repository/busy-box:my-tag To list all tags in repository my-repository in us-west1: - $ gcloud beta artifacts docker tags \ + $ gcloud beta artifacts docker tags list \ us-west1-docker.pkg.dev/my-project/my-repository To list tags for image busy-box in us-west1: - $ gcloud beta artifacts docker tags \ + $ gcloud beta artifacts docker tags list \ us-west1-docker.pkg.dev/my-project/my-repository/busy-box GCLOUD WIDE FLAGS diff --git a/gcloud/beta/builds/connections/add-iam-policy-binding b/gcloud/beta/builds/connections/add-iam-policy-binding index 010727ea9..98e5ae63d 100644 --- a/gcloud/beta/builds/connections/add-iam-policy-binding +++ b/gcloud/beta/builds/connections/add-iam-policy-binding @@ -87,8 +87,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections add-iam-policy-binding $ gcloud alpha builds connections add-iam-policy-binding diff --git a/gcloud/beta/builds/connections/create/github b/gcloud/beta/builds/connections/create/github index 988441932..e813f0d18 100644 --- a/gcloud/beta/builds/connections/create/github +++ b/gcloud/beta/builds/connections/create/github @@ -111,8 +111,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections create github $ gcloud alpha builds connections create github diff --git a/gcloud/beta/builds/connections/create/github-enterprise b/gcloud/beta/builds/connections/create/github-enterprise index ebce00b43..c6bfb8185 100644 --- a/gcloud/beta/builds/connections/create/github-enterprise +++ b/gcloud/beta/builds/connections/create/github-enterprise @@ -165,8 +165,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections create github-enterprise $ gcloud alpha builds connections create github-enterprise diff --git a/gcloud/beta/builds/connections/create/gitlab b/gcloud/beta/builds/connections/create/gitlab index f3435fc86..df8b3f9c0 100644 --- a/gcloud/beta/builds/connections/create/gitlab +++ b/gcloud/beta/builds/connections/create/gitlab @@ -142,8 +142,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections create gitlab $ gcloud alpha builds connections create gitlab diff --git a/gcloud/beta/builds/connections/create/help b/gcloud/beta/builds/connections/create/help index 068c4f065..11317f047 100644 --- a/gcloud/beta/builds/connections/create/help +++ b/gcloud/beta/builds/connections/create/help @@ -27,8 +27,10 @@ COMMANDS Enterprise. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections create $ gcloud alpha builds connections create diff --git a/gcloud/beta/builds/connections/delete b/gcloud/beta/builds/connections/delete index f861b150f..8d56c1182 100644 --- a/gcloud/beta/builds/connections/delete +++ b/gcloud/beta/builds/connections/delete @@ -65,8 +65,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections delete $ gcloud alpha builds connections delete diff --git a/gcloud/beta/builds/connections/describe b/gcloud/beta/builds/connections/describe index d4cd19238..df04b875a 100644 --- a/gcloud/beta/builds/connections/describe +++ b/gcloud/beta/builds/connections/describe @@ -61,8 +61,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections describe $ gcloud alpha builds connections describe diff --git a/gcloud/beta/builds/connections/get-iam-policy b/gcloud/beta/builds/connections/get-iam-policy index 2d40fdf88..6215846ba 100644 --- a/gcloud/beta/builds/connections/get-iam-policy +++ b/gcloud/beta/builds/connections/get-iam-policy @@ -89,8 +89,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections get-iam-policy $ gcloud alpha builds connections get-iam-policy diff --git a/gcloud/beta/builds/connections/help b/gcloud/beta/builds/connections/help index e7105c8a7..95e1a9a64 100644 --- a/gcloud/beta/builds/connections/help +++ b/gcloud/beta/builds/connections/help @@ -43,8 +43,10 @@ COMMANDS (BETA) Set the IAM policy for a Cloud Build connection. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections $ gcloud alpha builds connections diff --git a/gcloud/beta/builds/connections/list b/gcloud/beta/builds/connections/list index d67ce04ff..dccbcdd74 100644 --- a/gcloud/beta/builds/connections/list +++ b/gcloud/beta/builds/connections/list @@ -80,8 +80,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections list $ gcloud alpha builds connections list diff --git a/gcloud/beta/builds/connections/set-iam-policy b/gcloud/beta/builds/connections/set-iam-policy index 97c0c790b..0d1b88c7f 100644 --- a/gcloud/beta/builds/connections/set-iam-policy +++ b/gcloud/beta/builds/connections/set-iam-policy @@ -73,8 +73,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections set-iam-policy $ gcloud alpha builds connections set-iam-policy diff --git a/gcloud/beta/builds/connections/update/github b/gcloud/beta/builds/connections/update/github index c264f08cf..9c948d01f 100644 --- a/gcloud/beta/builds/connections/update/github +++ b/gcloud/beta/builds/connections/update/github @@ -83,8 +83,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections update github $ gcloud alpha builds connections update github diff --git a/gcloud/beta/builds/connections/update/github-enterprise b/gcloud/beta/builds/connections/update/github-enterprise index 70da1c981..1ea337ec2 100644 --- a/gcloud/beta/builds/connections/update/github-enterprise +++ b/gcloud/beta/builds/connections/update/github-enterprise @@ -109,8 +109,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections update github-enterprise $ gcloud alpha builds connections update github-enterprise diff --git a/gcloud/beta/builds/connections/update/gitlab b/gcloud/beta/builds/connections/update/gitlab index 08ba9a59b..05523212b 100644 --- a/gcloud/beta/builds/connections/update/gitlab +++ b/gcloud/beta/builds/connections/update/gitlab @@ -98,8 +98,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections update gitlab $ gcloud alpha builds connections update gitlab diff --git a/gcloud/beta/builds/connections/update/help b/gcloud/beta/builds/connections/update/help index 7b2403676..26a5da5ef 100644 --- a/gcloud/beta/builds/connections/update/help +++ b/gcloud/beta/builds/connections/update/help @@ -27,8 +27,10 @@ COMMANDS Enterprise. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds connections update $ gcloud alpha builds connections update diff --git a/gcloud/beta/builds/repositories/create b/gcloud/beta/builds/repositories/create index b183c28b1..fe1bf5bbe 100644 --- a/gcloud/beta/builds/repositories/create +++ b/gcloud/beta/builds/repositories/create @@ -80,8 +80,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds repositories create $ gcloud alpha builds repositories create diff --git a/gcloud/beta/builds/repositories/delete b/gcloud/beta/builds/repositories/delete index 8f9056f53..ad037e2f7 100644 --- a/gcloud/beta/builds/repositories/delete +++ b/gcloud/beta/builds/repositories/delete @@ -75,8 +75,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds repositories delete $ gcloud alpha builds repositories delete diff --git a/gcloud/beta/builds/repositories/describe b/gcloud/beta/builds/repositories/describe index b6914bfe6..ee66ade01 100644 --- a/gcloud/beta/builds/repositories/describe +++ b/gcloud/beta/builds/repositories/describe @@ -70,8 +70,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds repositories describe $ gcloud alpha builds repositories describe diff --git a/gcloud/beta/builds/repositories/help b/gcloud/beta/builds/repositories/help index bc80eb51a..8f7c6e892 100644 --- a/gcloud/beta/builds/repositories/help +++ b/gcloud/beta/builds/repositories/help @@ -29,8 +29,10 @@ COMMANDS (BETA) List all Cloud Build repositories in a connection. NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds repositories $ gcloud alpha builds repositories diff --git a/gcloud/beta/builds/repositories/list b/gcloud/beta/builds/repositories/list index b697ba9f8..d71b4d7f4 100644 --- a/gcloud/beta/builds/repositories/list +++ b/gcloud/beta/builds/repositories/list @@ -96,8 +96,10 @@ API REFERENCE API can be found at: https://cloud.google.com/cloud-build/docs/ NOTES - This command is currently in beta and might change without notice. This - variant is also available: + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud builds repositories list $ gcloud alpha builds repositories list diff --git a/gcloud/beta/builds/submit b/gcloud/beta/builds/submit index 3b42351dd..cc8e16ffc 100644 --- a/gcloud/beta/builds/submit +++ b/gcloud/beta/builds/submit @@ -118,7 +118,7 @@ FLAGS --machine-type=MACHINE_TYPE Machine type used to run the build. MACHINE_TYPE must be one of: - e2-highcpu-32, e2-highcpu-8, n1-highcpu-32, n1-highcpu-8. + e2-highcpu-32, e2-highcpu-8, e2-medium, n1-highcpu-32, n1-highcpu-8. --region=REGION The region of the Cloud Build Service to use. Must be set to a diff --git a/gcloud/beta/builds/triggers/create/bitbucketserver b/gcloud/beta/builds/triggers/create/bitbucketserver index db61d3009..fd7875182 100644 --- a/gcloud/beta/builds/triggers/create/bitbucketserver +++ b/gcloud/beta/builds/triggers/create/bitbucketserver @@ -105,24 +105,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud beta builds triggers create bitbucketserver ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/beta/builds/triggers/create/cloud-source-repositories b/gcloud/beta/builds/triggers/create/cloud-source-repositories index 2b8560b5c..fe3206199 100644 --- a/gcloud/beta/builds/triggers/create/cloud-source-repositories +++ b/gcloud/beta/builds/triggers/create/cloud-source-repositories @@ -87,24 +87,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud beta builds triggers create cloud-source-repositories ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/beta/builds/triggers/create/github b/gcloud/beta/builds/triggers/create/github index fe51d7bf4..e1c20a31d 100644 --- a/gcloud/beta/builds/triggers/create/github +++ b/gcloud/beta/builds/triggers/create/github @@ -96,24 +96,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud beta builds triggers create github ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/beta/builds/triggers/create/gitlab b/gcloud/beta/builds/triggers/create/gitlab new file mode 100644 index 000000000..7a6ca5f54 --- /dev/null +++ b/gcloud/beta/builds/triggers/create/gitlab @@ -0,0 +1,207 @@ +NAME + gcloud beta builds triggers create gitlab - create a build trigger for a + 2nd-gen GitLab repository + +SYNOPSIS + gcloud beta builds triggers create gitlab + (--trigger-config=PATH | [(--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-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) + : --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --name=NAME --region=REGION + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a build trigger for a 2nd-gen GitLab repository. + +EXAMPLES + To create a push trigger with a 2nd-gen repository for all branches: + + $ gcloud beta builds triggers create gitlab --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/global/connections/myconn/\ + repositories/myrepo" --branch-pattern=".*" \ + --build-config="cloudbuild.yaml" + + To create a pull request trigger with a 1st-gen repository for main: + + $ gcloud beta builds triggers create gitlab --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/global/connections/myconn/\ + repositories/myrepo" --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 + + --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. + + --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, builds/region, + which is the default region to use when working with Cloud Build + resources, is used. If builds/region is unset, region is set to + global. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --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: + + $ gcloud beta builds triggers create gitlab ... \ + --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". + + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, + SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values + + 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 regular expression 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 regular expression 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 argument 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. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 builds triggers create gitlab + + $ gcloud alpha builds triggers create gitlab + diff --git a/gcloud/beta/builds/triggers/create/gitlab-enterprise b/gcloud/beta/builds/triggers/create/gitlab-enterprise index d2d1e85de..4101382f9 100644 --- a/gcloud/beta/builds/triggers/create/gitlab-enterprise +++ b/gcloud/beta/builds/triggers/create/gitlab-enterprise @@ -86,24 +86,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud beta builds triggers create gitlab-enterprise ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/beta/builds/triggers/create/help b/gcloud/beta/builds/triggers/create/help index 8930c2ffd..038057266 100644 --- a/gcloud/beta/builds/triggers/create/help +++ b/gcloud/beta/builds/triggers/create/help @@ -25,6 +25,9 @@ COMMANDS github (BETA) Create a build trigger for a GitHub repository. + gitlab + (BETA) Create a build trigger for a 2nd-gen GitLab repository. + gitlab-enterprise (BETA) Create a build trigger for a GitLab Enterprise repository. diff --git a/gcloud/beta/builds/triggers/create/manual b/gcloud/beta/builds/triggers/create/manual index fa56f5090..85e023010 100644 --- a/gcloud/beta/builds/triggers/create/manual +++ b/gcloud/beta/builds/triggers/create/manual @@ -71,24 +71,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud beta builds triggers create manual ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/beta/builds/triggers/create/pubsub b/gcloud/beta/builds/triggers/create/pubsub index 1595f5369..65538b7b9 100644 --- a/gcloud/beta/builds/triggers/create/pubsub +++ b/gcloud/beta/builds/triggers/create/pubsub @@ -89,24 +89,23 @@ REQUIRED FLAGS for more details. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud beta builds triggers create pubsub ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/beta/builds/triggers/create/webhook b/gcloud/beta/builds/triggers/create/webhook index 6bae07711..116f3b9e3 100644 --- a/gcloud/beta/builds/triggers/create/webhook +++ b/gcloud/beta/builds/triggers/create/webhook @@ -95,24 +95,23 @@ REQUIRED FLAGS for more details. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud beta builds triggers create webhook ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/beta/builds/triggers/run b/gcloud/beta/builds/triggers/run index 3e11086f1..eb72beff5 100644 --- a/gcloud/beta/builds/triggers/run +++ b/gcloud/beta/builds/triggers/run @@ -47,24 +47,21 @@ POSITIONAL ARGUMENTS FLAGS --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For example: - For example (using some nonsensical substitution keys; all keys must - begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud beta builds triggers run ... \ --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. + Substitutions can be applied to user-defined variables (starting with + an underscore) and to the following built-in variables: 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values At most one of these can be specified: diff --git a/gcloud/beta/compute/backend-services/add-backend b/gcloud/beta/compute/backend-services/add-backend index ee5230124..aa14215f1 100644 --- a/gcloud/beta/compute/backend-services/add-backend +++ b/gcloud/beta/compute/backend-services/add-backend @@ -13,7 +13,8 @@ SYNOPSIS | --network-endpoint-group-zone=NETWORK_ENDPOINT_GROUP_ZONE]) [--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER] [--description=DESCRIPTION] [--failover] - [--max-utilization=MAX_UTILIZATION] [--global | --region=REGION] + [--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE] + [--global | --region=REGION] [--max-connections=MAX_CONNECTIONS | --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT | --max-connections-per-instance=MAX_CONNECTIONS_PER_INSTANCE @@ -232,6 +233,23 @@ OPTIONAL FLAGS capacity. For usage guidelines, see Balancing mode combinations (https://cloud.google.com/load-balancing/docs/backend-service#balancing-mode-combos). + --preference=PREFERENCE + Defines whether a backend should be fully utilized before sending + traffic to backends with default preference. This parameter cannot be + used with regional managed instance groups and when the endpoint type + of an attached network endpoint group is INTERNET_IP_PORT, + INTERNET_FQDN_PORT, or SERVERLESS. PREFERENCE must be one of: + + DEFAULT + This is the default setting. If the designated preferred backends + don't have enough capacity, backends in the default category are + used. Traffic is distributed between default backends based on the + load balancing algorithm you use. + + PREFERRED + Backends with this preference setting are used up to their capacity + limits first, while optimizing overall network latency. + At most one of these can be specified: --global diff --git a/gcloud/beta/compute/backend-services/update-backend b/gcloud/beta/compute/backend-services/update-backend index 738e1072a..38b1b4da0 100644 --- a/gcloud/beta/compute/backend-services/update-backend +++ b/gcloud/beta/compute/backend-services/update-backend @@ -11,7 +11,8 @@ SYNOPSIS : --network-endpoint-group-zone=NETWORK_ENDPOINT_GROUP_ZONE]) [--balancing-mode=BALANCING_MODE] [--capacity-scaler=CAPACITY_SCALER] [--description=DESCRIPTION] [--failover] - [--max-utilization=MAX_UTILIZATION] [--global | --region=REGION] + [--max-utilization=MAX_UTILIZATION] [--preference=PREFERENCE] + [--global | --region=REGION] [--max-connections=MAX_CONNECTIONS | --max-connections-per-endpoint=MAX_CONNECTIONS_PER_ENDPOINT | --max-connections-per-instance=MAX_CONNECTIONS_PER_INSTANCE @@ -201,6 +202,23 @@ OPTIONAL FLAGS capacity. For usage guidelines, see Balancing mode combinations (https://cloud.google.com/load-balancing/docs/backend-service#balancing-mode-combos). + --preference=PREFERENCE + Defines whether a backend should be fully utilized before sending + traffic to backends with default preference. This parameter cannot be + used with regional managed instance groups and when the endpoint type + of an attached network endpoint group is INTERNET_IP_PORT, + INTERNET_FQDN_PORT, or SERVERLESS. PREFERENCE must be one of: + + DEFAULT + This is the default setting. If the designated preferred backends + don't have enough capacity, backends in the default category are + used. Traffic is distributed between default backends based on the + load balancing algorithm you use. + + PREFERRED + Backends with this preference setting are used up to their capacity + limits first, while optimizing overall network latency. + At most one of these can be specified: --global diff --git a/gcloud/beta/compute/instances/ops-agents/policies/create b/gcloud/beta/compute/instances/ops-agents/policies/create index 603e86b2c..7ba3b63c9 100644 --- a/gcloud/beta/compute/instances/ops-agents/policies/create +++ b/gcloud/beta/compute/instances/ops-agents/policies/create @@ -245,6 +245,7 @@ REQUIRED FLAGS ubuntu 21.04 ubuntu 21.10 ubuntu 22.04 + ubuntu 23.04 windows 10.* windows 6.* diff --git a/gcloud/beta/compute/instances/ops-agents/policies/update b/gcloud/beta/compute/instances/ops-agents/policies/update index af4614bc7..f859b3db6 100644 --- a/gcloud/beta/compute/instances/ops-agents/policies/update +++ b/gcloud/beta/compute/instances/ops-agents/policies/update @@ -282,6 +282,7 @@ FLAGS ubuntu 21.04 ubuntu 21.10 ubuntu 22.04 + ubuntu 23.04 windows 10.* windows 6.* diff --git a/gcloud/beta/compute/networks/subnets/update b/gcloud/beta/compute/networks/subnets/update index 60daaf757..5f5e0c645 100644 --- a/gcloud/beta/compute/networks/subnets/update +++ b/gcloud/beta/compute/networks/subnets/update @@ -13,7 +13,8 @@ SYNOPSIS [--logging-metadata=LOGGING_METADATA] [--logging-metadata-fields=[METADATA_FIELD,...]] [--region=REGION] [--stack-type=STACK_TYPE] - [--add-secondary-ranges=PROPERTY=VALUE,[...] | --[no-]enable-flow-logs + [--add-secondary-ranges=PROPERTY=VALUE,[...] + | --[no-]allow-cidr-routes-overlap | --[no-]enable-flow-logs | --[no-]enable-private-ip-google-access | --private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE | --purpose=PURPOSE | --remove-secondary-ranges=PROPERTY=VALUE,[...] @@ -138,6 +139,11 @@ FLAGS ▸ RANGE_NAME - Name of the secondary range. ▸ RANGE - IP range in CIDR format. + --[no-]allow-cidr-routes-overlap + Allow/disallow this subnetwork's IP address ranges to conflict with + existing static routes. Use --allow-cidr-routes-overlap to enable and + --no-allow-cidr-routes-overlap to disable. + --[no-]enable-flow-logs Enable/disable VPC Flow Logs for this subnet. If the subnet does not support VPC Flow Logs, this flag has no effect. For more information, diff --git a/gcloud/beta/container/backup-restore/restore-plans/create b/gcloud/beta/container/backup-restore/restore-plans/create index b9f96df65..d0bc63c30 100644 --- a/gcloud/beta/container/backup-restore/restore-plans/create +++ b/gcloud/beta/container/backup-restore/restore-plans/create @@ -7,14 +7,18 @@ SYNOPSIS (RESTORE_PLAN : --location=LOCATION) --backup-plan=BACKUP_PLAN --cluster=CLUSTER --namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE - (--all-namespaces | --selected-applications=SELECTED_APPLICATIONS + (--all-namespaces | --excluded-namespaces=[EXCLUDED_NAMESPACES,...] + | --no-namespaces | --selected-applications=SELECTED_APPLICATIONS | --selected-namespaces=[SELECTED_NAMESPACES,...]) [--async] + [--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--substitution-rules-file=SUBSTITUTION_RULES_FILE] [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; default="no-volume-data-restoration"] - [--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY - --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE, + [--cluster-resource-scope-all-group-kinds + | --cluster-resource-scope-excluded-group-kinds=[CLUSTER_RESOURCE_SCOPE_EXCLUDED_GROUP_KINDS, + ...] | --cluster-resource-scope-no-group-kinds + | --cluster-resource-scope-selected-group-kinds=[CLUSTER_RESOURCE_SCOPE_SELECTED_GROUP_KINDS, ...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -110,11 +114,20 @@ REQUIRED FLAGS out of band process creates conflicting resources), a conflict will be reported. + The scope of namespaced resources to restore. + Exactly one of these must be specified: --all-namespaces If true, restore all namespaced resources in the backup. + --excluded-namespaces=[EXCLUDED_NAMESPACES,...] + List of selected namespaces to skip. All namespaced resources in all + namespaces excluding selected namespaces are restored. + + --no-namespaces + If true, do not restore any namespaced resources in the backup. + --selected-applications=SELECTED_APPLICATIONS List of selected applications to restore. Only those namespaced resources which belong to one of the selected applications are @@ -129,6 +142,24 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY + Define how to handle restore-time conflicts for cluster-scoped + resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: + + use-backup-version + Selecting 'use-existing-version' means deleting the existing + version of the conflicting resources before re-creating them from + the Backup. + + Note that this is a dangerous option which could cause + unintentional data loss if used inappropriately. For example, + deleting a CRD will cause Kubernetes to delete all CRs of that + type. + + use-existing-version + Selecting 'use-existing-version' means no conflicting resources + will be restored. + --description=DESCRIPTION The description of the restore plan. @@ -166,29 +197,29 @@ OPTIONAL FLAGS pre-provisioned using the volume handle of the original PV in the Backup. - --cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY - Define how to handle restore-time conflicts for cluster-scoped - resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: + The scope of cluster-scoped resources to restore. - use-backup-version - Selecting 'use-existing-version' means deleting the existing - version of the conflicting resources before re-creating them from - the Backup. + At most one of these can be specified: - Note that this is a dangerous option which could cause - unintentional data loss if used inappropriately. For example, - deleting a CRD will cause Kubernetes to delete all CRs of that - type. + --cluster-resource-scope-all-group-kinds + If true, all valid cluster-scoped resources will be restored. - use-existing-version - Selecting 'use-existing-version' means no conflicting resources - will be restored. + --cluster-resource-scope-excluded-group-kinds=[CLUSTER_RESOURCE_SCOPE_EXCLUDED_GROUP_KINDS,...] + List of cluster-scoped resource group kinds to NOT restore from the + backup. If specified, all valid cluster-scoped resources will be + restored except for those specified in the list. The format of a + resource is "/", e.g. storage.k8s.io/StorageClass for + StorageClass. Use an empty string for core API group. - --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE,...] - List of cluster-scoped resource types to be restored. Not specifying - this means NO cluster resource will be restored. The format of a - resource is "/", e.g. storage.k8s.io/StorageClass for - StorageClass. Use an empty string for core API group. + --cluster-resource-scope-no-group-kinds + If true, no cluster-scoped resources will be restored. + + --cluster-resource-scope-selected-group-kinds=[CLUSTER_RESOURCE_SCOPE_SELECTED_GROUP_KINDS,...] + List of cluster-scoped resource group kinds to restore from the + backup. If specified, only the selected resources will be restored. + The format of a resource is "/", e.g. + storage.k8s.io/StorageClass for StorageClass. Use an empty string for + core API group. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/container/backup-restore/restore-plans/update b/gcloud/beta/container/backup-restore/restore-plans/update index 73da63bad..03b70fb0e 100644 --- a/gcloud/beta/container/backup-restore/restore-plans/update +++ b/gcloud/beta/container/backup-restore/restore-plans/update @@ -5,17 +5,21 @@ NAME SYNOPSIS gcloud beta container backup-restore restore-plans update (RESTORE_PLAN : --location=LOCATION) [--async] + [--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY] [--description=DESCRIPTION] [--etag=ETAG] [--namespaced-resource-restore-mode=NAMESPACED_RESOURCE_RESTORE_MODE] [--substitution-rules-file=SUBSTITUTION_RULES_FILE] [--update-labels=[KEY=VALUE,...]] [--volume-data-restore-policy=VOLUME_DATA_RESTORE_POLICY; default="no-volume-data-restoration"] - [--all-namespaces | --selected-applications=SELECTED_APPLICATIONS + [--all-namespaces | --excluded-namespaces=[EXCLUDED_NAMESPACES,...] + | --no-namespaces | --selected-applications=SELECTED_APPLICATIONS | --selected-namespaces=[SELECTED_NAMESPACES,...]] [--clear-labels | --remove-labels=[KEY,...]] - [--cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY - --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE, + [--cluster-resource-scope-all-group-kinds + | --cluster-resource-scope-excluded-group-kinds=[CLUSTER_RESOURCE_SCOPE_EXCLUDED_GROUP_KINDS, + ...] | --cluster-resource-scope-no-group-kinds + | --cluster-resource-scope-selected-group-kinds=[CLUSTER_RESOURCE_SCOPE_SELECTED_GROUP_KINDS, ...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -71,6 +75,24 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY + Define how to handle restore-time conflicts for cluster-scoped + resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: + + use-backup-version + Selecting 'use-existing-version' means deleting the existing + version of the conflicting resources before re-creating them from + the Backup. + + Note that this is a dangerous option which could cause + unintentional data loss if used inappropriately. For example, + deleting a CRD will cause Kubernetes to delete all CRs of that + type. + + use-existing-version + Selecting 'use-existing-version' means no conflicting resources + will be restored. + --description=DESCRIPTION The description of the restore plan. @@ -136,11 +158,20 @@ FLAGS pre-provisioned using the volume handle of the original PV in the Backup. + The scope of namespaced resources to restore. + At most one of these can be specified: --all-namespaces If true, restore all namespaced resources in the backup. + --excluded-namespaces=[EXCLUDED_NAMESPACES,...] + List of selected namespaces to skip. All namespaced resources in all + namespaces excluding selected namespaces are restored. + + --no-namespaces + If true, do not restore any namespaced resources in the backup. + --selected-applications=SELECTED_APPLICATIONS List of selected applications to restore. Only those namespaced resources which belong to one of the selected applications are @@ -171,29 +202,29 @@ FLAGS silently ignored. If --update-labels is also specified then --update-labels is applied first. - --cluster-resource-conflict-policy=CLUSTER_RESOURCE_CONFLICT_POLICY - Define how to handle restore-time conflicts for cluster-scoped - resources. CLUSTER_RESOURCE_CONFLICT_POLICY must be one of: + The scope of cluster-scoped resources to restore. - use-backup-version - Selecting 'use-existing-version' means deleting the existing - version of the conflicting resources before re-creating them from - the Backup. + At most one of these can be specified: - Note that this is a dangerous option which could cause - unintentional data loss if used inappropriately. For example, - deleting a CRD will cause Kubernetes to delete all CRs of that - type. + --cluster-resource-scope-all-group-kinds + If true, all valid cluster-scoped resources will be restored. - use-existing-version - Selecting 'use-existing-version' means no conflicting resources - will be restored. + --cluster-resource-scope-excluded-group-kinds=[CLUSTER_RESOURCE_SCOPE_EXCLUDED_GROUP_KINDS,...] + List of cluster-scoped resource group kinds to NOT restore from the + backup. If specified, all valid cluster-scoped resources will be + restored except for those specified in the list. The format of a + resource is "/", e.g. storage.k8s.io/StorageClass for + StorageClass. Use an empty string for core API group. - --cluster-resource-restore-scope=[CLUSTER_RESOURCE_RESTORE_SCOPE,...] - List of cluster-scoped resource types to be restored. Not specifying - this means NO cluster resource will be restored. The format of a - resource is "/", e.g. storage.k8s.io/StorageClass for - StorageClass. Use an empty string for core API group. + --cluster-resource-scope-no-group-kinds + If true, no cluster-scoped resources will be restored. + + --cluster-resource-scope-selected-group-kinds=[CLUSTER_RESOURCE_SCOPE_SELECTED_GROUP_KINDS,...] + List of cluster-scoped resource group kinds to restore from the + backup. If specified, only the selected resources will be restored. + The format of a resource is "/", e.g. + storage.k8s.io/StorageClass for StorageClass. Use an empty string for + core API group. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index d4b062a33..0732a5353 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -185,7 +185,7 @@ FLAGS ADDON must be one of: HttpLoadBalancing, HorizontalPodAutoscaling, KubernetesDashboard, NetworkPolicy, NodeLocalDNS, ConfigConnector, GcePersistentDiskCsiDriver, GcpFilestoreCsiDriver, BackupRestore, - Istio, GcsFuseCsiDriver, CloudRun. + GcsFuseCsiDriver, Istio, CloudRun. --allow-route-overlap Allows the provided cluster CIDRs to overlap with existing routes that @@ -1239,6 +1239,8 @@ FLAGS Selects Cloud DNS as the DNS provider for the cluster. default Selects the default DNS provider (kube-dns) for the cluster. + kubedns + Selects Kube DNS as the DNS provider for the cluster. --cluster-dns-domain=CLUSTER_DNS_DOMAIN DNS domain for this cluster. The default value is cluster.local. This diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index e7bf186e3..94f5e37c3 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -855,6 +855,8 @@ REQUIRED FLAGS Selects Cloud DNS as the DNS provider for the cluster. default Selects the default DNS provider (kube-dns) for the cluster. + kubedns + Selects Kube DNS as the DNS provider for the cluster. --cluster-dns-domain=CLUSTER_DNS_DOMAIN DNS domain for this cluster. The default value is cluster.local. diff --git a/gcloud/beta/container/fleet/memberships/register b/gcloud/beta/container/fleet/memberships/register index 3e4ab0621..4ebf5fe9a 100644 --- a/gcloud/beta/container/fleet/memberships/register +++ b/gcloud/beta/container/fleet/memberships/register @@ -28,6 +28,8 @@ DESCRIPTION To register a GKE cluster, use --gke-cluster or --gke-uri flag (no --kubeconfig flag is required). Connect agent will not be installed by default for GKE clusters. To install it, specify --install-connect-agent. + The default value for --location is the same as the cluster's region or + zone, can be specified as global. Anthos clusters on VMware, bare metal, AWS, and Azure are registered with a fleet when the clusters are created. To register Amazon EKS clusters, see @@ -77,7 +79,7 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json Register a non-GKE cluster and output a manifest that can be used to - install the Connect agent: + install the Connect agent by kubectl: $ gcloud beta container fleet memberships register my-cluster \ --context=my-cluster-context \ @@ -96,6 +98,14 @@ EXAMPLES --gke-uri=my-cluster-gke-uri --install-connect-agent \ --service-account-key-file=/tmp/keyfile.json + Register a GKE cluster and output a manifest that can be used to install + the Connect agent by kubectl: + + $ gcloud beta container fleet memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri --enable-workload-identity \ + --install-connect-agent \ + --manifest-output-file=/tmp/manifest.yaml + Register a GKE cluster first, and install the Connect agent later. $ gcloud beta container fleet memberships register my-cluster \ diff --git a/gcloud/beta/container/hub/memberships/register b/gcloud/beta/container/hub/memberships/register index 3255e531d..7908d61e4 100644 --- a/gcloud/beta/container/hub/memberships/register +++ b/gcloud/beta/container/hub/memberships/register @@ -28,6 +28,8 @@ DESCRIPTION To register a GKE cluster, use --gke-cluster or --gke-uri flag (no --kubeconfig flag is required). Connect agent will not be installed by default for GKE clusters. To install it, specify --install-connect-agent. + The default value for --location is the same as the cluster's region or + zone, can be specified as global. Anthos clusters on VMware, bare metal, AWS, and Azure are registered with a fleet when the clusters are created. To register Amazon EKS clusters, see @@ -77,7 +79,7 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json Register a non-GKE cluster and output a manifest that can be used to - install the Connect agent: + install the Connect agent by kubectl: $ gcloud beta container hub memberships register my-cluster \ --context=my-cluster-context \ @@ -96,6 +98,14 @@ EXAMPLES --gke-uri=my-cluster-gke-uri --install-connect-agent \ --service-account-key-file=/tmp/keyfile.json + Register a GKE cluster and output a manifest that can be used to install + the Connect agent by kubectl: + + $ gcloud beta container hub memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri --enable-workload-identity \ + --install-connect-agent \ + --manifest-output-file=/tmp/manifest.yaml + Register a GKE cluster first, and install the Connect agent later. $ gcloud beta container hub memberships register my-cluster \ diff --git a/gcloud/beta/debug/help b/gcloud/beta/debug/help deleted file mode 100644 index f9f92b5e8..000000000 --- a/gcloud/beta/debug/help +++ /dev/null @@ -1,83 +0,0 @@ -NAME - gcloud beta debug - commands for interacting with the Cloud Debugger - -SYNOPSIS - gcloud beta debug GROUP [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Commands for interacting with the Cloud Debugger. - - Cloud Debugger is deprecated and will be shutdown May 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - The gcloud beta debug command group provides interaction with Cloud - Debugger, allowing you to list and manipulate debugging targets, snapshots - and logpoints. - - Cloud Debugger is a feature of Google Cloud that lets you inspect the state - of an application at any code location without using logging statements and - without stopping or slowing down your applications. - - More information on Cloud Debugger can be found here: - https://cloud.google.com/debugger and detailed documentation can be found - here: https://cloud.google.com/debugger/docs/ - -EXAMPLES - To view all available debug targets, run: - - $ gcloud beta debug targets list - - NAME ID DESCRIPTION - default-test gcp:1234:5678 myproject-test-9876543 - default-test2 gcp:9012:3456 myproject-test2-1234567 - - To create a snapshot for a particular target: - - $ gcloud beta debug snapshots create --target=default-test foo.py:12 - - Note that if there is not a target with the exact name or ID specified, the - target is treated as a regular expression to match against the name or - description: - - $ gcloud beta debug snapshots create --target=test foo.py:12 - - ERROR: (gcloud.beta.debug.snapshots.create) Multiple possible targets found. - Use the --target option to select one of the following targets: - default-test - default-test2 - - In the above case, "test" matches both targets' names. Specifying 'test$' - would match only "default-test" (by name), while "9876" would match - "default-test" by description. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - logpoints - (BETA) (DEPRECATED) Commands for interacting with Cloud Debugger - logpoints. - - snapshots - (BETA) (DEPRECATED) Commands for interacting with Cloud Debugger - snapshots. - - source - (BETA) (DEPRECATED) Commands to manage source information for Cloud - Debugger. - - targets - (BETA) (DEPRECATED) Commands for interacting with Cloud Debugger debug - targets. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud debug - diff --git a/gcloud/beta/debug/logpoints/create b/gcloud/beta/debug/logpoints/create deleted file mode 100644 index f0ec9ceef..000000000 --- a/gcloud/beta/debug/logpoints/create +++ /dev/null @@ -1,106 +0,0 @@ -NAME - gcloud beta debug logpoints create - add debug logpoints to a Cloud - Debugger debug target (debuggee) - -SYNOPSIS - gcloud beta debug logpoints create LOCATION LOG_FORMAT_STRING - [--condition=CONDITION] [--log-level=LOG_LEVEL; default="info"] - [--target=(ID|DESCRIPTION_REGEXP)] [--wait=WAIT; default=10] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May - 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud beta debug logpoints create is used to add a debug logpoint to a - debug target (debuggee). Logpoints add logging to your running service - without changing your code or restarting your application. When you create - a logpoint, the message you specify will be added to your logs whenever any - instance of your service executes the specified line of code. - - The default lifetime of a logpoint is 24 hours from creation, and the - output will go to the standard log for the programming language of the - target (java.logging for Java, logging for Python, etc.) - -EXAMPLES - To add a logpoint with no conditions that will print the value of the - variable 'name' at line 41 of file main.py of a debug target (debuggee), - run: - - $ gcloud beta debug logpoints create main.py:41 \ - "Variable name={name}" --target= - - To add a logpoint that will print the value of the variable 'name' at line - 41 of file main.py on a debug target (debuggee) that will only trigger if - the length of 'name' is greater than 3, run: - - $ gcloud beta debug logpoints create main.py:41 \ - "Variable name={name}" --target= \ - --condition="len(name) > 3" - - To add a logpoint with a log level of error at line 35 of file main.py on a - debug target (debuggee), run: - - $ gcloud beta debug logpoints create main.py:35 "Unexpected path" \ - --target= --log-level=error - -POSITIONAL ARGUMENTS - LOCATION - The logpoint location. Locations are of the form FILE:LINE, where FILE - can be simply the file name, or the file name preceded by enough path - components to differentiate it from other files with the same name. It - is an error to provide a file name that is not unique in the debug - target. - - LOG_FORMAT_STRING - A format string which will be logged every time the logpoint location - is executed. If the string contains curly braces ('{' and '}'), any - text within the curly braces will be interpreted as a run-time - expression in the debug target's language, which will be evaluated when - the logpoint is hit. - - The value of the expression will then replace the {} expression in the - resulting log output. For example, if you specify the format string - "a={a}, b={b}", and the logpoint is hit when local variable a is 1 and - b is 2, the resulting log output would be "a=1, b=2". - -FLAGS - --condition=CONDITION - A condition to restrict when the log output is generated. When the - logpoint is hit, the condition will be evaluated, and the log output - will be generated only if the condition is true. - - --log-level=LOG_LEVEL; default="info" - The logging level to use when producing the log message. LOG_LEVEL must - be one of: info, warning, error. - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - - --wait=WAIT; default=10 - The number of seconds to wait to ensure that no error is returned from - a debugger agent when creating the logpoint. When a logpoint is - created, there will be a delay before the agents see and apply the - logpoint. Until at least one agent has attempted to enable the - logpoint, it cannot be determined if the logpoint is valid. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 debug logpoints create - diff --git a/gcloud/beta/debug/logpoints/delete b/gcloud/beta/debug/logpoints/delete deleted file mode 100644 index 366c59bfe..000000000 --- a/gcloud/beta/debug/logpoints/delete +++ /dev/null @@ -1,86 +0,0 @@ -NAME - gcloud beta debug logpoints delete - delete debug logpoints for a Cloud - Debugger debug target (debuggee) - -SYNOPSIS - gcloud beta debug logpoints delete [ID ...] [--all-users] - [--include-inactive] [--location=LOCATION-REGEXP] - [--target=(ID|DESCRIPTION_REGEXP)] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May - 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud beta debug logpoints delete is used to delete logpoints from a Cloud - Debugger debug target (debuggee). It will ask for confirmation before - deleting any logpoints. To suppress confirmation, use the global --quiet - option. - -EXAMPLES - To delete all active debug logpoints created by the current user of the - debug target (debuggee), without being prompted for confirmation, run: - - $ gcloud beta debug logpoints delete --target= --quiet - - To delete all active and inactive debug logpoints created by all users of - the debug target (debuggee), run: - - $ gcloud beta debug logpoints delete --target= \ - --include-inactive --all-users - - To delete the debug logpoints with IDs 'ID1' and 'ID2' (where ID1 and ID2 - were each created by different users) of the debug target (debuggee), run: - - $ gcloud beta debug logpoints delete ID1 ID2 \ - --target= --all-users - -POSITIONAL ARGUMENTS - [ID ...] - Zero or more logpoint resource identifiers. The specified logpoints - will be deleted. - -FLAGS - --all-users - If set, any location regexp will match logpoints from all users, rather - than only logpoints created by the current user. This flag is not - required when specifying the exact ID of a logpoint created by another - user. - - --include-inactive - If set, any location regexp will also match inactive logpoints, rather - than only logpoints which have not expired. This flag is not required - when specifying the exact ID of an inactive logpoint. - - --location=LOCATION-REGEXP - A regular expression to match against logpoint locations. All logpoints - matching this value will be deleted. You may specify --location - multiple times. - - EXAMPLE: - - gcloud beta debug logpoints delete \ - --location foo.py:[1-3] --location bar.py:4 - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and 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 beta and might change without notice. This - variant is also available: - - $ gcloud debug logpoints delete - diff --git a/gcloud/beta/debug/logpoints/help b/gcloud/beta/debug/logpoints/help deleted file mode 100644 index 435623096..000000000 --- a/gcloud/beta/debug/logpoints/help +++ /dev/null @@ -1,96 +0,0 @@ -NAME - gcloud beta debug logpoints - commands for interacting with Cloud Debugger - logpoints - -SYNOPSIS - gcloud beta debug logpoints COMMAND [--target=(ID|DESCRIPTION_REGEXP)] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Commands for interacting with Cloud Debugger logpoints. - - Cloud Debugger is deprecated and will be shutdown May 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - Logpoints allow you to inject logging into running services without - restarting or interfering with the normal function of the service. Log - output will be sent to the appropriate log for the target's environment. On - App Engine, for example, output will go to the request log. - -EXAMPLES - The following command would log the value of the "name" attribute of the - "product" variable whenever any request executes line 123 of the file - product.py: - - $ gcloud beta debug logpoints create product.py:123 \ - "No description for {product.name}" - - The log output will appear wherever explicit logging output from your - program is normally written. For example, for an App Engine Standard - application, the output would appear in the request log. - - If you want to log output only when certain runtime conditions are met, you - can add a "--condition" option: - - $ gcloud beta debug logpoints create product.py:123 \ - "Suspicious price: {product.name} costs {price}" \ - --condition "price < .50" - - Logpoints remain active for 24 hours after creation. If you want to disable - a logpoint, use the logpoints delete command: - - $ gcloud beta debug logpoints delete product.* - - The above command would delete all logpoints in any file whose name begins - with "product". If you want to delete only a single logpoint, you should - first determine the logpoint ID using the logpoints list command, then - delete that specific ID: - - $ gcloud beta debug logpoints list ID LOCATION ... \ - 567890abcdef1-1234-56789 product.py:123 ... - $ gcloud beta debug logpoints delete 567890abcdef1-1234-56789 - - For App Engine services, logpoint resources include the "logQuery" - property, which is suitable for use with the "gcloud beta logging read" - command. You can save this property's value and use it to read logs from - the command line: - - $ log_query=$(gcloud beta debug logpoints create product.py:123 \ - "No description for {product.name}" --format="value(logQuery)") - $ gcloud logging read "$log_query" - -FLAGS - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - -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) (DEPRECATED) Add debug logpoints to a Cloud Debugger debug - target (debuggee). - - delete - (BETA) (DEPRECATED) Delete debug logpoints for a Cloud Debugger debug - target (debuggee). - - list - (BETA) (DEPRECATED) List the debug logpoints for a Cloud Debugger debug - target (debuggee). - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud debug logpoints - diff --git a/gcloud/beta/debug/logpoints/list b/gcloud/beta/debug/logpoints/list deleted file mode 100644 index 7203d9ac2..000000000 --- a/gcloud/beta/debug/logpoints/list +++ /dev/null @@ -1,105 +0,0 @@ -NAME - gcloud beta debug logpoints list - list the debug logpoints for a Cloud - Debugger debug target (debuggee) - -SYNOPSIS - gcloud beta debug logpoints list [ID ...] [--no-all-users] - [--include-inactive=INCLUDE_INACTIVE; default=300] - [--location=LOCATION-REGEXP] [--target=(ID|DESCRIPTION_REGEXP)] - [--filter=EXPRESSION] [--limit=LIMIT] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May - 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud beta debug logpoints list is used to display the debug logpoints for - a Cloud Debugger debug target (debuggee). By default all active logpoints - are returned. To obtain older, expired logoints, specify the - --include-inactive option. - -EXAMPLES - To list the active and recently completed debug logpoints of the debug - target (debuggee), run: - - $ gcloud beta debug logpoints list --target= - - To list all (both active and inactive) logpoints of the debug target - (debuggee), run: - - $ gcloud beta debug logpoints list --target= \ - --include-inactive=unlimited - - To list logpoints only created by the current user (by default all users - are returned) of the debug target (debuggee), run: - - $ gcloud beta debug logpoints list --target= \ - --no-all-users - -POSITIONAL ARGUMENTS - [ID ...] - Zero or more logpoint resource identifiers. The specified logpoints - will be listed. - -FLAGS - --all-users - If false, display only logpoints created by the current user. Enabled - by default, use --no-all-users to disable. - - --include-inactive=INCLUDE_INACTIVE; default=300 - Include logpoints which failed or expired in the last INCLUDE_INACTIVE - seconds. If the value is "unlimited", all failed or expired logpoints - will be included. - - --location=LOCATION-REGEXP - A regular expression to match against logpoint locations. All logpoints - matching this value will be listed. You may specify --location multiple - times. - - EXAMPLE: - - gcloud beta debug logpoints list \ - --location foo.py:[1-3] --location bar.py:4 - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - -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. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud debug logpoints list - diff --git a/gcloud/beta/debug/snapshots/create b/gcloud/beta/debug/snapshots/create deleted file mode 100644 index eb7172660..000000000 --- a/gcloud/beta/debug/snapshots/create +++ /dev/null @@ -1,96 +0,0 @@ -NAME - gcloud beta debug snapshots create - create debug snapshots for a Cloud - Debugger debug target (debuggee) - -SYNOPSIS - gcloud beta debug snapshots create LOCATION [--condition=CONDITION] - [--expression=EXPRESSION] [--target=(ID|DESCRIPTION_REGEXP)] - [--wait=WAIT; default=10] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May - 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud beta debug snapshots create is used to create a debug snapshot on a - Cloud Debugger debug target. Snapshots allow you to capture stack traces - and local variables from your running service without interfering with - normal operations. - - When any instance of the target executes the snapshot location, the - optional condition expression is evaluated. If the result is true (or if - there is no condition), the instance captures the current thread state and - reports it back to Cloud Debugger. Once any instance captures a snapshot, - the snapshot is marked as completed, and it will not be captured again. - - You can view snapshot results in the developer console. It is also possible - to inspect snapshot results with the "snapshots describe" command. - -EXAMPLES - To create a snapshot with no conditions or expressions at line 41 of file - main.py of a debug target (debuggee), run: - - $ gcloud beta debug snapshots create main.py:41 \ - --target= - - To create a snapshot at line 41 of file main.py on a debug target - (debuggee) that will only trigger if the variable name has the value of - 'foo', run: - - $ gcloud beta debug snapshots create main.py:41 \ - --target= --condition="name == 'foo'" - - To create a snapshot at line 41 of file main.py on a debug target - (debuggee) with the expressions name[0] and name[1], run: - - $ gcloud beta debug snapshots create main.py:41 \ - --target= --expression="name[0]" \ - --expression="name[1]" - -POSITIONAL ARGUMENTS - LOCATION - The location where the snapshot should be taken. Locations are of the - form FILE:LINE, where FILE can be simply the file name, or the file - name preceded by enough path components to differntiate it from other - files with the same name. If the file name is not unique in the debug - target, the behavior is unspecified. - -FLAGS - --condition=CONDITION - A condition to restrict when the snapshot is taken. When the snapshot - location is executed, the condition will be evaluated, and the snapshot - will be generated only if the condition is true. - - --expression=EXPRESSION - An expression to evaluate when the snapshot is taken. You may specify - --expression multiple times. - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - - --wait=WAIT; default=10 - The number of seconds to wait to ensure that no error is returned from - a debugger agent when creating the snapshot. When a snapshot is - created, there will be a delay before the agents see and apply the - snapshot. Until at least one agent has attempted to enable the - snapshot, it cannot be determined if the snapshot is valid. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 debug snapshots create - diff --git a/gcloud/beta/debug/snapshots/delete b/gcloud/beta/debug/snapshots/delete deleted file mode 100644 index aaad77def..000000000 --- a/gcloud/beta/debug/snapshots/delete +++ /dev/null @@ -1,83 +0,0 @@ -NAME - gcloud beta debug snapshots delete - delete debug snapshots for a Cloud - Debugger debug target (debuggee) - -SYNOPSIS - gcloud beta debug snapshots delete [ID ...] [--all-users] - [--include-inactive] [--location=LOCATION-REGEXP] - [--target=(ID|DESCRIPTION_REGEXP)] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May - 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud beta debug snapshots delete is used to delete snapshots from a Cloud - Debugger debug target (debuggee). It will ask for confirmation before - deleting any snapshots. To suppress confirmation, use the global --quiet - option. - -EXAMPLES - To delete all active snapshots created by the current user of the debug - target (debuggee), without being prompted for confirmation, run: - - $ gcloud beta debug snapshots delete --target= --quiet - - To delete all active and inactive snapshots created by all users of the - debug target (debuggee), run: - - $ gcloud beta debug snapshots delete --target= \ - --all-users --include-inactive - - To delete the debug snapshots with IDs 'ID1' and 'ID2' (where ID1 and ID2 - were each created by different users) of the debug target (debuggee), run: - - $ gcloud beta debug snapshots delete ID1 ID2 \ - --target= --all-users - -POSITIONAL ARGUMENTS - [ID ...] - Zero or more snapshot resource identifiers. The specified snapshots - will be deleted. - -FLAGS - --all-users - If set, matching snapshots from all users will be deleted, rather than - only snapshots created by the current user. - - --include-inactive - If set, also delete snapshots which have been completed. By default, - only pending snapshots will be deleted. - - --location=LOCATION-REGEXP - A regular expression to match against snapshot locations. All snapshots - matching this value will be deleted. You may specify --location - multiple times. - - EXAMPLE: - - gcloud beta debug snapshots delete \ - --location foo.py:[1-3] --location bar.py:4 - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and 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 beta and might change without notice. This - variant is also available: - - $ gcloud debug snapshots delete - diff --git a/gcloud/beta/debug/snapshots/describe b/gcloud/beta/debug/snapshots/describe deleted file mode 100644 index 8b1496f53..000000000 --- a/gcloud/beta/debug/snapshots/describe +++ /dev/null @@ -1,69 +0,0 @@ -NAME - gcloud beta debug snapshots describe - describe the debug snapshots for a - Cloud Debugger debug target (debuggee) - -SYNOPSIS - gcloud beta debug snapshots describe [ID ...] [--location=LOCATION-REGEXP] - [--target=(ID|DESCRIPTION_REGEXP)] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May - 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud beta debug snapshots describe is used to describe the debug - snapshots for a Cloud Debugger debug target (debuggee). If the snapshot has - completed, the output will include details on the stack trace and local - variables, stored in a compact form which is primarily intended to be - machine-readable rather than human-readable. - -EXAMPLES - To describe the debug snapshots for snapshots with IDs 'ID1' and 'ID2' of - the debug target (debuggee), run: - - $ gcloud beta debug snapshots describe ID1 ID2 --target= - - To describe all active snapshots in file main.py of the debug target - (debuggee), run: - - $ gcloud beta debug snapshots describe --target= \ - --location="main.py:.*" - -POSITIONAL ARGUMENTS - [ID ...] - Zero or more snapshot resource identifiers. The specified snapshots - will be displayed. - -FLAGS - --location=LOCATION-REGEXP - A regular expression to match against snapshot locations. All snapshots - matching this value will be displayed. You may specify --location - multiple times. - - EXAMPLE: - - gcloud beta debug snapshots describe \ - --location foo.py:[1-3] --location bar.py:4 - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and 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 beta and might change without notice. This - variant is also available: - - $ gcloud debug snapshots describe - diff --git a/gcloud/beta/debug/snapshots/help b/gcloud/beta/debug/snapshots/help deleted file mode 100644 index 6fd897988..000000000 --- a/gcloud/beta/debug/snapshots/help +++ /dev/null @@ -1,61 +0,0 @@ -NAME - gcloud beta debug snapshots - commands for interacting with Cloud Debugger - snapshots - -SYNOPSIS - gcloud beta debug snapshots COMMAND [--target=(ID|DESCRIPTION_REGEXP)] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Commands for interacting with Cloud Debugger snapshots. - - Cloud Debugger is deprecated and will be shutdown May 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - Commands to interact with debug snapshots. Snapshots allow you to capture - stack traces and local variables from running services without interfering - with the normal function of the service. - -FLAGS - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - -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) (DEPRECATED) Create debug snapshots for a Cloud Debugger debug - target (debuggee). - - delete - (BETA) (DEPRECATED) Delete debug snapshots for a Cloud Debugger debug - target (debuggee). - - describe - (BETA) (DEPRECATED) Describe the debug snapshots for a Cloud Debugger - debug target (debuggee). - - list - (BETA) (DEPRECATED) List the debug snapshots for a Cloud Debugger debug - target (debuggee). - - wait - (BETA) (DEPRECATED) Wait for debug snapshots on a Cloud Debugger debug - target (debuggee) to complete. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud debug snapshots - diff --git a/gcloud/beta/debug/snapshots/list b/gcloud/beta/debug/snapshots/list deleted file mode 100644 index ef86c94de..000000000 --- a/gcloud/beta/debug/snapshots/list +++ /dev/null @@ -1,103 +0,0 @@ -NAME - gcloud beta debug snapshots list - list the debug snapshots for a Cloud - Debugger debug target (debuggee) - -SYNOPSIS - gcloud beta debug snapshots list [ID ...] [--all-users] - [--include-inactive=INCLUDE_INACTIVE; default=300] - [--location=LOCATION-REGEXP] [--target=(ID|DESCRIPTION_REGEXP)] - [--filter=EXPRESSION] [--limit=LIMIT] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May - 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud beta debug snapshots list is used to display the debug snapshots for - a Cloud Debugger debug target (debuggee). By default all active snapshots - as well as any recently completed snapshots are returned. To obtain older - completed snapshots specify the --include-inactive option. - -EXAMPLES - To list the active and recently completed debug snapshots of the debug - target (debuggee), run: - - $ gcloud beta debug snapshots list --target= - - To list all (both active and inactive) snapshots of the debug target - (debuggee), run: - - $ gcloud beta debug snapshots list --include-inactive=unlimited \ - --target= - - To list snapshots created by all users of the debug target (debuggee), run: - - $ gcloud beta debug snapshots list --all-users --target= - -POSITIONAL ARGUMENTS - [ID ...] - Zero or more snapshot resource identifiers. The specified snapshots - will be displayed. - -FLAGS - --all-users - If set, display snapshots from all users, rather than only the current - user. - - --include-inactive=INCLUDE_INACTIVE; default=300 - Include snapshots which have completed in the last INCLUDE_INACTIVE - seconds. If the value is "unlimited", all inactive snapshots will be - included. - - --location=LOCATION-REGEXP - A regular expression to match against snapshot locations. All snapshots - matching this value will be displayed. You may specify --location - multiple times. - - EXAMPLE: - - gcloud beta debug snapshots list \ - --location foo.py:[1-3] --location bar.py:4 - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - -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. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud debug snapshots list - diff --git a/gcloud/beta/debug/snapshots/wait b/gcloud/beta/debug/snapshots/wait deleted file mode 100644 index d2edf8200..000000000 --- a/gcloud/beta/debug/snapshots/wait +++ /dev/null @@ -1,107 +0,0 @@ -NAME - gcloud beta debug snapshots wait - wait for debug snapshots on a Cloud - Debugger debug target (debuggee) to complete - -SYNOPSIS - gcloud beta debug snapshots wait [ID ...] [--all] [--all-users] - [--location=LOCATION-REGEXP] [--target=(ID|DESCRIPTION_REGEXP)] - [--timeout=TIMEOUT; default="unlimited"] [--filter=EXPRESSION] - [--limit=LIMIT] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May - 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud beta debug snapshots wait is used to wait for one or more snapshots - on a Cloud Debugger debug target to complete. A snapshot is considered - completed either if there was an error setting the snapshot or if the - snapshot was hit on an instance of the debug target. - -EXAMPLES - To wait for either of the snapshots with IDs of 'ID1' or 'ID2' of the debug - target (debuggee) to complete, run: - - $ gcloud beta debug snapshots wait ID1 ID2 --target= - - To wait for both of the snapshots with IDs 'ID1' and 'ID2' of the debug - target (debuggee) to complete, run: - - $ gcloud beta debug snapshots wait ID1 ID2 --target= \ - --all - - To wait up to 30 seconds for the snapshot with ID 'ID1' of the debug target - (debuggee) to complete, run: - - $ gcloud beta debug snapshots wait ID1 --target= \ - --timeout=30 - -POSITIONAL ARGUMENTS - [ID ...] - Zero or more snapshot resource identifiers. The command will wait for - any of the specified snapshots to complete. - -FLAGS - --all - If set, wait for all of the specified snapshots to complete, instead of - waiting for any one of them to complete. - - --all-users - If set, wait for matching snapshots from all users, rather than only - the current user. - - --location=LOCATION-REGEXP - A regular expression to match against snapshot locations. The command - will wait for any snapshots matching these criteria to complete. You - may specify --location multiple times. - - EXAMPLE: - - gcloud beta debug snapshots wait \ - --location foo.py:[1-3] --location bar.py:3 - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - - --timeout=TIMEOUT; default="unlimited" - Maximum number of seconds to wait for a snapshot to complete. By - default, wait indefinitely. - -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. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud debug snapshots wait - diff --git a/gcloud/beta/debug/source/gen-repo-info-file b/gcloud/beta/debug/source/gen-repo-info-file deleted file mode 100644 index 595f59135..000000000 --- a/gcloud/beta/debug/source/gen-repo-info-file +++ /dev/null @@ -1,47 +0,0 @@ -NAME - gcloud beta debug source gen-repo-info-file - generates repository - information files for the Cloud Debugger - -SYNOPSIS - gcloud beta debug source gen-repo-info-file - [--output-directory=OUTPUT_DIRECTORY; default="."] - [--source-directory=SOURCE_DIRECTORY; default="."] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May - 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - This command generates a file named source-context.json containing - information on the source revision and remote repository associated with - the given source directory. - -EXAMPLES - To generate repository information files for your app, from your source - directory run: - - $ gcloud beta debug source gen-repo-info-file - -FLAGS - --output-directory=OUTPUT_DIRECTORY; default="." - The directory in which to create the source context file. - - --source-directory=SOURCE_DIRECTORY; default="." - The directory containing the source code for the build. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 debug source gen-repo-info-file - diff --git a/gcloud/beta/debug/source/help b/gcloud/beta/debug/source/help deleted file mode 100644 index 769d3dc3b..000000000 --- a/gcloud/beta/debug/source/help +++ /dev/null @@ -1,36 +0,0 @@ -NAME - gcloud beta debug source - commands to manage source information for Cloud - Debugger - -SYNOPSIS - gcloud beta debug source COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Commands to manage source information for Cloud - Debugger. - - Cloud Debugger is deprecated and will be shutdown May 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - This set of commands allows you to provide Cloud Debugger with source code - version information. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - gen-repo-info-file - (BETA) (DEPRECATED) Generates repository information files for the - Cloud Debugger. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud debug source - diff --git a/gcloud/beta/debug/targets/help b/gcloud/beta/debug/targets/help deleted file mode 100644 index 70e31f6a6..000000000 --- a/gcloud/beta/debug/targets/help +++ /dev/null @@ -1,42 +0,0 @@ -NAME - gcloud beta debug targets - commands for interacting with Cloud Debugger - debug targets - -SYNOPSIS - gcloud beta debug targets COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (BETA) (DEPRECATED) Commands for interacting with Cloud Debugger debug - targets. - - Cloud Debugger is deprecated and will be shutdown May 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - Commands to interact with debug targets. A debug target can be an App - Engine module version or any other entity enabled for use with the cloud - debugger. - -EXAMPLES - To view all available debug targets, run: - - $ gcloud beta debug targets list - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - list - (BETA) (DEPRECATED) List the debug targets (debuggees) registered with - the Cloud Debugger. - -NOTES - This command is currently in beta and might change without notice. This - variant is also available: - - $ gcloud debug targets - diff --git a/gcloud/beta/healthcare/dicom-stores/create b/gcloud/beta/healthcare/dicom-stores/create index 39d14abcf..e70fb96ae 100644 --- a/gcloud/beta/healthcare/dicom-stores/create +++ b/gcloud/beta/healthcare/dicom-stores/create @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud beta healthcare dicom-stores create (DICOM_STORE : --dataset=DATASET --location=LOCATION) - [--pubsub-topic=PUBSUB_TOPIC : --send-for-bulk-import] - [GCLOUD_WIDE_FLAG ...] + [--pubsub-topic=PUBSUB_TOPIC] [--send-for-bulk-import] + [--stream-configs=STREAM_CONFIGS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a Cloud Healthcare API DICOM store. @@ -77,6 +77,13 @@ FLAGS Indicates whether or not to send Cloud Pub/Sub notifications on bulk import. Only supported for DICOM imports. + --stream-configs=STREAM_CONFIGS + The configuration that indicates the BigQuery destinations for + streaming instances of a DICOM store. To specify StreamConfigs, list + all BigQuery destinations into one string separated by comma. (e.g., + --stream-configs + bq://{bigqueryProjectId1}.{bigqueryDatasetId1}.{bigqueryTableId1},bq://{bigqueryProjectId2}.{bigqueryDatasetId2}.{bigqueryTableId2}). + 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/healthcare/dicom-stores/update b/gcloud/beta/healthcare/dicom-stores/update index 48cc23e49..25a83c172 100644 --- a/gcloud/beta/healthcare/dicom-stores/update +++ b/gcloud/beta/healthcare/dicom-stores/update @@ -5,8 +5,8 @@ NAME SYNOPSIS gcloud beta healthcare dicom-stores update (DICOM_STORE : --dataset=DATASET --location=LOCATION) - [--pubsub-topic=PUBSUB_TOPIC : --send-for-bulk-import] - [GCLOUD_WIDE_FLAG ...] + [--pubsub-topic=PUBSUB_TOPIC] [--send-for-bulk-import] + [--stream-configs=STREAM_CONFIGS] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Update a Cloud Healthcare API DICOM store. @@ -71,6 +71,13 @@ FLAGS Indicates whether or not to send Cloud Pub/Sub notifications on bulk import. Only supported for DICOM imports. + --stream-configs=STREAM_CONFIGS + The configuration that indicates the BigQuery destinations for + streaming instances of a DICOM store. To specify StreamConfigs, list + all BigQuery destinations into one string separated by comma. (e.g., + --stream-configs + bq://{bigqueryProjectId1}.{bigqueryDatasetId1}.{bigqueryTableId1},bq://{bigqueryProjectId2}.{bigqueryDatasetId2}.{bigqueryTableId2}). + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/iam/workforce-pools/providers/create-oidc b/gcloud/beta/iam/workforce-pools/providers/create-oidc index a4650abe4..483593287 100644 --- a/gcloud/beta/iam/workforce-pools/providers/create-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/create-oidc @@ -6,12 +6,12 @@ SYNOPSIS gcloud beta iam workforce-pools providers create-oidc (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL) --attribute-mapping=[ATTRIBUTE_MAPPING,...] --client-id=CLIENT_ID - --issuer-uri=ISSUER_URI [--async] - [--attribute-condition=ATTRIBUTE_CONDITION] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] - [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR, - [...]] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] - [GCLOUD_WIDE_FLAG ...] + --issuer-uri=ISSUER_URI + (--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE) [--async] + [--attribute-condition=ATTRIBUTE_CONDITION] + [--client-secret-value=CLIENT_SECRET_VALUE] [--description=DESCRIPTION] + [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Create a new OIDC workforce pool provider. @@ -146,6 +146,42 @@ REQUIRED FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. + This must be specified. + + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR + The behavior for how OIDC Claims are included in the assertion object + used for attribute mapping and attribute condition. + + Use merge-user-info-over-id-token-claims to merge the UserInfo + Endpoint Claims with ID Token Claims, preferring UserInfo Claim + Values for the same Claim Name. Currently this option is only + available for Authorization Code flow. + + Use only-id-token-claims to include only ID token claims. + + WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be one of: + assertion-claims-behavior-unspecified, + merge-user-info-over-id-token-claims, only-id-token-claims. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE + Response Type to request for in the OIDC Authorization Request for + web sign-in. + + Use code to select the authorization code flow + (https://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth) + + Use id-token to select the implicit flow + (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). + + WEB_SSO_RESPONSE_TYPE must be one of: code, id-token, + response-type-unspecified. + + This flag argument must be specified if any of the other arguments in + this group are specified. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to @@ -178,6 +214,10 @@ OPTIONAL FLAGS "'admins' in google.groups" + --client-secret-value=CLIENT_SECRET_VALUE + The OIDC client secret. Required to enable Authorization Code flow for + web sign-in. + --description=DESCRIPTION A description for the workforce pool provider. Cannot exceed 256 characters in length. @@ -192,19 +232,6 @@ OPTIONAL FLAGS A display name for the workforce pool provider. Cannot exceed 32 characters in length. - --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR,[...] - The behavior for how OIDC Claims are included in the assertion object - used for attribute mapping and attribute condition. Use - only-id-token-claims to include only ID token claims. - WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be (only one value is - supported): only-id-token-claims. - - --web-sso-response-type=WEB_SSO_RESPONSE_TYPE - Response Type to request for in the OIDC Authorization Request for web - sign-in. Use id-token to select the implicit flow - (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). - WEB_SSO_RESPONSE_TYPE must be (only one value is supported): id-token. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/iam/workforce-pools/providers/update-oidc b/gcloud/beta/iam/workforce-pools/providers/update-oidc index 9dc397987..b30eb3e01 100644 --- a/gcloud/beta/iam/workforce-pools/providers/update-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/update-oidc @@ -9,8 +9,9 @@ SYNOPSIS [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] [--client-id=CLIENT_ID] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] [--issuer-uri=ISSUER_URI] - [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR, - [...]] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] + [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] + [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] + [--clear-client-secret | --client-secret-value=CLIENT_SECRET_VALUE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -191,18 +192,34 @@ FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. - --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR,[...] + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR The behavior for how OIDC Claims are included in the assertion object used for attribute mapping and attribute condition. Use - only-id-token-claims to include only ID token claims. - WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be (only one value is - supported): only-id-token-claims. + merge-user-info-over-id-token-claims to merge the UserInfo Endpoint + Claims with ID Token Claims, preferring UserInfo Claim Values for the + same Claim Name. Currently this option is only available for + Authorization Code flow. Use only-id-token-claims to include only ID + token claims. WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be one of: + assertion-claims-behavior-unspecified, + merge-user-info-over-id-token-claims, only-id-token-claims. --web-sso-response-type=WEB_SSO_RESPONSE_TYPE Response Type to request for in the OIDC Authorization Request for web - sign-in. Use id-token to select the implicit flow + sign-in. Use code to select the authorization code flow + (https://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth) + Use id-token to select the implicit flow (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). - WEB_SSO_RESPONSE_TYPE must be (only one value is supported): id-token. + WEB_SSO_RESPONSE_TYPE must be one of: code, id-token, + response-type-unspecified. + + At most one of these can be specified: + + --clear-client-secret + Clear the OIDC client secret. + + --client-secret-value=CLIENT_SECRET_VALUE + The OIDC client secret. Required to enable Authorization Code flow + for web sign-in. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/network-security/firewall-endpoint-associations/help b/gcloud/beta/network-security/firewall-endpoint-associations/help index a5ef75805..732a5e176 100644 --- a/gcloud/beta/network-security/firewall-endpoint-associations/help +++ b/gcloud/beta/network-security/firewall-endpoint-associations/help @@ -29,6 +29,9 @@ COMMANDS list (BETA) List Firewall Plus endpoint associations. + update + (BETA) Update a Firewall Plus endpoint association. + NOTES This command is currently in beta and might change without notice. This variant is also available: diff --git a/gcloud/beta/network-security/firewall-endpoint-associations/update b/gcloud/beta/network-security/firewall-endpoint-associations/update new file mode 100644 index 000000000..b17faeaa8 --- /dev/null +++ b/gcloud/beta/network-security/firewall-endpoint-associations/update @@ -0,0 +1,125 @@ +NAME + gcloud beta network-security firewall-endpoint-associations update - update + a Firewall Plus endpoint association + +SYNOPSIS + gcloud beta network-security firewall-endpoint-associations update + (FIREWALL_ENDPOINT_ASSOCIATION : --zone=ZONE) [--async] + [--max-wait=MAX_WAIT; default="60m"] [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a firewall endpoint association. Check the progress of + association update by using gcloud network-security + firewall-endpoint-associations describe. + + For more examples, refer to the EXAMPLES section below. + +EXAMPLES + To update labels k1 and k2, run: + + $ gcloud beta network-security firewall-endpoint-associations \ + update my-assoc --zone=us-central1-a --project=my-proj \ + --update-labels=k1=v1,k2=v2 + + To remove labels k3 and k4, run: + + $ gcloud beta network-security firewall-endpoint-associations \ + update my-assoc --zone=us-central1-a --project=my-proj \ + --remove-labels=k3,k4 + + To clear all labels from the firewall endpoint association, run: + + $ gcloud beta network-security firewall-endpoint-associations \ + update my-assoc --zone=us-central1-a --project=my-proj \ + --clear-labels + +POSITIONAL ARGUMENTS + Firewall endpoint association resource - Firewall Plus. 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 FIREWALL_ENDPOINT_ASSOCIATION on the command + line with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + FIREWALL_ENDPOINT_ASSOCIATION + ID of the firewall endpoint association or fully qualified identifier + for the firewall endpoint association. + + To set the association-name attribute: + ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --zone=ZONE + Zone of the firewall endpoint association. + + To set the zone attribute: + ▸ provide the argument FIREWALL_ENDPOINT_ASSOCIATION on the command + line with a fully specified name; + ▸ provide the argument --zone on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. The default is True. Enabled by default, use --no-async to + disable. + + --max-wait=MAX_WAIT; default="60m" + Time to synchronously wait for the operation to complete, after which + the operation continues asynchronously. Ignored if --no-async isn't + specified. See $ gcloud topic datetimes for information on time + formats. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta network-security firewall-endpoint-associations \ + update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta network-security firewall-endpoint-associations \ + update --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-security firewall-endpoint-associations update + diff --git a/gcloud/beta/network-services/help b/gcloud/beta/network-services/help index bb760891e..2e79a1bfc 100644 --- a/gcloud/beta/network-services/help +++ b/gcloud/beta/network-services/help @@ -21,6 +21,9 @@ GROUPS service-bindings (BETA) Manage Network Services Bindings. + service-lb-policies + (BETA) Manage Network Services ServiceLbPolicies. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/network-services/service-lb-policies/create b/gcloud/beta/network-services/service-lb-policies/create new file mode 100644 index 000000000..53c38b9d0 --- /dev/null +++ b/gcloud/beta/network-services/service-lb-policies/create @@ -0,0 +1,108 @@ +NAME + gcloud beta network-services service-lb-policies create - create a service + LB policy + +SYNOPSIS + gcloud beta network-services service-lb-policies create + (SERVICE_LB_POLICY : --location=LOCATION) [--async] + [--auto-capacity-drain] [--description=DESCRIPTION] + [--load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; + default="waterfall-by-region"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new service LB policy with the given name. + +EXAMPLES + Create a service LB policy with the name 'my-service-lb-policy', load + balancing algorithm 'waterfall-by-region', and location 'global'. + + $ gcloud beta network-services service-lb-policies create \ + my-service-lb-policy \ + --load-balancing-algorithm=waterfall-by-region \ + --location="global" + +POSITIONAL ARGUMENTS + Service lb policy resource - Name of the service LB policy to be created. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument service_lb_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_LB_POLICY + ID of the service lb policy or fully qualified identifier for the + service lb policy. + + To set the service_lb_policy attribute: + ▸ provide the argument service_lb_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument service_lb_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --auto-capacity-drain + If specified, an unhealthy MIG/NEG will be removed from Global load + balancing and traffic routing for the service. A MIG/NEG is considered + to be unhealthy if less than 25% of the instance/endpoints in the + MIG/NEG are healthy. autoCapacityDrain will never drain more than 50% + of the configured MIGs/NEGs of a Backend Service. + + --description=DESCRIPTION + The description for the service LB policy. + + --load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region" + The global load balancing algorithm to be used. + LOAD_BALANCING_ALGORITHM must be one of: + + spray-to-region + Spread the traffic from each client to all the MIGs/NEGs in a + region. + + spray-to-world + Balance traffic across all backends across the world proportionally + based on capacity. + + waterfall-by-region + Direct traffic to the nearest region with endpoints and capacity + before spilling over to other regions. + + waterfall-by-zone + Attempt to keep traffic in a single zone closest to the client, + before spilling over to other zones. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services service-lb-policies create + diff --git a/gcloud/beta/network-services/service-lb-policies/delete b/gcloud/beta/network-services/service-lb-policies/delete new file mode 100644 index 000000000..49930e348 --- /dev/null +++ b/gcloud/beta/network-services/service-lb-policies/delete @@ -0,0 +1,73 @@ +NAME + gcloud beta network-services service-lb-policies delete - delete service LB + policy + +SYNOPSIS + gcloud beta network-services service-lb-policies delete + (SERVICE_LB_POLICY : --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete the specified service LB policy. + +EXAMPLES + To delete a service LB policy named my-service-lb-policy, run: + + $ gcloud beta network-services service-lb-policies delete \ + my-service-lb-policy --location=global + +POSITIONAL ARGUMENTS + Service lb policy resource - Name of the service LB policy you want to + delete. The arguments in this group can be used to specify the attributes + of this resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument service_lb_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_LB_POLICY + ID of the service lb policy or fully qualified identifier for the + service lb policy. + + To set the service_lb_policy attribute: + ▸ provide the argument service_lb_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument service_lb_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services service-lb-policies delete + diff --git a/gcloud/beta/network-services/service-lb-policies/describe b/gcloud/beta/network-services/service-lb-policies/describe new file mode 100644 index 000000000..3734035e6 --- /dev/null +++ b/gcloud/beta/network-services/service-lb-policies/describe @@ -0,0 +1,67 @@ +NAME + gcloud beta network-services service-lb-policies describe - describe a + service LB policy + +SYNOPSIS + gcloud beta network-services service-lb-policies describe + (SERVICE_LB_POLICY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show details of a service LB policy. + +EXAMPLES + Show details about a service LB policy named 'my-service-lb-policy'. + + $ gcloud beta network-services service-lb-policies describe \ + my-service-lb-policy --location=global + +POSITIONAL ARGUMENTS + Service lb policy resource - Name of the service LB policy to be + described. 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 service_lb_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_LB_POLICY + ID of the service lb policy or fully qualified identifier for the + service lb policy. + + To set the service_lb_policy attribute: + ▸ provide the argument service_lb_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument service_lb_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services service-lb-policies describe + diff --git a/gcloud/beta/network-services/service-lb-policies/export b/gcloud/beta/network-services/service-lb-policies/export new file mode 100644 index 000000000..a7d0c0de4 --- /dev/null +++ b/gcloud/beta/network-services/service-lb-policies/export @@ -0,0 +1,78 @@ +NAME + gcloud beta network-services service-lb-policies export - export service LB + policy + +SYNOPSIS + gcloud beta network-services service-lb-policies export + (SERVICE_LB_POLICY : --location=LOCATION) [--destination=DESTINATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Export a service LB policy. + +EXAMPLES + To export a service LB policy named my-service-lb-policy to a YAML file, + run: + + $ gcloud beta network-services service-lb-policies export \ + my-service-lb-policy --destination=my-service-lb-policy.yaml \ + --location=global + +POSITIONAL ARGUMENTS + Service lb policy resource - Name of the service LB policy to export. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument service_lb_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_LB_POLICY + ID of the service lb policy or fully qualified identifier for the + service lb policy. + + To set the service_lb_policy attribute: + ▸ provide the argument service_lb_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument service_lb_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --destination=DESTINATION + Path to a YAML file where the configuration will be exported. The + exported data will not contain any output-only fields. Alternatively, + you may omit this flag to write to standard output. For a schema + describing the export/import format, see + $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services service-lb-policies export + diff --git a/gcloud/beta/network-services/service-lb-policies/help b/gcloud/beta/network-services/service-lb-policies/help new file mode 100644 index 000000000..2317a74eb --- /dev/null +++ b/gcloud/beta/network-services/service-lb-policies/help @@ -0,0 +1,46 @@ +NAME + gcloud beta network-services service-lb-policies - manage Network Services + ServiceLbPolicies + +SYNOPSIS + gcloud beta network-services service-lb-policies COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Network Services ServiceLbPolicies. + +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 service LB policy. + + delete + (BETA) Delete service LB policy. + + describe + (BETA) Describe a service LB policy. + + export + (BETA) Export service LB policy. + + import + (BETA) Import service LB policy. + + list + (BETA) List ServiceLbPolicies. + + update + (BETA) Update a service LB policy. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services service-lb-policies + diff --git a/gcloud/beta/network-services/service-lb-policies/import b/gcloud/beta/network-services/service-lb-policies/import new file mode 100644 index 000000000..02c7e70e4 --- /dev/null +++ b/gcloud/beta/network-services/service-lb-policies/import @@ -0,0 +1,85 @@ +NAME + gcloud beta network-services service-lb-policies import - import service LB + policy + +SYNOPSIS + gcloud beta network-services service-lb-policies import + (SERVICE_LB_POLICY : --location=LOCATION) [--async] [--source=SOURCE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Import a service LB policy. + +EXAMPLES + To import a service LB policy named my-service-lb-policy from a YAML file, + run: + + $ gcloud beta network-services service-lb-policies import \ + my-service-lb-policy --source=my-service-lb-policy.yaml \ + --location=global + +POSITIONAL ARGUMENTS + Service lb policy resource - Name of the service LB policy to import. The + arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument service_lb_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_LB_POLICY + ID of the service lb policy or fully qualified identifier for the + service lb policy. + + To set the service_lb_policy attribute: + ▸ provide the argument service_lb_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument service_lb_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --source=SOURCE + Path to a YAML file containing the configuration export data. The YAML + file must not contain any output-only fields. Alternatively, you may + omit this flag to read from standard input. For a schema describing the + export/import format, see: $CLOUDSDKROOT/lib/googlecloudsdk/schemas/... + + $CLOUDSDKROOT is can be obtained with the following command: + + $ gcloud info --format='value(installation.sdk_root)' + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services service-lb-policies import + diff --git a/gcloud/beta/network-services/service-lb-policies/list b/gcloud/beta/network-services/service-lb-policies/list new file mode 100644 index 000000000..3f87aa9d8 --- /dev/null +++ b/gcloud/beta/network-services/service-lb-policies/list @@ -0,0 +1,88 @@ +NAME + gcloud beta network-services service-lb-policies list - list + ServiceLbPolicies + +SYNOPSIS + gcloud beta network-services service-lb-policies list --location=LOCATION + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all ServiceLbPolicies in the specified location of the current + project. + +EXAMPLES + To list service lb policies in the current project, run: + + $ gcloud beta network-services service-lb-policies list \ + --location=global + +REQUIRED FLAGS + Location resource - The project of the service LB policies to display. + This represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. + + To set the location attribute: + ▸ provide the argument --location on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services service-lb-policies list + diff --git a/gcloud/beta/network-services/service-lb-policies/update b/gcloud/beta/network-services/service-lb-policies/update new file mode 100644 index 000000000..599c7a837 --- /dev/null +++ b/gcloud/beta/network-services/service-lb-policies/update @@ -0,0 +1,107 @@ +NAME + gcloud beta network-services service-lb-policies update - update a service + LB policy + +SYNOPSIS + gcloud beta network-services service-lb-policies update + (SERVICE_LB_POLICY : --location=LOCATION) [--async] + [--auto-capacity-drain] [--description=DESCRIPTION] + [--load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; + default="waterfall-by-region"] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the detail of a service LB Policy. + +EXAMPLES + Update load-balancing-algorithm of a service LB policy named + my-service-lb-policy: + + $ gcloud beta network-services service-lb-policies update \ + my-service-lb-policy \ + --load-balancing-algorithm=waterfall-by-zone + +POSITIONAL ARGUMENTS + Service lb policy resource - Name of the service LB policy to be updated. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument service_lb_policy on the command line with a + fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_LB_POLICY + ID of the service lb policy or fully qualified identifier for the + service lb policy. + + To set the service_lb_policy attribute: + ▸ provide the argument service_lb_policy on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location Id. + + To set the location attribute: + ▸ provide the argument service_lb_policy on the command line with a + fully specified name; + ▸ provide the argument --location on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --auto-capacity-drain + If specified, an unhealthy MIG/NEG will be removed from Global load + balancing and traffic routing for the service. A MIG/NEG is considered + to be unhealthy if less than 25% of the instance/endpoints in the + MIG/NEG are healthy. autoCapacityDrain will never drain more than 50% + of the configured MIGs/NEGs of a Backend Service. + + --description=DESCRIPTION + The description for the service LB policy. + + --load-balancing-algorithm=LOAD_BALANCING_ALGORITHM; default="waterfall-by-region" + The global load balancing algorithm to be used. + LOAD_BALANCING_ALGORITHM must be one of: + + spray-to-region + Spread the traffic from each client to all the MIGs/NEGs in a + region. + + spray-to-world + Balance traffic across all backends across the world proportionally + based on capacity. + + waterfall-by-region + Direct traffic to the nearest region with endpoints and capacity + before spilling over to other regions. + + waterfall-by-zone + Attempt to keep traffic in a single zone closest to the client, + before spilling over to other zones. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkservices/v1beta1 API. The full documentation + for this API can be found at: https://cloud.google.com/networking + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha network-services service-lb-policies update + diff --git a/gcloud/beta/recommender/insights/list b/gcloud/beta/recommender/insights/list index 56710330a..a04acf341 100644 --- a/gcloud/beta/recommender/insights/list +++ b/gcloud/beta/recommender/insights/list @@ -2,16 +2,16 @@ NAME gcloud beta recommender insights list - list insights for a cloud entity SYNOPSIS - gcloud beta recommender insights list --insight-type=INSIGHT_TYPE - --location=LOCATION + gcloud beta recommender insights list --location=LOCATION (--billing-account=BILLING_ACCOUNT | --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID) - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--insight-type=INSIGHT_TYPE] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command will list all insights for a given cloud entity, - location and insight type. Supported insight-types can be found here: + (BETA) This command lists all insights for a given cloud entity, location + and insight type. Supported insight-types can be found here: https://cloud.google.com/recommender/docs/insights/insight-types. Currently the following cloud_entity_types are supported: project, billing_account, folder and organization. @@ -23,10 +23,6 @@ EXAMPLES --location=global --insight-type=google.compute.firewall.Insight REQUIRED FLAGS - --insight-type=INSIGHT_TYPE - Insight type to list insights for. Supported insight-types can be found - here: https://cloud.google.com/recommender/docs/insights/insight-types - --location=LOCATION Location @@ -50,6 +46,11 @@ REQUIRED FLAGS The Google Cloud Platform project ID. Overrides the default core/project property value for this command invocation. +FLAGS + --insight-type=INSIGHT_TYPE + Insight type to list insights for. Supported insight-types can be found + here: https://cloud.google.com/recommender/docs/insights/insight-types + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/recommender/recommendations/list b/gcloud/beta/recommender/recommendations/list index 8a52fd73e..916cb92bc 100644 --- a/gcloud/beta/recommender/recommendations/list +++ b/gcloud/beta/recommender/recommendations/list @@ -4,18 +4,18 @@ NAME SYNOPSIS gcloud beta recommender recommendations list --location=LOCATION - --recommender=RECOMMENDER (--billing-account=BILLING_ACCOUNT | --folder=FOLDER_ID | --organization=ORGANIZATION_ID | --project=PROJECT_ID) - [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] - [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + [--recommender=RECOMMENDER] [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) This command will list all recommendations for a given - cloud_entity_id, location and recommender. Supported recommenders can be - found here: https://cloud.google.com/recommender/docs/recommenders. - Currently the following cloud_entity_types are supported: project, - billing_account, folder and organization. + (BETA) This command lists all recommendations for a given cloud_entity_id, + location and recommender. Supported recommenders can be found here: + https://cloud.google.com/recommender/docs/recommenders. Currently the + following cloud_entity_types are supported: project, billing_account, + folder and organization. EXAMPLES Lists recommendations for a Cloud project. $ gcloud beta recommender recommendations list \ @@ -26,12 +26,6 @@ REQUIRED FLAGS --location=LOCATION Location - --recommender=RECOMMENDER - Recommender to list recommendations for. If no recommender is - specified, recommendations for all supported recommenders is listed. - Supported recommenders can be found here: - https://cloud.google.com/recommender/docs/recommenders - Resource that is associated with cloud entity type. Currently four mutually exclusive flags are supported, --project, --billing-account, --folder, --organization. @@ -52,6 +46,13 @@ REQUIRED FLAGS The Google Cloud Platform project ID. Overrides the default core/project property value for this command invocation. +FLAGS + --recommender=RECOMMENDER + Recommender to list recommendations for. If no recommender is + specified, recommendations for all supported recommenders is listed. + Supported recommenders can be found here: + https://cloud.google.com/recommender/docs/recommenders + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/redis/instances/update b/gcloud/beta/redis/instances/update index 202ceeb16..eb63b9567 100644 --- a/gcloud/beta/redis/instances/update +++ b/gcloud/beta/redis/instances/update @@ -175,6 +175,9 @@ FLAGS Redis version 5.0 and newer: stream-node-max-bytes, stream-node-max-entries. + Redis version 7.0 and newer: maxmemory-clients, lazyfree-lazy-eviction, + lazyfree-lazy-expire, lazyfree-lazy-user-del, lazyfree-lazy-user-flush. + At most one of these can be specified: --clear-labels diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 05042e1e7..a0e2d5c47 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -153,8 +153,8 @@ FLAGS Set a memory limit. Ex: 1024Mi, 4Gi. --min-instances=MIN_INSTANCES - The minimum number of container instances of the Service to run or - 'default' to remove any minimum. + The minimum number of container instances for this Revision of the + Service to run or 'default' to remove any minimum. --platform=PLATFORM; default="managed" Target platform for running commands. Alternatively, set the property diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 2a0ef08a0..41f959ea9 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -146,8 +146,8 @@ FLAGS Set a memory limit. Ex: 1024Mi, 4Gi. --min-instances=MIN_INSTANCES - The minimum number of container instances of the Service to run or - 'default' to remove any minimum. + The minimum number of container instances for this Revision of the + Service to run or 'default' to remove any minimum. --platform=PLATFORM; default="managed" Target platform for running commands. Alternatively, set the property diff --git a/gcloud/beta/scc/findings/create b/gcloud/beta/scc/findings/create index 6c9cfbf6c..ac620b4e1 100644 --- a/gcloud/beta/scc/findings/create +++ b/gcloud/beta/scc/findings/create @@ -14,30 +14,31 @@ DESCRIPTION (BETA) Create a Cloud Security Command Center finding. EXAMPLES - Create an ACTIVE my-finding with category: XSS_SCRIPTING attached to + Create an ACTIVE myFinding with category: XSS_SCRIPTING attached to example-project under organization 123456 and source 5678: - $ gcloud beta scc findings create my-finding --organization=123456 \ - --source=5678 --state=ACTIVE --category='XSS_SCRIPTING' \ + $ gcloud beta scc findings create `myFinding` \ + --organization=123456 --source=5678 --state=ACTIVE \ + --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' - Create an ACTIVE my-finding attached to example-project under project + Create an ACTIVE myFinding attached to example-project under project example-project and source 5678: $ gcloud beta scc findings create \ - projects/example-project/sources/5678/findings/my-finding \ + projects/example-project/sources/5678/findings/myFinding \ --state=ACTIVE --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' - Create an ACTIVE my-finding attached to example-project under folder 456 - and source 5678: + Create an ACTIVE myFinding attached to example-project under folder 456 and + source 5678: $ gcloud beta scc findings create \ - folders/456/sources/5678/findings/my-finding --state=ACTIVE \ + folders/456/sources/5678/findings/myFinding --state=ACTIVE \ --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ diff --git a/gcloud/beta/scc/findings/list-marks b/gcloud/beta/scc/findings/list-marks index ff8808465..6590a089f 100644 --- a/gcloud/beta/scc/findings/list-marks +++ b/gcloud/beta/scc/findings/list-marks @@ -12,22 +12,22 @@ DESCRIPTION (BETA) List a finding's security marks. EXAMPLES - List all security marks for my-finding under organization 123456 and source + List all security marks for myFinding under organization 123456 and source 5678: - $ gcloud beta scc findings list-marks my-finding \ + $ gcloud beta scc findings list-marks `myFinding` \ --organization=123456 --source=5678 - List all security marks for my-finding under project example-project and + List all security marks for myFinding under project example-project and source 5678: $ gcloud beta scc findings list-marks \ - projects/example-project/sources/5678/findings/my-finding + projects/example-project/sources/5678/findings/myFinding - List all security marks for my-finding under folder 456 and source 5678: + List all security marks for myFinding under folder 456 and source 5678: $ gcloud beta scc findings list-marks \ - folders/456/sources/5678/findings/my-finding + folders/456/sources/5678/findings/myFinding POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command diff --git a/gcloud/beta/scc/findings/update b/gcloud/beta/scc/findings/update index 75b996551..02ea57c64 100644 --- a/gcloud/beta/scc/findings/update +++ b/gcloud/beta/scc/findings/update @@ -13,33 +13,33 @@ DESCRIPTION (BETA) Update a Cloud Security Command Center finding. EXAMPLES - Update my-finding's state from ACTIVE to INACTIVE: + Update myFinding's state from ACTIVE to INACTIVE: - $ gcloud beta scc findings update my-finding --organization=123456 \ - --source=5678 --state=INACTIVE + $ gcloud beta scc findings update `myFinding` \ + --organization=123456 --source=5678 --state=INACTIVE - Update my-finding's state from ACTIVE to INACTIVE using project name for + Update myFinding's state from ACTIVE to INACTIVE using project name for example-project: $ gcloud beta scc findings update \ - projects/example-project/sources/5678/findings/my-finding \ + projects/example-project/sources/5678/findings/myFinding \ --state=INACTIVE - Update my-finding's state from ACTIVE to INACTIVE using folder name 456: + Update myFinding's state from ACTIVE to INACTIVE using folder name 456: $ gcloud beta scc findings update \ - folders/456/sources/5678/findings/my-finding --state=INACTIVE + folders/456/sources/5678/findings/myFinding --state=INACTIVE - Override all source properties on my-finding: + Override all source properties on myFinding: - $ gcloud beta scc findings update my-finding --organization=123456 \ - --source=5678 \ + $ gcloud beta scc findings update `myFinding` \ + --organization=123456 --source=5678 \ --source-properties="propKey1=propVal1,propKey2=propVal2" - Selectively update a specific source property on my-finding: + Selectively update a specific source property on myFinding: - $ gcloud beta scc findings update my-finding --organization=123456 \ - --source=5678 \ + $ gcloud beta scc findings update `myFinding` \ + --organization=123456 --source=5678 \ --source-properties="propKey1=propVal1,propKey2=propVal2" \ --update-mask="source_properties.propKey1" diff --git a/gcloud/beta/scc/findings/update-marks b/gcloud/beta/scc/findings/update-marks index ab53a6265..c07e2aa64 100644 --- a/gcloud/beta/scc/findings/update-marks +++ b/gcloud/beta/scc/findings/update-marks @@ -12,36 +12,36 @@ DESCRIPTION (BETA) Update Cloud Security Command Center finding's security marks. EXAMPLES - Selectively update security mark (Key1) with value (v1) on my-finding. Note - that other security marks on my-finding are untouched: + Selectively update security mark (Key1) with value (v1) on myFinding. Note + that other security marks on myFinding are untouched: - $ gcloud beta scc findings update-marks my-finding \ + $ gcloud beta scc findings update-marks `myFinding` \ --organization=123456 --source=5678 --security-marks="key1=v1" \ --update-mask="marks.markKey1" - Update all security marks on my-finding, under project example-project and + Update all security marks on myFinding, under project example-project and source 5678: $ gcloud beta scc findings update-marks \ - projects/example-project/sources/5678/findings/my-finding \ + projects/example-project/sources/5678/findings/myFinding \ --security-marks="key1=v1,key2=v2" - Update all security marks on my-finding, under folder 456 and source 5678: + Update all security marks on myFinding, under folder 456 and source 5678: $ gcloud beta scc findings update-marks \ - folders/456/sources/5678/findings/my-finding \ + folders/456/sources/5678/findings/myFinding \ --security-marks="key1=v1,key2=v2" - Update all security marks on my-finding, under organization 123456 and + Update all security marks on myFinding, under organization 123456 and source 5678: - $ gcloud beta scc findings update-marks my-finding \ + $ gcloud beta scc findings update-marks `myFinding` \ --organization=123456 --source=5678 \ --security-marks="key1=v1,key2=v2" - Delete all security marks on my-finding: + Delete all security marks on myFinding: - $ gcloud beta scc findings update-marks my-finding \ + $ gcloud beta scc findings update-marks `myFinding` \ --organization=123456 --source=5678 --security-marks="" POSITIONAL ARGUMENTS diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index 7ee59486e..fddc4f554 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -20,8 +20,9 @@ SYNOPSIS [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] - [--enable-bin-log] [--enable-google-private-path] - [--enable-password-policy] [--enable-point-in-time-recovery] + [--edition=EDITION] [--enable-bin-log] [--enable-data-cache] + [--enable-google-private-path] [--enable-password-policy] + [--enable-point-in-time-recovery] [--failover-replica-name=FAILOVER_REPLICA_NAME] [--[no-]insights-config-query-insights-enabled] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -35,6 +36,7 @@ SYNOPSIS [--master-instance-name=MASTER_INSTANCE_NAME] [--memory=MEMORY] [--network=NETWORK] [--password-policy-complexity=PASSWORD_POLICY_COMPLEXITY] + [--[no-]password-policy-disallow-compromised-credentials] [--[no-]password-policy-disallow-username-substring] [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] @@ -214,11 +216,19 @@ FLAGS --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME Time when the deny maintenance period starts or ends, that is 05:00:00. + --edition=EDITION + Specifies the edition of Cloud SQL instance. EDITION must be one of: + enterprise, enterprise-plus. + --enable-bin-log Allows for data recovery from a specific point in time, down to a fraction of a second. Must have automatic backups enabled to use. Make sure storage can support at least 7 days of logs. + --enable-data-cache + Enable use of data cache for accelerated read performance. This flag is + only available for Enterprise_Plus edition instances. + --enable-google-private-path Enable a private path for Google Cloud services. This flag specifies whether the instance is accessible to internal Google Cloud services @@ -327,6 +337,11 @@ FLAGS The default value if COMPLEXITY_DEFAULT is not specified. It implies that complexity check is not enabled. + --[no-]password-policy-disallow-compromised-credentials + Disallow credentials that have been compromised by a data breach. Use + --password-policy-disallow-compromised-credentials to enable and + --no-password-policy-disallow-compromised-credentials to disable. + --[no-]password-policy-disallow-username-substring Disallow username as a part of the password. Use --password-policy-disallow-username-substring to enable and @@ -357,16 +372,20 @@ FLAGS Specified if users connecting over IP must use SSL. --retained-backups-count=RETAINED_BACKUPS_COUNT - How many backups to keep. The valid range is between 1 and 365. The - default value is 7 if not specified. Applicable only if --no-backups is - not specified. + How many backups to keep. The valid range is between 1 and 365. Default + value is 7 for Enterprise edition instances. For Enterprise_Plus + Postgres and MySQL instances, default values are 15 and 8 respectively. + Applicable only if --no-backups is not specified. --retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS How many days of transaction logs to keep. The valid range is between 1 - and 35. The default value is 7. The 35 days log retention feature is - only enabled for specific customer. Only use this option when - point-in-time recovery is enabled. Storage size for transaction logs - increases when the number of days for log retention increases. + and 35. Only use this option when point-in-time recovery is enabled. If + logs are stored on disk, storage size for transaction logs could + increase when the number of days for log retention increases. For + Enterprise, default and max retention values are 7 and 7 respectively. + For MySQL Enterprise_Plus, default and max retention values are 7 and + 7. For Postgres Enterprise_Plus, default and max retention values are + 14 and 35. --root-password=ROOT_PASSWORD Root Cloud SQL user's password. diff --git a/gcloud/beta/sql/instances/list b/gcloud/beta/sql/instances/list index 81f92d066..450572998 100644 --- a/gcloud/beta/sql/instances/list +++ b/gcloud/beta/sql/instances/list @@ -3,14 +3,18 @@ NAME project SYNOPSIS - gcloud beta sql instances list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud beta sql instances list [--show-edition] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Lists Cloud SQL instances in a given project in the alphabetical order of the instance name. +FLAGS + --show-edition + Show the edition field. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index ebce4801c..8a650aa44 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -16,7 +16,8 @@ SYNOPSIS [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--diff] - [--[no-]enable-bin-log] [--[no-]enable-database-replication] + [--edition=EDITION] [--[no-]enable-bin-log] [--enable-data-cache] + [--[no-]enable-database-replication] [--[no-]enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] [--follow-gae-app=FOLLOW_GAE_APP] [--[no-]insights-config-query-insights-enabled] @@ -30,6 +31,7 @@ SYNOPSIS [--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR] [--memory=MEMORY] [--network=NETWORK] [--password-policy-complexity=PASSWORD_POLICY_COMPLEXITY] + [--[no-]password-policy-disallow-compromised-credentials] [--[no-]password-policy-disallow-username-substring] [--password-policy-min-length=PASSWORD_POLICY_MIN_LENGTH] [--password-policy-password-change-interval=PASSWORD_POLICY_PASSWORD_CHANGE_INTERVAL] @@ -157,12 +159,20 @@ FLAGS --diff Show what changed as a result of the update. + --edition=EDITION + Specifies the edition of Cloud SQL instance. EDITION must be one of: + enterprise, enterprise-plus. + --[no-]enable-bin-log Allows for data recovery from a specific point in time, down to a fraction of a second. Must have automatic backups enabled to use. Make sure storage can support at least 7 days of logs. Use --enable-bin-log to enable and --no-enable-bin-log to disable. + --enable-data-cache + Enable use of data cache for accelerated read performance. This flag is + only available for Enterprise_Plus edition instances. + --[no-]enable-database-replication Enable database replication. Applicable only for read replica instance(s). WARNING: Instance will be restarted. Use @@ -273,6 +283,11 @@ FLAGS The default value if COMPLEXITY_DEFAULT is not specified. It implies that complexity check is not enabled. + --[no-]password-policy-disallow-compromised-credentials + Disallow credentials that have been compromised by a data breach. Use + --password-policy-disallow-compromised-credentials to enable and + --no-password-policy-disallow-compromised-credentials to disable. + --[no-]password-policy-disallow-username-substring Disallow username as a part of the password. Use --password-policy-disallow-username-substring to enable and @@ -440,16 +455,20 @@ FLAGS UTC timezone. --retained-backups-count=RETAINED_BACKUPS_COUNT - How many backups to keep. The valid range is between 1 and 365. The - default value is 7 if not specified. Applicable only if --no-backups - is not specified. + How many backups to keep. The valid range is between 1 and 365. + Default value is 7 for Enterprise edition instances. For + Enterprise_Plus Postgres and MySQL instances, default values are 15 + and 8 respectively. Applicable only if --no-backups is not specified. --retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS How many days of transaction logs to keep. The valid range is between - 1 and 35. The default value is 7. The 35 days log retention feature - is only enabled for specific customer. Only use this option when - point-in-time recovery is enabled. Storage size for transaction logs - increases when the number of days for log retention increases. + 1 and 35. Only use this option when point-in-time recovery is + enabled. If logs are stored on disk, storage size for transaction + logs could increase when the number of days for log retention + increases. For Enterprise, default and max retention values are 7 and + 7 respectively. For MySQL Enterprise_Plus, default and max retention + values are 7 and 7. For Postgres Enterprise_Plus, default and max + retention values are 14 and 35. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/sql/operations/cancel b/gcloud/beta/sql/operations/cancel new file mode 100644 index 000000000..e6ee5e881 --- /dev/null +++ b/gcloud/beta/sql/operations/cancel @@ -0,0 +1,35 @@ +NAME + gcloud beta sql operations cancel - cancels a Cloud SQL instance operation + +SYNOPSIS + gcloud beta sql operations cancel OPERATION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Cancels a Cloud SQL instance operation. + +EXAMPLES + To cancel an operation with the id "prod-operation-id", like + "acb40108-a483-4a8b-8a5c-e27100000032", run: + + $ gcloud beta sql operations cancel prod-operation-id + +POSITIONAL ARGUMENTS + OPERATION + Name that uniquely identifies the operation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 sql operations cancel + + $ gcloud alpha sql operations cancel + diff --git a/gcloud/beta/sql/operations/help b/gcloud/beta/sql/operations/help index 77b3cb0c9..15c9163ee 100644 --- a/gcloud/beta/sql/operations/help +++ b/gcloud/beta/sql/operations/help @@ -18,6 +18,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + cancel + (BETA) Cancels a Cloud SQL instance operation. + describe (BETA) Retrieves information about a Cloud SQL instance operation. diff --git a/gcloud/beta/sql/tiers/list b/gcloud/beta/sql/tiers/list index 2a8327c57..3e3d534ae 100644 --- a/gcloud/beta/sql/tiers/list +++ b/gcloud/beta/sql/tiers/list @@ -3,13 +3,17 @@ NAME Cloud SQL SYNOPSIS - gcloud beta sql tiers list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud beta sql tiers list [--show-edition] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) Lists all available service tiers for Google Cloud SQL. +FLAGS + --show-edition + Show the edition field. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/beta/workstations/clusters/create b/gcloud/beta/workstations/clusters/create index 4e9abd1ba..86188a4a9 100644 --- a/gcloud/beta/workstations/clusters/create +++ b/gcloud/beta/workstations/clusters/create @@ -69,12 +69,10 @@ FLAGS Compute Engine resources. --network=NETWORK - The network that instances created under the cluster will be associated - with. + Fully specified network path for instances created in this cluster. --subnetwork=SUBNETWORK - The subnetwork that instances created under the cluster will be - associated with. + Fully specified subnetwork path for instances created in this cluster. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/workstations/configs/create b/gcloud/beta/workstations/configs/create index be661e001..db952a30e 100644 --- a/gcloud/beta/workstations/configs/create +++ b/gcloud/beta/workstations/configs/create @@ -155,10 +155,7 @@ FLAGS --machine-type=MACHINE_TYPE; default="e2-standard-4" Machine type determines the specifications of the Compute Engine machines that the workstations created under this configuration will - run on. MACHINE_TYPE must be one of: e2-standard-2, e2-standard-4, - e2-standard-8, e2-standard-16, e2-standard-32, n2-standard-8, - n1-standard-4, t2d-standard-6, n2d-standard-2, n2d-standard-4, - n2d-standard-8, n2d-standard-16, n2d-standard-32. + run on. --network-tags=[NETWORK_TAGS,...] Network tags to add to the Google Compute Engine machines backing the diff --git a/gcloud/beta/workstations/configs/update b/gcloud/beta/workstations/configs/update index 48007711b..7866dec3c 100644 --- a/gcloud/beta/workstations/configs/update +++ b/gcloud/beta/workstations/configs/update @@ -141,10 +141,7 @@ FLAGS --machine-type=MACHINE_TYPE Machine type determines the specifications of the Compute Engine machines that the workstations created under this configuration will - run on. MACHINE_TYPE must be one of: e2-standard-2, e2-standard-4, - e2-standard-8, e2-standard-16, e2-standard-32, n2-standard-8, - n1-standard-4, t2d-standard-6, n2d-standard-2, n2d-standard-4, - n2d-standard-8, n2d-standard-16, n2d-standard-32. + run on. --network-tags=[NETWORK_TAGS,...] Network tags to add to the Google Compute Engine machines backing the diff --git a/gcloud/builds/connections/add-iam-policy-binding b/gcloud/builds/connections/add-iam-policy-binding new file mode 100644 index 000000000..e395d9b71 --- /dev/null +++ b/gcloud/builds/connections/add-iam-policy-binding @@ -0,0 +1,95 @@ +NAME + gcloud builds connections add-iam-policy-binding - add IAM policy binding + to a Cloud Build connection + +SYNOPSIS + gcloud builds connections add-iam-policy-binding + (CONNECTION : --region=REGION) --member=PRINCIPAL --role=ROLE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add IAM policy binding to a Cloud Build connection. One binding consists of + a member and a role. + +EXAMPLES + To add an IAM policy binding for the role of + 'roles/cloudbuild.connectionViewer' for the user 'test-user@gmail.com' on a + Connection named 'my-conn', run: + + $ gcloud builds connections add-iam-policy-binding my-conn \ + --region=us-central1 --member='user:test-user@gmail.com' \ + --role='roles/cloudbuild.connectionViewer' + +POSITIONAL ARGUMENTS + Connection resource - Cloud Build Connection for which to add the IAM + policy binding. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections add-iam-policy-binding + + $ gcloud beta builds connections add-iam-policy-binding + diff --git a/gcloud/builds/connections/create/github b/gcloud/builds/connections/create/github new file mode 100644 index 000000000..196c73dbc --- /dev/null +++ b/gcloud/builds/connections/create/github @@ -0,0 +1,119 @@ +NAME + gcloud builds connections create github - create a Cloud Build Connection + of type GitHub + +SYNOPSIS + gcloud builds connections create github (CONNECTION : --region=REGION) + [--async] + [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + : --app-installation-id=APP_INSTALLATION_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Cloud Build Connection of type GitHub (for github.com). + + Connections for github.com can be created either by following an + installation process (that requires manual steps in a web browser) or by + providing the properties of an already-installed application (installation + ID and a user token) as arguments to this command. + +EXAMPLES + To create a connection by following the installation process, provide only + the connection name: + + $ gcloud builds connections create github myconn --project=myproj \ + --region=us-central1 + + The command will print a URL to be opened in a web browser in order to + authorize Cloud Build (i.e. Cloud Build gets an OAuth token for the github + account that you use). After doing this authorization, you can get the + connection's installation state with the describe command: + + $ gcloud alpha builds connections describe myconn + + The output will include a second link to install the Cloud Build GitHub + App. After doing this, the connection will be in installation state + COMPLETE and repositories can be added to it (see gcloud alpha builds + repositories create). + + -- + + To create a complete connection (e.g. based on an existing user token and + installation), provide both the authorizer secret token and the app + installation id: + + $ gcloud builds connections create github myconn --project=myproj \ + --region=us-central1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + mytoken/versions/1 --app-installation-id=1234 + + Above command creates the connection in installation state COMPLETE, ready + for adding repositories. + +POSITIONAL ARGUMENTS + Connection resource - Connection to create. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + Group of arguments for configuring a complete connnection. + + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the authorizer user's token. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --app-installation-id=APP_INSTALLATION_ID + Installation ID of the Cloud Build GitHub App. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections create github + + $ gcloud beta builds connections create github + diff --git a/gcloud/builds/connections/create/github-enterprise b/gcloud/builds/connections/create/github-enterprise new file mode 100644 index 000000000..086862ef2 --- /dev/null +++ b/gcloud/builds/connections/create/github-enterprise @@ -0,0 +1,173 @@ +NAME + gcloud builds connections create github-enterprise - create a Cloud Build + Connection of type GitHub Enterprise + +SYNOPSIS + gcloud builds connections create github-enterprise + (CONNECTION : --region=REGION) --host-uri=HOST_URI [--async] + [--app-id=APP_ID --app-slug=APP_SLUG + --private-key-secret-version=PRIVATE_KEY_SECRET_VERSION + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + : --app-installation-id=APP_INSTALLATION_ID] + [--service-directory-service=SERVICE_DIRECTORY_SERVICE + : --ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Cloud Build Connection of type GitHub Enterprise. + + Connections for GitHub Enterprise can be created either by following an + intallation process (that requires manual steps in a web browser) or by + providing all the properties of an already-installed application as + arguments to this command. + + If the GitHub Enterprise server can only be accessed within a VPC, a + Service Directory service resource can be provided for connecting to it. + +EXAMPLES + To create a connection by following the installation process, provide only + the connection name and the host URI. If the server can only be accessed + within a VPC, provide also the Service Directory service resource: + + $ gcloud builds connections create github-enterprise my-ghe-conn \ + --project=myproj --region=us-central1 \ + --host-uri=https://my.ghe-server.net \ + --service-directory-service=projects/myproj/namespaces/x/\ + services/mysds + + The command will print a URL to be opened in a web browser in order create + and install a GitHub App in that server. After following the URL, you can + get the connection's installation state with The describe command: + + $ gcloud alpha builds connections describe my-ghe-conn \ + --region=us-central1 + + If the connection's installation state is not COMPLETE yet, it will provide + a link to continue the installation process. Once the connection is in + installation state COMPLETE, repositories can be added to it (see gcloud + alpha builds repositories create). + + -- + + To create a complete connection (e.g. based on an existing installation), + provide all the parameters: + + $ gcloud builds connections create github-enterprise my-ghe-conn \ + --project=myproj --region=us-central1 --app-id=111 \ + --app-slug=gcb-app \ + --service-directory-service=projects/myproj/namespaces/x/\ + services/mysds \ + --private-key-secret-version=projects/myproj/secrets/pk/\ + versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 --app-slug=myapp --app-installation-id=1234 + + Above command creates the connection in installation state COMPLETE, ready + for adding repositories. + +POSITIONAL ARGUMENTS + Connection resource - Connection to create. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + --host-uri=HOST_URI + URI of the GitHub Enterprise server. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + Group of arguments for the GitHub App properties. + + --app-id=APP_ID + App ID of the GitHub App in the GitHub Enterprise server. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --app-slug=APP_SLUG + App slug (url-friendly name) of the GitHub App. When seeing the + configuration page of the App (e.g. in + https://my-ghe-server.net/settings/apps/my-app), the app-slug is the + last component of the URL path ("my-app" in that example). + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --private-key-secret-version=PRIVATE_KEY_SECRET_VERSION + Secret containing the private key of the GitHub App. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret containing the webhook secret string for validating webhook + events generated by the GitHub App. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --app-installation-id=APP_INSTALLATION_ID + Installation ID of the Cloud Build GitHub App. + + Group of arguments for configuring access through Service Directory. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + Service Directory service resource to use for accessing the GitHub + Enterprise Server. Necessary only if the server has no public access + from the internet. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --ssl-ca-file=SSL_CA_FILE + File containing the SSL_CA to be used. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections create github-enterprise + + $ gcloud beta builds connections create github-enterprise + diff --git a/gcloud/builds/connections/create/gitlab b/gcloud/builds/connections/create/gitlab new file mode 100644 index 000000000..ecc4f8c9e --- /dev/null +++ b/gcloud/builds/connections/create/gitlab @@ -0,0 +1,150 @@ +NAME + gcloud builds connections create gitlab - create a Cloud Build Connection + for gitlab.com or GitLab Enterprise + +SYNOPSIS + gcloud builds connections create gitlab (CONNECTION : --region=REGION) + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION [--async] + [--host-uri=HOST_URI] + [--service-directory-service=SERVICE_DIRECTORY_SERVICE + : --ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Cloud Build Connection for gitlab.com or GitLab Enterprise. + + A gitlab.com or GitLab Enterprise Connection can be created by using a + personal access token with api scope permission. A read_repository scoped + personal access token will also be required on gitlab.com or if the + self-hosted GitLab server doesn't support project access token (GitLab + Enterprise server version < 13.10). + + If the GitLab Enterprise server can only be accessed within a VPC, a + Service Directory service resource can be provided for connecting to it. + +EXAMPLES + To create a GitLab connection for gitlab.com, provide all the required + parameters: + + $ gcloud builds connections create gitlab my-gitlab-conn \ + --project=myproj --region=us-central1 \ + --read-authorizer-token-secret-version=projects/myproj/secrets/\ + read-pat/versions/1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + api-pat/versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 + + To create a GitLab connection for a GitLab server, provide host-uri + parameter as well: + + $ gcloud builds connections create gitlab my-gle-conn \ + --host-uri=https://my.gle-server.net --project=myproj \ + --region=us-central1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + api-pat/versions/1 \ + --read-authorizer-token-secret-version=projects/myproj/secrets/\ + read-pat/versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 + + To create a GitLab connection for a private GitLab server. provide the + service-directory-service and ssl-ca-file as well: + + $ gcloud builds connections create gitlab my-gle-conn \ + --host-uri=https://my.private-gle-server.net --project=myproj \ + --region=us-central1 \ + --service-directory-service=projects/myproj/namespaces/x/\ + services/mysds --ssl-ca-file=mycertificate.crt \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + api-pat/versions/1 \ + --read-authorizer-token-secret-version=projects/myproj/secrets/\ + read-pat/versions/1 \ + --webhook-secret-secret-version=projects/myproj/secrets/\ + whsecret/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to create. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the api personal access token. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the read_api personal access token. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret containing the webhook secret string for validating webhook + events sent by GitLab. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --host-uri=HOST_URI + URI of the GitLab instance. + + Group of arguments for configuring access through Service Directory. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + Service Directory service resource to use for accessing the + gitlab.com or GitLab Enterprise Server. Necessary only if the server + has no public access from the internet. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --ssl-ca-file=SSL_CA_FILE + File containing the SSL_CA to be used. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections create gitlab + + $ gcloud beta builds connections create gitlab + diff --git a/gcloud/builds/connections/create/help b/gcloud/builds/connections/create/help new file mode 100644 index 000000000..d9ef19a9e --- /dev/null +++ b/gcloud/builds/connections/create/help @@ -0,0 +1,33 @@ +NAME + gcloud builds connections create - create Connections in Google Cloud Build + +SYNOPSIS + gcloud builds connections create COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create Connections in Google Cloud Build. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + github + Create a Cloud Build Connection of type GitHub. + + github-enterprise + Create a Cloud Build Connection of type GitHub Enterprise. + + gitlab + Create a Cloud Build Connection for gitlab.com or GitLab Enterprise. + +NOTES + These variants are also available: + + $ gcloud alpha builds connections create + + $ gcloud beta builds connections create + diff --git a/gcloud/builds/connections/delete b/gcloud/builds/connections/delete new file mode 100644 index 000000000..1b52b7288 --- /dev/null +++ b/gcloud/builds/connections/delete @@ -0,0 +1,73 @@ +NAME + gcloud builds connections delete - delete a Cloud Build Connection + +SYNOPSIS + gcloud builds connections delete (CONNECTION : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Cloud Build Connection. + +EXAMPLES + To delete Cloud Build connection my-conn in region us-central1, run the + following command: + + $ gcloud builds connections delete my-conn --region=us-central1 + +POSITIONAL ARGUMENTS + Connection resource - Cloud Build connection to delete. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections delete + + $ gcloud beta builds connections delete + diff --git a/gcloud/builds/connections/describe b/gcloud/builds/connections/describe new file mode 100644 index 000000000..2b310e3ce --- /dev/null +++ b/gcloud/builds/connections/describe @@ -0,0 +1,68 @@ +NAME + gcloud builds connections describe - describe a Cloud Build Connection + +SYNOPSIS + gcloud builds connections describe (CONNECTION : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Cloud Build Connection. + +EXAMPLES + To describe a Connection my-conn in region us-central1, run the following + command: + + $ gcloud builds connections describe my-conn --region=us-central1 + +POSITIONAL ARGUMENTS + Connection resource - Cloud Build Connection to describe. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection 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, + --billing-project, --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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections describe + + $ gcloud beta builds connections describe + diff --git a/gcloud/builds/connections/get-iam-policy b/gcloud/builds/connections/get-iam-policy new file mode 100644 index 000000000..7cb0b8b68 --- /dev/null +++ b/gcloud/builds/connections/get-iam-policy @@ -0,0 +1,97 @@ +NAME + gcloud builds connections get-iam-policy - get the IAM policy for a Cloud + Build connection + +SYNOPSIS + gcloud builds connections get-iam-policy (CONNECTION : --region=REGION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get the IAM policy for a Cloud Build connection. + +EXAMPLES + To print the IAM policy for a Connection named 'my-conn', run the following + command: + + $ gcloud builds connections get-iam-policy my-conn \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Connection resource - Cloud Build Connection from which to get IAM policy. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ 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. + 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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections get-iam-policy + + $ gcloud beta builds connections get-iam-policy + diff --git a/gcloud/builds/connections/help b/gcloud/builds/connections/help new file mode 100644 index 000000000..4882c6737 --- /dev/null +++ b/gcloud/builds/connections/help @@ -0,0 +1,51 @@ +NAME + gcloud builds connections - manage connections for Google Cloud Build + +SYNOPSIS + gcloud builds connections GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage connections for Google Cloud Build. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + create + Create Connections in Google Cloud Build. + + update + Update Connections in Google Cloud Build. + +COMMANDS + COMMAND is one of the following: + + add-iam-policy-binding + Add IAM policy binding to a Cloud Build connection. + + delete + Delete a Cloud Build Connection. + + describe + Describe a Cloud Build Connection. + + get-iam-policy + Get the IAM policy for a Cloud Build connection. + + list + List all Cloud Build connections for a project and region. + + set-iam-policy + Set the IAM policy for a Cloud Build connection. + +NOTES + These variants are also available: + + $ gcloud alpha builds connections + + $ gcloud beta builds connections + diff --git a/gcloud/beta/debug/targets/list b/gcloud/builds/connections/list similarity index 59% rename from gcloud/beta/debug/targets/list rename to gcloud/builds/connections/list index a4bae8842..5e0dbf482 100644 --- a/gcloud/beta/debug/targets/list +++ b/gcloud/builds/connections/list @@ -1,37 +1,39 @@ NAME - gcloud beta debug targets list - list the debug targets (debuggees) - registered with the Cloud Debugger + gcloud builds connections list - list all Cloud Build connections for a + project and region SYNOPSIS - gcloud beta debug targets list [--include-inactive] [--filter=EXPRESSION] + gcloud builds connections list [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May - 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud beta debug targets list is used to display a list of the debug - targets (debuggees) registered with the Cloud Debugger. By default only the - active targets are shown, the --include-inactive can be provided to also - include the targets that are no longer active. + List all Cloud Build connections for a project and region. EXAMPLES - To list the active debug targets (debuggees) registered with the Cloud - Debugger, run: + To list all the Cloud Build connections in region us-central1, run the + following command: - $ gcloud beta debug targets list - - To list all (both active and inactive) debug targets (debuggees) registered - with the Cloud Debugger, run: - - $ gcloud beta debug targets list --include-inactive + $ gcloud builds connections list --region=us-central1 FLAGS - --include-inactive - If set, include targets which are no longer active. + Region resource - Cloud Build location to list all contained connections. + 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 @@ -73,9 +75,14 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +API REFERENCE + This command uses the cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + NOTES - This command is currently in beta and might change without notice. This - variant is also available: + These variants are also available: - $ gcloud debug targets list + $ gcloud alpha builds connections list + + $ gcloud beta builds connections list diff --git a/gcloud/builds/connections/set-iam-policy b/gcloud/builds/connections/set-iam-policy new file mode 100644 index 000000000..b28bb3fba --- /dev/null +++ b/gcloud/builds/connections/set-iam-policy @@ -0,0 +1,81 @@ +NAME + gcloud builds connections set-iam-policy - set the IAM policy for a Cloud + Build connection + +SYNOPSIS + gcloud builds connections set-iam-policy (CONNECTION : --region=REGION) + POLICY_FILE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Set the IAM policy for a Cloud Build connection as defined in a JSON or + YAML file. + + See https://cloud.google.com/iam/docs/managing-policies for details of the + policy file format and contents. + +EXAMPLES + The following command will read an IAM policy defined in a JSON file + 'policy.json' and set it for the Connection named 'my-conn': + + $ gcloud builds connections set-iam-policy my-conn policy.json \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Connection resource - Cloud Build Connection for which to set IAM policy. + The arguments in this group can be used to specify the attributes of this + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. + + To set the project attribute: + ◆ provide the argument connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections set-iam-policy + + $ gcloud beta builds connections set-iam-policy + diff --git a/gcloud/builds/connections/update/github b/gcloud/builds/connections/update/github new file mode 100644 index 000000000..2e1b6f4f5 --- /dev/null +++ b/gcloud/builds/connections/update/github @@ -0,0 +1,91 @@ +NAME + gcloud builds connections update github - update a Cloud Build Connection + of type GitHub + +SYNOPSIS + gcloud builds connections update github (CONNECTION : --region=REGION) + [--app-installation-id=APP_INSTALLATION_ID] [--async] + [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Cloud Build Connection of type GitHub (for github.com). + +EXAMPLES + To update the authorizer token, provide the connection name and the + authorizer token secret: + + $ gcloud builds connections update github myconn \ + --region=us-central1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + mytoken/versions/1 + + To update the installation id, provide the connection name and the + installation id of the Cloud Build GitHub app. + + $ gcloud builds connections update github myconn \ + --region=us-central1 --app-installation-id=1234 + +POSITIONAL ARGUMENTS + Connection resource - Connection to update. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --app-installation-id=APP_INSTALLATION_ID + Installation ID of the Cloud Build GitHub App. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the authorizer user's token. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections update github + + $ gcloud beta builds connections update github + diff --git a/gcloud/builds/connections/update/github-enterprise b/gcloud/builds/connections/update/github-enterprise new file mode 100644 index 000000000..c8c813e6f --- /dev/null +++ b/gcloud/builds/connections/update/github-enterprise @@ -0,0 +1,117 @@ +NAME + gcloud builds connections update github-enterprise - update a Cloud Build + Connection of type GitHub Enterprise + +SYNOPSIS + gcloud builds connections update github-enterprise + (CONNECTION : --region=REGION) [--app-id=APP_ID] + [--app-installation-id=APP_INSTALLATION_ID] [--app-slug=APP_SLUG] + [--async] [--host-uri=HOST_URI] + [--private-key-secret-version=PRIVATE_KEY_SECRET_VERSION] + [--service-directory-service=SERVICE_DIRECTORY_SERVICE] + [--ssl-ca-file=SSL_CA_FILE] + [--webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Cloud Build Connection of type GitHub Enterprise. + +EXAMPLES + To update the ssl_ca, provide the connection name and the ssl_ca file: + + $ gcloud builds connections update github-enterprise my-ghe-conn \ + --region=us-west1 --ssl-ca-file=mycertificate.crt + + To update the installation id, provide the connection name and the + installation id of the Cloud Build GitHub app. + + $ gcloud builds connections update github-enterprise my-ghe-conn \ + --region=us-west1 --app-installation-id=1234 + +POSITIONAL ARGUMENTS + Connection resource - Connection to update. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --app-id=APP_ID + App ID of the GitHub App in the GitHub Enterprise server. + + --app-installation-id=APP_INSTALLATION_ID + Installation ID of the Cloud Build GitHub App. + + --app-slug=APP_SLUG + App slug (url-friendly name) of the GitHub App. When seeing the + configuration page of the App (e.g. in + https://my-ghe-server.net/settings/apps/my-app), the app-slug is the + last component of the URL path ("my-app" in that example). + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --host-uri=HOST_URI + URI of the GitHub Enterprise server. + + --private-key-secret-version=PRIVATE_KEY_SECRET_VERSION + Secret containing the private key of the GitHub App. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + Service Directory service resource to use for accessing the GitHub + Enterprise Server. Necessary only if the server has no public access + from the internet. + + --ssl-ca-file=SSL_CA_FILE + File containing the SSL_CA to be used. + + --webhook-secret-secret-version=WEBHOOK_SECRET_SECRET_VERSION + Secret containing the webhook secret string for validating webhook + events generated by the GitHub App. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections update github-enterprise + + $ gcloud beta builds connections update github-enterprise + diff --git a/gcloud/builds/connections/update/gitlab b/gcloud/builds/connections/update/gitlab new file mode 100644 index 000000000..da67e95f8 --- /dev/null +++ b/gcloud/builds/connections/update/gitlab @@ -0,0 +1,105 @@ +NAME + gcloud builds connections update gitlab - update a Cloud Build Connection + of type gitlab.com or GitLab Enterprise + +SYNOPSIS + gcloud builds connections update gitlab (CONNECTION : --region=REGION) + [--async] + [--authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION] + [--host-uri=HOST_URI] + [--read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION] + [--service-directory-service=SERVICE_DIRECTORY_SERVICE] + [--ssl-ca-file=SSL_CA_FILE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Cloud Build Connection of type gitlab.com or GitLab Enterprise. + +EXAMPLES + To update the ssl_ca, provide the connection name and the ssl_ca file: + + $ gcloud builds connections update gitlab my-gle-conn \ + --region=us-west1 --ssl-ca-file=mycertificate.crt + + To update the authorization token, provide the connection name and the new + authorization token secret version. + + $ gcloud builds connections update gitlab my-gle-conn \ + --region=us-west1 \ + --authorizer-token-secret-version=projects/myproj/secrets/\ + api-pat/versions/1 + +POSITIONAL ARGUMENTS + Connection resource - Connection to update. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument connection on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument connection on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --authorizer-token-secret-version=AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the api personal access token. + + --host-uri=HOST_URI + URI of the GitLab instance. + + --read-authorizer-token-secret-version=READ_AUTHORIZER_TOKEN_SECRET_VERSION + Secret containing the read_repository personal access token. Required + for GitLab Enterprise versions older than 13.10. + + --service-directory-service=SERVICE_DIRECTORY_SERVICE + Service Directory service resource to use for accessing the GitLab + Enterprise Server. Necessary only if the server has no public access + from the internet. + + --ssl-ca-file=SSL_CA_FILE + File containing the SSL_CA to be used. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds connections update gitlab + + $ gcloud beta builds connections update gitlab + diff --git a/gcloud/builds/connections/update/help b/gcloud/builds/connections/update/help new file mode 100644 index 000000000..07871e5ba --- /dev/null +++ b/gcloud/builds/connections/update/help @@ -0,0 +1,34 @@ +NAME + gcloud builds connections update - update Connections in Google Cloud Build + +SYNOPSIS + gcloud builds connections update COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update Connections in Google Cloud Build. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + github + Update a Cloud Build Connection of type GitHub. + + github-enterprise + Update a Cloud Build Connection of type GitHub Enterprise. + + gitlab + Update a Cloud Build Connection of type gitlab.com or GitLab + Enterprise. + +NOTES + These variants are also available: + + $ gcloud alpha builds connections update + + $ gcloud beta builds connections update + diff --git a/gcloud/builds/help b/gcloud/builds/help index e092d14f3..0627cfce6 100644 --- a/gcloud/builds/help +++ b/gcloud/builds/help @@ -15,6 +15,12 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + connections + Manage connections for Google Cloud Build. + + repositories + Manage repositories for Google Cloud Build. + triggers Create and manage build triggers for Google Cloud Build. diff --git a/gcloud/builds/repositories/create b/gcloud/builds/repositories/create new file mode 100644 index 000000000..00720a0f0 --- /dev/null +++ b/gcloud/builds/repositories/create @@ -0,0 +1,88 @@ +NAME + gcloud builds repositories create - create a Cloud Build repository + +SYNOPSIS + gcloud builds repositories create + (REPOSITORY : --connection=CONNECTION --region=REGION) + --remote-uri=REMOTE_URI [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Cloud Build repository in a connection. + +EXAMPLES + To Create a repository with name my-repo in the connection my-conn, run the + following command: + + $ gcloud builds repositories create my-repo \ + --remote-uri=https://github.com/octocat/Hello-World.git \ + --connection=my-conn --region=us-central1 + +POSITIONAL ARGUMENTS + Repository resource - Repository to create. The arguments in this group + can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument repository on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + REPOSITORY + ID of the repository or fully qualified identifier for the + repository. + + To set the repository attribute: + ▸ provide the argument repository on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connection=CONNECTION + Connection ID. + + To set the connection attribute: + ▸ provide the argument repository on the command line with a fully + specified name; + ▸ provide the argument --connection on the command line. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument repository on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +REQUIRED FLAGS + --remote-uri=REMOTE_URI + The remote git clone URL of the repository. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds repositories create + + $ gcloud beta builds repositories create + diff --git a/gcloud/builds/repositories/delete b/gcloud/builds/repositories/delete new file mode 100644 index 000000000..ed4df335f --- /dev/null +++ b/gcloud/builds/repositories/delete @@ -0,0 +1,83 @@ +NAME + gcloud builds repositories delete - delete a Cloud Build Repository + +SYNOPSIS + gcloud builds repositories delete + (REPOSITORY : --connection=CONNECTION --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Cloud Build Repository in a Connection. + +EXAMPLES + To delete Cloud Build repository my-repo in connection my-conn, run the + following command: + + $ gcloud builds repositories delete my-repo --connection=my-conn \ + --region=us-central1 + +POSITIONAL ARGUMENTS + Repository resource - Cloud Build repository to delete. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument repository on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + REPOSITORY + ID of the repository or fully qualified identifier for the + repository. + + To set the repository attribute: + ▸ provide the argument repository on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connection=CONNECTION + Connection ID. + + To set the connection attribute: + ▸ provide the argument repository on the command line with a fully + specified name; + ▸ provide the argument --connection on the command line. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument repository on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property builds/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds repositories delete + + $ gcloud beta builds repositories delete + diff --git a/gcloud/builds/repositories/describe b/gcloud/builds/repositories/describe new file mode 100644 index 000000000..33a2dd3b8 --- /dev/null +++ b/gcloud/builds/repositories/describe @@ -0,0 +1,77 @@ +NAME + gcloud builds repositories describe - describe a Cloud Build Repository + +SYNOPSIS + gcloud builds repositories describe + (REPOSITORY : --connection=CONNECTION --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a Cloud Build Repository. + +EXAMPLES + To list all the Cloud Build connections in region us-central1, run the + following command: + + $ gcloud builds repositories describe --region=us-central1 + +POSITIONAL ARGUMENTS + Repository resource - Cloud Build Repository to describe. The arguments in + this group can be used to specify the attributes of this resource. (NOTE) + Some attributes are not given arguments in this group but can be set in + other ways. + + To set the project attribute: + ◆ provide the argument repository on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + REPOSITORY + ID of the repository or fully qualified identifier for the + repository. + + To set the repository attribute: + ▸ provide the argument repository on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --connection=CONNECTION + Connection ID. + + To set the connection attribute: + ▸ provide the argument repository on the command line with a fully + specified name; + ▸ provide the argument --connection on the command line. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument repository 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, + --billing-project, --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 cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds repositories describe + + $ gcloud beta builds repositories describe + diff --git a/gcloud/builds/repositories/help b/gcloud/builds/repositories/help new file mode 100644 index 000000000..1aeaa1fd0 --- /dev/null +++ b/gcloud/builds/repositories/help @@ -0,0 +1,36 @@ +NAME + gcloud builds repositories - manage repositories for Google Cloud Build + +SYNOPSIS + gcloud builds repositories COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage repositories for Google Cloud Build. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Cloud Build repository. + + delete + Delete a Cloud Build Repository. + + describe + Describe a Cloud Build Repository. + + list + List all Cloud Build repositories in a connection. + +NOTES + These variants are also available: + + $ gcloud alpha builds repositories + + $ gcloud beta builds repositories + diff --git a/gcloud/builds/repositories/list b/gcloud/builds/repositories/list new file mode 100644 index 000000000..f98dd5a2f --- /dev/null +++ b/gcloud/builds/repositories/list @@ -0,0 +1,103 @@ +NAME + gcloud builds repositories list - list all Cloud Build repositories in a + connection + +SYNOPSIS + gcloud builds repositories list (--connection=CONNECTION : --region=REGION) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List all Cloud Build repositories in a connection. + +EXAMPLES + To list all the repositories in the Cloud Build connection my-conn, run the + following command: + + $ gcloud builds repositories list --connection=my-conn \ + --region=us-central1 + +REQUIRED FLAGS + Connection resource - Cloud Build connection to list all contained + repositories. The arguments in this group can be used to specify the + attributes of this resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --connection on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --connection=CONNECTION + ID of the connection or fully qualified identifier for the + connection. + + To set the connection attribute: + ▸ provide the argument --connection on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --region=REGION + The Google Cloud region. + + To set the region attribute: + ▸ provide the argument --connection on the command line with a + fully specified name; + ▸ 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. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the cloudbuild/v2 API. The full documentation for this + API can be found at: https://cloud.google.com/cloud-build/docs/ + +NOTES + These variants are also available: + + $ gcloud alpha builds repositories list + + $ gcloud beta builds repositories list + diff --git a/gcloud/builds/submit b/gcloud/builds/submit index f77d74b17..5677ac551 100644 --- a/gcloud/builds/submit +++ b/gcloud/builds/submit @@ -118,7 +118,7 @@ FLAGS --machine-type=MACHINE_TYPE Machine type used to run the build. MACHINE_TYPE must be one of: - e2-highcpu-32, e2-highcpu-8, n1-highcpu-32, n1-highcpu-8. + e2-highcpu-32, e2-highcpu-8, e2-medium, n1-highcpu-32, n1-highcpu-8. --region=REGION The region of the Cloud Build Service to use. Must be set to a diff --git a/gcloud/builds/triggers/create/bitbucketserver b/gcloud/builds/triggers/create/bitbucketserver index 6ac516644..6fdbee2bf 100644 --- a/gcloud/builds/triggers/create/bitbucketserver +++ b/gcloud/builds/triggers/create/bitbucketserver @@ -105,24 +105,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud builds triggers create bitbucketserver ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/builds/triggers/create/cloud-source-repositories b/gcloud/builds/triggers/create/cloud-source-repositories index 65e3ddd6c..33094c7d0 100644 --- a/gcloud/builds/triggers/create/cloud-source-repositories +++ b/gcloud/builds/triggers/create/cloud-source-repositories @@ -87,24 +87,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud builds triggers create cloud-source-repositories ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/builds/triggers/create/github b/gcloud/builds/triggers/create/github index e7c517589..1a7fceabb 100644 --- a/gcloud/builds/triggers/create/github +++ b/gcloud/builds/triggers/create/github @@ -96,24 +96,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud builds triggers create github ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/builds/triggers/create/gitlab b/gcloud/builds/triggers/create/gitlab new file mode 100644 index 000000000..7885e8ca8 --- /dev/null +++ b/gcloud/builds/triggers/create/gitlab @@ -0,0 +1,206 @@ +NAME + gcloud builds triggers create gitlab - create a build trigger for a 2nd-gen + GitLab repository + +SYNOPSIS + gcloud builds triggers create gitlab + (--trigger-config=PATH | [(--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-image=DOCKERFILE_IMAGE + : --dockerfile-dir=DOCKERFILE_DIR; default="/"]) + : --description=DESCRIPTION --ignored-files=[GLOB,...] + --included-files=[GLOB,...] --name=NAME --region=REGION + --repository=REPOSITORY --[no-]require-approval + --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a build trigger for a 2nd-gen GitLab repository. + +EXAMPLES + To create a push trigger with a 2nd-gen repository for all branches: + + $ gcloud builds triggers create gitlab --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/global/connections/myconn/\ + repositories/myrepo" --branch-pattern=".*" \ + --build-config="cloudbuild.yaml" + + To create a pull request trigger with a 1st-gen repository for main: + + $ gcloud builds triggers create gitlab --name="my-trigger" \ + --service-account="projects/my-project/serviceAccounts/my-byosa@\ + my-project.iam.gserviceaccount.com" \ + --repository="projects/1234/locations/global/connections/myconn/\ + repositories/myrepo" --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 + + --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. + + --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, builds/region, + which is the default region to use when working with Cloud Build + resources, is used. If builds/region is unset, region is set to + global. + + --repository=REPOSITORY + Repository resource (2nd gen) to use, in the format + "projects/*/locations/*/connections/*/repositories/". + + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. + + --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: + + $ gcloud builds triggers create gitlab ... \ + --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". + + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + REPO_NAME, BRANCH_NAME, TAG_NAME, REVISION_ID, COMMIT_SHA, + SHORT_SHA. + + For more details, see: + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values + + 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 regular expression 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 regular expression 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 argument 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. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --dockerfile-image=DOCKERFILE_IMAGE + Docker image name to build. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --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. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 builds triggers create gitlab + + $ gcloud beta builds triggers create gitlab + diff --git a/gcloud/builds/triggers/create/gitlab-enterprise b/gcloud/builds/triggers/create/gitlab-enterprise index c13a9cd9c..30068a33c 100644 --- a/gcloud/builds/triggers/create/gitlab-enterprise +++ b/gcloud/builds/triggers/create/gitlab-enterprise @@ -86,24 +86,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud builds triggers create gitlab-enterprise ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/builds/triggers/create/help b/gcloud/builds/triggers/create/help index 013658786..c18a1b405 100644 --- a/gcloud/builds/triggers/create/help +++ b/gcloud/builds/triggers/create/help @@ -25,6 +25,9 @@ COMMANDS github Create a build trigger for a GitHub repository. + gitlab + Create a build trigger for a 2nd-gen GitLab repository. + gitlab-enterprise Create a build trigger for a GitLab Enterprise repository. diff --git a/gcloud/builds/triggers/create/manual b/gcloud/builds/triggers/create/manual index 2d34f24a1..74dabde5e 100644 --- a/gcloud/builds/triggers/create/manual +++ b/gcloud/builds/triggers/create/manual @@ -71,24 +71,23 @@ REQUIRED FLAGS projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud builds triggers create manual ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/builds/triggers/create/pubsub b/gcloud/builds/triggers/create/pubsub index 4495e38d9..f66c3269c 100644 --- a/gcloud/builds/triggers/create/pubsub +++ b/gcloud/builds/triggers/create/pubsub @@ -87,24 +87,23 @@ REQUIRED FLAGS for more details. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud builds triggers create pubsub ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/builds/triggers/create/webhook b/gcloud/builds/triggers/create/webhook index c27b314f8..975884233 100644 --- a/gcloud/builds/triggers/create/webhook +++ b/gcloud/builds/triggers/create/webhook @@ -93,24 +93,23 @@ REQUIRED FLAGS for more details. --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For + example: - For example (using some nonsensical substitution keys; all keys - must begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud builds triggers create webhook ... \ --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. + Substitutions can be applied to user-defined variables (starting + with an underscore) and to the following built-in variables: + 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values Exactly one of these must be specified: diff --git a/gcloud/builds/triggers/run b/gcloud/builds/triggers/run index a3bf793ea..77eb49eb5 100644 --- a/gcloud/builds/triggers/run +++ b/gcloud/builds/triggers/run @@ -47,24 +47,21 @@ POSITIONAL ARGUMENTS FLAGS --substitutions=[KEY=VALUE,...] - Parameters to be substituted in the build specification. + Parameters to be substituted in the build specification. For example: - For example (using some nonsensical substitution keys; all keys must - begin with an underscore): - - $ gcloud builds triggers create ... --config config.yaml + $ gcloud builds triggers run ... \ --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. + Substitutions can be applied to user-defined variables (starting with + an underscore) and to the following built-in variables: 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 + https://cloud.google.com/build/docs/configuring-builds/substitute-variable-values At most one of these can be specified: diff --git a/gcloud/compute/instances/create b/gcloud/compute/instances/create index 0b3a55ca6..381a349a6 100644 --- a/gcloud/compute/instances/create +++ b/gcloud/compute/instances/create @@ -58,6 +58,10 @@ SYNOPSIS [--image-family-scope=IMAGE_FAMILY_SCOPE --image-project=IMAGE_PROJECT --image=IMAGE | --image-family=IMAGE_FAMILY | --source-snapshot=SOURCE_SNAPSHOT] + [--instance-kms-key=INSTANCE_KMS_KEY + : --instance-kms-keyring=INSTANCE_KMS_KEYRING + --instance-kms-location=INSTANCE_KMS_LOCATION + --instance-kms-project=INSTANCE_KMS_PROJECT] [--node=NODE | --node-affinity-file=NODE_AFFINITY_FILE | --node-group=NODE_GROUP] [--public-ptr | --no-public-ptr] [--public-ptr-domain=PUBLIC_PTR_DOMAIN | --no-public-ptr-domain] @@ -998,6 +1002,44 @@ FLAGS ▸ https://compute.googleapis.com/compute/v1/projects/myproject/global/snapshots/snapshot ▸ snapshot + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the instance. The arguments in this group can be used + to specify the attributes of this resource. + + --instance-kms-key=INSTANCE_KMS_KEY + ID of the key or fully qualified identifier for the key. + + To set the kms-key attribute: + ▸ provide the argument --instance-kms-key on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --instance-kms-keyring=INSTANCE_KMS_KEYRING + The KMS keyring of the key. + + To set the kms-keyring attribute: + ▸ provide the argument --instance-kms-key on the command line with + a fully specified name; + ▸ provide the argument --instance-kms-keyring on the command line. + + --instance-kms-location=INSTANCE_KMS_LOCATION + The Cloud location for the key. + + To set the kms-location attribute: + ▸ provide the argument --instance-kms-key on the command line with + a fully specified name; + ▸ provide the argument --instance-kms-location on the command line. + + --instance-kms-project=INSTANCE_KMS_PROJECT + The Cloud project for the key. + + To set the kms-project attribute: + ▸ provide the argument --instance-kms-key on the command line with + a fully specified name; + ▸ provide the argument --instance-kms-project on the command line; + ▸ set the property core/project. + Sole Tenancy. At most one of these can be specified: diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 16da5c20a..c9ac701f4 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -197,7 +197,7 @@ FLAGS ADDON must be one of: HttpLoadBalancing, HorizontalPodAutoscaling, KubernetesDashboard, NetworkPolicy, NodeLocalDNS, ConfigConnector, GcePersistentDiskCsiDriver, GcpFilestoreCsiDriver, BackupRestore, - CloudRun. + GcsFuseCsiDriver, CloudRun. --async Return immediately, without waiting for the operation in progress to @@ -1115,6 +1115,8 @@ FLAGS Selects Cloud DNS as the DNS provider for the cluster. default Selects the default DNS provider (kube-dns) for the cluster. + kubedns + Selects Kube DNS as the DNS provider for the cluster. --cluster-dns-domain=CLUSTER_DNS_DOMAIN DNS domain for this cluster. The default value is cluster.local. This diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 9dadbe2b8..cd15d75b9 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -531,6 +531,7 @@ REQUIRED FLAGS ConfigConnector=ENABLED|DISABLED NodeLocalDNS=ENABLED|DISABLED GcePersistentDiskCsiDriver=ENABLED|DISABLED GcpFilestoreCsiDriver=ENABLED|DISABLED + GcsFuseCsiDriver=ENABLED|DISABLED --update-labels=[KEY=VALUE,...] Labels to apply to the Google Cloud resources in use by the @@ -756,6 +757,8 @@ REQUIRED FLAGS Selects Cloud DNS as the DNS provider for the cluster. default Selects the default DNS provider (kube-dns) for the cluster. + kubedns + Selects Kube DNS as the DNS provider for the cluster. --cluster-dns-domain=CLUSTER_DNS_DOMAIN DNS domain for this cluster. The default value is cluster.local. diff --git a/gcloud/container/fleet/memberships/register b/gcloud/container/fleet/memberships/register index 5ab728046..8729ce75c 100644 --- a/gcloud/container/fleet/memberships/register +++ b/gcloud/container/fleet/memberships/register @@ -28,6 +28,8 @@ DESCRIPTION To register a GKE cluster, use --gke-cluster or --gke-uri flag (no --kubeconfig flag is required). Connect agent will not be installed by default for GKE clusters. To install it, specify --install-connect-agent. + The default value for --location is the same as the cluster's region or + zone, can be specified as global. Anthos clusters on VMware, bare metal, AWS, and Azure are registered with a fleet when the clusters are created. To register Amazon EKS clusters, see @@ -77,7 +79,7 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json Register a non-GKE cluster and output a manifest that can be used to - install the Connect agent: + install the Connect agent by kubectl: $ gcloud container fleet memberships register my-cluster \ --context=my-cluster-context \ @@ -96,6 +98,14 @@ EXAMPLES --gke-uri=my-cluster-gke-uri --install-connect-agent \ --service-account-key-file=/tmp/keyfile.json + Register a GKE cluster and output a manifest that can be used to install + the Connect agent by kubectl: + + $ gcloud container fleet memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri --enable-workload-identity \ + --install-connect-agent \ + --manifest-output-file=/tmp/manifest.yaml + Register a GKE cluster first, and install the Connect agent later. $ gcloud container fleet memberships register my-cluster \ diff --git a/gcloud/container/hub/memberships/register b/gcloud/container/hub/memberships/register index aedb8a8ab..2acbe1683 100644 --- a/gcloud/container/hub/memberships/register +++ b/gcloud/container/hub/memberships/register @@ -27,6 +27,8 @@ DESCRIPTION To register a GKE cluster, use --gke-cluster or --gke-uri flag (no --kubeconfig flag is required). Connect agent will not be installed by default for GKE clusters. To install it, specify --install-connect-agent. + The default value for --location is the same as the cluster's region or + zone, can be specified as global. Anthos clusters on VMware, bare metal, AWS, and Azure are registered with a fleet when the clusters are created. To register Amazon EKS clusters, see @@ -76,7 +78,7 @@ EXAMPLES --service-account-key-file=/tmp/keyfile.json Register a non-GKE cluster and output a manifest that can be used to - install the Connect agent: + install the Connect agent by kubectl: $ gcloud container hub memberships register my-cluster \ --context=my-cluster-context \ @@ -95,6 +97,14 @@ EXAMPLES --gke-uri=my-cluster-gke-uri --install-connect-agent \ --service-account-key-file=/tmp/keyfile.json + Register a GKE cluster and output a manifest that can be used to install + the Connect agent by kubectl: + + $ gcloud container hub memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri --enable-workload-identity \ + --install-connect-agent \ + --manifest-output-file=/tmp/manifest.yaml + Register a GKE cluster first, and install the Connect agent later. $ gcloud container hub memberships register my-cluster \ diff --git a/gcloud/debug/help b/gcloud/debug/help deleted file mode 100644 index 82b606c46..000000000 --- a/gcloud/debug/help +++ /dev/null @@ -1,79 +0,0 @@ -NAME - gcloud debug - commands for interacting with the Cloud Debugger - -SYNOPSIS - gcloud debug GROUP [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Commands for interacting with the Cloud Debugger. - - Cloud Debugger is deprecated and will be shutdown May 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - The gcloud debug command group provides interaction with Cloud Debugger, - allowing you to list and manipulate debugging targets, snapshots and - logpoints. - - Cloud Debugger is a feature of Google Cloud that lets you inspect the state - of an application at any code location without using logging statements and - without stopping or slowing down your applications. - - More information on Cloud Debugger can be found here: - https://cloud.google.com/debugger and detailed documentation can be found - here: https://cloud.google.com/debugger/docs/ - -EXAMPLES - To view all available debug targets, run: - - $ gcloud debug targets list - - NAME ID DESCRIPTION - default-test gcp:1234:5678 myproject-test-9876543 - default-test2 gcp:9012:3456 myproject-test2-1234567 - - To create a snapshot for a particular target: - - $ gcloud debug snapshots create --target=default-test foo.py:12 - - Note that if there is not a target with the exact name or ID specified, the - target is treated as a regular expression to match against the name or - description: - - $ gcloud debug snapshots create --target=test foo.py:12 - - ERROR: (gcloud.beta.debug.snapshots.create) Multiple possible targets found. - Use the --target option to select one of the following targets: - default-test - default-test2 - - In the above case, "test" matches both targets' names. Specifying 'test$' - would match only "default-test" (by name), while "9876" would match - "default-test" by description. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - logpoints - (DEPRECATED) Commands for interacting with Cloud Debugger logpoints. - - snapshots - (DEPRECATED) Commands for interacting with Cloud Debugger snapshots. - - source - (DEPRECATED) Commands to manage source information for Cloud Debugger. - - targets - (DEPRECATED) Commands for interacting with Cloud Debugger debug - targets. - -NOTES - This variant is also available: - - $ gcloud beta debug - diff --git a/gcloud/debug/logpoints/create b/gcloud/debug/logpoints/create deleted file mode 100644 index f032716c0..000000000 --- a/gcloud/debug/logpoints/create +++ /dev/null @@ -1,104 +0,0 @@ -NAME - gcloud debug logpoints create - add debug logpoints to a Cloud Debugger - debug target (debuggee) - -SYNOPSIS - gcloud debug logpoints create LOCATION LOG_FORMAT_STRING - [--condition=CONDITION] [--log-level=LOG_LEVEL; default="info"] - [--target=(ID|DESCRIPTION_REGEXP)] [--wait=WAIT; default=10] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May 31, - 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud debug logpoints create is used to add a debug logpoint to a debug - target (debuggee). Logpoints add logging to your running service without - changing your code or restarting your application. When you create a - logpoint, the message you specify will be added to your logs whenever any - instance of your service executes the specified line of code. - - The default lifetime of a logpoint is 24 hours from creation, and the - output will go to the standard log for the programming language of the - target (java.logging for Java, logging for Python, etc.) - -EXAMPLES - To add a logpoint with no conditions that will print the value of the - variable 'name' at line 41 of file main.py of a debug target (debuggee), - run: - - $ gcloud debug logpoints create main.py:41 "Variable name={name}" \ - --target= - - To add a logpoint that will print the value of the variable 'name' at line - 41 of file main.py on a debug target (debuggee) that will only trigger if - the length of 'name' is greater than 3, run: - - $ gcloud debug logpoints create main.py:41 "Variable name={name}" \ - --target= --condition="len(name) > 3" - - To add a logpoint with a log level of error at line 35 of file main.py on a - debug target (debuggee), run: - - $ gcloud debug logpoints create main.py:35 "Unexpected path" \ - --target= --log-level=error - -POSITIONAL ARGUMENTS - LOCATION - The logpoint location. Locations are of the form FILE:LINE, where FILE - can be simply the file name, or the file name preceded by enough path - components to differentiate it from other files with the same name. It - is an error to provide a file name that is not unique in the debug - target. - - LOG_FORMAT_STRING - A format string which will be logged every time the logpoint location - is executed. If the string contains curly braces ('{' and '}'), any - text within the curly braces will be interpreted as a run-time - expression in the debug target's language, which will be evaluated when - the logpoint is hit. - - The value of the expression will then replace the {} expression in the - resulting log output. For example, if you specify the format string - "a={a}, b={b}", and the logpoint is hit when local variable a is 1 and - b is 2, the resulting log output would be "a=1, b=2". - -FLAGS - --condition=CONDITION - A condition to restrict when the log output is generated. When the - logpoint is hit, the condition will be evaluated, and the log output - will be generated only if the condition is true. - - --log-level=LOG_LEVEL; default="info" - The logging level to use when producing the log message. LOG_LEVEL must - be one of: info, warning, error. - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - - --wait=WAIT; default=10 - The number of seconds to wait to ensure that no error is returned from - a debugger agent when creating the logpoint. When a logpoint is - created, there will be a delay before the agents see and apply the - logpoint. Until at least one agent has attempted to enable the - logpoint, it cannot be determined if the logpoint is valid. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 beta debug logpoints create - diff --git a/gcloud/debug/logpoints/delete b/gcloud/debug/logpoints/delete deleted file mode 100644 index 5ae1134c8..000000000 --- a/gcloud/debug/logpoints/delete +++ /dev/null @@ -1,85 +0,0 @@ -NAME - gcloud debug logpoints delete - delete debug logpoints for a Cloud Debugger - debug target (debuggee) - -SYNOPSIS - gcloud debug logpoints delete [ID ...] [--all-users] [--include-inactive] - [--location=LOCATION-REGEXP] [--target=(ID|DESCRIPTION_REGEXP)] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May 31, - 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud debug logpoints delete is used to delete logpoints from a Cloud - Debugger debug target (debuggee). It will ask for confirmation before - deleting any logpoints. To suppress confirmation, use the global --quiet - option. - -EXAMPLES - To delete all active debug logpoints created by the current user of the - debug target (debuggee), without being prompted for confirmation, run: - - $ gcloud debug logpoints delete --target= --quiet - - To delete all active and inactive debug logpoints created by all users of - the debug target (debuggee), run: - - $ gcloud debug logpoints delete --target= \ - --include-inactive --all-users - - To delete the debug logpoints with IDs 'ID1' and 'ID2' (where ID1 and ID2 - were each created by different users) of the debug target (debuggee), run: - - $ gcloud debug logpoints delete ID1 ID2 --target= \ - --all-users - -POSITIONAL ARGUMENTS - [ID ...] - Zero or more logpoint resource identifiers. The specified logpoints - will be deleted. - -FLAGS - --all-users - If set, any location regexp will match logpoints from all users, rather - than only logpoints created by the current user. This flag is not - required when specifying the exact ID of a logpoint created by another - user. - - --include-inactive - If set, any location regexp will also match inactive logpoints, rather - than only logpoints which have not expired. This flag is not required - when specifying the exact ID of an inactive logpoint. - - --location=LOCATION-REGEXP - A regular expression to match against logpoint locations. All logpoints - matching this value will be deleted. You may specify --location - multiple times. - - EXAMPLE: - - gcloud debug logpoints delete \ - --location foo.py:[1-3] --location bar.py:4 - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and 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 variant is also available: - - $ gcloud beta debug logpoints delete - diff --git a/gcloud/debug/logpoints/help b/gcloud/debug/logpoints/help deleted file mode 100644 index b7feba9b1..000000000 --- a/gcloud/debug/logpoints/help +++ /dev/null @@ -1,95 +0,0 @@ -NAME - gcloud debug logpoints - commands for interacting with Cloud Debugger - logpoints - -SYNOPSIS - gcloud debug logpoints COMMAND [--target=(ID|DESCRIPTION_REGEXP)] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Commands for interacting with Cloud Debugger logpoints. - - Cloud Debugger is deprecated and will be shutdown May 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - Logpoints allow you to inject logging into running services without - restarting or interfering with the normal function of the service. Log - output will be sent to the appropriate log for the target's environment. On - App Engine, for example, output will go to the request log. - -EXAMPLES - The following command would log the value of the "name" attribute of the - "product" variable whenever any request executes line 123 of the file - product.py: - - $ gcloud debug logpoints create product.py:123 \ - "No description for {product.name}" - - The log output will appear wherever explicit logging output from your - program is normally written. For example, for an App Engine Standard - application, the output would appear in the request log. - - If you want to log output only when certain runtime conditions are met, you - can add a "--condition" option: - - $ gcloud debug logpoints create product.py:123 \ - "Suspicious price: {product.name} costs {price}" \ - --condition "price < .50" - - Logpoints remain active for 24 hours after creation. If you want to disable - a logpoint, use the logpoints delete command: - - $ gcloud debug logpoints delete product.* - - The above command would delete all logpoints in any file whose name begins - with "product". If you want to delete only a single logpoint, you should - first determine the logpoint ID using the logpoints list command, then - delete that specific ID: - - $ gcloud debug logpoints list ID LOCATION ... \ - 567890abcdef1-1234-56789 product.py:123 ... - $ gcloud debug logpoints delete 567890abcdef1-1234-56789 - - For App Engine services, logpoint resources include the "logQuery" - property, which is suitable for use with the "gcloud beta logging read" - command. You can save this property's value and use it to read logs from - the command line: - - $ log_query=$(gcloud debug logpoints create product.py:123 \ - "No description for {product.name}" --format="value(logQuery)") - $ gcloud logging read "$log_query" - -FLAGS - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (DEPRECATED) Add debug logpoints to a Cloud Debugger debug target - (debuggee). - - delete - (DEPRECATED) Delete debug logpoints for a Cloud Debugger debug target - (debuggee). - - list - (DEPRECATED) List the debug logpoints for a Cloud Debugger debug target - (debuggee). - -NOTES - This variant is also available: - - $ gcloud beta debug logpoints - diff --git a/gcloud/debug/logpoints/list b/gcloud/debug/logpoints/list deleted file mode 100644 index de96b0140..000000000 --- a/gcloud/debug/logpoints/list +++ /dev/null @@ -1,103 +0,0 @@ -NAME - gcloud debug logpoints list - list the debug logpoints for a Cloud Debugger - debug target (debuggee) - -SYNOPSIS - gcloud debug logpoints list [ID ...] [--no-all-users] - [--include-inactive=INCLUDE_INACTIVE; default=300] - [--location=LOCATION-REGEXP] [--target=(ID|DESCRIPTION_REGEXP)] - [--filter=EXPRESSION] [--limit=LIMIT] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May 31, - 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud debug logpoints list is used to display the debug logpoints for a - Cloud Debugger debug target (debuggee). By default all active logpoints are - returned. To obtain older, expired logoints, specify the --include-inactive - option. - -EXAMPLES - To list the active and recently completed debug logpoints of the debug - target (debuggee), run: - - $ gcloud debug logpoints list --target= - - To list all (both active and inactive) logpoints of the debug target - (debuggee), run: - - $ gcloud debug logpoints list --target= \ - --include-inactive=unlimited - - To list logpoints only created by the current user (by default all users - are returned) of the debug target (debuggee), run: - - $ gcloud debug logpoints list --target= --no-all-users - -POSITIONAL ARGUMENTS - [ID ...] - Zero or more logpoint resource identifiers. The specified logpoints - will be listed. - -FLAGS - --all-users - If false, display only logpoints created by the current user. Enabled - by default, use --no-all-users to disable. - - --include-inactive=INCLUDE_INACTIVE; default=300 - Include logpoints which failed or expired in the last INCLUDE_INACTIVE - seconds. If the value is "unlimited", all failed or expired logpoints - will be included. - - --location=LOCATION-REGEXP - A regular expression to match against logpoint locations. All logpoints - matching this value will be listed. You may specify --location multiple - times. - - EXAMPLE: - - gcloud debug logpoints list \ - --location foo.py:[1-3] --location bar.py:4 - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - -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. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud beta debug logpoints list - diff --git a/gcloud/debug/snapshots/create b/gcloud/debug/snapshots/create deleted file mode 100644 index 865856c82..000000000 --- a/gcloud/debug/snapshots/create +++ /dev/null @@ -1,93 +0,0 @@ -NAME - gcloud debug snapshots create - create debug snapshots for a Cloud Debugger - debug target (debuggee) - -SYNOPSIS - gcloud debug snapshots create LOCATION [--condition=CONDITION] - [--expression=EXPRESSION] [--target=(ID|DESCRIPTION_REGEXP)] - [--wait=WAIT; default=10] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May 31, - 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud debug snapshots create is used to create a debug snapshot on a Cloud - Debugger debug target. Snapshots allow you to capture stack traces and - local variables from your running service without interfering with normal - operations. - - When any instance of the target executes the snapshot location, the - optional condition expression is evaluated. If the result is true (or if - there is no condition), the instance captures the current thread state and - reports it back to Cloud Debugger. Once any instance captures a snapshot, - the snapshot is marked as completed, and it will not be captured again. - - You can view snapshot results in the developer console. It is also possible - to inspect snapshot results with the "snapshots describe" command. - -EXAMPLES - To create a snapshot with no conditions or expressions at line 41 of file - main.py of a debug target (debuggee), run: - - $ gcloud debug snapshots create main.py:41 --target= - - To create a snapshot at line 41 of file main.py on a debug target - (debuggee) that will only trigger if the variable name has the value of - 'foo', run: - - $ gcloud debug snapshots create main.py:41 --target= \ - --condition="name == 'foo'" - - To create a snapshot at line 41 of file main.py on a debug target - (debuggee) with the expressions name[0] and name[1], run: - - $ gcloud debug snapshots create main.py:41 --target= \ - --expression="name[0]" --expression="name[1]" - -POSITIONAL ARGUMENTS - LOCATION - The location where the snapshot should be taken. Locations are of the - form FILE:LINE, where FILE can be simply the file name, or the file - name preceded by enough path components to differntiate it from other - files with the same name. If the file name is not unique in the debug - target, the behavior is unspecified. - -FLAGS - --condition=CONDITION - A condition to restrict when the snapshot is taken. When the snapshot - location is executed, the condition will be evaluated, and the snapshot - will be generated only if the condition is true. - - --expression=EXPRESSION - An expression to evaluate when the snapshot is taken. You may specify - --expression multiple times. - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - - --wait=WAIT; default=10 - The number of seconds to wait to ensure that no error is returned from - a debugger agent when creating the snapshot. When a snapshot is - created, there will be a delay before the agents see and apply the - snapshot. Until at least one agent has attempted to enable the - snapshot, it cannot be determined if the snapshot is valid. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 beta debug snapshots create - diff --git a/gcloud/debug/snapshots/delete b/gcloud/debug/snapshots/delete deleted file mode 100644 index b4b314a38..000000000 --- a/gcloud/debug/snapshots/delete +++ /dev/null @@ -1,82 +0,0 @@ -NAME - gcloud debug snapshots delete - delete debug snapshots for a Cloud Debugger - debug target (debuggee) - -SYNOPSIS - gcloud debug snapshots delete [ID ...] [--all-users] [--include-inactive] - [--location=LOCATION-REGEXP] [--target=(ID|DESCRIPTION_REGEXP)] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May 31, - 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud debug snapshots delete is used to delete snapshots from a Cloud - Debugger debug target (debuggee). It will ask for confirmation before - deleting any snapshots. To suppress confirmation, use the global --quiet - option. - -EXAMPLES - To delete all active snapshots created by the current user of the debug - target (debuggee), without being prompted for confirmation, run: - - $ gcloud debug snapshots delete --target= --quiet - - To delete all active and inactive snapshots created by all users of the - debug target (debuggee), run: - - $ gcloud debug snapshots delete --target= --all-users \ - --include-inactive - - To delete the debug snapshots with IDs 'ID1' and 'ID2' (where ID1 and ID2 - were each created by different users) of the debug target (debuggee), run: - - $ gcloud debug snapshots delete ID1 ID2 --target= \ - --all-users - -POSITIONAL ARGUMENTS - [ID ...] - Zero or more snapshot resource identifiers. The specified snapshots - will be deleted. - -FLAGS - --all-users - If set, matching snapshots from all users will be deleted, rather than - only snapshots created by the current user. - - --include-inactive - If set, also delete snapshots which have been completed. By default, - only pending snapshots will be deleted. - - --location=LOCATION-REGEXP - A regular expression to match against snapshot locations. All snapshots - matching this value will be deleted. You may specify --location - multiple times. - - EXAMPLE: - - gcloud debug snapshots delete \ - --location foo.py:[1-3] --location bar.py:4 - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and 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 variant is also available: - - $ gcloud beta debug snapshots delete - diff --git a/gcloud/debug/snapshots/describe b/gcloud/debug/snapshots/describe deleted file mode 100644 index 1b0cb40ca..000000000 --- a/gcloud/debug/snapshots/describe +++ /dev/null @@ -1,68 +0,0 @@ -NAME - gcloud debug snapshots describe - describe the debug snapshots for a Cloud - Debugger debug target (debuggee) - -SYNOPSIS - gcloud debug snapshots describe [ID ...] [--location=LOCATION-REGEXP] - [--target=(ID|DESCRIPTION_REGEXP)] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May 31, - 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud debug snapshots describe is used to describe the debug snapshots for - a Cloud Debugger debug target (debuggee). If the snapshot has completed, - the output will include details on the stack trace and local variables, - stored in a compact form which is primarily intended to be machine-readable - rather than human-readable. - -EXAMPLES - To describe the debug snapshots for snapshots with IDs 'ID1' and 'ID2' of - the debug target (debuggee), run: - - $ gcloud debug snapshots describe ID1 ID2 --target= - - To describe all active snapshots in file main.py of the debug target - (debuggee), run: - - $ gcloud debug snapshots describe --target= \ - --location="main.py:.*" - -POSITIONAL ARGUMENTS - [ID ...] - Zero or more snapshot resource identifiers. The specified snapshots - will be displayed. - -FLAGS - --location=LOCATION-REGEXP - A regular expression to match against snapshot locations. All snapshots - matching this value will be displayed. You may specify --location - multiple times. - - EXAMPLE: - - gcloud debug snapshots describe \ - --location foo.py:[1-3] --location bar.py:4 - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and 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 variant is also available: - - $ gcloud beta debug snapshots describe - diff --git a/gcloud/debug/snapshots/help b/gcloud/debug/snapshots/help deleted file mode 100644 index 050ebf6df..000000000 --- a/gcloud/debug/snapshots/help +++ /dev/null @@ -1,60 +0,0 @@ -NAME - gcloud debug snapshots - commands for interacting with Cloud Debugger - snapshots - -SYNOPSIS - gcloud debug snapshots COMMAND [--target=(ID|DESCRIPTION_REGEXP)] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Commands for interacting with Cloud Debugger snapshots. - - Cloud Debugger is deprecated and will be shutdown May 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - Commands to interact with debug snapshots. Snapshots allow you to capture - stack traces and local variables from running services without interfering - with the normal function of the service. - -FLAGS - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (DEPRECATED) Create debug snapshots for a Cloud Debugger debug target - (debuggee). - - delete - (DEPRECATED) Delete debug snapshots for a Cloud Debugger debug target - (debuggee). - - describe - (DEPRECATED) Describe the debug snapshots for a Cloud Debugger debug - target (debuggee). - - list - (DEPRECATED) List the debug snapshots for a Cloud Debugger debug target - (debuggee). - - wait - (DEPRECATED) Wait for debug snapshots on a Cloud Debugger debug target - (debuggee) to complete. - -NOTES - This variant is also available: - - $ gcloud beta debug snapshots - diff --git a/gcloud/debug/snapshots/list b/gcloud/debug/snapshots/list deleted file mode 100644 index 1354def54..000000000 --- a/gcloud/debug/snapshots/list +++ /dev/null @@ -1,102 +0,0 @@ -NAME - gcloud debug snapshots list - list the debug snapshots for a Cloud Debugger - debug target (debuggee) - -SYNOPSIS - gcloud debug snapshots list [ID ...] [--all-users] - [--include-inactive=INCLUDE_INACTIVE; default=300] - [--location=LOCATION-REGEXP] [--target=(ID|DESCRIPTION_REGEXP)] - [--filter=EXPRESSION] [--limit=LIMIT] [--sort-by=[FIELD,...]] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May 31, - 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud debug snapshots list is used to display the debug snapshots for a - Cloud Debugger debug target (debuggee). By default all active snapshots as - well as any recently completed snapshots are returned. To obtain older - completed snapshots specify the --include-inactive option. - -EXAMPLES - To list the active and recently completed debug snapshots of the debug - target (debuggee), run: - - $ gcloud debug snapshots list --target= - - To list all (both active and inactive) snapshots of the debug target - (debuggee), run: - - $ gcloud debug snapshots list --include-inactive=unlimited \ - --target= - - To list snapshots created by all users of the debug target (debuggee), run: - - $ gcloud debug snapshots list --all-users --target= - -POSITIONAL ARGUMENTS - [ID ...] - Zero or more snapshot resource identifiers. The specified snapshots - will be displayed. - -FLAGS - --all-users - If set, display snapshots from all users, rather than only the current - user. - - --include-inactive=INCLUDE_INACTIVE; default=300 - Include snapshots which have completed in the last INCLUDE_INACTIVE - seconds. If the value is "unlimited", all inactive snapshots will be - included. - - --location=LOCATION-REGEXP - A regular expression to match against snapshot locations. All snapshots - matching this value will be displayed. You may specify --location - multiple times. - - EXAMPLE: - - gcloud debug snapshots list \ - --location foo.py:[1-3] --location bar.py:4 - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - -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. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud beta debug snapshots list - diff --git a/gcloud/debug/snapshots/wait b/gcloud/debug/snapshots/wait deleted file mode 100644 index d3de9a305..000000000 --- a/gcloud/debug/snapshots/wait +++ /dev/null @@ -1,104 +0,0 @@ -NAME - gcloud debug snapshots wait - wait for debug snapshots on a Cloud Debugger - debug target (debuggee) to complete - -SYNOPSIS - gcloud debug snapshots wait [ID ...] [--all] [--all-users] - [--location=LOCATION-REGEXP] [--target=(ID|DESCRIPTION_REGEXP)] - [--timeout=TIMEOUT; default="unlimited"] [--filter=EXPRESSION] - [--limit=LIMIT] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May 31, - 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud debug snapshots wait is used to wait for one or more snapshots on a - Cloud Debugger debug target to complete. A snapshot is considered completed - either if there was an error setting the snapshot or if the snapshot was - hit on an instance of the debug target. - -EXAMPLES - To wait for either of the snapshots with IDs of 'ID1' or 'ID2' of the debug - target (debuggee) to complete, run: - - $ gcloud debug snapshots wait ID1 ID2 --target= - - To wait for both of the snapshots with IDs 'ID1' and 'ID2' of the debug - target (debuggee) to complete, run: - - $ gcloud debug snapshots wait ID1 ID2 --target= --all - - To wait up to 30 seconds for the snapshot with ID 'ID1' of the debug target - (debuggee) to complete, run: - - $ gcloud debug snapshots wait ID1 --target= --timeout=30 - -POSITIONAL ARGUMENTS - [ID ...] - Zero or more snapshot resource identifiers. The command will wait for - any of the specified snapshots to complete. - -FLAGS - --all - If set, wait for all of the specified snapshots to complete, instead of - waiting for any one of them to complete. - - --all-users - If set, wait for matching snapshots from all users, rather than only - the current user. - - --location=LOCATION-REGEXP - A regular expression to match against snapshot locations. The command - will wait for any snapshots matching these criteria to complete. You - may specify --location multiple times. - - EXAMPLE: - - gcloud debug snapshots wait \ - --location foo.py:[1-3] --location bar.py:3 - - --target=(ID|DESCRIPTION_REGEXP) - The debug target. It may be a target ID or name obtained from 'debug - targets list', or it may be a regular expression uniquely specifying a - debuggee based on its description or name. For App Engine projects, if - not specified, the default target is the most recent deployment of the - default module and version. - - --timeout=TIMEOUT; default="unlimited" - Maximum number of seconds to wait for a snapshot to complete. By - default, wait indefinitely. - -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. - - --sort-by=[FIELD,...] - Comma-separated list of resource field key names to sort by. The - default order is ascending. Prefix a field with ``~'' for descending - order on that field. This flag interacts with other flags that are - applied in this order: --flatten, --sort-by, --filter, --limit. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This variant is also available: - - $ gcloud beta debug snapshots wait - diff --git a/gcloud/debug/source/gen-repo-info-file b/gcloud/debug/source/gen-repo-info-file deleted file mode 100644 index 09f1482ed..000000000 --- a/gcloud/debug/source/gen-repo-info-file +++ /dev/null @@ -1,46 +0,0 @@ -NAME - gcloud debug source gen-repo-info-file - generates repository information - files for the Cloud Debugger - -SYNOPSIS - gcloud debug source gen-repo-info-file - [--output-directory=OUTPUT_DIRECTORY; default="."] - [--source-directory=SOURCE_DIRECTORY; default="."] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May 31, - 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - This command generates a file named source-context.json containing - information on the source revision and remote repository associated with - the given source directory. - -EXAMPLES - To generate repository information files for your app, from your source - directory run: - - $ gcloud debug source gen-repo-info-file - -FLAGS - --output-directory=OUTPUT_DIRECTORY; default="." - The directory in which to create the source context file. - - --source-directory=SOURCE_DIRECTORY; default="." - The directory containing the source code for the build. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --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 beta debug source gen-repo-info-file - diff --git a/gcloud/debug/source/help b/gcloud/debug/source/help deleted file mode 100644 index b1ef991a7..000000000 --- a/gcloud/debug/source/help +++ /dev/null @@ -1,34 +0,0 @@ -NAME - gcloud debug source - commands to manage source information for Cloud - Debugger - -SYNOPSIS - gcloud debug source COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Commands to manage source information for Cloud Debugger. - - Cloud Debugger is deprecated and will be shutdown May 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - This set of commands allows you to provide Cloud Debugger with source code - version information. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - gen-repo-info-file - (DEPRECATED) Generates repository information files for the Cloud - Debugger. - -NOTES - This variant is also available: - - $ gcloud beta debug source - diff --git a/gcloud/debug/targets/help b/gcloud/debug/targets/help deleted file mode 100644 index 130a96bbf..000000000 --- a/gcloud/debug/targets/help +++ /dev/null @@ -1,40 +0,0 @@ -NAME - gcloud debug targets - commands for interacting with Cloud Debugger debug - targets - -SYNOPSIS - gcloud debug targets COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (DEPRECATED) Commands for interacting with Cloud Debugger debug targets. - - Cloud Debugger is deprecated and will be shutdown May 31, 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - Commands to interact with debug targets. A debug target can be an App - Engine module version or any other entity enabled for use with the cloud - debugger. - -EXAMPLES - To view all available debug targets, run: - - $ gcloud debug targets list - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - list - (DEPRECATED) List the debug targets (debuggees) registered with the - Cloud Debugger. - -NOTES - This variant is also available: - - $ gcloud beta debug targets - diff --git a/gcloud/iam/workforce-pools/providers/create-oidc b/gcloud/iam/workforce-pools/providers/create-oidc index e4bf33971..4a5149e94 100644 --- a/gcloud/iam/workforce-pools/providers/create-oidc +++ b/gcloud/iam/workforce-pools/providers/create-oidc @@ -6,12 +6,12 @@ SYNOPSIS gcloud iam workforce-pools providers create-oidc (PROVIDER : --location=LOCATION --workforce-pool=WORKFORCE_POOL) --attribute-mapping=[ATTRIBUTE_MAPPING,...] --client-id=CLIENT_ID - --issuer-uri=ISSUER_URI [--async] - [--attribute-condition=ATTRIBUTE_CONDITION] [--description=DESCRIPTION] - [--disabled] [--display-name=DISPLAY_NAME] - [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR, - [...]] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] - [GCLOUD_WIDE_FLAG ...] + --issuer-uri=ISSUER_URI + (--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE) [--async] + [--attribute-condition=ATTRIBUTE_CONDITION] + [--client-secret-value=CLIENT_SECRET_VALUE] [--description=DESCRIPTION] + [--disabled] [--display-name=DISPLAY_NAME] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a new OIDC workforce pool provider. @@ -146,6 +146,42 @@ REQUIRED FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. + This must be specified. + + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR + The behavior for how OIDC Claims are included in the assertion object + used for attribute mapping and attribute condition. + + Use merge-user-info-over-id-token-claims to merge the UserInfo + Endpoint Claims with ID Token Claims, preferring UserInfo Claim + Values for the same Claim Name. Currently this option is only + available for Authorization Code flow. + + Use only-id-token-claims to include only ID token claims. + + WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be one of: + assertion-claims-behavior-unspecified, + merge-user-info-over-id-token-claims, only-id-token-claims. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --web-sso-response-type=WEB_SSO_RESPONSE_TYPE + Response Type to request for in the OIDC Authorization Request for + web sign-in. + + Use code to select the authorization code flow + (https://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth) + + Use id-token to select the implicit flow + (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). + + WEB_SSO_RESPONSE_TYPE must be one of: code, id-token, + response-type-unspecified. + + This flag argument must be specified if any of the other arguments in + this group are specified. + OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to @@ -178,6 +214,10 @@ OPTIONAL FLAGS "'admins' in google.groups" + --client-secret-value=CLIENT_SECRET_VALUE + The OIDC client secret. Required to enable Authorization Code flow for + web sign-in. + --description=DESCRIPTION A description for the workforce pool provider. Cannot exceed 256 characters in length. @@ -192,19 +232,6 @@ OPTIONAL FLAGS A display name for the workforce pool provider. Cannot exceed 32 characters in length. - --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR,[...] - The behavior for how OIDC Claims are included in the assertion object - used for attribute mapping and attribute condition. Use - only-id-token-claims to include only ID token claims. - WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be (only one value is - supported): only-id-token-claims. - - --web-sso-response-type=WEB_SSO_RESPONSE_TYPE - Response Type to request for in the OIDC Authorization Request for web - sign-in. Use id-token to select the implicit flow - (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). - WEB_SSO_RESPONSE_TYPE must be (only one value is supported): id-token. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/iam/workforce-pools/providers/update-oidc b/gcloud/iam/workforce-pools/providers/update-oidc index fb763cdda..74dc8aec4 100644 --- a/gcloud/iam/workforce-pools/providers/update-oidc +++ b/gcloud/iam/workforce-pools/providers/update-oidc @@ -9,8 +9,9 @@ SYNOPSIS [--attribute-mapping=[ATTRIBUTE_MAPPING,...]] [--client-id=CLIENT_ID] [--description=DESCRIPTION] [--disabled] [--display-name=DISPLAY_NAME] [--issuer-uri=ISSUER_URI] - [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR, - [...]] [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] + [--web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR] + [--web-sso-response-type=WEB_SSO_RESPONSE_TYPE] + [--clear-client-secret | --client-secret-value=CLIENT_SECRET_VALUE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -191,18 +192,34 @@ FLAGS --issuer-uri=ISSUER_URI The OIDC issuer URI. Must be a valid URI using the 'https' scheme. - --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR,[...] + --web-sso-assertion-claims-behavior=WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR The behavior for how OIDC Claims are included in the assertion object used for attribute mapping and attribute condition. Use - only-id-token-claims to include only ID token claims. - WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be (only one value is - supported): only-id-token-claims. + merge-user-info-over-id-token-claims to merge the UserInfo Endpoint + Claims with ID Token Claims, preferring UserInfo Claim Values for the + same Claim Name. Currently this option is only available for + Authorization Code flow. Use only-id-token-claims to include only ID + token claims. WEB_SSO_ASSERTION_CLAIMS_BEHAVIOR must be one of: + assertion-claims-behavior-unspecified, + merge-user-info-over-id-token-claims, only-id-token-claims. --web-sso-response-type=WEB_SSO_RESPONSE_TYPE Response Type to request for in the OIDC Authorization Request for web - sign-in. Use id-token to select the implicit flow + sign-in. Use code to select the authorization code flow + (https://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth) + Use id-token to select the implicit flow (https://openid.net/specs/openid-connect-core-1_0.html#ImplicitFlowAuth). - WEB_SSO_RESPONSE_TYPE must be (only one value is supported): id-token. + WEB_SSO_RESPONSE_TYPE must be one of: code, id-token, + response-type-unspecified. + + At most one of these can be specified: + + --clear-client-secret + Clear the OIDC client secret. + + --client-secret-value=CLIENT_SECRET_VALUE + The OIDC client secret. Required to enable Authorization Code flow + for web sign-in. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/network-connectivity/hubs/add-iam-policy-binding b/gcloud/network-connectivity/hubs/add-iam-policy-binding new file mode 100644 index 000000000..3be3b7e9d --- /dev/null +++ b/gcloud/network-connectivity/hubs/add-iam-policy-binding @@ -0,0 +1,72 @@ +NAME + gcloud network-connectivity hubs add-iam-policy-binding - add an IAM policy + binding to the IAM policy of a hub resource + +SYNOPSIS + gcloud network-connectivity hubs add-iam-policy-binding HUB + --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Add an IAM policy binding to the IAM policy of a hub resource. One binding + consists of a member, a role, and an optional condition. + +EXAMPLES + To grant a user the roles/networkconnectivity.groupUser role on the hub + called my-hub, run the following command: + + $ gcloud network-connectivity hubs add-iam-policy-binding my-hub \ + --member="user:username@gmail.com" \ + --role="roles/networkconnectivity.groupUser" + +POSITIONAL ARGUMENTS + Hub resource - The hub that you want to update. 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 hub on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▸ provide the argument hub on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to add the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + Role name to assign to the principal. The role name is the complete + path of a predefined role, such as roles/logging.viewer, or the role ID + for a custom role, such as + organizations/{ORGANIZATION_ID}/roles/logging.viewer. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/debug/targets/list b/gcloud/network-connectivity/hubs/get-iam-policy similarity index 56% rename from gcloud/debug/targets/list rename to gcloud/network-connectivity/hubs/get-iam-policy index c56674435..e800df941 100644 --- a/gcloud/debug/targets/list +++ b/gcloud/network-connectivity/hubs/get-iam-policy @@ -1,37 +1,39 @@ NAME - gcloud debug targets list - list the debug targets (debuggees) registered - with the Cloud Debugger + gcloud network-connectivity hubs get-iam-policy - get the IAM policy for a + hub resource SYNOPSIS - gcloud debug targets list [--include-inactive] [--filter=EXPRESSION] - [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud network-connectivity hubs get-iam-policy HUB [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (DEPRECATED) Cloud Debugger is deprecated and will be shutdown May 31, - 2023. - - See: https://cloud.google.com/debugger/docs/deprecations - - gcloud debug targets list is used to display a list of the debug targets - (debuggees) registered with the Cloud Debugger. By default only the active - targets are shown, the --include-inactive can be provided to also include - the targets that are no longer active. + Get the IAM policy of a hub. If formatted as JSON, the output can be edited + and used as a policy file for set-iam-policy. EXAMPLES - To list the active debug targets (debuggees) registered with the Cloud - Debugger, run: + To get the IAM policy for a hub named my-hub, run: - $ gcloud debug targets list + $ gcloud network-connectivity hubs get-iam-policy my-hub - To list all (both active and inactive) debug targets (debuggees) registered - with the Cloud Debugger, run: +POSITIONAL ARGUMENTS + Hub resource - The hub for which you want 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. - $ gcloud debug targets list --include-inactive + To set the project attribute: + ◆ provide the argument hub on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. -FLAGS - --include-inactive - If set, include targets which are no longer active. + This must be specified. + + HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▸ provide the argument hub on the command line. LIST COMMAND FLAGS --filter=EXPRESSION @@ -59,12 +61,6 @@ LIST COMMAND FLAGS order on that field. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit. - --uri - Print a list of resource URIs instead of the default output, and change - the command output to a list of URIs. If this flag is used with - --format, the formatting is applied on this URI list. To display URIs - alongside other keys instead, use the uri() transform. - GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -73,8 +69,7 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. -NOTES - This variant is also available: - - $ gcloud beta debug targets list - +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/hubs/help b/gcloud/network-connectivity/hubs/help index c54b168bf..c696e075a 100644 --- a/gcloud/network-connectivity/hubs/help +++ b/gcloud/network-connectivity/hubs/help @@ -12,9 +12,18 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. +GROUPS + GROUP is one of the following: + + route-tables + Manage Network Connectivity Center route tables. + COMMANDS COMMAND is one of the following: + add-iam-policy-binding + Add an IAM policy binding to the IAM policy of a hub resource. + create Create a new hub. @@ -24,9 +33,21 @@ COMMANDS describe Describe a hub. + get-iam-policy + Get the IAM policy for a hub resource. + list List hubs. + list-spokes + List hub spokes. + + remove-iam-policy-binding + Remove an IAM policy binding from the IAM policy of a hub resource. + + set-iam-policy + Set the IAM policy of a hub resource. + update Update a hub. diff --git a/gcloud/network-connectivity/hubs/list-spokes b/gcloud/network-connectivity/hubs/list-spokes new file mode 100644 index 000000000..b7f9b0a58 --- /dev/null +++ b/gcloud/network-connectivity/hubs/list-spokes @@ -0,0 +1,86 @@ +NAME + gcloud network-connectivity hubs list-spokes - list hub spokes + +SYNOPSIS + gcloud network-connectivity hubs list-spokes HUB + [--spoke-locations=[LOCATION,...]] [--view=VIEW; default="basic"] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieve and display a list of all spokes associated with a hub. + +EXAMPLES + To list all spokes in the us-central1 region and the global location, run: + + $ gcloud network-connectivity hubs list-spokes \ + --spoke-locations=us-central1,global + +POSITIONAL ARGUMENTS + Hub resource - Name of the hub associated with the returned list of + spokes. 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 hub 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. + + HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▸ provide the argument hub on the command line. + +FLAGS + --spoke-locations=[LOCATION,...] + A comma separated list of locations. The locations can be set to + 'global' and/or Google Cloud supported regions. To see the names of + regions, see Viewing a list of available regions + (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). + + --view=VIEW; default="basic" + Enumeration to control which spoke fields are included in the response. + VIEW must be one of: basic, detailed. + +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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/hubs/remove-iam-policy-binding b/gcloud/network-connectivity/hubs/remove-iam-policy-binding new file mode 100644 index 000000000..81b8b33ca --- /dev/null +++ b/gcloud/network-connectivity/hubs/remove-iam-policy-binding @@ -0,0 +1,72 @@ +NAME + gcloud network-connectivity hubs remove-iam-policy-binding - remove an IAM + policy binding from the IAM policy of a hub resource + +SYNOPSIS + gcloud network-connectivity hubs remove-iam-policy-binding HUB + --member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Remove an IAM policy binding from the IAM policy of a hub resource. + +EXAMPLES + To remove the roles/networkconnectivity.groupUser role from a user of the + hub my-hub, run: + + $ gcloud network-connectivity hubs remove-iam-policy-binding \ + my-hub --member="user:username@gmail.com" \ + --role="roles/networkconnectivity.groupUser" + +POSITIONAL ARGUMENTS + Hub resource - The hub that you want to update. 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 hub on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▸ provide the argument hub on the command line. + +REQUIRED FLAGS + --member=PRINCIPAL + The principal to remove the binding for. Should be of the form + user|group|serviceAccount:email or domain:domain. + + Examples: user:test-user@gmail.com, group:admins@example.com, + serviceAccount:test123@example.domain.com, or + domain:example.domain.com. + + Deleted principals have an additional deleted: prefix and a ?uid=UID + suffix, where UID is a unique identifier for the principal. Example: + deleted:user:test-user@gmail.com?uid=123456789012345678901. + + Some resources also accept the following special values: + ◆ allUsers - Special identifier that represents anyone who is on the + internet, with or without a Google account. + ◆ allAuthenticatedUsers - Special identifier that represents anyone + who is authenticated with a Google account or a service account. + + --role=ROLE + The role to remove the principal from. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/hubs/route-tables/describe b/gcloud/network-connectivity/hubs/route-tables/describe new file mode 100644 index 000000000..b4e7f01aa --- /dev/null +++ b/gcloud/network-connectivity/hubs/route-tables/describe @@ -0,0 +1,61 @@ +NAME + gcloud network-connectivity hubs route-tables describe - describe a route + table + +SYNOPSIS + gcloud network-connectivity hubs route-tables describe + (ROUTE_TABLE : --hub=HUB) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieve and display details about a route table. + +EXAMPLES + To display details about a route table named my-route-table, run: + + $ gcloud network-connectivity hubs route-tables describe \ + my-route-table + +POSITIONAL ARGUMENTS + Route table resource - Name of the route table to describe. The arguments + in this group can be used to specify the attributes of this resource. + (NOTE) Some attributes are not given arguments in this group but can be + set in other ways. + + To set the project attribute: + ◆ provide the argument route_table on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + ROUTE_TABLE + ID of the route table or fully qualified identifier for the route + table. + + To set the route_table attribute: + ▸ provide the argument route_table on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --hub=HUB + Id of the hub. + + To set the hub attribute: + ▸ provide the argument route_table on the command line with a fully + specified name; + ▸ provide the argument --hub on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/hubs/route-tables/help b/gcloud/network-connectivity/hubs/route-tables/help new file mode 100644 index 000000000..aa8f79499 --- /dev/null +++ b/gcloud/network-connectivity/hubs/route-tables/help @@ -0,0 +1,30 @@ +NAME + gcloud network-connectivity hubs route-tables - manage Network Connectivity + Center route tables + +SYNOPSIS + gcloud network-connectivity hubs route-tables GROUP | COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Network Connectivity Center route tables. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + routes + Manage Network Connectivity Center routes. + +COMMANDS + COMMAND is one of the following: + + describe + Describe a route table. + + list + List route tables. diff --git a/gcloud/network-connectivity/hubs/route-tables/list b/gcloud/network-connectivity/hubs/route-tables/list new file mode 100644 index 000000000..1f1df7827 --- /dev/null +++ b/gcloud/network-connectivity/hubs/route-tables/list @@ -0,0 +1,77 @@ +NAME + gcloud network-connectivity hubs route-tables list - list route tables + +SYNOPSIS + gcloud network-connectivity hubs route-tables list --hub=HUB + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieve and display a list of all route tables in the specified hub. + +EXAMPLES + To list all route tables across all hubs, run: + + $ gcloud network-connectivity hubs route-tables list --hub=- + + To list all route tables in hub my-hub, run: + + $gcloud network-connectivity hubs route-tables list --hub=my-hub + +REQUIRED FLAGS + Hub resource - Parent hub of the route tables to display. This represents + a Cloud resource. (NOTE) Some attributes are not given arguments in this + group but can be set in other ways. + + To set the project attribute: + ◆ provide the argument --hub on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --hub=HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▸ provide the argument --hub on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/hubs/route-tables/routes/describe b/gcloud/network-connectivity/hubs/route-tables/routes/describe new file mode 100644 index 000000000..5a99f894c --- /dev/null +++ b/gcloud/network-connectivity/hubs/route-tables/routes/describe @@ -0,0 +1,68 @@ +NAME + gcloud network-connectivity hubs route-tables routes describe - describe a + route + +SYNOPSIS + gcloud network-connectivity hubs route-tables routes describe + (ROUTE : --hub=HUB --route_table=ROUTE_TABLE) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieve and display details about a route. + +EXAMPLES + To display details about a route named my-route, run: + + $ gcloud network-connectivity hubs route-tables routes describe \ + my-route + +POSITIONAL ARGUMENTS + Route resource - Name of the route to describe. The arguments in this + group can be used to specify the attributes of this resource. (NOTE) Some + attributes are not given arguments in this group but can be set in other + ways. + + To set the project attribute: + ◆ provide the argument route on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + ROUTE + ID of the route or fully qualified identifier for the route. + + To set the route attribute: + ▸ provide the argument route on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --hub=HUB + Id of the hub. + + To set the hub attribute: + ▸ provide the argument route on the command line with a fully + specified name; + ▸ provide the argument --hub on the command line. + + --route_table=ROUTE_TABLE + Id of the route table. + + To set the route_table attribute: + ▸ provide the argument route on the command line with a fully + specified name; + ▸ provide the argument --route_table on the command line. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/hubs/route-tables/routes/help b/gcloud/network-connectivity/hubs/route-tables/routes/help new file mode 100644 index 000000000..a7df8359f --- /dev/null +++ b/gcloud/network-connectivity/hubs/route-tables/routes/help @@ -0,0 +1,24 @@ +NAME + gcloud network-connectivity hubs route-tables routes - manage Network + Connectivity Center routes + +SYNOPSIS + gcloud network-connectivity hubs route-tables routes COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Network Connectivity Center routes. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe a route. + + list + List routes. diff --git a/gcloud/network-connectivity/hubs/route-tables/routes/list b/gcloud/network-connectivity/hubs/route-tables/routes/list new file mode 100644 index 000000000..a4fe07124 --- /dev/null +++ b/gcloud/network-connectivity/hubs/route-tables/routes/list @@ -0,0 +1,92 @@ +NAME + gcloud network-connectivity hubs route-tables routes list - list routes + +SYNOPSIS + gcloud network-connectivity hubs route-tables routes list + (--route_table=ROUTE_TABLE : --hub=HUB) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieve and display a list of all routes in the specified route table. + +EXAMPLES + To list all routes across all route tables, run: + + $ gcloud network-connectivity hubs route-tables routes list \ + --hub=- --route_table=- + + To list all routes in route table my-route-table, run: + + $gcloud network-connectivity hubs route-tables routes list --hub=my-hub --route_table=my-route-table + +REQUIRED FLAGS + Route table resource - Parent route table of the routes to display. 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 --route_table on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --route_table=ROUTE_TABLE + ID of the route table or fully qualified identifier for the route + table. + + To set the route_table attribute: + ▸ provide the argument --route_table on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --hub=HUB + Id of the hub. + + To set the hub attribute: + ▸ provide the argument --route_table on the command line with a + fully specified name; + ▸ provide the argument --hub on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/hubs/set-iam-policy b/gcloud/network-connectivity/hubs/set-iam-policy new file mode 100644 index 000000000..fa1a3f636 --- /dev/null +++ b/gcloud/network-connectivity/hubs/set-iam-policy @@ -0,0 +1,56 @@ +NAME + gcloud network-connectivity hubs set-iam-policy - set the IAM policy of a + hub resource + +SYNOPSIS + gcloud network-connectivity hubs set-iam-policy HUB POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Replace the existing IAM policy of a hub resource with a policy encoded in + a JSON or YAML file. + +EXAMPLES + To replace the IAM policy of a hub resource with the policy defined in a + file called policy.json, run: + + $ gcloud network-connectivity hubs set-iam-policy my-hub policy.json + +POSITIONAL ARGUMENTS + Hub resource - The hub for which to set 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 hub on the command line with a fully specified + name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + HUB + ID of the hub or fully qualified identifier for the hub. + + To set the hub attribute: + ▸ provide the argument hub on the command line. + + POLICY_FILE + Path to a local JSON or YAML formatted file containing a valid policy. + + The output of the get-iam-policy command is a valid file, as is any + JSON or YAML file conforming to the structure of a Policy + (https://cloud.google.com/iam/reference/rest/v1/Policy). + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/spokes/accept b/gcloud/network-connectivity/spokes/accept new file mode 100644 index 000000000..76e80ba83 --- /dev/null +++ b/gcloud/network-connectivity/spokes/accept @@ -0,0 +1,61 @@ +NAME + gcloud network-connectivity spokes accept - accept a spoke + +SYNOPSIS + gcloud network-connectivity spokes accept SPOKE [--async] [--global] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Accept a proposed or previously rejected VPC spoke. By accepting a spoke, + you permit connectivity between the associated VPC network and other VPC + networks that are attached to the same hub. + +EXAMPLES + To accept a spoke named myspoke, run: + + $ gcloud network-connectivity spokes accept myspoke --global + +POSITIONAL ARGUMENTS + Spoke resource - Name of the spoke to accept. 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 spoke on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --global on the command line. + + This must be specified. + + SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument spoke on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --global + Indicates that the spoke is global. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/spokes/delete b/gcloud/network-connectivity/spokes/delete index 4bd4d2eff..ac23eed6b 100644 --- a/gcloud/network-connectivity/spokes/delete +++ b/gcloud/network-connectivity/spokes/delete @@ -2,8 +2,8 @@ NAME gcloud network-connectivity spokes delete - delete a spoke SYNOPSIS - gcloud network-connectivity spokes delete SPOKE [--async] [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + gcloud network-connectivity spokes delete SPOKE [--async] + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Delete the specified spoke. @@ -44,10 +44,15 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. - --region=REGION - A Google Cloud region. To see the names of regions, see Viewing a list - of available regions - (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). + At most one of these can be specified: + + --global + Indicates that the spoke is global. + + --region=REGION + A Google Cloud region. To see the names of regions, see Viewing a + list of available regions + (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/network-connectivity/spokes/describe b/gcloud/network-connectivity/spokes/describe index 4f0fe1d41..202b88079 100644 --- a/gcloud/network-connectivity/spokes/describe +++ b/gcloud/network-connectivity/spokes/describe @@ -2,8 +2,8 @@ NAME gcloud network-connectivity spokes describe - describe a spoke SYNOPSIS - gcloud network-connectivity spokes describe SPOKE [--region=REGION] - [GCLOUD_WIDE_FLAG ...] + gcloud network-connectivity spokes describe SPOKE + [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Retrieve and display details about a spoke. @@ -41,10 +41,15 @@ POSITIONAL ARGUMENTS ▸ provide the argument spoke on the command line. FLAGS - --region=REGION - A Google Cloud region. To see the names of regions, see Viewing a list - of available regions - (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). + At most one of these can be specified: + + --global + Indicates that the spoke is global. + + --region=REGION + A Google Cloud region. To see the names of regions, see Viewing a + list of available regions + (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/network-connectivity/spokes/help b/gcloud/network-connectivity/spokes/help index ab07b4b7e..2471bd71e 100644 --- a/gcloud/network-connectivity/spokes/help +++ b/gcloud/network-connectivity/spokes/help @@ -22,12 +22,18 @@ GROUPS linked-router-appliances Manage Router appliance spokes. + linked-vpc-network + Manage VPC spokes. + linked-vpn-tunnels Manage VPN spokes. COMMANDS COMMAND is one of the following: + accept + Accept a spoke. + delete Delete a spoke. @@ -37,6 +43,9 @@ COMMANDS list List spokes. + reject + Reject a spoke. + NOTES This variant is also available: diff --git a/gcloud/network-connectivity/spokes/linked-vpc-network/create b/gcloud/network-connectivity/spokes/linked-vpc-network/create new file mode 100644 index 000000000..f229bfbf6 --- /dev/null +++ b/gcloud/network-connectivity/spokes/linked-vpc-network/create @@ -0,0 +1,90 @@ +NAME + gcloud network-connectivity spokes linked-vpc-network create - create a new + VPC spoke + +SYNOPSIS + gcloud network-connectivity spokes linked-vpc-network create SPOKE + --hub=HUB --vpc-network=VPC_NETWORK [--async] + [--description=DESCRIPTION] [--exclude-export-ranges=[CIDR_RANGE,...]] + [--global] [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new VPC spoke. + +EXAMPLES + To create a VPC spoke named myspoke, run: + + $ gcloud network-connectivity spokes linked-vpc-network create \ + myspoke \ + --hub="https://www.googleapis.com/networkconnectivity/v1/project\ + s/my-project/locations/global/hubs/my-hub" --global \ + --vpc-network="https://www.googleapis.com/compute/v1/projects/my\ + -project/global/networks/my-vpc" + +POSITIONAL ARGUMENTS + Spoke resource - Name of the spoke to create. 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 spoke on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --global on the command line. + + This must be specified. + + SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument spoke on the command line. + +REQUIRED FLAGS + --hub=HUB + Hub that the spoke will attach to. The hub must already exist. + + --vpc-network=VPC_NETWORK + VPC network that the spoke provides connectivity to. The resource must + already exist. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description of the spoke to create. + + --exclude-export-ranges=[CIDR_RANGE,...] + IP address range(s) to hide from subnets in VPC networks that are + peered through Network Connectivity Center peering. + + --global + Indicates that the spoke is global. + + --labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to add. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/spokes/linked-vpc-network/help b/gcloud/network-connectivity/spokes/linked-vpc-network/help new file mode 100644 index 000000000..c8c5ef6fa --- /dev/null +++ b/gcloud/network-connectivity/spokes/linked-vpc-network/help @@ -0,0 +1,23 @@ +NAME + gcloud network-connectivity spokes linked-vpc-network - manage VPC spokes + +SYNOPSIS + gcloud network-connectivity spokes linked-vpc-network COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage VPC spokes. + +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 new VPC spoke. + + update + Update a VPC spoke. diff --git a/gcloud/network-connectivity/spokes/linked-vpc-network/update b/gcloud/network-connectivity/spokes/linked-vpc-network/update new file mode 100644 index 000000000..e422cb6d5 --- /dev/null +++ b/gcloud/network-connectivity/spokes/linked-vpc-network/update @@ -0,0 +1,96 @@ +NAME + gcloud network-connectivity spokes linked-vpc-network update - update a VPC + spoke + +SYNOPSIS + gcloud network-connectivity spokes linked-vpc-network update SPOKE + [--async] [--description=DESCRIPTION] [--global] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update the details of a VPC spoke. + +EXAMPLES + To update the description of a global VPC spoke named my-spoke, run: + + $ gcloud network-connectivity spokes linked-vpc-network update \ + myspoke --global --description="new spoke description" + +POSITIONAL ARGUMENTS + Spoke resource - Name of the spoke to update. 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 spoke on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --global on the command line. + + This must be specified. + + SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument spoke on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + New description of the spoke. + + --global + Indicates that the spoke is global. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud network-connectivity spokes linked-vpc-network update \ + --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud network-connectivity spokes linked-vpc-network update \ + --clear-labels --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/spokes/list b/gcloud/network-connectivity/spokes/list index 9e93901f0..d24e622a1 100644 --- a/gcloud/network-connectivity/spokes/list +++ b/gcloud/network-connectivity/spokes/list @@ -2,7 +2,7 @@ NAME gcloud network-connectivity spokes list - list spokes SYNOPSIS - gcloud network-connectivity spokes list [--region=REGION] + gcloud network-connectivity spokes list [--global | --region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] @@ -19,11 +19,16 @@ EXAMPLES $ gcloud network-connectivity spokes list FLAGS - --region=REGION - A Google Cloud region. To see the names of regions, see Viewing a list - of available regions - (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). - Use ``-`` to specify all regions. + At most one of these can be specified: + + --global + Indicates that the spoke is global. + + --region=REGION + A Google Cloud region. To see the names of regions, see Viewing a + list of available regions + (https://cloud.google.com/compute/docs/regions-zones/viewing-regions-zones#viewing_a_list_of_available_regions). + Use ``-`` to specify all regions. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/network-connectivity/spokes/reject b/gcloud/network-connectivity/spokes/reject new file mode 100644 index 000000000..7b1b077d0 --- /dev/null +++ b/gcloud/network-connectivity/spokes/reject @@ -0,0 +1,65 @@ +NAME + gcloud network-connectivity spokes reject - reject a spoke + +SYNOPSIS + gcloud network-connectivity spokes reject SPOKE [--async] + [--details=DETAILS] [--global] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Reject a VPC spoke. By rejecting a spoke, you prevent or remove + connectivity between the associated VPC network and any other VPC networks + that are attached to the same hub. + +EXAMPLES + To reject a spoke named myspoke with reason myreason, run: + + $ gcloud network-connectivity spokes reject myspoke \ + --details="myreason" --global + +POSITIONAL ARGUMENTS + Spoke resource - Name of the spoke to reject. 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 spoke on the command line with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + To set the location attribute: + ◆ provide the argument spoke on the command line with a fully specified + name; + ◆ provide the argument --global on the command line. + + This must be specified. + + SPOKE + ID of the spoke or fully qualified identifier for the spoke. + + To set the spoke attribute: + ▸ provide the argument spoke on the command line. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --details=DETAILS + Additional details behind the rejection + + --global + Indicates that the spoke is global. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/pubsub/subscriptions/create b/gcloud/pubsub/subscriptions/create index c1e429a27..85afa57de 100644 --- a/gcloud/pubsub/subscriptions/create +++ b/gcloud/pubsub/subscriptions/create @@ -12,8 +12,15 @@ SYNOPSIS [--push-auth-service-account=SERVICE_ACCOUNT_EMAIL] [--push-auth-token-audience=OPTIONAL_AUDIENCE_OVERRIDE] [--push-endpoint=PUSH_ENDPOINT] [--retain-acked-messages] - [--bigquery-table=BIGQUERY_TABLE + [[--bigquery-table=BIGQUERY_TABLE : --drop-unknown-fields --use-topic-schema --write-metadata] + | [--cloud-storage-bucket=CLOUD_STORAGE_BUCKET + : --cloud-storage-file-prefix=CLOUD_STORAGE_FILE_PREFIX + --cloud-storage-file-suffix=CLOUD_STORAGE_FILE_SUFFIX + --cloud-storage-max-bytes=CLOUD_STORAGE_MAX_BYTES + --cloud-storage-max-duration=CLOUD_STORAGE_MAX_DURATION + --cloud-storage-output-format=OUTPUT_FORMAT; + default="text" --cloud-storage-write-metadata]] [--max-delivery-attempts=MAX_DELIVERY_ATTEMPTS [--dead-letter-topic=DEAD_LETTER_TOPIC : --dead-letter-topic-project=DEAD_LETTER_TOPIC_PROJECT]] @@ -140,31 +147,76 @@ OPTIONAL FLAGS --message-retention-duration window. Acknowledged messages are not retained by default. - BigQuery Config Options. The Cloud Pub/Sub service account associated with - the enclosing subscription's parent project (i.e., - service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must have - permission to write to this BigQuery table. + At most one of these can be specified: - --bigquery-table=BIGQUERY_TABLE - A BigQuery table of the form {project}:{dataset_name}.{table_name} to - which to write messages for this subscription. + BigQuery Config Options. The Cloud Pub/Sub service account associated + with the enclosing subscription's parent project (i.e., + service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must + have permission to write to this BigQuery table. - This flag argument must be specified if any of the other arguments in - this group are specified. + --bigquery-table=BIGQUERY_TABLE + A BigQuery table of the form {project}:{dataset_name}.{table_name} + to which to write messages for this subscription. - --drop-unknown-fields - When --use-topic-schema is set, whether or not to ignore fields in - the topic schema that do not appear in the BigQuery schema. If false, - then the BigQuery schema must contain all fields that are also - present in the topic schema. + This flag argument must be specified if any of the other arguments + in this group are specified. - --use-topic-schema - Whether or not to use the schema for the subscription's topic (if it - exists) when writing messages to BigQuery. + --drop-unknown-fields + When --use-topic-schema is set, whether or not to ignore fields in + the topic schema that do not appear in the BigQuery schema. If + false, then the BigQuery schema must contain all fields that are + also present in the topic schema. - --write-metadata - Whether or not to write message metadata including message ID, - publish timestamp, ordering key, and attributes to BigQuery. + --use-topic-schema + Whether or not to use the schema for the subscription's topic (if + it exists) when writing messages to BigQuery. + + --write-metadata + Whether or not to write message metadata including message ID, + publish timestamp, ordering key, and attributes to BigQuery. + + Cloud Storage Config Options. The Cloud Pub/Sub service account + associated with the enclosing subscription's parent project (i.e., + service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must + have permission to write to this Cloud Storage bucket and to read this + bucket's metadata. + + --cloud-storage-bucket=CLOUD_STORAGE_BUCKET + A Cloud Storage bucket to which to write messages for this + subscription. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --cloud-storage-file-prefix=CLOUD_STORAGE_FILE_PREFIX + The prefix for Cloud Storage filename. + + --cloud-storage-file-suffix=CLOUD_STORAGE_FILE_SUFFIX + The suffix for Cloud Storage filename. + + --cloud-storage-max-bytes=CLOUD_STORAGE_MAX_BYTES + The maximum bytes that can be written to a Cloud Storage file + before a new file is created. The value must be between 1KB to + 10GB. If the unit is omitted, KB is assumed. + + --cloud-storage-max-duration=CLOUD_STORAGE_MAX_DURATION + The maximum duration that can elapse before a new Cloud Storage + file is created. The value must be between 1m and 10m. Valid values + are strings of the form INTEGER[UNIT], where UNIT is one of "s", + "m", "h", and "d" for seconds, minutes, hours, and days, + respectively. If the unit is omitted, seconds is assumed. + + --cloud-storage-output-format=OUTPUT_FORMAT; default="text" + The output format for data written to Cloud Storage. Values: text + (messages will be written as raw text, separated by a newline) or + avro (messages will be written as an Avro binary). OUTPUT_FORMAT + must be one of: text, avro. + + --cloud-storage-write-metadata + Whether or not to write the subscription name, message_id, + publish_time, attributes, and ordering_key as additional fields in + the output. This has an effect only for subscriptions with + --cloud-storage-output-format=avro. Dead Letter Queue Options. The Cloud Pub/Sub service account associated with the enclosing subscription's parent project (i.e., diff --git a/gcloud/pubsub/subscriptions/update b/gcloud/pubsub/subscriptions/update index da302fff4..fb70e525d 100644 --- a/gcloud/pubsub/subscriptions/update +++ b/gcloud/pubsub/subscriptions/update @@ -12,7 +12,15 @@ SYNOPSIS [--push-endpoint=PUSH_ENDPOINT] [--retain-acked-messages] [--update-labels=[KEY=VALUE,...]] [--clear-bigquery-config | [--bigquery-table=BIGQUERY_TABLE - : --drop-unknown-fields --use-topic-schema --write-metadata]] + : --drop-unknown-fields --use-topic-schema --write-metadata] + | --clear-cloud-storage-config + | [--cloud-storage-bucket=CLOUD_STORAGE_BUCKET + : --cloud-storage-file-prefix=CLOUD_STORAGE_FILE_PREFIX + --cloud-storage-file-suffix=CLOUD_STORAGE_FILE_SUFFIX + --cloud-storage-max-bytes=CLOUD_STORAGE_MAX_BYTES + --cloud-storage-max-duration=CLOUD_STORAGE_MAX_DURATION + --cloud-storage-output-format=OUTPUT_FORMAT; + default="text" --cloud-storage-write-metadata]] [--clear-dead-letter-policy | --max-delivery-attempts=MAX_DELIVERY_ATTEMPTS [--dead-letter-topic=DEAD_LETTER_TOPIC @@ -104,34 +112,89 @@ FLAGS At most one of these can be specified: - --clear-bigquery-config - If set, clear the BigQuery config from the subscription. + At most one of these can be specified: - BigQuery Config Options. The Cloud Pub/Sub service account associated - with the enclosing subscription's parent project (i.e., - service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must - have permission to write to this BigQuery table. + --clear-bigquery-config + If set, clear the BigQuery config from the subscription. - --bigquery-table=BIGQUERY_TABLE - A BigQuery table of the form {project}:{dataset_name}.{table_name} - to which to write messages for this subscription. + BigQuery Config Options. The Cloud Pub/Sub service account associated + with the enclosing subscription's parent project (i.e., + service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must + have permission to write to this BigQuery table. - This flag argument must be specified if any of the other arguments - in this group are specified. + --bigquery-table=BIGQUERY_TABLE + A BigQuery table of the form + {project}:{dataset_name}.{table_name} to which to write messages + for this subscription. - --drop-unknown-fields - When --use-topic-schema is set, whether or not to ignore fields in - the topic schema that do not appear in the BigQuery schema. If - false, then the BigQuery schema must contain all fields that are - also present in the topic schema. + This flag argument must be specified if any of the other + arguments in this group are specified. - --use-topic-schema - Whether or not to use the schema for the subscription's topic (if - it exists) when writing messages to BigQuery. + --drop-unknown-fields + When --use-topic-schema is set, whether or not to ignore fields + in the topic schema that do not appear in the BigQuery schema. If + false, then the BigQuery schema must contain all fields that are + also present in the topic schema. - --write-metadata - Whether or not to write message metadata including message ID, - publish timestamp, ordering key, and attributes to BigQuery. + --use-topic-schema + Whether or not to use the schema for the subscription's topic (if + it exists) when writing messages to BigQuery. + + --write-metadata + Whether or not to write message metadata including message ID, + publish timestamp, ordering key, and attributes to BigQuery. + + At most one of these can be specified: + + --clear-cloud-storage-config + If set, clear the Cloud Storage config from the subscription. + + Cloud Storage Config Options. The Cloud Pub/Sub service account + associated with the enclosing subscription's parent project (i.e., + service-{project_number}@gcp-sa-pubsub.iam.gserviceaccount.com) must + have permission to write to this Cloud Storage bucket and to read this + bucket's metadata. + + Note that an update to the Cloud Storage config will replace it with a + new config containing only the flags that are passed in the update + CLI. + + --cloud-storage-bucket=CLOUD_STORAGE_BUCKET + A Cloud Storage bucket to which to write messages for this + subscription. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --cloud-storage-file-prefix=CLOUD_STORAGE_FILE_PREFIX + The prefix for Cloud Storage filename. + + --cloud-storage-file-suffix=CLOUD_STORAGE_FILE_SUFFIX + The suffix for Cloud Storage filename. + + --cloud-storage-max-bytes=CLOUD_STORAGE_MAX_BYTES + The maximum bytes that can be written to a Cloud Storage file + before a new file is created. The value must be between 1KB to + 10GB. If the unit is omitted, KB is assumed. + + --cloud-storage-max-duration=CLOUD_STORAGE_MAX_DURATION + The maximum duration that can elapse before a new Cloud Storage + file is created. The value must be between 1m and 10m. Valid + values are strings of the form INTEGER[UNIT], where UNIT is one + of "s", "m", "h", and "d" for seconds, minutes, hours, and days, + respectively. If the unit is omitted, seconds is assumed. + + --cloud-storage-output-format=OUTPUT_FORMAT; default="text" + The output format for data written to Cloud Storage. Values: text + (messages will be written as raw text, separated by a newline) or + avro (messages will be written as an Avro binary). OUTPUT_FORMAT + must be one of: text, avro. + + --cloud-storage-write-metadata + Whether or not to write the subscription name, message_id, + publish_time, attributes, and ordering_key as additional fields + in the output. This has an effect only for subscriptions with + --cloud-storage-output-format=avro. At most one of these can be specified: diff --git a/gcloud/recaptcha/keys/migrate b/gcloud/recaptcha/keys/migrate index 96c2afed1..ac32b2360 100644 --- a/gcloud/recaptcha/keys/migrate +++ b/gcloud/recaptcha/keys/migrate @@ -2,7 +2,8 @@ NAME gcloud recaptcha keys migrate - migrate a key to reCAPTCHA Enterprise SYNOPSIS - gcloud recaptcha keys migrate KEY [GCLOUD_WIDE_FLAG ...] + gcloud recaptcha keys migrate KEY [--skip-billing-check] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Migrate a key from reCAPTCHA to reCAPTCHA Enterprise. @@ -31,6 +32,11 @@ POSITIONAL ARGUMENTS To set the key attribute: ▸ provide the argument key on the command line. +FLAGS + --skip-billing-check + If true, skips the billing check. If your usage of reCAPTCHA is under + the free quota, you can safely skip the billing check. + 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/recommender/insights/list b/gcloud/recommender/insights/list index 9a09905c8..fc4cc9efa 100644 --- a/gcloud/recommender/insights/list +++ b/gcloud/recommender/insights/list @@ -10,7 +10,7 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command will list all insights for a given cloud entity, location and + This command lists all insights for a given cloud entity, location and insight type. Supported insight-types can be found here: https://cloud.google.com/recommender/docs/insights/insight-types. Currently the following cloud_entity_types are supported: project, billing_account, diff --git a/gcloud/recommender/recommendations/list b/gcloud/recommender/recommendations/list index 74127426e..e7f6fa56b 100644 --- a/gcloud/recommender/recommendations/list +++ b/gcloud/recommender/recommendations/list @@ -11,7 +11,7 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - This command will list all recommendations for a given cloud_entity_id, + This command lists all recommendations for a given cloud_entity_id, location and recommender. Supported recommenders can be found here: https://cloud.google.com/recommender/docs/recommenders. Currently the following cloud_entity_types are supported: project, billing_account, diff --git a/gcloud/redis/instances/update b/gcloud/redis/instances/update index 32504387b..fa51c32a8 100644 --- a/gcloud/redis/instances/update +++ b/gcloud/redis/instances/update @@ -174,6 +174,9 @@ FLAGS Redis version 5.0 and newer: stream-node-max-bytes, stream-node-max-entries. + Redis version 7.0 and newer: maxmemory-clients, lazyfree-lazy-eviction, + lazyfree-lazy-expire, lazyfree-lazy-user-del, lazyfree-lazy-user-flush. + At most one of these can be specified: --clear-labels diff --git a/gcloud/run/deploy b/gcloud/run/deploy index f197a93e4..e59990bfa 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -149,8 +149,8 @@ FLAGS Set a memory limit. Ex: 1024Mi, 4Gi. --min-instances=MIN_INSTANCES - The minimum number of container instances of the Service to run or - 'default' to remove any minimum. + The minimum number of container instances for this Revision of the + Service to run or 'default' to remove any minimum. --platform=PLATFORM; default="managed" Target platform for running commands. Alternatively, set the property diff --git a/gcloud/run/services/update b/gcloud/run/services/update index e07528258..94181e94c 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -141,8 +141,8 @@ FLAGS Set a memory limit. Ex: 1024Mi, 4Gi. --min-instances=MIN_INSTANCES - The minimum number of container instances of the Service to run or - 'default' to remove any minimum. + The minimum number of container instances for this Revision of the + Service to run or 'default' to remove any minimum. --platform=PLATFORM; default="managed" Target platform for running commands. Alternatively, set the property diff --git a/gcloud/scc/findings/create b/gcloud/scc/findings/create index 2dc17fdb5..f76fe3524 100644 --- a/gcloud/scc/findings/create +++ b/gcloud/scc/findings/create @@ -13,30 +13,30 @@ DESCRIPTION Create a Cloud Security Command Center finding. EXAMPLES - Create an ACTIVE my-finding with category: XSS_SCRIPTING attached to + Create an ACTIVE myFinding with category: XSS_SCRIPTING attached to example-project under organization 123456 and source 5678: - $ gcloud scc findings create my-finding --organization=123456 \ + $ gcloud scc findings create `myFinding` --organization=123456 \ --source=5678 --state=ACTIVE --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' - Create an ACTIVE my-finding attached to example-project under project + Create an ACTIVE myFinding attached to example-project under project example-project and source 5678: $ gcloud scc findings create \ - projects/example-project/sources/5678/findings/my-finding \ + projects/example-project/sources/5678/findings/myFinding \ --state=ACTIVE --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ example-project' - Create an ACTIVE my-finding attached to example-project under folder 456 - and source 5678: + Create an ACTIVE myFinding attached to example-project under folder 456 and + source 5678: $ gcloud scc findings create \ - folders/456/sources/5678/findings/my-finding --state=ACTIVE \ + folders/456/sources/5678/findings/myFinding --state=ACTIVE \ --category='XSS_SCRIPTING' \ --event-time=2023-01-11T07:00:06.861Z \ --resource-name='//cloudresourcemanager.googleapis.com/projects/\ diff --git a/gcloud/scc/findings/list-marks b/gcloud/scc/findings/list-marks index 91aaaa75c..c6f0233c8 100644 --- a/gcloud/scc/findings/list-marks +++ b/gcloud/scc/findings/list-marks @@ -12,22 +12,22 @@ DESCRIPTION List a finding's security marks. EXAMPLES - List all security marks for my-finding under organization 123456 and source + List all security marks for myFinding under organization 123456 and source 5678: - $ gcloud scc findings list-marks my-finding --organization=123456 \ + $ gcloud scc findings list-marks `myFinding` --organization=123456 \ --source=5678 - List all security marks for my-finding under project example-project and + List all security marks for myFinding under project example-project and source 5678: $ gcloud scc findings list-marks \ - projects/example-project/sources/5678/findings/my-finding + projects/example-project/sources/5678/findings/myFinding - List all security marks for my-finding under folder 456 and source 5678: + List all security marks for myFinding under folder 456 and source 5678: $ gcloud scc findings list-marks \ - folders/456/sources/5678/findings/my-finding + folders/456/sources/5678/findings/myFinding POSITIONAL ARGUMENTS Finding resource - The finding to be used for the SCC (Security Command diff --git a/gcloud/scc/findings/update b/gcloud/scc/findings/update index ee9a30df7..442e09fe7 100644 --- a/gcloud/scc/findings/update +++ b/gcloud/scc/findings/update @@ -12,32 +12,32 @@ DESCRIPTION Update a Cloud Security Command Center finding. EXAMPLES - Update my-finding's state from ACTIVE to INACTIVE: + Update myFinding's state from ACTIVE to INACTIVE: - $ gcloud scc findings update my-finding --organization=123456 \ + $ gcloud scc findings update `myFinding` --organization=123456 \ --source=5678 --state=INACTIVE - Update my-finding's state from ACTIVE to INACTIVE using project name for + Update myFinding's state from ACTIVE to INACTIVE using project name for example-project: $ gcloud scc findings update \ - projects/example-project/sources/5678/findings/my-finding \ + projects/example-project/sources/5678/findings/myFinding \ --state=INACTIVE - Update my-finding's state from ACTIVE to INACTIVE using folder name 456: + Update myFinding's state from ACTIVE to INACTIVE using folder name 456: $ gcloud scc findings update \ - folders/456/sources/5678/findings/my-finding --state=INACTIVE + folders/456/sources/5678/findings/myFinding --state=INACTIVE - Override all source properties on my-finding: + Override all source properties on myFinding: - $ gcloud scc findings update my-finding --organization=123456 \ + $ gcloud scc findings update `myFinding` --organization=123456 \ --source=5678 \ --source-properties="propKey1=propVal1,propKey2=propVal2" - Selectively update a specific source property on my-finding: + Selectively update a specific source property on myFinding: - $ gcloud scc findings update my-finding --organization=123456 \ + $ gcloud scc findings update `myFinding` --organization=123456 \ --source=5678 \ --source-properties="propKey1=propVal1,propKey2=propVal2" \ --update-mask="source_properties.propKey1" diff --git a/gcloud/scc/findings/update-marks b/gcloud/scc/findings/update-marks index 6e74c3433..64f8b6cdd 100644 --- a/gcloud/scc/findings/update-marks +++ b/gcloud/scc/findings/update-marks @@ -12,36 +12,36 @@ DESCRIPTION Update Cloud Security Command Center finding's security marks. EXAMPLES - Selectively update security mark (Key1) with value (v1) on my-finding. Note - that other security marks on my-finding are untouched: + Selectively update security mark (Key1) with value (v1) on myFinding. Note + that other security marks on myFinding are untouched: - $ gcloud scc findings update-marks my-finding \ + $ gcloud scc findings update-marks `myFinding` \ --organization=123456 --source=5678 --security-marks="key1=v1" \ --update-mask="marks.markKey1" - Update all security marks on my-finding, under project example-project and + Update all security marks on myFinding, under project example-project and source 5678: $ gcloud scc findings update-marks \ - projects/example-project/sources/5678/findings/my-finding \ + projects/example-project/sources/5678/findings/myFinding \ --security-marks="key1=v1,key2=v2" - Update all security marks on my-finding, under folder 456 and source 5678: + Update all security marks on myFinding, under folder 456 and source 5678: $ gcloud scc findings update-marks \ - folders/456/sources/5678/findings/my-finding \ + folders/456/sources/5678/findings/myFinding \ --security-marks="key1=v1,key2=v2" - Update all security marks on my-finding, under organization 123456 and + Update all security marks on myFinding, under organization 123456 and source 5678: - $ gcloud scc findings update-marks my-finding \ + $ gcloud scc findings update-marks `myFinding` \ --organization=123456 --source=5678 \ --security-marks="key1=v1,key2=v2" - Delete all security marks on my-finding: + Delete all security marks on myFinding: - $ gcloud scc findings update-marks my-finding \ + $ gcloud scc findings update-marks `myFinding` \ --organization=123456 --source=5678 --security-marks="" POSITIONAL ARGUMENTS diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index 700d92219..4dc038550 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -19,8 +19,9 @@ SYNOPSIS [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] - [--enable-bin-log] [--enable-google-private-path] - [--enable-password-policy] [--enable-point-in-time-recovery] + [--edition=EDITION] [--enable-bin-log] [--enable-data-cache] + [--enable-google-private-path] [--enable-password-policy] + [--enable-point-in-time-recovery] [--failover-replica-name=FAILOVER_REPLICA_NAME] [--[no-]insights-config-query-insights-enabled] [--insights-config-query-plans-per-minute=INSIGHTS_CONFIG_QUERY_PLANS_PER_MINUTE] @@ -206,11 +207,19 @@ FLAGS --deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME Time when the deny maintenance period starts or ends, that is 05:00:00. + --edition=EDITION + Specifies the edition of Cloud SQL instance. EDITION must be one of: + enterprise, enterprise-plus. + --enable-bin-log Allows for data recovery from a specific point in time, down to a fraction of a second. Must have automatic backups enabled to use. Make sure storage can support at least 7 days of logs. + --enable-data-cache + Enable use of data cache for accelerated read performance. This flag is + only available for Enterprise_Plus edition instances. + --enable-google-private-path Enable a private path for Google Cloud services. This flag specifies whether the instance is accessible to internal Google Cloud services @@ -341,16 +350,20 @@ FLAGS Specified if users connecting over IP must use SSL. --retained-backups-count=RETAINED_BACKUPS_COUNT - How many backups to keep. The valid range is between 1 and 365. The - default value is 7 if not specified. Applicable only if --no-backups is - not specified. + How many backups to keep. The valid range is between 1 and 365. Default + value is 7 for Enterprise edition instances. For Enterprise_Plus + Postgres and MySQL instances, default values are 15 and 8 respectively. + Applicable only if --no-backups is not specified. --retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS How many days of transaction logs to keep. The valid range is between 1 - and 35. The default value is 7. The 35 days log retention feature is - only enabled for specific customer. Only use this option when - point-in-time recovery is enabled. Storage size for transaction logs - increases when the number of days for log retention increases. + and 35. Only use this option when point-in-time recovery is enabled. If + logs are stored on disk, storage size for transaction logs could + increase when the number of days for log retention increases. For + Enterprise, default and max retention values are 7 and 7 respectively. + For MySQL Enterprise_Plus, default and max retention values are 7 and + 7. For Postgres Enterprise_Plus, default and max retention values are + 14 and 35. --root-password=ROOT_PASSWORD Root Cloud SQL user's password. diff --git a/gcloud/sql/instances/list b/gcloud/sql/instances/list index ed34f7884..06f444fe0 100644 --- a/gcloud/sql/instances/list +++ b/gcloud/sql/instances/list @@ -2,14 +2,18 @@ NAME gcloud sql instances list - lists Cloud SQL instances in a given project SYNOPSIS - gcloud sql instances list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud sql instances list [--show-edition] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Lists Cloud SQL instances in a given project in the alphabetical order of the instance name. +FLAGS + --show-edition + Show the edition field. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index d4b963ad4..3009a4729 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -13,7 +13,8 @@ SYNOPSIS [--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE] [--deny-maintenance-period-start-date=DENY_MAINTENANCE_PERIOD_START_DATE] [--deny-maintenance-period-time=DENY_MAINTENANCE_PERIOD_TIME] [--diff] - [--[no-]enable-bin-log] [--[no-]enable-database-replication] + [--edition=EDITION] [--[no-]enable-bin-log] [--enable-data-cache] + [--[no-]enable-database-replication] [--[no-]enable-google-private-path] [--enable-password-policy] [--enable-point-in-time-recovery] [--follow-gae-app=FOLLOW_GAE_APP] [--[no-]insights-config-query-insights-enabled] @@ -155,12 +156,20 @@ FLAGS --diff Show what changed as a result of the update. + --edition=EDITION + Specifies the edition of Cloud SQL instance. EDITION must be one of: + enterprise, enterprise-plus. + --[no-]enable-bin-log Allows for data recovery from a specific point in time, down to a fraction of a second. Must have automatic backups enabled to use. Make sure storage can support at least 7 days of logs. Use --enable-bin-log to enable and --no-enable-bin-log to disable. + --enable-data-cache + Enable use of data cache for accelerated read performance. This flag is + only available for Enterprise_Plus edition instances. + --[no-]enable-database-replication Enable database replication. Applicable only for read replica instance(s). WARNING: Instance will be restarted. Use @@ -404,16 +413,20 @@ FLAGS UTC timezone. --retained-backups-count=RETAINED_BACKUPS_COUNT - How many backups to keep. The valid range is between 1 and 365. The - default value is 7 if not specified. Applicable only if --no-backups - is not specified. + How many backups to keep. The valid range is between 1 and 365. + Default value is 7 for Enterprise edition instances. For + Enterprise_Plus Postgres and MySQL instances, default values are 15 + and 8 respectively. Applicable only if --no-backups is not specified. --retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS How many days of transaction logs to keep. The valid range is between - 1 and 35. The default value is 7. The 35 days log retention feature - is only enabled for specific customer. Only use this option when - point-in-time recovery is enabled. Storage size for transaction logs - increases when the number of days for log retention increases. + 1 and 35. Only use this option when point-in-time recovery is + enabled. If logs are stored on disk, storage size for transaction + logs could increase when the number of days for log retention + increases. For Enterprise, default and max retention values are 7 and + 7 respectively. For MySQL Enterprise_Plus, default and max retention + values are 7 and 7. For Postgres Enterprise_Plus, default and max + retention values are 14 and 35. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/sql/operations/cancel b/gcloud/sql/operations/cancel new file mode 100644 index 000000000..45c5cadd5 --- /dev/null +++ b/gcloud/sql/operations/cancel @@ -0,0 +1,34 @@ +NAME + gcloud sql operations cancel - cancels a Cloud SQL instance operation + +SYNOPSIS + gcloud sql operations cancel OPERATION [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Cancels a Cloud SQL instance operation. + +EXAMPLES + To cancel an operation with the id "prod-operation-id", like + "acb40108-a483-4a8b-8a5c-e27100000032", run: + + $ gcloud sql operations cancel prod-operation-id + +POSITIONAL ARGUMENTS + OPERATION + Name that uniquely identifies the operation. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha sql operations cancel + + $ gcloud beta sql operations cancel + diff --git a/gcloud/sql/operations/help b/gcloud/sql/operations/help index fb666e3a9..7463f1216 100644 --- a/gcloud/sql/operations/help +++ b/gcloud/sql/operations/help @@ -18,6 +18,9 @@ GCLOUD WIDE FLAGS COMMANDS COMMAND is one of the following: + cancel + Cancels a Cloud SQL instance operation. + describe Retrieves information about a Cloud SQL instance operation. diff --git a/gcloud/sql/tiers/list b/gcloud/sql/tiers/list index c4ee664e1..46187017c 100644 --- a/gcloud/sql/tiers/list +++ b/gcloud/sql/tiers/list @@ -3,13 +3,17 @@ NAME SQL SYNOPSIS - gcloud sql tiers list [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + gcloud sql tiers list [--show-edition] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION Lists all available service tiers for Google Cloud SQL. +FLAGS + --show-edition + Show the edition field. + LIST COMMAND FLAGS --filter=EXPRESSION Apply a Boolean filter EXPRESSION to each resource item to be listed. diff --git a/gcloud/storage/cp b/gcloud/storage/cp index 1cea4e95a..c28a552ea 100644 --- a/gcloud/storage/cp +++ b/gcloud/storage/cp @@ -220,7 +220,7 @@ FLAGS Content-Encoding metadata is set to gzip and the Cache-Control metadata set to no-transform. The data remains compressed on Cloud Storage servers and will not be decompressed on download by gcloud - stroage because of the no-transform field. + storage because of the no-transform field. Since the local gzip option compresses data prior to upload, it is not subject to the same compression buffer bottleneck of the diff --git a/gcloud/storage/mv b/gcloud/storage/mv index 98ba0e809..9fbf30934 100644 --- a/gcloud/storage/mv +++ b/gcloud/storage/mv @@ -225,7 +225,7 @@ FLAGS Content-Encoding metadata is set to gzip and the Cache-Control metadata set to no-transform. The data remains compressed on Cloud Storage servers and will not be decompressed on download by gcloud - stroage because of the no-transform field. + storage because of the no-transform field. Since the local gzip option compresses data prior to upload, it is not subject to the same compression buffer bottleneck of the diff --git a/gcloud/workstations/clusters/create b/gcloud/workstations/clusters/create index 3b08a8926..374964017 100644 --- a/gcloud/workstations/clusters/create +++ b/gcloud/workstations/clusters/create @@ -68,12 +68,10 @@ FLAGS Compute Engine resources. --network=NETWORK - The network that instances created under the cluster will be associated - with. + Fully specified network path for instances created in this cluster. --subnetwork=SUBNETWORK - The subnetwork that instances created under the cluster will be - associated with. + Fully specified subnetwork path for instances created in this cluster. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/workstations/configs/create b/gcloud/workstations/configs/create index a3fbcec67..1f9f7f924 100644 --- a/gcloud/workstations/configs/create +++ b/gcloud/workstations/configs/create @@ -151,10 +151,7 @@ FLAGS --machine-type=MACHINE_TYPE; default="e2-standard-4" Machine type determines the specifications of the Compute Engine machines that the workstations created under this configuration will - run on. MACHINE_TYPE must be one of: e2-standard-2, e2-standard-4, - e2-standard-8, e2-standard-16, e2-standard-32, n2-standard-8, - n1-standard-4, t2d-standard-6, n2d-standard-2, n2d-standard-4, - n2d-standard-8, n2d-standard-16, n2d-standard-32. + run on. --network-tags=[NETWORK_TAGS,...] Network tags to add to the Google Compute Engine machines backing the diff --git a/gcloud/workstations/configs/update b/gcloud/workstations/configs/update index 2e54460bf..051e1df46 100644 --- a/gcloud/workstations/configs/update +++ b/gcloud/workstations/configs/update @@ -139,10 +139,7 @@ FLAGS --machine-type=MACHINE_TYPE Machine type determines the specifications of the Compute Engine machines that the workstations created under this configuration will - run on. MACHINE_TYPE must be one of: e2-standard-2, e2-standard-4, - e2-standard-8, e2-standard-16, e2-standard-32, n2-standard-8, - n1-standard-4, t2d-standard-6, n2d-standard-2, n2d-standard-4, - n2d-standard-8, n2d-standard-16, n2d-standard-32. + run on. --network-tags=[NETWORK_TAGS,...] Network tags to add to the Google Compute Engine machines backing the