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 12 Packages Projects Releases 10 Wiki Activity

Config file: Add Tags from installer script #980

New Issue
Closed
opened 2026-02-04 22:23:46 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 22:23:46 +03:00
Owner
Copy Link

Originally created by @Gregor-zbjk on GitHub (May 19, 2025).

Originally assigned to: @michelroegl-brunner on GitHub.

🌟 Briefly describe the feature

Add tags from installer script to Config file (.settings)

📝 Detailed description

I noticed that when I run the installer with option "Config file" only the tag "community-scripts" is added instead of "community-scripts" & "cloud" (e.g. Nextcloudpi)

I would like to see an option to transfer the tags from the installation script to the config file
e.g.

TAGS="dev,DEFAULT”

DEFAULT=Default Tags of the installer script (e.g. Nextcloudpi: “community-scripts” & “cloud”)

This would be following Tags as result:
dev, community-scripts, cloud

💡 Why is this useful?

This would allow the original installer script tags to be retained and new ones, e.g. “dev”, to be added... thus allowing better differentiation in Proxmox

Originally created by @Gregor-zbjk on GitHub (May 19, 2025). Originally assigned to: @michelroegl-brunner on GitHub. ### 🌟 Briefly describe the feature Add tags from installer script to Config file (.settings) ### 📝 Detailed description I noticed that when I run the installer with option "Config file" only the tag "community-scripts" is added instead of "community-scripts" & "cloud" (e.g. Nextcloudpi) I would like to see an option to transfer the tags from the installation script to the config file e.g. ``` TAGS="dev,DEFAULT” ``` DEFAULT=Default Tags of the installer script (e.g. Nextcloudpi: “community-scripts” & “cloud”) This would be following Tags as result: `dev, community-scripts, cloud` ### 💡 Why is this useful? This would allow the original installer script tags to be retained and new ones, e.g. “dev”, to be added... thus allowing better differentiation in Proxmox
OVERLORD added the enhancement label 2026-02-04 22:23:46 +03:00
OVERLORD commented 2026-02-04 22:23:54 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (May 20, 2025):

Available when #4601 merges.

@michelroegl-brunner commented on GitHub (May 20, 2025): Available when #4601 merges.
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#980
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?