Skip to content

Do not return profile-specific property sources#3023

Merged
ryanjbaxter merged 1 commit intospring-cloud:4.3.xfrom
ryanjbaxter:no-profile-propertysources-new
Aug 20, 2025
Merged

Do not return profile-specific property sources#3023
ryanjbaxter merged 1 commit intospring-cloud:4.3.xfrom
ryanjbaxter:no-profile-propertysources-new

Conversation

@ryanjbaxter
Copy link
Copy Markdown
Contributor

When a property source uses spring.profiles.import the config server would return property sources activated by this configuration property even if the config client did not request profile information. This is due to using Spring Boots ConfigDataEnvironmentPostProcessor to load configuration from the file system (which is not only used for native but also for git and svn). This change makes it so the config server will not activate profiles if the config client does not request any profile data.

See the corresponding change in Spring Boot spring-projects/spring-boot#42932 (comment)

@ryanjbaxter ryanjbaxter changed the title No profile property sources new Do not return profile-specific property sources Aug 20, 2025
@ryanjbaxter ryanjbaxter added this to the 4.3.1 milestone Aug 20, 2025
@ryanjbaxter ryanjbaxter merged commit dd431e9 into spring-cloud:4.3.x Aug 20, 2025
2 checks passed
@github-project-automation github-project-automation Bot moved this to Done in 2025.0.1 Aug 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

No open projects
Status: Done
Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants