A manifest for execution

With the integration and configuration manifests built and all required plugins installed, the DevOps team was ready to move into one of the more difficult parts of continuous delivery: the pipeline execution. Each execution would leverage the integration and configuration manifests, as well as significant native Ansible capabilities. Some parts of the pipeline would need to run sequentially while other parts would be run in parallel. Approvals, health checks, and dry runs would all need to be defined in code as well.

As the team started building out the mockup of what the execution process should look like, they were informed that the engineering leadership team would be moving forward with purchasing Harness licenses. Although this meant that the team would have to start over with the integrations, the onboarding time should be significantly shorter. Harness has a file generation process that converts all of the setup in Harness to a set of YAML configuration...