You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 as PROFILE_SPECIFIC in ConfigServerConfigDataLoader 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:
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: