3 ms·

Part of me hopes a fork comes out of this. I mean maybe features like this PR[1] for local state file encryption can then finally get merged. [1] https://githu

Part of me hopes a fork comes out of this. I mean maybe features like this PR[1] for local state file encryption can then finally get merged. [1] https://github.com/hashicorp/terraform/pull/28603 https://github.com/hashicorp/terraform/pull/28603

LVB 3y ago
I did see https://github.com/diggerhq/open-terraform https://github.com/diggerhq/open-terraform but have no idea if it is related. And I’m sure there are others. What I’ll be interested to see with the forks is how they will practically be maintained. All the bug and security fixes that HashiCorp is writing can’t just be cherry-picked into these forks (I think?), so what exactly are they supposed to do? Update: and in the past hour this repo is gone.
- yellowapple 3y ago
  > Update: and in the past hour this repo is gone. Which is interesting, since Digger (the company that created that fork) is one of the OpenTF Manifesto signatories. Maybe they're recreating it under a different name / without the Hashicorp/Terraform branding all over the place?
- pawelpiwosz 3y ago
  Hi! OpenTF is not connected with a single company. This is an united, community-driven effort. You can check on the manifesto side who is behind. And we welcome all support! The fork you mentioned is no longer existing.
- JeremyNT 3y ago
  > All the bug and security fixes that HashiCorp is writing can’t just be cherry-picked into these forks (I think?), so what exactly are they supposed to do? Indeed, any fork will need to implement their own bug fixes. Ideally they should do this "clean room" and not even look at the BSL'd code, to help defend against any accusations of copyright infringement.
fishnchips 3y ago
That would be one of the 1st things I'd love to see myself. Plus opening of "internal" to let folks build new stuff on top of Terraform elements.
Fawlty 3y ago
Hashi got really good at ignoring PRs if they weren't their own. They even ignored the PRs coming from the dev teams of their own customers (ie users of TF Cloud and Enterprise) which speaks volumes about their willingness to listen to the community...

LVB 3y ago

I did see https://github.com/diggerhq/open-terraform https://github.com/diggerhq/open-terraform but have no idea if it is related. And I’m sure there are others. What I’ll be interested to see with the forks is how they will practically be maintained. All the bug and security fixes that HashiCorp is writing can’t just be cherry-picked into these forks (I think?), so what exactly are they supposed to do? Update: and in the past hour this repo is gone.

yellowapple 3y ago
> Update: and in the past hour this repo is gone. Which is interesting, since Digger (the company that created that fork) is one of the OpenTF Manifesto signatories. Maybe they're recreating it under a different name / without the Hashicorp/Terraform branding all over the place?
pawelpiwosz 3y ago
Hi! OpenTF is not connected with a single company. This is an united, community-driven effort. You can check on the manifesto side who is behind. And we welcome all support! The fork you mentioned is no longer existing.
JeremyNT 3y ago
> All the bug and security fixes that HashiCorp is writing can’t just be cherry-picked into these forks (I think?), so what exactly are they supposed to do? Indeed, any fork will need to implement their own bug fixes. Ideally they should do this "clean room" and not even look at the BSL'd code, to help defend against any accusations of copyright infringement.

fishnchips 3y ago

That would be one of the 1st things I'd love to see myself. Plus opening of "internal" to let folks build new stuff on top of Terraform elements.

Fawlty 3y ago

Hashi got really good at ignoring PRs if they weren't their own. They even ignored the PRs coming from the dev teams of their own customers (ie users of TF Cloud and Enterprise) which speaks volumes about their willingness to listen to the community...