Before starting to implement your custom trigger, is important to understand what the classes involved in the trigger pipeline are and what their responsibility is in that pipeline:
- TriggerConfigProvider: This implements the IExtensionConfigProvider interface and it has the responsibility of configuring the entire trigger process in terms of:
- The attribute that defines the trigger
- The payload associated with the trigger (for example, the HTTP request for HttpTrigger)
- The actual binding provider class to use to create the actual binding object
- TriggerAttribute: This is used to decorate a method parameter to identify the function trigger. It inherits from Attribute and is decorated by BindingAttribute. It has the responsibility of containing the trigger data (for example, the schedule expression for TimerTrigger).
- TriggerBindingProvider: This implements...