Fix: Avoid aborting SCAP update on failed CVE entries #2159
Conversation
This file contains 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
Conventional Commits Report
🚀 Conventional commits found. |
jhelmold
approved these changes
Mar 25, 2024
On failed CVE entry, a warning is logged and the entry is skipped instead of aborting the whole SCAP update.
a-h-abdelsalam
force-pushed
the
fix-aborting-scap-update-on-cve-entry
branch
from
8a61407
to
fc2d217
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Avoid aborting entire SCAP update on failed CVE entries and instead skip the entry, log a warning and continue with next entries.
If any of the following sub-elemens are missing, the CVE entry will be skipped:
Why
Avoid aborting the entire SCAP update on problematic CVE entries such as rejected CVEs.
References
GEA-512