Check gvmd data feed subdirectories #1362
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
The check if the gvmd feed data directory exists now also checks the version-specific subdirectories for configs, port lists and report formats in case only those are missing.
mattmundell
approved these changes
Nov 23, 2020
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:
The check if the gvmd feed data directory exists now also checks the
version-specific subdirectories for configs, port lists and report
formats in case only those are missing.
Why:
If the parent directory is created but the subdirectory is missing, gvmd would
still generate a large number of warning messages.
How did you test it:
Renaming one subdirectory of the 20.08 feed (e.g.
configstoconfigs~)at a time and then renaming it back to the original name,
waiting for the log messages to appear after each step.
Checklist: