← Back to issue list

Fallback once to `snap download` if snap not found in global store

View original Github issue

Metadata

Project
craft-parts
Number
#1490
Type
issue
State
open
Author
soumyaDghosh
Labels
—
Created
Updated
Closed
—

Current evaluation

Private or dedicated-store build snaps are unsupported when absent from the global store; a one-time `snap download` fallback is requested. The issue has no labels, comments, or maintainer triage.

Suggested action: needs triage

Reason: The current `install_snaps` path calls `get_store_snap_info()` and only proceeds to `snap install` when store data is present, while `SnapPackage.download()` exists separately; the request identifies a concrete gap for authenticated dedicated stores. However, the issue has no labels, comments, or maintainer response, and provides no reproducer or precise specification for installing the downloaded artifact, so it needs triage before implementation.

Evaluated by: mr-cal-bot

Impact: 48 Quick Win: 14 Complexity: 55 Confidence: 86 Actionability: 64

Issue body

### What needs to get done `snap install` can only install snaps from the global store, but if the snap is not listed in the global store, then a retry should be done with `snap download`, because the snap might be in a dedicated snap store, and those credentials might be set in the environment. If the command returns `snap not found` then, the credentials are not at all set. If it returns 404, then the store url is set, but the snap is not accessible with the given credential. ### Why it needs to get done This will help for private snap development process or cases, where the snap is not in the global store, or are even set as private. The current setup, makes it necessary to make a snap public to be able to use it.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 48
Quick Win: 14
Complexity: 55
Confidence: 86
Actionability: 64
needs triage Private or dedicated-store build snaps are unsupported when absent from the global store; a one-time `snap download` fallback is requested. The issue has no labels, comments, or maintainer triage.
stealth/space-bunny-alpha
Impact: 46
Quick Win: 9
Complexity: 60
Confidence: 88
Actionability: 48
needs triage Private or dedicated-store build snaps remain unsupported because install_snaps only handles snaps found through snapd, and the proposed download fallback is untriaged.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 13
Complexity: 40
Confidence: 70
Actionability: 70
needs triage Feature request to add fallback from snap install to snap download for private snap store support
qwen/qwen3.8-27b
Impact: 35
Quick Win: 19
Staleness: 55
Complexity: 45
Confidence: 80
Support Request: 20
needs triage Feature request to make craft-parts fall back to `snap download` when `snap install` fails because a snap is not in the global store, enabling private/dedicated snap stores. Unlabelled, zero comments, no maintainer response in ~6 months; code in craft_parts/packages/snaps.py still has no such fallback.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 45
Confidence: 85
Support Request: 10
needs triage Feature request to add fallback to snap download when snap install fails to find a snap in the global store, enabling private store usage. Currently unlabelled and inactive for 136 days.
qwen3.6-35b-a3b-mtp-q6
Staleness: 55
Complexity: 45
Confidence: 90
Support Request: 10
needs triage Proposal to add a fallback mechanism to snap install that tries snap download when a snap isn't found in the global store, enabling private snap store support. Currently unlabelled and inactive for 123 days.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft (launchpad)#1802327 (confidence 82%)

    Open Launchpad bug reports the related inability to use private or alternate-store snaps as build or stage dependencies.

Related issues

No related issues found above the similarity threshold.