docs(iot): BAN-31435 vulnerability/list groupby=vulnerability pagination + includeDeviceIdList - #1401
Open
despera3821 wants to merge 4 commits into
Open
Conversation
…ports pagination + includeDeviceIdList - pagelength/offset now apply to groupby=vulnerability (was device-only) - add includeDeviceIdList=no (device counts instead of full id lists) to bound large responses
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
BAN-31435 follow-up docs: the public
GET /vulnerability/list?groupby=vulnerabilityendpoint now supports pagination and a counts-only option (backend MRs !7415 + !7423).Changes (openapi-specs/iot/api/public/vulnerabilityList.yaml)
groupby=vulnerabilitytoo (the docs previously said device-only). Note to use a smaller page length for large tenants.no, each vulnerability returns the device count instead of the full device-ID list, producing a much smaller response — use it (or a smaller pagelength) to keep large-tenant responses under the size limit.Publish once the backend fix is deployed. Ticket: BAN-31435.