starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-27 10:16:03 +03:00

[GH-ISSUE #9306] full-auto deployment compatibility passing -variables #2042

New issue

Closed

opened 2026-02-26 12:51:07 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 12:51:07 +03:00

Owner

Originally created by @ne0YT on GitHub (Nov 20, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9306

🌟 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.

Originally created by @ne0YT on GitHub (Nov 20, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9306 ### 🌟 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.

kerem

2026-02-26 12:51:07 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 12:51:07 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 20, 2025):

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)"

@MickLesk commented on GitHub (Nov 20, 2025): 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. ```bash 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)" ```

kerem commented

2026-02-26 12:51:07 +03:00

Author

Owner

@ne0YT commented on GitHub (Nov 20, 2025):

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.

@ne0YT commented on GitHub (Nov 20, 2025): > 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.

kerem commented

2026-02-26 12:51:07 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 20, 2025):

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.

@MickLesk commented on GitHub (Nov 20, 2025): 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.

kerem commented

2026-02-26 12:51:07 +03:00

Author

Owner

@ne0YT commented on GitHub (Nov 20, 2025):

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

@ne0YT commented on GitHub (Nov 20, 2025): I see, thank you:) I mean February/March sounds nice too!

kerem referenced this issue

2026-02-26 13:33:43 +03:00

[PR #2042] [MERGED] Bump vitest from 2.1.6 to 2.1.9 in /frontend #3500

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2042

No description provided.

Rows
Columns