gcloud: Wed Apr 20 08:58:18 UTC 2022

gcloud/alpha/builds/enterprise-config/gitlab/describe

@@ -0,0 +1,29 @@
+NAME
+    gcloud alpha builds enterprise-config gitlab describe - describe a GitLab
+        Enterprise config in a Google Cloud project
+
+SYNOPSIS
+    gcloud alpha builds enterprise-config gitlab describe CONFIG
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Describe a GitLab Enterprise config in a Google Cloud project.
+
+POSITIONAL ARGUMENTS
+     CONFIG
+        The id of the GitLab Enterprise Config
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --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.
+

gcloud/alpha/builds/enterprise-config/gitlab/help

@@ -0,0 +1,30 @@
+NAME
+    gcloud alpha builds enterprise-config gitlab - manage GitLab Enterprise
+        configurations for Google Cloud Build
+
+SYNOPSIS
+    gcloud alpha builds enterprise-config gitlab COMMAND [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Manage GitLab Enterprise configurations 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:
+
+     describe
+        (ALPHA) Describe a GitLab Enterprise config in a Google Cloud project.
+
+     list
+        (ALPHA) List all GitLab Enterprise configs in a Google Cloud project.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+

gcloud/alpha/builds/enterprise-config/gitlab/list

@@ -0,0 +1,58 @@
+NAME
+    gcloud alpha builds enterprise-config gitlab list - list all GitLab
+        Enterprise configs in a Google Cloud project
+
+SYNOPSIS
+    gcloud alpha builds enterprise-config gitlab list [--filter=EXPRESSION]
+        [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) List all GitLab Enterprise configs in a Google Cloud project.
+
+LIST COMMAND FLAGS
+     --filter=EXPRESSION
+        Apply a Boolean filter EXPRESSION to each resource item to be listed.
+        If the expression evaluates True, then that item is listed. For more
+        details and examples of filter expressions, run $ gcloud topic filters.
+        This flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --limit=LIMIT
+        Maximum number of resources to list. The default is unlimited. This
+        flag interacts with other flags that are applied in this order:
+        --flatten, --sort-by, --filter, --limit.
+
+     --page-size=PAGE_SIZE
+        Some services group resource list output into pages. This flag
+        specifies the maximum number of resources per page. The default is
+        determined by the service if it supports paging, otherwise it is
+        unlimited (no paging). Paging may be applied before or after --filter
+        and --limit depending on the service.
+
+     --sort-by=[FIELD,...]
+        Comma-separated list of resource field key names to sort by. The
+        default order is ascending. Prefix a field with ``~'' for descending
+        order on that field. This flag interacts with other flags that are
+        applied in this order: --flatten, --sort-by, --filter, --limit.
+
+     --uri
+        Print a list of resource URIs instead of the default output, and change
+        the command output to a list of URIs. If this flag is used with
+        --format, the formatting is applied on this URI list. To display URIs
+        alongside other keys instead, use the uri() transform.
+
+GCLOUD WIDE FLAGS
+    These flags are available to all commands: --access-token-file, --account,
+    --billing-project, --configuration, --flags-file, --flatten, --format,
+    --help, --impersonate-service-account, --log-http, --project, --quiet,
+    --trace-token, --user-output-enabled, --verbosity.
+
+    Run $ gcloud help for details.
+
+NOTES
+    This command is currently in alpha and might change without notice. If this
+    command fails with API permission errors despite specifying the correct
+    project, you might be trying to access an API with an invitation-only early
+    access allowlist.
+

gcloud/alpha/builds/enterprise-config/help

@@ -22,6 +22,9 @@ GROUPS
      github
         (ALPHA) Manage GitHub Enterprise configurations for Google Cloud Build.
 
+     gitlab
+        (ALPHA) Manage GitLab Enterprise configurations for Google Cloud Build.
+
 NOTES
     This command is currently in alpha and might change without notice. If this
     command fails with API permission errors despite specifying the correct

gcloud/alpha/builds/triggers/create/help

@@ -25,6 +25,9 @@ COMMANDS
      github
         (ALPHA) Create a build trigger for a GitHub repository.
 
+     manual
+        (ALPHA) Create a build trigger with a manual trigger event.
+
      pubsub
         (ALPHA) Create a build trigger with a Pub/Sub trigger event.
 

gcloud/alpha/builds/triggers/create/manual

@@ -0,0 +1,160 @@
+NAME
+    gcloud alpha builds triggers create manual - create a build trigger with a
+        manual trigger event
+
+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 --filter=FILTER --name=NAME
+          --require-approval --service-account=SERVICE_ACCOUNT
+          --substitutions=[KEY=VALUE,...]
+          --repo=REPO --repo-type=REPO_TYPE (--branch=BRANCH | --tag=TAG)])
+        [GCLOUD_WIDE_FLAG ...]
+
+DESCRIPTION
+    (ALPHA) Create a build trigger with a manual trigger event.
+
+EXAMPLES
+    To create a manual trigger that builds off branch my-branch in a GitHub
+    repository named my-repo:
+
+        $ gcloud alpha builds triggers create manual \
+            --name=my-manual-trigger --build-config=cloudbuild.yaml \
+            --repo=https://www.github.com/owner/repo --repo-type=GITHUB \
+            --branch=my-branch
+
+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.
+
+         --filter=FILTER
+            CEL filter expression for the trigger. See
+            https://cloud.google.com/build/docs/filter-build-events-using-cel
+            for more details.
+
+         --name=NAME
+            Build trigger name.
+
+         --require-approval
+            Require manual approval for triggered builds.
+
+         --service-account=SERVICE_ACCOUNT
+            The service account used for all user-controlled operations
+            including UpdateBuildTrigger, RunBuildTrigger, CreateBuild, and
+            CancelBuild. If no service account is set, then the standard Cloud
+            Build service account ([PROJECT_NUM]@system.gserviceaccount.com) is
+            used instead. Format:
+            projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT_ID_OR_EMAIL}.
+
+         --substitutions=[KEY=VALUE,...]
+            Parameters to be substituted in the build specification.
+
+            For example (using some nonsensical substitution keys; all keys
+            must begin with an underscore):
+
+                $ gcloud builds triggers create ... --config config.yaml
+                    --substitutions _FAVORITE_COLOR=blue,_NUM_CANDIES=10
+
+            This will result in a build where every occurrence of
+            ${_FAVORITE_COLOR} in certain fields is replaced by "blue", and
+            similarly for ${_NUM_CANDIES} and "10".
+
+            Only the following built-in variables can be specified with the
+            --substitutions flag: REPO_NAME, BRANCH_NAME, TAG_NAME,
+            REVISION_ID, COMMIT_SHA, SHORT_SHA.
+
+            For more details, see:
+            https://cloud.google.com/cloud-build/docs/api/build-requests#substitutions
+
+         Exactly one of these must be specified:
+
+           Build file configuration flags
+
+             --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
+
+           Build configuration file
+
+             --inline-config=PATH
+                Local path to a YAML or JSON file containing a build
+                configuration.
+
+           Dockerfile build configuration flags
+
+             --dockerfile=DOCKERFILE
+                Path of Dockerfile to use for builds in the repository.
+
+                If specified, a build config will be generated to run docker
+                build using the specified file.
+
+                The filename is relative to the Dockerfile directory.
+
+             --dockerfile-dir=DOCKERFILE_DIR; default="/"
+                Location of the directory containing the Dockerfile in the
+                repository.
+
+                The directory will also be used as the Docker build context.
+
+             --dockerfile-image=DOCKERFILE_IMAGE
+                Docker image name to build.
+
+                If not specified,
+                gcr.io/PROJECT/github.com/REPO_OWNER/REPO_NAME:$COMMIT_SHA will
+                be used.
+
+                Use a build configuration (cloudbuild.yaml) file for building
+                multiple images in a single trigger.
+
+         Flags for repository information
+
+           --repo=REPO
+              URI of the repository. Currently only HTTP URIs for GitHub and
+              Cloud Source Repositories are supported.
+
+              This flag must be specified if any of the other arguments in this
+              group are specified.
+
+           --repo-type=REPO_TYPE
+              Type of the repository. Currently only GitHub and Cloud Source
+              Repository types are supported.
+
+              This flag must be specified if any of the other arguments in this
+              group are specified.
+
+           Exactly one of these must be specified:
+
+             --branch=BRANCH
+                Branch to build.
+
+             --tag=TAG
+                Tag to 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 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.
+