VULCAN-581: Enhance Import from Spreadsheet workflow #582
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
…sfaction when file contains rules satistied by many others Signed-off-by: Vanessa Fotso <vfotso@mitre.org>
|
So as long as "Satisfied By: " is in the "Vendor Comments" column with a comma separated list it will parse that if I am reading it correctly? |
it currently handles comma or space separated, or the edge case where multiple "Satisfied By: " statement and duplicated STIG ID. The following will parse correctly:
|
rlakey
approved these changes
May 18, 2023
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.
Fix the import from spreadsheet workflow to properly create rule satisfaction when file contains rules satisfied by many others
Fix #581