Ansible is open-source software that sets up and configures your servers for you. You write the steps once in a plain text file, and Ansible runs them the same way every time, across as many machines as you like.
These posts cover using it day to day: inventories, playbooks and roles, variables and templates, keeping tasks safe to re-run, and tying it in with tools like NetBox.
Reading a vSphere estate with the dynamic inventory, mirroring its VLANs into Proxmox SDN, and rebuilding every VM as a diskless shell before a single disk moves. Why every VMware info module hides the one field the migration needs, why vlan_id is three different types, and why one NFS export mounted twice turns the cutover into a local read.
The community.proxmox collection is an API client, not a configuration agent, and that changes the shape of every playbook that uses it. Where the tasks actually run, why proxmox_kvm declines to converge rather than updating, why proxmox_disk and proxmox_nic are where disk and NIC changes belong, and the undocumented return value you will end up needing.