Use pre-installed AWS SDK on Lambda

KlaasH commented 6 years ago

Overview

The Lambda environment comes with the AWS SDK pre-installed, so it wastes space in the bundle to install it ourselves.

Also bumps the version listed in package.json (and installed in development) to the current version pre-installed on Lambda

Notes

Per this issue, just moving it to devDependencies won't work because Claudia validates the bundle and it's an error for the package to be missing, but that can be worked around by making at an optional dependency and telling Claudia not to install optional.
This also adds a --no-deps argument to a few of the docker-compose commands in places where the tiler container is being used but the database container (on which it depends via the links: parameter) isn't needed.

Testing Instructions

To test local development, delete node_modules or run scripts/clean to clear the existing installation, then run scripts/update to build the tiler container again. It should still install aws-sdk and work normally.
To test the deployed package, run scripts/publish or scripts/publish --new. Export the Lambda function to a zip file and confirm that aws-sdk is not present in the node_modules directory.
If you already had a Lambda function deployed, you should be able to export the previous version and confirm that the size of the bundle has decreased.

Resolves #118.

mtford90 commented 5 years ago

Is this live yet?

jeancochrane commented 5 years ago

@mtford90 It is in the sense that it's been pulled into develop, which we use as the base branch for the repo. Currently we recommend installing and using the library by cloning the repo with Git, so you should be able to access these changes if you're using it that way.

azavea / tilegarden