-
Notifications
You must be signed in to change notification settings - Fork 137
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
Database interface refactor #544
Conversation
a3ebeed
to
7334b1d
Compare
Codecov Report
@@ Coverage Diff @@
## main #544 +/- ##
=======================================
Coverage 34.36% 34.36%
=======================================
Files 44 44
Lines 3384 3384
=======================================
Hits 1163 1163
Misses 2122 2122
Partials 99 99
Continue to review full report at Codecov.
|
Hey @micahhausler can you split this into a few commits please? I'm thinking:
looks to be the best break down to me. |
For an already small change is breaking it down further more of a preference or is there a documented style guide? I'm happy to do it if you think its necessary |
There is not a style guide covering this, which is unfortunate and I will remedy that soon. Looking at the history of PRs to this and other tinkerbell repos I think we've all pretty much landed on one-commit-per-change, more or less.
Yes, please. |
Also, I'll channel my @tstromberg senses and ask you to please update the PR description with info for all the changes being submitted. This way we can be sure the changes are intentional. |
Signed-off-by: Micah Hausler <[email protected]>
Signed-off-by: Micah Hausler <[email protected]>
Signed-off-by: Micah Hausler <[email protected]>
This change adds a separate interface for calls that are only invoked by APIs made by the Tink worker Signed-off-by: Micah Hausler <[email protected]>
7334b1d
to
d932a47
Compare
Done! I think CI is now waiting for some sort of maintainer approval |
Signed-off-by: Micah Hausler [email protected]
Description
This includes 4 changes that are preparatory for future work to migrate to the Kubernetes data model.
context.Background()
was used, but the stream provides a context objectcontext
package calls could be made in the methodcontext.Context
toGetWorkflowsForWorker()
database API. This plumbs down the context from the API call into thed.instance.QueryContext()
call.WorkerWorkflow
with the methods that get used by APIs the Tink Worker invokes. This is essentially a no-op for now.Why is this needed
See tinkerbell/proposals#46
How Has This Been Tested?
Locally ran tests.
How are existing users impacted? What migration steps/scripts do we need?
No impact to existing users
Checklist:
I have: