jprdonnelly/opentf
1
0
Fork 0
mirror of https://github.com/opentffoundation/opentf.git synced 2025-12-25 10:00:44 -05:00
Code Issues Packages Projects Releases Wiki Activity

Rename website to OpenTofu (#516)

Browse Source 
Co-authored-by: Damian Stasik <920747+damianstasik@users.noreply.github.com>
Co-authored-by: Roman Grinovski <roman.grinovski@gmail.com>
This commit is contained in:
Julien Levasseur
2023-09-21 05:57:47 -04:00
committed by GitHub
parent e5878055b6
commit 4c0bda5386
221 changed files with 2497 additions and 2497 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
website/docs/intro/vs/boto.mdx
View File

@@ -1,8 +1,8 @@
---
description: 'How OpenTF compares to cloud provider client libraries like Boto and Fog. '
description: 'How OpenTofu compares to cloud provider client libraries like Boto and Fog. '
---
# OpenTF vs. Boto, Fog, etc.
# OpenTofu vs. Boto, Fog, etc.
Libraries like Boto, Fog, etc. are used to provide native access
to cloud providers and services by using their APIs. Some
@@ -11,9 +11,9 @@ to bridge them all and mask the semantic differences. Using a client
library only provides low-level access to APIs, requiring application
developers to create their own tooling to build and manage their infrastructure.
OpenTF is not intended to give low-level programmatic access to
OpenTofu is not intended to give low-level programmatic access to
providers, but instead provides a high level syntax for describing
how cloud resources and services should be created, provisioned, and
combined. OpenTF is very flexible, using a plugin-based model to
combined. OpenTofu is very flexible, using a plugin-based model to
support providers and provisioners, giving it the ability to support
almost any service that exposes APIs.

10
website/docs/intro/vs/chef-puppet.mdx
View File

@@ -1,22 +1,22 @@
---
description: >-
How OpenTF compares to configuration management tools like Chef and
How OpenTofu compares to configuration management tools like Chef and
Puppet.
---
# OpenTF vs. Chef, Puppet, etc.
# OpenTofu vs. Chef, Puppet, etc.
Configuration management tools install and manage software on a machine
that already exists. OpenTF is not a configuration management tool,
that already exists. OpenTofu is not a configuration management tool,
and it allows existing tooling to focus on their strengths: bootstrapping
and initializing resources.
OpenTF focuses on the higher-level abstraction of the datacenter and
OpenTofu focuses on the higher-level abstraction of the datacenter and
associated services, while allowing you to use configuration management
tools on individual systems. It also aims to bring the same benefits of
codification of your system configuration to infrastructure management.
If you are using traditional configuration management within your compute
instances, you can use OpenTF to configure bootstrapping software like
instances, you can use OpenTofu to configure bootstrapping software like
cloud-init to activate your configuration management software on first
system boot.

22
website/docs/intro/vs/cloudformation.mdx
View File

@@ -1,38 +1,38 @@
---
description: >-
How OpenTF compares to other infrastructure as code tools like
CloudFormation and Heat. OpenTF can simultaneously manage multiple cloud
How OpenTofu compares to other infrastructure as code tools like
CloudFormation and Heat. OpenTofu can simultaneously manage multiple cloud
providers (AWS, OpenStack, etc.) and services (Cloudflare, DNSimple, etc.).
---
# OpenTF vs. CloudFormation, Heat, etc.
# OpenTofu vs. CloudFormation, Heat, etc.
Tools like CloudFormation, Heat, etc. allow the details of an infrastructure
to be codified into a configuration file. The configuration files allow
the infrastructure to be elastically created, modified and destroyed. OpenTF
the infrastructure to be elastically created, modified and destroyed. OpenTofu
is inspired by the problems they solve.
OpenTF similarly uses configuration files to detail the infrastructure
OpenTofu similarly uses configuration files to detail the infrastructure
setup, but it goes further by being both cloud-agnostic and enabling
multiple providers and services to be combined and composed. For example,
OpenTF can be used to orchestrate an AWS and OpenStack cluster simultaneously,
OpenTofu can be used to orchestrate an AWS and OpenStack cluster simultaneously,
while enabling 3rd-party providers like Cloudflare and DNSimple to be integrated
to provide CDN and DNS services. This enables OpenTF to represent and
to provide CDN and DNS services. This enables OpenTofu to represent and
manage the entire infrastructure with its supporting services, instead of
only the subset that exists within a single provider. It provides a single
unified syntax, instead of requiring operators to use independent and
non-interoperable tools for each platform and service.
OpenTF also separates the planning phase from the execution phase,
by using the concept of an execution plan. By running `opentf plan`,
OpenTofu also separates the planning phase from the execution phase,
by using the concept of an execution plan. By running `tofu plan`,
the current state is refreshed and the configuration is consulted to
generate an action plan. The plan includes all actions to be taken:
which resources will be created, destroyed or modified. It can be
inspected by operators to ensure it is exactly what is expected. Using
`opentf graph`, the plan can be visualized to show dependent ordering.
`tofu graph`, the plan can be visualized to show dependent ordering.
Once the plan is captured, the execution phase can be limited to only
the actions in the plan. Other tools combine the planning and execution
phases, meaning operators are forced to mentally reason about the effects
of a change, which quickly becomes intractable in large infrastructures.
OpenTF lets operators apply changes with confidence, as they know exactly
OpenTofu lets operators apply changes with confidence, as they know exactly
what will happen beforehand.

10
website/docs/intro/vs/custom.mdx
View File

@@ -1,10 +1,10 @@
---
description: >-
Why OpenTF is easier to use and maintain than custom, internal
Why OpenTofu is easier to use and maintain than custom, internal
infrastructure solutions.
---
# OpenTF vs. Custom Solutions
# OpenTofu vs. Custom Solutions
Most organizations start by manually managing infrastructure through
simple scripts or web-based interfaces. As the infrastructure grows,
@@ -21,7 +21,7 @@ updated in lockstep with any new features or infrastructure,
it becomes the limiting factor for how quickly the infrastructure
can evolve.
OpenTF is designed to tackle these challenges. It provides a simple,
OpenTofu is designed to tackle these challenges. It provides a simple,
unified syntax, allowing almost any resource to be managed without
learning new tooling. By capturing all the resources required, the
dependencies between them can be resolved automatically so that operators
@@ -29,9 +29,9 @@ do not need to remember and reason about them. Removing the burden
of building the tool allows operators to focus on their infrastructure
and not the tooling.
Furthermore, OpenTF is an open source tool. The community around OpenTF
Furthermore, OpenTofu is an open source tool. The community around OpenTofu
helps to extend its features, fix bugs and document new use cases.
OpenTF helps solve a problem that exists in every organization and provides
OpenTofu helps solve a problem that exists in every organization and provides
a standard that can be adopted to avoid reinventing the wheel between
and within organizations.
Its open source nature ensures it will be around in the long term.

14
website/docs/intro/vs/index.mdx
View File

@@ -1,19 +1,19 @@
---
description: An overview of how OpenTF compares to alternative software and tools.
description: An overview of how OpenTofu compares to alternative software and tools.
---
# OpenTF vs. Alternatives
# OpenTofu vs. Alternatives
OpenTF provides a flexible abstraction of resources and providers. This model
OpenTofu provides a flexible abstraction of resources and providers. This model
allows for representing everything from physical hardware, virtual machines, and
containers, to email and DNS providers. Because of this flexibility, OpenTF
containers, to email and DNS providers. Because of this flexibility, OpenTofu
can be used to solve many different problems. This means there are a number of
existing tools that overlap with the capabilities of OpenTF. We compare OpenTF
to a number of these tools, but it should be noted that OpenTF is not mutually
existing tools that overlap with the capabilities of OpenTofu. We compare OpenTofu
to a number of these tools, but it should be noted that OpenTofu is not mutually
exclusive with other systems. It can be used to manage a single application, or the
entire datacenter.
Learn how OpenTF compares to:
Learn how OpenTofu compares to:
- [Chef, Puppet, etc.](/docs/intro/vs/chef-puppet)
- [CloudFormation, Heat, etc.](/docs/intro/vs/cloudformation)