spring-cloud / spring-cloud/spring-cloud-config
Activate a different profile from within a default one
Open
in progress
- Dominant language
- Java
- Stars
- 2k
- Forks
- 1.3k
- Avg merge
- 2d 59m
- Merged PRs (30d)
- 16
Description
Describe the bug
Currently (with SB >= 2.4.x) a profile that gets activated from within a default profile section is not taking effect. A remote application gets configured still with the default profile's properties.
Properties source for the activated profile should be reloaded. However with SB 2.4.x, it's not possible to specify spring.profiles.active from within a default section, see this issue. However, that is possible now with SB 2.5.x (snapshot now).
The attached PR works only with remote client applications that use SB 2.5.x
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.