Enable our lambda wrapper to support IronFunctions

[treeder]

Maybe check PAYLOAD_FILE to support worker, then read STDIN if it doesn't exist.

• [x] Add STDIN support to iron-io/lambda
• [x] Add some documentation to this repo for how to use it

cc @nikhilm

[nikhilm]

Yes, adding reading from stdin support sounds like a good idea.

On Sat, Oct 15, 2016 at 2:43 PM, Travis Reeder notifications@github.com wrote:

Maybe check PAYLOAD_FILE to support worker, then read STDIN if it doesn't exist.

• Add STDIN support to iron-io/lambda
• Add some documentation to this repo for how to use it

cc @nikhilm https://github.com/nikhilm

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iron-io/functions/issues/179, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEzWkhH8C_-_zA4DfpbtJ8pnfwv7jdQks5q0UjmgaJpZM4KX0pQ .

[nikhilm]

iron-io/lambda#61

[nikhilm]

Those images just expect a JSON blob in the style of AWS Lambda to be sent in via stdin. If the API gateway does that, not sure what else is to be documented.

[treeder]

There's no documentation in here how to use this. Let's make a docs/lambda.md and put a lambda quickstart in there.

@rdallman should use your new cli tool for that doc.

[nikhilm]

How does functions discriminate between 200 and other status codes? Right now our lambda wrappers only print out direct output from console.log() and so on. How would they inter-op with this?

[ucirello]

@seiflotfy are we done with this?

[seiflotfy]

missing https://github.com/iron-io/functions/pull/264