InvalidConfigDataPropertyException thrown when server processed ConfigData contains profiles #24890
Comments
This was referenced Jan 19, 2021
|
I've got a fix that should restore previous Spring Cloud Config Server behavior. There is one unfortunate issue that I can't fix until Spring Boot 2.5. If you have a I think we can live with this limitation for now, since the same thing happened with previous versions of Spring Cloud/Boot. |
This was referenced Mar 11, 2021
Closed
Merged
Merged
This was referenced Mar 16, 2021
Closed
Bump spring-boot-starter-parent from 2.4.2 to 2.4.3
checkmarx-ltd/checkmarx-spring-boot-java-sdk#106
Closed
philwebb
added a commit
that referenced
this issue
Apr 9, 2021
Add custom `ApplicationEnvironment`, `ApplicationServletEnvironment` and `ApplicationReactiveWebEnvironment` subclasses for use with `SpringApplication`. The subclasses all disable the resolution of active and default profiles using properties since this is handled directly by the `ConfigDataEnvironmentPostProcessor`. Closes gh-24892 See gh-24890
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With Spring Cloud Config Server any
spring.profiles.activeandspring.profiles.includeproperties should only apply to the server-side. The config should ignore them. See #24876 and spring-cloud/spring-cloud-config#1788 for additional background.Since we don't want to revert #24733, we need to find a way for Spring Cloud's
ConfigServerConfigDataLocationResolverto indicate that a property source should not process any of it's profile properties. It looks like we might be able to do this by adding aConfigData.IGNORE_PROFILESoption that Spring Cloud can set.The text was updated successfully, but these errors were encountered: