dogtagpki

#426 Archiving default deployment config
Closed: Fixed Opened by edewata.

Closed: Fixed
Reopen Issue

Previously the pkispawn will archive the entire deployment configuration file so that it can be read by pkidestroy. With the recent simplification of the deployment configuration, the pkispawn will now only archive the user-provided configuration file, not the default configuration file. So any changes in the default configuration might affect the ability to remove existing instances.

The preferred solution is to implement ticket #425. A temporary solution would be to archive both user-provided and default configuration files.

master:

  • 81bb209d0a3227f544b7b8e4ec3fc0631c8f3c47

Metadata Update from @edewata:
- Issue assigned to mharmsen
- Issue set to the milestone: 10.0.0-0.X.rc1

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/997

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
None
None
None
Normal
defect
Installation/Configuration
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.