Been using lambda-tester for a while an it's a great experience, so first of thanks for the tool!
Currently Lambda only implements LAMBDA_TASK_ROOT of the Runtime Environment Variables specified here => https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html. It would be great if lambda-tester could inject more (or even all) of the env variables specified in the link above.
For context my current use case is using the aws-iot-device-sdk and the sdk looks for AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY in the Lambda Environment.
Hi!
Been using lambda-tester for a while an it's a great experience, so first of thanks for the tool!
Currently Lambda only implements
LAMBDA_TASK_ROOT
of theRuntime Environment Variables
specified here => https://docs.aws.amazon.com/lambda/latest/dg/configuration-envvars.html. It would be great if lambda-tester could inject more (or even all) of the env variables specified in the link above.For context my current use case is using the
aws-iot-device-sdk
and the sdk looks forAWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
in the Lambda Environment.https://github.com/aws/aws-iot-device-sdk-js#export-variables-to-system-environment,