Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses the following issues related to the Usage UI:
null
values to users without access to thelistUsageServerMetrics
API (Fixes Usage server metrics section shown to users without access to the API #9992);removeRawUsageRecords
API (Fixes Purge usage records action shown to users without access toremoveRawUsageRecords
#9995);generateUsageRecords
API (Fixes Generate usage records action shown to users without access togenerateUsageRecords
#9994);listUsageTypes
API. Since theusageid
parameter of thelistUsageRecords
API can only be used alongside thetype
parameter, both form fields are now hidden when the caller does not have access to thelistUsageTypes
API.Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
listUsageServerMetrics
,removeRawUsageRecords
,generateUsageRecords
andlistUsageTypes
APIsHow Has This Been Tested?
listUsageServerMetrics
,removeRawUsageRecords
,generateUsageRecords
andlistUsageTypes
APIs were not able to interact with them through the UI.