go-proxmox VS cv4pve-autosnap

The best way to handle this (which is really terrible, honestly, but it works) is to make configdrive2 ISOs locally, and upload those using the API. That is, don't give Proxmox a cloud-init snippet, but rather a fully-built cloud-init ISO. This is basically bypassing/reimplementing Proxmox's cloud-init features yourself, which is terrible. But it works really well.

There's a pretty neat Proxmox API library written in Go that can do this all for you: https://github.com/luthermonson/go-proxmox

There's a Terraform plugin planned, as well. Not sure what the status on it is, currently.

I also am slowly working on my own Proxmox CLI, consuming the go-proxmox library: https://github.com/perchnet/gomox

But unfortunately I don't have much software engineering experience, so it's a very slow process... :)

From my research, I can see two options: - Proxmox specific cv4pve-autosnap - generic zfs-auto-snapshot, available in repos

You can use https://github.com/Corsinvest/cv4pve-autosnap to make automated snapshots of guests in proxmox.

Also, for being able to quickly revert mishaps with your vms, and lxc containers i use https://github.com/Corsinvest/cv4pve-autosnap to make hourly snapshots of all vms and lxc containers (taking snapshots suspends disk io from the vm's point of view. Some software, especially game servers, can't deal with this).

Since Proxmox natively supports ZFS, you could that to make your snapshots. You can do automatic snapshots with zfs-auto-snapshot or for VMs with cv4pve-autosnap.

to achieve this fabulous glory of software-engineering i utilized this projects: cv4pve-autosnap and Zamba Fileserver on LXC

If you want automatic snapshots that appear in the Proxmox GUI and can be rolled back from there, too, you could check out https://github.com/Corsinvest/cv4pve-autosnap. I recently set it up and it works nicely. It uses the Proxmox API to trigger snapshots. Corsinvest is the company behind this tool. They are part of the Proxmox partner program.