←back to thread

IBM to acquire Confluent

(www.confluent.io)
443 points abd12 | 2 comments | | HN request time: 0.55s | source
Show context
hadrien01 ◴[] No.46192816[source]
Genuine question: how did the IBM acquisitions of Red Hat and HashiCorp turn out?

For Red Hat, there's no longer an official "public" distribution of RHEL, but apart from that they seemingly have been left alone and able to continue to develop their own products. But that's only my POV as a user of OSS Red Hat products at home and of RHEL and OpenShift at work.

replies(8): >>46192864 #>>46192912 #>>46193004 #>>46193010 #>>46193433 #>>46198058 #>>46201336 #>>46202389 #
rmccue ◴[] No.46193010[source]
We moved off HashiCorp's Terraform Cloud when they tried to hike the price 100x on us, although that was technically pre-acquisition I think (it was their move to resource-based pricing). In talking with our account manager, they basically said they only really cared about enterprise accounts, and that migrating away would probably make sense for us.

HashiCorp also changed their licenses to non-open-source licenses, but again I think this was technically pre-acquisition (I think as they were gearing up to be a more attractive target for an exit).

replies(3): >>46193245 #>>46193416 #>>46193841 #
1. dangus ◴[] No.46193245[source]
In addition to this, I’ve noticed that OpenTofu is gaining much more interesting features and are actually acting upon long-requested functionality that HashiCorp has refused to implement (example: provider for_each in 1.9.0)
replies(1): >>46201421 #
2. aryonoco ◴[] No.46201421[source]
Yeah I just implemented a new stack and noticed OpenTofu now supports client side encryption for the state files in with keys stored in Azure KeyVault (in the latest 1.11 release). AWS and GCP had been supported for a while.

Client side state encryption was one of the things which HashiCorp always gatekeeped for HashiCorp Cloud and never implemented in the Open Souce / Sourece Available versions.