Consider replacing https://github.com/Ecwid/consul-api with Interface Clients

[spencergibb]

A move to non-blocking infrastructure like spring-cloud-loadbalancer will be problematic with a blocking client.

[varnson]

Is anyone working on consul-api with WebClient?

[pturczyk]

It seems that although Ecwid/consula-api is still listed on official consul API docs, it is not really actively maintained. Last release happened on Apr 9, 2020 and reported Issues are not being addressed nor commented.

Perhaps it's worth bringing up the topic of replacing the underlying Consul API again. Especially, as some API's has been deprecated and some new features like caching are not supported.

[spencergibb]

I would use the new Interface Clients from Spring Framework. It would make it easy to do both reactive and blocking.

[alex-kormukhin]

Consul token query parameter deprecated in Consul 1.17 #809

[M-Whitaker]

Is anyone working on this? Are you accepting PRs?

[spencergibb]

Not yet, PRs wecome

[M-Whitaker]

I’m happy to start to look at creating an interface client as suggested removing the lib from the config module.

[M-Whitaker]

@spencergibb Any comments on the current draft PR are most welcome to get some feedback on the implementation.

[spencergibb]

I will look when I have time

[monwolf]

@spencergibb it's still pending, are you planning to review this PR?

[spencergibb]

@monwolf as the PR stands, it will need to wait for our major in 2025.1 (Nov 2025) as it is a breaking change. If you want to make it opt-in, I can schedule it for 2025.0 (May 2025) and then we can remove the old one in 2025.1.