Backlog
Investigations and plans waiting for implementation, sorted by last updated date.
| Document | Goal | Updated |
|---|---|---|
Plan: Application catalogue entries (install_type: application) | Support a third entry kind in template-registry.json — an application, whose install | 2026-09-14 |
Investigate: Add inClusterPort to UIS services.json | Determine how UIS should surface the in-cluster port for each service it manages (the upstream Helm chart's default service port), so downstream consumers like TMP's template-registry generator and documentation builders can render accurate "pod connects to <service>.svc.cluster.local:<port>" labels and instructions without hardcoding. | 2026-09-14 |
| Investigate: Docusaurus Design Tweaks | Collect and track design improvements for the Docusaurus site. Each tweak is independent and can be implemented separately. | 2026-09-14 |
| Investigate: CI + Deployment Targets as First-Class Template Metadata | Make CI workflow + deployment target first-class fields in template-info.yaml, consumed by both documentation generators and actual deployment tooling, so that (a) the implicit .github/workflows/ convention becomes explicit, (b) Azure and future deployment targets slot in without a schema rewrite, and (c) the template page renders a concrete "builds via X, deploys to Y" line instead of leaving the reader to guess. | 2026-09-14 |
Investigate: Application catalogue entries in template-registry.json | Let template-registry.json carry a third entry kind — an application: a multi-service | 2026-09-14 |