Group F - Fix spending per tenant
All checks were successful
Build and Push / build (push) Successful in 1m22s
All checks were successful
Build and Push / build (push) Successful in 1m22s
This commit is contained in:
@@ -67,18 +67,12 @@ export default async function TenantDetailPage({
|
||||
);
|
||||
const channelUsers = tenant.spec.channelUsers || {};
|
||||
|
||||
// Admins inspecting another tenant's usage: pass teamId AND keyAlias so
|
||||
// the backend filters spend logs by this specific tenant's virtual key.
|
||||
// Without keyAlias the response would include sibling tenants in the
|
||||
// same org, since teams are now shared (Slice 2).
|
||||
// Customers viewing their own: pass nothing — backend resolves both
|
||||
// from the session-bound tenant.
|
||||
const usageTeamId = user.isPlatform
|
||||
? tenant.status?.litellmTeamId || undefined
|
||||
: undefined;
|
||||
const usageKeyAlias = user.isPlatform
|
||||
? tenant.status?.litellmKeyAlias || undefined
|
||||
: undefined;
|
||||
// Bug 19 fix: every viewer (customer or admin) passes the tenant
|
||||
// name to UsageDisplay. The /api/usage route resolves team+alias
|
||||
// from the tenant CR's status and applies the visibility check, so
|
||||
// no per-role branching is needed here. Previous version only
|
||||
// passed identifiers for platform admins; customers got "the first
|
||||
// visible tenant" by API fallback, mingling siblings.
|
||||
|
||||
return (
|
||||
<div>
|
||||
@@ -150,7 +144,7 @@ export default async function TenantDetailPage({
|
||||
<h2 className="text-xs font-semibold uppercase tracking-wider text-text-muted mb-3">
|
||||
{t("usage")}
|
||||
</h2>
|
||||
<UsageDisplay teamId={usageTeamId} keyAlias={usageKeyAlias} />
|
||||
<UsageDisplay tenant={name} />
|
||||
</section>
|
||||
|
||||
{/* Packages */}
|
||||
|
||||
Reference in New Issue
Block a user