ansible-skills-admin

To prevent configuration drift across distributed Ansible gateways, you must enforce a canonical repository as the single source of truth for skill configurations. This ensures runtime skill mirrors match the canonical version by verifying deployments and reconciling differences through drift cleanup workflows.

The best way to synchronize Ansible skill deployments is to use standard workflows for editing, committing, pulling, verifying, and restarting gateways. This approach enforces a canonical repository policy for golden source management and verifies local runtime mirror parity.

You can verify that your local runtime skill mirror matches the canonical Ansible version by running required checks for canonical clean state and local runtime mirror parity. The skill provides deployment verification mechanisms to ensure runtime mirrors match the canonical repository.

You need to run drift cleanup procedures for Ansible skills when required checks detect discrepancies between your canonical clean state and local or VPS runtime mirror parity. The skill provides triage procedures to reconcile these detected differences and restore consistency across gateways.

Yes, you can manage the entire lifecycle of Ansible skills on VPS instances. The skill handles source-of-truth edits, mirror synchronization, deployment verification, and drift cleanup, including required checks for VPS mirror parity to ensure consistency.