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

news updates
All checks were successful
CI / test (push) Successful in 2m36s
Details

Browse source
This commit is contained in:
Miguel Jacq 2026-06-21 15:36:33 +10:00
parent 7cda9a0519
commit 277249c4c5
Signed by: mig5
GPG key ID: 03906B4110AAD3B8
1 changed files with 5 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

9
src/content/news/0-7-0.html
View file

@ -24,14 +24,13 @@ summary: "Enroll can now render Puppet and Salt manifests alongside Ansible, det
<ul>
<li><strong>Puppet support!</strong> <code>--target puppet</code> renders Puppet module/control-repo style output., and in <code>--fqdn</code> mode, renders per-host Hiera data.</li>
<li><strong>Salt Stack support!</strong> <code>--target salt</code> renders Salt state trees and, in <code>--fqdn</code> mode, Salt pillar data.</li>
<li>Ansible works basically as it always did, and is the default, but you can specify <code>--target ansible</code> too.</li>
<li>Evaluating how different config managers work? You can rendered repeatedly into different config management tools without re-harvesting the host, because they all use the same harvest state!</li>
<li>Single-site output tries to combine package/service data by their package manager's <code>Section</code> (or equivalent metadata), to reduce role/module/state sprawl and speed up execution.</li>
<li>Single-site output tries to combine package/service data by their package manager's <code>Section</code> category, to reduce role sprawl and speed up execution.</li>
<li>Flatpak and Snap detection!</li>
<li>Docker image detection!</li>
</ul>
<h2 class="h4 fw-bold mt-4">Dry-run examples: choose your own config management adventure!</h2>
<p>Feels too good to be true, but it isn't:</p>
<div class="codeblock terminal">
<button class="btn btn-sm btn-outline-secondary copy-btn" data-copy-target="#news-070-noop"><i class="bi bi-clipboard"></i> Copy</button>
<pre class="mb-0"><code id="news-070-noop"><span class="prompt">$</span> enroll harvest --out ./harvest
@ -50,10 +49,12 @@ summary: "Enroll can now render Puppet and Salt manifests alongside Ansible, det
<p>I recommend using Salt 3008.1 - on Debian 13 I encountered annoying noisy Python errors with version 3007, which are unrelated to Enroll.</p>
<p>Bonus: since Salt uses Jinja2 templates, it will take advantage of my other tool <a href="https://git.mig5.net/mig5/jinjaturtle" target="_blank" rel="noopener noreferrer">JinjaTurtle</a>, if it's on your <code>PATH</code>, just like Ansible does!</p>
<p>Since Salt uses Jinja2 templates, it will take advantage of my other tool <a href="https://git.mig5.net/mig5/jinjaturtle" target="_blank" rel="noopener noreferrer">JinjaTurtle</a>, if it's on your <code>PATH</code>, just like Ansible does.</p>
<p>And because I didn't want Puppet users to feel left out, version 0.5.5 of JinjaTurtle (despite its name) also supports <code>erb</code> templates as well. This means Puppet templates will be generated if you have JinjaTurtle and there are viable config files for it, too!</p>
<p>Have you used <code>enroll diff --enforce</code> to enforce reverting a system to an older harvest state via Ansible? Well, that works too for Puppet or Salt - just add <code>--target [salt|puppet]</code> to that command.</p>
<h2 class="h4 fw-bold mt-4">New grouping behaviour in roles/modules</h2>
<p class="text-secondary">Did you find the number of manifested roles overwhelming?</p>
<p>Previously, Enroll created an Ansible role (or, now, a Puppet module or Salt role) for pretty much every 'package' it found. In some cases this could result in hundreds of roles.</p>