Have --verbose also pass verbose to subcommands #61
Labels
good first issue
Good for newcomers
Comments
|
@bawolff @jeffw16 I found that internal commands can propagate verbose to their internal subcommands, but can't propagate verbose to external subcommands called by exec. So what I need to do is to address the problem with external commands, especially docker-compose? |
|
@chl178 Assigned to you. |
chl178
added a commit
to chl178/Canasta-CLI
that referenced
this issue
Mar 15, 2023
chl178
added a commit
to chl178/Canasta-CLI
that referenced
this issue
Mar 15, 2023
chl178
added a commit
to chl178/Canasta-CLI
that referenced
this issue
Mar 15, 2023
This was referenced Mar 15, 2023
yaronkoren
pushed a commit
that referenced
this issue
Nov 3, 2023
* Add propagating verbose to external subcommands(#61) * Add propagating verbose to external subcommands(#61) * Add propagating verbose to external subcommands(#61) * enhanced create and add for wiki farm * added add and remove wiki in the Canasta container feature * updated farmsettings.go * cleaned the code * structure 0.1 * structure 0.2 * midterm version * Add documentation * Add documentation * test version * Update with HTTPS * Canasta-CLI 2.0 adding wiki farm support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you specify --verbose, you still don't get all that much info. In particular the
docker-compose up -dstep can take a rather long time where it is unclear what it is doing.I would suggest that if the user specified --verbose (alternatively some tools use the practise where you do something like -vv to get extra verbosity), it would pass verbose options to subcommands, especially docker-compose.
The text was updated successfully, but these errors were encountered: