Google Functions with YAML

YAML parameters for Google Functions

NameTypeDescription
function_name
Required		StringThe name of the Google function.
integration_id
Required		IntegerThe ID of the integration.
trigger_time __
Required		StringSpecifies when the action should be executed. Can be one of ON_EVERY_EXECUTION, ON_FAILURE or ON_BACK_TO_SUCCESS.
application_id __
Required		StringThe id of the Google Cloud project.
type
Required		StringThe type of the action. Should be set to GOOGLE_FUNCTIONS.
payloadStringThe JSON that will be provided as input to the Google function.
trigger_conditionStringDefines when the build action should be run. Can be one of ALWAYS, ON_CHANGE, ON_CHANGE_AT_PATH, VAR_IS, VAR_IS_NOT or VAR_CONTAINS.
trigger_condition_pathsString[]Required when trigger_condition is set to ON_CHANGE_AT_PATH.
trigger_variable_keyStringRequired when trigger_condition is set to VAR_IS, VAR_IS_NOT or VAR_CONTAINS. Defines the name of the desired variable.
trigger_variable_valueStringRequired when trigger_condition is set to VAR_IS, VAR_IS_NOT or VAR_CONTAINS. Defines the value of the desired variable which will be compared with its current value.
disabledBooleanWhen set to true the action is disabled. By default it is set to false.

YAML example for Google Functions

actions:
  - action: "Invoke function hello-world"
    type: "GOOGLE_FUNCTIONS"
    integration_id: 1
    application_id: "prime-team-855"
    function_name: "projects/tokyo-house-138923/locations/us-central1/functions/buddy-function"
    payload: "{\r\n    \"message\": \"$BUDDY_EXECUTION_COMMENT\"\r\n}"
Questions?

Not sure how to configure a pipeline for your process? Reach out on the live-chat, contact support, or ask our community on our forum.

Sign up for Buddy Digest

Best practices on CI/CD and fresh changelogs delivered weekly to your inbox.