Open m0mus opened 2 years ago
Configuration metadata consists of two parts:
The specification should define both of these, not necessarily the way we get from the first information to the second
(see here on how spring does)
This needs to be namespace aware: if the file is inside in the app jar, it is scoped to the enclosed app. If the file is under a server location, there should be a way to specify which application scope it means for. Issue: how to bind to the particular app? app name?
We need to consider the tree structure, which might help. Need more thoughts on this.
As an app deployer and container administrator I want to be able to discover expected configuration options of a deployment (application). Such a discovery should allow me to read configuration keys, expected type (boolean, String), configured default value, and description.