Repository navigation
Do not return profile-specific property sources - #3023
Merged
ryanjbaxter merged 1 commit intoAug 20, 2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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)