chore(deps): update terraform http to v3.6.0 #24

Merged
Peter merged 2 commits from renovate/http-3.x into main 2026-05-26 15:44:13 +02:00
Collaborator

This PR contains the following updates:

Package Type Update Change
http (source) required_provider minor 3.5.03.6.0

Release Notes

hashicorp/terraform-provider-http (http)

v3.6.0

Compare Source

ENHANCEMENTS:

  • Added linux/s390x build target for IBM Z platform support (#​613)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 6am on Tuesday"
  • 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 Mend Renovate.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [http](https://search.opentofu.org/provider/hashicorp/http) ([source](https://github.com/hashicorp/terraform-provider-http)) | required_provider | minor | `3.5.0` → `3.6.0` | --- ### Release Notes <details> <summary>hashicorp/terraform-provider-http (http)</summary> ### [`v3.6.0`](https://github.com/hashicorp/terraform-provider-http/blob/HEAD/CHANGELOG.md#360-May-12-2026) [Compare Source](https://github.com/hashicorp/terraform-provider-http/compare/v3.5.0...v3.6.0) ENHANCEMENTS: - Added linux/s390x build target for IBM Z platform support ([#&#8203;613](https://github.com/hashicorp/terraform-provider-http/issues/613)) </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - "before 6am on Tuesday" - 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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xNjEuMCIsInVwZGF0ZWRJblZlciI6IjQzLjE2MS4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJyZW5vdmF0ZSJdfQ==-->
renovate added 1 commit 2026-05-19 02:02:24 +02:00
chore(deps): update terraform http to v3.6.0
All checks were successful
Tofu Plan pve01.wheatley.in templates / tofu-plan-templates (pull_request) Successful in 23s
818b7e6ac3
First-time contributor

Tofu Plan pve01.wheatley.in templates

OpenTofu Format and Style 🖌

OpenTofu Initialization ⚙️

OpenTofu Validation 🤖

Validation Output
Success! The configuration is valid.

OpenTofu Plan 📖

Show Plan
OpenTofu used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place (current -> planned)

OpenTofu will perform the following actions:

  # module.talos.proxmox_virtual_environment_vm.talos-template[1.12.6] will be updated in-place
  ~ resource proxmox_virtual_environment_vm talos-template {
        id                                   = 11126
      ~ ipv4_addresses                       = [] -> (known after apply)
      ~ ipv6_addresses                       = [] -> (known after apply)
        name                                 = talos-template-1.12.6
      ~ network_interface_names              = [] -> (known after apply)
        tags                                 = [
            tofu,
        ]
        # (28 unchanged attributes hidden)

        # (7 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so OpenTofu can't
guarantee to take exactly these actions if you run tofu apply now.
### Tofu Plan pve01.wheatley.in templates #### ✅ OpenTofu Format and Style 🖌 #### ✅ OpenTofu Initialization ⚙️ #### ✅ OpenTofu Validation 🤖 <details><summary>Validation Output</summary> ``` Success! The configuration is valid. ``` </details> #### ✅ OpenTofu Plan 📖 <details><summary>Show Plan</summary> ``` OpenTofu used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: ~ update in-place (current -> planned) OpenTofu will perform the following actions: # module.talos.proxmox_virtual_environment_vm.talos-template[1.12.6] will be updated in-place ~ resource proxmox_virtual_environment_vm talos-template { id = 11126 ~ ipv4_addresses = [] -> (known after apply) ~ ipv6_addresses = [] -> (known after apply) name = talos-template-1.12.6 ~ network_interface_names = [] -> (known after apply) tags = [ tofu, ] # (28 unchanged attributes hidden) # (7 unchanged blocks hidden) } Plan: 0 to add, 1 to change, 0 to destroy. ───────────────────────────────────────────────────────────────────────────── Note: You didn't use the -out option to save this plan, so OpenTofu can't guarantee to take exactly these actions if you run tofu apply now. ``` </details>
Peter added 1 commit 2026-05-26 15:42:03 +02:00
Merge branch 'main' into renovate/http-3.x
All checks were successful
Tofu Plan pve01.wheatley.in templates / tofu-plan-templates (pull_request) Successful in 23s
db04e17d22
Peter merged commit 26762bfdd7 into main 2026-05-26 15:44:13 +02:00
First-time contributor

Tofu Apply pve01.wheatley.in templates

OpenTofu Format and Style 🖌

OpenTofu Initialization ⚙️

OpenTofu Validation 🤖

Validation Output
Success! The configuration is valid.

OpenTofu Apply 🚀

Show Apply
OpenTofu used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place (current -> planned)

OpenTofu will perform the following actions:

  # module.talos.proxmox_virtual_environment_vm.talos-template[1.12.6] will be updated in-place
  ~ resource proxmox_virtual_environment_vm talos-template {
        id                                   = 11126
      ~ ipv4_addresses                       = [] -> (known after apply)
      ~ ipv6_addresses                       = [] -> (known after apply)
        name                                 = talos-template-1.12.6
      ~ network_interface_names              = [] -> (known after apply)
        tags                                 = [
            tofu,
        ]
        # (28 unchanged attributes hidden)

        # (7 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.
module.talos.proxmox_virtual_environment_vm.talos-template[1.12.6]: Modifying... [id=11126]
module.talos.proxmox_virtual_environment_vm.talos-template[1.12.6]: Modifications complete after 0s [id=11126]

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
### Tofu Apply pve01.wheatley.in templates #### ✅ OpenTofu Format and Style 🖌 #### ✅ OpenTofu Initialization ⚙️ #### ✅ OpenTofu Validation 🤖 <details><summary>Validation Output</summary> ``` Success! The configuration is valid. ``` </details> #### ✅ OpenTofu Apply 🚀 <details><summary>Show Apply</summary> ``` OpenTofu used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: ~ update in-place (current -> planned) OpenTofu will perform the following actions: # module.talos.proxmox_virtual_environment_vm.talos-template[1.12.6] will be updated in-place ~ resource proxmox_virtual_environment_vm talos-template { id = 11126 ~ ipv4_addresses = [] -> (known after apply) ~ ipv6_addresses = [] -> (known after apply) name = talos-template-1.12.6 ~ network_interface_names = [] -> (known after apply) tags = [ tofu, ] # (28 unchanged attributes hidden) # (7 unchanged blocks hidden) } Plan: 0 to add, 1 to change, 0 to destroy. module.talos.proxmox_virtual_environment_vm.talos-template[1.12.6]: Modifying... [id=11126] module.talos.proxmox_virtual_environment_vm.talos-template[1.12.6]: Modifications complete after 0s [id=11126] Apply complete! Resources: 0 added, 1 changed, 0 destroyed. ``` </details>
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: wheatley/infrastructure#24
No description provided.