8cd72fd78d
All checks were successful
continuous-integration/drone/push Build is passing
a) compose.ccci.yml is FIRST-CLASS: the harness auto-copies tests/<recipe>/ compose.ccci.yml into the run's recipe checkout (ABRA_DIR-aware, lifecycle. provide_ccci_overlay) and auto-chaoses the pinned base deploy on its presence (kills the R7 implicit coupling). ghost/discourse install_steps.sh (copy-only boilerplate) deleted; CHAOS_BASE_DEPLOY removed from both metas + the registry. b) install-time deps wiring is the ONLY mode: deps with DEPS provision BEFORE the single deploy; legacy post-deploy provisioning + the setup_custom_tests.sh invocation machinery deleted. lasuite-docs migrated to install_steps.sh OIDC wiring (same env names/values as the old hook — only the timing moved); lasuite-drive's remaining post-deploy MinIO bucket one-shot moved to ops.py pre_install; both setup_custom_tests.sh files deleted; OIDC_AT_INSTALL removed from drive/meet metas + the registry. c) SKIP_GENERIC meta key deleted (zero users). Env form CCCI_SKIP_GENERIC* stays as the documented dev-only escape hatch; when active in a drone CI run the orchestrator prints a loud !! warning (manifest embedding lands in P5). d) conftest cleanup: dead pre-deploy-once fixtures deployed/deployed_app deleted (zero users), app_domain + _short + _wait_healthy dropped (only users were the deleted fixtures); deps_apps+deps_creds consolidated into ONE deps fixture (entries expose .domain etc. as attributes; dict access intact); the 6 lasuite test files renamed deps_creds->deps (fixture name only — assertions and flows byte-identical). requires_deps marker + F2-11 skip-report plumbing unchanged. Registry is now exactly the 14 final keys; docs §4 table regenerated. Stale setup_custom_tests/OIDC_AT_INSTALL prose in docstrings/comments/assert MESSAGES updated (no assert logic or expected value touched). Verified on cc-ci: cc-ci-run -m pytest tests/unit -q -> 175 passed; scripts/lint.sh -> PASS.
38 lines
2.2 KiB
Python
38 lines
2.2 KiB
Python
# Per-recipe harness config for lasuite-meet (Phase 2 Q3.3 — La Suite / impress sibling of
|
|
# lasuite-docs + lasuite-drive; real-time video meetings via LiveKit, OIDC-dependent).
|
|
#
|
|
# Stack: app (React SPA) + backend (Django) + celery + db (postgres) + redis + livekit (SFU/WebSocket
|
|
# signaling) + web (nginx). OIDC (keycloak) is REQUIRED by the recipe.
|
|
#
|
|
# Health: the SPA is served at `/` and returns 200 unauthenticated (login is OIDC-gated, exercised by
|
|
# the SSO functional tests, not the install health check).
|
|
HEALTH_PATH = "/"
|
|
HEALTH_OK = (200, 301, 302)
|
|
# Moderate stack (no onlyoffice/collabora office backends — lighter than lasuite-drive); livekit +
|
|
# impress front/backend + postgres. Generous but smaller window than drive.
|
|
DEPLOY_TIMEOUT = 1200
|
|
HTTP_TIMEOUT = 600
|
|
|
|
# SSO-dependent (recipe.toml requires=["keycloak"], [sso] provider=keycloak). OIDC is wired at
|
|
# INSTALL time (the only deps mode since rcust P2b) against the live-warm keycloak: the
|
|
# orchestrator provisions the per-run realm BEFORE the single `abra app deploy`, and
|
|
# tests/lasuite-meet/install_steps.sh writes the OIDC env + client secret into that one deploy
|
|
# (no post-deploy reconverge). Meet boots fine with OIDC env set because keycloak is live-warm.
|
|
DEPS = ["keycloak"]
|
|
|
|
|
|
def EXTRA_ENV(domain):
|
|
# lasuite-meet routes LiveKit's WebSocket signaling on a DOMAIN-derived **nested** subdomain
|
|
# `LIVEKIT_DOMAIN="livekit.${DOMAIN}"`. The cc-ci wildcard TLS cert is `*.ci.commoninternet.net`
|
|
# (single label only), so a 2-label name like `livekit.lasuite-meet-pr0-abc.ci.commoninternet.net`
|
|
# is NOT covered → TLS failure on that router. Flatten to a single-label SIBLING under the
|
|
# wildcard (`livekit-<domain>`) so the existing wildcard cert covers it and Traefik routes it with
|
|
# no cert/gateway change. Same fix as lasuite-drive's minio/collabora siblings (DECISIONS.md
|
|
# "Phase 2 — nested DOMAIN-derived subdomains").
|
|
return {
|
|
"LIVEKIT_DOMAIN": f"livekit-{domain}",
|
|
# abra's internal per-deploy convergence TIMEOUT (default 300s) is too short for this stack on
|
|
# a cold image cache; bump it (kept under DEPLOY_TIMEOUT so Python never kills abra mid-wait).
|
|
"TIMEOUT": "1000",
|
|
}
|