erabii

I don't know about this... you can write your own listener and catch `RefreshScopeRefreshedEvent`, right?

I was not too verbose on the above comment, but IMO, I don't understand what log statement you would want. When we log: "Detected change in config maps" for example,...

I don't think that this is what OP is asking for. That log statement still comes when we receive an event from kubernetes about the state of a certain configmap....

@litepl I think you should have mentioned that in the initial description. We have a bunch of logs from configuration watcher side for this. At the moment they are on...

I am still inclined not to do this. A log statement there does nothing useful, imho; but if someone really needs it, its really easy to write your own Listener...

very nice, thank you for this one!

we hit the same issue with `5.4.0` ``` "hz.client_1.event-5@9677" tid=0x4a nid=NA waiting java.lang.Thread.State: WAITING at jdk.internal.misc.Unsafe.park(Unsafe.java:-1) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:371) at com.hazelcast.spi.impl.AbstractInvocationFuture.manageParking(AbstractInvocationFuture.java:694) at com.hazelcast.spi.impl.AbstractInvocationFuture.get(AbstractInvocationFuture.java:616) at com.hazelcast.client.impl.spi.ClientProxy.invokeOnPartition(ClientProxy.java:188) at com.hazelcast.client.impl.spi.ClientProxy.invoke(ClientProxy.java:182) at com.hazelcast.client.impl.proxy.ClientMapProxy.getInternal(ClientMapProxy.java:266) at com.hazelcast.client.impl.proxy.ClientMapProxy.get(ClientMapProxy.java:260)...

This is a good example where we can't drop the usual set-up of the integration test, cause we need a side container here. So all I did in this module...

@ryanjbaxter minor thing here as I continue to refactor integration tests

I spent some time yesterday looking at this one. `DiscoveryClient` can give back two things : _names_ of the services and _instances_ of a single service (endpoints under a service)....