-
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 support for propery source origin introduced in boot 2 #866
Comments
Boot's env endpoint changed for a simple key -> value, to key -> {value, origin}. Config server would need to be backward compatible. Two options, either a new prefix (v2) or a content type (which is what boot uses). I think I lean towards the content type. Boot's content type Example output:
|
We could enhance the origin depending on the environment. For example, git blame information could be added, etc... |
From
|
Adds a new format if requested using v2 Accept header, otherwise the format is backwards compatible so older clients will work with new servers. fixes gh-866
This comment has been minimized.
This comment has been minimized.
Adds a new format if requested using v2 Accept header, otherwise the format is backwards compatible so older clients will work with new servers. fixes gh-866
This allows the boot origin tracking mechanism to work if bootstrap loaded propertysources themselves are also origin tracked. See spring-cloud/spring-cloud-config#866
This allows the boot origin tracking mechanism to work if bootstrap loaded propertysources themselves are also origin tracked. See spring-cloud/spring-cloud-config#866
Adds a new format if requested using v2 Accept header, otherwise the format is backwards compatible so older clients will work with new servers. fixes gh-866
Adds a new format if requested using v2 Accept header, otherwise the format is backwards compatible so older clients will work with new servers. fixes gh-866
This would be helpful in debugging configuration problems.
@dsyer @twicksell
The text was updated successfully, but these errors were encountered: