Files
cc-ci/tests/lasuite-meet/recipe_meta.py
autonomic-bot 136100f610
All checks were successful
continuous-integration/drone/push Build is passing
feat(canon): M1.3 enroll all 21 used-recipes as data-warm canonicals (§2.B)
WARM_CANONICAL=True added to every recipe in cc-ci-plan/used-recipes.md (20 weekly +
uptime-kuma external). enrolled_recipes() now returns all 21. Test fixtures
(custom-html-*-bad, concurrency, regression) intentionally left unenrolled.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-17 06:35:30 +00:00

43 lines
2.4 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(ctx):
# 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-{ctx.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",
}
# canon §2.B: enroll as a DATA-WARM canonical (all recipes enrolled — operator 2026-06-17).
# The weekly sweep promotes this recipe's canonical to its latest green RELEASE TAG.
WARM_CANONICAL = True