-
Notifications
You must be signed in to change notification settings - Fork 135
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
Krm/tink server #573
Krm/tink server #573
Conversation
d60b502
to
2ed353d
Compare
2ed353d
to
a82ae63
Compare
Codecov Report
@@ Coverage Diff @@
## main #573 +/- ##
==========================================
- Coverage 45.86% 44.39% -1.48%
==========================================
Files 56 61 +5
Lines 3268 3489 +221
==========================================
+ Hits 1499 1549 +50
- Misses 1686 1857 +171
Partials 83 83
Continue to review full report at Codecov.
|
b679144
to
418b8b8
Compare
## Description * Externalized worker package for testability * Created `ContainerManager` and `ContainerLogger` abstractions * Added tests for new interfaces * Cleaned up worker method arguments (logger is now passed via context) * Left worker logic unchanged * Refactored `Worker` struct and initialization ## Why is this needed I was working on #573 and wanted to be able to create a 'virtual worker' with faked-out Docker client calls. This refactor will make it easy immediately test API changes and later refactor the worker logic. ## How Has This Been Tested? * Tested locally with a workflow * Added unit tests ## How are existing users impacted? What migration steps/scripts do we need? No impact to existing users ## Checklist: I have: - [ ] updated the documentation and/or roadmap (if required) - [x] added unit or e2e tests - [ ] provided instructions on how to upgrade
418b8b8
to
16639c2
Compare
16639c2
to
4be71dd
Compare
4be71dd
to
8387611
Compare
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.
NIIIIIIIIIIIIIIIIICE, /lgtm
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.
skipped over virtual-worker stuff and everything else looks alright. Haven't really used bdd style tests and tooling but if that works for you then 👍. server
is looking pretty big, we should split it up so the k8s and sql backends are separate subpackages later I think.
I've added do-not-merge just until #602 is merged. |
8387611
to
3d7ac1d
Compare
3d7ac1d
to
e064472
Compare
6efd3d7
to
f80d5fa
Compare
f80d5fa
to
2a8c9a6
Compare
* Add e2e ginkgo tests Signed-off-by: Micah Hausler <[email protected]>
2a8c9a6
to
cc49e78
Compare
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.
I'm a little late on the review here. I've noted a few places we can iterate on.
I'm glad to see we're moving ahead 🚀
@@ -60,6 +60,7 @@ func NewRootCommand(version string, logger log.Logger) *cobra.Command { | |||
logger, | |||
tinkWorker.WithMaxFileSize(maxFileSize), | |||
tinkWorker.WithRetries(retryInterval, retries), | |||
tinkWorker.WithDataDir("./worker"), |
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.
I realize the virtual-worker has limited use-cases, but perhaps --data-dir
could be added with ./worker
as the default.
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.
Good idea!
}, | ||
wantErr: nil, | ||
}, | ||
{ |
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.
Perhaps we can also test Global Timeout.
return nil, errNotImplemented | ||
} | ||
|
||
// ListWOrkflows will return a not implemented error. |
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.
// ListWOrkflows will return a not implemented error. | |
// ListWorkflows will return a not implemented error. |
Description
This PR adds a Kubernetes API backend to Tinkerell as a replacement for Postgres.
This PR builds on #563 and adds new API capabilities
Why is this needed
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have: