Skip to content
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

Deploy the CA password file to ssl build directory #416

Merged
merged 1 commit into from
Sep 22, 2023

Conversation

ehelms
Copy link
Member

@ehelms ehelms commented Sep 22, 2023

As the pki_dir is intended for deployment rather than generation, and the CA password file is needed primarily for certificate generation it should reside in the build directory.

Copy link
Member

@ekohl ekohl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we ensure the old path is absent as well, just to clean things up?

@ekohl
Copy link
Member

ekohl commented Sep 22, 2023

Something appears to be very broken in the acceptance tests.

@ehelms
Copy link
Member Author

ehelms commented Sep 22, 2023

I think we should ensure we are managing the build directory first -- #419

As the pki_dir is intended for deployment rather than generation,
and the CA password file is needed primarily for certificate generation
it should reside in the build directory.
@@ -23,6 +23,10 @@
String $ca_key_password = $certs::ca_key_password,
Stdlib::Absolutepath $ca_key_password_file = $certs::ca_key_password_file,
) {
file { "${certs::pki_dir}/private/${default_ca_name}.pwd":
ensure => absent,
}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the cleanup

@ehelms ehelms requested a review from ekohl September 22, 2023 17:07
@ekohl ekohl merged commit 4ba477a into theforeman:master Sep 22, 2023
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants