Trigger

A project-specific mapping between an event-type (provided by a connection) and an entry-point function (implemented in a specific file in the project's code).

Formal Definition

Let AutoKitteh have a configured project $(P)$, and:

• $P$ has a configured connection $(C_p)$
  • $C_p$ provides a certain event-type $(E_c)$
• $P$ implements a certain function $(F_p)$ in its code
• $P$ has a configured trigger $(T_{ef})$ between $E_c$ and $F_p$
• $P$ has an active deployment $(D_p)$

Whenever $C_p$ receives an instance of $E_c$, the AutoKitteh server will:

• Dispatch $E_c$ to $D_p$
  • Start a runtime session $(S_{def})$ that executes $F_p$

note

Connections may be reused by multiple projects, and event-types may be significant to multiple projects. In other words, any event may be a trigger for multiple entry-point functions.

Therefore, the AutoKitteh dispatcher supports a "fan-out" behavior, to distribute each event to multiple consumers simultaneously, if needed.

Configuration Details

Field	Type	Description
connection	String	Connection name
event_type	String	Provided by the integration that the connection is an instance of
entrypoint	String	Format: file_name:function_name

YAML Manifest Examples

triggers:
  - connection: my_github_connection
    event_type: pull_request
    entrypoint: program.star:on_github_pull_request
  - connection: my_http_connection
    event_type: get
    entrypoint: program.star:on_http_get