Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(cluster): Implement "next-id" and "notify" PVE API cluster options
This commit implements the `next-id` and `notify` PVE API cluster options. The `next-id` attribute allows to control the range for the next free VM ID. It is implemented as object and can be used in the `proxmox_virtual_environment_cluster_options` resource and can be used like this: ```terraform resource "proxmox_virtual_environment_cluster_options" "options" { next_id = { lower = 200 upper = 299 } } ``` Note that the minimum and maximum values are unfortunately not documented in the PVE API explorer but can be found in the web UI where the form fields have validations! The `notify` PVE API attribute is also an object that has all the PVE API fields: ```terraform resource "proxmox_virtual_environment_cluster_options" "options" { notify = { ha_fencing_mode = "never" ha_fencing_target = "default-matcher" package_updates = "always" package_updates_target = "default-matcher" package_replication = "always" package_replication_target = "default-matcher" } } ```terraform Note that the "fencing" attribute names have been adjusted to better reflect their meaning since they are scoped to the Proxmox VE HA fencing feature [1]. All attributes with the `_target` suffix are names for the Proxmox VE notifications matchers [2]. [1]: https://pve.proxmox.com/wiki/Fencing [2]: https://pve.proxmox.com/pve-docs/chapter-notifications.html#notification_matchers Signed-off-by: Sven Greb <[email protected]>
- Loading branch information