#399 add system specific overrides to pkideployment.cfg so that a single file can be customized for multiple subsystems
Closed: Fixed None Opened 11 years ago by vakwetu.

Currently installing from the same config file works only if the defaults are used (without any overrides).

We will need system specific overrides for general operation.

Take for example, IPA. They will have already defined many of the parameters (admin_uid, db name, dn etc). So if they want to install a KRA then they work need to customize a second file. That is not ideal.


master:

  • 68751fb281477190cad960d2ef4fce2d15e00798
  • ba1e743ed6903d063543c817abe6543c8bae74ba

master:

  • 5e93dc2ce2c26c43d3e2f7e9a40cbf08507a5ea6
  • 471a49326ee8755bf2440962a36a30f4df619a17

interpolation code:

065d883a5595154ec4ca91e890aa380e3bf1d6b2
a3f7d585fed02fb8b0adaf46228f23bf1275c596

master:

  • 81bb209d0a3227f544b7b8e4ec3fc0631c8f3c47

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

7 years ago

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

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.

Login to comment on this ticket.

Metadata