`login` command should validate channel names as full channel names
Metadata
Current evaluation
`login --channel` still accepts risk-only names such as `edge`; this precise but unlabelled request remains open with only an automated Jira comment.
Suggested action: needs triage
Reason: LoginCommand currently passes --channel values through as plain strings, and its unit tests explicitly accept "edge", confirming the gap. The report gives a clear expected form and example, but it has no labels or substantive maintainer response beyond an autogenerated Jira-bot comment, so it still needs triage.
Evaluated by: mr-cal-bot
Impact:
40
Quick Win:
26
Complexity:
24
Confidence:
94
Actionability:
84
Issue body
### What needs to get done
Charmhub doesn't validate channel names when requesting permissions, but in the end needs the channel name to be the full name (e.g. `latest/edge` rather than `edge`). `login` should validate this for the user.
### Why it needs to get done
As a complement to https://github.com/canonical/charmcraft/issues/1657
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
40
Quick Win:
26
Complexity:
24
Confidence:
94
Actionability:
84
|
needs triage | `login --channel` still accepts risk-only names such as `edge`; this precise but unlabelled request remains open with only an automated Jira comment. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
13
Complexity:
40
Confidence:
70
Actionability:
70
|
keep open | The `login` command should validate that channel names are full format (e.g. `latest/edge` not `edge`). Currently unvalidated channels may cause issues with Charmhub permissions. | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
19
Staleness:
72
Complexity:
25
Confidence:
75
Support Request:
0
|
keep open | charmcraft login --channel should validate that channel names are full names (e.g. latest/edge) since Charmhub requires them for permission attenuation. Unlabeled, no maintainer activity since a 2024 bot comment; code still lacks the validation. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
20
Confidence:
85
Support Request:
10
|
needs triage | login command lacks validation for full channel names (e.g., latest/edge vs edge). Currently unlabelled and inactive for over a year, awaiting maintainer assessment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
20
Confidence:
70
Support Request:
10
|
needs triage | Feature request to validate full channel names in the login command. Unlabelled, unassigned, and inactive for over 10 months with only an automated bot response. Requires maintainer triage to prioritize. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
90
Complexity:
25
Confidence:
80
Support Request:
10
|
needs triage | The login command lacks validation for channel names, requiring full names like latest/edge instead of short forms. Currently unlabelled, inactive for over a year, and awaiting triage. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/charmcraft#1657
(confidence 100%)
The issue explicitly describes this validation work as a complement to the open login documentation request.
Related issues
No related issues found above the similarity threshold.