#opentofu (2023-12)

Update CONTRIBUTING.md to remove hold-off message for alpha (#945)

Removed comment about waiting until we’re alpha from contributing.md

What’s Changed

• Fixes #292: Testing feature documentation by @janosdebugs in #939 • Fixes #292: Fixing broken website build by @janosdebugs in #952 • Fix global schema caching by @kislerdm in #954 • Add gcs end-to-end tests to the makefile. by @cube2222 in #955 • Make goreleaser create draft releases instead of full releases, so that we can customize the description. by @cube2222 in #956 • Update aws-sdk-go-base and fix resulting type errors. by @cube2222 in #957 • Improve comments around the global and local provider schema cache. by @cube2222 in #958 • Bump version for new beta. by @cube2222 in #963 • Update CONTRIBUTING.md to remove hold-off message for alpha by @Yantrio in #945

Full Changelog: v1.6.0-beta1…v1.6.0-beta2

Hey, bug fix time! There was a bug with the new global schema cache which caused it to not be used with older versions of providers and could make execution much slower. This is now fixed. You can …

Hi opentofu developers, I am switching my workload from terraform to opentofu. When I use 1.6.0-alpha5 and aliyun cloud provider 1.213.0, the provider is really slow to orchestrate the resources. I…

Signed-off-by: Jakub Martin [email protected]

Time for another beta release!

This release marks the last of our “renaming” changes. We’re changing the default provider/module namespace in the registry to opentofu. Crucially, the old default namespace and opentofu contain the same providers in the OpenTofu registry, so this change is fully transparent. If you reference providers by name only (like random) then you will see changes to your lockfiles.

You can find more details in the updated changelog!

You can find the whole diff here: v1.6.0-beta2…v1.6.0-beta3

Time for another beta release! This release marks the last of our “renaming” changes. We’re changing the default provider/module namespace in the registry to opentofu. Crucially, the old default na…

Time for another beta release! This release marks the last of our “renaming” changes. We’re changing the default provider/module namespace in the registry to opentofu. Crucially, the old default na…

Signed-off-by: Jakub Martin [email protected]

Bugfix time!

At the end of last week we’ve made a beta release changing the default provider namespace to opentofu. This had some unintended consequences on implicitly merged version requirements if you had providers referenced in both full form and short form. You can read more here.

After evaluating possible solutions to this, in order to provide the most stable experience, we’ve decided that the best course of action will be to roll back the change, avoid changing the default namespace, and instead deprecate the concept of short-form provider references (that skip the namespace) altogether. They will keep working, but there will be a note in the docs and in trace-level logs to encourage using the full form, namespace/provider when referencing providers.

You can find more details in the updated changelog!

You can find the whole diff here: v1.6.0-beta3…v1.6.0-beta4

Important Note: the changes in this release have known issues, please avoid using it and instead use later releases. Time for another beta release! This release marks the last of our “renaming” cha…

Bugfix time! At the end of last week we’ve made a beta release changing the default provider namespace to opentofu. This had some unintended consequences on implicitly merged version requirements i…

OpenTofu Version OpenTofu v1.6.0-beta3 on linux_amd64 + provider registry.opentofu.org/community-terraform-providers/ignition v2.2.2 + provider registry.opentofu.org/datadog/datadog v3.33.0 + provi…

Signed-off-by: Jakub Martin [email protected]

Signed-off-by: Janos Bonic [email protected]

Signed-off-by: Janos Bonic [email protected]

Signed-off-by: Janos Bonic [email protected]

New beta release time!

This one’s fairly tiny, and should be the last beta release before the release candidate next week. It includes:

• GPG-signing for RPM and Debian archives. • Various code and documentation cleanup efforts.

You can find more details in the updated changelog!

You can find the whole diff here: v1.6.0-beta4…v1.6.0-beta5

New beta release time! This one’s fairly tiny, and should be the last beta release before the release candidate next week. It includes:

GPG-signing for RPM and Debian archives. Various code and do…

Signed-off-by: Jakub Martin [email protected]

Time for our first prerelease!

This is a big step for us, and if all goes well, this version will become stable on the 10th of January.

This version includes the new module testing feature, an updated s3 backend, tons of minor improvements, bug fixes, and performance improvements. It also includes our new registry.

This release is a great time to take OpenTofu for a spin, integrate it with your 3rd party tooling, and prepare for the stable release coming soon. You can find our simple migration guide in our documentation.

Importantly, we’ve changed the identity of the cosign signatures to the new version branch, which means that when verifying binaries from GitHub releases, you’ll need to pass --certificate-identity <https://github.com/opentofu/opentofu/.github/workflows/release.yml@refs/heads/v1.6>. This is because branch protection is much stronger than tag protection in GitHub.

You can find the full changelog here.

The tofu test command performs integration tests of OpenTofu modules.

OpenTofu can store state remotely in S3 and lock that state with DynamoDB.