Relative path for configFile in ACME configuration

[pki-bot]

This issue was migrated from Pagure Issue #3216. Originally filed by edewata (@edewata) on 2020-10-01 11:19:43:

• Assigned to nobody

---

Currently the configFile parameters in some ACME configuration files will only work with absolute paths. Ideally it should work with paths relative to the instance directory. For example, the following relative path:

configFile=conf/ca/CS.cfg

should be equivalent to this absolute path under the instance directory:

configFile=/var/lib/pki/pki-tomcat/conf/ca/CS.cfg

or this path under /etc directory which is linked from the instance directory:

configFile=/etc/pki/pki-tomcat/ca/CS.cfg

[pki-bot]

Comment from pingou at 2020-10-02 16:57:17

Metadata Update from @Pingou:

• Custom field component adjusted to None
• Custom field feature adjusted to None
• Custom field origin adjusted to None
• Custom field proposedmilestone adjusted to None
• Custom field proposedpriority adjusted to None
• Custom field reviewer adjusted to None
• Custom field type adjusted to None
• Custom field version adjusted to None