chore(deps): update dependency opentofu/opentofu to v1.11.2 in dockerfile (main)#6067
Merged
renovate[bot] merged 1 commit intomainfrom Jan 7, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.10.7→1.11.2Release Notes
opentofu/opentofu (opentofu/opentofu)
v1.11.2Compare Source
UPGRADE NOTES:
The change from #2643, that was announced previously in v1.11.0, has been reverted in this release. OpenTofu will no longer directly recommend using the
-exclude=option to work around problems caused by unknown values in provider configurations.Unfortunately there are existing providers that spuriously report that they cannot plan due to unknown values even when planning would have been successful, and so we cannot rely on providers to accurately signal when unknown values are the cause of an error. Using
-excludeis still a valid workaround for these problems even though OpenTofu cannot accurately detect when it's useful to make that suggestion.BUG FIXES:
hashicorp/helmandhashicorp/kubernetesproviders when the provider configuration contains unknown values, as long as the configuration is carefully written to avoid the plan phase actually depending on those values. (#3592)tofu initon Windows with an azurerm backend, the subscription_id is quoted correctly allowing successful authentication. (#3602)Full Changelog: opentofu/opentofu@v1.11.1...v1.11.2
v1.11.1Compare Source
BUG FIXES:
Full Changelog: opentofu/opentofu@v1.11.0...v1.11.1
v1.11.0Compare Source
OpenTofu 1.11.0
We're proud to announce that OpenTofu 1.11.0 is now officially available! 🎉
Highlights
This release cycle introduces major new capabilities and integrations:
Ephemeral Values and Write Only Attributes
Ephemeral resources allow you to work with confidential data, temporary credentials, and transient infrastructure without persisting them to your state.
The
enabledMeta-ArgumentIf you want to conditionally deploy a resource, you no longer have to use
count = var.create_my_resource ? 1 : 0, you can now add the newenabledmeta-argument to your resource to conditionally deploy it.Compatibility Notes
macOS: Requires macOS 12 Monterey or later
Azure Backend (
azurerm):endpointandARM_ENDPOINTconfiguration options are no longer supportedmsi_endpointandARM_MSI_ENDPOINToptions are no longer supportedenvironmentandmetadata_hostarguments are now mutually exclusiveissensitive() Function: Now correctly returns unknown results when evaluating unknown values. Code that previously relied on the incorrect behavior may need updates.
Testing with Mocks: Mock values generated during testing now strictly adhere to provider schemas. Test configurations with invalid mock values will need to be corrected.
S3 Module Installation: When installing module packages from Amazon S3 buckets using S3 source addresses OpenTofu will use the same credentials as the AWS CLI and SDK.
TLS and SSH Security:
draft-miller-ssh-cert-03specification-var/-var-fileduringtofu apply <planfile>:-var/-var-fileduringtofu apply <planfile>to pass again the values for ephemeral variables during apply-var/-var-fileto be used with non-ephemeral variables too, but it will error if the values given for this type of variables is different from the ones given during the plan creationTF_VARvalues should stay consistent betweenplanandapply <planfile>to avoid the errors mentioned aboveReference
Thank you for your continued support and testing of the OpenTofu project!
v1.10.8Compare Source
SECURITY ADVISORIES:
This release contains fixes for some security advisories related to previous releases in this series.
Incorrect handling of excluded subdomain constraint in conjunction with TLS certificates containing wildcard SANs
This release incorporates the upstream fixes for GO-2025-4175.
Excessive CPU usage when reporting error about crafted TLS certificate with many hostnames
This release incorporates the upstream fixes for GO-2025-4155.
Full Changelog: opentofu/opentofu@v1.10.7...v1.10.8
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.