SINCE VERSION 1.0
A Pipeline Trigger or just Trigger is an action which causes a persisted pipeline to be executed.
These triggers are the common ones in PIPEFORCE:
See https://logabit.atlassian.net/wiki/spaces/PA/pages/2544795677 for more details.
Triggers a pipeline as a job which must be executed after a certain amount of time.
See https://logabit.atlassian.net/wiki/spaces/PA/pages/2545320123 for more details.
Triggers a pipeline in case a message of interest is on the message queue / bus.
See https://logabit.atlassian.net/wiki/spaces/PA/pages/2545287223 for more details.
Triggers a pipeline in case an internal event of interest has occured. Events are quite similar to messages, except that their origin is always the hub backend.
Common event examples are:
property.created = A new property has been created in the https://logabit.atlassian.net/wiki/spaces/PA/pages/2545451009.
property.deleted = A new property has been deleted from the https://logabit.atlassian.net/wiki/spaces/PA/pages/2545451009.
iam.bruteforce.detected = A potential brute force attack has been detected.
See https://logabit.atlassian.net/wiki/spaces/PA/pages/2545287270 for more details.
Triggers a pipeline in case an external system sends a request to one of the custom webhook endpoints.
See https://logabit.atlassian.net/wiki/spaces/PA/pages/2547089621 for more details.
Triggers a pipeline in case a HTTP request to an API Gateway endpoint was made which in term is linked to a pipeline.
See https://logabit.atlassian.net/wiki/spaces/PA/pages/2542862901 for more details..
Triggers a pipeline in case a HTTP POST request to the endpoint /api/v3/pipeline was done.