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