-
Notifications
You must be signed in to change notification settings - Fork 54
Add credential manager for external secret providers #63
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
Conversation
jjmerchante
left a comment
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.
Overall, it looks good to me as it includes useful functionality, but it might need some changes that I detail below.
|
I'm on it, will update when I fix those. |
|
All the changes are up! |
sduenas
left a comment
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 made some general comments to your PR. I think this is a nice functionality to have but there's room for improvement. Please address my comments and fix the flake8 errors reported too.
grimoirelab_toolkit/credential_manager/secrets_manager_factory.py
Outdated
Show resolved
Hide resolved
|
All changes should be up and running. I'll be waiting for any other corrections! :) |
08b2f0f to
f3e0133
Compare
Implement unified credential management system that supports retrieving secrets from Bitwarden, HashiCorp Vault, and AWS Secrets Manager. Key features: - Factory pattern - Command-line interface - Python API - Full test coverage The system allows secure credential management without hardcoding sensitive information in configuration files. Signed-off-by: [Your Name] <[your-email]> This is a combination of 2 commits. Added credential_manager tool and tests. Updated README.md to include credential_manager instructions,. Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
…lems. Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
… of the project. Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Also updated docstring to reflect the change. Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
…rogram. Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Also fixed some docstring formatting. Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
Signed-off-by: Alberto Ferrer Sánchez <alberefe@tutanota.com>
7d1b8a5 to
d8cb01f
Compare
|
I force-pushed stuff following the instructions that I found in DCO from the signoff problems. I am not sure this was the correct thing to do and would like some guidance / opinions on the matter and hope I'm not breaking anything. |
sduenas
left a comment
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.
Can you squash your commits and create the commits only needed for this feature? It will be easier to review them.
grimoirelab_toolkit/credential_manager/secrets_manager_factory.py
Outdated
Show resolved
Hide resolved
sduenas
left a comment
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.
Why don't you open a new PR, with just the basic functionality, probably just the code needed to make it work with Bitwarden, and after we merge it, you add the functionality in different PRs for Amazon and Hashicorp Vault?
This way it would be easier to test and review and you can just push the necessary commits for it. I suggest you should rebase the commits, squashing them and keeping only the relevant code.
Please read this: https://github.com/chaoss/grimoirelab/blob/main/CONTRIBUTING_WITH_CODE.md#contributing-with-code
|
Okay, I'll do a new PR. Just fixed the bw_manager.py and will open a new PR with the changes like you say. Will reread that document, sorry for not following all the things, first time doing something like this and it's being a little overwhelming. Will follow your instructions after reading the document. |
Implement unified credential management system that supports retrieving secrets from Bitwarden, HashiCorp Vault, and AWS Secrets Manager.
Key features:
The system allows secure credential management without hardcoding sensitive information in configuration files.
Updated README.md to include instructions.