mig5/enroll.sh
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

enroll diff --enforce can take --target for specific config managers
All checks were successful
CI / test (push) Successful in 2m39s
Details

Browse source
This commit is contained in:
Miguel Jacq 2026-06-21 12:49:20 +10:00
parent 3e635c8e47
commit 89831d600b
Signed by: mig5
GPG key ID: 03906B4110AAD3B8
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
src/content/docs.html
View file

@ -359,7 +359,7 @@ ignore_package_versions = true
<div class="callout p-4 mb-3"> <div class="callout p-4 mb-3">
<div class="fw-semibold mb-1">Optional: enforce the old harvest state (<code>--enforce</code>)</div> <div class="fw-semibold mb-1">Optional: enforce the old harvest state (<code>--enforce</code>)</div>
<div class="small text-secondary mb-0">If drift exists and <code>ansible-playbook</code> is on <code>PATH</code>, Enroll can generate a manifest from the <em>old</em> harvest and apply it locally to restore expected state. It avoids package downgrades, and will often run Ansible with <code>--tags role_...</code> so only the roles implicated by the drift are applied. This is intentionally Ansible-based today, even when you also use Puppet or Salt rendering for normal manifests.</div> <div class="small text-secondary mb-0">If drift exists and your desired config manager is on <code>$PATH</code>, Enroll can generate a manifest from the <em>old</em> harvest and apply it locally to restore expected state, if you pass the <code>--enforce</code> argument to <code>enroll diff</code>. By default, it will try to use Ansible for that, but you can pass <code>--target [puppet|sops]</code> just like with <code>enroll manifest</code>.</div>
</div> </div>
<div class="terminal mb-4"> <div class="terminal mb-4">