Files
computer-playbook/tests/unit/python/utils/certs/README.md
T
kevinveenbirkenbachandClaude Opus 5 fcc98bcad1 fix(docs): require a README behind every directory link
The lint accepted a link that resolved to a file or a directory. myst
builds a document reference only when the target is_file(), so a link to
a directory without a README is a bare file listing on GitHub and a dead
cross-reference in the documentation build. It now reports which of the
two reasons applies.

The tightened rule found 41 links. Where a README backs the directory,
bd15eae9fa's resolver carries the link and it stays. Where none exists,
the link becomes a code span rather than an invented README: 15 of them
point at a role's meta/addons/, whose addon table already sits below the
sentence, and the rest at code directories such as utils/ or
cli/administration/deploy/runner/.

The changed sentences are msgids, so these entries return to the
translator on the next extract.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-25 18:42:23 +02:00

604 B

Certificate & TLS Unit Tests 🔐

Unit tests for the top-level certificate and TLS helper modules in utils/: cert_utils.py (wildcard/exact match logic, newest-certificate selection) and tls_common.py (flavor handling, SAN overrides, domain normalisation).

Tests in this directory MUST only cover the pure-function behaviour of utils.cert_utils and utils.tls_common. Lookup-plugin integration that depends on these modules MUST live under tests/unit/python/plugins/lookup/.

For framework and make test-unit usage see unit.md.