[GH-ISSUE #72] Feature: Snap from tags #67

Closed
opened 2026-02-26 17:44:15 +03:00 by kerem · 7 comments
Owner

Originally created by @franklupo on GitHub (Dec 16, 2022).
Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/72

Originally assigned to: @franklupo on GitHub.

Added ability to snap for VM/CT on specific tags.
You could specify in the --vmid parameter the value @tags_<tag_name>.

https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_tags

Originally created by @franklupo on GitHub (Dec 16, 2022). Original GitHub issue: https://github.com/Corsinvest/cv4pve-autosnap/issues/72 Originally assigned to: @franklupo on GitHub. Added ability to snap for VM/CT on specific tags. You could specify in the --vmid parameter the value @tags_<tag_name>. https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_tags
kerem 2026-02-26 17:44:15 +03:00
Author
Owner

@turrini commented on GitHub (Jan 4, 2023):

Or when grouped as pools. I have in my scenario some pools, would be nice too!

<!-- gh-comment-id:1370960580 --> @turrini commented on GitHub (Jan 4, 2023): Or when grouped as pools. I have in my scenario some pools, would be nice too!
Author
Owner

@franklupo commented on GitHub (Jan 4, 2023):

Or when grouped as pools. I have in my scenario some pools, would be nice too!

For pool work use @pool-

<!-- gh-comment-id:1371036654 --> @franklupo commented on GitHub (Jan 4, 2023): > Or when grouped as pools. I have in my scenario some pools, would be nice too! For pool work use @pool-<poolname>
Author
Owner

@franklupo commented on GitHub (Jan 4, 2023):

--vmid The id or name VM/CT comma separated (eg. 100,101,102,TestDebian) -vmid or -name exclude (e.g. -200,-TestUbuntu) '@pool-???' for all VM/CT in specific pool (e.g. @pool-customer1), '@all-???' for all VM/CT in specific host (e.g. @all-pve1, @all-\$(hostname)), '@all' for all VM/CT in cluster

<!-- gh-comment-id:1371038905 --> @franklupo commented on GitHub (Jan 4, 2023): `--vmid The id or name VM/CT comma separated (eg. 100,101,102,TestDebian) -vmid or -name exclude (e.g. -200,-TestUbuntu) '@pool-???' for all VM/CT in specific pool (e.g. @pool-customer1), '@all-???' for all VM/CT in specific host (e.g. @all-pve1, @all-\$(hostname)), '@all' for all VM/CT in cluster`
Author
Owner

@turrini commented on GitHub (Jan 4, 2023):

Did you already implemented the @tags_ feature? It didn't work for me in the latest version:

ACTION Snap
PVE Version:      7.3-3
VMs:              @tags_test
Label:            test
Keep:             1
State:            False
Only running:     True
Timeout:          30 sec.
Timestamp format: yyMMddHHmmss
Max % Storage :   95%
----- VMs with '@tags_test' NOT FOUND -----
----- POSSIBLE PROBLEM PERMISSION 'VM.Audit' -----
----- POSSIBLE PROBLEM PERMISSION 'Datastore.Audit' -----
<!-- gh-comment-id:1371337078 --> @turrini commented on GitHub (Jan 4, 2023): Did you already implemented the @tags_ feature? It didn't work for me in the latest version: ``` ACTION Snap PVE Version: 7.3-3 VMs: @tags_test Label: test Keep: 1 State: False Only running: True Timeout: 30 sec. Timestamp format: yyMMddHHmmss Max % Storage : 95% ----- VMs with '@tags_test' NOT FOUND ----- ----- POSSIBLE PROBLEM PERMISSION 'VM.Audit' ----- ----- POSSIBLE PROBLEM PERMISSION 'Datastore.Audit' ----- ```
Author
Owner

@franklupo commented on GitHub (Jan 5, 2023):

@tag- not implemnted
@pool- implemented

<!-- gh-comment-id:1371912255 --> @franklupo commented on GitHub (Jan 5, 2023): @tag- not implemnted @pool- implemented
Author
Owner

@PMExtra commented on GitHub (May 16, 2023):

Can I use - to except a tag or pool? Such as --vmid=@all,-@tag-foo,-@tag-bar

<!-- gh-comment-id:1549069509 --> @PMExtra commented on GitHub (May 16, 2023): Can I use `-` to except a tag or pool? Such as `--vmid=@all,-@tag-foo,-@tag-bar`
Author
Owner

@franklupo commented on GitHub (May 16, 2023):

The - work only for VmId or VmName

<!-- gh-comment-id:1549072314 --> @franklupo commented on GitHub (May 16, 2023): The ```-``` work only for VmId or VmName
Sign in to join this conversation.
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/cv4pve-autosnap#67
No description provided.