kgess-mirror/opentofu.org
1
0
Fork 0
mirror of https://github.com/opentofu/opentofu.org.git synced 2026-01-11 19:56:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Update FAQ per opentofu/opentofu.org/issues/261 (#336)

Browse source 
Signed-off-by: mrjones <8253488+mrjones-plip@users.noreply.github.com>
This commit is contained in:
mrjones 2024-10-30 04:40:03 -07:00 • committed by GitHub
parent 48b5b49060
commit f4eb761696
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
faq.mdx
View file

@ -1,11 +1,13 @@
<AccordionItem id="what-is-opentofu" summary="What is OpenTofu?" open highlight>
OpenTofu is a Terraform fork, created as an initiative of Gruntwork, Spacelift, Harness, Env0, Scalr, and others, in response to HashiCorp’s switch from an open-source license to the BUSL. The initiative has many supporters, all of whom are listed [here](/supporters).
OpenTofu is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. OpenTofu can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features.
</AccordionItem>
<AccordionItem id="why-was-opentofu-created" summary="Why was OpenTofu created?" highlight>
OpenTofu is a Terraform fork, created as an initiative of Gruntwork, Spacelift, Harness, Env0, Scalr, and others, in response to HashiCorp’s switch from an open-source license to the BUSL. The initiative has many supporters, all of whom are listed [here](/supporters).
The BUSL and the additional use grant outlined by the HashiCorp team are ambiguous, which makes it challenging for companies, vendors, and developers using Terraform to decide whether their actions could be interpreted as being outside the permitted scope of use.
Hashicorp’s FAQs give some peace of mind to end users and system integrators for now, but the licensing terms’ implications for future usage are unclear. The possibility that the company’s definition of _“competitive”_ or _“embedding”_ could change or the license could be further modified to make it closed source prompts uncertainty for Terraform users.