You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Poco currently has strict option validation with the assistance of the docopt library for each and every command. Docopt handles the parsing of command line arguments and provides help messages in case of wrongly used commands.
It would be great if we could somehow pass any number of arbitrary command line options to the underlying docker-compose command.
Let's take this simple use case: the poco logs command works by calling the docker-compose logs command under the hood, but we cannot pass the switch -f to follow the logs to the poco command, even though the docker-compose command would accept it.
This is a very simple example where this feature would be useful. There are other, more complex poco commands where passing arbitrary options like this is not so straightforward.
The first issue that has to be solved regarding this feature request is that docopt does not allow unknown options to be handled by the program in the current implementation. Identifying and maintaining the list of valid options of docker-compose commands is a huge task, which is not the goal of poco. Poco should not validate these options, let the underlying command do the validation.
The text was updated successfully, but these errors were encountered:
Poco currently has strict option validation with the assistance of the docopt library for each and every command. Docopt handles the parsing of command line arguments and provides help messages in case of wrongly used commands.
It would be great if we could somehow pass any number of arbitrary command line options to the underlying docker-compose command.
Let's take this simple use case: the
poco logs
command works by calling thedocker-compose logs
command under the hood, but we cannot pass the switch-f
to follow the logs to the poco command, even though the docker-compose command would accept it.This is a very simple example where this feature would be useful. There are other, more complex poco commands where passing arbitrary options like this is not so straightforward.
The first issue that has to be solved regarding this feature request is that docopt does not allow unknown options to be handled by the program in the current implementation. Identifying and maintaining the list of valid options of docker-compose commands is a huge task, which is not the goal of poco. Poco should not validate these options, let the underlying command do the validation.
The text was updated successfully, but these errors were encountered: