Zappa is a tool wrap the deployment of serverless applications to AWS Lambda, you can invoke your function with AWS APIGatway using curl easily. For some use cases you would like to avoid opening your function to APIGateway and to call your function directly. there are many steps implemented by zappa which makes it difficult, this package is a wrapper to save you that pain.
Metadata
Release files for zappa-client 0.0.1
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 |
|---|---|---|---|---|
| zappa_client-0.0.1.tar.gz | 1.3 kB | Without provenance | Details for zappa_client-0.0.1.tar.gz |
Release files / zappa_client-0.0.1.tar.gz
| Download URL | zappa_client-0.0.1.tar.gz |
|---|---|
| Size | 1.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ee2091cce0a44dfd496b0fe69d86ed809d7e8efaa41ab6dac16a005aa9ae14a
|
|
BLAKE2b-256 checksum How to use checksums |
bc9b195a82e106a5e24c4ccc81324dddb59ed887bfd323225340b4ad4b81617a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zappa-client 0.0.1
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.