Manage Infrastructures

Use /admin/common/infrastructures to verify infrastructure registry and control-plane sync health.

What this page is for

  • Confirm infra metadata (name, region, API base URLs, status)
  • Observe Common synchronization health from each infra
  • Trigger authz snapshot sync when drift or lag appears

Common sync status

Each row includes a Common sync summary:

  • authz <age>: staleness of authz snapshot sync
  • repos <age>: staleness of repo provisioning sync
  • fail <n>: consecutive failures for that sync track

If ages increase unexpectedly or failure counters rise, investigate infra-to-Common connectivity immediately.

Safe operations

  1. Verify api_base_url is browser-reachable for operators.
  2. Verify service_api_base_url is valid for service-to-service routing where used.
  3. Keep infrastructure status accurate (ACTIVE when usable).
  4. Use Sync now only when you need deterministic refresh after control-plane changes.

Failure triage

  • error in sync cell usually means auth or network failure from infra to Common.
  • Persistent repo sync failures often correlate with tenant repos stuck in PROVISIONING.
  • Fix environment wiring first, then re-run sync.