7 Commits
Author SHA1 Message Date
dualfroz fd3e2a1b0f Describe this repository 2026-10-22 21:06:10 +02:00
dualfroz 41d137eef8 ldap: query groups: also return the description
The description is a common attribute of groups, for example of
groupOfNames in OpenLDAP, of groups in Active Directory and of user
groups in FreeIPA. Query it together with the members and return it,
so that the realm sync can use it as the comment of a synced group.

Signed-off-by: Michal Fox <me@dualfroz.com>
2026-10-03 02:10:21 +02:00
dualfroz 1f627a1a14 Notes added by 'git notes copy' 2026-10-02 16:42:24 +02:00
dualfroz 7f6d5660ee Notes added by 'git notes add' 2026-10-02 16:42:14 +02:00
dualfroz 9373a6089b fix #5607: schema: say what a valid configuration ID looks like
The 'pve-configid' format is used for many IDs, for example the names
of resource mappings, but an invalid ID only got rejected with:

  invalid configuration ID 'gpu@node1'

which does not tell what is wrong with it, so users had to guess or
look up the regex in the code.

Explain the rules in the error message: an ID must start with a letter,
be at least two characters long and only contain letters, digits, '-'
and '_'. These are the same rules the tooltip of the 'ConfigId'
validation in the web UI lists. Add a test for the message.

Signed-off-by: Michal Fox <me@dualfroz.com>
2026-10-02 16:42:24 +02:00
dualfroz dccc97a0ea cli formatter: decode the output of the yaml renderer
YAML::XS::Dump returns UTF-8 encoded octets, but the value returned by
a renderer gets encoded when the text output is printed, like any other
value. So for properties using the 'yaml' renderer, for example the
account details shown by 'pvenode acme account info', any non-ASCII
character got encoded twice and ended up mangled.

Decode the output of YAML::XS::Dump in the renderer, so it returns a
character string like all other renderers, and add a test for it.

Fixes: 99d0252 ("properly encode YAML via YAML::XS")
Signed-off-by: Michal Fox <me@dualfroz.com>
2026-10-02 16:25:55 +02:00
dualfroz 2ad66a1cb4 fix #6305: cli formatter: avoid encoding YAML output twice
YAML::XS::Dump already returns UTF-8 encoded octets, but its output
still got encoded once more. This is a leftover from when the YAML
output was generated by CPAN::Meta::YAML, which returns a character
string.

As a result, all non-ASCII characters got mangled with the 'yaml'
output format, for example a cluster description with a German umlaut
when running:

  pvesh get /cluster/options --output-format yaml

Print the output of YAML::XS::Dump as is, like it is already done for
the 'json' output format, and add a test for the encoding of both.

Fixes: 99d0252 ("properly encode YAML via YAML::XS")
Signed-off-by: Michal Fox <me@dualfroz.com>
2026-10-02 16:05:27 +02:00