Proprietary manifest building

One of the main pain points associated with building out any kind of manifest, regardless of language, is the requirement to learn the proprietary syntax. This is the biggest issue that the DevOps team has with a tool such as Ansible. Every action and execution that the DevOps team would want requires an Ansible YAML file to be created, stored, and linked appropriately. Ansible has made some of the file building easier by leveraging the naming convention of the different YAML objects as instructions. But when extra capabilities are brought into Ansible, such as plugins and extra modules, it would require extra knowledge to be added to the execution process. Also, adding a relatively uncommon templating style to the YAML files adds extra complexity. But the DevOps team has found extensive documentation and examples from the community to aid in this area, which gives them a step up when learning the nuances specific to Ansible YAML.

Harness has the same...