Trigger
Configuration for an automated build in response to source repository changes.
To get more information about Trigger, see:
Create a Trigger Resource
new Trigger(name: string, args?: TriggerArgs, opts?: CustomResourceOptions);def Trigger(resource_name, opts=None, build=None, description=None, disabled=None, filename=None, github=None, ignored_files=None, included_files=None, name=None, project=None, substitutions=None, trigger_template=None, __props__=None);func NewTrigger(ctx *Context, name string, args *TriggerArgs, opts ...ResourceOption) (*Trigger, error)public Trigger(string name, TriggerArgs? args = null, CustomResourceOptions? opts = null)- name string
- The unique name of the resource.
- args TriggerArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- opts ResourceOptions
- A bag of options that control this resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args TriggerArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args TriggerArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
Trigger Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Programming Model docs.
Inputs
The Trigger resource accepts the following input properties:
- Build
Trigger
Build Args Contents of the build template. Either a filename or build template must be provided. Structure is documented below.
- Description string
Human-readable description of the trigger.
- Disabled bool
Whether the trigger is disabled or not. If true, the trigger will never result in a build.
- Filename string
Path, from the source root, to a file whose contents is used for the template. Either a filename or build template must be provided.
- Github
Trigger
Github Args Describes the configuration of a trigger that creates a build whenever a GitHub event is received. One of
trigger_templateorgithubmust be provided. Structure is documented below.- Ignored
Files List<string> 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.- Included
Files List<string> 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.- Name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- Project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- Substitutions Dictionary<string, string>
Substitutions data for Build resource.
- Trigger
Template TriggerTrigger Template Args 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_templateorgithubmust be provided. Structure is documented below.
- Build
Trigger
Build Contents of the build template. Either a filename or build template must be provided. Structure is documented below.
- Description string
Human-readable description of the trigger.
- Disabled bool
Whether the trigger is disabled or not. If true, the trigger will never result in a build.
- Filename string
Path, from the source root, to a file whose contents is used for the template. Either a filename or build template must be provided.
- Github
Trigger
Github Describes the configuration of a trigger that creates a build whenever a GitHub event is received. One of
trigger_templateorgithubmust be provided. Structure is documented below.- Ignored
Files []string 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.- Included
Files []string 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.- Name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- Project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- Substitutions map[string]string
Substitutions data for Build resource.
- Trigger
Template TriggerTrigger Template 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_templateorgithubmust be provided. Structure is documented below.
- build
Trigger
Build Contents of the build template. Either a filename or build template must be provided. Structure is documented below.
- description string
Human-readable description of the trigger.
- disabled boolean
Whether the trigger is disabled or not. If true, the trigger will never result in a build.
- filename string
Path, from the source root, to a file whose contents is used for the template. Either a filename or build template must be provided.
- github
Trigger
Github Describes the configuration of a trigger that creates a build whenever a GitHub event is received. One of
trigger_templateorgithubmust be provided. Structure is documented below.- ignored
Files string[] 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.- included
Files string[] 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.- name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- substitutions {[key: string]: string}
Substitutions data for Build resource.
- trigger
Template TriggerTrigger Template 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_templateorgithubmust be provided. Structure is documented below.
- build
Dict[Trigger
Build] Contents of the build template. Either a filename or build template must be provided. Structure is documented below.
- description str
Human-readable description of the trigger.
- disabled bool
Whether the trigger is disabled or not. If true, the trigger will never result in a build.
- filename str
Path, from the source root, to a file whose contents is used for the template. Either a filename or build template must be provided.
- github
Dict[Trigger
Github] Describes the configuration of a trigger that creates a build whenever a GitHub event is received. One of
trigger_templateorgithubmust be provided. Structure is documented below.- ignored_
files List[str] 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.- included_
files List[str] 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.- name str
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- project str
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- substitutions Dict[str, str]
Substitutions data for Build resource.
- trigger_
template Dict[TriggerTrigger Template] 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_templateorgithubmust be provided. Structure is documented below.
Outputs
All input properties are implicitly available as output properties. Additionally, the Trigger resource produces the following output properties:
- create_
time str Time when the trigger was created.
- id str
- The provider-assigned unique ID for this managed resource.
- trigger_
id str The unique identifier for the trigger.
Look up an Existing Trigger Resource
Get an existing Trigger resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: TriggerState, opts?: CustomResourceOptions): Triggerstatic get(resource_name, id, opts=None, build=None, create_time=None, description=None, disabled=None, filename=None, github=None, ignored_files=None, included_files=None, name=None, project=None, substitutions=None, trigger_id=None, trigger_template=None, __props__=None);func GetTrigger(ctx *Context, name string, id IDInput, state *TriggerState, opts ...ResourceOption) (*Trigger, error)public static Trigger Get(string name, Input<string> id, TriggerState? state, CustomResourceOptions? opts = null)- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
The following state arguments are supported:
- Build
Trigger
Build Args Contents of the build template. Either a filename or build template must be provided. Structure is documented below.
- Create
Time string Time when the trigger was created.
- Description string
Human-readable description of the trigger.
- Disabled bool
Whether the trigger is disabled or not. If true, the trigger will never result in a build.
- Filename string
Path, from the source root, to a file whose contents is used for the template. Either a filename or build template must be provided.
- Github
Trigger
Github Args Describes the configuration of a trigger that creates a build whenever a GitHub event is received. One of
trigger_templateorgithubmust be provided. Structure is documented below.- Ignored
Files List<string> 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.- Included
Files List<string> 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.- Name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- Project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- Substitutions Dictionary<string, string>
Substitutions data for Build resource.
- Trigger
Id string The unique identifier for the trigger.
- Trigger
Template TriggerTrigger Template Args 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_templateorgithubmust be provided. Structure is documented below.
- Build
Trigger
Build Contents of the build template. Either a filename or build template must be provided. Structure is documented below.
- Create
Time string Time when the trigger was created.
- Description string
Human-readable description of the trigger.
- Disabled bool
Whether the trigger is disabled or not. If true, the trigger will never result in a build.
- Filename string
Path, from the source root, to a file whose contents is used for the template. Either a filename or build template must be provided.
- Github
Trigger
Github Describes the configuration of a trigger that creates a build whenever a GitHub event is received. One of
trigger_templateorgithubmust be provided. Structure is documented below.- Ignored
Files []string 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.- Included
Files []string 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.- Name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- Project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- Substitutions map[string]string
Substitutions data for Build resource.
- Trigger
Id string The unique identifier for the trigger.
- Trigger
Template TriggerTrigger Template 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_templateorgithubmust be provided. Structure is documented below.
- build
Trigger
Build Contents of the build template. Either a filename or build template must be provided. Structure is documented below.
- create
Time string Time when the trigger was created.
- description string
Human-readable description of the trigger.
- disabled boolean
Whether the trigger is disabled or not. If true, the trigger will never result in a build.
- filename string
Path, from the source root, to a file whose contents is used for the template. Either a filename or build template must be provided.
- github
Trigger
Github Describes the configuration of a trigger that creates a build whenever a GitHub event is received. One of
trigger_templateorgithubmust be provided. Structure is documented below.- ignored
Files string[] 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.- included
Files string[] 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.- name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- project string
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- substitutions {[key: string]: string}
Substitutions data for Build resource.
- trigger
Id string The unique identifier for the trigger.
- trigger
Template TriggerTrigger Template 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_templateorgithubmust be provided. Structure is documented below.
- build
Dict[Trigger
Build] Contents of the build template. Either a filename or build template must be provided. Structure is documented below.
- create_
time str Time when the trigger was created.
- description str
Human-readable description of the trigger.
- disabled bool
Whether the trigger is disabled or not. If true, the trigger will never result in a build.
- filename str
Path, from the source root, to a file whose contents is used for the template. Either a filename or build template must be provided.
- github
Dict[Trigger
Github] Describes the configuration of a trigger that creates a build whenever a GitHub event is received. One of
trigger_templateorgithubmust be provided. Structure is documented below.- ignored_
files List[str] 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.- included_
files List[str] 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.- name str
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- project str
The ID of the project in which the resource belongs. If it is not provided, the provider project is used.
- substitutions Dict[str, str]
Substitutions data for Build resource.
- trigger_
id str The unique identifier for the trigger.
- trigger_
template Dict[TriggerTrigger Template] 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_templateorgithubmust be provided. Structure is documented below.
Supporting Types
TriggerBuild
- Steps
List<Trigger
Build Step Args> The operations to be performed on the workspace. Structure is documented below.
- Images List<string>
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.
- List<string>
Tags for annotation of a Build. These are not docker tags.
- Timeout string
Time limit for executing this build step. If not defined, the step has no time limit and will be allowed to continue to run until either it completes or the build itself times out.
- Steps
[]Trigger
Build Step The operations to be performed on the workspace. Structure is documented below.
- Images []string
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.
- []string
Tags for annotation of a Build. These are not docker tags.
- Timeout string
Time limit for executing this build step. If not defined, the step has no time limit and will be allowed to continue to run until either it completes or the build itself times out.
- steps
Trigger
Build Step[] The operations to be performed on the workspace. Structure is documented below.
- images string[]
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.
- string[]
Tags for annotation of a Build. These are not docker tags.
- timeout string
Time limit for executing this build step. If not defined, the step has no time limit and will be allowed to continue to run until either it completes or the build itself times out.
- steps
List[Trigger
Build Step] The operations to be performed on the workspace. Structure is documented below.
- images List[str]
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.
- List[str]
Tags for annotation of a Build. These are not docker tags.
- timeout str
Time limit for executing this build step. If not defined, the step has no time limit and will be allowed to continue to run until either it completes or the build itself times out.
TriggerBuildStep
- Name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- Args List<string>
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
Working directory to use when running this step’s container. If this value is a relative path, it is relative to the build’s working directory. If this value is absolute, it may be outside the build’s working directory, in which case the contents of the path may not be persisted across build step executions, unless a
volumefor that path is specified. If the build specifies aRepoSourcewithdirand a step with adir, which specifies an absolute path, theRepoSourcediris ignored for the step’s execution.- Entrypoint string
Entrypoint to be used instead of the build step image’s default entrypoint. If unset, the image’s default entrypoint is used
- Envs List<string>
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
Unique identifier for this build step, used in
wait_forto reference this build step as a dependency.- Secret
Envs List<string> 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
Time limit for executing this build step. If not defined, the step has no time limit and will be allowed to continue to run until either it completes or the build itself times out.
- Timing string
Output only. Stores timing information for executing this build step.
- Volumes
List<Trigger
Build Step Volume Args> 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.
- Wait
Fors List<string> 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_forhave completed successfully. Ifwait_foris empty, this build step will start when all previous build steps in theBuild.Stepslist have completed successfully.
- Name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- Args []string
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
Working directory to use when running this step’s container. If this value is a relative path, it is relative to the build’s working directory. If this value is absolute, it may be outside the build’s working directory, in which case the contents of the path may not be persisted across build step executions, unless a
volumefor that path is specified. If the build specifies aRepoSourcewithdirand a step with adir, which specifies an absolute path, theRepoSourcediris ignored for the step’s execution.- Entrypoint string
Entrypoint to be used instead of the build step image’s default entrypoint. If unset, the image’s default entrypoint is used
- Envs []string
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
Unique identifier for this build step, used in
wait_forto reference this build step as a dependency.- Secret
Envs []string 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
Time limit for executing this build step. If not defined, the step has no time limit and will be allowed to continue to run until either it completes or the build itself times out.
- Timing string
Output only. Stores timing information for executing this build step.
- Volumes
[]Trigger
Build Step Volume 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.
- Wait
Fors []string 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_forhave completed successfully. Ifwait_foris empty, this build step will start when all previous build steps in theBuild.Stepslist have completed successfully.
- name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- args string[]
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
Working directory to use when running this step’s container. If this value is a relative path, it is relative to the build’s working directory. If this value is absolute, it may be outside the build’s working directory, in which case the contents of the path may not be persisted across build step executions, unless a
volumefor that path is specified. If the build specifies aRepoSourcewithdirand a step with adir, which specifies an absolute path, theRepoSourcediris ignored for the step’s execution.- entrypoint string
Entrypoint to be used instead of the build step image’s default entrypoint. If unset, the image’s default entrypoint is used
- envs string[]
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
Unique identifier for this build step, used in
wait_forto reference this build step as a dependency.- secret
Envs string[] 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
Time limit for executing this build step. If not defined, the step has no time limit and will be allowed to continue to run until either it completes or the build itself times out.
- timing string
Output only. Stores timing information for executing this build step.
- volumes
Trigger
Build Step Volume[] 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.
- wait
Fors string[] 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_forhave completed successfully. Ifwait_foris empty, this build step will start when all previous build steps in theBuild.Stepslist have completed successfully.
- name str
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- args List[str]
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 str
Working directory to use when running this step’s container. If this value is a relative path, it is relative to the build’s working directory. If this value is absolute, it may be outside the build’s working directory, in which case the contents of the path may not be persisted across build step executions, unless a
volumefor that path is specified. If the build specifies aRepoSourcewithdirand a step with adir, which specifies an absolute path, theRepoSourcediris ignored for the step’s execution.- entrypoint str
Entrypoint to be used instead of the build step image’s default entrypoint. If unset, the image’s default entrypoint is used
- envs List[str]
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 str
Unique identifier for this build step, used in
wait_forto reference this build step as a dependency.- secret
Envs List[str] 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 str
Time limit for executing this build step. If not defined, the step has no time limit and will be allowed to continue to run until either it completes or the build itself times out.
- timing str
Output only. Stores timing information for executing this build step.
- volumes
List[Trigger
Build Step Volume] 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.
- wait
Fors List[str] 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_forhave completed successfully. Ifwait_foris empty, this build step will start when all previous build steps in theBuild.Stepslist have completed successfully.
TriggerBuildStepVolume
- Name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- Path string
Path at which to mount the volume. Paths must be absolute and cannot conflict with other volume paths on the same build step or with certain reserved volume paths.
- Name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- Path string
Path at which to mount the volume. Paths must be absolute and cannot conflict with other volume paths on the same build step or with certain reserved volume paths.
- name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- path string
Path at which to mount the volume. Paths must be absolute and cannot conflict with other volume paths on the same build step or with certain reserved volume paths.
- name str
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- path str
Path at which to mount the volume. Paths must be absolute and cannot conflict with other volume paths on the same build step or with certain reserved volume paths.
TriggerGithub
- Name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- Owner string
Owner of the repository. For example: The owner for https://github.com/googlecloudplatform/cloud-builders is “googlecloudplatform”.
- Pull
Request TriggerGithub Pull Request Args filter to match changes in pull requests. Specify only one of pullRequest or push. Structure is documented below.
- Push
Trigger
Github Push Args filter to match changes in refs, like branches or tags. Specify only one of pullRequest or push. Structure is documented below.
- Name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- Owner string
Owner of the repository. For example: The owner for https://github.com/googlecloudplatform/cloud-builders is “googlecloudplatform”.
- Pull
Request TriggerGithub Pull Request filter to match changes in pull requests. Specify only one of pullRequest or push. Structure is documented below.
- Push
Trigger
Github Push filter to match changes in refs, like branches or tags. Specify only one of pullRequest or push. Structure is documented below.
- name string
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- owner string
Owner of the repository. For example: The owner for https://github.com/googlecloudplatform/cloud-builders is “googlecloudplatform”.
- pull
Request TriggerGithub Pull Request filter to match changes in pull requests. Specify only one of pullRequest or push. Structure is documented below.
- push
Trigger
Github Push filter to match changes in refs, like branches or tags. Specify only one of pullRequest or push. Structure is documented below.
- name str
Name of the volume to mount. Volume names must be unique per build step and must be valid names for Docker volumes. Each named volume must be used by at least two build steps.
- owner str
Owner of the repository. For example: The owner for https://github.com/googlecloudplatform/cloud-builders is “googlecloudplatform”.
- pull
Request Dict[TriggerGithub Pull Request] filter to match changes in pull requests. Specify only one of pullRequest or push. Structure is documented below.
- push
Dict[Trigger
Github Push] filter to match changes in refs, like branches or tags. Specify only one of pullRequest or push. Structure is documented below.
TriggerGithubPullRequest
- Branch string
Regex of branches to match. Specify only one of branch or tag.
- Comment
Control string Whether to block builds on a “/gcbrun” comment from a repository owner or collaborator.
- Invert
Regex bool When true, only trigger a build if the revision regex does NOT match the git_ref regex.
- Branch string
Regex of branches to match. Specify only one of branch or tag.
- Comment
Control string Whether to block builds on a “/gcbrun” comment from a repository owner or collaborator.
- Invert
Regex bool When true, only trigger a build if the revision regex does NOT match the git_ref regex.
- branch string
Regex of branches to match. Specify only one of branch or tag.
- comment
Control string Whether to block builds on a “/gcbrun” comment from a repository owner or collaborator.
- invert
Regex boolean When true, only trigger a build if the revision regex does NOT match the git_ref regex.
- branch str
Regex of branches to match. Specify only one of branch or tag.
- comment
Control str Whether to block builds on a “/gcbrun” comment from a repository owner or collaborator.
- invert
Regex bool When true, only trigger a build if the revision regex does NOT match the git_ref regex.
TriggerGithubPush
TriggerTriggerTemplate
- Branch
Name string Name of the branch to build. Exactly one a of branch name, tag, or commit SHA must be provided. This field is a regular expression.
- Commit
Sha string Explicit commit SHA to build. Exactly one of a branch name, tag, or commit SHA must be provided.
- Dir string
Working directory to use when running this step’s container. If this value is a relative path, it is relative to the build’s working directory. If this value is absolute, it may be outside the build’s working directory, in which case the contents of the path may not be persisted across build step executions, unless a
volumefor that path is specified. If the build specifies aRepoSourcewithdirand a step with adir, which specifies an absolute path, theRepoSourcediris ignored for the step’s execution.- Invert
Regex bool When true, only trigger a build if the revision regex does NOT match the git_ref regex.
- Project
Id string ID of the project that owns the Cloud Source Repository. If omitted, the project ID requesting the build is assumed.
- Repo
Name string Name of the Cloud Source Repository. If omitted, the name “default” is assumed.
- Tag
Name string Name of the tag to build. Exactly one of a branch name, tag, or commit SHA must be provided. This field is a regular expression.
- Branch
Name string Name of the branch to build. Exactly one a of branch name, tag, or commit SHA must be provided. This field is a regular expression.
- Commit
Sha string Explicit commit SHA to build. Exactly one of a branch name, tag, or commit SHA must be provided.
- Dir string
Working directory to use when running this step’s container. If this value is a relative path, it is relative to the build’s working directory. If this value is absolute, it may be outside the build’s working directory, in which case the contents of the path may not be persisted across build step executions, unless a
volumefor that path is specified. If the build specifies aRepoSourcewithdirand a step with adir, which specifies an absolute path, theRepoSourcediris ignored for the step’s execution.- Invert
Regex bool When true, only trigger a build if the revision regex does NOT match the git_ref regex.
- Project
Id string ID of the project that owns the Cloud Source Repository. If omitted, the project ID requesting the build is assumed.
- Repo
Name string Name of the Cloud Source Repository. If omitted, the name “default” is assumed.
- Tag
Name string Name of the tag to build. Exactly one of a branch name, tag, or commit SHA must be provided. This field is a regular expression.
- branch
Name string Name of the branch to build. Exactly one a of branch name, tag, or commit SHA must be provided. This field is a regular expression.
- commit
Sha string Explicit commit SHA to build. Exactly one of a branch name, tag, or commit SHA must be provided.
- dir string
Working directory to use when running this step’s container. If this value is a relative path, it is relative to the build’s working directory. If this value is absolute, it may be outside the build’s working directory, in which case the contents of the path may not be persisted across build step executions, unless a
volumefor that path is specified. If the build specifies aRepoSourcewithdirand a step with adir, which specifies an absolute path, theRepoSourcediris ignored for the step’s execution.- invert
Regex boolean When true, only trigger a build if the revision regex does NOT match the git_ref regex.
- project
Id string ID of the project that owns the Cloud Source Repository. If omitted, the project ID requesting the build is assumed.
- repo
Name string Name of the Cloud Source Repository. If omitted, the name “default” is assumed.
- tag
Name string Name of the tag to build. Exactly one of a branch name, tag, or commit SHA must be provided. This field is a regular expression.
- branch
Name str Name of the branch to build. Exactly one a of branch name, tag, or commit SHA must be provided. This field is a regular expression.
- commit
Sha str Explicit commit SHA to build. Exactly one of a branch name, tag, or commit SHA must be provided.
- dir str
Working directory to use when running this step’s container. If this value is a relative path, it is relative to the build’s working directory. If this value is absolute, it may be outside the build’s working directory, in which case the contents of the path may not be persisted across build step executions, unless a
volumefor that path is specified. If the build specifies aRepoSourcewithdirand a step with adir, which specifies an absolute path, theRepoSourcediris ignored for the step’s execution.- invert
Regex bool When true, only trigger a build if the revision regex does NOT match the git_ref regex.
- project_
id str ID of the project that owns the Cloud Source Repository. If omitted, the project ID requesting the build is assumed.
- repo
Name str Name of the Cloud Source Repository. If omitted, the name “default” is assumed.
- tag
Name str Name of the tag to build. Exactly one of a branch name, tag, or commit SHA must be provided. This field is a regular expression.
Package Details
- Repository
- https://github.com/pulumi/pulumi-gcp
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
google-betaTerraform Provider.