The CS.cfg contains many absolute paths which could make it harder to manage during customization or migration. It would be better to use relative paths to reduce the number of parameters that need to be fixed.
To simplify the transition, the code could support both absolute and relative paths. For example, currently we have:
instanceRoot=/var/lib/pki/pki-tomcat passwordFile=/var/lib/pki/pki-tomcat/conf/password.conf profile.DomainController.config=/var/lib/pki/pki-tomcat/ca/profiles/ca/DomainController.cfg
We can use the initial "/" to distinguish absolute and relative paths. So the above parameters can be converted like this:
instanceRoot=/var/lib/pki/pki-tomcat passwordFile=conf/password.conf profileDir=ca/profiles/ca profile.DomainController.config=DomainController.cfg
Or we can use path variables like this:
instanceRoot=/var/lib/pki/pki-tomcat passwordFile=${instanceRoot}/conf/password.conf profileDir=${instanceRoot}/ca/profiles/ca profile.DomainController.config=${profileDir}/DomainController.cfg
Legacy configuration should continue to work using the absolute paths.
Metadata Update from @edewata: - Issue assigned to vakwetu - 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/957
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)