Except it isn’t actually YAML you’re writing, it’s a jinja2 string template that parses to YAML because the expressions they came up with ended up not being sufficient.
No. Because the python version of the host and the target server must loosely match up. Otherwise you get some cryptic error messages in some unexpected modules.
Red Hat’s solution: just manage RHEL 9 targets from RHEL9 hosts and RHEL8 from RHEL8 hosts. There is no official way to align python versions across that major.
“Keep it simple” says the project that decided it would be great to program in YAML…
I’ve tried using it to manage a few home servers and parameterizing anything was painful and boilerplate-ridden
Except it isn’t actually YAML you’re writing, it’s a jinja2 string template that parses to YAML because the expressions they came up with ended up not being sufficient.
Mm, I love stacking weird formats. How many backslashes do I need for a regular expression to work right? 🥵
Well it’s bash down the line so I’ll say five.
Jist wait until you have to start fucking around with multiple incompatible versions of python for different targets.
They’re being treated for PTSD in solaris-land.
Yeah. I said solaris.
Because group or host vars are hard?
No. Because the python version of the host and the target server must loosely match up. Otherwise you get some cryptic error messages in some unexpected modules. Red Hat’s solution: just manage RHEL 9 targets from RHEL9 hosts and RHEL8 from RHEL8 hosts. There is no official way to align python versions across that major.
That’s not entirely true. You could use Ansible Navigator and Execution Environments.
I seem to remember having the same trouble, maybe with hiding vars from logs?