-
Notifications
You must be signed in to change notification settings - Fork 160
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 client_key_contents #402
Conversation
Signed-off-by: Ferenc Kovács <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
bump |
any feedback would be appreciated to move this forward, I'm using this patch locally without an issue for a month now, would be nice having it merged |
bump |
hello, any update on this? please let me know if there is anything needed from my side to move ahead with merging this. |
Hi @Tyrael, thanks for creating the PR. We have marked the review/merge in our task queue. If possible, could you please add a test for this change? |
sure, would the following two test scenarios be enough:
|
Signed-off-by: Ferenc Kovács <[email protected]>
hi @vkarve-chef, |
Signed-off-by: Vikram Karve <[email protected]>
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
I can see that this also present in the v4.1.11 tag but I can't see that tag on https://rubygems.org/gems/chef-vault/versions/ |
nevermind, I can see the "Changes not yet released to rubygems.org" part in the Changelog, so this was intentional |
Description
adds support for chef-vault to use the private key from the client_key_contents chef configuration option
Related Issue
#401
Types of changes
Checklist: