Post #1144628

2026-04-13 21:26 UTC

@wild1145@mastodonapp.uk @philcowans@universeodon.com several points: * You can find out if an apt upgrade needs reboot. I don't know the details, but the info is somewhere. * You can define Ansible variables per machine, including the user used to connect with. * You can bootstrap an Ansible user with an arbitrary sudoer user, like https://gist.github.com/StyXman/0003d9f903edb0dc12a3ac561a37c8df #Ansible

Replies (1)

@wild1145@mastodonapp.uk 2026-04-14 08:04

@mdione@en.osm.town @philcowans@universeodon.com Sorry I should have been more clear, I am aware I could make ansible work for this, but right now we don't use ansible and I'm very aware of the huge amount of limitations ansible as a stack has (And patch management isn't something it's designed to do). The goal here was not to need to spend a huge amount of time and energy making my own solution because it seems like the sort of problem a lot of smarter people would have already solved. The reality is I'd like in the future to get to the point where all our services are managed and provisioned by ansible, but that's a hell of a lot of work and isn't really the answer I'm hoping for when it comes to my "How do I automate patch management" or get anywhere close to some sort of centralised view on patch management across my servers.

Open ##1144627