Refrenced: https://wenku.baidu.com/view/493cf9eba300a6c30d229f49.html Root WebApplicationContext and the Servlet WebApplicationContext uses Environment and initializes PropertySources based on the spring profile. For non-spring boot apps, we need to customize these to get the properties from Config Server and to refresh the beans whenever there is a property change. Below are the changes that needs to happen to get … Read more
Run with spring.profiles.active=native. See the File System Backend for more details. You’ll want to set spring.cloud.config.server.native.searchLocations to the dirs you want to look at.
I realized that self preservation mode was never actually being disabled. It turns out the actual property is eureka.server.enableSelfPreservation=false (See DefaultEurekaServerConfig Code), which I haven’t found documented anywhere. This resolved my issue.
It can be done with a “serviceId” instead of a “url”. E.g. @FeignClient(“foo”) interface Client { … } and foo.ribbon.listOfServers: localhost:9000 e.g. see http://projects.spring.io/spring-cloud/spring-cloud.html#spring-cloud-ribbon-without-eureka for docs.
Spring Boot 2.4 has improved the way that application.properties and application.yml files are processed. See here for details: https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-Config-Data-Migration-Guide Long story short: If you have for example an application-local.yml and inside you defined spring: profiles: active: local then just remove this entry in the yaml file.
You need to tell the Feign scanner where to locate the interfaces. You can use @EnableFeignClients(basePackages = {“my.external.feign.client.package”, “my.local.package”}).
As pointed put by Nicoll, With Spring Cloud Vault 3.0 and Spring Boot 2.4, the bootstrap context initialization (bootstrap.yml, bootstrap.properties) of property sources was deprecated. This can be fixed in one of the 2 ways Use Spring Boot 2.4.0 Config Data API to import configuration from Vault (Preferred) Legacy Processing: Enable the bootstrap context either … Read more
In my case I had to change the following property: zuul.host.socket-timeout-millis=30000
Feign allows you to abstract the mechanics of calling a REST service. Once you configure and annotate the Feign interface, you can call a REST service by making a simple Java function call. The actual implementation of making a REST call is handled at runtime by Feign. This means that the implementation can be configured … Read more