Add certs command#935
Conversation
cd4e29a to
29d2d21
Compare
|
This requires theforeman/puppet-certs#449 and will remain in draft until it's merged. |
1609d58 to
feec588
Compare
c0e12a9 to
05a0bb3
Compare
|
/packit build |
ed4f09d to
4c5f2bc
Compare
4c5f2bc to
6b050e5
Compare
271e39c to
d49b954
Compare
58364d5 to
17a0996
Compare
41a4b0f to
d027d7f
Compare
|
It seems that theforeman/puppet-certs#449 has been already merged for a while. I've discovered this because while trying to test |
|
/packit build |
|
Account arvind4501 has no write access nor is author of PR! |
|
this needed a rebase to get the updated version after branching, which I just did |
|
/packit build |
Signed-off-by: Eric D. Helms <ericdhelms@gmail.com>
|
@evgeni at this point, do you think we should just merge this? |
|
Do/will we need this, outside of CI? |
|
Originally I had some ideas for this use case, but this is largely for CI purposes and testing of migration from foreman-installer to |
|
I'm not opposed in merging this, but we should see that we don't ship it as part of the regular installer package to not confuse (end) users. |
The idea here is to introduce a command that can stand-alone generate certificates as is done within the installer using the same logic of puppet-certs module. This intentionally does not cover deployment, it simply allows generation of the certificates. This relies upon theforeman/puppet-certs#449 as it introduces a class that makes this process works and avoids the complication that the individual certificate classes create via their params.
The full design idea is to split generation from deployment and allow generation to happen prior to full
puppet applywithin the installer and allow the installer part to only handle deployment. This will put us a step closer to allowing users to provider their own certificates by standardizing on the set of certificates as inputs where those inputs can come directly from the user or from the self-generated set.