fix: Skip unused FoD vulnerability filters for large-tenant performance - #1103
Merged
rsenden merged 7 commits intoSep 22, 2026
Merged
Conversation
jmadhur87
force-pushed
the
mjain6/fixFoDPerformanceIssue
branch
from
September 22, 2026 10:24
f0e57d9 to
b8fc8fc
Compare
jmadhur87
marked this pull request as ready for review
September 22, 2026 10:25
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
2 participants
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.
Add
excludeFilters=trueto FoD vulnerability endpoint calls.Changes
FoDIssueGetCommand,FoDIssueListCommand, andFoDIssueHelper.excludeFilters: trueto the vulnerabilities list request in the 10 bundled FoD report actions (aws, bitbucket, github-pr-comment, github, gitlab codequality/dast/debricked/sast, sarif, sonarqube).