Overview of Triggers and Bindings
-
A triggers defines how the function is invoked and each function in Azure must have only one trigger.
-
Triggers usually have associated data which is payload that triggers the function
-
Different types of Triggers
- BlobTrigger: This trigger gets fired when new blob or blob update is detected
- QueueTrigger: This triggers gets fired when a new message arrives the Azure Storage Queue
- EventHubTrigger: This trigger gets fired when any event is delivered to the Azure Event Hub Service
- TimerTrigger: This trigger is called on Schedule basic. We can set the time to execute the function using this trigger
- HTTPTrigger: This trigger gets fired when the HTTP request arrives
- ServiceBusTrigger: This trigger gets fired when a new message comes into Azure Service Bus topic or queue
- Generic WebHook: This trigger gets fired when a webhook HTTP request comes from any service that supports webhooks
- GitHub WebHook: This trigger gets fired when the following events occur in GitHub Repository
- Create Branch
- Delete Branch
- Issue Comment
- Commit Comment
-
Binding to a function is a way of declaratively connecting another resource to functions.
-
Bindings can be input bindings or output bindings or both
-
Azure Functions 2.0 has the following bindings
- Blob Storage
- CosmosDB
- Event Grid
- Event Hubs
- HTTP & WebHooks
- Queue Storage
- Table Storage
- Service Bus
- Timer
- SendGrid
- SignalR
- Twillo
- Microsoft Graph
-
Bindings are optional in Azure functions and you can have multiple input and output bindings.
-
In Azure Functions, all the bindings must be registered except HTTP and Timer
-
Refer Here for all the supported bindings
