Lambda-uploader

Latest version: v1.3.0

Safety actively analyzes 629639 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 3

1.0.0

-----
- Warn if the lambda package is over the current AWS max size of 50MB
- Add --extra-file flag for adding arbitrary file(s) outside of the
project directory.
- Add --requirements flag to allow setting a requirements file as a CLI
option
- Updated the Package() object so only the build() method actually needs
to be called.
- Updated the Package() constructor and removed most of the allowed
variables in favor of calling setter methods.
- Add -c shorthand to the --config flag
- Fixed the ignores to match against paths relative to the source dir
- Added support for placing your lambda functions in specific VPC
subnets and security groups

0.5.1

-----
- Set hard Python requirements on 2.7
- Fixed issue with lambda-uploader only looking for requirements.txt in the cwd

0.5.0

-----
- Added optional zip file name to package class(API only)
- Updated boto3 version to 1.2.2

0.4.0

-----
- Added support for ignoring files
- Added the ability to use an existing virtual environment
- Fixed the temporary workspace name to prevent confusion
- Updated the virtualenv site-packages copy to include lib64 if it
is not a symlink
- Add --no-virtualenv flag and set the default behavior to no longer create
a virtual environment unless package requirements are found

0.3.0

-----
- Added flag to allow specifying the lambda.json path
- Added a role flag and environment variable to use in lieu of setting
it in the config

0.2.2

-----
- Fixed issue with multiple requirements set in the config causing
an error

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.