cameleer/cameleer-saas
2
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects Releases Wiki Activity

V2: Vendor — Provision server for a tenant #41

New Issue
Closed
opened 2026-04-09 21:24:06 +02:00 by claude · 1 comment
claude commented 2026-04-09 21:24:06 +02:00
Owner
Copy Link

User Story: As a vendor, I want to provision a server for a tenant so they have a running Cameleer instance.

Acceptance Criteria:

  • SaaS creates cameleer3-server + server-ui containers via Docker API
  • Correct env vars: database URL, ClickHouse URL, tenant ID, OIDC config, license token
  • Containers join cameleer + cameleer-traefik networks
  • Traefik labels route /t/{slug}/* to tenant's server
  • Health check passes (poll /actuator/health, timeout 60s)
  • License pushed to server via M2M API
  • Tenant status transitions PROVISIONING → ACTIVE
  • Pluggable interface (TenantProvisioner) supports Docker now, K8s later

Spec: docs/superpowers/specs/2026-04-09-platform-redesign.md — Section 3
API: Part of POST /api/vendor/tenants flow

**User Story:** As a vendor, I want to provision a server for a tenant so they have a running Cameleer instance. **Acceptance Criteria:** - SaaS creates cameleer3-server + server-ui containers via Docker API - Correct env vars: database URL, ClickHouse URL, tenant ID, OIDC config, license token - Containers join `cameleer` + `cameleer-traefik` networks - Traefik labels route `/t/{slug}/*` to tenant's server - Health check passes (poll /actuator/health, timeout 60s) - License pushed to server via M2M API - Tenant status transitions PROVISIONING → ACTIVE - Pluggable interface (`TenantProvisioner`) supports Docker now, K8s later **Spec:** `docs/superpowers/specs/2026-04-09-platform-redesign.md` — Section 3 **API:** Part of `POST /api/vendor/tenants` flow
claude added the platforminfraday-1 labels 2026-04-09 21:24:06 +02:00
claude commented 2026-04-10 20:43:41 +02:00
Author
Owner
Copy Link

All acceptance criteria implemented: DockerTenantProvisioner creates server + UI containers via Docker API, correct env vars, tenant + traefik + shared networks, Traefik labels for /t/{slug}/*, health check polling, license + OIDC push via M2M API, status transition PROVISIONING → ACTIVE, pluggable TenantProvisioner interface. Closing.

All acceptance criteria implemented: `DockerTenantProvisioner` creates server + UI containers via Docker API, correct env vars, tenant + traefik + shared networks, Traefik labels for `/t/{slug}/*`, health check polling, license + OIDC push via M2M API, status transition PROVISIONING → ACTIVE, pluggable `TenantProvisioner` interface. Closing.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auth
Identity, authentication, OIDC, RBAC
 billing
Billing, metering, and Stripe integration
 day-1
Required for initial launch
 epic
Top-level epic grouping related issues
 future
Planned for future release
 infra
Infrastructure, GitOps, K8s orchestration
 licensing
License module and feature gating
 networking
Network isolation, VPN, tenant separation
 observability
Observability integration (cameleer3-server)
 ops
Platform operations and self-monitoring
 phase-1
Phase 1: Foundation + Auth
 phase-2
Phase 2: Tenants + Licensing
 phase-3
Phase 3: Runtime Orchestration + Environments
 phase-4
Phase 4: Observability Pipeline + Inbound Routing
 phase-5
Phase 5: K8s Operational Layer
 phase-6
Phase 6: Billing + Metering
 phase-7
Phase 7: Billing + Metering
 phase-8
Phase 8: Security Hardening + Self-Monitoring
 phase-9
Phase 9: Frontend (React Shell)
 platform
SaaS management platform
 runtime
Camel application runtime
 secrets
Secrets management and vault integration
 security
Security, compliance, SOC 2, audit
 task
Implementation task within a phase
No Label day-1 infra platform
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cameleer/cameleer-saas#41
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?