codepiper
This tool provides some utilities for working with AWS CodePipeline:
watch- Monitor a pipeline for executions and also follow CodeBuild logs.debug- Run stage with debug mode enabled.verify_clear- Verify that a pipeline is clear, or the details if not.rollback- Rollback a stage of a pipeline to a prior execution.
Watch
To monitor all active executions for a pipeline:
codepiper --profile toolchain --region us-west-2 watch -p my-pipeline-name
To monitor a pipeline along with logs from CodeBuild:
codepiper --profile toolchain --region us-west-2 watch -p my-pipeline-name -f
To monitor one specific execution for a pipeline:
codepiper --profile toolchain --region us-west-2 watch -p my-pipeline-name -e 20b20f00-f63d-4b05-8921-20a4fc16090e
codepiper --profile toolchain --region us-west-2 verify_clear -p my-pipeline-name
Debug
View a running build in Session Manager
You will need to add the codebuild-breakpoint command in the buildspec where you want to pause execution. When you are done debugging run codebuild-resume in the CLI to resume the build.
The debug option will output a codebuild URL for the build. Once the build is PROVISIONED there will be an SSM Session link to follow to get CLI access.
To run a pipeline stage in debug mode:
codepiper --profile toolchain --region us-west-2 debug --pipeline my-pipeline-name --stage Integration
To run a pipeline stage in debug mode with new or overridden env vars:
codepiper --profile toolchain --region us-west-2 debug --pipeline my-pipeline-name --stage Integration --envvar JAVA_OPTS="-Xmx1g -Dproperty=value" --envvar JAVA_VAR1=new_value
Rollback
To rollback a pipeline stage to last successful execution:
codepiper --profile toolchain --region us-west-2 rollback -p my-pipeline-name -s Production
To rollback a pipeline stage to a specific commit id:
codepiper --profile toolchain --region us-west-2 rollback -p my-pipeline-name -s Production -c af32c18
To rollback a pipeline stage and watch logs
codepiper --profile toolchain --region us-west-2 rollback -p my-pipeline-name -s Production -f
Verify Pipeline Clear
To verify that a pipeline is currently clear:
codepiper --profile toolchain --region us-west-2 verify_clear --pipeline my-pipeline-name
Installation
Use the upgrade flag to ensure you have the latest version.
pip install codepiper --upgrade
Limitations
$CODEBUILD_RESOLVED_SOURCE_VERSIONis unavailable since the CodeBuild execution is not initiated via CodePipeline. The workaround for this is to use CodePipeline Variables to pass theCommitIdfrom source stage as a user defined environment variable to your CodeBuild project.
Metadata
Release files for codepiper 0.2.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 |
|---|---|---|---|---|
| codepiper-0.2.1.tar.gz | 13.8 kB | Without provenance | Details for codepiper-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| codepiper-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for codepiper-0.2.1-py3-none-any.whl |
Total release size: 28.2 kB
Release files / codepiper-0.2.1.tar.gz
| Download URL | codepiper-0.2.1.tar.gz |
|---|---|
| Size | 13.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d95f50650235b5b0498ae26bd87321b3d8cbc84bcc3b263008b442072d749bb4
|
|
BLAKE2b-256 checksum How to use checksums |
10482d252691896e7722ad5e5a22046c0ea0180e8706abd4c3fc44756289f46f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Release files / codepiper-0.2.1-py3-none-any.whl
| Download URL | codepiper-0.2.1-py3-none-any.whl |
|---|---|
| Size | 14.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa5ee198e634e54218d075e2e2e439ee96c0c0f96144aa16b8b08966cca44fc0
|
|
BLAKE2b-256 checksum How to use checksums |
1e0fc16fab2f16d084bc0d6c11f990d9b41a5e857c539143457adc313e5be187
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Security for codepiper 0.2.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.