Open smartb-pair opened 6 years ago
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.
I still think this would help in onboarding. I keep getting very negative feedback from folks in the early stages of learning Habitat, mostly because of inconsistent experiences like this or because of surprising behavior on the CLI. We need to find a way to get a little closer the initial Docker flow, or else abandon these user cases and only go after people struggling with hardcore lift-and-shift problems for big legacy (non-cloud-native) apps.
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.
"As a Habitat user, I want to" be able to discover how the
hab
cli works without being forced to consult the (generally excellent) online docs. Habitat's current CLI behavior is great in the sense that it's self documenting - if I want to know how a particular verb can be used, I can simply typewith no arguments and get helpful output.
Where this model breaks a bit is with configs that are currently set only in environment variables, such as the
HAB_NONINTERACTIVE
option, which is commonly needed when building various kinds of scripting/automation, but is easy to forget and hard to discover.Adding a flag like
--interactive=<boolean>
would be self-documenting and less mysterious. There are probably other configuration options that are currently only handled by env vars that could additionally be controlled via flags.