#425 Outdated archived deployment config
Closed: migrated by dmoluguw. Opened by edewata.

Currently pkidestroy will use the deployment configuration archived by pkispawn to get the various settings of the instance (e.g. file locations, port numbers). The problem is the archived configuration might become obsolete because any changes to the instance by the user will be done in the actual instance configuration files (e.g. CS.cfg, server.xml).

One solution is the pkidestroy should be modified to read the actual instance configuration files to get the parameter values needed by the scriplets.


Metadata Update from @edewata:
- Issue assigned to 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/996

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