unknown resource error message could be more helpful
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
If you use k8s_resource with a resource name that doesn't exist, you can an error message like this:
specified unknown resource "ml-pipeline-ui:service:kubeflow". known resources: [list of valid resources]
If the resource list is empty, we should have a better error message - it probably means the user has misunderstood how to set up tilt, and needs some pointers to how to register YAML and/or CRDs
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 by tracing k8s_resource handling for the unknown-resource error and the empty known-resource case. Check how YAML and CRDs are registered; done when an empty resource list produces actionable setup pointers while existing error behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100