Remove NVD config options that are no longer relevant #190
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
Since we don't offer mirroring via feeds anymore, all related configs were removed from the UI. Similarly, because the last modified timestamp is not maintained in the database anymore, its respective UI element is removed as well. Signed-off-by: nscuro <[email protected]>
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.
Description
Removes NVD config options that are no longer relevant.
Since we don't offer mirroring via feeds anymore, all related configs were removed from the UI.
Similarly, because the last modified timestamp is not maintained in the database anymore, its respective UI element is removed as well.
Addressed Issue
N/A
Additional Details
This was reported via Slack: https://owasp.slack.com/archives/C06S1BY0JKZ/p1732176565916269
Checklist
This PR introduces new or alters existing behavior, and I have updated the documentation accordingly