Am 03/05/2023 um 13:26 schrieb Dominik Csapak: > just a short comment since this series overlaps a bit with my > cluster resource mapping series (i plan on sending a v4 soon). > > i'd prefer to have the configuration endpoints for mapping bundled in a > subdirectory > so instead of /nodes/<node>/dirs/ i'd put it in /nodes/<node>/mapping/dirs/ > (or /nodes/<node>/map/dirs ) > > @thomas, @fabian, any other input on that? >
huh? aren't mappings per definition cluster wide i.e. /cluster/resource-map/<mapping-id> than then allows to add/update the mapping of a resource on a specific node? A node specific path makes no sense to me, at max it would if adding/removing a mapping is completely decoupled from adding/removing/updaing entries to it – but that seems convoluted from an usage POV and easy to get out of sync with the actual mapping list. _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
