Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EventGrid Based Storage Triggers #2583

Open
derekrprice opened this issue Feb 27, 2025 · 0 comments
Open

EventGrid Based Storage Triggers #2583

derekrprice opened this issue Feb 27, 2025 · 0 comments

Comments

@derekrprice
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant