@acarmisc/backstage-plugin-litellm 0.25.0 → 0.27.0

package/README.md

@@ -86,11 +86,12 @@ The **Models** tab lists every model the LiteLLM proxy exposes, with per-model i
 - `litellmPlugin` — the frontend plugin instance
 - `LiteLLMPage` — main plugin page (keys, usage, team context)
 - `LiteLLMHomeWidget` — homepage usage summary card
-- `GenerateKeyDialog` — shared "Generate New Key" dialog (surfaces failures inline, warns on duplicate aliases)
+- `KeyFormDialog` — shared key form for both generating and editing a key (surfaces failures inline, warns on duplicate aliases, team-scoped model picker, unlimited-budget toggle when gated on)
+- `GenerateKeyDialog` — deprecated wrapper around `KeyFormDialog` with `mode="create"`
 - `DashboardHeader`, `KeysTable`, `UsageStats`, `TeamUsage` — individual page sections, exported for composition
 - `LiteLlmApi`, `liteLlmApiRef` — API client and its Backstage API ref
 
-Note: `DashboardHeader` and `KeysTable` are composition pieces driven by `LiteLLMPage` and their props differ from older versions. `LiteLLMPage` is the supported entry point; composing the sections directly means keeping them in sync with the page's data wiring (keys, models, teams, and the `onGenerateKeyClick` callback).
+Note: `DashboardHeader` and `KeysTable` are composition pieces driven by `LiteLLMPage` and their props differ from older versions. `LiteLLMPage` is the supported entry point; composing the sections directly means keeping them in sync with the page's data wiring (keys, models, teams, and the `onGenerateKeyClick`/`onEditKey` callbacks).
 
 ## License
 

package/dist/components/GenerateKeyButton.d.ts

@@ -0,0 +1,18 @@
+import React from 'react';
+/**
+ * The single "create a key" call-to-action used everywhere in the plugin —
+ * the plugin page (header, keys table) and the homepage budget card all
+ * render this instead of their own inline `Button`, so the copy, icon and
+ * styling stay identical.
+ */
+export interface GenerateKeyButtonProps {
+    /** Deep-link target (e.g. `/litellm?generate=1`). Ignored when `onClick` is set. */
+    to?: string;
+    /** Click handler. Takes precedence over `to` when both are given. */
+    onClick?: () => void;
+    /** Override the default `Generate New Key` copy (e.g. empty-state variants). */
+    label?: string;
+    /** Button size — card footers use `small`, page headers the default. */
+    size?: 'small' | 'medium' | 'large';
+}
+export declare const GenerateKeyButton: React.FC<GenerateKeyButtonProps>;

package/dist/components/GenerateKeyDialog.d.ts

@@ -1,20 +1,21 @@
 import React from 'react';
-import { VirtualKey, ModelInfo, TeamInfo, GenerateKeyRequest, GenerateKeyResponse, LiteLlmConfig } from '../types';
-interface GenerateKeyDialogProps {
+import { GenerateKeyRequest, GenerateKeyResponse, LiteLlmConfig, ModelInfo, TeamInfo, VirtualKey } from '../types';
+/**
+ * @deprecated Use {@link KeyFormDialog} with `mode="create"` instead — this
+ * wrapper only forwards props for backwards compatibility with the public
+ * entrypoint and will be removed in a future release.
+ */
+export declare const GenerateKeyDialog: React.FC<{
     open: boolean;
     onClose: () => void;
     keys: VirtualKey[];
     models: ModelInfo[];
     teams: TeamInfo[];
-    /** Current user's LiteLLM user id, used to pre-fill a default key alias. */
     username?: string;
-    /** Controls for the "Generate New Key" form; see litellm.keyGeneration in app-config.yaml. */
     keyGenerationSettings?: {
         allowUnlimitedBudget: boolean;
         teamRequired: boolean;
     };
     onGenerateKey: (request: GenerateKeyRequest) => Promise<GenerateKeyResponse>;
     onGetConfig: () => Promise<LiteLlmConfig>;
-}
-export declare const GenerateKeyDialog: React.FC<GenerateKeyDialogProps>;
-export {};
+}>;

package/dist/components/KeyFormDialog.d.ts

@@ -0,0 +1,42 @@
+import React from 'react';
+import { VirtualKey, ModelInfo, TeamInfo, GenerateKeyRequest, GenerateKeyResponse, UpdateKeyRequest, LiteLlmConfig } from '../types';
+/**
+ * Single form dialog for both key creation (`mode="create"`) and key editing
+ * (`mode="edit"`).
+ *
+ * Create mode: alias (pre-filled), team, models, duration, budget (+unlimited
+ * when gated on), TPM/RPM in the Advanced accordion, and the post-generation
+ * screen with copyable key + starter snippets.
+ *
+ * Edit mode: the same shared fields but no duration (expiry is immutable after
+ * creation) and no team switch (LiteLLM /key/update semantics); adds a masked
+ * key header and the Danger Zone (reset spend). Budget validation, the
+ * unlimited toggle and the team-scoped model filtering behave exactly as they
+ * do at creation time.
+ */
+export type KeyFormDialogMode = 'create' | 'edit';
+export interface KeyFormDialogProps {
+    open: boolean;
+    onClose: () => void;
+    /** `create` generates a new key; `edit` updates an existing one. */
+    mode: KeyFormDialogMode;
+    /** Key being edited (edit mode only). */
+    keyToEdit?: VirtualKey | null;
+    keys: VirtualKey[];
+    models: ModelInfo[];
+    teams: TeamInfo[];
+    /** Current user's LiteLLM user id, used to pre-fill a default key alias. */
+    username?: string;
+    /** Controls for the key form; see litellm.keyGeneration in app-config.yaml. */
+    keyGenerationSettings?: {
+        allowUnlimitedBudget: boolean;
+        teamRequired: boolean;
+    };
+    onCreateKey: (request: GenerateKeyRequest) => Promise<GenerateKeyResponse>;
+    onUpdateKey: (keyId: string, request: UpdateKeyRequest) => Promise<void>;
+    onResetKeySpend?: (keyId: string) => Promise<void>;
+    onGetConfig: () => Promise<LiteLlmConfig>;
+}
+export declare const KeyFormDialog: React.FC<KeyFormDialogProps>;
+export declare function fmtCost(perToken?: number): string | null;
+export declare function formatContextWindow(maxInput?: number, maxOutput?: number): string | null;

package/dist/components/KeysTable.d.ts

@@ -1,15 +1,14 @@
 import React from 'react';
-import { VirtualKey, ModelInfo, UpdateKeyRequest } from '../types';
+import { VirtualKey } from '../types';
 interface KeysTableProps {
     keys: VirtualKey[];
-    models: ModelInfo[];
-    /** Opens the shared "Generate New Key" dialog (rendered at page level). */
+    /** Opens the shared key form dialog in create mode (rendered at page level). */
     onGenerateKeyClick: () => void;
+    /** Opens the shared key form dialog in edit mode for the given key. */
+    onEditKey: (key: VirtualKey) => void;
     loading: boolean;
-    onUpdateKey: (keyId: string, request: UpdateKeyRequest) => Promise<void>;
     onBlockKey: (keyId: string) => Promise<void>;
     onUnblockKey: (keyId: string) => Promise<void>;
-    onResetKeySpend: (keyId: string) => Promise<void>;
     onDeleteKey: (keyId: string) => Promise<void>;
     onPruneExpiredKeys: () => Promise<{
         pruned: number;

package/dist/components/LiteLLMBudgetGauges.d.ts

@@ -1,19 +1,26 @@
 /**
  * Condensed budget card for a homepage column: one ring gauge per
- * enforcement level (key → personal → team), each showing the limit nearest
- * its cap. Where the full `LiteLLMBudgetWidget` lists every limit as a
- * spend-vs-cap meter, this trades detail for density — a single row of rings
- * with a label and spend figure under each.
+ * enforcement level (key → personal → team) plus a month-to-date daily
+ * token-usage mini-chart, in a fixed four-column row. Each gauge shows the
+ * limit nearest its cap; where the full `LiteLLMBudgetWidget` lists every
+ * limit as a spend-vs-cap meter, this trades detail for density — a single
+ * row with a label and spend figure under each gauge, and the MTD token
+ * total under the chart.
  *
  * Gauges are always rendered in the same order, with an empty ring when the
  * user has no cap at that level, so the card keeps a stable shape as data
  * loads and across users. When a level holds several limits, the ring shows
  * the one closest to its cap and a "+N more" link counts the rest.
  *
- * The bottom action bar is composable: pass any subset of `ctas` — mint a new
- * key, open the LiteLLM module, or expand the full per-limit list in place —
- * in the order you want. `action` remains an escape hatch for a fully custom
- * node; when either is present it renders below a divider.
+ * The usage period is frozen to month-to-date (no period selector): the
+ * chart always covers the 1st of the current month through today.
+ *
+ * The bottom action bar is composable: pass any subset of `ctas` — generate
+ * a new key, open the LiteLLM module, or expand the full per-limit list in
+ * place — in the order you want. `action` remains an escape hatch for a
+ * fully custom node; when either is present it renders below a divider. The
+ * `new-key` CTA renders the shared `GenerateKeyButton`, identical to the
+ * one on the plugin page.
  */
 import React from 'react';
 /** Preset action-bar buttons. `label` overrides the default copy. */
@@ -35,8 +42,9 @@ export interface LiteLLMBudgetGaugesProps {
     /** Where the module CTA points. Defaults to the LiteLLM page. */
     moduleHref?: string;
     /**
-     * Called when the "new key" CTA is used. When omitted, the CTA deep-links
-     * to the module with `?generate=1`, which opens the generate-key dialog.
+     * Called when the "Generate New Key" CTA is used. When omitted, the CTA
+     * deep-links to the module with `?generate=1`, which opens the
+     * generate-key dialog.
      */
     onCreateKey?: () => void;
     /**
@@ -56,4 +64,9 @@ export interface LiteLLMBudgetGaugesProps {
     /** Fully custom node pinned below the CTAs, below a divider. */
     action?: React.ReactNode;
 }
+/** Month-to-date range as `YYYY-MM-DD` strings: the 1st of the current month through today. */
+export declare function monthToDateRange(now?: Date): {
+    startDate: string;
+    endDate: string;
+};
 export declare const LiteLLMBudgetGauges: React.FC<LiteLLMBudgetGaugesProps>;