Marketplace
BrowsePublish
Marketplace
You are viewing an outdated version of provider-gcp.Go to Latest
upbound/provider-gcp@v0.41.2
Trigger
cloudbuild.gcp.upbound.io
Trigger
upbound/provider-gcp@v0.41.2cloudbuild.gcp.upbound.io

Trigger is the Schema for the Triggers API. Configuration for an automated build in response to source repository changes.

Type

CRD

Group

cloudbuild.gcp.upbound.io

Version

v1beta1

apiVersion: cloudbuild.gcp.upbound.io/v1beta1

kind: Trigger

API Documentation
apiVersion
string
kind
string
metadata
object
spec
object
object

TriggerSpec defines the desired state of Trigger

forProvider
requiredobject
requiredobject

No description provided.

array

Configuration for manual approval to start a build invocation of this BuildTrigger. Builds created by this trigger will require approval before they execute. Any user with a Cloud Build Approver role for the project can approve a build. Structure is documented below.

array

BitbucketServerTriggerConfig describes the configuration of a trigger that creates a build whenever a Bitbucket Server event is received. Structure is documented below.

array

Filter to match changes in pull requests. Structure is documented below.

push
array
array

Filter to match changes in refs like branches, tags. Structure is documented below.

branch
string
tag
string
repoSlug
string
build
array
array

Contents of the build template. Either a filename or build template must be provided. Structure is documented below.

array

Artifacts produced by the build that should be uploaded upon successful completion of all build steps. Structure is documented below.

images
array
array

A list of images to be pushed upon the successful completion of all build steps. The images are pushed using the builder service account's credentials. The digests of the pushed images will be stored in the Build resource's results field. If any of the images fail to be pushed, the build status is marked FAILURE.

objects
array
array

A list of objects to be uploaded to Cloud Storage upon successful completion of all build steps. Files in the workspace matching specified paths globs will be uploaded to the Cloud Storage location using the builder service account's credentials. The location and generation of the uploaded objects will be stored in the Build resource's results field. If any objects fail to be pushed, the build is marked FAILURE. Structure is documented below.

location
string
paths
array
array

Path globs used to match files in the build's workspace.

array

Secrets and secret environment variables. Structure is documented below.

array

Pairs a secret environment variable with a SecretVersion in Secret Manager. Structure is documented below.

env
string
images
array
array

A list of images to be pushed upon the successful completion of all build steps. The images are pushed using the builder service account's credentials. The digests of the pushed images will be stored in the Build resource's results field. If any of the images fail to be pushed, the build status is marked FAILURE.

options
array
array

Special options for this build. Structure is documented below.

env
array
array

A list of environment variable definitions to be used when running a step. The elements are of the form "KEY=VALUE" for the environment variable "KEY" being given the value "VALUE".

logging
string
array

A list of environment variables which are encrypted using a Cloud Key Management Service crypto key. These values must be specified in the build's Secret.

array

Requested hash for SourceProvenance. Each value may be one of: NONE, SHA256, MD5.

volumes
array
array

List of volumes to mount into the build step. Each volume is created as an empty volume prior to execution of the build step. Upon completion of the build, volumes and their contents are discarded. Using a named volume in only one step is not valid as it is indicative of a build request with an incorrect configuration. Structure is documented below.

name
string
path
string
queueTtl
string
secret
array
array

Secrets to decrypt using Cloud Key Management Service. Structure is documented below.

source
array
array

The location of the source files to build. One of storageSource or repoSource must be provided. Structure is documented below.

array

Location of the source in a Google Cloud Source Repository. Structure is documented below.

commitSha
string
dir
string
projectId
string
repoName
string
tagName
string
array

Location of the source in an archive file in Google Cloud Storage. Structure is documented below.

bucket
string
object
string
step
array
array

The operations to be performed on the workspace. Structure is documented below.

array

Allow this build step to fail without failing the entire build if and only if the exit code is one of the specified codes. If allowFailure is also specified, this field will take precedence.

args
array
array

A list of arguments that will be presented to the step when it is started. If the image used to run the step's container has an entrypoint, the args are used as arguments to that entrypoint. If the image does not define an entrypoint, the first element in args is used as the entrypoint, and the remainder will be used as arguments.

dir
string
env
array
array

A list of environment variable definitions to be used when running a step. The elements are of the form "KEY=VALUE" for the environment variable "KEY" being given the value "VALUE".

id
string
name
string
script
string
array

A list of environment variables which are encrypted using a Cloud Key Management Service crypto key. These values must be specified in the build's Secret.

timeout
string
timing
string
volumes
array
array

List of volumes to mount into the build step. Each volume is created as an empty volume prior to execution of the build step. Upon completion of the build, volumes and their contents are discarded. Using a named volume in only one step is not valid as it is indicative of a build request with an incorrect configuration. Structure is documented below.

name
string
path
string
waitFor
array
array

The ID(s) of the step(s) that this build step depends on. This build step will not start until all the build steps in wait_for have completed successfully. If wait_for is empty, this build step will start when all previous build steps in the Build.Steps list have completed successfully.

tags
array
array

Tags for annotation of a Build. These are not docker tags.

timeout
string
disabled
boolean
filename
string
filter
string
array

The file source describing the local or remote Build template. Structure is documented below.

github
array
array

Describes the configuration of a trigger that creates a build whenever a GitHub event is received. One of trigger_template, github, pubsub_config or webhook_config must be provided. Structure is documented below.

name
string
owner
string
array

filter to match changes in pull requests. Specify only one of pull_request or push. Structure is documented below.

push
array
array

filter to match changes in refs, like branches or tags. Specify only one of pull_request or push. Structure is documented below.

branch
string
tag
string
array

ignoredFiles and includedFiles are file glob matches using https://golang.org/pkg/path/filepath/#Match extended with support for **. If ignoredFiles and changed files are both empty, then they are not used to determine whether or not to trigger a build. If ignoredFiles is not empty, then we ignore any files that match any of the ignored_file globs. If the change has no files that are outside of the ignoredFiles globs, then we do not trigger a build.

array

ignoredFiles and includedFiles are file glob matches using https://golang.org/pkg/path/filepath/#Match extended with support for **. If any of the files altered in the commit pass the ignoredFiles filter and includedFiles is empty, then as far as this filter is concerned, we should trigger the build. If any of the files altered in the commit pass the ignoredFiles filter and includedFiles is not empty, then we make sure that at least one of those files matches a includedFiles glob. If not, then we do not trigger a build.

location
string
name
string
project
string
array

PubsubConfig describes the configuration of a trigger that creates a build whenever a Pub/Sub message is published. One of trigger_template, github, pubsub_config webhook_config or source_to_build must be provided. Structure is documented below.

topic
string
topicRef
object
object

Reference to a Topic in pubsub to populate topic.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
object

Selector for a Topic in pubsub to populate topic.

policy
object
object

Policies for selection.

resolve
string
array

The configuration of a trigger that creates a build whenever an event from Repo API is received. Structure is documented below.

array

Contains filter properties for matching Pull Requests. Structure is documented below.

push
array
array

Contains filter properties for matching git pushes. Structure is documented below.

branch
string
tag
string
object

Reference to a ServiceAccount in cloudplatform to populate serviceAccount.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
object

Selector for a ServiceAccount in cloudplatform to populate serviceAccount.

policy
object
object

Policies for selection.

resolve
string
array

The repo and ref of the repository from which to build. This field is used only for those triggers that do not respond to SCM events. Triggers that respond to such events build source at whatever commit caused the event. This field is currently only used by Webhook, Pub/Sub, Manual, and Cron triggers. One of trigger_template, github, pubsub_config webhook_config or source_to_build must be provided. Structure is documented below.

tags
array
array

Tags for annotation of a BuildTrigger

array

Template describing the types of source changes to trigger a build. Branch and tag names in trigger templates are interpreted as regular expressions. Any branch or tag change that matches that regular expression will trigger a build. One of trigger_template, github, pubsub_config, webhook_config or source_to_build must be provided. Structure is documented below.

commitSha
string
dir
string
projectId
string
repoName
string
tagName
string
array

WebhookConfig describes the configuration of a trigger that creates a build whenever a webhook is sent to a trigger's webhook URL. One of trigger_template, github, pubsub_config webhook_config or source_to_build must be provided. Structure is documented below.

secret
string
secretRef
object
object

Reference to a SecretVersion in secretmanager to populate secret.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
object

Selector for a SecretVersion in secretmanager to populate secret.

policy
object
object

Policies for selection.

resolve
string
object

THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.

array

Configuration for manual approval to start a build invocation of this BuildTrigger. Builds created by this trigger will require approval before they execute. Any user with a Cloud Build Approver role for the project can approve a build. Structure is documented below.

array

BitbucketServerTriggerConfig describes the configuration of a trigger that creates a build whenever a Bitbucket Server event is received. Structure is documented below.

array

Filter to match changes in pull requests. Structure is documented below.

push
array
array

Filter to match changes in refs like branches, tags. Structure is documented below.

branch
string
tag
string
repoSlug
string
build
array
array

Contents of the build template. Either a filename or build template must be provided. Structure is documented below.

array

Artifacts produced by the build that should be uploaded upon successful completion of all build steps. Structure is documented below.

images
array
array

A list of images to be pushed upon the successful completion of all build steps. The images are pushed using the builder service account's credentials. The digests of the pushed images will be stored in the Build resource's results field. If any of the images fail to be pushed, the build status is marked FAILURE.

objects
array
array

A list of objects to be uploaded to Cloud Storage upon successful completion of all build steps. Files in the workspace matching specified paths globs will be uploaded to the Cloud Storage location using the builder service account's credentials. The location and generation of the uploaded objects will be stored in the Build resource's results field. If any objects fail to be pushed, the build is marked FAILURE. Structure is documented below.

location
string
paths
array
array

Path globs used to match files in the build's workspace.

array

Secrets and secret environment variables. Structure is documented below.

array

Pairs a secret environment variable with a SecretVersion in Secret Manager. Structure is documented below.

env
string
images
array
array

A list of images to be pushed upon the successful completion of all build steps. The images are pushed using the builder service account's credentials. The digests of the pushed images will be stored in the Build resource's results field. If any of the images fail to be pushed, the build status is marked FAILURE.

options
array
array

Special options for this build. Structure is documented below.

env
array
array

A list of environment variable definitions to be used when running a step. The elements are of the form "KEY=VALUE" for the environment variable "KEY" being given the value "VALUE".

logging
string
array

A list of environment variables which are encrypted using a Cloud Key Management Service crypto key. These values must be specified in the build's Secret.

array

Requested hash for SourceProvenance. Each value may be one of: NONE, SHA256, MD5.

volumes
array
array

List of volumes to mount into the build step. Each volume is created as an empty volume prior to execution of the build step. Upon completion of the build, volumes and their contents are discarded. Using a named volume in only one step is not valid as it is indicative of a build request with an incorrect configuration. Structure is documented below.

name
string
path
string
queueTtl
string
secret
array
array

Secrets to decrypt using Cloud Key Management Service. Structure is documented below.

source
array
array

The location of the source files to build. One of storageSource or repoSource must be provided. Structure is documented below.

array

Location of the source in a Google Cloud Source Repository. Structure is documented below.

commitSha
string
dir
string
projectId
string
repoName
string
tagName
string
array

Location of the source in an archive file in Google Cloud Storage. Structure is documented below.

bucket
string
object
string
step
array
array

The operations to be performed on the workspace. Structure is documented below.

array

Allow this build step to fail without failing the entire build if and only if the exit code is one of the specified codes. If allowFailure is also specified, this field will take precedence.

args
array
array

A list of arguments that will be presented to the step when it is started. If the image used to run the step's container has an entrypoint, the args are used as arguments to that entrypoint. If the image does not define an entrypoint, the first element in args is used as the entrypoint, and the remainder will be used as arguments.

dir
string
env
array
array

A list of environment variable definitions to be used when running a step. The elements are of the form "KEY=VALUE" for the environment variable "KEY" being given the value "VALUE".

id
string
name
string
script
string
array

A list of environment variables which are encrypted using a Cloud Key Management Service crypto key. These values must be specified in the build's Secret.

timeout
string
timing
string
volumes
array
array

List of volumes to mount into the build step. Each volume is created as an empty volume prior to execution of the build step. Upon completion of the build, volumes and their contents are discarded. Using a named volume in only one step is not valid as it is indicative of a build request with an incorrect configuration. Structure is documented below.

name
string
path
string
waitFor
array
array

The ID(s) of the step(s) that this build step depends on. This build step will not start until all the build steps in wait_for have completed successfully. If wait_for is empty, this build step will start when all previous build steps in the Build.Steps list have completed successfully.

tags
array
array

Tags for annotation of a Build. These are not docker tags.

timeout
string
disabled
boolean
filename
string
filter
string
array

The file source describing the local or remote Build template. Structure is documented below.

github
array
array

Describes the configuration of a trigger that creates a build whenever a GitHub event is received. One of trigger_template, github, pubsub_config or webhook_config must be provided. Structure is documented below.

name
string
owner
string
array

filter to match changes in pull requests. Specify only one of pull_request or push. Structure is documented below.

push
array
array

filter to match changes in refs, like branches or tags. Specify only one of pull_request or push. Structure is documented below.

branch
string
tag
string
array

ignoredFiles and includedFiles are file glob matches using https://golang.org/pkg/path/filepath/#Match extended with support for **. If ignoredFiles and changed files are both empty, then they are not used to determine whether or not to trigger a build. If ignoredFiles is not empty, then we ignore any files that match any of the ignored_file globs. If the change has no files that are outside of the ignoredFiles globs, then we do not trigger a build.

array

ignoredFiles and includedFiles are file glob matches using https://golang.org/pkg/path/filepath/#Match extended with support for **. If any of the files altered in the commit pass the ignoredFiles filter and includedFiles is empty, then as far as this filter is concerned, we should trigger the build. If any of the files altered in the commit pass the ignoredFiles filter and includedFiles is not empty, then we make sure that at least one of those files matches a includedFiles glob. If not, then we do not trigger a build.

location
string
name
string
project
string
array

PubsubConfig describes the configuration of a trigger that creates a build whenever a Pub/Sub message is published. One of trigger_template, github, pubsub_config webhook_config or source_to_build must be provided. Structure is documented below.

topic
string
topicRef
object
object

Reference to a Topic in pubsub to populate topic.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
object

Selector for a Topic in pubsub to populate topic.

policy
object
object

Policies for selection.

resolve
string
array

The configuration of a trigger that creates a build whenever an event from Repo API is received. Structure is documented below.

array

Contains filter properties for matching Pull Requests. Structure is documented below.

push
array
array

Contains filter properties for matching git pushes. Structure is documented below.

branch
string
tag
string
object

Reference to a ServiceAccount in cloudplatform to populate serviceAccount.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
object

Selector for a ServiceAccount in cloudplatform to populate serviceAccount.

policy
object
object

Policies for selection.

resolve
string
array

The repo and ref of the repository from which to build. This field is used only for those triggers that do not respond to SCM events. Triggers that respond to such events build source at whatever commit caused the event. This field is currently only used by Webhook, Pub/Sub, Manual, and Cron triggers. One of trigger_template, github, pubsub_config webhook_config or source_to_build must be provided. Structure is documented below.

tags
array
array

Tags for annotation of a BuildTrigger

array

Template describing the types of source changes to trigger a build. Branch and tag names in trigger templates are interpreted as regular expressions. Any branch or tag change that matches that regular expression will trigger a build. One of trigger_template, github, pubsub_config, webhook_config or source_to_build must be provided. Structure is documented below.

commitSha
string
dir
string
projectId
string
repoName
string
tagName
string
array

WebhookConfig describes the configuration of a trigger that creates a build whenever a webhook is sent to a trigger's webhook URL. One of trigger_template, github, pubsub_config webhook_config or source_to_build must be provided. Structure is documented below.

secret
string
secretRef
object
object

Reference to a SecretVersion in secretmanager to populate secret.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
object

Selector for a SecretVersion in secretmanager to populate secret.

policy
object
object

Policies for selection.

resolve
string
array

THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md

object

ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
object

PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.

configRef
object
object

SecretStoreConfigRef specifies which secret store config should be used for this ConnectionSecret.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
metadata
object
object

Metadata is the metadata for connection secret.

labels
object
type
string
name
requiredstring
object

WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.

name
requiredstring
namespace
requiredstring
status
object
object

TriggerStatus defines the observed state of Trigger.

object

No description provided.

array

Configuration for manual approval to start a build invocation of this BuildTrigger. Builds created by this trigger will require approval before they execute. Any user with a Cloud Build Approver role for the project can approve a build. Structure is documented below.

array

BitbucketServerTriggerConfig describes the configuration of a trigger that creates a build whenever a Bitbucket Server event is received. Structure is documented below.

array

Filter to match changes in pull requests. Structure is documented below.

push
array
array

Filter to match changes in refs like branches, tags. Structure is documented below.

branch
string
tag
string
repoSlug
string
build
array
array

Contents of the build template. Either a filename or build template must be provided. Structure is documented below.

array

Artifacts produced by the build that should be uploaded upon successful completion of all build steps. Structure is documented below.

images
array
array

A list of images to be pushed upon the successful completion of all build steps. The images are pushed using the builder service account's credentials. The digests of the pushed images will be stored in the Build resource's results field. If any of the images fail to be pushed, the build status is marked FAILURE.

objects
array
array

A list of objects to be uploaded to Cloud Storage upon successful completion of all build steps. Files in the workspace matching specified paths globs will be uploaded to the Cloud Storage location using the builder service account's credentials. The location and generation of the uploaded objects will be stored in the Build resource's results field. If any objects fail to be pushed, the build is marked FAILURE. Structure is documented below.

location
string
paths
array
array

Path globs used to match files in the build's workspace.

timing
array
array

Output only. Stores timing information for executing this build step.

endTime
string
startTime
string
array

Secrets and secret environment variables. Structure is documented below.

array

Pairs a secret environment variable with a SecretVersion in Secret Manager. Structure is documented below.

env
string
images
array
array

A list of images to be pushed upon the successful completion of all build steps. The images are pushed using the builder service account's credentials. The digests of the pushed images will be stored in the Build resource's results field. If any of the images fail to be pushed, the build status is marked FAILURE.

options
array
array

Special options for this build. Structure is documented below.

env
array
array

A list of environment variable definitions to be used when running a step. The elements are of the form "KEY=VALUE" for the environment variable "KEY" being given the value "VALUE".

logging
string
array

A list of environment variables which are encrypted using a Cloud Key Management Service crypto key. These values must be specified in the build's Secret.

array

Requested hash for SourceProvenance. Each value may be one of: NONE, SHA256, MD5.

volumes
array
array

List of volumes to mount into the build step. Each volume is created as an empty volume prior to execution of the build step. Upon completion of the build, volumes and their contents are discarded. Using a named volume in only one step is not valid as it is indicative of a build request with an incorrect configuration. Structure is documented below.

name
string
path
string
queueTtl
string
secret
array
array

Secrets to decrypt using Cloud Key Management Service. Structure is documented below.

source
array
array

The location of the source files to build. One of storageSource or repoSource must be provided. Structure is documented below.

array

Location of the source in a Google Cloud Source Repository. Structure is documented below.

commitSha
string
dir
string
projectId
string
repoName
string
tagName
string
array

Location of the source in an archive file in Google Cloud Storage. Structure is documented below.

bucket
string
object
string
step
array
array

The operations to be performed on the workspace. Structure is documented below.

array

Allow this build step to fail without failing the entire build if and only if the exit code is one of the specified codes. If allowFailure is also specified, this field will take precedence.

args
array
array

A list of arguments that will be presented to the step when it is started. If the image used to run the step's container has an entrypoint, the args are used as arguments to that entrypoint. If the image does not define an entrypoint, the first element in args is used as the entrypoint, and the remainder will be used as arguments.

dir
string
env
array
array

A list of environment variable definitions to be used when running a step. The elements are of the form "KEY=VALUE" for the environment variable "KEY" being given the value "VALUE".

id
string
name
string
script
string
array

A list of environment variables which are encrypted using a Cloud Key Management Service crypto key. These values must be specified in the build's Secret.

timeout
string
timing
string
volumes
array
array

List of volumes to mount into the build step. Each volume is created as an empty volume prior to execution of the build step. Upon completion of the build, volumes and their contents are discarded. Using a named volume in only one step is not valid as it is indicative of a build request with an incorrect configuration. Structure is documented below.

name
string
path
string
waitFor
array
array

The ID(s) of the step(s) that this build step depends on. This build step will not start until all the build steps in wait_for have completed successfully. If wait_for is empty, this build step will start when all previous build steps in the Build.Steps list have completed successfully.

tags
array
array

Tags for annotation of a Build. These are not docker tags.

timeout
string
disabled
boolean
filename
string
filter
string
array

The file source describing the local or remote Build template. Structure is documented below.

github
array
array

Describes the configuration of a trigger that creates a build whenever a GitHub event is received. One of trigger_template, github, pubsub_config or webhook_config must be provided. Structure is documented below.

name
string
owner
string
array

filter to match changes in pull requests. Specify only one of pull_request or push. Structure is documented below.

push
array
array

filter to match changes in refs, like branches or tags. Specify only one of pull_request or push. Structure is documented below.

branch
string
tag
string
id
string
array

ignoredFiles and includedFiles are file glob matches using https://golang.org/pkg/path/filepath/#Match extended with support for **. If ignoredFiles and changed files are both empty, then they are not used to determine whether or not to trigger a build. If ignoredFiles is not empty, then we ignore any files that match any of the ignored_file globs. If the change has no files that are outside of the ignoredFiles globs, then we do not trigger a build.

array

ignoredFiles and includedFiles are file glob matches using https://golang.org/pkg/path/filepath/#Match extended with support for **. If any of the files altered in the commit pass the ignoredFiles filter and includedFiles is empty, then as far as this filter is concerned, we should trigger the build. If any of the files altered in the commit pass the ignoredFiles filter and includedFiles is not empty, then we make sure that at least one of those files matches a includedFiles glob. If not, then we do not trigger a build.

location
string
name
string
project
string
array

PubsubConfig describes the configuration of a trigger that creates a build whenever a Pub/Sub message is published. One of trigger_template, github, pubsub_config webhook_config or source_to_build must be provided. Structure is documented below.

array

The configuration of a trigger that creates a build whenever an event from Repo API is received. Structure is documented below.

array

Contains filter properties for matching Pull Requests. Structure is documented below.

push
array
array

Contains filter properties for matching git pushes. Structure is documented below.

branch
string
tag
string
array

The repo and ref of the repository from which to build. This field is used only for those triggers that do not respond to SCM events. Triggers that respond to such events build source at whatever commit caused the event. This field is currently only used by Webhook, Pub/Sub, Manual, and Cron triggers. One of trigger_template, github, pubsub_config webhook_config or source_to_build must be provided. Structure is documented below.

tags
array
array

Tags for annotation of a BuildTrigger

triggerId
string
array

Template describing the types of source changes to trigger a build. Branch and tag names in trigger templates are interpreted as regular expressions. Any branch or tag change that matches that regular expression will trigger a build. One of trigger_template, github, pubsub_config, webhook_config or source_to_build must be provided. Structure is documented below.

commitSha
string
dir
string
projectId
string
repoName
string
tagName
string
array

WebhookConfig describes the configuration of a trigger that creates a build whenever a webhook is sent to a trigger's webhook URL. One of trigger_template, github, pubsub_config webhook_config or source_to_build must be provided. Structure is documented below.

secret
string
state
string
array

Conditions of the resource.

lastTransitionTime
requiredstring
message
string
reason
requiredstring
status
requiredstring
type
requiredstring
Marketplace

Discover the building blocks for your internal cloud platform.

© 2022 Upbound, Inc.

SolutionsProvidersConfigurations
LearnDocumentationTry for Free
MorePrivacy PolicyTerms & Conditions
Marketplace

© 2022 Upbound, Inc.

Marketplace

Discover the building blocksfor your internal cloud platform.