fix: Configure nvd.api.delay default #6112
Merged
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
… in case of actual misconfiguration to WARN level
aikebah
changed the title
aikebah
changed the title
|
The IT will fail. I'm working on a work around for the release testing. |
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.
Configure nvd.api.delay to take the coded defaults and raise log in case of actual misconfiguration to WARN level
Fixes Issue #6111
Description of Change
Add a default for nvd.api.key with value 0 to use the coded API-key present/not-present defaults and raise the log-level in case of Long parsing issues to WARN level as there was an invalid user-configured api delay
Have test cases been added to cover the new functionality?
no