3 ms·
So, my hot take on this is that it's an advanced GUI for AWS with change management built in. 1. Is that a good summary? 2. Why would I pick this? I know you
by pnathan 2y ago
So, my hot take on this is that it's an advanced GUI for AWS with change management built in.
1. Is that a good summary?
2. Why would I pick this?
I know you LOVE it, it's your baby. But why should I love it? :-)
- holoway 2y agoIt's not a bad summary, but it is a shallow one. :) You should love it because it's a more intuitive and more powerful way to build this kind of infrastructure automation. What's happening under the hood isn't just infrastructure as code with a UI - it's a full reactive model of how things work. That's what makes the UI possible, but it's also what brings about so much power - the code that drives those models is also fully exposed and versioned. So when you have something like a policy to write, you think about what resources you need, use them as inputs to the function, and then store the results. Check out what an early user had to say about it: https://matthewsanabria.dev/posts/take-the-system-initiative/ https://matthewsanabria.dev/posts/take-the-system-initiative... We'll find out if you love it or not. :)