Skip to main content

A cli that implements a gitlab git server side pre-receive hook that gets driven from dynamodb and reports to slack offending pushes.

Development Workflow

The workflow supports the following steps

  • lint

  • test

  • build

  • document

  • upload

  • graph

These actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices. Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.

The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that. It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the project

Once the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme. So for the initial delivery one would call

$ _tag –minor

which would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.

So the full workflow after git is initialized is:

  • repeat as necessary (of course it could be test - code - lint :) )

    • code

    • lint

    • test

  • commit and push

  • develop more through the code-lint-test cycle

  • tag (with the appropriate argument)

  • build

  • upload (if you want to host your package in pypi)

  • document (of course this could be run at any point)

Important Information

This template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed. So when building a package out of this do not simple call

$ python setup.py sdist bdist_egg

as this will produce an unusable artifact with files missing. Instead use the provided build and upload scripts that create all the necessary files in the artifact.

Project Features

Can protect directories and files from tampering by checking hash entries for them in a dynamodb Please refer to USAGE.rst for setup details.

History

0.0.1 (26-02-2019)

  • First code creation

0.1.0 (26-02-2019)

  • First public release

0.1.1 (29-09-2020)

  • Updated quaratine path logic

0.1.2 (02-10-2020)

  • Fix for get_project method

0.1.3 (02-10-2020)

  • Fixed project_group name logic

0.2.0 (16-10-2020)

  • Implemented web identity authentication.

0.2.1 (16-10-2020)

  • Bumped dependencies

1.0.0 (30-12-2020)

  • Replace hyphens with underscores in all project names for dynamo lookup.

1.0.1 (07-01-2021)

  • Made error message friendlier.

1.0.2 (09-03-2021)

  • Explicitly targeting the copy git repo for the latest gitlab.

1.1.0 (16-03-2021)

  • Implemented archive instead of checkout as checkout corrupted repositories in Gitlab after 13.8 and the exposure of GIT_DIR environment variable.

1.1.1 (22-03-2021)

  • Handling special 00000 ref case by not handling it.

1.1.2 (26-04-2021)

  • Bumped dependencies.

1.1.3 (08-06-2021)

  • Bumped dependencies.

Metadata

Release files for prereceivecli 1.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for prereceivecli 1.1.3
File Size Uploaded Provenance
prereceivecli-1.1.3.tar.gz 58.0 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for prereceivecli 1.1.3
File Interpreter ABI Platform
prereceivecli-1.1.3-py3.7.egg Legacy Egg format - - Details

Total release size: 118.0 kB

Release files / prereceivecli-1.1.3.tar.gz

Download URL prereceivecli-1.1.3.tar.gz
Size 58.0 kB
Tags Source
SHA-256 checksum
How to use checksums
bfd746fd299e26d499ad8cdcdad44d383b7e138eb1e4658a894216743b091f25
BLAKE2b-256 checksum
How to use checksums
fd9a32edf271acb4c83fd332a451d6df3499889e2150a43df382ed2463842234
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.7.0 requests/2.21.0 setuptools/57.0.0 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.7.10

Release files / prereceivecli-1.1.3-py3.7.egg

Download URL prereceivecli-1.1.3-py3.7.egg
Size 60.0 kB
Tags Egg
SHA-256 checksum
How to use checksums
361bcfab40dbb980b5b9a4c096969e2f359be993e94d43dafafec93f4cec7450
BLAKE2b-256 checksum
How to use checksums
78f6d435a053b96573f6973ff8654f6198bb1f4dcb908b6e5d9a24023a896235
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.7.0 requests/2.21.0 setuptools/57.0.0 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.7.10

Security for prereceivecli 1.1.3

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page