-
Notifications
You must be signed in to change notification settings - Fork 51
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
Push-OutputBinding Should Throw Exceptions at Script Scope #284
Comments
So this is not possible currently because there's no way to communicate with the worker while the operation is still ongoing, output bindings are all sent at once after the function is completed. azure-functions-powershell-worker/src/RequestProcessor.cs Lines 446 to 478 in d08886b
Hence this is blocking on the worker protocol having a proactive outputbinding RPC function. I created an issue for this and this issue will be blocking on this being completed. |
Is there any progress on this? It's impossible to implement proper HTTP error codes for functions without this being fixed. As there is also no functionality to choose an insert mode for table storage, it's impossible to return e.g. a 409 when the entity already exists. |
@itpropro theres an upstream dependency here that has to be implemented: Azure/azure-functions-language-worker-protobuf#47 I saw no comments on my request so I assume it's not a priority. |
Tried pushing an output binding to a table today, and it errored with the following:
Unfortunately I can't try/catch or trap{} it, so my script just dies. As a workaround I just fetch a table object directly, but I shouldn't have to, I should be able to follow the output binding pattern and practice, but be able to handle any issues that might crop up.
The text was updated successfully, but these errors were encountered: