-
Notifications
You must be signed in to change notification settings - Fork 6
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
Support PostgreSQL Binding #24
Comments
It's a valid point regarding the PostgreSQL binding requirements. Currently, the ff-python framework already supports exposing the Dapr client to users. If you are interested in having the same functionality in ff-go, we would greatly appreciate your contributions to develop this feature. |
Hi @tpiperatgod, I've gone ahead and created a PR in the ff-go repo (mentioned above). However I am incurring some issues with the function builder. Namely that it does not respect the |
Hi @Mershab99 , for information on how to make ff-go builder image, see this doc. Please feel free to give suggestions to enhance the documentation! |
Closing this issue as OpenFunction/functions-framework-go#78 has been merged which addresses this concern. Thanks all for your help! |
The postgres binding uses the
exec
andquery
operations, and invokes the binding with the SQL command embedded in themetadata
field of thedapr.InvokeBindingRequest
. However the currentctx.Send
method only fills thedata
field. This is insufficient for the postgres binding.https://docs.dapr.io/reference/components-reference/supported-bindings/postgresql/
Alternatively exposing the daprClient as part of the
FunctionContext
would allow users to access the underlying dapr client and invoke our own methods beyond the scope of the OF spec.The text was updated successfully, but these errors were encountered: