feat: implement proper context in scope methods #1575
+42
−44
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.
/kind feature
What this PR does / why we need it:
As discussed in #1506 (comment) there's no proper context in place for scope methods and using
context.TODO()is not a valid solution as it's only expected to be used temporarily, for testing or in non-production projects. Effectively this is simply a workaround for passing a nil value to functions that require a context object but it just won't ever timeout.This PR tries to implement proper context to scope methods. I think I updated all of them, but feel free to call me out on any missing occurrences of
context.TODO().Which issue(s) this PR fixes:
Fixes #1573
Special notes for your reviewer:
No changes are applied to testing files where
context.TODO()is still used and should be considered a valid solution for simpler context management.TODOs:
Release note: