Matthias SchmidtSpent the Sunday morning updating my personal #ansible playbooks. Man, these guys keep on deprecating quite a lot :)
Now, all my #OpenBSD servers get their configuration without the usage of deprecated variables.
Klaus Umbach@xhr We all love to deprecate stuff! But we all hate it, if others do it.
@treibholz TBH I love it when people do yak shaving. But not caring about playbooks for 2y means work for me :)
@xhr feel free to use a "stable" virtualenv with a lot of pinned old versions in requirements.txt - seems to be "Industry Standard" anyway... All the major security professionals seem to do it. They can't be wrong!
@treibholz No that you mention it!!1elf
@xhr I'm currently learning to like uv. I have to debug a python3.9-script. The dependencies have deprecated many things and the old ones don't work on modern python3. And as upgrading the "machine" is not an option anyway, I have a python3.9 virtualenv for local development.
```
[root@kindle root]# uptime
21:20:38 up 1038 days, 18:56, load average: 0.00, 0.02, 0.00
[root@kindle root]# uname -a
Linux kindle 2.6.31-rt11-lab126 #5 Sat Jan 12 20:39:09 PST 2013 armv7l unknown
```
Tall Simon@xhr Glad to hear I'm not the only one. I started using Ansible to simplify things, but after having a couple of years of relatively simple times, a lot of recipes stopped working with the next LTS update of Ubuntu.
(/me hears the 'verse echoing with "I think I see your problem".)
Sigh... Sunday should be Systemadminday...
@TallSimon The best ansible advice was given to me by a fellow coworker. Fix your playbooks, learn to trust them and run them always and often. This made things easier for me.
I didn't update parts of the playbooks for 2y, because the servers simply need no care. Benefit of running OpenBSD :) But yes, the Universe also echoed that back to me this morning ;)