As far as I can tell Aruba passes the correct command around and runs it.
So I suspect this might not be trivial to track down the cause of:
Using Aruba's step definition (with 'lucid64-base' or lucid64-base):
Given I successfully run `vagrant basebox export 'lucid64-base' 2>&1 |tee lucid64-base-export.log`
RuntimeError: Exit status was 1. Output:
"export" was called incorrectly. Call as "vagrant basebox export [NAME]".
I suspect that the way aruba passes args to the command causes this.
I would test print with ARGV in the vagrant binary to see if these get passed as different args, or end up all in ARGV
Closing this due to age, no response, and not being part of the core veewee feature set.