The runtime interface emulator at https://github.com/aws/aws-lambda-runtime-interface-emulator/ is an AWS-provided way to test Lambda Functions locally. It doesn't set all the environment variables set by the "real" environment, and this causes hal to crash when trying to start. The RIE's docs call out the following three variables:
AWS_LAMBDA_FUNCTION_VERSIONAWS_LAMBDA_FUNCTION_NAMEAWS_LAMBDA_FUNCTION_MEMORY_SIZE
There are two more that hal expects to be present:
AWS_LAMBDA_LOG_GROUP_NAMEAWS_LAMBDA_LOG_STREAM_NAME
Would you take a PR to make these fields optional?
The runtime interface emulator at https://github.com/aws/aws-lambda-runtime-interface-emulator/ is an AWS-provided way to test Lambda Functions locally. It doesn't set all the environment variables set by the "real" environment, and this causes
halto crash when trying to start. The RIE's docs call out the following three variables:AWS_LAMBDA_FUNCTION_VERSIONAWS_LAMBDA_FUNCTION_NAMEAWS_LAMBDA_FUNCTION_MEMORY_SIZEThere are two more that
halexpects to be present:AWS_LAMBDA_LOG_GROUP_NAMEAWS_LAMBDA_LOG_STREAM_NAMEWould you take a PR to make these fields optional?