Added documentation for init service discovery

This commit is contained in:
vishalnayak 2016-07-21 17:12:54 -04:00
parent f557457909
commit 5316082675
1 changed files with 50 additions and 26 deletions

View File

@ -290,6 +290,30 @@ Init Options:
-recovery-pgp-keys If provided, behaves like "pgp-keys" but for the -recovery-pgp-keys If provided, behaves like "pgp-keys" but for the
recovery key shares. This is not normally available. recovery key shares. This is not normally available.
-auto If set, performs service discovery using the underlying
Consul storage backend. When one or more Vault servers
are running on Consul storage backend (none else),
setting this flag will create a Consul client and
discovrs the nodes using the service name under which
Vault nodes are registered with Consul. Service name
should be supplied using 'consul-service' flag. This
option works well when each Vault cluster is registered
under a unique service name. Ensure that environment
variables required to communicate with Consul, like
(CONSUL_HTTP_ADDR, CONSUL_HTTP_TOKEN, CONSUL_HTTP_SSL,
et al) are properly set. If, only one Vault node is
discovered, then an initialization attempt will be made.
If more than one Vault nodes are discovered, they will
be listed on the output, requiring another execution of
this command with updated VAULT_ADDR environment variable.
-consul-service Service name under which the all nodes of Vault are
registered with Consul. When Vault is using Consul
as its storage backend, by default, it will auto register
itself with Consul under the default name of "vault".
This name can be modified in Vault's configuration file,
using the "service" option under Consul backend.
` `
return strings.TrimSpace(helpText) return strings.TrimSpace(helpText)
} }