Feature/command delay jitter#244
Merged
whotwagner merged 6 commits intoJun 11, 2026
Merged
Conversation
whotwagner
approved these changes
Jun 11, 2026
This file contains hidden or 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
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.
Task
#240
Description
schemas/config.py: Added three fields to CommandConfig with safe defaults so all existing playbooks are unaffected:
attackmate.py: Refactored the delay logic in _run_commands to compute per-command delay inside the loop. When jitter is off the behavior is identical to before. When on, it computes delay per command. The log message is now per-command (showing the actual delay used)
added unit tests to test/units/test_commanddelay.py
How Has This Been Tested?
new tests in
test/units/test_commanddelay.py
manual testing:
playbook:
config:
output:

config (testing min 0)
config (testing jitter false)
Checklist