The terraform block allows you to configure OpenTofu behavior, including the OpenTofu version, backend, integration with TACOS (TF Automation and Collaboration Software), and required providers.| opentofu.org
Providers are plugins that allow OpenTofu to interact with services, cloud providers, and other APIs. Learn how to declare providers in a configuration.| opentofu.org
Learn how to name, organize, and store OpenTofu configuration files. Also learn how OpenTofu evaluates modules.| opentofu.org
String literals and template sequences interpolate values and manipulate text. Learn about both quoted and heredoc string syntax.| opentofu.org
The provider network mirror protocol is implemented by a server intending to provide a mirror or read-through caching proxy for OpenTofu providers, as an alternative distribution source from the provider's origin provider registry.| opentofu.org
Credentials helpers are external programs that know how to store and retrieve API tokens for remote OpenTofu services.| opentofu.org
Use OCI registries as an alternative installation source for OpenTofu providers| opentofu.org
Central configuration of credentials for use when interacting with OCI Registries.| opentofu.org
Learn to use environment variables to change OpenTofu's default behavior. Configure log content and output, set variables, and more.| opentofu.org
The tofu login command can be used to automatically obtain and save an API token for any host that offers OpenTofu-compatible services.| opentofu.org
Input variables allow you to customize modules without altering their source code. Learn how to declare, define, and reference variables in configurations.| opentofu.org
Use the `backend` block to control where OpenTofu stores state. Learn about the available state backends, the backend block, initializing backends, partial backend configuration, changing backend configuration, and unconfiguring a backend.| opentofu.org
The source argument tells OpenTofu where to find child modules's configurations in locations like GitHub, the OpenTofu Registry, Bitbucket, Git, Mercurial, S3, and GCS.| opentofu.org
Modules are containers for multiple resources that are used together in a configuration. Learn when to create modules and about module structure.| opentofu.org
The tofu plan command creates an execution plan with a preview of the changes that OpenTofu will make to your infrastructure.| opentofu.org
Learn all about the new features in OpenTofu 1.7.| opentofu.org
Modules are containers for multiple resources that are used together in a configuration. Find resources for using, developing, and publishing modules.| opentofu.org
Version constraint strings specify a range of acceptable versions for modules, providers, and OpenTofu itself. Learn version constraint syntax and behavior.| opentofu.org
Learn to use the CLI configuration file to customize your CLI settings, including credentials, plugin caching, provider installation methods, etc.| opentofu.org
The tofu init command initializes a working directory containing configuration files and installs plugins for required providers.| opentofu.org
An introduction to the tofu command and its available subcommands.| opentofu.org
Learn all about the new features in OpenTofu 1.8.| opentofu.org
Use the OpenTofu configuration language to describe the infrastructure that OpenTofu manages.| opentofu.org
OpenTofu uses the dependency lock file .terraform.lock.hcl to track and select provider versions. Learn about dependency installation and lock file changes.| opentofu.org
Terraform was open-sourced in 2014 under the Mozilla Public License (v2.0) (the “MPL”). Over the next ~9 years, it built up a community that included thousands of users, contributors, customers, certified practitioners, vendors, and an ecosystem of open-source modules, plugins, libraries, and extensions.| opentofu.org