#2914 Moving list of available audit events out of CS.cfg
Closed: fixed by edewata. Opened by edewata.

Currently the list of available audit events is stored as a comment in the CS.cfg, which does not get updated automatically without writing an upgrade script.

log.instance.SignedAudit._000=##
log.instance.SignedAudit._001=## Signed Audit Logging
log.instance.SignedAudit._002=##
log.instance.SignedAudit._003=##
log.instance.SignedAudit._004=## Available Audit events:
log.instance.SignedAudit._005=## AUDIT_LOG_STARTUP,AUDIT_LOG_SHUTDOWN,ROLE_ASSUME,...
log.instance.SignedAudit._006=##

A short term solution is to move the list into a man page (e.g. pki-server-config.5), and remove the list from existing instances with an upgrade script.

A long term solution is to provide a CLI to manage audit events:

$ pki-server ca-audit-event-find
------------------
37 entries matched
------------------
  Event Name: ACCESS_SESSION_ESTABLISH
  Enabled: True
  Filter: None
  Event Name: AUTH
  Enabled: False
  Filter: None
  Event Name: RANDOM_GENERATION
  Enabled: True
  Filter: (Outcome=Failure)
  ...
$ pki-server ca-audit-event-mod AUTH --enabled True --filter "(Outcome=Success)"

Metadata Update from @mharmsen:
- 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
- Issue set to the milestone: 0.0 NEEDS_TRIAGE

Fixed in master: https://github.com/dogtagpki/pki/commit/0ec550d2652e322a7e4a5af6a379852346926c5d

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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

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