Refactor #23799
closedMake PuppetCA pluggable
Description
Since we are planning to offer alternative options for autosinging in the future (token based instead of hostname based) (see [[http://projects.theforeman.org/issues/23211]]), and want to allow users to choose their autosigning variant (primarily to allow compatibility with old versions, old foreman versions etc) we need to make the PuppetCA module pluggable, which means moving the autosinging functionality to a provider, which can then be swapped using the SmartProxy settings. We also want to clean up the module a bit and use dependency injections etc. The common logic for listing/signing/cleaning certificates (not autosign-entries) that uses the `puppet cert` command will remain in the puppetca-module.
Updated by The Foreman Bot about 6 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/smart-proxy/pull/586 added
Updated by Timo Goebel about 6 years ago
- Translation missing: en.field_release set to 353
Updated by Julian Todt about 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset e3256834a3c3f34d23fafeef807cb63e3d7e8950.
Updated by Tomer Brisker about 6 years ago
- Triaged set to No
- Fixed in Releases added
Updated by Lukas Zapletal about 6 years ago
- Related to Bug #24553: PuppetCA migration does not work added
Updated by Ewoud Kohl van Wijngaarden about 6 years ago
- Target version changed from 869 to 1.19.0
- Fixed in Releases 1.19.0 added
- Fixed in Releases deleted (
)