dgraph-lambda-go
dgraph-lambda-go copied to clipboard
Schartey
I'm trying to invoke the WASM generator, but failing. ```lambda.yaml ... server: mode: wasm_only # wasm_only, server (if wasm language not defined, will generate a pure golang server) ``` The...
I'm not entirely sure how to debug this one, but it seems to be crashing in this call in `./internal/packages.go` defaultPackage, err := config.Packages.Load(defaultModelPath) I noticed that if the `lambda`...
The tool still requires the `ID` fields, even though the object is an interface and not a type. This is a bug in the tool and also makes the tool...
I'm currently actively working on bringing WASM to DGraph Lambda. You can read about it [here](https://discuss.dgraph.io/t/develop-lambdas-with-any-programming-language/16257/21). With the next version of DGraph-Lambda-Go, creating embedded as well as external lambdas with...
Calling generate will remove all custom code and comments outside from generated functions in generated resolvers. These need to be copied over to the new resolver.
We can parse the Authorization information from the schema just like DGraph does. So we can provide an authentication middleware from the start.
DGraph Cloud does not support custom lambda servers. Add a config flag for generating forwarders in JavaScript that forward the lambda requests on DGraph Cloud to the custom lambda server....