| When trying to run an adhoc script I discovered that the Bolt CLI seems to silently consume and ignore arguments passed intended to be used with a "script run". These should be valid arguments to pass. In this case, I was trying to pass a LDAP DN, which had a number of equal signs. You can see the CLI option vanish when running bolt in debug mode: bolt script run myscript.sh string1 a=b string2 -n testnode ... Starting: script myscript.sh on testnode
Running script myscript.sh with '["string1", "string2"]' on ["testnode"] ... Displaying the contents of ARGV confirms the argument with the equal sign was never received by the script. Invoking the run_script function from within a Bolt plan does not suffer from the same issue, leading me to believe it is a problem with the CLI parsing somewhere. Thanks! |
