Closed
Description
In many of Laravel's commands like the migration ones, the --no-interaction and --no-ansi flags are not forwarded when subsequent commands are called with ->call(). We should make sure all of that information is forwarded, otherwise one can run migrate with no interaction, then find the seed sub-command asks for input, or starts using colours when we have specified we don't want them.
Why does this matter? This is breaking stuff like automated setup of Laravel, where we need no interaction, say for building a docker container. // @jbrooksuk (RE Cachet Docker)