Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Activate a different profile from within a default one #1834

Open
Haybu opened this issue Mar 15, 2021 · 0 comments
Open

Activate a different profile from within a default one #1834

Haybu opened this issue Mar 15, 2021 · 0 comments
Assignees
@Haybu
Labels
in progress

Comments

@Haybu
Copy link
Contributor

Haybu commented Mar 15, 2021 •
edited
Loading

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
@Haybu Haybu self-assigned this Mar 15, 2021
Haybu pushed a commit to Haybu/spring-cloud-config that referenced this issue Mar 15, 2021
reload properties of remotely activated profile fixes spring-cloudgh-…
bce9d5d 
…1834
@Haybu Haybu linked a pull request Mar 15, 2021 that will close this issue
reload properties of remotely activated profile fixes gh-1834 #1835
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Haybu Haybu

Labels
in progress
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

reload properties of remotely activated profile fixes gh-1834 Haybu/spring-cloud-config
2 participants
@spencergibb @Haybu