Documented configuration option for url
This commit is contained in:
parent
ef7fd10b15
commit
a3f88eddad
1 changed files with 7 additions and 1 deletions
|
@ -50,6 +50,12 @@ Other options include:
|
|||
|
||||
which restricts the included nodes to those from the given datacenter
|
||||
|
||||
'url':
|
||||
|
||||
the URL of the Consul cluster. host, port and scheme are derived from the
|
||||
URL. If not specified, connection configuration defaults to http requests
|
||||
to localhost on port 8500.
|
||||
|
||||
'domain':
|
||||
|
||||
if specified then the inventory will generate domain names that will resolve
|
||||
|
@ -95,7 +101,7 @@ kv_metadata is used to lookup metadata for each discovered node. Like kv_groups
|
|||
above it is used to build a path to lookup in the kv store where it expects to
|
||||
find a json dictionary of metadata entries. If found, each key/value pair in the
|
||||
dictionary is added to the metadata for the node. eg node 'nyc-web-1' in datacenter
|
||||
'nyc-dc1' and kv_metadata = 'ansible/metadata', then the key
|
||||
'nyc-dc1' and kv_metadata = 'ansible/metadata', then the key
|
||||
'ansible/groups/nyc-dc1/nyc-web-1' should contain '{"databse": "postgres"}'
|
||||
|
||||
'availability':
|
||||
|
|
Loading…
Reference in a new issue