Best practices first, then GitOps

The most important step that the DevOps team had taken over the months of testing different solutions was the process mapping. They had spent many hours interviewing different teams on what their requirements and common activities were, in the hope of being able to automate most, if not all, of it. The interviews covered the engineering teams, the quality assurance and testing teams, the security and compliance teams, and different persons in leadership. As the requirements and individual processes were documented and added together, the DevOps team had to sift through the resulting list and separate out the hard requirements from the nice-to-haves. The hard requirements were any that would prevent a deployment from being successfully rolled out, such as security scanning, dependency deployments, and compliance requirements. The rest of the requirements, such as testing, ticketing, approvals, and documentation, could be handled in a manual way until...