rollingpin
rollingpin copied to clipboard
fast deploy to lots of servers
Bumps [cryptography](https://github.com/pyca/cryptography) from 2.3 to 41.0.3. Changelog Sourced from cryptography's changelog. 41.0.3 - 2023-08-01 * Fixed performance regression loading DH public keys. * Fixed a memory leak when using :class:`~cryptography.hazmat.primitives.ciphers.aead.ChaCha20Poly1305`....
Bumps [twisted](https://github.com/twisted/twisted) from 17.5.0 to 22.10.0. Release notes Sourced from twisted's releases. Twisted 22.10.0 (2022-10-30) This release contains a security fix for CVE-2022-39348. This is a low-severity security bug. Twisted...
## 💸 TL;DR I have applied [Black](https://github.com/psf/black) to format everything in `rollingpin`. This makes the whole project more uniform and readable.
When monitoring #salon, graphs, issue collectors, event collectors, etc... it would be useful to have an audible/visible reminder that rollingpin needs attention.
adds support for a build step that can be triggered on the code host after a build is complete.
``` dan@my-deploy-server-01:~$ rollout foo rollout -h apps --parallel=100 --timeout=60 -d foo -r all ``` In this case, if I try to run the expanded command, it fails with: ``` usage:...
e.g. `-c puppet` should work on the build host. Maybe we should just have the deploy script accept and ignore them?
To improve consistency, we should allow the -d commands to follow the same ordering as the rest.