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

add support for client_key_contents #402

Merged
merged 3 commits into from
Feb 14, 2023

Conversation

Tyrael
Copy link
Contributor

@Tyrael Tyrael commented Sep 25, 2022

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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

  • I have read the CONTRIBUTING document.
  • I have run the pre-merge tests locally and they pass.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • All commits have been signed-off for the Developer Certificate of Origin.

Signed-off-by: Ferenc Kovács <tyra3l@gmail.com>
@Tyrael Tyrael requested review from a team as code owners September 25, 2022 00:18
@sonarcloud
Copy link

sonarcloud bot commented Sep 25, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@Tyrael
Copy link
Contributor Author

Tyrael commented Oct 4, 2022

bump

@Tyrael
Copy link
Contributor Author

Tyrael commented Nov 4, 2022

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
cc @sanjain-progress @kasif-adnan @jeremiahsnapp

@Tyrael
Copy link
Contributor Author

Tyrael commented Nov 25, 2022

bump

@Tyrael
Copy link
Contributor Author

Tyrael commented Jan 13, 2023

hello, any update on this?

please let me know if there is anything needed from my side to move ahead with merging this.

@vkarve-chef
Copy link
Contributor

vkarve-chef commented Jan 16, 2023

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?
our apologies on not getting to it sooner 🙏

@Tyrael
Copy link
Contributor Author

Tyrael commented Jan 17, 2023

sure, would the following two test scenarios be enough:

  • if client_key_contents is set and client_key is not then client_key_contents should be used
  • if client_key_contents is set and client_key is also set then client_key_contents should be used

Signed-off-by: Ferenc Kovács <tyra3l@gmail.com>
@Tyrael
Copy link
Contributor Author

Tyrael commented Feb 8, 2023

hi @vkarve-chef,
sorry for the delay, I've just pushed the test related changes(some rspec, some cucumber/aruba), let me know if they look good to you or if there is anything else needed to move this PR forward

Signed-off-by: Vikram Karve <vikram.karve@progress.com>
@sonarcloud
Copy link

sonarcloud bot commented Feb 14, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@Tyrael
Copy link
Contributor Author

Tyrael commented Feb 16, 2023

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/
is that normal/expected?

@Tyrael
Copy link
Contributor Author

Tyrael commented Feb 16, 2023

nevermind, I can see the "Changes not yet released to rubygems.org" part in the Changelog, so this was intentional

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants