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

Async tenant provisioning (frontend UX) #52

New Issue
Closed
opened 2026-04-10 09:55:57 +02:00 by claude · 1 comment
claude commented 2026-04-10 09:55:57 +02:00
Owner
Copy Link

Problem

Tenant provisioning is synchronous — the Create Tenant button blocks for ~30-60s while the backend provisions Docker containers, waits for health checks, pushes license and OIDC config.

Expected

  • Show a "Provisioning..." spinner/progress indicator immediately
  • Navigate to the tenant detail page with status=PROVISIONING
  • Poll for status changes (PROVISIONING → ACTIVE)
  • Toast notification when provisioning completes

Current behavior

The Create Tenant form hangs with no feedback until provisioning completes, then redirects to the detail page.

Scope

Frontend-only change. Backend already sets status=PROVISIONING before provisioning and updates to ACTIVE on success.

## Problem Tenant provisioning is synchronous — the Create Tenant button blocks for ~30-60s while the backend provisions Docker containers, waits for health checks, pushes license and OIDC config. ## Expected - Show a "Provisioning..." spinner/progress indicator immediately - Navigate to the tenant detail page with status=PROVISIONING - Poll for status changes (PROVISIONING → ACTIVE) - Toast notification when provisioning completes ## Current behavior The Create Tenant form hangs with no feedback until provisioning completes, then redirects to the detail page. ## Scope Frontend-only change. Backend already sets status=PROVISIONING before provisioning and updates to ACTIVE on success.
claude commented 2026-04-10 17:14:46 +02:00
Author
Owner
Copy Link

Fixed in 252c18b.

Backend: Extracted Docker provisioning (containers, health check, license push, OIDC config) into an @Async method. The API now returns immediately after creating the tenant record (PROVISIONING), Logto org, admin user, and license. Provisioning runs in a background thread and updates status to ACTIVE on success or sets provisionError on failure.

Frontend:

  • CreateTenantPage navigates to detail page immediately with "provisioning in progress" toast
  • TenantDetailPage polls every 3s while status=PROVISIONING (via refetchInterval callback)
  • Shows spinner + "Provisioning..." indicator next to status badge
  • Toast notification when provisioning completes (success or warning)
  • VendorTenantsPage list already had 30s refetch, so it picks up status changes too
Fixed in `252c18b`. **Backend**: Extracted Docker provisioning (containers, health check, license push, OIDC config) into an `@Async` method. The API now returns immediately after creating the tenant record (PROVISIONING), Logto org, admin user, and license. Provisioning runs in a background thread and updates status to ACTIVE on success or sets `provisionError` on failure. **Frontend**: - CreateTenantPage navigates to detail page immediately with "provisioning in progress" toast - TenantDetailPage polls every 3s while status=PROVISIONING (via `refetchInterval` callback) - Shows spinner + "Provisioning..." indicator next to status badge - Toast notification when provisioning completes (success or warning) - VendorTenantsPage list already had 30s refetch, so it picks up status changes too
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
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#52
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?