#OpenTofu responds to #Hashicorp showing that they kept receipts with a simple git diff.
https://opentofu.org/blog/our-response-to-hashicorps-cease-and-desist/
#OpenSource #Terraform
検索
You ever go through a bad breakup and keep getting reminded of your awful ex?
#Hashicorp #Fedora
Idea: An #opensource #secrets manager, with a fancy web UI like #Hashicorp #Vault, that can organize secrets by folders and deployment target (dev, staging, prod) and the CLI tool can translate those folders, keys, and values into *structured* YAML or JSON output in addition to environment variables. Additionally, it can *import* secrets into new projects with structure YAML/JSON into the format.
Something like this for the data backend: https://github.com/smithjm/etcd-export
I hope someone else takes the reigns on #opensourcedotcom. I'm the age of #Hashicorp, we need a microphone so that truly #opensource companies can be discovered and gain visibility. The need for such a website is great and timely right now.
返信元:
Some very good news. #podman support in #SystemInitiative is coming along! The discord (yeah, I know) is very active right now. If you have ways you might want to contribute or test and give feedback for this fresh #opensource #DevOps service, it's a good time to jump in the pool.
If you're not living what #Hashicorp did, between #SystemInitiative and #OpenTF, you now have a way to channel that energy for good and for the benefit of everyone. When it comes to #opensource, the community generally wins in the end. Now is a great time to get involved!
返信元:
I can definitely see #SystemInitiative becoming a serious alternative to #Terraform. It's been fun to watch this very promising #opensource project take shape over discord. Things are moving along very fast!
https://www.youtube.com/watch?v=zyEOYl23pd8
While #Hashicorp decided to bank on being proprietary, #SystemInit decided to go all in on commercial #opensource, encouraging not only contributions, but competition.
https://www.systeminit.com/blog-open-source
Looks like #HashiCorp is keeping the 1.9 branch of #Packer under the #MPL-2.0, and I assume 1.10(?) will use the #BUSL-1.1 license.
Building 1.9.3 for #COPR soon...
https://fosstodon.org/@omenos/110895471715396206
I don't think I'm going to make it to this one. I think we've seen enough of that particular "agenda". #Hashicorp
I'm not convinced Hashicorp have been the best custodian of terraform, most obviously where efforts conflicted with their purported business model.
So I'd be happy seeing it moved under an independent foundation, whether Hashicorp are involved or not - it'll be a bumpy ride but it would be worth it.
https://opentf.org/
#terraform #hashicorp #freesoftware #opentf
As a result of the #HashiCorp licensing change, all utilities from them in my #COPR will be frozen at their latest version.
- #Terraform 1.5.5
- #Packer 1.9.2
Based on the Not-Allowed license list for @[email protected] the Business Source License (BUSL-1.1) is strictly forbidden. As COPR requires compliance with Fedora guidelines, there's not much I can do here.
https://docs.fedoraproject.org/en-US/legal/not-allowed-licenses/
返信元:
To those who are concerned that I'm going to talk about nothing but #Hashicorp for weeks, don't be. I was harder on #RedHat, not because I think that Red Hat had done something worse (they didn't), but rather that I frankly care about Red Hat more. The shop where I work is also a Hashicorp customer, but that relationship is far more expendable, IMO, and I had hopes that some in Red Hat would hear and consider feedback where I generally don't believe that to be the case for Hashicorp.
That said, I am happy to advocate for truly #opensource forks or alternatives to #Hashicorp products and may continue to post about my own experiences with migrating to other things. Keep in mind that my use cases may be different from yours, but if you're stuck on how to replace #Terraform, #Vault, etc, speak up and let the OSS *community* help you find what you need. There is plenty of opportunity in the midst of this tragedy and the story of open source, free or commercial, is far from over.
To those who are concerned that I'm going to talk about nothing but #Hashicorp for weeks, don't be. I was harder on #RedHat, not because I think that Red Hat had done something worse (they didn't), but rather that I frankly care about Red Hat more. The shop where I work is also a Hashicorp customer, but that relationship is far more expendable, IMO, and I had hopes that some in Red Hat would hear and consider feedback where I generally don't believe that to be the case for Hashicorp.
返信元:
As much flack as I've given #RedHat over #RHEL source shenanigans, they've kept #Ansible AWX #opensource and available to the public, very much to their credit. Tower was proprietary when they bought it and they opened it and kept it open.
There is also a bit of schadenfreude about this as Red Hat will more have to pull Terraform from #Openshift as some collateral damage for #Hashicorp doing an anti-competitive thing with its source code.
People are like "don't contribute to #hashicorp projects" but jokes on you, I've been waiting for an outside pull request getting merged for a year now
One of the mechanisms that let #Hashicorp relicense their stack was the CLA. Whenever you see an "open core" shop (ie, they have proprietary "Enterprise" versions or extensions) and they require you to agree to a CLA before accepting a PR, be aware that the company may not be using #opensource in good faith and may relicense your contributions to be proprietary. Think twice about spending your time and efforts if such a move would bother you.