fix(server): pf-4402 allow custom resource load limits - #331
Merged
Merged
Conversation
Merged
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 is it?
Notes
The bad, this indirectly affects consumers by limiting data availability, notably the API crawl. And the good, despite this strict-cap/bug, consumers are not, currently, adversely affected since the information was never there to begin with. Consumers have an added gain with estimates around 900+/- API records, see fix(collection): pf-4402 increase pf api crawler limits #325
the limiter is in place to reign in out-of-control agent interactions, however it was blanketing all docs calls going through the central docs function.
allows customizing limiting, throttling for general loading of documentation
Updates issue/story
related to pf-4402