lambdev

A simple interface wrapped around a boto3 lambda client, lambdev simplifies testing, deploying, and versioning AWS lambda functions from your local development environment.
Installation
pip install lambdev
Configuration
AWS credentials
Please refer to the boto3
documentation on configuring your aws credentials. Best option when working with lambdev is to store your credentials
(AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY) and region (AWS_DEFAULT_REGION) as environment variables.
create .lambdevignore.txt
create a file called .lambdevignore.txt where you can list the names of files and directories that are in your project folder
that you would like to exclude from your lambda function deployment package.
for example:
env
test.py
build.sh
function_name.txt
All hidden files (names that start with .) are
ignored by default (ie .gitignore) and do not need to be added to the ignore file.
Usage
simply run the lambdev functions from the root directory of your AWS lambda function project folder.
Available functions:
lambdev.create()- creates a new lambda function by uploading a deployment package from the non-ignored files in the working directory.
Saves new function ARN in
$WORKINGDIR/function_name.txt.
- creates a new lambda function by uploading a deployment package from the non-ignored files in the working directory.
Saves new function ARN in
lambdev.test()- uploads non-ignored code in working dir to lambda function
$latestchannel, invokes it, and returns log.
- uploads non-ignored code in working dir to lambda function
lambdev.publish()- publishes code in
$latestand updates input alias to point to new version.
- publishes code in
Examples
Example files can be found here
Metadata
Release files for lambdev 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| lambdev-0.1.2.tar.gz | 4.0 kB | Without provenance | Details for lambdev-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lambdev-0.1.2-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for lambdev-0.1.2-py2.py3-none-any.whl |
Total release size: 9.3 kB
Release files / lambdev-0.1.2.tar.gz
| Download URL | lambdev-0.1.2.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9bd2964a653b39b3c980aa43f7f4711f03a3fd4f3cacc9fb8dbe4b9e276a4c2f
|
|
BLAKE2b-256 checksum How to use checksums |
70ed3085e8c41e7a671a3f13de028e8264c293c5bfa6f013bf98155456fad69e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.7.3 requests-toolbelt/0.9.1 tqdm/4.30.0 CPython/3.6.3
|
Release files / lambdev-0.1.2-py2.py3-none-any.whl
| Download URL | lambdev-0.1.2-py2.py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
dcbf2ab17750d8f454e138d93af1eff2048de51ebb7a125a8c3238b4b5169662
|
|
BLAKE2b-256 checksum How to use checksums |
073a82254ea599fc5b0b3d62b377e878d25f33c090b50169bee16829734ad2c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.7.3 requests-toolbelt/0.9.1 tqdm/4.30.0 CPython/3.6.3
|
Security for lambdev 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.