[PATCH pve-cluster v5 2/7] datacenter config: add unique-next-id to schema

["Michael Köppl" <m.koeppl@proxmox.com>]

From: Severen Redwood <severen.redwood@sitehost.co.nz>

Add the `unique-next-id` property to the datacenter config schema to
track whether only unique (ie. neither currently nor previously in use)
VM/CT IDs should be suggested by the `/cluster/nextid` API endpoint.

Co-authored-by: Daniel Krambrock <krambrock@hrz.uni-marburg.de>
Signed-off-by: Severen Redwood <severen.redwood@sitehost.co.nz>
[MK: use datacenter in commit message instead of datacentre]
Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
---
 src/PVE/DataCenterConfig.pm | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/PVE/DataCenterConfig.pm b/src/PVE/DataCenterConfig.pm
index 004122e..54f9c10 100644
--- a/src/PVE/DataCenterConfig.pm
+++ b/src/PVE/DataCenterConfig.pm
@@ -415,6 +415,12 @@ my $datacenter_schema = {
             format => $next_id_format,
             description => "Control the range for the free VMID auto-selection pool.",
         },
+        'unique-next-id' => {
+            optional => 1,
+            type => 'boolean',
+            description =>
+                "Only suggest VMIDs that are neither currently in use nor have previously been used.",
+        },
         migration => {
             optional => 1,
             type => 'string',
-- 
2.47.3