Hacker News Reader

Comment by jakozaur | Hacker News Reader

Hashicorp is one of the extreme examples. Terraform Cloud is an okay product at best, which went from expensive to very expensive. Moreover, they aggressively changed the Terraform license from open-source to BSL.

So after the whole community contributed a lot of providers, they want to profit from that.

You should use OpenTofu and buy IAC from one of the companies sponsoring full-time engineers on that project: Spacelift, env0, Harness or Scalr.

View on HN

In all fairness, the Terraform provider registry has always been clearly proprietary, prohibiting commercial use by default:

> You may download or copy the Content (and other items displayed on the Services for download) for personal non-commercial use only

https://web.archive.org/web/20201106225027/https://registry....

I listened to a changelog.com podcast the other day on the subject of OpenTofu (It was a few months old so they were still calling it OpenTF).

Apparently a lot of the actual images are hosted on the GitHub container registry (ghcr.io), and in many cases, the Terraform registry is just passing the request through to download an image from a repo that may be owned by someone else.

So in effect, they're putting scary licensing text on a lot of content they have no control over.

It is, btw, why it was so easy for us to spin up a quick-and-dirty registry for our alpha release[0] that basically contains all providers and modules - almost everything is hosted on GitHub.

Right now we're working on the stable registry[1,2], and that's basically the main blocker left to a full stable release. You can track the progress in our weekly updates[3].

Note: Interim Tech Lead of the OpenTofu project

[0]: https://github.com/opentofu/registry

[1]: https://github.com/opentofu/opentofu/issues/741

[2]: https://github.com/opentofu/registry-stable

[3]: https://github.com/opentofu/opentofu/blob/main/WEEKLY_UPDATE...

I would use opentofu but still waiting on cdktf https://github.com/opentofu/manifesto/issues/58

Yet, HashiCorp does not support CDKTF natively in their commercial product! It puts very little effort into CDKTF as it doesn't make any extra revenue. The only reason they did it was to offer an alternative to Pulumi.

Why not use the HashiCorp one? It's still MPL and should remain compatible with OpenTofu...

At the hashi conf last month they started talking about adding terraform features that would only work on terraform cloud.

It was very sad to see

Sure, could do, just that I'd rather ensure that compatibility remains rather than retool on opentofu (admit that's not a big deal currently whilst in parity) and have some compatibility drift in the future. Would rather wait and see if there's a more unified solution.

https://www.nullstone.io/ (YC 23) is also a great option

I am a terraform user but haven't courage to migrate as IAC is trickier than it looks. How much is OpenTofu compatible with terraform? Is there any page which tracks this or list down things which might break on migration.

OpenTofu is a superset of Terraform. They maintain complete compatibility with Terraform while adding additional features on top of it. They have more dedicated developers on the project than Hashicorp does, and they are building out a fairly robust RFC process for the additional features.

I would not recommend using OpenTofu in production until they've had their first official release though. They currently have some alpha releases out that you can experiment with.

A superset of Terraform 1.5. Terraform 1.6 has features that OpenTofu does not have.

No, it's a superset of Terraform. The developers of OpenTofu have been adding every new feature in, and are committing to version parity. They've already got the new testing framework built out for example, as well as the changes to the S3 backend.

Is there any source to this? I have heard lot of conflicting things just like in this thread.

https://github.com/opentofu/opentofu/blob/b8e2fad8e24cdd98c5...

Reply on news.ycombinator.com