Let me preface this by saying that I\'m not using Spring Cloud Config directly, it is transitive via Spring Cloud Hystrix starter.
When only using @EnableHystr
I had the same problem, I wanted to have the config server disabled (as we do not need it so far) but the property mentioned above is not correct for RC1 at least.
spring.cloud.enabled
Should be:
spring.cloud.config.enabled
The config server is needed during bootstrap, and that's where the parent property sources come from. It looks like all you need to do is move your spring.cloud.config.enabled
property to bootstrap.yml (or .properties).
Regarding the discovery service followup (looks like no other posts on that), setting spring.cloud.config.discovery.enabled: false
worked for me, but only if it was set in bootstrap(yml/properties) and if I removed the @EnableDiscoveryClient
annotation from my Application
class. I guess this means one cannot use that annotation for any service where discovery will not be used at times.
spring.cloud.config.enabled=false
. ORSPRING_CLOUD_CONFIG_ENABLED=false
ORConfig server client can be disabled by adding a parameter to your app, if you pass the args to parameters to SpringApplication.run:
public static void main(String[] args) throws Exception {
SpringApplication.run(YourApplication.class, args);
}
and start the app by:
java -jar yourapplication.jar --spring.cloud.config.enabled=false
I tried all of the above changes and still config client never stopped somehow.
The only way I was able to disable it by using following exclusion in my project's pom.xml file.
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-starter</artifactId>
<exclusions>
<exclusion>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-config-client</artifactId>
</exclusion>
</exclusions>
</dependency>