.TH "GCLOUD_ALPHA_BUILDS_TRIGGERS_IMPORT" 1



.SH "NAME"
.HP
gcloud alpha builds triggers import \- import a build trigger



.SH "SYNOPSIS"
.HP
\f5gcloud alpha builds triggers import\fR \fB\-\-source\fR=\fIPATH\fR [\fB\-\-region\fR=\fIREGION\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR To import a trigger from a file: $ cat > trigger.yaml <<EOF name:
my\-trigger github: owner: GoogleCloudPlatform name: cloud\-builders push:
branch: .\fB EOF


\fR

.SH "EXAMPLES"

To import a build trigger from a file called trigger.yaml, run:

.RS 2m
$ gcloud alpha builds triggers import \-\-source=trigger.yaml
.RE



.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-source\fR=\fIPATH\fR

File path where trigger should be imported from.


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-region\fR=\fIREGION\fR

The region of the Cloud Build Service to use. Must be set to a supported region
name (e.g. \f5us\-central1\fR). If unset, \f5builds/region\fR, which is the
default region to use when working with Cloud Build resources, is used. If
builds/region is unset, region is set to \f5global\fR. Note: Region must be
specified in 2nd gen repo; \f5global\fR is not supported.


.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "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:

.RS 2m
$ gcloud builds triggers import
.RE

.RS 2m
$ gcloud beta builds triggers import
.RE