feat(dashboard): integrate PymtHouse usage, API keys, and discovery#3
Open
eliteprox wants to merge 17 commits into
Open
feat(dashboard): integrate PymtHouse usage, API keys, and discovery#3eliteprox wants to merge 17 commits into
eliteprox wants to merge 17 commits into
Conversation
- Implemented `usage-capability-display.ts` for displaying account usage capabilities with color coding and data distribution. - Created `useAccountUsage.ts` hook to manage account usage state and fetch usage data. - Added `useApiKeys.ts` for managing API keys with create and revoke functionality. - Introduced `useDiscoveryModel.ts` and `useExploreModels.ts` for fetching and managing discovery models. - Developed `useSigningSession.ts` for handling signing sessions and token management. - Added discovery client functions in `client.ts` for fetching capabilities and models. - Created configuration and constants files for discovery service. - Implemented mapping functions for transforming discovery capabilities to models. - Defined types for discovery service API responses. - Updated package dependencies and added type definitions for jmuxer and mux.js.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…a visualization - Updated StackedAreaChart to support Y-axis ticks, horizontal grid lines, and per-day hover tooltips. - Integrated dayKeys prop for better date handling in the chart. - Modified UsageView to utilize new daily data structure, including dynamic period day count and improved data fetching. - Added utility functions for generating UTC date keys and aligning daily request series with OpenMeter data. - Introduced tests for new utility functions to ensure correctness in date handling and data alignment.
- Changed dependency from local link to versioned package for @pymthouse/builder-sdk in package.json and pnpm-lock.yaml. - Updated lock file to reflect the new version and its peer dependencies.
- Added new environment variable `GATEWAY_SIGNER_FROM_REQUEST_ORIGIN` to control signer URL behavior. - Implemented API route rewrites for orchestrator info, discovery, and payment generation to use the dashboard's signer proxy. - Refactored session handling in the API to read configuration from the request context. - Introduced a new signer proxy handler to forward requests based on allowed paths. - Updated the LiveStreamPlayground component to optimize sleep intervals for better performance. - Adjusted gateway configuration functions to support request-based signer URL resolution.
…up related code - Deleted unused gateway session API routes and related handlers to streamline the codebase. - Removed references to the LiveStreamPlayground component and associated gateway checks from the playground tab. - Cleaned up environment variables in `.env.example` by removing obsolete gateway configurations. - Updated the `next.config.ts` to eliminate unnecessary rewrites related to the gateway. - Enhanced the API key exchange configuration to include audience requirements for improved security. - Refactored the CodeSnippets component to simplify snippet generation without gateway dependencies.
- Eliminated the audience parameter from the API key exchange configuration in both exchange routes to simplify the code and avoid reliance on deprecated functionality.
- Updated the fetchAccountUsageForExternalUser function to include the `includeRetail` parameter for both current and prior usage data requests, enhancing the data retrieval capabilities for external users.
- Changed dependency from local link to versioned package for @pymthouse/builder-sdk in package.json and pnpm-lock.yaml. - Updated lock file to reflect the new version and its peer dependencies.
- Added `dynamic` export to force dynamic rendering for live data. - Implemented `NO_STORE_HEADERS` to prevent caching of account usage responses, ensuring users always receive the latest data. - Updated the `GET` method to include these headers in both successful and error responses. - Modified the `useAccountUsage` hook to fetch account usage data with `cache: "no-store"` to align with the new caching strategy.
- Updated dependency for @pymthouse/builder-sdk in package.json and pnpm-lock.yaml to the latest version 0.4.3. - Adjusted lock file to reflect the new version and its integrity hash.
# Conflicts: # app/(app)/apps/[id]/page.tsx # app/(app)/layout.tsx # app/(app)/page.tsx # components/dashboard/KeysView.tsx # components/dashboard/UsageView.tsx
Adopt direct signer DMZ integration: bump builder-sdk from 0.4.3, remove the dashboard /api/signer proxy route, and return signerUrl from exchange handlers only when PYMTHOUSE_SIGNER_URL (or SIGNER_PUBLIC_URL) points at the remote signer DMZ base — not a dashboard proxy path.
eliteprox
changed the title
Updated the @pymthouse/builder-sdk dependency in package.json and pnpm-lock.yaml to version 0.4.6, reflecting the latest changes and integrity hash.
Drop the OIDC device-flow routes, device-approved page, and login UI branches from this branch so PR #3 stays focused on API keys, usage, discovery, and signing. Relocate createPmtHouseClientForPublicApp into pymthouse-bff so remaining BFF routes keep working without device-flow.ts.
eliteprox
changed the title
4 tasks
Updated the layout components for both the app and auth sections to utilize AuthProvider instead of the now-removed DashboardProviders. This change simplifies the authentication context management. Additionally, modified the .env.example file to clarify the purpose of PymtHouse configuration variables and removed deprecated signing token API and related components to streamline the codebase.
…environment configuration - Added support for live runner integration, including new API routes for managing signer sessions and forwarding requests to the runner gateway. - Introduced `RunnerGatewayProvider` and context to manage live runner state in the playground. - Updated `.env.example` to include `RUNNER_DISCOVERY_URL` for local development. - Bumped `@pymthouse/builder-sdk` dependency to version 0.5.0, reflecting changes in the SDK for live runner support. - Enhanced playground code snippets to accommodate live runner calls and external user ID handling.
…ent configurations - Updated `.env.example` to reflect new PymtHouse URLs for production and local development. - Introduced new API routes for handling live runner capabilities and improved playground functionality. - Enhanced routing in `next.config.ts` to support dynamic paths for app management. - Added new components and context for managing live runner state in the dashboard. - Improved error handling and response parsing in API interactions for better reliability.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Wire the dashboard to PymtHouse backend services: live account usage from OpenMeter, API key management, and a discovery-backed model catalog — replacing mock data and deprecated gateway paths.
Device-code login (OIDC device flow for CLI/python-gateway) is split into a follow-up stacked PR (#7) on top of this one.
Usage
useAccountUsagehook and/api/pymthouse/account-usageBFF route withno-storecaching for live data.usage-capability-display.tsfor capability breakdowns, color coding, and UTC date-key alignment with OpenMeter daily buckets.UsageViewandStackedAreaChartfor per-day visualization (Y-axis ticks, grid lines, hover tooltips, dynamic period length).SidebarUsageCardto show real balances.API keys
useApiKeyshook and/api/pymthouse/keysBFF route for create/revoke./api/pymthouse/keys/exchangeBFF facade so CLI clients (e.g. python-gateway via--billing-url) can exchange an API key for a signer session.signerUrlfrom the exchange handler only whenPYMTHOUSE_SIGNER_URL(orSIGNER_PUBLIC_URL) points at the remote signer base.KeysViewto use live key data instead of mocks.Discovery & explore
map-to-modeltransforms./api/discovery/explore,/api/discovery/models/[id]).useExploreModels,useDiscoveryModel, andExploreViewto the discovery service.Cleanup
LiveStreamPlayground, and related env/config.CodeSnippetswithout gateway dependencies.Config
Env vars documented in
.env.example:PYMTHOUSE_ISSUER_URL,PYMTHOUSE_PUBLIC_CLIENT_ID,PYMTHOUSE_M2M_CLIENT_ID,PYMTHOUSE_M2M_CLIENT_SECRET,PYMTHOUSE_SIGNER_URL.Test plan
POST /api/pymthouse/keys/exchange) returns a signer session