what to do with making changes to the software automation?

 The answer is simple - automation is essentially a code, we use the Infrastructure as Code approach. More precisely, we have Infrastructure as Code as a development process, and this is not the same as Infrastructure as Scripts, as is very often the case. Accordingly, to simplify planning and work, we are starting to apply classical development practices: we are working on a component model of the code that describes our infrastructure, we are working on the formats and sequences of messaging in our infrastructure (for example, which script pulls which hooks and what transmits), we are building a release process for the infrastructure code, we are working on the feature backlog - in a word, we work with the infrastructure as if it were another component of the application.