[PR #9534/aac71990 backport][stable-10] (abc*, doc frags): style adjustments (#9541)

(abc*, doc frags): style adjustments (#9534)

(cherry picked from commit aac7199087)

Co-authored-by: Alexei Znamensky <103110+russoz@users.noreply.github.com>
This commit is contained in:
patchback[bot] 2025-01-06 22:01:09 +01:00 committed by GitHub
parent 80f43bbbf5
commit 26b8f30afa
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
28 changed files with 215 additions and 209 deletions

View file

@ -16,9 +16,9 @@ description:
- Registers services and checks for an agent with a Consul cluster. A service is some process running on the agent node
that should be advertised by Consul's discovery mechanism. It may optionally supply a check definition, a periodic service
test to notify the Consul cluster of service's health.
- Checks may also be registered per node, for example disk usage, or cpu usage and notify the health of the entire node to the cluster.
Service level checks do not require a check name or id as these are derived by Consul from the Service name and id respectively
by appending V(service:) Node level checks require a O(check_name) and optionally a O(check_id).
- Checks may also be registered per node, for example disk usage, or cpu usage and notify the health of the entire node
to the cluster. Service level checks do not require a check name or ID as these are derived by Consul from the Service
name and ID respectively by appending V(service:) Node level checks require a O(check_name) and optionally a O(check_id).
- Currently, there is no complete way to retrieve the script, interval or TTL metadata for a registered check. Without this
metadata it is not possible to tell if the data supplied with ansible represents a change to a check. As a result this
does not attempt to determine changes and will always report a changed occurred. An API method is planned to supply this