My feedback for those who helped me or are interested in following up :)
Pyinfra was the perfect match.
I have used their "operations" to pile up the actions that come with the next release:
- A new package (apt)
- an updtated pip dependency
- checking a file
- and docker-compose actions to update all containers
I was able define my "inventory" easily, which allows me to update my whole fleet with one single command. One caveat here, the timeout is not properly configurable with a ProxyJump. Discussion opened on stackoverflow.
Pyinfra idempotency and dry-run approaches allow me to run the update as many times as I want.
For the next release, would I need to change anything different, I will simply add a new operation. The beauty of it is that all operations are strictly executed in the order I define them, which mean that any devices that would not have been updated with the first release, would be still updated appropriately with the second release.
Thanks for the idea ! I will try pyinfra first, which provides a way to connect to the fleet and then to execute a whole set of scripts. Whereas Dependabot's perimeter looks more contained on dependencies update.
1) yes, docker containers are immutable. The pain comes more from updates that are around them
2) Trying pyinfra. Thanks for pointing it to me ! Looks promising indeed :)
- [OK] Time Tree: a (basic) shared calendar will fill up the requirements quite nicely with reccuring events and nice views of who will attend which events
- [KO] Calendly: which provides interesting feature to set up the events, but no view of who is going to attend when
- [KO] DigiCal, another shared calendar but could set up properly/simply a shared calendar
How would you use pyinfra to manage a fleet of edge devices ? The main difference with a park of servers being that the edge devices are mounted on vehicles and therefore switching on and off with their own rhythm each.
We cutrently get an alert from each device when an update is needed, ssh into it, and docker-compose the latest services.
Pyinfra was the perfect match.
I have used their "operations" to pile up the actions that come with the next release:
- A new package (apt)
- an updtated pip dependency
- checking a file
- and docker-compose actions to update all containers
I was able define my "inventory" easily, which allows me to update my whole fleet with one single command. One caveat here, the timeout is not properly configurable with a ProxyJump. Discussion opened on stackoverflow.
Pyinfra idempotency and dry-run approaches allow me to run the update as many times as I want.
For the next release, would I need to change anything different, I will simply add a new operation. The beauty of it is that all operations are strictly executed in the order I define them, which mean that any devices that would not have been updated with the first release, would be still updated appropriately with the second release.
Cheers !