[pve-devel] GET /access/users/{userid} has parameter 'tokens' with 'additionalProperties' containing object definition

Fabian Grünbichler f.gruenbichler at proxmox.com
Tue Apr 2 09:27:57 CEST 2024


> Jona Draaijer via pve-devel <pve-devel at lists.proxmox.com> hat am 01.04.2024 22:00 CEST geschrieben:
> Hi,
> 
> As per the title, that endpoint has an additionalProperties value that is
> not a bool, but rather an object definition. (It's defined in
> pve-access-control/src/PVE/API2/User.pm).
> 
> As far as I can tell, all other 'additionalProperties' are bools. Does
> anyone know why this specific one is different, or if this difference is
> intentional?

I think this was just an accident.

> From the looks of it it seems like it's used as a "we need this standard
> option, but also have to make it optional". I am still quite new to perl,
> so I don't know if there is a way to do what was intended.

My guess is the intent was to have

	    tokens => get_standard_option('token-info', { optional => 1 }),

instead, @Wolfgang?




More information about the pve-devel mailing list