Mapping out the process

The DevOps team had already settled on two different potential solutions for applying GitOps practices to their delivery process. One of the tools, Ansible, is open source and allows the team to achieve their GitOps requirements without any licensing cost. The other tool, Harness, is not an open source tool and requires the company to purchase licenses. Harness also allows the team to achieve continuous delivery with GitOps, and with significantly less setup, configuration, and administration than Ansible.

As the deliberation over whether Harness will be purchased or not continues, the DevOps team is finding that they have less and less time to get their first iteration of the process ready and usable by the other engineers. To make the solution setup and configuration easier, they decide to map out their process, tools, platforms, security requirements, and so on. They know that a cloud platform and their data centers will all need to be supported. The artifacts...