Expand description
The strongly typed data structures representing canonical consul objects.
Structs§
- Represents a request to read a key from Consul Key Value store.
- Represents a request to delete a key or all keys sharing a prefix from Consul’s Key Value store.
- The service to deregister with consul’s global catalog. See https://www.consul.io/api/agent/service for more information.
- Request for the nodes providing a specified service registered in Consul.
- Represents a request to create a lock .
- Represents a request to read a key from Consul’s Key Value store.
- The node information of an instance providing a Consul service.
- Query options for Consul endpoints.
- Represents a request to read a key from Consul’s Key Value store.
- Represents a request to read a key from Consul Key Value store.
- Information related to registering a check. See https://www.consul.io/docs/discovery/checks for more information.
- Payload struct to register or update entries in consul’s catalog. See https://www.consul.io/api-docs/catalog#register-entity for more information.
- The service to register with consul’s global catalog. See https://www.consul.io/api/agent/service for more information.
- Encapsulates a consul query response and the returned metadata, if any.
- The service information of an instance providing a Consul service.
- An instance of a node providing a Consul service.
Enums§
- Most of the read query endpoints support multiple levels of consistency. Since no policy will suit all clients’ needs, these consistency modes allow the user to have the ultimate say in how to balance the trade-offs inherent in a distributed system.
- Controls the behavior of locks when a session is invalidated. See consul docs for more information.