In the previous chapters, you learned how to write patterns for modules and dependencies. You also applied some general practices for writing infrastructure as code and sharing modules. The patterns, practices, and workflows had a lot of steps.
Furthermore, many of the workflows require careful coordination of changes. One day, you might try to make a change only to find out that your teammate’s updates might overwrite yours! How do you make sure you manage conflicts during the development process?
One solution involves submitting change requests to a ticketing system. For example, if you want to change a server, you’d need to fill out a change request in your ticketing system. This change request then gets reviewed by your peers (usually your team) and the change advisory board (on behalf of the company).