Documentation as Code: Using YAML, GitHub Actions, and Azure to Power a Living Catalog
Objective
More and more companies are moving into the world of DevOps and automation. As this grows, you begin to face a scaling problem. You now have dozens of automations interacting with different systems, each using its own API keys or managed identities. With so many moving pieces, you need a way to keep track of everything. After spending time looking through different products to help with this problem, I realized that we could lean into automation itself to help with a solution. When creating the product I kept several goals in mind:
- Be able to manage, update and deploy using Git. Leveraging CI/CD to update the front end for me.
- Automation project structure should be simple, I don’t want engineers or managers spending a lot of time adding or editing projects.
- The site should be easily customizable to fit different needs.
- Ability to track time saved and cost saved