EventGrid Based Storage Triggers
- Dominant language
- PowerShell
- Stars
- 1.1k
- Forks
- 215
- Avg merge
- 4h 2m
- Merged PRs (30d)
- 1
Description
We have a trigger defined like so, and it works in the Azure Functions in App Service.
```
"bindings": [
{
"name": "myBlob",
"type": "blobTrigger",
"direction": "in",
"path": "log/{customerID}/{unitID}/{fileName}",
"dataType": "binary",
"source": "EventGrid",
"connection": "AzureLogFileStorage"
},
// ...
}
```
We are having trouble migrating JUST this ONE EventGrid-based trigger. I can get the new blob event posted to the Azure Functions Runtime container in AKS, but there is nothing listening for it at the path that works in the Azure Functions instance (/runtime/webhooks/blobs). I am trying to figure out what Functions service normally handles that URL path as I am seeing a 404 from the Functions Runtime container. The doc on the net is tantalizing but sketchy. It sounds like a few people have gotten this to work, but they have not provided detailed instructions on how to duplicate the feat.
Can anyone provide any details on making this setup work? Thanks in advance!
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.