Re: [pve-devel] [PATCH manager 1/3] api: ceph: add endpoint to fetch config keys

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

Am 08/03/2023 um 13:14 schrieb Dominik Csapak:
> high level:
> 
> as you mentioned the path 'configkey' is not really optimal
> 
> i recently mentioned off-list that we could clean this up on
> the next breaking major release with a breaking api change:
> 
> have a 'config' dir and a
> 'file'
> 'db'
> and 'key'( or 'value') api endpoint inside
> that represents the different things
> 
> for now a possible change could be to do it in 'config'
> but with a new parameter, though that's also not ideal
> 
> any further ideas/suggestions @Thomas?


We could add the full

cfg/
   raw
   db
   value

now already, re-mount the 'cfg/raw' one on the current 'config' (or just keep
the code duplicated, not much gain if we remove it anyway) one and then drop that
old 'config' one in PVE 8.0; slightly hacky but IMO not that much.

Might want to check what other uses of config, cfg, conf, configuration there are
in API path's though, as ideally we keep the total unique count of them the same ;-)