[UI BUG] Resource limits for type 15 (ObjectStorage) and 16 (GPU) do not sync/display correctly in Web UI

[ms30063600]

problem

Hi,

I found that more resource limits are shown in the application then is actually mentioned in https://cloudstack.apache.org/api/apidocs-4.22/apis/updateResourceLimit.html. So I asked my AI assistent. He/she came up with additional resource type ids 12, 13, 14, 15 and 16. This seemed to work fine, except that it does not work for resource type id 15 and 16, based on that my newly imposed limits were not shown in the application. But then I tried the listResourceLimit api endpoint, and the values for both resource types (15, 16) were shown correctly. So this is about the presentation of this data in the UI.
The following problem description is created by the AI assistent. But I hope the picture is clear already.

Kind regards, Maurice.

There is a synchronization and presentation discrepancy between the CloudStack backend API and the Vue.js Web UI regarding resource limits for newer resource types (specifically resourcetype 15 for ObjectStorage and 16 for GPU).
While the backend correctly processes these values via updateResourceLimit and returns them accurately via listResourceLimits, the Web UI limits configuration panel fails to parse, map, or visually reflect these values accurately.
Steps to Reproduce

1. Update the GPU resource limit for a domain/account via the API using: updateResourceLimit resourcetype=16 max=2 ...
2. Verify the backend successfully registered the limit by calling the listResourceLimits API endpoint (the value shows up correctly).
3. Log into the CloudStack Web UI as a Root Admin and navigate to the limits configuration for that same domain/account.
4. Observe that the values for "Max. Object Storage (GiB)" and/or "Max. GPUs" do not reflect the values set via the API, or fail to display the updated state.
   Expected Behavior
   The Web UI's frontend mapping array should dynamically parse or correctly hardcode mappings for sequential backend resource IDs beyond 11 (including 12 through 16) so that administrative changes made via the API align 1:1 with the graphical dashboard views.
   Actual Behavior
   The backend successfully enforces and reports the limits via API, but the Web UI component fails to map the frontend input fields to resourcetype 15 and 16 data payloads.

versions

The versions of ACS, hypervisors, storage, network etc..

The steps to reproduce the bug

...

What to do about it?

No response

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template!

[DaanHoogland]

@ms30063600 / Maurice, the UI is behind the API in principle. Some people feel you should implement immediately in the UI what you implement in the API. I could agree less. Or actually couldn’t oppose more. The API is prone to PoC and shouldn’t be sold as clickable bait in my not so humble opinion. However, and more specific to you example, feel free to implement UI changes that reflect the current state of this particular API if you feel you need it. Object Storage and GPU are latecomers though not entirely new any more.

@abh1sar @vishesh92 , maybe you guys have more inviting ideas on this?