Layered Configuration

[Ichthyostega]

Develop a design for structured configuration within the application.

Requirements

• allow for groups of configuration accessible as scope from parts of the application. E.g. the Engine can have an EngineConfig
• investigate the possibility of consistency checking, i.e. the consumer of the configuration (the implementation part) should be able to define valid keys, both required and optional; misspelled and nonexistent configuration should be reported
• Configuration must be assembled from several configuration sources, with clear defined precedence and shadowing. Notably we have default configuration, system-wide configuration, user specific configuration and project related configuration
• Application must be able to alter configuration settings, thereby intelligently routing the changes into the appropriate configuration source
• Any detected configuration change must be captured and logged as Event

[Undercover Agent]

Migration MasterTickets ⟼ Subtickets-plugin