community / community.general / 0.1.1 / module / gcp_cloudbuild_trigger_facts Gather info for GCP Trigger Authors: Google Inc. (@googlecloudplatform) preview | supported by communitycommunity.general.gcp_cloudbuild_trigger_facts (0.1.1) — module
Install with ansible-galaxy collection install community.general:==0.1.1
collections: - name: community.general version: 0.1.1
Gather info for GCP Trigger
- name: get info on a trigger gcp_cloudbuild_trigger_info: project: test_project auth_kind: serviceaccount service_account_file: "/tmp/auth.pem"
scopes: description: - Array of scopes to be used type: list project: description: - The Google Cloud Platform project to use. type: str env_type: description: - Specifies which Ansible environment you're running this module within. - This should not be set unless you know what you're doing. - This only alters the User Agent string for any API requests. type: str auth_kind: choices: - application - machineaccount - serviceaccount description: - The type of credential used. required: true type: str service_account_file: description: - The path of a Service Account JSON file if serviceaccount is selected as type. type: path service_account_email: description: - An optional service account email address if machineaccount is selected and the user does not wish to use the default email. type: str service_account_contents: description: - The contents of a Service Account JSON file, either in a dictionary or as a JSON string that represents it. type: jsonarg
resources: contains: build: contains: images: description: - 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. returned: success type: list steps: contains: args: description: - 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. returned: success type: list dir: description: - 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 `volume` for that path is specified. - If the build specifies a `RepoSource` with `dir` and a step with a `dir`, which specifies an absolute path, the `RepoSource` `dir` is ignored for the step's execution. returned: success type: str entrypoint: description: - Entrypoint to be used instead of the build step image's default entrypoint. - If unset, the image's default entrypoint is used . returned: success type: str env: description: - 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". returned: success type: list id: description: - Unique identifier for this build step, used in `wait_for` to reference this build step as a dependency. returned: success type: str name: description: - The name of the container image that will run this particular build step. - If the image is available in the host's Docker daemon's cache, it will be run directly. If not, the host will attempt to pull the image first, using the builder service account's credentials if necessary. - The Docker daemon's cache will already have the latest versions of all of the officially supported build steps (U(https://github.com/GoogleCloudPlatform/cloud-builders)). - The Docker daemon will also have cached many of the layers for some popular images, like "ubuntu", "debian", but they will be refreshed at the time you attempt to use them. - If you built an image in a previous build step, it will be stored in the host's Docker daemon's cache and is available to use as the name for a later build step. returned: success type: str secretEnv: description: - 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`. returned: success type: list timeout: description: - 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. returned: success type: str timing: description: - Output only. Stores timing information for executing this build step. returned: success type: str volumes: contains: name: description: - 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. returned: success type: str path: description: - 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. returned: success type: str description: - 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. returned: success type: complex waitFor: description: - 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. returned: success type: list description: - The operations to be performed on the workspace. returned: success type: complex tags: description: - Tags for annotation of a Build. These are not docker tags. returned: success type: list description: - Contents of the build template. Either a filename or build template must be provided. returned: success type: complex createTime: description: - Time when the trigger was created. returned: success type: str description: description: - Human-readable description of the trigger. returned: success type: str disabled: description: - Whether the trigger is disabled or not. If true, the trigger will never result in a build. returned: success type: bool filename: description: - Path, from the source root, to a file whose contents is used for the template. Either a filename or build template must be provided. returned: success type: str id: description: - The unique identifier for the trigger. returned: success type: str ignoredFiles: description: - ignoredFiles and includedFiles are file glob matches using http://godoc/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. returned: success type: list includedFiles: description: - ignoredFiles and includedFiles are file glob matches using http://godoc/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. returned: success type: list name: description: - Name of the trigger. Must be unique within the project. returned: success type: str substitutions: description: - Substitutions data for Build resource. returned: success type: dict triggerTemplate: contains: branchName: description: - 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. returned: success type: str commitSha: description: - Explicit commit SHA to build. Exactly one of a branch name, tag, or commit SHA must be provided. returned: success type: str dir: description: - Directory, relative to the source root, in which to run the build. - This must be a relative path. If a step's dir is specified and is an absolute path, this value is ignored for that step's execution. returned: success type: str projectId: description: - ID of the project that owns the Cloud Source Repository. If omitted, the project ID requesting the build is assumed. returned: success type: str repoName: description: - Name of the Cloud Source Repository. If omitted, the name "default" is assumed. returned: success type: str tagName: description: - 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. returned: success type: str description: - 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. returned: success type: complex description: List of resources returned: always type: complex