Post #1144630
2026-04-13 12:37 UTC
@philcowans@universeodon.com So that's my other option, my reason for trying to avoid it is it won't highlight when I need to go reboot machines or anything like that. And I'll also need to go through and change how auth works as right now each server has unique creds which will be moderately difficult (IIRC) to map into ansible. But equally it might be the best way forward and just run the playbook on a cron.
Replies (1)
-
@mdione@en.osm.town 2026-04-13 21:26
@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