[PATCH storage v2 7/7] lvm plugin: schema: align description of 'tagged_only' with actual behavior

[Fiona Ebner <f.ebner@proxmox.com>]

The only thing that the 'tagged_only' property affects is the
list_images() method and this has been the case since the option was
introduced 10 years ago with commit 7a9dd11 ("add tagged_only option
to LVM storage"). There are no other checks against using such
volumes if their name adheres to the vm-ID-XYZ schema. For example,
they can be accessed via 'pvesm free' and assigned to a VM with
'qm set'. If such checks are added, that should be done as part of a
major release to avoid breaking any existing setup. Document the
actual behavior for now.

Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---

New in v2.

 src/PVE/Storage/LVMPlugin.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/PVE/Storage/LVMPlugin.pm b/src/PVE/Storage/LVMPlugin.pm
index b4cb0c5..ff8c5f4 100644
--- a/src/PVE/Storage/LVMPlugin.pm
+++ b/src/PVE/Storage/LVMPlugin.pm
@@ -440,7 +440,7 @@ sub properties {
             type => 'string',
         },
         tagged_only => {
-            description => "Only use logical volumes tagged with 'pve-vm-ID'.",
+            description => "Only list logical volumes tagged with 'pve-vm-ID'.",
             type => 'boolean',
         },
     };
-- 
2.47.3