← Back to issue list

`login` command should validate channel names as full channel names

View original Github issue

Metadata

Project
charmcraft
Number
#1658
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

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.

Suggested action: keep open

Reason: Verified at pinned HEAD that LoginCommand.run() in charmcraft/application/commands/store.py still forwards parsed_args.channel to store.get_credentials()/login() with no full-channel-name validation, so the request remains applicable rather than obsolete. The author is a maintainer (lengau) who filed it as a scoped task and it complements open issue #1657, so it warrants keeping open despite 381 days of inactivity and the only comment being the 2024-04-18 Jira-sync bot message.

Impact: 25 Quick Win: 18.75 Staleness: 72 Complexity: 25 Confidence: 75 Support Request: 0

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
qwen/qwen3.8-27b
Impact: 25
Quick Win: 18.75
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 80
Complexity: 20
Confidence: 80
Support Request: 5
needs triage Validate channel names as full format in the login command before requesting permissions. Open and awaiting implementation, synced to Jira. Last updated 304 days ago.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/charmcraft#1657 (confidence 85%)

    Explicitly referenced in the issue body as a complement (documenting login permissions/channels); still open and unlabelled.

Related issues

No related issues found above the similarity threshold.