From 7e0d6f57e990315c98d5f53c6fee58814dfcfb3c Mon Sep 17 00:00:00 2001 From: Pierre Souchay Date: Tue, 24 Apr 2018 22:40:41 +0200 Subject: [PATCH] Improved documentation --- website/source/docs/agent/services.html.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/website/source/docs/agent/services.html.md b/website/source/docs/agent/services.html.md index 746eff388b..81a72edd10 100644 --- a/website/source/docs/agent/services.html.md +++ b/website/source/docs/agent/services.html.md @@ -61,10 +61,11 @@ simpler to configure; this way, the address and port of a service can be discovered. The `meta` object is a map of max 64 key/values with string semantics. Key can contain -only ASCII chars and no special characters (`A-Z` `a-z` `0-9` `_` and `-`, no `.`). +only ASCII chars and no special characters (`A-Z` `a-z` `0-9` `_` and `-`). For performance and security reasons, values as well as keys are limited to 128 -characters for keys, 512 for values, it has the same limitations as the node meta -keys. All those meta data can be retrieved individually per instance of the service +characters for keys, 512 for values. This object has the same limitations as the node +meta keys. +All those meta data can be retrieved individually per instance of the service and all the instances of a given service have their own copy of it. Services may also contain a `token` field to provide an ACL token. This token is