Some checks failed
continuous-integration/drone/push Build is failing
Per operator: the level ladder is now the FOUR essential rungs every recipe is held to — install, upgrade (essential), backup/restore, functional (top = L4). Integration (SSO/OIDC) and recipe-local are OPTIONAL capabilities: they no longer appear as level rungs or skip rows and never cap the level. SSO is still enforced for the run VERDICT (unchanged in run_recipe_ci.py); it just doesn't affect the level. derive_rungs simplified accordingly (drops declared/deps/sso/repo-local inputs). custom-html-tiny's EXPECTED_NA is back to just backup_restore. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
17 lines
1.1 KiB
Python
17 lines
1.1 KiB
Python
# Per-recipe config for custom-html-tiny (a fast static-web-server). Shorter timeouts than the
|
|
# defaults: it converges + serves in seconds, so the generic install's fail-without-hook case
|
|
# (DG5) is detected quickly instead of waiting the default 300s HTTP timeout.
|
|
DEPLOY_TIMEOUT = 120
|
|
HTTP_TIMEOUT = 90
|
|
|
|
# Rungs this recipe INTENTIONALLY skips, each with a reason. Any essential rung skipped (N/A) and NOT
|
|
# listed here is reported as an *unintentional* skip (a coverage gap to fill or declare). A skip still
|
|
# caps the level either way — the harness never claims a rung it did not verify; this only records
|
|
# that the skip is deliberate. (The level ladder is the four essential rungs install/upgrade/
|
|
# backup_restore/functional; integration + recipe-local are optional and not leveled.)
|
|
# custom-html-tiny is a stateless static-web-server, so it has no backup surface:
|
|
EXPECTED_NA = {
|
|
"backup_restore": "stateless static file server: serves an ephemeral content volume seeded at "
|
|
"deploy, with no persistent/user data to back up or restore (no backupbot.backup label)",
|
|
}
|