Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2930
Thanks, looks great.
The positional arguments don't seem to be sorted. I get
```
usage: storm [-h] [--config CONFIG] [-storm_config_opts -c]
{jar,localconfvalue,remoteconfvalue,local,sql,kill,upload-credentials,blobstore,heartbeats,activate,list,deactivate,rebalance,get-errors,kill_workers,admin,shell,repl,nimbus,pacemaker,supervisor,ui,logviewer,drpc-client,drpc,dev-zookeeper,version,classpath,server_classpath,monitor}
...
positional arguments:
{jar,localconfvalue,remoteconfvalue,local,sql,kill,upload-credentials,blobstore,heartbeats,activate,list,deactivate,rebalance,get-errors,kill_workers,admin,shell,repl,nimbus,pacemaker,supervisor,ui,logviewer,drpc-client,drpc,dev-zookeeper,version,classpath,server_classpath,monitor}
jar Runs the main method of class with the specified
arguments. The storm worker dependencies and configs
in ~/.storm are put on the classpath. The process is
configured so that StormSubmitter
(http://storm.apache
.org/releases/current/javadocs/org/apache/storm/StormS
ubmitter.html) will upload the jar at topology-jar-
path when the topology is submitted. When you pass
jars and/or artifacts options, StormSubmitter will
upload them when the topology is submitted, and they
will be included to classpath of both the process
which runs the class, and also workers for that
topology.
localconfvalue Prints out the value for conf-name in the local
Storm
configs. The local Storm configs are the ones in
~/.storm/storm.yaml merged in with the configs in
defaults.yaml.
remoteconfvalue Prints out the value for conf-name in the cluster's
Storm configs. The cluster's Storm configs are the
ones in $STORM-PATH/conf/storm.yaml merged in with
the
configs in defaults.yaml. This command must be run
on
a cluster machine.
local Runs the main method of class with the specified
arguments but pointing to a local cluster The storm
jars and configs in ~/.storm are put on the
classpath.
The process is configured so that StormSubmitter
(http
://storm.apache.org/releases/current/javadocs/org/apac
he/storm/StormSubmitter.html) and others will
interact
with a local cluster instead of the one configured
by
default. Most options should work just like with the
storm jar command.
<snip>
```
It's extremely minor though, and I'm not sure how to fix it. +1.
---
