cdflow - create and manage software services using continuous delivery
This repository contains the cdflow command that you can install on your system (e.g. on your dev machine or CI server) in order to release, deploy and (eventally) decommission software services with ease.
The code here is just a thin wrapper for the cdflow docker image used to ensure you get the latest version when you release (with the option to pin should you need to) and that the image used remains consistent through your pipeline.
Full documentation is here: https://mergermarket.github.io/cdflow/
Install
pip install cdflow
Running
If you are using the cdflow wrapper comamnd mentioned above, you can get usage information by running:
$ cdflow --help
cdflow
Create and manage software services using continuous delivery.
Usage:
cdflow release --platform-config <platform_config> <version> [options]
cdflow deploy <environment> <version> [options]
cdflow destroy <environment> [options]
Options:
-c <component_name>, --component <component_name>
-v, --verbose
-p, --plan-only
Tests
./test.sh
1 maintainer
Metadata
1 maintainer
Release files for cdflow 169
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 | |
|---|---|---|---|---|
| cdflow-169.tar.gz | 11.9 kB | Without provenance | Details |
Release files / cdflow-169.tar.gz
| Download URL | cdflow-169.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5d175a5775a4d89509c68a9afb4cd423609d01261bedddc798457a87e3d49ba2
|
|
BLAKE2b-256 checksum How to use checksums |
1e7a7cbd556afc0969c660c11d67dadd409fb9c6f963f9ca70993a8ca97573a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.40.2 CPython/3.7.4
|
Security for cdflow 169
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.
