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).
To elaborate on @M-deinum’s comment, setting Spring Boot version to 2.3.4.RELEASE (instead of 2.4.2 in my case) solved the issue. In gradle this meant changing: plugins { id ‘org.springframework.boot’ version ‘2.4.2’ … } To plugins { id ‘org.springframework.boot’ version ‘2.3.4.RELEASE’ … }
Both Spring MVC and Spring cloud feign are using the same ParameterNameDiscoverer – named DefaultParameterNameDiscoverer to find parameter name. It tries to find the parameter names with the following step. First, it uses StandardReflectionParameterNameDiscoverer. It tries to find the variable name with reflection. It is only possible when your classes are compiled with -parameters. Second, … Read more
Use a comma separated list of peers in eureka.client.serviceUrl.defaultZone. eureka.client.serviceUrl.defaultZone=http://<peer1host>:<peer1port>/eureka,http://<peer2host>:<peer2port>/eureka
Eureka Discovery Server should be used in the Peer-Aware config mode in production setups. Check: http://cloud.spring.io/spring-cloud-static/spring-cloud.html#_peer_awareness For instance your first eureka server instance will have config like this: server: port: 1111 eureka: instance: hostname: peer1 client: serviceUrl: defaultZone: http://peer2:1112/eureka/ ..and second server instance like this: server: port: 1112 eureka: instance: hostname: peer2 client: serviceUrl: defaultZone: … Read more
Spring Boot is app-centric. As @kryger said, Spring Cloud builds on boot. It solves higher level problems, such as: Distributed configuration: How to configure every instance of all of your services (standard boot config files checked into git or svn and distributed via config server). Service registration and discovery: how to locate a specific instance … Read more
We are using Spring Session to replicate the session across all of our services that sit behind a Zuul Edge Server. Zuul will authenticate the user which populates the users credentials and inserts the authenticated user into the session. This is then replicated across all the services and each service is responsible for their own … Read more
These annotations mark your services with different OAuth 2.0 roles. @EnableResourceServer annotation means that your service (in terms of OAuth 2.0 – Resource Server) expects an access token in order to process the request. Access token should be obtained from Authorization Server by OAuth 2.0 Client before calling the Resource Server. @EnableOAuth2Sso: marks your service … Read more