← Back to issue list

Approach for using store commands programmatically

View original Github issue

Metadata

Project
charmcraft
Number
#183
Type
issue
State
closed
Author
jamesbeedy
Labels
—
Created
Updated
Closed

Current evaluation

Programmatic store authentication landed with login export and CHARMCRAFT_AUTH support; maintainers confirmed the core feature, while JSON output remained unplanned when the request closed.

Resolution: closed resolved

Reason: Facundobatista confirmed on 2022-02-23 that CHARMCRAFT_AUTH had landed, enabling scripted remote authentication. His 2022-03-03 follow-up said JSON output had no current plans, leaving only that separate automation concern unresolved.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Hello, We are trying to create some release infrastructure to help us automate releasing charms to the store. Is anyone currently using store commands programmatically? It seems we currently need to auth against the ubuntu one from the browser. Is there a way to do this without a human? Thanks

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Programmatic store authentication landed with login export and CHARMCRAFT_AUTH support; maintainers confirmed the core feature, while JSON output remained unplanned when the request closed.
stealth/space-bunny-alpha — closed resolved Programmatic Charmhub auth landed in canonical/charmcraft#43 via login --with and CHARMCRAFT_AUTH, enabling unattended store use; JSON output remained unimplemented.
stealth/space-bunny-alpha — closed resolved Programmatic Charmhub authentication was delivered via CHARMCRAFT_AUTH, enabling unattended CI store commands without browser login; proposed JSON output remained unimplemented.
stealth/space-bunny-alpha — closed resolved Programmatic Charmhub authentication shipped via login --export and CHARMCRAFT_AUTH in Charmcraft 1.5 (PR #602, commit f0e57248); JSON output remained unimplemented.
stealth/space-bunny-alpha — closed resolved Programmatic authentication shipped in Charmcraft 1.3 via CHARMCRAFT_AUTH and login --export; JSON output remained outstanding when #183 closed.
stealth/space-bunny-alpha — closed resolved Programmatic store authentication was delivered through CHARMCRAFT_AUTH; structured JSON output remained unimplemented when canonical/charmcraft#183 closed.
stealth/space-bunny-alpha — closed resolved Programmatic store authentication landed via CHARMCRAFT_AUTH in PR #43. JSON output for scripted status and error handling remained unimplemented.
qwen3.6-35b-a3b-mtp-q6 — — Resolved by implementing CHARMCRAFT_AUTH environment variable support for token-based programmatic authentication. JSON output for scripting remains unimplemented. Issue closed.
qwen/qwen3.6-35b-a3b — — Closed after implementing programmatic authentication via the CHARMCRAFT_AUTH environment variable. JSON output for scripting was deferred as a future priority.
qwen/qwen3.6-35b-a3b — — Programmatic authentication was resolved by implementing the CHARMCRAFT_AUTH environment variable, enabling headless CI/CD workflows. JSON output for scripting was deferred. The issue closed after the auth feature landed.
qwen3.6-35b-a3b-mtp-q6 — — Resolved by implementing CHARMCRAFT_AUTH for token-based programmatic authentication. JSON output for scripting was deferred. The core automation requirement was addressed.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: charmcraft#602 (confidence 96%)

    Added login --export for obtaining reusable credentials.

  • Related To: charmcraft#609 (confidence 88%)

    Merged alternate-auth handling, including disabling interactive login when alternate credentials are supplied.

Related issues

No related issues found above the similarity threshold.