chore(deps): update terraform proxmox to v0.116.0 #45

Merged
Peter merged 1 commit from renovate/proxmox-0.x into main 2026-10-07 17:29:52 +02:00
Collaborator

This PR contains the following updates:

Package Type Update Change
proxmox (source) required_provider minor 0.114.0 → 0.116.0

Release Notes

bpg/terraform-provider-proxmox (proxmox)

v0.116.0

Compare Source

Features
Bug Fixes
Miscellaneous

v0.115.0

Compare Source

Features
  • backup: add comment to backup job resource and data source (#​3107) (81b61dc)
Bug Fixes
Miscellaneous
  • deps: update golangci/golangci-lint (v2.13.2 → v2.14.0) (#​3119) (8033af1)
  • deps: update module github.com/brianvoe/gofakeit/v7 (v7.17.0 → v7.17.1) (#​3118) (c94b2ca)

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 | |---|---|---|---| | [proxmox](https://search.opentofu.org/provider/bpg/proxmox) ([source](https://github.com/bpg/terraform-provider-proxmox)) | required_provider | minor | `0.114.0` → `0.116.0` | --- ### Release Notes <details> <summary>bpg/terraform-provider-proxmox (proxmox)</summary> ### [`v0.116.0`](https://github.com/bpg/terraform-provider-proxmox/blob/HEAD/CHANGELOG.md#01160-2026-10-06) [Compare Source](https://github.com/bpg/terraform-provider-proxmox/compare/v0.115.0...v0.116.0) ##### Features - **backup:** add `notification_mode` to backup job ([#&#8203;3130](https://github.com/bpg/terraform-provider-proxmox/issues/3130)) ([3685082](https://github.com/bpg/terraform-provider-proxmox/commit/3685082bbe88428aab312f05044fcf7bd811831d)) - **lxc:** migrate container on node change ([#&#8203;3104](https://github.com/bpg/terraform-provider-proxmox/issues/3104)) ([c7c4177](https://github.com/bpg/terraform-provider-proxmox/commit/c7c417708e733ce0eedb066534509ac2b35edcb2)) - **ssh:** add docs link to SSH connection errors ([#&#8203;3128](https://github.com/bpg/terraform-provider-proxmox/issues/3128)) ([08f8d94](https://github.com/bpg/terraform-provider-proxmox/commit/08f8d940707b41b488a35a3c17aa65ea8c812865)) ##### Bug Fixes - **access:** preserve user token state diagnostics ([#&#8203;3132](https://github.com/bpg/terraform-provider-proxmox/issues/3132)) ([39cdb0f](https://github.com/bpg/terraform-provider-proxmox/commit/39cdb0fceb281ef73ec5768dcd05dbc9f7a3a3b6)) - **file:** fallback to other nodes for state refresh ([#&#8203;3122](https://github.com/bpg/terraform-provider-proxmox/issues/3122)) ([6ea92ce](https://github.com/bpg/terraform-provider-proxmox/commit/6ea92ce21b40d6c786550c548b3061a7563694de)) - **vm:** refresh smbios from Proxmox for cloned VMs ([#&#8203;3131](https://github.com/bpg/terraform-provider-proxmox/issues/3131)) ([86bcfcc](https://github.com/bpg/terraform-provider-proxmox/commit/86bcfcc6264e82511ff38ae4453ff58ad9616728)) - **vm:** reject initialization interface that collides with disk or efi\_disk ([#&#8203;3127](https://github.com/bpg/terraform-provider-proxmox/issues/3127)) ([6c41063](https://github.com/bpg/terraform-provider-proxmox/commit/6c41063d5890f0aa11fb5fe9d89b70a079e82d47)) ##### Miscellaneous - **deps:** update image golang ([`3680233`](https://github.com/bpg/terraform-provider-proxmox/commit/3680233) → [`e0174e5`](https://github.com/bpg/terraform-provider-proxmox/commit/e0174e5)) ([#&#8203;3125](https://github.com/bpg/terraform-provider-proxmox/issues/3125)) ([6b83622](https://github.com/bpg/terraform-provider-proxmox/commit/6b836227f497ebcb1f38071964a3761bff3aaa9c)) ### [`v0.115.0`](https://github.com/bpg/terraform-provider-proxmox/blob/HEAD/CHANGELOG.md#01150-2026-10-02) [Compare Source](https://github.com/bpg/terraform-provider-proxmox/compare/v0.114.0...v0.115.0) ##### Features - **backup:** add comment to backup job resource and data source ([#&#8203;3107](https://github.com/bpg/terraform-provider-proxmox/issues/3107)) ([81b61dc](https://github.com/bpg/terraform-provider-proxmox/commit/81b61dc123b28ab1a4d07f59faff12dc6661c5c9)) ##### Bug Fixes - **lxc:** backfill container timeout defaults on import ([#&#8203;3111](https://github.com/bpg/terraform-provider-proxmox/issues/3111)) ([0ed18bd](https://github.com/bpg/terraform-provider-proxmox/commit/0ed18bd2de11b5ee7ddbcd0b744756b1987988f2)) - **lxc:** resolve container node from the cluster on read and delete ([#&#8203;3115](https://github.com/bpg/terraform-provider-proxmox/issues/3115)) ([f7f4622](https://github.com/bpg/terraform-provider-proxmox/commit/f7f462263146874044a14104a6c445084b9b099b)) - **test:** allow overriding the container test datastore ([#&#8203;3114](https://github.com/bpg/terraform-provider-proxmox/issues/3114)) ([47d1b06](https://github.com/bpg/terraform-provider-proxmox/commit/47d1b06b461bf544ff8b3f0d18fc5ab84ea55bcb)) - **vm:** send smbios.sku to Proxmox ([#&#8203;3120](https://github.com/bpg/terraform-provider-proxmox/issues/3120)) ([c42a893](https://github.com/bpg/terraform-provider-proxmox/commit/c42a893f5142a748b78b8292707d73efd98864d7)) ##### Miscellaneous - **deps:** update golangci/golangci-lint (v2.13.2 → v2.14.0) ([#&#8203;3119](https://github.com/bpg/terraform-provider-proxmox/issues/3119)) ([8033af1](https://github.com/bpg/terraform-provider-proxmox/commit/8033af1ce3c2d2d02ff5df585cda50cee469ee77)) - **deps:** update module github.com/brianvoe/gofakeit/v7 (v7.17.0 → v7.17.1) ([#&#8203;3118](https://github.com/bpg/terraform-provider-proxmox/issues/3118)) ([c94b2ca](https://github.com/bpg/terraform-provider-proxmox/commit/c94b2caf2f2b4148b9cb0542b4e275a80d88d4f6)) </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==-->
chore(deps): update terraform proxmox to v0.115.0
All checks were successful
Tofu Plan pve01.wheatley.in containers / tofu-plan-containers (pull_request) Successful in 24s
Tofu Plan k8s-wheatley / tofu-plan-k8s-wheatley (pull_request) Successful in 27s
Tofu Plan pve01.wheatley.in templates / tofu-plan-templates (pull_request) Successful in 24s
a3fa7b514e

Tofu Plan pve01.wheatley.in containers

✅ OpenTofu Format and Style 🖌

✅ OpenTofu Initialization ⚙️

✅ OpenTofu Validation 🤖

Validation Output
Success! The configuration is valid.

✅ OpenTofu Plan 📖

Show Plan
proxmox_network_linux_bridge.internal: Refreshing state... [id=pve01:vmbr9]
proxmox_oci_image.alloy: Refreshing state... [id=local:vztmpl/alloy_v1.17.0.tar]
proxmox_oci_image.pve_exporter: Refreshing state... [id=local:vztmpl/prometheus-pve-exporter_3.4.7.tar]
proxmox_virtual_environment_container.pve_exporter: Refreshing state... [id=901]

OpenTofu used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

OpenTofu will perform the following actions:

  # proxmox_virtual_environment_container.alloy will be created
  + resource proxmox_virtual_environment_container alloy {
      + delete_unreferenced_disks_on_destroy = false
      + id                                   = (known after apply)
      + ipv4                                 = (known after apply)
      + ipv6                                 = (known after apply)
      + migrate                              = false
      + node_name                            = pve01
      + protection                           = false
      + purge_on_destroy                     = true
      + start_on_boot                        = true
      + started                              = true
      + tags                                 = [
          + tofu,
          + monitoring,
        ]
      + template                             = false
      + timeout_clone                        = 1800
      + timeout_create                       = 1800
      + timeout_delete                       = 60
      + timeout_migrate                      = 1800
      + timeout_start                        = 300
      + timeout_update                       = 1800
      + unprivileged                         = true
      + vm_id                                = 900

      + cpu {
          + architecture = amd64
          + cores        = 1
          + limit        = 0
          + units        = (known after apply)
        }

      + disk {
          + acl               = false
          + datastore_id      = nvme-fastpool
          + path_in_datastore = (known after apply)
          + quota             = false
          + replicate         = false
          + size              = 4
        }

      + initialization {
          + entrypoint = /bin/alloy run --server.http.listen-addr=0.0.0.0:12345 --storage.path=/var/lib/alloy/data /etc/alloy-conf/monitoring-config.alloy
          + hostname   = alloy

          + dns {
              + servers = [
                  + 9.9.9.9,
                ]
            }

          + ip_config {
              + ipv4 {
                  + address = 10.13.37.4/24
                  + gateway = 10.13.37.1
                }
            }
          + ip_config {
              + ipv4 {
                  + address = 10.10.10.4/24
                }
            }
        }

      + memory {
          + dedicated = 512
          + swap      = 0
        }

      + mount_point {
          + acl               = false
          + backup            = false
          + path              = /etc/alloy-conf
          + path_in_datastore = (known after apply)
          + quota             = false
          + read_only         = true
          + replicate         = true
          + shared            = false
          + volume            = /var/lib/vz/snippets/alloy
        }

      + network_interface {
          + bridge       = vmbr1
          + enabled      = true
          + firewall     = false
          + host_managed = false
          + mac_address  = (known after apply)
          + mtu          = 0
          + name         = eth0
          + rate_limit   = 0
          + vlan_id      = 0
        }
      + network_interface {
          + bridge       = vmbr9
          + enabled      = true
          + firewall     = false
          + host_managed = false
          + mac_address  = (known after apply)
          + mtu          = 0
          + name         = eth1
          + rate_limit   = 0
          + vlan_id      = 0
        }

      + operating_system {
          + template_file_id = local:vztmpl/alloy_v1.17.0.tar
          + type             = unmanaged
        }
    }

  # proxmox_virtual_environment_file.alloy_config will be created
  + resource proxmox_virtual_environment_file alloy_config {
      + content_type           = snippets
      + datastore_id           = local
      + file_modification_date = (known after apply)
      + file_name              = (known after apply)
      + file_size              = (known after apply)
      + file_tag               = (known after apply)
      + id                     = (known after apply)
      + node_name              = pve01
      + overwrite              = true
      + timeout_upload         = 1800
      + upload_mode            = stream

      + source_file {
          + changed   = false
          + file_name = alloy/monitoring-config.alloy
          + insecure  = false
          + path      = ./files/config.alloy
        }
    }

Plan: 2 to add, 0 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 containers #### ✅ 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> ``` proxmox_network_linux_bridge.internal: Refreshing state... [id=pve01:vmbr9] proxmox_oci_image.alloy: Refreshing state... [id=local:vztmpl/alloy_v1.17.0.tar] proxmox_oci_image.pve_exporter: Refreshing state... [id=local:vztmpl/prometheus-pve-exporter_3.4.7.tar] proxmox_virtual_environment_container.pve_exporter: Refreshing state... [id=901] OpenTofu used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create OpenTofu will perform the following actions: # proxmox_virtual_environment_container.alloy will be created + resource proxmox_virtual_environment_container alloy { + delete_unreferenced_disks_on_destroy = false + id = (known after apply) + ipv4 = (known after apply) + ipv6 = (known after apply) + migrate = false + node_name = pve01 + protection = false + purge_on_destroy = true + start_on_boot = true + started = true + tags = [ + tofu, + monitoring, ] + template = false + timeout_clone = 1800 + timeout_create = 1800 + timeout_delete = 60 + timeout_migrate = 1800 + timeout_start = 300 + timeout_update = 1800 + unprivileged = true + vm_id = 900 + cpu { + architecture = amd64 + cores = 1 + limit = 0 + units = (known after apply) } + disk { + acl = false + datastore_id = nvme-fastpool + path_in_datastore = (known after apply) + quota = false + replicate = false + size = 4 } + initialization { + entrypoint = /bin/alloy run --server.http.listen-addr=0.0.0.0:12345 --storage.path=/var/lib/alloy/data /etc/alloy-conf/monitoring-config.alloy + hostname = alloy + dns { + servers = [ + 9.9.9.9, ] } + ip_config { + ipv4 { + address = 10.13.37.4/24 + gateway = 10.13.37.1 } } + ip_config { + ipv4 { + address = 10.10.10.4/24 } } } + memory { + dedicated = 512 + swap = 0 } + mount_point { + acl = false + backup = false + path = /etc/alloy-conf + path_in_datastore = (known after apply) + quota = false + read_only = true + replicate = true + shared = false + volume = /var/lib/vz/snippets/alloy } + network_interface { + bridge = vmbr1 + enabled = true + firewall = false + host_managed = false + mac_address = (known after apply) + mtu = 0 + name = eth0 + rate_limit = 0 + vlan_id = 0 } + network_interface { + bridge = vmbr9 + enabled = true + firewall = false + host_managed = false + mac_address = (known after apply) + mtu = 0 + name = eth1 + rate_limit = 0 + vlan_id = 0 } + operating_system { + template_file_id = local:vztmpl/alloy_v1.17.0.tar + type = unmanaged } } # proxmox_virtual_environment_file.alloy_config will be created + resource proxmox_virtual_environment_file alloy_config { + content_type = snippets + datastore_id = local + file_modification_date = (known after apply) + file_name = (known after apply) + file_size = (known after apply) + file_tag = (known after apply) + id = (known after apply) + node_name = pve01 + overwrite = true + timeout_upload = 1800 + upload_mode = stream + source_file { + changed = false + file_name = alloy/monitoring-config.alloy + insecure = false + path = ./files/config.alloy } } Plan: 2 to add, 0 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>

Tofu Plan k8s-wheatley

✅ OpenTofu Format and Style 🖌

✅ OpenTofu Initialization ⚙️

✅ OpenTofu Validation 🤖

Validation Output
Success! The configuration is valid.

✅ OpenTofu Plan 📖

Show Plan
No changes. Your infrastructure matches the configuration.

OpenTofu has compared your real infrastructure against your configuration and
found no differences, so no changes are needed.
### Tofu Plan k8s-wheatley #### ✅ 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> ``` No changes. Your infrastructure matches the configuration. OpenTofu has compared your real infrastructure against your configuration and found no differences, so no changes are needed. ``` </details>

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.14.0] will be updated in-place
  ~ resource proxmox_virtual_environment_vm talos-template {
        id                                   = 11140
      ~ ipv4_addresses                       = [] -> (known after apply)
      ~ ipv6_addresses                       = [] -> (known after apply)
        name                                 = talos-template-1.14.0
      ~ 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.14.0] will be updated in-place ~ resource proxmox_virtual_environment_vm talos-template { id = 11140 ~ ipv4_addresses = [] -> (known after apply) ~ ipv6_addresses = [] -> (known after apply) name = talos-template-1.14.0 ~ 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>
renovate force-pushed renovate/proxmox-0.x from a3fa7b514e
All checks were successful
Tofu Plan pve01.wheatley.in containers / tofu-plan-containers (pull_request) Successful in 24s
Tofu Plan k8s-wheatley / tofu-plan-k8s-wheatley (pull_request) Successful in 27s
Tofu Plan pve01.wheatley.in templates / tofu-plan-templates (pull_request) Successful in 24s
to d661b74a52
Some checks failed
Tofu Plan k8s-wheatley / tofu-plan-k8s-wheatley (pull_request) Failing after 19s
Tofu Plan pve01.wheatley.in containers / tofu-plan-containers (pull_request) Successful in 20s
Tofu Plan pve01.wheatley.in templates / tofu-plan-templates (pull_request) Successful in 25s
2026-10-07 02:04:27 +02:00
Compare
renovate changed title from chore(deps): update terraform proxmox to v0.115.0 to chore(deps): update terraform proxmox 2026-10-07 02:04:32 +02:00
renovate force-pushed renovate/proxmox-0.x from d661b74a52
Some checks failed
Tofu Plan k8s-wheatley / tofu-plan-k8s-wheatley (pull_request) Failing after 19s
Tofu Plan pve01.wheatley.in containers / tofu-plan-containers (pull_request) Successful in 20s
Tofu Plan pve01.wheatley.in templates / tofu-plan-templates (pull_request) Successful in 25s
to 7a12da555c
All checks were successful
Tofu Plan pve01.wheatley.in containers / tofu-plan-containers (pull_request) Successful in 37s
Tofu Plan k8s-wheatley / tofu-plan-k8s-wheatley (pull_request) Successful in 47s
Tofu Plan pve01.wheatley.in templates / tofu-plan-templates (pull_request) Successful in 45s
2026-10-07 10:01:41 +02:00
Compare
renovate changed title from chore(deps): update terraform proxmox to chore(deps): update terraform proxmox to v0.116.0 2026-10-07 10:01:48 +02:00
Peter merged commit 8774f61603 into main 2026-10-07 17:29:52 +02:00

Tofu Apply pve01.wheatley.in containers

✅ OpenTofu Format and Style 🖌

✅ OpenTofu Initialization ⚙️

✅ OpenTofu Validation 🤖

Validation Output
Success! The configuration is valid.

❌ OpenTofu Apply 🚀

Show Apply
proxmox_oci_image.alloy: Refreshing state... [id=local:vztmpl/alloy_v1.17.0.tar]
proxmox_network_linux_bridge.internal: Refreshing state... [id=pve01:vmbr9]
proxmox_oci_image.pve_exporter: Refreshing state... [id=local:vztmpl/prometheus-pve-exporter_3.4.7.tar]
proxmox_virtual_environment_container.pve_exporter: Refreshing state... [id=901]

OpenTofu used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

OpenTofu will perform the following actions:

  # proxmox_virtual_environment_container.alloy will be created
  + resource proxmox_virtual_environment_container alloy {
      + delete_unreferenced_disks_on_destroy = false
      + id                                   = (known after apply)
      + ipv4                                 = (known after apply)
      + ipv6                                 = (known after apply)
      + migrate                              = false
      + node_name                            = pve01
      + protection                           = false
      + purge_on_destroy                     = true
      + start_on_boot                        = true
      + started                              = true
      + tags                                 = [
          + tofu,
          + monitoring,
        ]
      + template                             = false
      + timeout_clone                        = 1800
      + timeout_create                       = 1800
      + timeout_delete                       = 60
      + timeout_migrate                      = 1800
      + timeout_start                        = 300
      + timeout_update                       = 1800
      + unprivileged                         = true
      + vm_id                                = 900

      + cpu {
          + architecture = amd64
          + cores        = 1
          + limit        = 0
          + units        = (known after apply)
        }

      + disk {
          + acl               = false
          + datastore_id      = nvme-fastpool
          + path_in_datastore = (known after apply)
          + quota             = false
          + replicate         = false
          + size              = 4
        }

      + initialization {
          + entrypoint = /bin/alloy run --server.http.listen-addr=0.0.0.0:12345 --storage.path=/var/lib/alloy/data /etc/alloy-conf/monitoring-config.alloy
          + hostname   = alloy

          + dns {
              + servers = [
                  + 9.9.9.9,
                ]
            }

          + ip_config {
              + ipv4 {
                  + address = 10.13.37.4/24
                  + gateway = 10.13.37.1
                }
            }
          + ip_config {
              + ipv4 {
                  + address = 10.10.10.4/24
                }
            }
        }

      + memory {
          + dedicated = 512
          + swap      = 0
        }

      + mount_point {
          + acl               = false
          + backup            = false
          + path              = /etc/alloy-conf
          + path_in_datastore = (known after apply)
          + quota             = false
          + read_only         = true
          + replicate         = true
          + shared            = false
          + volume            = /var/lib/vz/snippets/alloy
        }

      + network_interface {
          + bridge       = vmbr1
          + enabled      = true
          + firewall     = false
          + host_managed = false
          + mac_address  = (known after apply)
          + mtu          = 0
          + name         = eth0
          + rate_limit   = 0
          + vlan_id      = 0
        }
      + network_interface {
          + bridge       = vmbr9
          + enabled      = true
          + firewall     = false
          + host_managed = false
          + mac_address  = (known after apply)
          + mtu          = 0
          + name         = eth1
          + rate_limit   = 0
          + vlan_id      = 0
        }

      + operating_system {
          + template_file_id = local:vztmpl/alloy_v1.17.0.tar
          + type             = unmanaged
        }
    }

  # proxmox_virtual_environment_file.alloy_config will be created
  + resource proxmox_virtual_environment_file alloy_config {
      + content_type           = snippets
      + datastore_id           = local
      + file_modification_date = (known after apply)
      + file_name              = (known after apply)
      + file_size              = (known after apply)
      + file_tag               = (known after apply)
      + id                     = (known after apply)
      + node_name              = pve01
      + overwrite              = true
      + timeout_upload         = 1800
      + upload_mode            = stream

      + source_file {
          + changed   = false
          + file_name = alloy/monitoring-config.alloy
          + insecure  = false
          + path      = ./files/config.alloy
        }
    }

Plan: 2 to add, 0 to change, 0 to destroy.
proxmox_virtual_environment_file.alloy_config: Creating...
### Tofu Apply pve01.wheatley.in containers #### ✅ 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> ``` proxmox_oci_image.alloy: Refreshing state... [id=local:vztmpl/alloy_v1.17.0.tar] proxmox_network_linux_bridge.internal: Refreshing state... [id=pve01:vmbr9] proxmox_oci_image.pve_exporter: Refreshing state... [id=local:vztmpl/prometheus-pve-exporter_3.4.7.tar] proxmox_virtual_environment_container.pve_exporter: Refreshing state... [id=901] OpenTofu used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create OpenTofu will perform the following actions: # proxmox_virtual_environment_container.alloy will be created + resource proxmox_virtual_environment_container alloy { + delete_unreferenced_disks_on_destroy = false + id = (known after apply) + ipv4 = (known after apply) + ipv6 = (known after apply) + migrate = false + node_name = pve01 + protection = false + purge_on_destroy = true + start_on_boot = true + started = true + tags = [ + tofu, + monitoring, ] + template = false + timeout_clone = 1800 + timeout_create = 1800 + timeout_delete = 60 + timeout_migrate = 1800 + timeout_start = 300 + timeout_update = 1800 + unprivileged = true + vm_id = 900 + cpu { + architecture = amd64 + cores = 1 + limit = 0 + units = (known after apply) } + disk { + acl = false + datastore_id = nvme-fastpool + path_in_datastore = (known after apply) + quota = false + replicate = false + size = 4 } + initialization { + entrypoint = /bin/alloy run --server.http.listen-addr=0.0.0.0:12345 --storage.path=/var/lib/alloy/data /etc/alloy-conf/monitoring-config.alloy + hostname = alloy + dns { + servers = [ + 9.9.9.9, ] } + ip_config { + ipv4 { + address = 10.13.37.4/24 + gateway = 10.13.37.1 } } + ip_config { + ipv4 { + address = 10.10.10.4/24 } } } + memory { + dedicated = 512 + swap = 0 } + mount_point { + acl = false + backup = false + path = /etc/alloy-conf + path_in_datastore = (known after apply) + quota = false + read_only = true + replicate = true + shared = false + volume = /var/lib/vz/snippets/alloy } + network_interface { + bridge = vmbr1 + enabled = true + firewall = false + host_managed = false + mac_address = (known after apply) + mtu = 0 + name = eth0 + rate_limit = 0 + vlan_id = 0 } + network_interface { + bridge = vmbr9 + enabled = true + firewall = false + host_managed = false + mac_address = (known after apply) + mtu = 0 + name = eth1 + rate_limit = 0 + vlan_id = 0 } + operating_system { + template_file_id = local:vztmpl/alloy_v1.17.0.tar + type = unmanaged } } # proxmox_virtual_environment_file.alloy_config will be created + resource proxmox_virtual_environment_file alloy_config { + content_type = snippets + datastore_id = local + file_modification_date = (known after apply) + file_name = (known after apply) + file_size = (known after apply) + file_tag = (known after apply) + id = (known after apply) + node_name = pve01 + overwrite = true + timeout_upload = 1800 + upload_mode = stream + source_file { + changed = false + file_name = alloy/monitoring-config.alloy + insecure = false + path = ./files/config.alloy } } Plan: 2 to add, 0 to change, 0 to destroy. proxmox_virtual_environment_file.alloy_config: Creating... ``` </details>

Tofu Apply k8s-wheatley

✅ OpenTofu Format and Style 🖌

✅ OpenTofu Initialization ⚙️

✅ OpenTofu Validation 🤖

Validation Output
Success! The configuration is valid.

✅ OpenTofu Apply 🚀

Show Apply
No changes. Your infrastructure matches the configuration.

OpenTofu has compared your real infrastructure against your configuration and
found no differences, so no changes are needed.

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Outputs:

kubeconfig = <sensitive>
talosconfig = <sensitive>
### Tofu Apply k8s-wheatley #### ✅ 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> ``` No changes. Your infrastructure matches the configuration. OpenTofu has compared your real infrastructure against your configuration and found no differences, so no changes are needed. Apply complete! Resources: 0 added, 0 changed, 0 destroyed. Outputs: kubeconfig = <sensitive> talosconfig = <sensitive> ``` </details>

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.14.0] will be updated in-place
  ~ resource proxmox_virtual_environment_vm talos-template {
        id                                   = 11140
      ~ ipv4_addresses                       = [] -> (known after apply)
      ~ ipv6_addresses                       = [] -> (known after apply)
        name                                 = talos-template-1.14.0
      ~ 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.14.0]: Modifying... [id=11140]
module.talos.proxmox_virtual_environment_vm.talos-template[1.14.0]: Modifications complete after 1s [id=11140]

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.14.0] will be updated in-place ~ resource proxmox_virtual_environment_vm talos-template { id = 11140 ~ ipv4_addresses = [] -> (known after apply) ~ ipv6_addresses = [] -> (known after apply) name = talos-template-1.14.0 ~ 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.14.0]: Modifying... [id=11140] module.talos.proxmox_virtual_environment_vm.talos-template[1.14.0]: Modifications complete after 1s [id=11140] 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
2 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!45
No description provided.