[pve-devel] applied: [PATCH common v2 1/1] JSONSchema: add pve-tag format

[Thomas Lamprecht]

On 10/3/19 1:50 PM, Dominik Csapak wrote:
> this will be used for vm/ct tag-lists, so that (config) management systems
> or similar add additional information that does not reside in the
> description
> 
> putting it here, since we want to eventually have it also for
> nodes,storages,etc.
> 
> Signed-off-by: Dominik Csapak <d.csapak at proxmox.com>
> ---
>  src/PVE/JSONSchema.pm | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm
> index db38d44..8332a19 100644
> --- a/src/PVE/JSONSchema.pm
> +++ b/src/PVE/JSONSchema.pm
> @@ -499,6 +499,18 @@ register_standard_option('bwlimit', {
>      format => $bwlimit_format,
>  });
>  
> +# used for pve-tag-list in e.g., guest configs
> +register_format('pve-tag', \&pve_verify_tag);
> +sub pve_verify_tag {
> +    my ($value, $noerr) = @_;
> +
> +    return $value if $value =~ m/^[a-z0-9_][a-z0-9_\-\+\.]*$/i;
> +
> +    return undef if $noerr;
> +
> +    die "invalid characters in tag\n";
> +}
> +
>  sub pve_parse_startup_order {
>      my ($value) = @_;
>  
> 

applied, albeit it would be great if I remembered this yesterday,
then we would had it in the package and version-dependency bump
included "for free"..