#opentofu - April 2024

My fear is enterprises and businesses alike, begin to distrust open source, especially open source backed with commercial interests as “bait and switch”

@Erik Osterman (Cloud Posse)
I’m not sure that’s the case. Most of the leaders I talk with are juggling a few factors: capabilities, risk and cost. Pure open source solutions aren’t free as in beer, they’re free as in puppy. There are still costs around building and maintaining solutions. There is risk around supportability and variance between solutions. If a team can build a solution with the highest amount of capability for the business with the lowest risk and cost, that solution will win, regardless of it is built on OSS or not.

Also, the practitioners have their own biases. I’ve seen plenty of cases where top-down driven solutions have failed because the folks that inherited those solutions weren’t capable or motivated to use them. The vast majority of good leaders will allow their practitioners to select the best solutions, again, regardless of how they got to those solutions as long as risk and cost are optimized.

I’ll give you an example from $lastJob. Consul was a mission critical part of our ad delivery system. We botched an upgrade and had a six hour outage. At the time, there wasn’t a commercial version of Consul, hence no support. Also, it was late at night and, even though we got a response through community channels, they came in the next day. The amount of money we lost in those six hours greatly exceeded what our license costs would have been could we have bought a product.

Even with all of that, our leadership still allowed us to continue to build our solutions on OSS projects. They did open up the ability for us to buy products if we chose, but at the time, few of the OSS projects we used had commercial versions available (we were also early K8s adopters). We did pay for commercial Hadoop and OpenStack because they were available.

I tent to not think of something through, which is my limit, for example, when early days k8s chose etcd instead of consul, my thought was why the community chose a product from CoreOS (acquired by another company), why they don’t choose Consul, from then great company and stable team/feature development, and now we know the things changed, and I realize my limit as well. The point is when people are saying or supporting one good thing, the bad actor is acting to change the good to bad, but the actor will never realize it, instead he/she/they(Lol) will always defend it, one day when he/she realizes, that is the cost for him/her/them to pay back a bigger failure than the success.

We just launched our blog post on switching from TF => OpenTofu. Should be a good read for folks here since it involves atmos + Cloud Posse module usage: https://www.linkedin.com/feed/update/urn:li:activity:7183494705052090369/

Hey everybody, OpenTofu core team member here,

On April 3rd, OpenTofu received a Cease and Desist letter from Hashicorp claiming copyright infringement on the part of one of our core developers.

The OpenTofu team vehemently disagrees with any suggestion that it misappropriated, mis-sourced, or otherwise misused HashiCorp’s BSL code. All such statements have zero basis in facts.

You can find our response, along with the cease & desist letter, our response letter, as well as the source code origin document resulting from our investigation in this blog post: https://opentofu.org/blog/our-response-to-hashicorps-cease-and-desist/

Despite these events, we have managed to carry out significant development on OpenTofu 1.7, and we will be releasing a new pre-release version next week, including provider-defined functions!

Has Hashicorp done something unprecedented in open source history? I never remember one open-source project sued the other. Please correct me if I missed. You may be very successful in the current business, but what Hashicorp is doing will take away future opportunities of your future generations. 10000%

this is not new, pretty common, and usually you do not see it

Today got some free time, and took a look at Tofu’s issue, https://github.com/opentofu/opentofu/issues/1490. It looks when the data inside check block is included in hcl.Traversal.

v1.7.0-beta1: Allow configured providers to provide additional functions. (#1491)
Signed-off-by: Christian Mesh christianmesh1@gmail.com (christianmesh1@gmail.com)

v1.7.0-beta1: Issue #1033: Docs for for_each on import (#1503)
Signed-off-by: Janos 86970079+janosdebugs@users.noreply.github.com (86970079+janosdebugs@users.noreply.github.com)
Co-authored-by: Oleksandr Levchenkov ollevche@gmail.com (ollevche@gmail.com)

v1.7.0-beta1
⚠️ Do not use this release for production workloads! ⚠️
It's time for the first beta release of the 1.7.0 version! This includes a lot of major and minor new features, as well as a ton of community contributions!
The highlights are:

State Encryption (docs)
Provider-defined Functions (<a href="https://1-7-0-beta1.opentofu.pages.dev/docs/language/functions/#provider-defined-functions"...

please thump up or give positive emoji to OpenTofu issues and PRs, I believe this will help foster a better community 🙂

Got a quick question about the projects that Terraform depends on, e.g. https://github.com/hashicorp/hcl/tree/main, why are the licenses of the similar projects not converted by Hashicorp?

v1.7.0-rc1: Versioned docs: replacing docs links with relative variants (#1537)
Signed-off-by: Janos 86970079+janosdebugs@users.noreply.github.com (86970079+janosdebugs@users.noreply.github.com)
Signed-off-by: Damian Stasik 920747+damianstasik@users.noreply.github.com (920747+damianstasik@users.noreply.github.com)
Signed-off-by: Roman Grinovski roman.grinovski@gmail.com (roman.grinovski@gmail.com)
Co-authored-by: Damian Stasik <a...

v1.7.0-rc1: Bump version. (#1548)
Signed-off-by: Jakub Martin kubam@spacelift.io (kubam@spacelift.io)

v1.7.0-rc1
Today, we're releasing the first release candidate of OpenTofu 1.7. If all goes well, this very version will be released next week as a stable release. This includes a lot of major and minor new features, as well as a ton of community contributions!
The highlights are:

State Encryption (docs)
Provider-defined Functions (<a...

Our live stream starting in 10 mins https://www.youtube.com/watch?v=6OXBv0MYalY 😄

as said before, there is no way for the current Hashicorp employees to survive in next wave of layoff, time to embrace OpenTofu

I’m also on OpenTofu Slack channel to answer questions 🙂 take a look there if you’ve got any

v1.7.0: Bump version to 1.7.0 final (#1578)
Signed-off-by: James Humphries james@james-humphries.co.uk (james@james-humphries.co.uk)

v1.7.0
We're proud to announce that OpenTofu 1.7.0 is now officially out! 🎉
What’s New?

State Encryption - Protect your precious state files with end-to-end encryption.
Dynamic Provider-defined Functions - Author custom functions as part of providers.
Declarative removed Blocks - No more fighting with the CLI, execute your removals declaratively!
Loopable Import Blocks - Streamline importing multiple resources.
...and much, much more!

See the launch post on our blog: <a...

Hey, OpenTofu 1.7.0 is out with state encryption, provider-defined functions, and a lot more: https://opentofu.org/blog/opentofu-1-7-0/!

This post reminds me to think, https://newsletter.goodtechthings.com/p/why-didnt-google-cloud-buy-hashicorp, when I looked into Terraform and put up a couple of PRs before, I found there are many Google engineers working actively on Terraform, Google must have done audits for the potential acquisition but didn’t do it with their reasons. If you put my 2 cents with this article, you will be convinced that how bad the Hashicorp’s decision of license change is.