Synchronizations
Synchronizations
Open Platform as Code → Synchronizations to reconcile Git manifests with platform resources in Axio. Synchronizations discover YAML, validate schemas, build a sync plan, apply changes (with approval when required), and record results in Recent runs.
Prerequisites
A Git repository connected under Administration → Integrations → Source Control with manifests under the configured working directory (default platform-config). Administrators (pac:manage) configure schedules and approve plans; scoped Members can run Sync now on Admin-configured repositories.
Git is the source of truth for Git-managed resources. The first Sync now on a connected repository registers it for Platform as Code reconciliation automatically. Removing a manifest from Git may stage a pending removal — review under Pending removals and approve sensitive changes before they apply.
What are Synchronizations?
Synchronizations compare desired state in Git with live platform resources. For each run Axio discovers YAML/JSON manifests, validates schemas and dependencies, previews a plan, and applies creates, updates, or staged deletions. Successful runs update Resources inventory and appear in sync history.
Connected repositories
Each row shows repository, provider, branch, schedule, last sync, and status. Actions:
- Auto — Enable or disable scheduled reconciliation (Administrators)
- Interval — Poll frequency when Auto is on
- Sync now — Immediate run (Administrators and scoped Members)
- Remove — Delete PaC sync configuration for the repo (Administrators)
Best Practices
- Keep manifests focused — one resource per file or logical grouping under
platform-config/. - Use descriptive commit messages; each sync run records the commit SHA.
- Enable Auto on production repos or run Sync now after merging manifest changes.
- Review Recent runs validation and approval columns before assuming apply succeeded.
- Declare parent resources (Project → Workspace → Environment) before children, or sync all manifests together.
- Use
metadata.sensitive: truedeliberately — it triggers approval for Git-driven updates and deletions.
Run Sync now after important Git changes or when Resources show drift. Search repositories and recent runs using the search boxes on this page. For schema reference before editing manifests, use Catalog.
Recent run columns:
- Trigger — Manual, scheduled, or webhook-driven
- Approval / Validation — Plan gate and schema outcome
- Changed — Count of resources created, updated, or deleted
- Summary — Plan overview; click a row for full details