-
Notifications
You must be signed in to change notification settings - Fork 107
Custom binding error #408
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
Labels
Comments
@asavaritayal #66 laid the foundation for the unstructured bindings, but we didn't explicitly enable support for arbitrary binding types, only the bindings that are supported (registered) otherwise. If generic support for arbitrary bindings is desired, I can make a PR to enable this behavior. |
maiqbal11
pushed a commit
that referenced
this issue
Jul 1, 2019
* Allow arbitrary bindings with elementary dataType Add a generic binding implementation to allow unknown bindings with `dataType: string` and `dataType: binary`. Fixes: #66 Fixes: #408 * Add support for untyped queue trigger binding * Support unannotated elementary bindings * Decouple rich binding support from the worker Per discussion, the worker no longer includes support for rich bindings by default. The implementation have been moved to azure-functions-python-library, and the runtime dependency on is has been removed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I created an HTTP triggered function with an output binding of type Azure Table Storage. Here is the
function.json
definition:I see the following error when trying to run locally:
I expected this to work since the issue here - #66 has been closed.
The text was updated successfully, but these errors were encountered: