-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help/USAGE message for hab sup load
shows positional args with incorrect order
#2221
Comments
The usage messages are controlled by the clap crate and not directly fromo the habitat code. My suspision after looking into this briefly is that there may be a bug in clap related to parameters that can take multiple values. I noticed that any of the params other than |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you. |
1 similar comment
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you. |
When you run
hab sup load --help
it tells you:However if you do something like this:
sudo hab sup load --bind database:postgresql.default myorgin/mypkg
it throws the following error:The working command is:
sudo hab sup load myorigin/mypkg --bind database:postgresql.default
This seems like it should be a simple enough bug for me to fix on my own, but I haven't quite figured out where in the supervisor code these messages are being generated and displayed. This may be a bug in the upstream command line parser as well.
The text was updated successfully, but these errors were encountered: