Ryan Baxter

> Additionally, when using the refresh endpoint, we want to ensure that only the intended configuration changes are applied, without incorporating changes made by others. But again EVENTUALLY these changes...

> I mean multiple team updating configuration of a single application. So when team one updates configuration values and does a partial refresh and then team two updates configuration values...

After discussing this with the team we have decided to mark this as "waiting for votes" to see if anyone else would like this feature.

I fixed the current version and snapshot, @OlgaMaciaszek @marcingrzejszczak will see what they can do about the others.

Can you let us know once spring-retry 2.0.10 is released?

@klopfdreh thanks for the heads up, can you merge in the latest changes from 4.1.x and push them to your branch?

Wouldn't this log statement do the same thing? https://github.com/spring-cloud/spring-cloud-kubernetes/blob/main/spring-cloud-kubernetes-commons/src/main/java/org/springframework/cloud/kubernetes/commons/config/reload/ConfigurationChangeDetector.java#L50

So you want a log statement here? https://github.com/spring-cloud/spring-cloud-commons/blob/main/spring-cloud-context/src/main/java/org/springframework/cloud/endpoint/RefreshEndpoint.java#L41

Well this is not the repo for the request as the code that handles the `/refresh` endpoint lives in Spring Cloud Commons. It is not specific to Kubernetes its any...

I could have swore there was an issue around this already...but I can't seem to find it. I seem to remember looking into something similar a while back and discovering...