-
Notifications
You must be signed in to change notification settings - Fork 20
Generate certificate bundle #90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
b6c101f to
dc3b348
Compare
dc3b348 to
b84f5e7
Compare
b84f5e7 to
d79a072
Compare
d79a072 to
896243b
Compare
|
@evgeni do you think we should merge this in to have this functionality available? |
|
This is sort-of, but not exactly, foreman-proxy-certs-generate? |
|
Yes - this only generates the bundle, it does not generate a set of certificates to be used. |
I don't know why I said that. It does generate: |
Signed-off-by: Eric D. Helms <[email protected]>
896243b to
a9ad699
Compare
| - role: foreman_installer_certs | ||
| when: "certificate_source == 'installer'" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This won't work as that role is not present on a prod install. How do we want to handle that?
a9ad699 to
05a6c94
Compare
Here is an idea I am playing around with. To help with splitting the installation, this would allow new installer method to generate a certificate tarball the same structure as expected input as what's created today.
This includes #89