more thoughts
This commit is contained in:
parent
7541165721
commit
7847ad62f1
1 changed files with 13 additions and 0 deletions
13
README.md
13
README.md
|
@ -10,6 +10,19 @@ Further, having one or more endpoints for recieving, and even calling webhooks.
|
|||
The webhooks must be a specified node.
|
||||
Perhaps the webhooks recieved would broadcast a message on the node network, and specific types of node network messages would translate out to calling a webhook.
|
||||
|
||||
## Use-cases
|
||||
|
||||
* agent on a node doing a liveness check on a service
|
||||
* agent on a node sending metric like battery power status change
|
||||
* container build event
|
||||
* curl for modtime change, and sync a repo
|
||||
|
||||
## Alternate approach
|
||||
|
||||
Since there is data pushed and data pulled, as well as new services brought in and services expected, consul.io is a very possible project to use.
|
||||
Publishing services is interesting, but maybe not the connect proxy for routing.
|
||||
Primarily for kv usage, and possibly for liveness testing of services in the datacenter.
|
||||
|
||||
# references
|
||||
|
||||
* https://github.com/adnanh/webhook
|
||||
|
|
Loading…
Reference in a new issue