Default maven filtering does not apply to bootstrap.yml

[Laures]

With the spring-boot default config (parent-pom) i can only use maven filtering in application-properties or -yml files but not the spring-cloud-config bootstrap.yml.

I'm my case i want to use cloud-config together with eureka and i want the metadata-map of eureka to include the project version so my bootstrap.yml looks like this:

spring:
    application:
        name: gateway-service
    profiles:
        active: staging
    cloud:
        config:
          discovery:
            service-id: service-registry
            enabled: true

eureka:
  client:
    serviceUrl:
      defaultZone: http://service-registry:8761/eureka/
  instance:
    instanceId: ${spring.application.name}:${spring.application.instance-id:${random.value}}
    prefer-ip-address: true
    metadata-map:
      profile: ${spring.profiles.active}
      version: ${info.project.version}

info:
  project:
    version: @project.version@

i did add the bootstrap.yml to the list of filtered resources but filtering it by default sounds useful to me.

[wilkinsona]

Spring Boot doesn’t know anything about bootstrap.yml as it’s a Spring Cloud concern. If we change that, we’ll create a conceptual cycle between Boot and Cloud so I don’t think we should. The alternative would be to filter all .yml and .yaml files but I think that may be going too far. For these reasons I think we should decline this request, but let’s see what the rest of the team thinks.

[spencergibb]

If you used spring.config.name=myconfig, so boot was looking for myconfig.{yml|properties} you'd be in a similar situation.

[wilkinsona]

Thanks for the suggestion, but we've decided that we don't want to do this for the reasons described above.