While a HTTP triggered API is nice that returns a HTTP response, as a developer I would like to output some other stuff to db tables, queues, event hubs and what not automatically when I finish running of my function.
Similair to #83 (Function Inputs), we need an abstraction on outputs.
While a HTTP triggered API is nice that returns a HTTP response, as a developer I would like to output some other stuff to db tables, queues, event hubs and what not automatically when I finish running of my function.
Similair to #83 (Function Inputs), we need an abstraction on outputs.
Ideas:
First solution:
hedge.edn
handler signature change example:
Notes:
{:out1 (atom nil) :out2 (atom nil)}
. Keys correspond the:key
names defined in hedge.edn"message"
or["message1" "message2"]
Todo first solution: