-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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.
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
Add API To Config Server To Return Configuration Only For Profiles #2291
Labels
Comments
ryanjbaxter
added a commit
to ryanjbaxter/spring-cloud-config
that referenced
this issue
Jun 16, 2023
ryanjbaxter
added a commit
to ryanjbaxter/spring-cloud-config
that referenced
this issue
Jun 16, 2023
ryanjbaxter
added a commit
to ryanjbaxter/spring-cloud-config
that referenced
this issue
Jun 16, 2023
ryanjbaxter
added a commit
that referenced
this issue
Jun 16, 2023
Fixes #2279 Fixes #2289 See #2291 Co-authored-by: Ryan Baxter <[email protected]>
This was referenced Jul 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Spring Boots Config Data support separates loading config data into two steps, configuration data without profiles and then configuration with profiles. We try our best to label
PropertySources
asPROFILE_SPECIFIC
inConfigServerConfigDataLoader
but its error prone because depending on the configuration of the config server the profile separator could be anything. AWS Secrets Manage, AWS Parameter Store and Vault all allow for profile separator configuration.We know when the config data API is only requesting profile specific property sources so we could make a specific request to the config server to just return the profile specific property sources.
The text was updated successfully, but these errors were encountered: