Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Are there any incompatibilities cropping up between terraform and opentofu?

OpenTofu is indeed a hard fork. When doing similar features (like provider-defined functions) we try to stay compatible where it makes sense, but there's often some differences (like our more extended capabilities of provider-defined functions[0]) and also new features in Terraform that we're not introducing - and vice versa.

You can check for known incompatibilities in our migration guides[1], based on your Terraform version. In practice, the longer you wait, the more the projects will diverge, so if you still want to "wait and see" I would suggest settling on your current Terraform version for now - otherwise, the migration will just be more work for you later.

Regarding the reasons for switching, I'd say features and community-first process. We're striving to be very community driven in what work we're prioritizing[2] and have received a lot of positive feedback over that from our users.

Some companies we've spoken to see adopting the open-source community-driven project as a way to reduce risk long-term. It's also a way to keep your options open if you're in the market for commercial Terraform/OpenTofu management systems.

[0]: https://github.com/opentofu/terraform-provider-go

[1]: https://opentofu.org/docs/intro/migration/

[2]: https://github.com/opentofu/opentofu/issues/1496



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: