You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While this sample with input and output binding to a queue is a nice start, most of my az fuctions operate on a http trigger basis, so I was wondering on where to set to url in the function metadata. Are HttpTriggers not supported?
Do you have and roadmap on when you will support functions in the C# implementation of the sdk?
The text was updated successfully, but these errors were encountered:
I understand / have learned that at the moment you support only Azure Functions using queues as Actions for Azure AI Agents but was pointing at the fact that many exiting Azure Functions might be using the HttpTrigger template. But I found I workaround. l let GH Copilot generate an OpenAI Definition for those and then add the existing Azure Functions using the OpenApi 3.0 spec tool. So if you want you can close and leave this as a reference for others, but if you want you can also take this as an input
Uh oh!
There was an error while loading. Please reload this page.
While this sample with input and output binding to a queue is a nice start, most of my az fuctions operate on a http trigger basis, so I was wondering on where to set to url in the function metadata. Are HttpTriggers not supported?
Do you have and roadmap on when you will support functions in the C# implementation of the sdk?
The text was updated successfully, but these errors were encountered: