The deployment code uses slots to configure various files by substituting it with the real value. The slot variables are hard-coded creating a maintenance issue and limiting the ability to add new parameters without changing the base code. It might be possible to use the parameter names directly as slots to avoid these problems.
For example, a slot is used to configure registry_instance:
PKI_SERVER_XML_CONF=[PKI_SERVER_XML_CONF]
The slot itself is defined in pkislots.cfg:
PKI_SERVER_XML_CONF_SLOT=[PKI_SERVER_XML_CONF]
And the value is defined in pkiparser.py:
config.pki_master_dict['PKI_SERVER_XML_CONF_SLOT'] =\ config.pki_master_dict['pki_target_server_xml']
Ideally the parameter itself should be used as slot directly:
PKI_SERVER_XML_CONF=[pki_target_server_xml]
At a bare minimum, can at least the assignments in 'pkiparser.py' be moved into the 'default.cfg'?
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1005
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)