Skip to content

Conversation

@negillett
Copy link
Member

Environment variables are not supported by Lambda@Edge, so replace their
usage with a configuration file. A JSON format file was chosen to
prevent additional dependencies.

Also, the transformed URI is now prepended with a forward-slash, "/", to
correct the path to the file object.

Tests were updated to reflect these changes.

Fixes #8, fixes #10

@negillett negillett requested a review from rohanpm as a code owner February 20, 2020 21:34
@negillett negillett force-pushed the fix_map_to_s3_config branch 2 times, most recently from 840476f to e492fb0 Compare February 20, 2020 22:05
Environment variables are not supported by Lambda@Edge, so replace their
usage with a configuration file. A JSON format file was chosen to
prevent additional dependencies.

Also, the transformed URI is now prepended with a forward-slash, "/", to
correct the path to the file object.

Tests were updated to reflect these changes.

Fixes #8, fixes #10
@negillett negillett force-pushed the fix_map_to_s3_config branch from e492fb0 to 0647dd2 Compare February 20, 2020 22:16
This commit moves the lambda function into a class so that objects can
be reused if multiple events are received while the AWS Lambda
container is still active.
@negillett negillett requested a review from rohanpm February 25, 2020 00:42
This commit includes some touch-ups to in-line comments and log
messages, moves some variables, and cleans up a couple of leftover
print functions used in development.
@negillett negillett requested a review from rohanpm February 25, 2020 13:31
@negillett
Copy link
Member Author

Will go ahead with merge, as new changes are minor.

@negillett negillett merged commit e574806 into release-engineering:master Feb 25, 2020
@negillett negillett deleted the fix_map_to_s3_config branch February 25, 2020 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

'/' missing from the uri returned to cloudfront map_to_s3 function depends on non-existent enviroment variables

3 participants