Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency opentofu/opentofu to v1.9.0 #9490

Merged
merged 1 commit into from
Jan 9, 2025

Conversation

uniget-bot
Copy link

This PR contains the following updates:

Package Update Change
opentofu/opentofu minor 1.8.8 -> 1.9.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

opentofu/opentofu (opentofu/opentofu)

v1.9.0

Compare Source

We're proud to announce that OpenTofu 1.9.0 is now officially out! 🎉

This release includes a lot of major and minor new features, as well as a ton of community contributions!

The highlights are:

  • for_each in provider configuration blocks: An alternate (aka "aliased") provider configuration can now have multiple dynamically-chosen instances using the for_each argument:

    provider "aws" {
      alias    = "by_region"
      for_each = var.aws_regions
    
      region = each.key
    }

    Each instance of a resource can also potentially select a different instance of the associated provider configuration, making it easier to declare infrastructure that ought to be duplicated for each region.

  • -exclude planning option: similar to -target, this allows operators to tell OpenTofu to work on only a subset of the objects declared in the configuration or tracked in the state.

    tofu plan -exclude=kubernetes_manifest.crds

    While -target specifies the objects to include and skips everything not needed for the selected objects, -exclude instead specifies objects to skip. OpenTofu will exclude the selected objects and everything that depends on them.

Please take the above for a spin and let us know your feedback!

For all the features, see the detailed changelog.

You can find the full diff here.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Copy link

@nicholasdille-bot nicholasdille-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved because label type/renovate is present.

Copy link

github-actions bot commented Jan 9, 2025

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/opentofu:1.9.0

📦 Image Reference ghcr.io/uniget-org/tools/opentofu:1.9.0
digestsha256:2f5d5afc7a3f66ba038367290d45efc4da220320392899be9d1a217c1a4d3042
vulnerabilitiescritical: 0 high: 0 medium: 1 low: 1
platformlinux/amd64
size26 MB
packages209
critical: 0 high: 0 medium: 1 low: 1 github.com/aws/aws-sdk-go 1.44.122 (golang)

pkg:golang/github.com/aws/aws-sdk-go@1.44.122

medium : CVE--2020--8911

Affected range>=0
Fixed versionNot Fixed
Description

A padding oracle vulnerability exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. The SDK allows users to encrypt files with AES-CBC without computing a Message Authentication Code (MAC), which then allows an attacker who has write access to the target's S3 bucket and can observe whether or not an endpoint with access to the key can decrypt a file, they can reconstruct the plaintext with (on average) 128*length (plaintext) queries to the endpoint, by exploiting CBC's ability to manipulate the bytes of the next block and PKCS5 padding errors. It is recommended to update your SDK to V2 or later, and re-encrypt your files.

low : CVE--2020--8912

Affected range>=0
Fixed versionNot Fixed
Description

A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. An attacker with write access to the targeted bucket can change the encryption algorithm of an object in the bucket, which can then allow them to change AES-GCM to AES-CTR. Using this in combination with a decryption oracle can reveal the authentication key used by AES-GCM as decrypting the GMAC tag leaves the authentication key recoverable as an algebraic equation. It is recommended to update your SDK to V2 or later, and re-encrypt your files.

Copy link

github-actions bot commented Jan 9, 2025

Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/12694429351.

Copy link

github-actions bot commented Jan 9, 2025

PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/12694429351.

@github-actions github-actions bot merged commit 10c70b5 into main Jan 9, 2025
10 checks passed
@github-actions github-actions bot deleted the renovate/opentofu-opentofu-1.x branch January 9, 2025 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants