declaratively manage infrastructure
Project homepage: https://opentofu.org/
Description
OpenTofu is an OSS tool for building, changing, and versioning infrastructure
safely and efficiently. OpenTofu can manage existing and popular service
providers as well as custom in-house solutions.
The key features of OpenTofu are:
Infrastructure as Code: Infrastructure is described using a high-level
configuration syntax. This allows a blueprint of your datacenter to be versioned
and treated as you would any other code. Additionally, infrastructure can be
shared and re-used.
Execution Plans: OpenTofu has a "planning" step where it generates an execution
plan. The execution plan shows what OpenTofu will do when you call apply. This
lets you avoid any surprises when OpenTofu manipulates infrastructure.
Resource Graph: OpenTofu builds a graph of all your resources, and parallelizes
the creation and modification of any non-dependent resources. Because of this,
OpenTofu builds infrastructure as efficiently as possible, and operators get
insight into dependencies in their infrastructure.
Change Automation: Complex changesets can be applied to your infrastructure with
minimal human interaction. With the previously mentioned execution plan and
resource graph, you know exactly what OpenTofu will change and in what order,
avoiding many possible human errors.
Package information
- Ports path
- sysutils/opentofu
- Package architecture
- amd64
- Maintainer
- Antoine Jacoutot <ajacoutot@openbsd.org>
- Categories
- sysutils, net, lang/go
- Available flavors
- None listed
- Only for architectures
- aarch64, amd64, arm, i386, riscv64
Ports list build and test dependencies as well as runtime dependencies. pkg_add selects those needed for installation.
Direct dependencies
Build
OpenBSD README
This README contains unresolved ports variables; replace them before using its commands.
+-------------------------------------------------------------------------------
| Running opentofu on OpenBSD
+-------------------------------------------------------------------------------
Most plugins and providers are available for OpenBSD on the the OpenTofu
registry (https://search.opentofu.org/).
Here's a sample build procedure for missing or in-house plugins and providers.
Example: Terraform AWS provider; version 6.50.0
===============================================
Building
--------
A few packages are required for building:
# pkg_add bash git gmake go
$ git clone https://github.com/opentofu/terraform-provider-aws
$ cd terraform-provider-aws
Choose the release tag you want to build:
$ git fetch --all --tags && git checkout tags/v6.50.0 -b 6.50.0
Go eats a lot of memory and you may need to bump your limits (`ulimit -d`).
Build the provider (manual fixes may be needed to properly build on OpenBSD)
$ gmake build
The provider will be available at ${GOPATH}/bin/terraform-provider-aws.
GOPATH defaults to ${HOME}/go/bin.
Installing
----------
Providers can be installed under any of these directories:
${PWD}/terraform.d/plugins
~/.terraform.d/plugins
~/.local/share/terraform/plugins
${TRUEPREFIX}/share/terraform/plugins
They must follow the sub-hierarchy according to the plugin configuration.
Using this code in the Terraform configuration...
---8<-------------------------
terraform {
required_providers {
aws = {
source = "hashicorp/aws"
version = "6.50.0"
}
}
}
provider "aws" {
# Configuration options
}
---8<-------------------------
... means the Terraform AWS provider for OpenBSD/amd64 must be installed as:
${PLUGINSDIR}/registry.opentofu.org/hashicorp/aws/6.50.0/openbsd_amd64/terraform-provider-aws
`tofu init` should now be able to detect this provider plugin.