-
Notifications
You must be signed in to change notification settings - Fork 3
About Pipelines
DaAPI is shipped with a built-in notification pipeline. This component intends to interact with other systems easily.
A pipeline consists of three different elements: Trigger, Condition, and Actor.
In the current version, this system is built to serve a particular use case. In the upcoming releases, we will include many more Triggers, Conditions, and Actors to make this feature more useful for many different use cases.
A trigger can be understood as the source of an event, the reason. It can be an update of a lease, the filtering of a packet, or that a scope has no free addresses anymore. The occurrence of a trigger is the start of each pipeline.
Each Trigger, can carry details about the event like information on the lease, the scope, etc. This information is available in Conditions and Actors.
A Condition is the second stage of a pipeline. The purpose of a condition is to decide if the Trigger with its specific information is eligible to fire an Actor.
Maybe, not each scope should send an alert if their address space is exhausted. Or not every change of a binding should trigger a static route creation.
Actors are the last part of a pipeline and responsible for executing an action. The type of activity is determinate by the type of Actor, but the specific parameters are based on information from the Trigger.
An actor can execute a script, create a route, or sending a message.