1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-21 06:27:15 +00:00

gcloud: Thu Jan 19 00:56:33 UTC 2023

This commit is contained in:
Automated 2023-01-19 00:56:33 +00:00
parent 348d9760ee
commit 1248f773ec
1462 changed files with 51835 additions and 5402 deletions

View file

@ -24,8 +24,9 @@ POSITIONAL ARGUMENTS
FLAGS
--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 is
used. If builds/region is unset,region is set to "global".
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.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

View file

@ -20,8 +20,9 @@ POSITIONAL ARGUMENTS
FLAGS
--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 is
used. If builds/region is unset,region is set to "global".
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.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

View file

@ -53,8 +53,9 @@ OPTIONAL FLAGS
--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 is
used. If builds/region is unset,region is set to "global".
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.
--ssl-ca-file=SSL_CA_FILE
Path to a local file that contains SSL certificate to use for requests

View file

@ -16,8 +16,9 @@ POSITIONAL ARGUMENTS
FLAGS
--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 is
used. If builds/region is unset,region is set to "global".
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.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

View file

@ -16,8 +16,9 @@ POSITIONAL ARGUMENTS
FLAGS
--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 is
used. If builds/region is unset,region is set to "global".
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.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

View file

@ -14,8 +14,9 @@ DESCRIPTION
FLAGS
--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 is
used. If builds/region is unset,region is set to "global".
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.
LIST COMMAND FLAGS
--filter=EXPRESSION

View file

@ -37,8 +37,9 @@ FLAGS
--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 is
used. If builds/region is unset,region is set to "global".
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.
--ssl-ca-file=SSL_CA_FILE
Path to a local file that contains SSL certificate to use for requests

View file

@ -25,18 +25,17 @@ FLAGS
--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 is
used. If builds/region is unset,region is set to "global".
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.
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.
With the exception of regex matching, this flag interacts with other
flags that are applied in this order: --flatten, --sort-by, --filter,
--limit. Any regex operations specified by --filter are applied
client-side, after --limit.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT; default=50
Maximum number of resources to list. The default is 50. This flag

View file

@ -26,8 +26,9 @@ POSITIONAL ARGUMENTS
FLAGS
--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 is
used. If builds/region is unset,region is set to "global".
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.
--stream
If a build is ongoing, stream the logs to stdout until the build

View file

@ -94,8 +94,9 @@ FLAGS
--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 is
used. If builds/region is unset,region is set to "global".
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.
--substitutions=[KEY=VALUE,...]
Parameters to be substituted in the build specification.
@ -168,9 +169,6 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
NOTES
You can also run a build locally using the separate component: gcloud
components install cloud-build-local.
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

View file

@ -63,7 +63,7 @@ FLAGS
--resource-format=RESOURCE_FORMAT
Format of the configuration to export. Available configuration formats
are Kubernetes Resource Model (krm) or Terraform HCL (terraform).
are Kubernetes Resource Model YAML (krm) or Terraform HCL (terraform).
Command defaults to "krm". RESOURCE_FORMAT must be one of: krm,
terraform.

View file

@ -7,10 +7,11 @@ SYNOPSIS
(--trigger-config=PATH
| [--bitbucket-server-config-resource=BITBUCKET_SERVER_CONFIG_RESOURCE --project-key=PROJECT_KEY --repo-slug=REPO_SLUG (--branch-pattern=REGEX | --tag-pattern=REGEX | [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL; default=CommentControlValueValuesEnum(COMMENTS_ENABLED,
1)]) (--build-config=PATH | --inline-config=PATH
| --dockerfile=DOCKERFILE --dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE)
| [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE])
: --description=DESCRIPTION --ignored-files=[GLOB,...]
--included-files=[GLOB,...] --name=NAME --require-approval
--included-files=[GLOB,...] --name=NAME --region=REGION
--require-approval
--service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]])
[GCLOUD_WIDE_FLAG ...]
@ -84,6 +85,13 @@ REQUIRED FLAGS
--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.
--require-approval
Require manual approval for triggered builds.
@ -163,20 +171,16 @@ REQUIRED FLAGS
Exactly one of these must be specified:
Build file configuration flags
--build-config=PATH
Path to a YAML or JSON file containing the build configuration in
the repository.
--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
For more details, see:
https://cloud.google.com/cloud-build/docs/build-config
Build configuration file
--inline-config=PATH
Local path to a YAML or JSON file containing a build
configuration.
--inline-config=PATH
Local path to a YAML or JSON file containing a build
configuration.
Dockerfile build configuration flags
@ -188,6 +192,9 @@ REQUIRED FLAGS
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-dir=DOCKERFILE_DIR; default="/"
Location of the directory containing the Dockerfile in the
repository.
@ -216,7 +223,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 triggers create bitbucketserver
$ gcloud beta builds triggers create bitbucketserver

