Repository navigation
Let the last label take precedence in the native repository - #3376
Merged
Merged
Conversation
With multiple labels the native repository passed all label locations to Spring Boot, which interleaved them by profile and gave the first label precedence. The SCM, S3, JDBC and other repositories resolve each label on its own and let the last label win. Resolve one label at a time and let the last label take precedence. The previous behavior can be restored with spring.cloud.config.server.native.lastLabelWins=false. Enable the compliance test for multiple labels. Signed-off-by: Ryan Baxter <ryan.baxter@broadcom.com>
spencergibb
approved these changes
Nov 2, 2026
spencergibb
left a comment
spencergibb
left a comment
Member
There was a problem hiding this comment.
Lot's of subtleties coming out because of your fixture. Good stuff.
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.
With multiple labels the native repository passed all label locations to Spring Boot, which interleaved them by profile and gave the first label precedence. The SCM, S3, JDBC and other repositories resolve each label on its own and let the last label win.
Resolve one label at a time and let the last label take precedence. The previous behavior can be restored with
spring.cloud.config.server.native.lastLabelWins=false.
Enable the compliance test for multiple labels.