hybridops-tech/terraform-proxmox-sdn

Area Provider compatibility Relevant reference versions.tf, the root README, and the five shipped examples in v0.2.0-beta.1. Expected behaviour Every bpg/proxmox release accepted by the module constraint should contain and validate the SDN resources used by the module. Observed behaviour The repository currently advertises bpg/proxmox >= 0.50.0. Provider v0.83.0 and earlier do not contain the VNet and subnet resources used in main.tf. Those resources first appear in v0.84.0, but the current module fails terraform validate against that release with: Error: Invalid Subnet Could not parse subnet: invalid CIDR address: The upstream interpolation fix was included after v0.84.0 in bpg/terraform-provider-proxmox#2204. An exact v0.85.0 provider selection validates successfully. The current main test suite passes with 26 tests, and the head of PR #64 passes with 35 tests. Steps to reproduce Select bpg/proxmox = 0.84.0. Run terraform init -backend=false -input=false. Run terraform validate. O

Area Module inputs or validation Problem The VLAN zone resource fixes mtu at 1500. Operators using jumbo frames or a smaller underlay MTU must fork the module to change one supported provider setting. Proposed change Add a zone_mtu input with a default of 1500, pass it to the VLAN zone resource, and document it in the input table and examples. Validate the value as a whole number within the range supported by Proxmox. Acceptance criteria Existing callers continue to plan with MTU 1500. A caller can set a different supported MTU without editing the module. Invalid values fail during validation. Mocked Terraform tests cover the default, an override, and invalid input. terraform fmt -check -recursive, terraform validate, and terraform test -no-color pass.

Area Proxmox SDN objects Relevant reference v0.2.0-beta.1, vnets.description, main.tf Expected behaviour The description supplied for each VNet should appear on the corresponding Proxmox SDN object. Observed behaviour description is required by the module input, but the VNet resource only sets id, zone, and tag. The provider exposes this field as alias, so the submitted description is currently discarded. Steps to reproduce Set a VNet description in any shipped example. Run terraform plan. Inspect proxmox_virtual_environment_sdn_vnet.vnet and note that no alias is planned. Environment Terraform 1.13.4, bpg/proxmox 0.111.1, module v0.2.0-beta.1. Scope Map each.value.description to the provider's VNet alias field and add a mocked assertion that proves the value reaches the planned resource. Existing examples should continue to validate.

Area Documentation Relevant reference v0.2.0-beta.1 README quickstart https://github.com/hybridops-tech/terraform-proxmox-sdn/tree/v0.2.0-beta.1/examples/api-only-edge-routed https://developer.hashicorp.com/terraform/language/expressions/version-constraints#specify-a-prerelease-version Expected behaviour The API-only quickstart should select a module release that supports enable_host_orchestration. A copied example should validate before any provider operation is attempted. Observed behaviour The quickstart uses: version = "~> 0.1.6" enable_host_orchestration = false That constraint selects the stable 0.1.x line. The v0.1.6 module requires proxmox_host and does not define enable_host_orchestration. terraform validate returns: Error: Missing required argument The argument "proxmox_host" is required, but no definition was found. Error: Unsupported argument An argument named "enable_host_orchestration" is not expected here. The GitHub release text uses version = "= 0.2.0-beta.1". Terraf

Area Host-side scripts Problem The roadmap describes the SDN recovery helper as optional, but every deployment with host orchestration enabled installs the watcher and its systemd units. An operator cannot keep host L3, SNAT, or DHCP while choosing not to run the watcher. Proposed change Add an explicit input for the recovery watcher. Keep the current behaviour as the default so existing deployments do not change unexpectedly. Acceptance criteria The default still installs and enables the current recovery components. Disabling the option leaves host L3, SNAT, DHCP, and static routes available without installing the watcher. Changing the option from enabled to disabled removes only the files and units owned by this module. API-only mode remains unchanged. Tests and the input documentation cover both settings.