-
Notifications
You must be signed in to change notification settings - Fork 480
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
feat(security): Enable Vault's Consul secrets engine #3179
feat(security): Enable Vault's Consul secrets engine #3179
Conversation
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.
Works as expected.
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.
Most of these changes are rendered obsolete by by PRs. The rebase will be nasty. ;-)
not too bad I think; just 20 files... :-) |
c0a071a
to
17b3f08
Compare
@lenny-intel Rebased to the lastest secretstore client from go-mod-secret. Please review. Thanks. |
Codecov Report
@@ Coverage Diff @@
## master #3179 +/- ##
==========================================
+ Coverage 40.76% 40.86% +0.09%
==========================================
Files 170 171 +1
Lines 14507 14523 +16
==========================================
+ Hits 5914 5935 +21
+ Misses 8264 8257 -7
- Partials 329 331 +2
Continue to review full report at Codecov.
|
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.
Nice Job, just a few minor items to address.
- Add Secret Engine Enabler so that it can be re-used for both of Consul and KV secrets engines - Hookup the code in secretstore-setup so that both KV and Consul secret engines are enabled Closes: edgexfoundry#3154 Signed-off-by: Jim Wang <yutsung.jim.wang@intel.com>
…led merging conflicts Refator to move enabler to secretstore-setup in edgex-go Rebased and resolved the merging conflicts Use the secret client from go-mod-secret Signed-off-by: Jim Wang <yutsung.jim.wang@intel.com>
Address PR comments Signed-off-by: Jim Wang <yutsung.jim.wang@intel.com>
17b3f08
to
e54cfd9
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
@lenny-intel I've addressed your comments, please re-review it. Thanks! |
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.
LGTM
Closes: #3154
Signed-off-by: Jim Wang yutsung.jim.wang@intel.com
PR Checklist
Please check if your PR fulfills the following requirements:
If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/master/.github/Contributing.md.
What is the current behavior?
No Consul secret engine for Vault yet
Issue Number: #3154
What is the new behavior?
Enable Vault's Consul secret engine
Does this PR introduce a breaking change?
New Imports
Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information
To verify the Consul secret engine is enabled locally, one can observe the log message of docker container
edgex-secretstore-setup
for the first time enabling:docker logs edgex-secretstore-setup | grep Consul