0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-06 19:01:54 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 4.7 16626a7670 fix(env-test): resolve Fedora release dynamically in cache probe

The package-cache active probe in
scripts/tests/environment/utils/cache.sh had `releases/40/...`
hardcoded as the upstream path for the `yum-fedora` Nexus proxy.
Fedora 40 went EOL in May 2025 and dl.fedoraproject.org stopped
serving its repodata, so the probe failed every Test Environment
(fedora:latest) CI job with:

    [probe] package-cache: GET /repository/yum-fedora/releases/40/Everything/x86_64/os/repodata/repomd.xml
    curl: (22) The requested URL returned error: 404
    [FAIL] package-cache: proxy 'yum-fedora' did not serve
        'releases/40/Everything/x86_64/os/repodata/repomd.xml'

Resolve the version dynamically from the runtime image's
`/etc/os-release` instead. The new `_resolve_fedora_release` helper
runs `docker run --rm --entrypoint /bin/cat <image> /etc/os-release`
and lifts `VERSION_ID` via awk, so `fedora:latest` is tracked
automatically and future EOL transitions no longer require a code
change.

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

2026-05-03 23:58:04 +02:00

deploy

docs(design): rename matrix-deploy.md to variants.md, add inventory.md, sync cross-links

2026-04-28 12:54:09 +02:00

e2e

feat(rbac): hierarchical /roles/<app>/<role> + service-gated Playwright + Discourse round-trip

2026-04-25 08:51:01 +02:00

environment

fix(env-test): resolve Fedora release dynamically in cache probe

2026-05-03 23:58:04 +02:00

code.sh

test(external): split live registry checks

2026-04-10 22:31:42 +02:00

dns.sh

refactor: collapse INFINITO_DISTRO/INFINITO_CONTAINER to a single SPOT and align all consumers

2026-04-26 12:21:35 +02:00

README.md

Improve distro compatibility and dev environment testing

2026-03-18 20:00:33 +01:00

README.md

Test Utilities 🧪

This directory holds the operational side of testing in Infinito.Nexus.

These assets are meant to support confidence, not ceremony. They help the project validate real-world behavior across local development, CI environments, and deployment-oriented smoke tests. The emphasis is on practical feedback: when something breaks, the surrounding test tooling should make the failure easier to understand, easier to reproduce, and easier to clean up. 🚀

Good changes in this area usually make the test experience more:

repeatable
diagnosable
environment-aware
safe to rerun

The ideal outcome is boring reliability: contributors should be able to trust that a test run says something meaningful about the system, not just about the machine that happened to execute it. ✅