Remove cacher backend #127
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
chrisdoherty4
force-pushed
the
feat/remove-cacher-backend
branch
5 times, most recently
from
e9b5a2a to
740fe46
Compare
jacobweinstock
previously approved these changes
Oct 24, 2022
Signed-off-by: Chris Doherty <[email protected]>
chrisdoherty4
force-pushed
the
feat/remove-cacher-backend
branch
from
740fe46 to
3ac2c99
Compare
Codecov Report
@@ Coverage Diff @@
## main #127 +/- ##
==========================================
+ Coverage 21.77% 24.26% +2.49%
==========================================
Files 8 7 -1
Lines 744 680 -64
==========================================
+ Hits 162 165 +3
+ Misses 560 493 -67
Partials 22 22
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
jacobweinstock
approved these changes
Oct 24, 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.
Remove the cacher backend and the deprecated 'Watch' APIs. The cacher backend is obsolete and not used in the context of the Tinkerbell project. There are no known long-term usecases hence this is a good simplification.
Closes #126