Designing safe, concurrent change automations
So far, we have shown how to execute commands locally or remotely.
In the modern day, we often need to run sets of commands across multiple systems to achieve some end state. Depending on your scale, you may want to run a system such as Ansible or Jenkins to attempt to automate these processes.
For some work, it is simpler to use Go directly to execute changes across a set of systems. This allows the DevOps group to simply understand the Go language and a small bit of code versus understanding the complexities of a workflow system such as Ansible, which requires its own skillset, system updates, and so on.
In this section, we are going to talk about the components of changing a set of systems, a framework for achieving this, and an example application to apply a set of changes.
Components of a change
When writing a system that makes a change, there are several types of actions that must be dealt with. In broad terms, I define...
