Describe the bug
Version: 2.2.7.RELEASE
This is floating bug. ConfigWatch holds last saved index, but after Consul restarting, Consul can set same index for value therefore ConfigWatch doesn't publish updating event.
if (!this.consulIndexes.containsValue(newIndex) && !currentIndex.equals(-1L)) {
log.trace("Context " + context + " has new index "+ newIndex);
RefreshEventData data = new RefreshEventData(context, currentIndex, newIndex);
this.publisher.publishEvent(new RefreshEvent(this, data, data.toString()));
Sample
Put KV
Restart Consul
Put same key with changed value in Consul
AR: ConsulWatch didn't publish update event
ER: ConsulWatch published update event
Describe the bug Version: 2.2.7.RELEASE This is floating bug. ConfigWatch holds last saved index, but after Consul restarting, Consul can set same index for value therefore ConfigWatch doesn't publish updating event.
Sample