Travis Reeder
Travis Reeder
Or share the repo you have.
We'll probably have to do the initial upload though so we can own chocolatey package name if you don't mind?
Is this only for async functions? We named them call_id in reference to a "functions calls", not sure we should have task_id and call_id.
The main thing that bugs me about this is having different names for essentially the same thing. We should choose one or the other across the board.
I believe @rdallman has something like this for IronWorker, we could probably make use of the same code here.
hi @savaki , did you see the diagram here? https://github.com/iron-io/functions/blob/master/docs/operating/production.md Lifecycle diagram would be a good idea.
I don't see why we couldn't allow this via a port, could be an option. But I think long term (few months), people would typically use a wrapper lib to...
fnlb needs a lot of work still... Saw your test harness for it, nice work. #573
Are you trying to build int the root dir of the `iron-io/functions` repo? Make a fresh new directory and with nothing in it and start there.