The REST interface provides simpler and more granular way to change the configuration file. Right now each modification will generate a new backup file since the backup is timestamped. On a stable production server the changes will be rare, but during the initial setup or during fine-tuning there could be a lot of changes, which might fill the configuration folder quickly with backup files.
Some possible solutions: 1. Move the backup files into /var/log/pki/<instance>/<subsystem>/conf. 2. Move state properties that are often changed outside of CS.cfg. 3. Move non-critical properties (e.g. profiles) outside of CS.cfg. 4. Create backup at certain events (e.g. on server restart). 5. Create backup at a regular interval (e.g. using a background task). 6. Create backup on-demand (e.g. using CLI command or UI button).
Metadata Update from @edewata: - 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/1314
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)
Login to comment on this ticket.