pala46/azure-inventory-dashboard

Purpose and Runtime

Azure Inventory Dashboard is a live, read-only Azure subscription inventory system. A React/Vite browser client calls a FastAPI REST API; the backend authenticates users with Microsoft Entra ID and queries Azure Resource Graph rather than maintaining an inventory database. Development runs Vite on :5173 and uvicorn on :8000; production FastAPI can serve the built frontend.

Paths: backend/app.py, frontend/src/main.jsx, frontend/vite.config.js

Application Composition and Entry Points

backend.app:app is the server entry point: it assembles API routes, error handling, health behavior, and optional static frontend hosting. The React entry mounts the application, while the top-level app owns routing, shared layout, and page selection. Convenience launchers provision and start both runtimes.

Paths: backend/app.py, frontend/src/App.jsx, run.sh

Authentication Boundary

The frontend is gated by auth state and never accesses Azure directly. Auth endpoints expose status, initiate interactive browser login, and clear the in-memory session. Backend authentication encapsulates InteractiveBrowserCredential, persisted OS token caching, MFA-capable browser flow, token-claim user extraction, and thread-pool handling for its synchronous credential calls. Failed Azure authentication is translated to a client-facing 401.

Paths: backend/auth.py, backend/routes/auth.py, frontend/src/context/AuthContext.jsx

Azure Query Layer

Azure access is centralized behind a reusable Resource Graph client and Kusto-query definitions. Request handlers invoke this layer on demand against the configured subscription; there is no database, scheduled scan, or backend inventory persistence. This isolation is the intended insertion boundary for caching, persistence, alternate credentials, or multi-subscription support.

Paths: backend/azure_client.py, backend/resource_graph.py, backend/config.py

API Domain Stages

The API is organized by inventory domain. Dashboard routes compose summary metrics, charts, and curated lists; resource routes implement paginated listing, filtered global search, full resource detail, and relationship discovery. Category routes issue targeted Resource Graph queries for compute, storage, database, network, containers, security, monitoring, resource groups, and tags.

Paths: backend/routes/dashboard.py, backend/routes/resources.py, backend/routes/compute.py

Frontend Data and Presentation Flow

Pages fetch REST data through the shared Axios client and data-fetch hook, rendering reusable tables, charts, loading/error states, and export controls. Auth and refresh contexts coordinate session gating and reload behavior across routes. Detail and search pages consume the generic resource APIs; category pages consume their corresponding domain endpoints.

Paths: frontend/src/api/client.js, frontend/src/hooks/useApi.js, frontend/src/pages/ResourceDetail.jsx

External Services and Deployment Boundaries

Microsoft Entra ID supplies interactive authentication; Azure Resource Graph supplies all inventory data and requires subscription Reader-level query access. The client uses Bootstrap-oriented UI components and Chart.js visualizations. In development, Vite proxies /api to FastAPI; in deployment, a reverse proxy such as nginx/Caddy provides TLS ahead of uvicorn, while FastAPI may host frontend/dist.

Paths: frontend/package.json, frontend/vite.config.js, backend/.env.example