Hi all,
Is targetcli-fb still the only user of configshell-fb? Other users would hopefully be on this list, right? Well, I sure hope so...
One long-standing issue with targetcli is that when giving it single commands from the command line, it doesn't return a nonzero error code if there's an error of certain types -- it prints a message, but a success error code. This makes it hard for targetcli to be scripted. Not that I think scripting targetcli is a great way to do things, but people seem to be doing it a lot.
The fix for this is to change the way configshell's command loop works, so that critical ExecutionError exceptions aren't swallowed by configshell, but propagate to the caller (in targetcli's case, "scripts/targetcli"). The caller then has the option to print the error and continue (likely what you want to do if in interactive mode) or exit with an error (what we want to do for cmdline mode).
So, before I go ahead, any objections, or discussion? Speak up, or I'm going ahead early next week :)
Regards -- Andy