tobiipro / aws-lambda-proxy Goto Github PK

from bunyan

along with simulating the getRemainingTimeInMillis
github.com/tobiipro/aws-lambda-proxy/blob/bb8016e/src/express-app.js#L83

https://github.com/tobiipro/aws-lambda-proxy/blob/master/src/handlers/local.js#L22 and https://github.com/tobiipro/aws-util-firecloud/blob/master/src/lambda/env-ctx.js#L127 makes it impossible to override lambda's env vars e.g. LOG_LEVEL

for the time being, I reckon that it is by design (lambda's env vars should not be overridden; otherwise the logic becomes even more complicated and error prone).
if it's not by design, we might want to allow this

cc @tobiiasl @IanSavchenko

to be http-agnostic and allow debugging any lambda triggered by any service

gist of v1 UX:

$ aws-lambda-proxy \
  --function-name <value> \
  --ip <value> \
  --port <value> \
  [--listen | --no-listen]

$ cd path/to/aws/lambda/code
$ aws-lambda-proxy-listen \
  --runtime <value> \
  --ip <value> \
  --port <value> \

at this point all calls to your lambda inside the AWS walls will proxy everythint (event, context, process.env, smth else?) to your local server started by aws-lambda-proxy-listen that will call the main function on each request

v1 can be as simple as that, supporting nodejs only. future versions could

• integrate with ngrok, in order to bypass NATs
• implement a unique auth token so that the local server cannot be called without it
• assume lambda roles, in order to simulate even closer the lambda runtime constraints
• ?

// cc @tobiiasl

• readme/docs needed
• example based on atex-platform

Now fails badly with bluebird error.