-
Notifications
You must be signed in to change notification settings - Fork 442
function.json
Mathew Charles edited this page Nov 17, 2015
·
29 revisions
In a script function directory, there should be a companion function.json file that contains the configuration metadata for the function. Below are examples for each of the trigger types.
QueueTrigger Example:
{
"trigger": {
"type": "queue",
"queueName": "samples-workitems"
}
BlobTrigger Example:
{
"trigger": {
"type": "blob",
"blobPath": "samples-workitems"
}
}
TimerTrigger Example:
{
"trigger": {
"type": "timer",
"schedule": "*/10 * * * * *",
"runOnStartup": true
}
}
WebHookTrigger Example:
{
"trigger": {
"type": "webHook"
}
}
ServiceBusTrigger Example (Queue):
{
"trigger": {
"type": "serviceBus",
"queueName": "samples-workitems"
}
}
ServiceBusTrigger Example (Topic):
{
"trigger": {
"type": "serviceBus",
"topicName": "samples-topic",
"subscriptionName": "samples-subscription"
}
}
- Configuration Settings
- function.json
- host.json
- host.json (v2)
- Http Functions
- Function Runtime Versioning
- Official Functions developers guide
- Host Health Monitor
- Managing Connections
- Renaming a Function
- Retrieving information about the currently running function
- Site Extension Resolution
- Linux Consumption Regions
- Using LinuxFxVersion for Linux Function apps
- Out-of-proc Cancellation Tokens
- Assembly Resolution in Azure Functions
- ILogger
- Precompiled functions
- Official Functions C# developer reference
- Contributor Onboarding
- Development Process
- Deploying the Functions runtime as a private site extension
- Authoring & Testing Language Extensions
- Bindings in out-of-proc
- Language Extensibility
- Worker Capabilities
- Investigating and reporting issues with timer triggered functions not firing
- Sharing Your Function App name privately
- Azure Functions CLI release notes [moved here]
- Function App Zipped Deployment [deprecated]