#1643 Support for 'pki_instance_name' under [SUBSYSTEM]
Closed: migrated by dmoluguw. Opened by mharmsen.

It is very simple to override the /etc/pki/default.cfg value of 'pki_instance_name' in a PKI Instance override configuration file:

[DEFAULT]
...
pki_instance_name=foobar
...

However, it was recently discovered that if this value is attempted to be overridden by placing it inside of a [SUBSYSTEM] level block, an error occurs:

[DEFAULT]
...
[CA]
...
pki_instance_name=foobar
...

an error occurs as both '/var/lib/pki/pki-tomcat' and '/var/lib/pki/foobar' directories are created:

# pkispawn -s CA -f /root/pki/foobar.cfg 
Log file: /var/log/pki/pki-ca-spawn.20151009120308.log
Loading deployment configuration from /root/pki/foobar.cfg.
Installing CA into /var/lib/pki/foobar.
Storing deployment configuration into /etc/sysconfig/pki/tomcat/pki-tomcat/ca/deployment.cfg.
pkispawn    : WARNING  ....... Dangling symlink '/var/lib/pki/pki-tomcat/lib/log4j.properties'-->'/etc/pki/pki-tomcat/log4j.properties'
Installation failed.

A use case for this feature would be to allow for easier automation for deployments utilizing a large number of cloned instances.


Per CS/DS Meeting of 10/12/2015 - 10.4 - Nice to Have

Metadata Update from @mharmsen:
- 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/2202

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

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)

Metadata