erabii

@ryanjbaxter from the previous conversation that we had some time ago (where you approved the changes), all I did now is add an integration test (that is why I left...

- from the previous conversation, we agreed that since this is feature flag protected (and we do not drop the previous implementation) it does not need a major - DCO...

Can you provide a sample that for example is a github repo, with clear instructions how to re-produce the issue, let's say to deploy it in minikube or kind?

I am a bit confused, you do not have proper rights to create _any_ ConfigMap for example?

hmm... we need to know when "something" (configmap/secret in our current implementation) has changed and for that, at the moment, we use informers (think ConfigMap/Secret listeners if you want). I...

> which ConfigMaps and Secrets should I monitor (the annotations spring.cloud.kubernetes.secret.informer.enabled and spring.cloud.kubernetes.config.informer.enabled) A bit not correct. We have two ways for you to tell us which configmaps you want...

Filtering is happening in the watcher, yes. In theory, you could pass those configurations to us, via env variables for example; but how would we know _when_ to trigger a...

hmm, actually I think I get you a little. The changes in the configmaps still happens, so we can catch that event (this is when refresh must be called). Using...

yeah, this sounds like a reasonable enhancement to me, but there are things to think about here, merging is one, backwards compatibility is another... I'll see if I can find...

This is next on my TODO list, but I am heading for a vacation in a week or so. Nevertheless, I will start thinking and working on it. FYI