fix(onboarding): explain blocked Next, humanise errors, de-jargon provisioning

This commit is contained in:
2026-05-29 23:28:45 +02:00
parent 08f28aeb93
commit 3110b40cf9
2 changed files with 99 additions and 42 deletions

View File

@@ -432,25 +432,35 @@ export function ProvisioningStatus({ requestId, canAct }: Props) {
<span className="text-xs text-text-muted">{t("phase")}</span>
<StatusBadge phase={phase} />
</div>
{conditions.map((c, i) => (
<div
key={i}
className="flex items-center justify-between bg-surface-2 border border-border rounded-lg px-4 py-2"
>
<span className="text-xs text-text-muted">{c.type}</span>
<span
className={`text-xs font-mono ${
c.status === "True"
? "text-emerald-400"
: c.status === "False"
? "text-red-400"
: "text-text-muted"
}`}
>
{c.reason || c.status}
</span>
</div>
))}
{/* Setup progress. The operator reports readiness as a list of
internal K8s conditions (OpenBao policy, LiteLLM key, network
policy, …) — meaningful to operators, jargon to customers.
We surface the *shape* of that progress (how many steps are
done) without leaking the internal names. */}
{conditions.length > 0 &&
(() => {
const done = conditions.filter((c) => c.status === "True").length;
const total = conditions.length;
const pct = Math.round((done / total) * 100);
return (
<div className="bg-surface-2 border border-border rounded-lg px-4 py-3">
<div className="flex items-center justify-between mb-2">
<span className="text-xs text-text-muted">
{t("setupProgress")}
</span>
<span className="text-xs font-medium text-text-secondary tabular-nums">
{t("setupStepsComplete", { done, total })}
</span>
</div>
<div className="h-1.5 w-full rounded-full bg-surface-3 overflow-hidden">
<div
className="h-full bg-accent transition-all duration-500"
style={{ width: `${pct}%` }}
/>
</div>
</div>
);
})()}
</div>
</Card>
);