Policy: Identify path to support offset/limit pagination for resource LIST rpc's #55
Labels
comp:policy
Policy Configuration ( attributes, subject mappings, resource mappings, kas registry)
enhancement
New feature or request
scaling
Issues that may cause difficulties as usage or the size of a deployed system increases
Right now, a LIST call for an Attribute/Namespace/SubjectMapping/etc will return every value found, but we need to support limit and offset/pagination for the simple "get all" queries.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: