Skip to content

Clarify the Terraform's license compliance and support policy for OpenTaco #2429

@minamijoyo

Description

@minamijoyo

I'm glad to hear about the rebranding from Digger to OpenTaco. 🚀

According to the announcement, OpenTaco will support both Terraform and OpenTofu.
https://www.opentaco.dev/

  1. Reducing fragmentation.
    The community shouldn’t have to pick sides between Terraform and OpenTofu. Our vision is to provide one open, self-hostable platform where users can choose whichever they prefer and still work seamlessly together.
    We’re not fully there yet, but OpenTaco is a step toward that future.

If I recall correctly, the previous Digger's policy was not to support Terraform 1.6 or later due to the BUSL license. While checking the documentation to be sure, I noticed the FAQ has also been removed recently.
https://github.com/diggerhq/digger/blob/18271bb87e9cdd5b84a155dc739b61286718b4e9/docs/readme/faq.mdx

My understanding is that self-hosting the open-source version of the Digger CE backend, or using it in Backendless mode, does not violate Terraform's BUSL. However, license compliance and the development team's support policy are strictly separate concerns.

I'd like to recommend Digger to my friends, but in reality, many of them still use Terraform. While I fully understand Digger's stance of supporting OpenTofu, that stance makes migrating to OpenTofu a prerequisite for adopting Digger, which has made it difficult for me to recommend Digger to them until now.

Could you share the development team's perspective on Terraform's license compliance and support policy for OpenTaco? Even if it's not in the FAQ, it would be a huge help if it were mentioned somewhere in the official product documentation when recommending OpenTaco to my friends.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions