ReconcileTenantRegistry
Finds tenants that a parent lists but the system registry lacks (GetTenants -r vs -a) and, with --apply, inserts the missing registry rows. Dry run by default.
Examples
Dry run: report what would be inserted and any conflicts:
octo-cli -c ReconcileTenantRegistry
Insert the missing system registry rows:
octo-cli -c ReconcileTenantRegistry -a
Options
| Short | Long | Required | Description |
|---|---|---|---|
-a | --apply | no | Write the missing system registry rows. Without it the command only reports (dry run). |
Notes
A tenant that its parent lists (GetTenants -r) but that has no row in the system registry (GetTenants -a) is invisible to client mirror provisioning, token cleanup, CORS and health checks. Rows are only inserted, never changed or deleted; rows that disagree with the parent's registry and registries that cannot be read are reported as conflicts and left alone. A second --apply inserts nothing.
Only answered on the system tenant (user tokens need AdminPanelManagement), otherwise HTTP 403. Needs an asset-repo service that has the route; an older service answers 404.
Runbook: run without --apply, review the inserts and conflicts, run with --apply, then re-run the client mirror backfill (ProvisionClientInExistingTenants).