Change Details

New options are available in the proxmox provider plugin so: - Add vmid as defined in proxmox today (so it won't try and generate one for some reason) - Had to inline the "module node" call for the storage0 node (which has more than 1 disk). It's now inlined like the gateway (which has more than 1 network declaration). So it's a bit repetitive but it's declared appropriately. - Separate staging from production to avoid touching the managed production nodes (for now) - As a poor man configuration shared management, i added the staging `terraform.tfstate` within the repository... (no sensible information in there) - Do not fallback to default values. So some properties are not set for everyone (e.g. hypervisor, bridge, etc...). They must be declared explicitely for each node. Now the` terraform plan` for staging looks reasonable. I modified some production nodes according to their current configuration but stopped as it's a subject for another time. (Shout out if i need to remove those but this sounds like lost time to do so, might as well keep it since it's done)

New options are available in the proxmox provider plugin so: - Add vmid as defined in proxmox today (so it won't try and generate one for some reason) - Open multiple configuration variables needed: bridge, balloon, numa, ... - Avoid default values fallback. So some properties are not set for all nodes (e.g. hypervisor, bridge, etc...). They must be declared explicitely for each node instead. - Had to inline the "module node" call [1] for the storage0 node (2 disks to declare). It's now inlined like the gateway (declares 2 networks). So it's a bit repetitive but it's declared appropriately. - Separate `staging` nodes (from `production`) to its own arborescence. So we don't touch the production nodes when applying - As a poor man configuration shared management, added the staging `terraform.tfstate` within the staging arborescence... (no sensible information in there plus now we can share that state) - Ignore the target_node/hypervisor change (as required in the diff) Now the` terraform plan` for staging looks reasonable. I modified some production nodes according to their current configuration but stopped as it's a subject for another time. (Shout out if i need to remove those but this sounds like lost time to do so, might as well keep it since it's done) [1] The module node only allows 1 disk and 1 network declaration. At the time of its design, determining how to do conditional was not found.

New options are available in the proxmox provider plugin so: - Add vmid as defined in proxmox today (so it won't try and generate one for some reason) - Had to inline the "module node" call for the storage0 node (which has more than 1 disk).Open multiple configuration variables needed: bridge, balloon, numa, ... - Avoid default values fallback. So some properties are not set for all nodes (e.g. hypervisor, bridge, It's now inlined like the gateway (which has more than 1 network declarationetc...). So it's a bit repetitive but it's declared appropriatelyThey must be declared explicitely for each node instead. - Separate staging from production to avoid touching the managed production nodes (for now)Had to inline the "module node" call [1] for the storage0 node (2 disks to declare). It's now inlined like the gateway (declares 2 networks). So it's a bit repetitive but it's declared appropriately. - As a poor man configuration shared management, i added the staging `terraform.tfstate` within the repository..- Separate `staging` nodes (from `production`) to its own arborescence. (no sensible informaSo we don't touch the production in there)nodes when applying - Do not fallback to default values. So some properties are not set for everyone (e.g.- As a poor man configuration shared management, hypervisor, bridge,added the staging `terraform.tfstate` within the staging arborescence... etc...). They must be declared explicitely for each node.(no sensible information in there plus now we can share that state) - Ignore the target_node/hypervisor change (as required in the diff) Now the` terraform plan` for staging looks reasonable. I modified some production nodes according to their current configuration but but stopped as it's a subject for another time. (Shout out if i need to remove those but this sounds like lost time to do so, might as well keep it since it's done) [1] The module node only allows 1 disk and 1 network declaration. At the time of its design, determining how to do conditional was not found. (Shout out if i need to remove those but this sounds like lost time to do so, might as well keep it since it's done)