8edb485caf
The close-audit DoD validator on a Sovereign host
(e.g. console.t32.omani.works) probes POST /api/v1/billing/purchase
+ POST /api/v1/sme/billing/purchase during the marketplace
customer-journey re-walk (Step 15 — "Purchase" button). On t32 both
returned 404 because the route was never registered on catalyst-api
or the billing service — distinct from the prior 502 class which
was a billing-service-Pod-stale / NATS-connection failure (TBD-A1
The canonical purchase wire has always been
POST /api/billing/checkout (marketplace gateway → billing service
Checkout handler — see CheckoutStep.svelte:722 + handlers.go +
routes.go); the validator vocabulary diverged from the in-cluster
naming. Rather than renaming the canonical handler or migrating
every existing caller, this PR registers two thin aliases:
- billing service (core/services/billing/handlers/routes.go):
POST /billing/purchase → existing Checkout handler. Same
promo-code application, same Stripe-session creation, same
paid_by_credit shortcut. Semantic alias only.
- catalyst-api (products/catalyst/bootstrap/api/...):
POST /api/v1/billing/purchase + POST /api/v1/sme/billing/purchase
→ proxy to SME gateway /api/billing/purchase → billing
service /billing/purchase. Mirrors sme_billing_vouchers.go
proxy shape — same mintSMEBridgeToken RS256→HS256 bridge,
same 503 sme-gateway-unreachable graceful-degradation on a
Sovereign without the SME services tier.
Marketplace UI continues to call /api/billing/checkout unchanged
(no FE migration), so every existing customer-journey GREEN path
remains stable. The new aliases exist primarily so the
operator-side DoD validator on console.<sov-fqdn> stops 404'ing.
Chart bump: 1.4.188 → 1.4.189 + bootstrap-kit pin synced.
Tests: routes_test.go asserts both /billing/purchase and
/billing/checkout resolve (regression guard for accidental
rename / removal). All existing billing + catalyst-api handler
tests pass.
Co-authored-by: hatiyildiz <hatiyildiz@users.noreply.github.com>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| admin | ||
| cmd | ||
| console | ||
| controllers | ||
| marketplace | ||
| marketplace-api | ||
| pkg/dynadot-client | ||
| pool-domain-manager | ||
| services | ||
| README.md | ||
Catalyst Control Plane (core/)
The user-facing Catalyst control plane modules. Status: Consolidated and deployed on Catalyst-Zero (Contabo k3s) as of Pass 105 (2026-04-28).
Read first:
docs/PROVISIONING-PLAN.md,docs/GLOSSARY.md,docs/ARCHITECTURE.md,docs/IMPLEMENTATION-STATUS.md.
What this is
The four modules that constitute the Catalyst control plane's user-facing surface, plus the Go backend they share. Each is its own Containerfile-built workload, deployed on every Catalyst Sovereign (starting with Catalyst-Zero on Contabo, and on every franchised Sovereign provisioned thereafter).
| Module | Stack | Purpose | Deployed image |
|---|---|---|---|
console/ |
Astro + Svelte | Primary user-facing UI. Form / Advanced / IaC editor depths. The Sovereign-provisioning wizard at /sovereign (Phase 3) lives here. |
ghcr.io/openova-io/openova/console:<sha> |
admin/ |
Astro + Svelte | Sovereign-admin operations UI. Includes the canonical voucher / billing / catalog / orders / tenants admin surface that sovereign-admin uses to issue vouchers to franchised tenants. | ghcr.io/openova-io/openova/admin:<sha> |
marketplace/ |
Astro + Svelte | Public-facing Blueprint card grid (the "App Store"). 5-step Plan → Apps → Addons → Checkout → Review flow. |
ghcr.io/openova-io/openova/marketplace:<sha> |
marketplace-api/ |
Go | Backend API for marketplace and console. Handlers (handlers/), provisioner (provisioner/), store (store/). Phase 4 extends this with full Hetzner provisioning. |
ghcr.io/openova-io/openova/marketplace-api:<sha> |
The Helm chart that deploys all four (plus catalyst-ui, catalyst-api, and the legacy SME backend services) lives at products/catalyst/chart/.
CI / Build
Each module has a corresponding GitHub Actions workflow:
.github/workflows/console-build.yaml.github/workflows/admin-build.yaml.github/workflows/marketplace-build.yaml.github/workflows/marketplace-api-build.yaml.github/workflows/catalyst-build.yaml— coversproducts/catalyst/bootstrap/{ui,api}/(the React SPA + Go bootstrap API)
Each workflow watches its module path, builds the Containerfile, pushes to GHCR with a SHA tag, and pins the SHA into the corresponding manifest in products/catalyst/chart/templates/ (so Flux on Catalyst-Zero picks up the new image on the next reconciliation).
Migration history
- Pass 105 (2026-04-28):
console/,admin/,marketplace/consolidated fromopenova-private/apps/{console,admin,marketplace}/into this directory.marketplace-api/consolidated fromopenova-private/website/marketplace-api/. Six CI workflows migrated to.github/workflows/of the public repo. Catalyst-Zero K8s manifests migrated fromopenova-private/clusters/contabo-mkt/apps/{catalyst,sme/services,marketplace-api}/intoproducts/catalyst/chart/templates/. Image references updated fromghcr.io/openova-io/openova-private/sme-{admin,console,marketplace}toghcr.io/openova-io/openova/{admin,console,marketplace}. The 8 legacy SME backend services (auth,billing,catalog,domain,gateway,notification,provisioning,tenant) keep theiropenova-private/sme-*image refs until their source code migrates in a follow-up phase.
Part of OpenOva