spring.profiles.include must be a comma separated value in contrast to to non-cloud usage #1417
Labels
Comments
quaff
added a commit
to quaff/spring-cloud-commons
that referenced
this issue
Feb 6, 2025
…eparated value in bootstrapProperties Fix spring-cloudGH-1417 Signed-off-by: Yanming Zhou <[email protected]>
quaff
added a commit
to quaff/spring-cloud-commons
that referenced
this issue
Feb 6, 2025
…eparated value in bootstrapProperties Fix spring-cloudGH-1417 Signed-off-by: Yanming Zhou <[email protected]>
quaff
added a commit
to quaff/spring-cloud-commons
that referenced
this issue
Feb 7, 2025
…eparated value in bootstrapProperties Fix spring-cloudGH-1417 spring-cloudGH-1329 Signed-off-by: Yanming Zhou <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
According to the documentation for
spring.profiles.includethe value forspring.profiles.includeis a list.But using this in a configuration file provided via cloud config it does not work. Instead it expects the value to be a comma separated string value:
spring.profiles.include=common,localThe offending code:
https://github.com/spring-cloud/spring-cloud-commons/blob/main/spring-cloud-context/src/main/java/org/springframework/cloud/bootstrap/config/PropertySourceBootstrapConfiguration.java#L306-L317
In Spring Boot the configuration setting is processed as a string list:
https://github.com/spring-projects/spring-boot/blob/main/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/context/config/ConfigDataEnvironment.java#L291-L310
The difference in behavior is not documented anywhere.
The text was updated successfully, but these errors were encountered: