Companion

The metadata a module adds by hand to what its properties classes give.

The prefix of the environment variables checked: Spring maps WOW_X_Y to wow.x.y.

The maps of beans whose keys are checked to the value's properties (MAPS), by the map's name: the permits of the calling services, the peers this one calls, and each aggregate's, store's, subscription's, schedule's and error code's settings.

The metadata Spring Boot's tooling reads, in the host's jar and any module's.

The migration guide's page of the configuration keys of earlier versions.

The modules whose own metadata declares the keys under a prefix: a key there is unknown when the module is not on the class path, and the refusal names it.

Why a variable of the application's own under a Wow group is refused too, and what to do.

The module that declares key, when its prefix is one of MODULES.

The property name key stands for: a wow.* key as written, an environment variable as Spring maps it (lower case, _ a dot, a number an index).

The property names key may stand for: a wow.* key as written; an environment variable as nameOf maps it, and in Spring's legacy form too, each underscore between two words a dash or a dot (WOW_COSEC_TENANT_LEVEL_ROLES is wow.cosec.tenant-level.roles), as Spring's binder reads it.

The keys of every METADATA and ADDITIONAL_METADATA resource of classLoader, each module's, and the declared keys no metadata needs to list (the wow.<type>.<key> options the node's providers declare), with the prefixes of the application's other properties beans (prefixes) that no metadata describes, and the storeOptions the store providers declare, which a store sets as wow.stores.<name>.<key>.