action_trigger_runner.pl runs with invalid arguments

[Josh Stompro]

EG 2.10.6

I've messed up numerous times when running action_trigger_runner.pl by entering an argument slightly wrong. The way it is currently configured it just ignores unknown arguments and tries to run with what is left. This can cause major problems if you do something like say --custom-filter=blah instead of the correct --custom-filters=blah. The difference between creating 800 events vs 38000 events in my experience.

It is simple to tell getopt to die if it encounters an argument that it doesn't know of. Would anyone support changing it's behavior so it exits or displays the help and exits when that happens? The consequences of a mistyped argument can be big enough that I think it would be worth it.

One downside would be that anyone with a currently harmless typo would have their events stop.

Josh