starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Automated updates via "update" command #1663

New Issue
Closed
opened 2026-02-05 01:53:36 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 01:53:36 +03:00
Owner
Copy Link

Originally created by @YeloMelo95 on GitHub (Sep 23, 2025).

🌟 Briefly describe the feature

Add support for arguments / switches to the"update" command

📝 Detailed description

Allow the "update" command to be run fully silently via arguments / switches passed directly into the command, ie. update --silent. Currently the CHOICE variable dictates the start of the update script; if this could be passed when running the update script, the only other things to consider would be prompts from the update process (such as restarting services as asked by APT) and any potential individual application prompts.

💡 Why is this useful?

Allows users to create cronjobs or ansible scripts targeting specific LXCs for an application update where applicable. By adding supported arguments / switches, the update process would be made much more convenient.

Originally created by @YeloMelo95 on GitHub (Sep 23, 2025). ### 🌟 Briefly describe the feature Add support for arguments / switches to the"update" command ### 📝 Detailed description Allow the "update" command to be run fully silently via arguments / switches passed directly into the command, ie. update --silent. Currently the CHOICE variable dictates the start of the update script; if this could be passed when running the update script, the only other things to consider would be prompts from the update process (such as restarting services as asked by APT) and any potential individual application prompts. ### 💡 Why is this useful? Allows users to create cronjobs or ansible scripts targeting specific LXCs for an application update where applicable. By adding supported arguments / switches, the update process would be made much more convenient.
OVERLORD added the enhancement label 2026-02-05 01:53:36 +03:00
OVERLORD commented 2026-02-05 01:53:41 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 23, 2025):

Nope Not directly. If Breaking Scripts it Breaks. In next time a Big refactor of core are available, then some Users can use another Script (created before an snapshot)

@MickLesk commented on GitHub (Sep 23, 2025): Nope Not directly. If Breaking Scripts it Breaks. In next time a Big refactor of core are available, then some Users can use another Script (created before an snapshot)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1663
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?