CWZ - CMK-Werk-Zeug
Tools for Checkmk development. Some solid, some rough, some experimental.
Tools
cmk-components - who owns what in check_mk, straight from Gerrit's
code-owners plugin. TUI by default. list, info, owners PATH, me and friends for scripts.
update-gerrit-changes - a table of your local commits against their Gerrit changes: in sync, behind, diverged, not pushed. Read-only.
cmk-infect - hardlink the files you changed into an installed OMD
version (or a site's local/ with --mkp), for 2.4, 2.5 and master checkouts. Zero-second
deploy, no code generation, rough edges. --check-paths shows where each file would go.
cmk-up (alias cmk-setup) - build a Checkmk setup from a YAML
playbook: versions (pinned, or the newest daily since a date), sites with remotes, hosts with
faked or real services, users, roles, rules, BI, host relations. Reverts itself unless told
otherwise. Playbooks combine: several on the command line, include: in the file,
disabled: true to leave a part out, - for stdin. A window per site tails its logs, runs
omd/cmk -R and deploys a checkout with cmk-dev-deploy; --verify reads everything back;
--rm wipes the machine. --init writes a starter, --enroll a playbook from an existing
machine or a crash report. cmk-up 01-minimal runs a shipped example.
cmk-check-plugins - run check plugins against recorded SNMP walks
and agent outputs. Proof of concept. Needs a check_mk Python environment.
ci-build-metrics - fetch finished Jenkins builds, match failures against known issues, export to PostgreSQL. Sheriff tooling, built for one user.
worklog-from-fs (alias forgot-to-track-time-again) - guess your
daily activity from file modification times.
gmine - a Textual TUI for your Gerrit changes: list, diff, comment, vote,
submit (gated too), trigger CI, rebase, watches with desktop notifications, Jira ticket moves.
gmine --configure sets it up; GMINE_FAKE=1 gmine runs it on sample data.
cmk-devboard (also devboard) is installed too: an experimental Gerrit/Jira dashboard TUI.
Undocumented.
Gerrit and Jenkins credentials work the same for all tools: doc/credentials.md.
Install
Use without installation:
uvx --from cmk-werk-zeug <CMD> # e.g. cmk-up, gmine, cmk-infect
Easy pipx based installation:
pipx install cmk-werk-zeug
Development setup:
git clone ssh://review.lan.tribe29.com:29418/cmk-werk-zeug
cd cmk-werk-zeug && uv sync
uv run <CMD>
uv tool install --editable .
ci/run-change-validation.sh # what CI runs: lock check, pre-commit, unit and system tests
ci-build-metrics export needs a local PostgreSQL (sudo apt install postgresql). Setup in
doc/ci-build-metrics.md.
1 maintainer
Metadata
1 maintainer
Release files for cmk-werk-zeug 0.4.10
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 | |
|---|---|---|---|---|
| cmk_werk_zeug-0.4.10.tar.gz | 778.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cmk_werk_zeug-0.4.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.3 MB
Release files / cmk_werk_zeug-0.4.10.tar.gz
| Download URL | cmk_werk_zeug-0.4.10.tar.gz |
|---|---|
| Size | 778.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63d91c2ea99324022f659be78dda22596ffc0eb70ba80d6ab521d32d57e1401e
|
|
BLAKE2b-256 checksum How to use checksums |
c699df7e824beccc3255e0bfc3fc6710246c2fb579c5dbbd3f26579b2c415891
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.27 {"installer":{"name":"uv","version":"0.9.27","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / cmk_werk_zeug-0.4.10-py3-none-any.whl
| Download URL | cmk_werk_zeug-0.4.10-py3-none-any.whl |
|---|---|
| Size | 484.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2dda75d1b1f03b5558f3282362792ba552056f59208e83737eb29c48a36205a1
|
|
BLAKE2b-256 checksum How to use checksums |
9af387f19ea02d32b7e35206e4221207d2985a9ca95b7eac7b1c22159cca6e4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.27 {"installer":{"name":"uv","version":"0.9.27","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for cmk-werk-zeug 0.4.10
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.
