0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-10 04:36:40 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 5 b7ccff3278 fix(checkmk): give the site tmp a mode instead of trusting the engine default

The default is what varies between Docker versions, not the explicit value.
Measured by starting each engine and reading the mount back:

    engine   tmpfs without mode   tmpfs with mode 1777
    29.7.2   1777 root            honoured
    28.5.2   755 root             1777 root

A checkmk site runs as uid 1000, so a root-owned 755 tmp makes omdlib fail
`mkdir /omd/sites/cmk/tmp/apache` and the container restarts forever. That is
exactly what run 34348821577 shows, on runners reporting Docker 28.0.4.

f3eba39cae removed `mode: "01777"` here after measuring on 29.7.2 alone, where
the default happens to match, and so replaced the mechanism that behaves the
same everywhere with the one that does not. The mode comes back.

The validator loses the ban with it. Its stated reason, that `docker stack
deploy` drops the key, is a different claim from the one the removing commit
made, and neither survives the measurement above for the compose path this
failure came from; it now checks the type and nothing more.

One thing this does not settle. The note this repository kept on the earlier
attempt records run 33923190220 failing the same way on 28.0.4 while the mode
WAS set. That contradicts the 28.5.2 row and did not reproduce, so either the
patch releases differ or that diagnosis was wrong. The next run decides it:
read the engine version out of the rescue artifact and check whether the site
tmp comes up 1777.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-10 00:55:05 +02:00

annotations

…

cache

perf(volumes): answer one role from its own file, not from a whole-tree build

2026-09-09 18:16:20 +02:00

claude

…

cleanup

…

diagnostics

fix(diagnostics): let the in-zone probes read the drop-in that holds the zone

2026-09-03 12:50:58 +02:00

docker

perf(healthcheck): let the start window outlast a real boot

2026-09-09 21:54:26 +02:00

domains

…

env

…

github

fix(ci): replay the instructions on a row that runs in the guide's mode

2026-09-01 22:21:13 +02:00

handler

fix(vault): keep ansible off the CI runner host's import path

2026-09-08 22:28:47 +02:00

install

fix(test): resolve the PHP vendor tree against a declared floor

2026-09-09 02:15:56 +02:00

inventory

…

manager

…

README.md

Shared Utilities (`utils/`)

This directory contains shared Python helpers used by custom modules and plugins.

Purpose

Use utils/ for reusable code that should not be duplicated across:

library/ modules,
plugins/action/,
plugins/filter/,
plugins/lookup/.

Typical shared utilities:

API clients,
validation/conversion helpers,
path and configuration helpers,
cross-plugin/module domain logic.
Shared HTTP(S) connection handler for multiple modules.
Common validation or transformation functions for user input.
Utility functions for interacting with Docker, LDAP, etc.
Grouped helper packages such as utils/domains/ for related domain logic.

Design Guidelines

Keep helpers focused and composable.
Avoid side effects during import.
Prefer explicit function/class APIs over implicit globals.
Keep dependencies minimal so modules/plugins stay lightweight.

Example Import

from utils.domains.primary_domain import get_primary_domain

What Does Not Belong Here

Standalone executable modules (put in library/).
Ansible plugin entrypoints (put in plugins/*).

References

Module utilities: https://docs.ansible.com/ansible/latest/dev_guide/developing_module_utilities.html
Plugin development: https://docs.ansible.com/ansible/latest/dev_guide/developing_plugins.html