So, has anything changed with Terraform since IBM acquired HashiCorp a few months back? I'm keen to hear the community's thoughts on this. We're just starting our journey into infrastructure as code (IaC), torn between Microsoft Bicep and Terraform. Given that we're mainly using Azure, Bicep might seem to be the natural fit on the surface. However, we might end up needing to adopt AWS or other cloud platforms in the future, depending on potential acquisitions. For now, Azure meets our needs, but I'm curious if Terraform is still a reliable option in this new context with IBM involved. I've heard IBM is fairly hands-off, like how they managed Red Hat, but I'd appreciate insights from anyone more plugged into the Terraform ecosystem.
5 Answers
If IBM handles HashiCorp like they did with Red Hat, then Terraform should remain a solid choice. But if they treat it like other brands they've absorbed, like Tivoli and Cognos, then I’d be wary.
Just so you know, Azure Terraform code doesn’t directly translate to AWS. They look similar on the surface, but the infrastructure concepts differ. We are experimenting with Bicep ourselves and have found it practical, especially because of its solid backing.
From what I've seen, a lot of folks are moving towards OpenTofu, especially since it’s open-source. I'm still getting my feet wet with IaC and using Bicep feels right for our Azure setup.
It looks like Terraform is likely to be integrated into Red Hat, similar to what happened with Ansible. If you're worried about Terraform's future, you might want to start looking into the OpenTofu fork instead.
As long as IBM keeps their hands off, like they have with Red Hat, HashiCorp will probably continue to thrive. If things go south like they did with other brands, consider switching to OpenTofu or something similar.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures