couchbase-cli cluster-init does not work as documented

When trying to init a new cluster using the command line tool /opt/couchbase/bin/couchbase-cli it does not init a cluster per what the utility's help system or our web site documentation says either new or old style of cluster-init as it seems it changed for 3.0.

If you do the following command as prescribed when doing couchbase-cli -h or on the web documentation for 3.0 it looks like this:

./couchbase-cli cluster-init -c 127.0.0.1 \
--cluster-username=Administrator \
--cluster-password=password \
--cluster-port=8091 \
--cluster-ramsize=256

This does not work.

The way it was done in 2.5.1 and earlier was like this:
./couchbase-cli cluster-init -c 127.0.0.1 \
--cluster-init-username=Administrator \
--cluster-init-password=password \
--cluster-init-port=8091 \
--cluster-init-ramsize=256

This does not work on Couchbase 3.0 or 3.0.1.

Both of the above methods throw an error that you need a -u and -p, but since this is an init of a new cluster, there is no existing username or password. If I just add a -u and -p with appropriate information, it throws an error that the username and/or password are incorrect, but again since there is no cluster yet, how can that be true.

The only way I was able to get this to work was using as follows:

1. ./couchbase-cli cluster-init -c 127.0.0.1 \
   > -u Administrator \
   > -p password \
   > --cluster-init-port=8091 \
   > --cluster-init-ramsize=300
   SUCCESS: init 127.0.0.1

This method does not follow either the newly documented method or the old one. IMO, the tool needs to be fixed to actually follow the current documentation. Just changing the document will not be enough as what the utility does today does not follow any convention. So it is the utility that needs to be fixed.