Option for the Cloud-Init "Upgrade Packages" feature

[michaelmumenthaler]

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Description

Proxmox VE 8 introduced a cloud-init option called ciupgrade that controls wheter a machine should upgrade it's packages on boot. Currently this option cannot be controlled with Packer.

Use Case(s)

As the default value of this option is set to truethis means that when using the Proxmox Cloud-Init (i.e. with the ipconfig Packer option or other) the Cloud-Init drive gets created which then in return, by default, upgrades the packages on the first boot. This can lead to unexpected behaviour when running different workflows after the VM creation (apt in locked state etc.).

Potential configuration

A boolean flag called upgrade_packages with the default set to true, to match the API default, that can be overriden in the builder template.

Potential References

Documentation:
https://pve.proxmox.com/wiki/Cloud-Init_Support

Feature Introduction:
https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_8.0