We had this pattern in a previous role. Essentially, there was a repo with yaml config files in it. A dev team would write their code they wanted to deploy, con

We had this pattern in a previous role. Essentially, there was a repo with yaml config files in it. A dev team would write their code they wanted to deploy, configure the yaml files, and infrastructure would be deployed in AWS. That infrastructure was owned by the operations team. This caused as many disasters as you’d expect. For example, when something breaks (like ECS, or a bad AMI is deployed), the dev team is stuck waiting on the operations team to fix it because the infrastructure is owned by the ops team. I was part of transitioning to a different model where the same general concept applies; a bunch of yaml leads to infrastructure being deployed. But that infrastructure was fully owned by the dev team that deployed the code. It only made things generally easier, because then if the deployment code broke (i.e. the code responsible for converting the yaml files to infrastructure, like terraform modules), we’d have to fix it. Ultimately it was just a fancier and more guided version of Kubernetes.