ConfigWatch requires spring-boot-actuator

Hi,

I'm using consul config in a spring application that doesn't have a web server. So I didn't include spring-boot-actuator, since I didn't see the need for it. However in ConsulConfigAutoConfiguration the ConfigWatch is enabled only when RefreshEndpoint from actuator is available.

If I put the following into my app, ConfigWatch works as expected without the actuator dependency.

@EnableScheduling
public class App extends SpringApplication {

    @Bean
    public ConfigWatch configWatch(ConsulConfigProperties properties, ConsulPropertySourceLocator locator, ConsulClient consul) {
        return new ConfigWatch(properties, locator.getContexts(), consul);
    }
}

Actuator enables scheduling automatically in MetricExportAutoConfiguration and so it would have to be enabled in ConsulConfigAutoConfiguration. I don't think there would be any side-effects from this change.

Cheers,
Michal

Start by reading ConsulConfigAutoConfiguration and ConfigWatch, focusing on the RefreshEndpoint condition and the scheduling setup. Reproduce the reported case in a Spring application without a web server or spring-boot-actuator, comparing it with the shown ConfigWatch bean. Done means ConfigWatch works without the actuator dependency while the existing configuration behavior remains intact.