Is Terraform Still a Safe Choice After IBM’s Purchase?

0
0
Asked By TechyTurtle987 On

We're a company primarily focused on Azure, and we're trying to decide between using Bicep and Terraform for our infrastructure as code (IaC) rollout. Bicep seems like a natural fit since it integrates well with Azure and simplifies onboarding. However, we're also considering Terraform because we might acquire organizations using AWS or GCP in the future, and we want the flexibility to adapt to different cloud environments down the line.

With IBM buying HashiCorp, we're feeling a bit wary. IBM's track record with Red Hat hasn't been aggressive, and we're curious if anyone has noticed changes with Terraform's licensing, support, or direction. For a mostly Azure setup, is sticking with Terraform still a smart move, or should we just commit to Bicep and think about multi-cloud later? I'm looking for insights from others in the DevOps community!

4 Answers

Answered By DevOpsDude42 On

OpenTofu is worth considering as it's production-ready and compatible with Terraform for now. Just keep in mind that licensing has shifted recently with HashiCorp moving from an open-source model to a source-available one, which might affect future compatibility. If you’re okay with a bit of uncertainty, it could provide a viable alternative.

Answered By SkepticalSquirrel22 On

Bicep's the way to go if you want simplicity and native support. Plus, it avoids some Terraform quirks—like state mismatches that can drive you nuts. If you're considering a multi-cloud future, you can always handle that later, but keeping it clean with Bicep sounds smarter for now.

Answered By CloudyCheese123 On

You might want to check out OpenTofu. It's a fork of Terraform that's being supported by the Linux Foundation, and honestly, I would trust that over anything related to IBM after their past experiences with CentOS. It could be a safe bet for your needs without the IBM concerns.

Answered By AzureAficionado On

If you're mainly on Azure, go with Bicep! It integrates perfectly, doesn't need that external state management mess like Terraform, and you won’t have to juggle different deployment scripts later for Azure and AWS. This could save you headaches down the road.

Related Questions

Convert Json To Xml

Bitrate Converter

GUID Generator

GUID Validator

Convert Json To C# Class

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.