4 ms·
Your first concern is addressed by saltstack - they chose an agent based approach, with client subscription, as the default, which makes for a significantly fas
by Jedd 5y ago
Your first concern is addressed by saltstack - they chose an agent based approach, with client subscription, as the default, which makes for a significantly faster experience.
They subsequently offered an ssh-based option for those that wanted the poor performance of Ansible across larger fleets, or where agents were not palatable.
Unfortunately it doesn't address your second concern, as it also uses yml + jinja.
- takeda 5y agoI wish saltstack would be more popular. It's so far the best one I used (I didn't use Puppet and CFEngine). As for the second concern, you actually kind of can: https://docs.saltproject.io/en/latest/ref/renderers/ https://docs.saltproject.io/en/latest/ref/renderers/ yaml never bothered me, so I just used it, but you could use a different one. I suppose none of the ones from the list would make parent poster happy, but then one could write own renderer.
- takeda 5y agoCame too late, so can't edit anymore, but here's an example of a custom renderer, that allows writing states using java properties format: https://github.com/saltstack/salt-contrib/blob/master/renderers/jproperties.py https://github.com/saltstack/salt-contrib/blob/master/render...
- Jedd 5y agoI agree - Saltstack felt like a significantly superior design, but alas the RHEL effect won out.
- deleted 5y ago[deleted]