Raise usage errors if inappropriate hab svc load options are given in hab sup run

[christophermaier]

hab sup run is used to start a Supervisor, and hab svc load is used to instruct a running Supervisor to load a new service.

However, as a way to have allow Habitat containers to start-and-load a service in a single ENTRYPOINT, hab sup run takes options and arguments of hab svc load to effectively perform both operations at once.

However, this has led to confusion, in that it is currently possible to provide hab svc load options to hab sup run commands that have no effect, but are not marked as errors.

For example, hab sup run --topology=leader is legal, and a Supervisor starts up, but it makes no sense, as --topology concerns how services run, not how Supervisors run. As a result, some users talk about "running a Supervisor in a leader topology". This is wrong, and needlessly confusing.

(A more correct invocation would be hab sup run core/redis --topology=leader, which says "Start a Supervisor, and then load and run core/redis as a service in a leader topology".)

Other scenarios can be presented for all the other hab svc load options that are provided to hab sup run without also providing the package identifier of the service they should apply to.

While it would be nice to ultimately tease these two commands apart more completely, for the near term we should adjust our CLI code to better document such instances, as well as catch them as errors when they are invoked. This will help to make it more clear what the distinction between Supervisors and Services is.

[stale]

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.