status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Doc changes in response to review.

This commit is contained in:
Shawn Cook 2015-09-11 15:26:30 -07:00
parent 598526eba2
commit 1f330add02
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/source/docs/agent/services.html.markdown
View File

@ -74,10 +74,10 @@ from `1`.
Note: there is more information about [checks here](/docs/agent/checks.html).
The `enableTagOverride` can optionally specified to disable the antientropy feature for
this service. If `enableTagOverride` is set to TRUE then external agents can
reregister this service and modify the tags. Subsequent local sync operations
by this agent will ignore the updated tags. For instance: If an external agent
The `enableTagOverride` can optionally be specified to disable the anti-entropy
feature for this service. If enableTagOverride is set to TRUE then external
agents can update this service in the [catalog](/docs/agent/http/catalog.html) and modify the tags. Subsequent
local sync operations by this agent will ignore the updated tags. For instance: If an external agent
modified both the tags and the port for this service and `enableTagOverride`
was set to TRUE then after the next sync cycle the service's port would revert
to the original value but the tags would maintain the updated value. As a

2
website/source/docs/internals/anti-entropy.html.markdown
View File

@ -139,7 +139,7 @@ automatically recover from these types of transient failures.
### EnableTagOverride
Synchronization of service registration can be partially modified to allow
external agents change the tag value of a service. This can be useful in
external agents to change the tags for a service. This can be useful in
situations where an external monitoring service needs to be the source of
truth for tag information. For instance: Redis DB and its monitoring service
Redis Sentinel have this kind of relationship. Redis instances are responsible