one way of addressing #827, making dangerWillRobinson a number that m… #831
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.
This is a first shot at #827... I think getting a count that matches what is being done is a good thing. I don't think y/n prompts help, because the analyst will then ask for a -y option, and in any event if the analyst didn't notice the problem immediately, they could answer yes anyways. having to supply a number that matches the number of configs affected is almost like a 2nd factor. Correlation is a good thing.
So this patch does that, but more is needed prior to merging this: