-
Notifications
You must be signed in to change notification settings - Fork 39
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
Use puppet-openssl and remove use of katello-certs-tool #453
base: master
Are you sure you want to change the base?
Conversation
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.
Interesting idea. Do we today have any checks in katello-certs-tools that we would need to port over?
@@ -59,7 +59,7 @@ | |||
String $city = $certs::city, | |||
String $org = $certs::org, | |||
String $org_unit = $certs::org_unit, | |||
String $expiration = $certs::expiration, | |||
Variant[Integer, String] $expiration = $certs::expiration, |
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.
I'd be open to a PR that already changes it from Strings to Integers prior to merging this.
Checks? None that I am aware of - do you have ideas of what you are thinking? The riskiest part of this change I believe is to ensure that for existing installations the CA certificate / key / password are not regenerated. I've added a new migration test that uses a copy of what a standard looking katello-certs-tool based generated certificate looks like to check that it does not change. |
a1ce816
to
99d5f71
Compare
I've opened a PR for the puppet-openssl support I am relying on here. (voxpupuli/puppet-openssl#188) |
99d5f71
to
0e25381
Compare
No description provided.