Skip to content

Allow multiple networks declaration

Same as for disks... Unfortunately a bit more involved. Although, i quite like it forces to declare explicitely the gateway now.

Test Plan

terraform plan says:

"Nothing to do, move along, move along"

terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

module.worker1.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/118]
module.webapp.proxmox_vm_qemu.node: Refreshing state... [id=branly/qemu/119]
module.db0.proxmox_vm_qemu.node: Refreshing state... [id=orsay/qemu/115]
module.worker2.proxmox_vm_qemu.node: Refreshing state... [id=branly/qemu/112]
module.storage0.proxmox_vm_qemu.node: Refreshing state... [id=orsay/qemu/114]
module.journal0.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/122]
module.gateway.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/109]
module.scheduler0.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/116]
module.worker0.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/117]
module.deposit.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/120]
module.vault.proxmox_vm_qemu.node: Refreshing state... [id=beaubourg/qemu/121]

------------------------------------------------------------------------

No changes. Infrastructure is up-to-date.

This means that Terraform did not detect any differences between your
configuration and real physical resources that exist. As a result, no
actions need to be performed.

Migrated from D4195 (view on Phabricator)

Merge request reports