Oracle dumps Terraform for OpenTofu

Original Article ↗ Hacker News Discussion ↗

Oracle’s decision to replace Terraform with the open-source fork OpenTofu in parts of its tooling is seen as a strategic move to avoid licensing and vendor-dependence risks, especially now that HashiCorp is owned by competitor IBM. Commenters frame this as part of a broader trend: popular infrastructure tools moving to restrictive licenses, prompting forks like OpenTofu that regain community control and attract backing from large enterprises. The thread also weighs Terraform’s technical pain points and OpenTofu’s new features, with many predicting a gradual but steady migration toward the fork.

Scope and impact of Oracle’s move

  • Oracle is switching some E-Business Suite (EBS) cloud migration tooling from Terraform to OpenTofu.
  • Commenters think this targets a narrow use case (on‑prem EBS → Oracle Cloud) rather than huge Terraform volumes.
  • Oracle’s managed Terraform service (OCI Resource Manager) still uses an old open‑source Terraform (1.2.9), suggesting limited attention and careful license line‑drawing.

Licensing, IBM, and vendor risk

  • Main motive cited: avoid downstream complications from HashiCorp’s BUSL and from relying on a tool now owned by direct competitor IBM.
  • Several see this as a predictable response: large vendors won’t want mission‑critical integrations tied to a competitor’s proprietary licensing.
  • Some speculate HashiCorp’s relicensing was about protecting itself from cloud resellers (including IBM), and possibly sweetening the IBM acquisition.
  • There’s debate whether IBM might eventually roll back the Terraform license change; even if so, OpenTofu has already hard‑forked.

Oracle’s behavior and “hypocrisy” debate

  • Many call it ironic that Oracle, famous for aggressive license enforcement, is fleeing restrictive licensing from others.
  • Counterpoint: not hypocrisy, just rational profit maximization; companies take as much as they can and give as little as they must.
  • Some argue this underscores why permissive licenses let companies like Oracle benefit without giving much back; others defend permissive licensing as an intentional “gift to the public.”

State of OpenTofu

  • OpenTofu is presented as a community‑run hard fork of Terraform with new features (e.g., end‑to‑end state encryption, enhanced provider‑defined functions).
  • Migration is currently easy (in simple cases often just swapping the binary name), but divergence from Terraform will grow over time.
  • Some see OpenTofu as reducing long‑term vendor risk and providing a more community‑driven roadmap.

Terraform / IaC technical issues and alternatives

  • Multiple complaints about Terraform/HCL ergonomics: difficult refactoring, awkward iteration and typing, poor debuggability, and project sprawl.
  • OpenTofu maintainers acknowledge needs like better tracing/debugging and conditional modules, but note technical complexity.
  • Alternatives mentioned: Pulumi (with TypeScript, Kotlin, Scala, F#, etc.), CDK for Terraform, Dhall, Nix‑based tools, with trade‑offs in maturity and dependency on Terraform core.

Broader relicensing and OSS governance

  • Commenters note a broader trend: popular projects (Terraform, Redis, Elastic, others) relicensing away from OSI licenses, prompting forks (OpenTofu, OpenSearch, etc.).
  • Some propose assessing “relicensing risk” via governance, contributor diversity, CLAs, and ownership (foundations vs single vendors).