__This is a local fork of this client. Newer versions of consul do not return X-Consul-Knownleader: true
when steaming. This breaks the current behavior of this client. This fork removes the check for that. Hopefully this can be PR'd into the rickfast version and we can move back to it at some point.
See hashicorp/consul#9776 for more information.
Simple client for the Consul HTTP API. For more information about the Consul HTTP API, go here.
Although this is pretty obvious to those following this repo, I am no longer actively enhancing or fixing issues for this library. I will continue to merge PRs and cut releases. I am in the process of moving off of Travis to Actions, and will set up automatic releases for any merge to master.
In 0.13.x, both shaded and non-shaded JARs are provided. The shaded JAR has a shaded
classifier, while the non-shaded JAR has no classifier. Note that this is a change from 0.12 and 0.11.
In 0.11.X and 0.12.x, the Consul JAR is a shaded JAR, with most dependencies included. This was done because a number of issues being files were related to dependency conflicts. The JAR is a bit bigger, but the HTTP + JSON libraries are now internal to the JAR. Only Guava is still a transitive dependency.
dependencies {
implementation 'com.orbitz.consul:consul-client:1.5.3'
}
dependencies {
implementation("com.orbitz.consul:consul-client:1.5.3")
}
<dependencies>
<dependency>
<groupId>com.orbitz.consul</groupId>
<artifactId>consul-client</artifactId>
<version>1.5.3</version>
</dependency>
</dependencies>
Consul client = Consul.builder().build(); // connect on localhost
AgentClient agentClient = client.agentClient();
String serviceId = "1";
Registration service = ImmutableRegistration.builder()
.id(serviceId)
.name("myService")
.port(8080)
.check(Registration.RegCheck.ttl(3L)) // registers with a TTL of 3 seconds
.tags(Collections.singletonList("tag1"))
.meta(Collections.singletonMap("version", "1.0"))
.build();
agentClient.register(service);
// Check in with Consul (serviceId required only).
// Client will prepend "service:" for service level checks.
// Note that you need to continually check in before the TTL expires, otherwise your service's state will be marked as "critical".
agentClient.pass(serviceId);
HealthClient healthClient = client.healthClient();
// Discover only "passing" nodes
List<ServiceHealth> nodes = healthClient.getHealthyServiceInstances("DataService").getResponse();
KeyValueClient kvClient = client.keyValueClient();
kvClient.putValue("foo", "bar");
String value = kvClient.getValueAsString("foo").get(); // bar
You can use the ConsulCache implementations to easily subscribe to Key-Value changes.
final KeyValueClient kvClient = client.keyValueClient();
kvClient.putValue("foo", "bar");
KVCache cache = KVCache.newCache(kvClient, "foo");
cache.addListener(newValues -> {
// Cache notifies all paths with "foo" the root path
// If you want to watch only "foo" value, you must filter other paths
Optional<Value> newValue = newValues.values().stream()
.filter(value -> value.getKey().equals("foo"))
.findAny();
newValue.ifPresent(value -> {
// Values are encoded in key/value store, decode it if needed
Optional<String> decodedValue = newValue.get().getValueAsString();
decodedValue.ifPresent(v -> System.out.println(String.format("Value is: %s", v))); //prints "bar"
});
});
cache.start();
// ...
cache.stop();
You can also use the ConsulCache implementations to easily subscribe to healthy service changes.
HealthClient healthClient = client.healthClient();
String serviceName = "my-service";
ServiceHealthCache svHealth = ServiceHealthCache.newCache(healthClient, serviceName);
svHealth.addListener((Map<ServiceHealthKey, ServiceHealth> newValues) -> {
// do something with updated server map
});
svHealth.start();
// ...
svHealth.stop();
StatusClient statusClient = client.statusClient();
statusClient.getPeers().forEach(System.out::println);
StatusClient statusClient = client.statusClient();
System.out.println(statusClient.getLeader()); // 127.0.0.1:8300
consul-client
makes use of immutables to generate code for many of the value classes.
This provides a lot of functionality and benefit for little code, but it does require some additional development setup.
Official instructions are here, although you may want to change the target directories to the more gradle-like "generated/source/apt/main" and "generated/source/apt/test" targets.
Runs consul with Testcontainers
Their instructions for eclipse a bit difficult to grok, but I was able to get eclipse to compile by following the second part of the instructions. Essentially, enable annotation processing, then extend the M2_REPO variable to include the immutables annotation processor. One thing is that documentation is out of date in that it tells you the wrong jar to include - it should be org/immutables/value/2.0.16/value-2.0.16.jar.
One caveat found using IntelliJ is that you must mark your source directory as a "Generated sources root" for IntelliJ to add the contents to your classpath. For example, if you setup your target directory as "generated/source/apt/main", right-click on the 'main' subfolde and click "Mark Directory as -> Generated sources root".
Another issue is that upon changes to the build.gradle file or reimporting the gradle project, the "sources root" designation may be cleared, and it will need to be re-marked.