[Akhil-1527]

Setting spring.cloud.util.enabled=false stops the application from starting. The blocking and reactive simple discovery client configurations take InetUtils in their constructors, and that bean only exists while the util auto-configuration is enabled.

Both configurations now take an ObjectProvider<InetUtils> and use it only when the bean is available, to set the local instance host. Without it, the local instance keeps the host bound from spring.cloud.discovery.client.simple.local.host and still gets the web server port.

UtilDisabledSimpleDiscoveryPropertiesAutoConfigurationTests starts a web application with util disabled and checks the blocking and reactive local instances. It fails without the change.

Fixes #631

[kdelay]

Looks right, and the new test passes locally. One note: the host assertion holds only because InetUtils is absent. Same test without spring.cloud.util.enabled=false (keeping local.host=myhost):

expected: "myhost"
 but was: "10.10.11.209"

onApplicationEvent(WebServerInitializedEvent) re-sets the host whenever InetUtils exists, so a configured local.host is kept only when util is disabled. That predates this PR, so maybe a separate issue.

[Akhil-1527]

Thanks for running it. You're right, that overwrite is already on 5.0.x: onApplicationEvent replaces the host with the InetUtils one when the web server starts, so a configured local.host only survives when InetUtils is missing. The new test covers the spring.cloud.util.enabled=false case from gh-631, which is why it passes.

I'd keep this PR to gh-631. The fix would be a small check in both onApplicationEvent methods (set the host only when local.host is empty). Happy to add it here or open a separate issue, whichever the maintainers prefer.