Background
The Fabric/PowerBI path is ongoing but slow to iterate. This spike explores building a lightweight, read-only reporting app on our existing stack.
Proposed approach
pay-insights-ui — Nuxt, reusing sbc-common-components (header, login, session)
pay-insights-api — Flask, deployed in the existing pay GCP project
Data — read-only service account on the data warehouse; reuse the SQL already written for the Fabric notebooks
Access — a "PAY Insights" tile on the sbc-auth staff dashboard; Keycloak SSO (no second login); new role pay_insights_viewer (or reuse existing roles); the API enforces JWT + role on every endpoint
Deployment — same GitHub CI/CD as express-checkout
Background
The Fabric/PowerBI path is ongoing but slow to iterate. This spike explores building a lightweight, read-only reporting app on our existing stack.
Proposed approach
pay-insights-ui — Nuxt, reusing sbc-common-components (header, login, session)
pay-insights-api — Flask, deployed in the existing pay GCP project
Data — read-only service account on the data warehouse; reuse the SQL already written for the Fabric notebooks
Access — a "PAY Insights" tile on the sbc-auth staff dashboard; Keycloak SSO (no second login); new role pay_insights_viewer (or reuse existing roles); the API enforces JWT + role on every endpoint
Deployment — same GitHub CI/CD as express-checkout