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

/docs/dynamic-app-config/

This commit is contained in:
boruszak 2022-09-23 16:31:00 -05:00
parent cbc8d5df55
commit 0b742a0d75
3 changed files with 10 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
website/content/docs/dynamic-app-config/kv.mdx
View File

@ -1,10 +1,11 @@
---
layout: docs
page_title: Consul KV
description: Consul KV is a core feature of Consul and is installed with the Consul agent.
page_title: Key/Value (KV) Store Overview
description: >-
Consul includes a KV store for indexed objects, configuration parameters, and metadata that you can use to dynamically configure apps. Learn about accessing and using the KV store to extend Consul's functionality through watches, sessions, and Consul Template.
---
# Consul KV
# Key/Value (KV) Store Overview
Consul KV is a core feature of Consul and is installed with the Consul agent.
Once installed with the agent, it will have reasonable defaults. Consul KV allows

9
website/content/docs/dynamic-app-config/sessions.mdx
View File

@ -1,14 +1,11 @@
---
layout: docs
page_title: Sessions
page_title: Sessions and Distributed Locks Overview
description: >-
Consul provides a session mechanism which can be used to build distributed
locks. Sessions act as a binding layer between nodes, health checks, and
key/value data. They are designed to provide granular locking and are heavily
inspired by The Chubby Lock Service for Loosely-Coupled Distributed Systems.
Consul supports sessions that you can use to build distributed locks with granular locking. Learn about sessions, how they can prevent ""split-brain"" systems by ensuring consistency in deployments, and how they can integrate with the key/value (KV) store.
---
# Sessions
# Sessions and Distributed Locks Overview
Consul provides a session mechanism which can be used to build distributed locks.
Sessions act as a binding layer between nodes, health checks, and key/value data.

10
website/content/docs/dynamic-app-config/watches.mdx
View File

@ -1,15 +1,11 @@
---
layout: docs
page_title: Watches
page_title: Watches Overview and Reference
description: >-
Watches are a way of specifying a view of data (e.g. list of nodes, KV pairs,
health checks) which is monitored for updates. When an update is detected, an
external handler is invoked. A handler can be any executable. As an example,
you could watch the status of health checks and notify an external system when
a check is critical.
Watches monitor the key/value (KV) store, services, nodes, health checks, and events for updates. When it detects a change, it invokes a handler that can call an HTTP endpoint or run an executable. Learn how to configure watches to dynamically respond to changes in Consul.
---
# Watches
# Watches Overview and Reference
Watches are a way of specifying a view of data (e.g. list of nodes, KV pairs, health
checks) which is monitored for updates. When an update is detected, an external handler