fix: add secretstores.Metadata
#582
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: seeflood <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #582 +/- ##
==========================================
+ Coverage 60.62% 60.70% +0.07%
==========================================
Files 120 120
Lines 6382 6382
==========================================
+ Hits 3869 3874 +5
+ Misses 2143 2139 -4
+ Partials 370 369 -1
Continue to review full report at Codecov.
|
zhenjunMa
previously approved these changes
May 19, 2022
Signed-off-by: seeflood <[email protected]>
…etstores_metadata
wenxuwan
approved these changes
May 19, 2022
zhenjunMa
approved these changes
May 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: seeflood [email protected]
What this PR does:
add
secretstores.MetadataWhich issue(s) this PR fixes:
Fixes #580
Special notes for your reviewer:
Does this PR introduce a user-facing change?: