Open bgelens opened 5 years ago
@fabiocav and @paulbatum - I know we have been talking about this internally, is there already a GitHub issue already tracking this?
@mhoeger Off the top of my head, I'm not aware of one. So for now I suggest we keep this issue open tracking this feature request.
Hi team, just adding support for this request. I see it's been on the backlog for 4 years now, but it would be great if it could be prioritised - extensions like SQL Bindings would benefit greatly from imperative binding for other supported languages, due to significant limitations with having input bindings triggered automatically when the function endpoint is called.
Related issues - https://github.com/Azure/azure-functions-sql-extension/issues/605 https://github.com/Azure/azure-functions-sql-extension/issues/1086
@mhoeger - any update perhaps?
What problem would the feature you're requesting solve? Please describe.
I started using Azure Functions with v2 and PowerShell as the language. Since PowerShell is so flexible, I thought imperative bindings would be logical to be used in our project over declarative bindings. Luckily there is a lot of flexibility in the function.json so I'm not blocked but still there is somewhat of a disconnect between the bindings and the PowerShell process.
Describe the solution you'd like
I'd like imperative bindings to be available in out of process languages (for me PowerShell)
Describe alternatives you've considered
Right now I'm using json body in requests to define which queue a message should be send to. This puts backend logic on the front-end which is what we would like to avoid.
Additional context
This issue is a follow up on an issue addressed at the PowerShell worker.