aws-cdk-build-badge
This an AWS CDK custom construct for get the status of a CodeBuild Project with has CodePipeline as source. That is currently not possible:
How the native badges are working you find in the AWS docs:
After you created the build badge construct you can use the api gateway url to get the badge picture. Additionally you can retrieve the url to to the CodeBuild build with adding ?url=true to the query parameter. See the example.
URL to Build
If you want your badge forwarding you to your build when you click on it use the url=true parameter:
Build succeeded: [](https://fktijpwdng.execute-api.eu-central-1.amazonaws.com/prod/?projectName=PipelineCustomStageprodTest-Fdei5bm2ulR6&url=true)
Default project name
You can use the defaultProjectName in the cdk construct to point the badge to a specific project. That way you don't need to write the projectName parameter in thr url.
new BuildBadge(stack, 'BuildBadge2', { defaultProjectName: 'Build123' });
Example
There are more badges (see ./badges/) but I don't have build in that state atm.
# Example automatically generated without compilation. See https://github.com/aws/jsii/issues/826
app = cdk.App()
stack = cdk.Stack(app, "my-build-badge-demo-stack")
# without exposing the account id in the url when using ?url=true
BuildBadge(stack, "BuildBadge")
# with exposing the account id in the url when using ?url=true
BuildBadge(stack, "BuildBadge2", hide_account_iD="no")
# partly exposing the account id in the url when using ?url=true
BuildBadge(stack, "BuildBadge3", hide_account_iD="XX123356")
Thanks To
- The CDK Community cdk-dev.slack.com
- Projen project and the community around it
- https://github.com/btorun/aws-codebuild-badges
- ...
Metadata
Release files for aws-cdk-build-badge 1.97.21
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 |
|---|---|---|---|---|
| aws-cdk-build-badge-1.97.21.tar.gz | 13.7 MB | Without provenance | Details for aws-cdk-build-badge-1.97.21.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aws_cdk_build_badge-1.97.21-py3-none-any.whl | Python 3 | none | any | Details for aws_cdk_build_badge-1.97.21-py3-none-any.whl |
Total release size: 27.5 MB
Release files / aws-cdk-build-badge-1.97.21.tar.gz
| Download URL | aws-cdk-build-badge-1.97.21.tar.gz |
|---|---|
| Size | 13.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d59bbc84baec942f322f2a36d87e458e225d91d132d2707bdd47e9e9bbaf8982
|
|
BLAKE2b-256 checksum How to use checksums |
1b5e3b90ac250fc559b8a43b058bfb5a1bc87318db1d425f725ac8e7220d3d60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.3.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.7.9
|
Release files / aws_cdk_build_badge-1.97.21-py3-none-any.whl
| Download URL | aws_cdk_build_badge-1.97.21-py3-none-any.whl |
|---|---|
| Size | 13.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
294195b8e58bc5850be153fa26289db9a992678eb57e68bcc09038ce0055d53c
|
|
BLAKE2b-256 checksum How to use checksums |
f67ce9bd5de21c15fa5a0852d206d3a59f9b47a411454f8a3bf9f812364385e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.3.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.7.9
|
Security for aws-cdk-build-badge 1.97.21
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.