[stub] check for deletion timestamp in supervisor Kube storage
Open
Nobody has claimed this yet.
priority/undecided
- Dominant language
- Go
- Stars
- 739
- Forks
- 85
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
We should probably fail validation with a not found error if deletion timestamp is not nil.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in internal/crud/crud.go at the linked line and inspect how supervisor Kube storage validation handles deletion timestamps. Confirm the expected not-found error behavior for a non-nil deletion timestamp, then verify the relevant validation behavior with the repository's existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100