Thanks Benson Qiu for the patch
There are some more high level thoughts after i was checking various CLI and other PBImpl code.
- We are not sharing per-label Queue resource usage
- We are not sharing per-label Queue configurations (capacity etc).
More or less I am thinking in line of thoughts shared by Bibin A Chundatt earlier.
Since many informations related to configuration is already exposed by QueueInfo, Properties may not a become a better logical grouping unless we move all existing config items to new subclass.
I still kind of feel above statement makes sense. However this is similar to a problem addressed in QueueCapacities etc. And in long run, this may be helpful.
My proposal is something like below.
In QueueInfo, lets have an api called setQueueConfigurations. A new api record could be added named QueueConfigurations and it can have below sub items
If we have a map in QueueInfo per-label, then QueueConfigurations could be mapped against its accessable-labels.
I would like to have discussion on this approach and we can make it more generic. Benson Qiu, Bibin A Chundatt and Rohith Sharma K S , thoughts?