-
Notifications
You must be signed in to change notification settings - Fork 98
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
Add support for certificate_content and private_key_content parameters #385
Add support for certificate_content and private_key_content parameters #385
Conversation
java_ks is a typeBreaking changes to this file MAY impact these 19 modules (near match):
This module is declared in 6 of 579 indexed public
|
fa6e69e
to
3dd4ecc
Compare
7198628
to
bdee364
Compare
Is there a timeline for review end eventually merge of the PR? |
Hey @hajee, thank you for your contribution and sorry for such a long wait. I'm happy with your PR and would like to get it merged. I'm just going to re-kick CI by closing and re-opening the PR, then pending a green run, we are good to go. |
java_ks is a typeBreaking changes to this file MAY impact these 19 modules (near match):
This module is declared in 6 of 579 indexed public
|
java_ks is a typeBreaking changes to this file MAY impact these 19 modules (near match):
This module is declared in 6 of 579 indexed public
|
Hey @hajee, please could you rebase so that this PR has the latest from main? That should get CI going again! |
bdee364
to
cffcf77
Compare
I don't think I can do something to ensure a running acceptance test, do I? |
@chelnak What is the progress on this? Anything I can do? |
java_ks is a typeBreaking changes to this file MAY impact these 19 modules (near match):
This module is declared in 6 of 579 indexed public
|
I've just re-kicked the CI jobs. Lets see what happens. |
@hajee Could you add an example to the Once that's done I think we will be ready to merge! |
cffcf77
to
c153723
Compare
@chelnak I added some text to the README and force pushed it so there is a clean git history |
Fantastic thank you! I'll get this merged! |
@hajee I just had a second look prior to merge and noticed a couple of things. Firstly, we like to keep the scope of PRs limited to their intention. I noticed you'd updated the ToC in this contribution. Please could you revert the change here? I'd be happy to accept it in another PR! Secondly I've added a comment where I think there may be a small typo in the example |
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.
Added a comment regarding the example
The current implementation only allows you to pass a file name to the certificate and private_key parameters. When you are fetching certificates from vault or another secure store, you'll first have to save them to a file. This is very innconveniant. This PR add's the parameters certificate_content and private_key_content. These parameters are mutually exclusive from their file counterparts. With this change, you can now fetch a certificate and/or a password from vault (through a hiera lookup for example) and use it directly on the type. Because these values can be sensitive, both of the new parameters support passing the value as a sensitive data type.
c153723
to
2875855
Compare
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.
Looks great! Thank you 🚀
@chelnak Thanks for merging. The next question is of course: When is a release planned? |
I'll see if we can get something out soon! |
|
||
# When no certificate file is specified, we infer the usage of | ||
# certificate content and create a tempfile containing this value. | ||
# we leave it to to the tempfile to clean it up after the pupet run exists. |
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.
or... anytime after this method exits leading to a race condition. See #425
The current implementation only allows you to pass a file name to the
certificate
andprivate_key
parameters. When you are fetching certificates from vault or another secure store, you'll first have to save them to a file. This is very innconveniant.This PR add's the parameters
certificate_content
andprivate_key_content
. These parameters are mutually exclusive from their file counterparts.With this change, you can now fetch a certificate and/or a password from vault (through a hiera lookup for example) and use it directly on the type.
Because these values can be sensitive, both of the new parameters support passing the value as a sensitive data type.