As a user of the ATT&CK website, I want the CLI to be robust and catch edge cases when I'm specifying arguments. I want it to tell me if my arguments are invalid.
The current implementation of update-attack.py on the modularization branch builds without having to specify a build flag. However, the optional --modules flag can be used to specify a subset of modules to run. If the user runs python3 update-attack.py --modules without specifying any modules to run, it should tell them it requires at least one argument.
Probably the optimal way to do this is to simply specify the nargs for modules as + instead of *.
This should also be done for --test.
As a user of the ATT&CK website, I want the CLI to be robust and catch edge cases when I'm specifying arguments. I want it to tell me if my arguments are invalid.
The current implementation of update-attack.py on the modularization branch builds without having to specify a build flag. However, the optional
--modulesflag can be used to specify a subset of modules to run. If the user runspython3 update-attack.py --moduleswithout specifying any modules to run, it should tell them it requires at least one argument.Probably the optimal way to do this is to simply specify the nargs for modules as
+instead of*.This should also be done for
--test.