use kube current-context when entering click
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
No repository file or test is named. Start by locating the CLI entry point and the code that initializes click's stored Kubernetes context and namespace, then compare it with kubectl config current-context behavior. Done means entering click uses the current context and its associated namespace instead of requiring duplicate click configuration, while the prompt still reports both values.
Written by the indexing model from the issue text.
Description
Hey, this tool is pretty awesome thanks a lot!
Not sure if this is a sensible suggestion or not, but it feels like a semi-common pattern to have some quick shell helpers to swap kubectl config current-context around for kubectl.
Was wondering if it is possible to have click use my current context (and its associated namespace if set in the context triple) when entering instead of storing it in the click config? It feels a bit overkill to have this info set in two places personally, and it also slightly deceptive to someone who has their kube context on PS1.
If people set contexts carefully to point to specific clusters with specific namespaces, then it's easier to just swap the context outside click than it is to do it interactively. The repl prompt showing the context and the namespace set is a very nice touch though.
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from databricks/click
-
ClickOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
databricks/click#237 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
databricks/click#234 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
databricks/click#233 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
databricks/click#227 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
databricks/click#218 · 7 comments ·
All issues in databricks/click
Similar issues
-
enhancement feature review: low Sonnet ui
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MMFoundation/WallpaperMachine#190 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
servo/rust-smallvec#877 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
cloudflare/workers-rs#1140 ·
Maintainers usually reply within 7 days
-
A-documentation S-needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Quantinuum/hugr#3344 ·
Maintainers usually reply within 1 day
-
P4
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
HerringtonDarkholme/hd-lang#1718 · 1 comment ·
Maintainers usually reply within 1 day