View file

@ -6,10 +6,11 @@ SYNOPSIS
gcloud alpha builds triggers create cloud-source-repositories
(--trigger-config=PATH | [--repo=REPO (--branch-pattern=REGEX
| --tag-pattern=REGEX) (--build-config=PATH | --inline-config=PATH
| --dockerfile=DOCKERFILE --dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE)
| [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE])
: --description=DESCRIPTION --ignored-files=[GLOB,...]
--included-files=[GLOB,...] --name=NAME --require-approval
--included-files=[GLOB,...] --name=NAME --region=REGION
--require-approval
--service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]])
[GCLOUD_WIDE_FLAG ...]
@ -63,6 +64,13 @@ REQUIRED FLAGS
--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.
--require-approval
Require manual approval for triggered builds.
@ -120,20 +128,16 @@ REQUIRED FLAGS
Exactly one of these must be specified:
Build file configuration flags
--build-config=PATH
Path to a YAML or JSON file containing the build configuration in
the repository.
--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
For more details, see:
https://cloud.google.com/cloud-build/docs/build-config
Build configuration file
--inline-config=PATH
Local path to a YAML or JSON file containing a build
configuration.
--inline-config=PATH
Local path to a YAML or JSON file containing a build
configuration.
Dockerfile build configuration flags
@ -145,6 +149,9 @@ REQUIRED FLAGS
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-dir=DOCKERFILE_DIR; default="/"
Location of the directory containing the Dockerfile in the
repository.
@ -173,7 +180,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 triggers create cloud-source-repositories
$ gcloud beta builds triggers create cloud-source-repositories

View file

