284313f908
Some checks are pending
Bidi Control Character Guard / bidi-control-guard (push) Waiting to run
Circular Dependency Check / Check for new circular dependencies (push) Waiting to run
Citus Migration Smoke / Combined migrations on single-node Citus (push) Waiting to run
E2E Fresh Install Tests / fresh-install-e2e (push) Waiting to run
ext-v2 guardrails / Run ext-v2 guard and ESLint (push) Waiting to run
Integration Tests / Check for relevant changes (push) Waiting to run
Integration Tests / ${{ (github.event_name == 'schedule' || github.event.inputs.suite == 'full') && 'Full integration suite' || 'Tier-1 integration subset' }} (push) Blocked by required conditions
Mobile checks / Mobile lint + typecheck (push) Waiting to run
Mobile checks / Mobile unit tests (push) Waiting to run
Mobile checks / Mobile dependency audit (report) (push) Waiting to run
Mobile checks / Mobile reproducibility checks (push) Waiting to run
Secrets guard (env backups) / Ensure no tracked env backup files (push) Waiting to run
Temporal Readiness / fast-readiness (push) Waiting to run
Temporal Readiness / docker-parity (push) Waiting to run
TypeScript Type Check / Nx affected typecheck (push) Waiting to run
Unit Tests / Skipped-test budget (push) Waiting to run
Unit Tests / Nx affected unit tests (push) Waiting to run
Unit Tests / Server unit coverage (informational) (push) Waiting to run
Validate Tenant Management Schema / Check for relevant changes (push) Waiting to run
Validate Tenant Management Schema / Validate Tenant Management Schema (push) Blocked by required conditions
EE Workflows Build Guard / ee-workflows-build-guard (push) Waiting to run
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz Source: /opt/alga-psa on psa.joliet.tech
73 lines
2.4 KiB
JSON
73 lines
2.4 KiB
JSON
[
|
|
{
|
|
"id": "F001",
|
|
"description": "Add an appliance-owned Flux profile for Talos single-node deployment under `ee/appliance/flux/`.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F002",
|
|
"description": "Add appliance values overlays for the root Alga chart and each EE service chart used by the Talos profile.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F003",
|
|
"description": "Add appliance bootstrap/deploy scripts that target the Talos single-node Flux profile.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F004",
|
|
"description": "Add a Kubernetes deployment path for PgBouncer as a Helm chart under `ee/helm/pgbouncer`.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F005",
|
|
"description": "Route the root chart server deployment through PgBouncer when the appliance profile enables it.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F006",
|
|
"description": "Preserve generated root-chart DB credentials across Helm reconciliations instead of rotating them on reinstall.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F007",
|
|
"description": "Replace the current split migration/seed Helm hook flow with a single idempotent bootstrap hook job using the setup image.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F008",
|
|
"description": "Make the setup entrypoint safe to run in Kubernetes jobs that provide DB credentials via environment variables rather than Docker secret files only.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F009",
|
|
"description": "Ensure the bootstrap flow only runs seeds when the application database is still unseeded.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F010",
|
|
"description": "Wire `workflow-worker` to the appliance profile with PgBouncer-backed DB configuration and release ordering.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F011",
|
|
"description": "Wire `email-service` to the appliance profile with PgBouncer-backed DB configuration and release ordering.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F012",
|
|
"description": "Wire `temporal-worker` to the appliance profile with PgBouncer-backed DB configuration and Temporal dependency ordering.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F013",
|
|
"description": "Wire a Temporal server release into the appliance profile for single-node operation.",
|
|
"implemented": true
|
|
},
|
|
{
|
|
"id": "F014",
|
|
"description": "Document the Talos appliance GitOps deployment shape and validation expectations in repo plan/design docs.",
|
|
"implemented": true
|
|
}
|
|
]
|