allow giving the 'uncategorized' resource a label
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
Describe the Feature You Want
A way to put the "uncategorized" resource into a group
e.g., k8s_resource('uncategorized', labels=['mygroup'])
(which might also allow other configuration on the uncategorized resource, e.g. trigger_mode)
Current Behavior
The best alternative is to make a new resource and pull all uncategorized objects into it, e.g.:
k8s_resource(new_name='other', labels=['mygroup'], objects=['secrets:Service:default', 'servantes-stuff:Secret:default'])
Why Do You Want This?
- If you've taken the time to tidily sorted all your resources into groups, it's annoying to have this one "uncategorized" resource sticking out under "unlabeled" like a sore thumb.
- 'uncategorized' has not historically been easy for users to pick up, and we don't provide much help discovering options such as the one listed above under Current Behavior (which hopefully #5417 will help with)
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 from the k8s_resource API and the handling of the automatically created "uncategorized" resource. Check how labels and other resource configuration are currently applied, then review existing tests for resource grouping. Done means users can assign a label to "uncategorized" and the requested configuration behaves consistently with named resources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100