Backlog
Investigations and plans waiting for implementation, sorted by last updated date.
| Document | Goal | Updated |
|---|---|---|
| Platform Roadmap | Track prioritized investigations and planned work for the UIS platform | 2026-05-01 |
| NOTE — Response to Atlas's PostgREST verification findings (2026-04-28) | — | 2026-05-01 |
| NOTE — PostgREST verification findings from Atlas (2026-04-29) | — | 2026-05-01 |
| NOTE — PostgREST documentation review: approved (2026-04-29) | — | 2026-05-01 |
| INVESTIGATE: Version Pinning for Helm Charts and Container Images | Everything works today, but 18 of 21 Helm charts and several container images have no version pinning. Any upstream release — intentional or accidental — can break the system without warning. A single ./uis deploy could pull a new chart version with breaking changes. | 2026-05-01 |
| INVESTIGATE: Verification Playbooks Usage and Coverage | The ansible/playbooks/utility/ folder contains a mix of verification playbooks, task includes, setup helpers, and one-off utilities. Several of these files appear to have no active caller in the current repo. | 2026-05-01 |
| INVESTIGATE: Undeploy --purge flag | — | 2026-05-01 |
Investigate: ./uis deploy <service> semantics for services without a playbook | Decide what ./uis deploy <service> should do when the target service has SCRIPT_PLAYBOOK="" (and SCRIPT_MANIFEST="") — the "metadata-only" case introduced when service-postgrest.sh shipped without a playbook (PLAN-001 documentation gate; PLAN-002 will add the playbook). | 2026-05-01 |
| Investigate: UIS Connect Commands for All Services | Design and build uis connect <service> commands that open interactive clients into deployed services without requiring clients in the uis-provision-host image. | 2026-05-01 |
| Investigate: Version Metadata in Service Scripts | Decide how service scripts should expose version information for docs generation and CLI display | 2026-05-01 |
| INVESTIGATE: Remote Deployment Targets & Target Management | — | 2026-05-01 |
| INVESTIGATE: Provision-Host Tools and Provider Authentication | — | 2026-05-01 |
| Investigate: PostgREST as a UIS service | Decide whether and how to package PostgREST as a UIS service that turns a curated PostgreSQL schema into a public REST API, fitting the existing ./uis deploy flow and the contributor conventions in website/docs/contributors/. | 2026-05-01 |
| INVESTIGATE: Platform Provisioning Layer | — | 2026-05-01 |
| INVESTIGATE: Migrate Host Documentation to UIS CLI | — | 2026-05-01 |
| Investigate: Deploy Gravitee APIM 4.11 on PostgreSQL with a minimal footprint | Deploy Gravitee API Management on the UIS local cluster as a working API gateway with admin UI, using PostgreSQL as the management store and no Elasticsearch / no Redis / no MongoDB, on the smallest sustainable resource footprint. | 2026-05-01 |
| Investigate: First UIS Stack Template | Decide which UIS stack template to create first, then build it as the reference implementation for uis template. | 2026-05-01 |
| Notes for installing EspoCRM in UIS | — | 2026-05-01 |
| Investigate: Enonic Content Deployment | Determine how content (data) moves between Enonic environments and whether it can be automated | 2026-05-01 |
| Investigate: Enonic App Deployment Pipeline | Design and implement a pull-based pipeline for deploying Enonic apps (JAR files) into the Enonic XP instance running in UIS | 2026-05-01 |
| Investigate: Docs Markdown Generator Update Logic | Add logic to uis-docs-markdown.sh to update metadata-driven sections of existing markdown pages without overwriting manually written content | 2026-05-01 |
| Investigate: DCT One-Command ArgoCD Deployment | Enable a developer to deploy their current project to the UIS Kubernetes cluster from inside the DCT devcontainer with a single command. | 2026-05-01 |
| Investigate: UIS Container Pull Command | Add a ./uis pull command that pulls the latest provision-host container image and restarts the container | 2026-05-01 |
| Investigate: Backstage Developer Portal for UIS | Deploy Backstage as the developer portal for UIS, modeling all existing services in a software catalog | 2026-05-01 |
| Investigate: Backstage Enhancements | Evaluate and prioritize additional Backstage features beyond the initial deployment (PLAN-002) | 2026-05-01 |
| Investigate: Backstage Authentik OIDC Authentication | Investigate adding Authentik OIDC authentication to Backstage (replacing guest access) | 2026-05-01 |
| INVESTIGATE: Authentik User Config Migration | User-configurable Authentik data (test users, domains, protected services, OAuth apps) is hardcoded in manifests/ where users shouldn't be editing files. This data should live in .uis.extend/ so users can customize their setup without touching infrastructure code. | 2026-05-01 |