DevOps App
The operator console — pods, logs, terminals, Helm releases, outbox backlogs, Service Bus, read-only SQL, feature flags, and links to the consoles used to operate Flow.
devops-app is the browser surface for operating a deployed environment. It holds no credentials:
operational panels read from devops-service, scoped to the region and subscription selected in
the header. Developer resources are a committed catalog of outside consoles and do not go through
the service.
- Domain
- Operations
- Kind
- Next.js application
- Lifecycle
- Active
- flowctl project
- None
- Stacks
- Runs on its own
- Source
- frontend/devops-app
Run it locally
Environment variables, the dev server, and what works without Cloudflare Access.
The views
What each page shows and which of them can change something.
The service behind it
Scope resolution, the registry, roles, and deployment.
Scope: region and subscription
The operator selects a region and a subscription. Dev and prod are where a service or app was deployed — they come from the catalog and show as tags on those entries, not as a third selector.
| Level | Where it comes from | Selectable |
|---|---|---|
| Region | The scope selector in the header | Yes |
| Subscription | The scope selector in the header | Yes |
| Environment | A tag on each catalog entry (pipeline stage) | No |
Selecting a scope writes ?region=…&subscription=… into the address bar, which makes a link to a
pod or a query carry the subscription it was read from.
What it does not do
Nothing here drains an outbox, deletes a dead letter, or writes a row. Peek reads Service Bus without consuming, the SQL session is read-only in Postgres itself, and the outbox view counts and lists recent rows.
The app writes in two places. A Helm rollback needs the admin role. The Feature Flags view — which edits flag values and their rollout strategies, creates features and applications, edits feature details, reveals API keys, and manages FeatureHub service accounts — needs the engineer role, which an admin also holds.