All, I have a query with respect to this defect. With a build off the master it looks like the updateResourceCount api is returning the count of resources a user can use or create and that appears to be the documented behaviour for this api. Furthermore it appears that the UI is correctly displaying that.
With respect to issue raised in the defect the expected behaviour is that instead of the count of resources that can be created or used it should display the actual usage count. Could someone please clarify whats the correct expected behaviour with respect to the updateResourceCount api and if this a valid bug? Thanks Saurav