Pavel Boldyrev c20d79dfbe fix(vm): cpu.architecture showed as new attribute at re-apply after creation (#1524) ... Fix for another use case of mismanaged default value. This one was a bit trickier to spot as it triggered only when provider is authenticated using root@pam, as architecture change is allowed only for root. Removing default value altogether, as the PVE API default for this attribute is an empty string. VM2 resource will have no such issue, related: #1310, #1311 Signed-off-by: Pavel Boldyrev <627562+bpg@users.noreply.github.com>		2024-09-08 19:25:40 -04:00
..
disk	chore(vm): refactor storage devices handling from/to API (#1394)	2024-06-17 01:23:48 +00:00
network	chore: remove unused code (#1236)	2024-04-24 20:52:41 -04:00
validators_test.go	chore(deps): update module github.com/golangci/golangci-lint (v1.56.2 → v1.57.1) in /tools (#1149)	2024-03-25 21:06:06 -04:00
validators.go	fix(vm): cpu.architecture showed as new attribute at re-apply after creation (#1524)	2024-09-08 19:25:40 -04:00
vm_test.go	feat(vm): add support for numa architecture attribute (#1156) (#1175)	2024-04-06 16:30:13 -04:00
vm.go	fix(vm): cpu.architecture showed as new attribute at re-apply after creation (#1524)	2024-09-08 19:25:40 -04:00