In this episode, we continue our Vibe Coding experiment. Now that we’ve figured out how to interface with MaaS, this time we wrestle with mapping and how different systems interact with each other. We’re joined by Greg Althaus, RackN CTO, who reviews the project and asks some really great questions. We talk about our decision to restart the experiment, taking the lessons we’ve learned to the newer software available. Enjoy!
Human factors make governance as code a challenge – today we discuss why looking at things like audit and how we determine what has happened and respond to it in an automated way, may be a great first step to adding controls into a system.
We talk about a lot of human factors of what makes it hard to create a governance system, or what creates a biased system or an unevenly governed system.
We spent the first couple minutes of this podcast talking about our agenda, and those conversations spell out a lot of interesting topics that we will discuss. So hang in for those first couple of minutes, and then we will get straight to the governance.
We continue our Governance as Code discussions in today’s episode.
We started by very broadly looking at Governance as Code generally, but quickly drilled down into Infrastructure as Code meets Governance as Code focused discussion. Understanding that intersection is critical to building something that is both automated and governable.
The topic explored how we audit controls for systems. We also need to make sure that when we build infrastructure, it’s following our policies. The challenge here is making sure that what we’ve automated is conforming to our governance.
Our discussion about governance as code today is one of a series that we’re going to be starting. In today’s episode, we started out discussing what is Governance as Code. Then we dug into identity and how important it is to know who is doing what in a governance process.
Along the way, we touch on topics such as Infrastructure as Code, trust, logging, and audit – all essential components for governance.
If this is your first time hearing about Governance as Code, you will learn a lot here. Even if you already know the topic, the back half of today’s podcast poses some fantastic conversations and questions.
In the May 9th Cloud 2030 discussion on “Governance as Code,” Rob Hirschfeld emphasizes the significance of building automation as code for creating resilient infrastructure. The conversation focuses on the challenge of tracking identity in automated systems to understand who initiated specific changes. Recognizing the importance of untangling transitions and identifying contributors becomes a foundational component of governance as code efforts. Join the insightful discussions at the2030.cloud and explore the in-depth May 9th episode of DevOps Lunch and Learn with Cloud 2030.
