this post was submitted on 14 Jan 2025
403 points (92.1% liked)
memes
10963 readers
4694 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to [email protected]
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads
No advertisements or spam. This is an instance rule and the only way to live.
Sister communities
- [email protected] : Star Trek memes, chat and shitposts
- [email protected] : Lemmy Shitposts, anything and everything goes.
- [email protected] : Linux themed memes
- [email protected] : for those who love comic stories.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
"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
Jist wait until you have to start fucking around with multiple incompatible versions of python for different targets.
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.
They're being treated for PTSD in solaris-land.
Yeah. I said solaris.
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.
I seem to remember having the same trouble, maybe with hiding vars from logs?