I understand their reasoning, but am still left disappointed.
That's where I'm at too. Philosophically its a bummer. For the majority of users of their codebase however, this presents zero changes and the only entity I known of who would be impacted by this change going forward is AWS
So I was trying to figure out what are they getting defensive against. It was clear in redhat's case, but I only really found pulumi as some sort of alternative to terraform and I'm not even sure it relies on it. What is the AWS product that's competing here?
Service Catalog has terraform constructs built in now
Curious, how will AWS be affected? I'm not familiar with all of Hashicorp's tools. Mostly just Terraform (and obvs AWS had Cloud Formation, then CDK - they even worked with HashiCorp I believe to build CDKTF).
I understand their reasoning, but am still left disappointed.
That's where I'm at too. Philosophically its a bummer. For the majority of users of their codebase however, this presents zero changes and the only entity I known of who would be impacted by this change going forward is AWS
So I was trying to figure out what are they getting defensive against. It was clear in redhat's case, but I only really found pulumi as some sort of alternative to terraform and I'm not even sure it relies on it. What is the AWS product that's competing here?
Service Catalog has terraform constructs built in now
Curious, how will AWS be affected? I'm not familiar with all of Hashicorp's tools. Mostly just Terraform (and obvs AWS had Cloud Formation, then CDK - they even worked with HashiCorp I believe to build CDKTF).