Change Details

Automatic parsing and integration of the PKI subsystem into the resulting config dict is a key feature nowadays by simply passing `with_pki=True` to `get_config_dict()`. It has one small cosmetic disadvantage - when there is no PKI configured, the resulting dictionary carries an empty dictionary key - which we should avoid. We should only carry keys when we have something to tell (data available).

Automatic parsing and integration of the PKI subsystem into the resulting config dict is now enabled by passing `with_pki=True` to `get_config_dict()`. However, when no PKI configuration is present, the resulting dictionary still includes an empty PKI key. This is undesirable; we should only include keys in the dictionary when they contain relevant data.

Automatic parsing and integration of the PKI subsystem into the resulting config dict is a key feature nowadays by simply passing `with_pki=True` to `get_config_dict()`. It has one small cosmetic disadvantage - when there is no PKI configured,now enabled by passing `with_pki=True` to `get_config_dict()`. However, when no PKI configuration is present, the resulting dictionary still includes an empty PKI key. the resulting dictionary carries an empty dictionary key - which we should avoid.This is undesirable; Wwe should only carryinclude keys when we have something to tell (data available)in the dictionary when they contain relevant data.