Common and Infra Registration
This page is for SynckHub-managed deployments. Customer-operated Free Self-Hosting registers through the interactive initializer and stores its client-generated credential only on the customer host; do not put it in SynckHub inventory or Vault.
SynckHub-managed infrastructure deployments register with Common and authenticate using infra tokens.
Required wiring
On SynckHub hosts:
SYNCK_CONTROL_PLANE_BASE_URLSYNCK_CONTROL_PLANE_INFRA_TOKEN
Without valid wiring, provisioning/authz snapshot sync will fail.
Source of truth model
- Desired infra identity is in
inventory.yml(infra_region,public_hostname, status) - Generated infra IDs/tokens are stored in Vault maps
Normal lifecycle is driven by reconcile scripts/workflows, not manual UI data entry.
Post-freshdb recovery
If Common DB is reset, old infra tokens are invalid.
Re-mint and persist tokens through infra-ansible workflow before redeploying SynckHub nodes.
Lifecycle states
Use ACTIVE, DISABLED, RETIRED instead of deleting infra rows.
Deleting identity history makes audit and incident recovery worse.