Sensitive config values with fallback

[paullatzelsperger]

Feature

Implement sensitive configuration values:

Solution proposal

every sensitive config value is resolvable as follows:

• if <configkey>.alias is not-null, interpret its value as secret alias and resolve the sensitive configuration value from the Vault
• if <configkey>.alias is null, resolve the value directly from a configuration <configkey>
• both <configkey>.alias and <configkey> must be non-required to allow this mechanism. If a config value is indeed mandatory, this must be handled in client code, e.g. in the initialize() method.

[paullatzelsperger]

@benhid if you want, feel free to take this and assign it to yourself :)

[github-actions]

This issue is stale because it has been open for 14 days with no activity.

[github-actions]

This issue is stale because it has been open for 14 days with no activity.