full-auto deployment compatibility passing -variables

[ne0YT]

🌟 Briefly describe the feature

full-auto deployment compatibility passing -variables

📝 Detailed description

I'd love to get a oneliner or something when deploying a new vm which makes it possible to create this exact vm without any dialog for it.

💡 Why is this useful?

it makes deployments scriptable and faster, instead of waiting for dialog options just passing them would be nice sometimes.

[MickLesk]

Example? LXC's are full auto passed and more configurable. VM's not.

With the new Core (ProxmoxVED) there are no dialogues needed. f.e.

var_version=22.04 var_os="ubuntu" preset="mydefaults" var_vlan=100 var_ssh="yes" var_disk=25 var_ram=8192 bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/ct/upgopher.sh)" 

[ne0YT]

Example? LXC's are full auto passed and more configurable. VM's not.

With the new Core (ProxmoxVED) there are no dialogues needed. f.e.

var_version=22.04 var_os="ubuntu" preset="mydefaults" var_vlan=100 var_ssh="yes" var_disk=25 var_ram=8192 bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/ct/upgopher.sh)"

yeah, I'd love to have the feature for VMs, I'm not using LXC. it's easy to script cloud-init after but would be really nice to have the option to also create them scripted using all the scripts in the same way.

[MickLesk]

Then definitly not this year, maybe 2nd quarter of 2026. Unfortunately, developing VM scripts takes an enormous amount of time, is sometimes very vulnerable (since we have to support Proxmox 8.x to 9.x), and, to be honest, the VMs are massively overbuilt, unfortunately by tteck itself.

We started building a “vm-core.func” in DEV, but kept running into problems. The issue is currently off the table, as I am currently rebuilding the entire “LXC core” and want to have that finalized first.

If you don't mind, I would convert it into a discussion and include it in my roadmap, but as I said, I don't think I'll be able to do that before February/March. Unfortunately, none of the contributors really dare to tackle the VMs because, as mentioned above, they are very sensitive.

[ne0YT]

I see, thank you:)
I mean February/March sounds nice too!