A manifest for integrations
As the DevOps team started to build out the different declarative file structures for the application stacks, they decided that the easiest piece to start with was solution integrations. Some of the solutions were common across the application stacks, but other tools were unique to a specific platform or artifact type. An advantage to using an open source solution such as Ansible meant that some of the work might have been completed by others already. For example, the team needed an integration with a popular ticketing solution to handle some of the auditing requirements. Since the tool is widely used, it was highly likely that there are already plugins or examples of the tool being used in Ansible. After finding the community plugin and discovering how to add it to their Ansible configuration, they needed to figure out the best way to pass in the different requirements from the myriad of engineering teams and their differing processes into the tickets.
...
