Repository navigation
tech-debt: relocate ProviderFallbackView/SystemHealthView from autobot-frontend into SLM #12637
Description
Activity
Picked this up as a decision-free relocation and stopped — it is not one. There is a translation-coverage blocker the issue does not mention.
Finding
Both views are fully translated in all 11 locales of the main frontend:
autobot-frontend/src/i18n/locales/ -> 11 files ar de en es fa fr he lv pl pt ur -> admin.systemHealth present in ALL 11The SLM frontend has one:
autobot-slm-frontend/src/locales/ -> en.json (only)So "relocate + re-wire router/nav/i18n, no behaviour change" cannot hold as written: moving these views as-is would drop them from 11 languages to 1. That is a user-visible regression, and it runs straight into the standing rule that UI strings must be translated across all 11 locales.
The decision this needs
- Port the i18n infrastructure + all 11 locale files into the SLM frontend first, then relocate. Preserves coverage, but is a substantially larger piece of work than a view move — and it implies the SLM control plane becomes a fully localised app, which is a product call.
- Accept English-only for admin surfaces and relocate now, explicitly recording that admin tooling is not localised.
- Leave them in place and treat "admin tooling belongs in SLM" as satisfied by proxying rather than relocating.
Option 2 is the only one that keeps this a small change, and it is a deliberate product decision about whether admin UI is localised — not something to settle as a side effect of a tech-debt move.
Leaving unclaimed pending that call. Everything else about the move is mechanical: 2
.vuefiles, 2 specs, a router entry each side (autobot-frontend/src/router/index.ts:871,883), and the manualnavItemsentry inApp.vue.
Discovered during umbrella #12630. Rule: admin tooling belongs in the SLM control plane.
ProviderFallbackView.vueandSystemHealthView.vuecurrently live inautobot-frontend/src/views/(the managed-service frontend), not inautobot-slm-frontend(the admin control plane). Relocate them into SLM monitoring so all admin surfaces are consistent. Out of scope for #12630; filed for a dedicated move (relocate + re-wire router/nav + i18n, no behaviour change).