fix: stop command missing --name flag to specify which instance to stop
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start at the stop command entry point and compare its flags and context resolution with the start command, focusing on ResolveContext(). Verify the command help exposes --name, confirm the name reaches context resolution, and check that stopping a named instance works without the unnecessary empty output.
Written by the indexing model from the issue text.
Description
Why we need this:
The start command supports --name flag to name a Microcks instance
but the stop command has no --name flag. Users cannot specify which
instance to stop when multiple instances exist.
How this will help:
Adding --name flag to stop command makes it consistent with start
command and allows users to stop a specific named instance.
Problem
microcks start --name myinstance ✅ works
microcks stop --name myinstance ❌ flag does not exist
The stop command always resolves the current context instead of
allowing the user to specify which instance to stop by name.
Fix
- Add --name flag to stop command
- Pass name to ResolveContext() so correct instance is stopped
- Remove unnecessary empty fmt.Println() call
- Dominant language
- Go
- Stars
- 52
- Forks
- 67
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 13
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.
More from microcks/microcks-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microcks/microcks-cli#536 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
microcks/microcks-cli#535 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
microcks/microcks-cli#534 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microcks/microcks-cli#511 ·
-
component/cli kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
microcks/microcks-cli#503 · 4 comments ·
All issues in microcks/microcks-cli
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·