This release is a pre-release and may not be stable for production use.
proman-workflows
Overview
This project is a task runner to help automate common development tasks for projects using Python.
The goal of this effort is help implement DevSecOps practices consistly with the Software Development Lifecycle (SDLC) without burdening developers.
The objectives for achieving this goal are:
- Enforce use of commit signing
- Introduce QA tools early in development
- SAST, SCA, and DAST integration
- Encapulate processes for seamless integration with CI/CD systems
- Make TUF compliant packages for PyPI
Install
The project can be installed using the following command:
pip install proman-workflows
The above will only install the workflows but not all dependencies. The additional dependencies can be install with:
pip install proman-workflow[all]
Usage
Currently, there are three command line utilities included with this install. This is due to the primary CLI tool being under heavy development.
The workflow-tools command provides direct access to each of integrations
provided by the task runner. It can either be used directory or extended as
a library for additional workflows.
The workflow-setup command
The workflow command is the intended CLI for the task runner but is still
under development. It will allow control of integrated tools through abstracted
phases accessible to a developer. The functionality is still imited at this time.
Setup
Setup a signing key for development:
workflow-tools setup
FAQ
Q: Why should developers use this? A: Coodinating procedures and setup for multiple team members and projects is difficult and error prone. Task runners are purpose built to solve this problem.
Q: Why not include this using project templates? A: Since this is distributed as a library updates and changes can be much more easilly distributed.
Q: Why not use Invocations A: While this project is inspired by Invocations, it does not support a pluggable architecture.
Refereces
Metadata
Release files for proman-workflows 0.1.0a8
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 | |
|---|---|---|---|---|
| proman-workflows-0.1.0a8.tar.gz | 104.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| proman_workflows-0.1.0a8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 281.7 kB
Release files / proman-workflows-0.1.0a8.tar.gz
| Download URL | proman-workflows-0.1.0a8.tar.gz |
|---|---|
| Size | 104.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c1fdfafed34c60f6ab63ebcf62410cd516aa2edd967804cab0d0dc0bb193bd13
|
|
BLAKE2b-256 checksum How to use checksums |
b4eef9ad44051157b3555b5ec4b28eee329e8392869a43d3b13f05fdad44cef9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.13 CPython/3.10.4 Linux/5.16.18-200.fc35.x86_64
|
Release files / proman_workflows-0.1.0a8-py3-none-any.whl
| Download URL | proman_workflows-0.1.0a8-py3-none-any.whl |
|---|---|
| Size | 177.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
04c55e8289366c66121542443b1dd8934274664fe9bd79e46fea0403a4e397e5
|
|
BLAKE2b-256 checksum How to use checksums |
9098f8631dada7f67d309089590603f7a78c0d91d33455c6180992c617d5a66e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.13 CPython/3.10.4 Linux/5.16.18-200.fc35.x86_64
|
Security for proman-workflows 0.1.0a8
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.