lintipy
AWS Lambda handlers for GitHub events wrapped in SNS messages.
How it works
The services is designed following event-driven architecture. It is solely based upon AWS services. Namely AWS Lambda as event consumers and emitters as well as consumers and AWS SNS as channels.
The exchange of events between AWS and GitHub is done using CRUD HTTP methods. Events coming from GitHub are transferred to SNS using a small API Gateway service called github-webhook-lambda. This part is not displayed in the sequence diagram above. Essentially each event coming from GitHub forwarded to a SNS. The topic of the SNS event is the same as the GitHub event type.
Note that the check suite does not interact directly with the check runs nor via SNS. We rely on GitHub to trigger the correct events. This means that initial running of a check or rerunning it using the GitHub interface are treated identically.
Usage
from lintipy import CheckRun
handle = CheckRun.as_handler('PEP8', 'pycodestyle', '.')
See also:
This package is used on FussyFox
Metadata
Release files for lintipy 1.4.4
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 |
|---|---|---|---|---|
| lintipy-1.4.4.tar.gz | 11.7 kB | Without provenance | Details for lintipy-1.4.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lintipy-1.4.4-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for lintipy-1.4.4-py2.py3-none-any.whl |
Total release size: 21.1 kB
Release files / lintipy-1.4.4.tar.gz
| Download URL | lintipy-1.4.4.tar.gz |
|---|---|
| Size | 11.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6600ee38d70f1d09a8bcfa988dde3fc094628f7d411f33b9eeb8fd64b266fa5d
|
|
BLAKE2b-256 checksum How to use checksums |
beead9bf0af3c8c47b1e9ef7df2c07e3a0443c593cc179471823f546a53fd626
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.1.1 requests-toolbelt/0.9.1 tqdm/4.55.1 CPython/3.9.1
|
Release files / lintipy-1.4.4-py2.py3-none-any.whl
| Download URL | lintipy-1.4.4-py2.py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
470331daed129cea4d16e4bb52ea7976aa97d684dac6dbbd7ae3e5fd63de6455
|
|
BLAKE2b-256 checksum How to use checksums |
757760f7bdf4f69c716289785223fd76836a689d3ab9846cd1a322452ec68581
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.1.1 requests-toolbelt/0.9.1 tqdm/4.55.1 CPython/3.9.1
|
Security for lintipy 1.4.4
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.