chore(deps): update dependency opentofu/opentofu to v1.8.7

[renovate]

This PR contains the following updates:

Package	Update	Change
opentofu/opentofu	patch	v1.8.2 -> v1.8.7

---

Release Notes

opentofu/opentofu (opentofu/opentofu)

v1.8.7

Compare Source

BUG FIXES:

• Error messages related to validation of sensitive input variables will no longer disclose the sensitive value in the UI. (#​2219)
• Changes to encryption configuration now auto-apply the migration (#​2232)
• Updated github.com/golang-jwt/jwt/v4 from 4.4.2 to 4.5.1 to make security scanners happy (no vulnerability, see #​2179)
• tofu test is now setting nulls for dynamic type when generating mock values. (#​2245)
• Variables declared in test files are now taking into account type default values. (#​2244)

v1.8.6

Compare Source

ENHANCEMENTS:

• OpenTofu builds now use Go version 1.22 (#​2050)

BUG FIXES:

• Extended trace logging for HTTP backend, including request and response bodies. (#​2120)
• The tofu test command doesn't try to validate mock provider definition by its underlying provider schema now. (#​2140)
• Type validation for mocks and overrides are now less strict in tofu test. (#​2144)

v1.8.5

Compare Source

BUG FIXES:

• Provider functions will now handle partially unknown arguments per the tfplugin spec (#​2127)
• tofu init will no longer return a spurious "Backend configuration changed" error when re-initializing a working directory with existing initialization of a backend whose configuration schema has required arguments. This was a regression caused by the similar fix in the v1.8.4 release. (#​2135)

Full Changelog: opentofu/opentofu@v1.8.4...v1.8.5

v1.8.4

Compare Source

BUG FIXES:

• tofu init will no longer return a supurious "Backend configuration changed" error when re-initializing a working directory with identical settings, backend configuration contains references to variables or local values, and when the -backend-config command line option is used. That combination previously caused OpenTofu to incorrectly treat the backend configuration as invalid. (#​2055)
• configuration generation should no longer fail when generating sensitive properties
• Provider defined functions are now supported better in child modules
• Fixed an issue where X-Terraform-Get was not being read correctly if a custom module registry returns a 200 statuscode instead of 201

Full Changelog: opentofu/opentofu@v1.8.3...v1.8.4

v1.8.3

Compare Source

What's Changed

SECURITY:

• Added option to enable the sensitive flag for variables used in module sources/versions and backend configurations.
  • This emits a warning by default to prevent breaking compatability with previous 1.8.x versions.
  • It is highly recommended to set TOFU_ENABLE_STATIC_SENSITIVE=1 in any environments using this release.
  • This will be enabled by default as a breaking change in v1.9.0

BUG FIXES:

• Fixed autoloaded test tfvar files being used in non-test scenarios (#​2039)
• Fixed crash when using sensitive values in module sources/versions and backend configurations (#​2046)

Full Changelog: opentofu/opentofu@v1.8.2...v1.8.3

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.