custom commands broken in dev console

[jalper]

Bug

Current Behavior

Seeing two issues with custom commands in the dev console:

First, when you first enter the dev console, trying to run a custom command results in the following error:

Could not find command. Try typing help to see the available commands.

If you run something else built-in like help or deploy and then try the custom command, it will now work.

The second issue, however, is that some custom commands fail like this:

Missing cli argument in custom command wrapper. This is a bug. Please report it!

Both times I've seen this were on commands that use $concat: ${args.$rest} to allow args to be supplied to the custom command, but should work without any args.

Your environment

• OS: macOS
  % garden version 0.13.2

[shumailxyz]

The 2nd issue is that custom garden commands currently do not work at all in dev mode and result in that error. Tracking 2nd issue separately with #4668