Welcome to aws_codecommit Documentation
aws_codecommit aim to extract more potential from AWS CodeCommit. aws_codecommit library is the foundation to bring GitHub Action Trigger, CircleCI Workflow Trigger, Jenkins Multi branch trigger, GitLab Pipeline Trigger into AWS CodeCommit, and give you the flexibility to create more advanced custom trigger.
I created one-click deployable, extentible CI/CD solution using AWS CodeCommit and AWS CodeBuild on top of aws_codecommit.
Features:
better codecommit boto API
Install
aws_codecommit is released on PyPI, so all you need is:
$ pip install aws_codecommit
To upgrade to latest version:
$ pip install --upgrade aws_codecommit
Metadata
Release files for aws-codecommit 1.4.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 |
|---|---|---|---|---|
| aws_codecommit-1.4.1.tar.gz | 20.3 kB | Without provenance | Details for aws_codecommit-1.4.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aws_codecommit-1.4.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for aws_codecommit-1.4.1-py2.py3-none-any.whl |
Total release size: 42.2 kB
Release files / aws_codecommit-1.4.1.tar.gz
| Download URL | aws_codecommit-1.4.1.tar.gz |
|---|---|
| Size | 20.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eed24e8f2ff8dfffe67ef3b164a9431ebafddc4935641a527549d03ea714a7e4
|
|
BLAKE2b-256 checksum How to use checksums |
6c7c88e2be487f796f0a35c182cbd72c6461930506a56e92a99ab9865e19eda3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.11
|
Release files / aws_codecommit-1.4.1-py2.py3-none-any.whl
| Download URL | aws_codecommit-1.4.1-py2.py3-none-any.whl |
|---|---|
| Size | 21.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
bbb7e1f97aa457e9ffaf07bea34a54a437339e18e545a7862ca012dbe0ef598e
|
|
BLAKE2b-256 checksum How to use checksums |
74de7f188785ca37bd9cdcc1a7a85a46e8d77eece5e7d7bffef13d9cae040e71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.11
|
Security for aws-codecommit 1.4.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.