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 provider - senhasegura DevOps Secrets Management (DSM) #830

Closed

Conversation

lfraga
Copy link
Contributor

@lfraga lfraga commented Mar 15, 2022

Add senhasegura DevOps Secrets Management (DSM) provider

Let me know if I missed something in the provider implementation

Copy link
Contributor

@paul-the-alien paul-the-alien bot left a comment

Choose a reason for hiding this comment

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

Greetings!
Thank you for contributing to this project!
If this is your first time contributing, please make
sure to read the Developer and Contributing Process guides.
Please also mind and follow our Code of Conduct.

Useful commands:

  • make fmt: Formats the code
  • make check-diff: Ensures the branch is clean
  • make reviewable: Ensures a PR is ready for review

@knelasevero
Copy link
Member

knelasevero commented Mar 21, 2022

Thanks @lfraga! I did not know about this provider. We are a bit worried about starting to add too many providers to our list, and with that, keep increasing the maintenance load.

With that said, I want to ask you, can we count on you to respond to inquiries regarding this provider? Just cause we had some people contributing big things in the beginning and vanishing after a while :)

Also, if we need to test something, do you have an account handy to test it? If you could include a bit more info about how to create the secret and all that in the docs would be also nice!

Thanks again for the contribution!

@lfraga
Copy link
Contributor Author

lfraga commented Mar 25, 2022

Hi @knelasevero thanks for your reply

Yes, I can help with maintenance and questions about the senhasegura provider, I've been using ESO and senhasegura for a while

I'll add details in provider docs

About tests, do you have a reference guide to help me create the mocking for tests ?

@lfraga
Copy link
Contributor Author

lfraga commented Mar 25, 2022

Hi @gusfcarvalho

Thanks for you review, I will work on that and update the PR

@knelasevero
Copy link
Member

Hey @lfraga just wanted to check your availability to finish this PR :)

@lfraga
Copy link
Contributor Author

lfraga commented Apr 6, 2022

Hey @lfraga just wanted to check your availability to finish this PR :)

Hey @knelasevero , yes i'm available and working on this PR locally, thanks :)

@knelasevero
Copy link
Member

Hey @lfraga this might be relevant to you as well :)

#967

@lfraga lfraga force-pushed the feature/provider-senhasegura-dsm branch from 1650dfe to c0c1e98 Compare April 21, 2022 15:34
@lfraga
Copy link
Contributor Author

lfraga commented Apr 26, 2022

Hey @gusfcarvalho and @knelasevero , could you review again? I made the requested implementations/fixes, added improvements in the documentation, provider tests and other minor changes.

I believe the only pending task is mock for tests non-provider (go pkg dsm and auth), right ?

@lfraga
Copy link
Contributor Author

lfraga commented Apr 26, 2022

Thanks @lfraga! I did not know about this provider. We are a bit worried about starting to add too many providers to our list, and with that, keep increasing the maintenance load.

With that said, I want to ask you, can we count on you to respond to inquiries regarding this provider? Just cause we had some people contributing big things in the beginning and vanishing after a while :)

Also, if we need to test something, do you have an account handy to test it? If you could include a bit more info about how to create the secret and all that in the docs would be also nice!

Thanks again for the contribution!

Hi @knelasevero , I have several accounts on senhasegura that can be used to test DSM, tomorrow I'll send in another location to you and @gusfcarvalho details about authentication parameters 😉 (post auth info here is not a good idea)

@knelasevero
Copy link
Member

Thanks @lfraga! I did not know about this provider. We are a bit worried about starting to add too many providers to our list, and with that, keep increasing the maintenance load.
With that said, I want to ask you, can we count on you to respond to inquiries regarding this provider? Just cause we had some people contributing big things in the beginning and vanishing after a while :)
Also, if we need to test something, do you have an account handy to test it? If you could include a bit more info about how to create the secret and all that in the docs would be also nice!
Thanks again for the contribution!

Hi @knelasevero , I have several accounts on senhasegura that can be used to test DSM, tomorrow I'll send in another location to you and @gusfcarvalho details about authentication parameters wink (post auth info here is not a good idea)

🥳 Nice! If you wanna use an ots service (+ instant messaging) to send it to one of us: https://ots.uncloud.do/ Are you on kubernetes slack?

lfraga and others added 2 commits April 27, 2022 14:26
Co-authored-by: Lucas Severo Alves <lucassalves65@gmail.com>
@knelasevero
Copy link
Member

knelasevero commented Apr 27, 2022

(Not mandatory)

We have an Automatically generated change log, (that sometimes we manually edit). Would you please squash some of your intermediary commits so we have them showing up cleanly in the change log?

@sonarcloud
Copy link

sonarcloud bot commented Apr 27, 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 2 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@lfraga
Copy link
Contributor Author

lfraga commented May 2, 2022

(Not mandatory)

We have an Automatically generated change log, (that sometimes we manually edit). Would you please squash some of your intermediary commits so we have them showing up cleanly in the change log?

Yeap @knelasevero , I had a lot of conflicts during the traditional rebase and I decided to create a new PR with the exact same content as this one, but with a clean commit history

New PR: #1075

Closing this PR

@lfraga lfraga closed this May 2, 2022
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.

None yet

3 participants