@ -4,15 +4,16 @@ NAME
SYNOPSIS
gcloud alpha builds triggers create github
(--trigger-config=PATH | [--repo-name=REPO_NAME
--repo-owner=REPO_OWNER (--branch-pattern=REGEX | --tag-pattern=REGEX
(--trigger-config=PATH | [(--branch-pattern=REGEX | --tag-pattern=REGEX
| [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL;
default="COMMENTS_ENABLED"]) (--build-config=PATH
| --inline-config=PATH | --dockerfile=DOCKERFILE
--dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE)
: --description=DESCRIPTION --ignored-files=[GLOB,...]
--include-logs-with-status --included-files=[GLOB,...] --name=NAME
| --inline-config=PATH | [--dockerfile=DOCKERFILE
: --dockerfile-dir=DOCKERFILE_DIR; default="/"
--dockerfile-image=DOCKERFILE_IMAGE]) (--repository=REPOSITORY
| [--repo-name=REPO_NAME --repo-owner=REPO_OWNER
: --enterprise-config=ENTERPRISE_CONFIG]) : --description=DESCRIPTION
--ignored-files=[GLOB,...] --include-logs-with-status
--included-files=[GLOB,...] --name=NAME --region=REGION
--require-approval
--service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]])
[GCLOUD_WIDE_FLAG ...]
@ -21,7 +22,7 @@ DESCRIPTION
(ALPHA) Create a build trigger for a GitHub repository.
EXAMPLES
To create a push trigger for all branches:
To create a push trigger with a 1st-gen repository for all branches:
$ gcloud alpha builds triggers create github --name="my-trigger" \
--service-account="projects/my-project/serviceAccounts/my-byosa@\
@ -30,7 +31,7 @@ EXAMPLES
--repo-name="cloud-builders" --branch-pattern=".*" \
--build-config="cloudbuild.yaml"
To create a pull request trigger for master:
To create a pull request trigger with a 1st-gen repository for master:
$ gcloud alpha builds triggers create github --name="my-trigger" \
--service-account="projects/my-project/serviceAccounts/my-byosa@\
@ -39,6 +40,14 @@ EXAMPLES
--repo-name="cloud-builders" --pull-request-pattern="^master$" \
--build-config="cloudbuild.yaml"
To create a pull request trigger with a 2nd gen repository for master:
$ gcloud alpha builds triggers create github --name="my-trigger" \
--repository=projects/my-project/locations/us-central1/\
connections/my-conn/repositories/my-repo \
--pull-request-pattern="^master$" \
--build-config="cloudbuild.yaml"
REQUIRED FLAGS
Exactly one of these must be specified:
@ -49,18 +58,6 @@ REQUIRED FLAGS
Flag based trigger configuration
--repo-name=REPO_NAME
Name of the GitHub Repository.
This flag argument must be specified if any of the other arguments
in this group are specified.
--repo-owner=REPO_OWNER
Owner of the GitHub Repository.
This flag argument must be specified if any of the other arguments
in this group are specified.
--description=DESCRIPTION
Build trigger description.
@ -79,6 +76,13 @@ REQUIRED FLAGS
--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.
--require-approval
Require manual approval for triggered builds.
@ -170,20 +174,16 @@ REQUIRED FLAGS
Exactly one of these must be specified:
Build file configuration flags
--build-config=PATH
Path to a YAML or JSON file containing the build configuration in
the repository.
--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
For more details, see:
https://cloud.google.com/cloud-build/docs/build-config
Build configuration file
--inline-config=PATH
Local path to a YAML or JSON file containing a build
configuration.
--inline-config=PATH
Local path to a YAML or JSON file containing a build
configuration.
Dockerfile build configuration flags
@ -195,6 +195,9 @@ REQUIRED FLAGS
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-dir=DOCKERFILE_DIR; default="/"
Location of the directory containing the Dockerfile in the
repository.
@ -211,6 +214,33 @@ REQUIRED FLAGS
Use a build configuration (cloudbuild.yaml) file for building
multiple images in a single trigger.
Exactly one of these must be specified:
--repository=REPOSITORY
Repository resource (2nd gen) to use, in the format
"projects/*/locations/*/connections/*/repositories/".
1st-gen repository settings.
--repo-name=REPO_NAME
Name of the GitHub Repository (1st gen).
This flag argument must be specified if any of the other
arguments in this group are specified.
--repo-owner=REPO_OWNER
Owner of the GitHub Repository (1st gen).
This flag argument must be specified if any of the other
arguments in this group are specified.
--enterprise-config=ENTERPRISE_CONFIG
Resource name of the GitHub Enterprise config that should be
applied to this installation.
For example:
"projects/{$project_id}/locations/{$location_id}/githubEnterpriseConfigs/{$config_id}
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
@ -223,7 +253,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 triggers create github
$ gcloud beta builds triggers create github

View file

@ -6,15 +6,16 @@ SYNOPSIS
gcloud alpha builds triggers create gitlab-enterprise
(--trigger-config=PATH
| [--gitlab-config-resource=GITLAB_CONFIG_RESOURCE
--project-namespace=PROJECT_NAMESPACE
--region=REGION (--branch-pattern=REGEX | --tag-pattern=REGEX
| [--pull-request-pattern=REGEX : --comment-control=COMMENT_CONTROL;
--project-namespace=PROJECT_NAMESPACE (--branch-pattern=REGEX
| --tag-pattern=REGEX | [--pull-request-pattern=REGEX
: --comment-control=COMMENT_CONTROL;
default=CommentControlValueValuesEnum(COMMENTS_ENABLED,
1)]) (--build-config=PATH | --inline-config=PATH
| --dockerfile=DOCKERFILE --dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE)
| [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE])
: --description=DESCRIPTION --ignored-files=[GLOB,...]
--included-files=[GLOB,...] --name=NAME --require-approval
--included-files=[GLOB,...] --name=NAME --region=REGION
--require-approval
--service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]])
[GCLOUD_WIDE_FLAG ...]
@ -65,14 +66,6 @@ REQUIRED FLAGS
This flag argument must be specified if any of the other arguments
in this group are specified.
--region=REGION
The region of the Cloud Build Service to use. Must be set to a
supported region name (e.g. us-central1). If unset, builds/region
is used. If builds/region is unset,region is set to "global".
This flag argument must be specified if any of the other arguments
in this group are specified.
--description=DESCRIPTION
Build trigger description.
@ -87,6 +80,13 @@ REQUIRED FLAGS
--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.
--require-approval
Require manual approval for triggered builds.
@ -187,6 +187,9 @@ REQUIRED FLAGS
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-dir=DOCKERFILE_DIR; default="/"
Location of the directory containing the Dockerfile in the
repository.
@ -215,7 +218,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 triggers create gitlab-enterprise
$ gcloud beta builds triggers create gitlab-enterprise

View file

@ -41,7 +41,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 triggers create
$ gcloud beta builds triggers create

View file

@ -5,11 +5,11 @@ NAME
SYNOPSIS
gcloud alpha builds triggers create manual
(--trigger-config=PATH | [(--build-config=PATH | --inline-config=PATH
| --dockerfile=DOCKERFILE --dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE)
: --description=DESCRIPTION --name=NAME --require-approval
--service-account=SERVICE_ACCOUNT
--subscription-filter=SUBSCRIPTION_FILTER
| [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE])
: --description=DESCRIPTION
--github-enterprise-config=GITHUB_ENTERPRISE_CONFIG --name=NAME
--region=REGION --require-approval --service-account=SERVICE_ACCOUNT
--substitutions=[KEY=VALUE,...]
--repo=REPO --repo-type=REPO_TYPE (--branch=BRANCH | --tag=TAG)])
[GCLOUD_WIDE_FLAG ...]
@ -39,9 +39,22 @@ REQUIRED FLAGS
--description=DESCRIPTION
Build trigger description.
--github-enterprise-config=GITHUB_ENTERPRISE_CONFIG
The resource name of the GitHub Enterprise config that should be
applied to this source. Format:
projects/{project}/locations/{location}/githubEnterpriseConfigs/{id}
or projects/{project}/githubEnterpriseConfigs/{id}
--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.
--require-approval
Require manual approval for triggered builds.
@ -53,11 +66,6 @@ REQUIRED FLAGS
used instead. Format:
projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}.
--subscription-filter=SUBSCRIPTION_FILTER
CEL filter expression for the trigger. See
https://cloud.google.com/build/docs/filter-build-events-using-cel
for more details.
--substitutions=[KEY=VALUE,...]
Parameters to be substituted in the build specification.
@ -80,20 +88,16 @@ REQUIRED FLAGS
Exactly one of these must be specified:
Build file configuration flags
--build-config=PATH
Path to a YAML or JSON file containing the build configuration in
the repository.
--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
For more details, see:
https://cloud.google.com/cloud-build/docs/build-config
Build configuration file
--inline-config=PATH
Local path to a YAML or JSON file containing a build
configuration.
--inline-config=PATH
Local path to a YAML or JSON file containing a build
configuration.
Dockerfile build configuration flags
@ -105,6 +109,9 @@ REQUIRED FLAGS
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-dir=DOCKERFILE_DIR; default="/"
Location of the directory containing the Dockerfile in the
repository.
@ -157,7 +164,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 triggers create manual
$ gcloud beta builds triggers create manual

View file

@ -5,11 +5,12 @@ NAME
SYNOPSIS
gcloud alpha builds triggers create pubsub
(--trigger-config=PATH | [--topic=TOPIC (--build-config=PATH
| --inline-config=PATH | --dockerfile=DOCKERFILE
--dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE)
: --description=DESCRIPTION --name=NAME --require-approval
--service-account=SERVICE_ACCOUNT
| --inline-config=PATH | [--dockerfile=DOCKERFILE
: --dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE])
: --description=DESCRIPTION
--github-enterprise-config=GITHUB_ENTERPRISE_CONFIG --name=NAME
--region=REGION --require-approval --service-account=SERVICE_ACCOUNT
--subscription-filter=SUBSCRIPTION_FILTER
--substitutions=[KEY=VALUE,...]
--repo=REPO --repo-type=REPO_TYPE (--branch=BRANCH | --tag=TAG)])
@ -49,9 +50,22 @@ REQUIRED FLAGS
--description=DESCRIPTION
Build trigger description.
--github-enterprise-config=GITHUB_ENTERPRISE_CONFIG
The resource name of the GitHub Enterprise config that should be
applied to this source. Format:
projects/{project}/locations/{location}/githubEnterpriseConfigs/{id}
or projects/{project}/githubEnterpriseConfigs/{id}
--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.
--require-approval
Require manual approval for triggered builds.
@ -90,20 +104,16 @@ REQUIRED FLAGS
Exactly one of these must be specified:
Build file configuration flags
--build-config=PATH
Path to a YAML or JSON file containing the build configuration in
the repository.
--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
For more details, see:
https://cloud.google.com/cloud-build/docs/build-config
Build configuration file
--inline-config=PATH
Local path to a YAML or JSON file containing a build
configuration.
--inline-config=PATH
Local path to a YAML or JSON file containing a build
configuration.
Dockerfile build configuration flags
@ -115,6 +125,9 @@ REQUIRED FLAGS
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-dir=DOCKERFILE_DIR; default="/"
Location of the directory containing the Dockerfile in the
repository.
@ -167,7 +180,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 triggers create pubsub
$ gcloud beta builds triggers create pubsub

View file

@ -5,11 +5,12 @@ NAME
SYNOPSIS
gcloud alpha builds triggers create webhook
(--trigger-config=PATH | [--secret=SECRET (--build-config=PATH
| --inline-config=PATH | --dockerfile=DOCKERFILE
--dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE)
: --description=DESCRIPTION --name=NAME --require-approval
--service-account=SERVICE_ACCOUNT
| --inline-config=PATH | [--dockerfile=DOCKERFILE
: --dockerfile-dir=DOCKERFILE_DIR;
default="/" --dockerfile-image=DOCKERFILE_IMAGE])
: --description=DESCRIPTION
--github-enterprise-config=GITHUB_ENTERPRISE_CONFIG --name=NAME
--region=REGION --require-approval --service-account=SERVICE_ACCOUNT
--subscription-filter=SUBSCRIPTION_FILTER
--substitutions=[KEY=VALUE,...]
--repo=REPO --repo-type=REPO_TYPE (--branch=BRANCH | --tag=TAG)])
@ -52,9 +53,22 @@ REQUIRED FLAGS
--description=DESCRIPTION
Build trigger description.
--github-enterprise-config=GITHUB_ENTERPRISE_CONFIG
The resource name of the GitHub Enterprise config that should be
applied to this source. Format:
projects/{project}/locations/{location}/githubEnterpriseConfigs/{id}
or projects/{project}/githubEnterpriseConfigs/{id}
--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.
--require-approval
Require manual approval for triggered builds.
@ -93,20 +107,16 @@ REQUIRED FLAGS
Exactly one of these must be specified:
Build file configuration flags
--build-config=PATH
Path to a YAML or JSON file containing the build configuration in
the repository.
--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
For more details, see:
https://cloud.google.com/cloud-build/docs/build-config
Build configuration file
--inline-config=PATH
Local path to a YAML or JSON file containing a build
configuration.
--inline-config=PATH
Local path to a YAML or JSON file containing a build
configuration.
Dockerfile build configuration flags
@ -118,6 +128,9 @@ REQUIRED FLAGS
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-dir=DOCKERFILE_DIR; default="/"
Location of the directory containing the Dockerfile in the
repository.
@ -170,7 +183,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 triggers create webhook
$ gcloud beta builds triggers create webhook

View file

@ -52,7 +52,9 @@ NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct
project, you might be trying to access an API with an invitation-only early
access allowlist. This variant is also available:
access allowlist. These variants are also available:
$ gcloud builds triggers delete
$ gcloud beta builds triggers delete

View file

@ -53,7 +53,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 triggers describe
$ gcloud beta builds triggers describe

View file

@ -47,7 +47,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 triggers
$ gcloud beta builds triggers

View file

@ -22,8 +22,9 @@ REQUIRED FLAGS
OPTIONAL FLAGS
--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 is
used. If builds/region is unset,region is set to "global".
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.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
@ -37,7 +38,9 @@ NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct
project, you might be trying to access an API with an invitation-only early
access allowlist. This variant is also available:
access allowlist. These variants are also available:
$ gcloud builds triggers import
$ gcloud beta builds triggers import

View file

@ -18,8 +18,9 @@ EXAMPLES
FLAGS
--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 is
used. If builds/region is unset,region is set to "global".
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.
LIST COMMAND FLAGS
--filter=EXPRESSION
@ -65,7 +66,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 triggers list
$ gcloud beta builds triggers list

View file

@ -3,7 +3,7 @@ NAME
SYNOPSIS
gcloud alpha builds triggers run (TRIGGER : --region=REGION)
[--branch=BRANCH | --sha=SHA | --tag=TAG] [GCLOUD_WIDE_FLAG ...]
(--branch=BRANCH | --sha=SHA | --tag=TAG) [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Run a build trigger.
@ -40,8 +40,8 @@ POSITIONAL ARGUMENTS
▸ provide the argument --region on the command line;
▸ set the property builds/region.
FLAGS
At most one of these can be specified:
REQUIRED FLAGS
Exactly one of these must be specified:
--branch=BRANCH
Branch to run.
@ -64,7 +64,9 @@ NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct
project, you might be trying to access an API with an invitation-only early
access allowlist. This variant is also available:
access allowlist. These variants are also available:
$ gcloud builds triggers run
$ gcloud beta builds triggers run

View file

@ -5,7 +5,8 @@ NAME
SYNOPSIS
gcloud alpha builds worker-pools create WORKER_POOL --region=REGION
[--config-from-file=CONFIG_FROM_FILE | --peered-network=PEERED_NETWORK
--no-public-egress --worker-disk-size=WORKER_DISK_SIZE
--peered-network-ip-range=PEERED_NETWORK_IP_RANGE --no-public-egress
--worker-disk-size=WORKER_DISK_SIZE
--worker-machine-type=WORKER_MACHINE_TYPE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -20,11 +21,13 @@ EXAMPLES
To create a private pool in project p1 in region us-central1 where workers
are of machine type e2-standard-2 and are peered to the VPC network
projects/123/global/networks/default and have a disk size of 64GB, run:
projects/123/global/networks/default within the IP range 192.168.0.0/28 and
have a disk size of 64GB, run:
$ gcloud alpha builds worker-pools create pwp1 --project=p1 \
--region=us-central1 \
--peered-network=projects/123/global/networks/default \
--peered-network-ip-range=192.168.0.0/28 \
--worker-machine-type=e2-standard-2 --worker-disk-size=64GB
▪ Hybrid pools
@ -78,6 +81,19 @@ OPTIONAL FLAGS
If not specified, the workers are not peered to any network.
--peered-network-ip-range=PEERED_NETWORK_IP_RANGE
An IP range for your peered network. Specify the IP range using
Classless Inter-Domain Routing (CIDR) notation with a slash and
the subnet prefix size, such as '/29'.
Your subnet prefix size must be between 1 and 29. Optional: you
can specify an IP address before the subnet prefix value - for
example 192.168.0.1/24.
If no IP address is specified, your VPC automatically determines
the starting IP for the range. If no IP range is specified, Cloud
Build uses '/24' as the default network IP range.
--no-public-egress
If set, workers in the worker pool are created without an
external IP address.