You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
using org.springframework.cloud:spring-cloud-starter-config springCloudVerson 2020.0.0
which importsorg.springframework.cloud:spring-cloud-starter-config:3.0.0
I made new projects using Spring Initializr for Config Client and Config Server. spring.profiles.active property is ignored by Config Client and the profile default is all that's used. I see in org/springframework/cloud/config/client/ConfigServerConfigDataLocationResolver.class
The issue seems to be the ConfigServerConfigDataLocationResolver receives the active profiles via the ConfigDataLocationResolverContext but doesn't set the profile on the ConfigClientProperties instance.
Starting the app results in conflicting log statements. Where the application environment logs the new profile dev while the Spring Cloud environment logs the profile default.
2021-01-04 16:44:44.248 INFO 68447 --- [ main] m.d.client.ClientApplicationKt : The following profiles are active: dev
2021-01-04 16:44:44.285 INFO 68447 --- [ main] o.s.b.context.config.ConfigDataLoader : Fetching config from server at : http://localhost:8888
2021-01-04 16:44:44.285 INFO 68447 --- [ main] o.s.b.context.config.ConfigDataLoader : Located environment: name=client, profiles=[default], label=null, version=17e7a5825eb6a7f2dbb42003fd8c97261bf8250e, state=null
The text was updated successfully, but these errors were encountered:
iamdarkes
changed the title
Active profiles set with spring.profiles.active in application.yml not being respect by Config Client version 3.0.0
Active profiles set with spring.profiles.active in application.yml not being respect by Config Client version 3.0.0
Jan 5, 2021
iamdarkes
changed the title
Active profiles set with spring.profiles.active in application.yml not being respect by Config Client version 3.0.0
Active profiles set with spring.profiles.active in application.yml not being respected by Config Client version 3.0.0
Jan 5, 2021
Uh oh!
There was an error while loading. Please reload this page.
using
org.springframework.cloud:spring-cloud-starter-config
springCloudVerson 2020.0.0which imports
org.springframework.cloud:spring-cloud-starter-config:3.0.0
I made new projects using Spring Initializr for Config Client and Config Server.
spring.profiles.active
property is ignored by Config Client and the profiledefault
is all that's used. I see inorg/springframework/cloud/config/client/ConfigServerConfigDataLocationResolver.class
The issue seems to be the
ConfigServerConfigDataLocationResolver
receives the active profiles via theConfigDataLocationResolverContext
but doesn't set the profile on theConfigClientProperties
instance.Starting the app results in conflicting log statements. Where the application environment logs the new profile
dev
while the Spring Cloud environment logs the profiledefault
.The text was updated successfully, but these errors were encountered: