Remove decryption grpc from pipedv1 plugin api#5414
Merged
khanhtc1202 merged 1 commit intomasterfrom Dec 12, 2024
Merged
Conversation
Signed-off-by: khanhtc1202 <khanhtc1202@gmail.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5414 +/- ##
==========================================
- Coverage 25.82% 25.80% -0.03%
==========================================
Files 450 449 -1
Lines 48520 48472 -48
==========================================
- Hits 12530 12507 -23
+ Misses 35013 34987 -26
- Partials 977 978 +1 ☔ View full report in Codecov by Sentry. |
Merged
Merged
This file contains hidden or 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
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.
What this PR does:
as title
Why we need it:
We agreed that Piped should be in charge of preparing the deploy source, and the plugin can just pull and use it. The plugins should not need to care whether the manifest is encrypted or not.
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: