Spring Cloud Config Starter Bootstrap ignores config discovery from application.yml

Hello Spring Cloud Config Team,

I have recently been making changes to a personal project, I have updated to the spring cloud version 2020.0.0 (with the spring-cloud-config-dependencies 3.0.1 fixes) and I am also modifying the configurations to use discovery first. I have a config server (port 8889) and a eureka server that we are going to assume well configured and they register correctly. I also have a client service with the following configuration and dependencies:

application.yml

spring:
  application:
    name: client-service
  cloud:
    config:
      discovery:
        enabled: true
        service-id: config-server
      username: user
      password: 1234  
eureka:
  client:
    serviceUrl:
      defaultZone: http://localhost:8761/eureka/

pom.xml

<dependencies>
  <dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-web</artifactId>
  </dependency>
  <dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-oauth2-resource-server</artifactId>
  </dependency>
  <dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-data-mongodb</artifactId>
  </dependency>
  <dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter</artifactId>
  </dependency>
  <dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-netflix-eureka-client</artifactId>
  </dependency>
  <dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-sleuth-zipkin</artifactId>
  </dependency>
  <dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-openfeign</artifactId>
  </dependency>
  <dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-bootstrap</artifactId>
  </dependency>
  <dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-config</artifactId>
  </dependency>
  <dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-aop</artifactId>
  </dependency>
  <dependency>
    <groupId>org.springframework.retry</groupId>
    <artifactId>spring-retry</artifactId>
  </dependency>
  <dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-actuator</artifactId>
  </dependency>

  <!-- ... Test Dependencies, Mapstruct and Lombok -->

</dependencies>

<dependencyManagement>
  <dependencies>
    <!-- Temp Fix, see https://github.com/spring-cloud/spring-cloud-release/wiki/Spring-Cloud-2020.0-Release-Notes#known-issues -->
    <dependency>
      <groupId>org.springframework.cloud</groupId>
      <artifactId>spring-cloud-config-dependencies</artifactId>
      <version>3.0.1</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
    <dependency>
      <groupId>org.springframework.cloud</groupId>
      <artifactId>spring-cloud-dependencies</artifactId>
      <version>${spring-cloud.version}</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  </dependencies>
</dependencyManagement>

With this configuration the client tries to connect to http: // localhost: 8888 and debugging the start you can see this:

Condition OnPropertyCondition on org.springframework.cloud.netflix.eureka.config.EurekaConfigServerBootstrapConfiguration did not match due to @ConditionalOnProperty (spring.cloud.config.discovery.enabled) did not find property 'spring.cloud.config.discovery.enabled'

However if I rename the application.yml to bootstrap.yml it works fine, and the application ends up configured with the properties from config server. From what I understand in the documentation the new spring-cloud-starter-bootstrap replaces the need for the bootstrap.yml, right? or should some things still go there?

Thank you very much for the great job you do.

Comment From: spencergibb

If you have the bootstrap starter it needs to be in bootstrap.yml

Comment From: yelkko

Oh I am sorry, in that case I misunderstood the documentation. I understood that the new starter came to replace the bootstrapping including the bootstrap.yml file. Thank you very much for the quick response and excuse me for the inconvenience. The incident can be closed, regards.