Option to pause runner between atomics & invoke-commandfix #161
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 PR introduces a "-PauseBetweenAtomics" option to be used with "Invoke-AtomicRunner -ListOfAtomics" where you specify the number of seconds to pause between executions. If you specify zero, you will be prompted to press any key to run the next atomic.
This PR has an internal improvement to pass arguments as an array of strings instead of a single string which avoids problems of quoting double quotes inside of double quotes.
Fixes an issue introduced with the "-anyOS" PR where atomics that don't apply to the given OS are being invoked. For example, invoking T1016 on linux would attempt to run all of the atomics even though only one applies to linux.
Also, not redirecting stdin during atomic execution because the redirected input wasn't being used anywhere and was breaking some atomics (such as those that use ADFind)
Testing on Windows and Linux