Added propagating verbose to subcommands support #72
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue: #61
The following PR Added propagating verbose to subcommands support
Areas of discussion
In the Canasta-CLI, internal commands can propagate verbose to their internal subcommands, but can't propagate verbose to external subcommands called by exec.Command().
To get more info when executing external subcommands especially docker-compose, I passed the verbose flag to the external subcommands from their parent commands.
Changes made
Test
Only docker-compose has the –-verbose option among these external commands, so the following show the commands successfully propagate verbose to docker-compose subcommands.
This is my first time contributing to the community. Any feedback or suggestions are greatly appreciated.