Supporting meta-data (schema)

[m0mus]

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.

[tomas-langer]

Configuration metadata consists of two parts:

• a way to declare what properties/configurable objects are required by the application (such as a source annotation)
• a way to transfer this information to runtime (such as a file META-INF/config/config-metadata.json in each jar file that uses configuratino)

The specification should define both of these, not necessarily the way we get from the first information to the second

[Emily-Jiang]

(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.