This repository has been archived by the owner on Jan 19, 2022. It is now read-only.
Fix for property ordering as reported in https://github.com/spring-cl… #773
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.
…oud/spring-cloud-aws/issues/772
📢 Type of change
📜 Description
When building up the context path use the active profiles in reverse order.
E.g. with the following properties and using the prefix of context:
spring.profiles.active=profile_a,profile_b
spring.application.name: sample-app
Ensure that the context paths are in the following order:
context/sample-app_profile_b/
context/sample-app_profile_a/
context/sample-app/
context/application_profile_a
context/application_profile_b
context/application
💡 Motivation and Context
Fixed a bug introduced in 582fdc6 where properties don't seem to be able to be overridden based on the the last specified profile
This caused some confusion when running an upgraded spring boot and spring cloud project on our test servers due to properties being in a different order from previous versions
Fix #772
💚 How did you test it?
Wrote unit tests and tested locally using a snapshot version
📝 Checklist
🔮 Next steps