-
Notifications
You must be signed in to change notification settings - Fork 59
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
doc: add example for write using kv v2 engine #245
Conversation
Docs Build 📝Thank you for contribution!✨ This PR has been merged and the docs are now incorporated into |
@askalski85 thank you! I hope to implement dedicated kv modules/plugins that would make this easier, but in the meantime, that is a very helpful example. I do apologize about the time spent figuring it out. Please feel free to open a discussion for help with things like this in the future. |
CI failures are not related to this PR. Despite the status being set back to operational, it seems to be caused by this dockerhub incident: https://status.docker.com/pages/incident/533c6539221ae15e3f000031/626016617fef2d04d335c7d4 |
Codecov Report
@@ Coverage Diff @@
## main #245 +/- ##
=======================================
Coverage 97.49% 97.49%
=======================================
Files 56 56
Lines 2518 2518
Branches 185 241 +56
=======================================
Hits 2455 2455
Misses 49 49
Partials 14 14
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
SUMMARY
In order to use the vault_write module I had to experiment for a longer time. Its nice to have such an example directly in the documentation so others could benefit.
ISSUE TYPE
COMPONENT NAME
Updated module: vault_write
ADDITIONAL INFORMATION
none