← Back to issue list

snapcraft doesn't validate plugs: values

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1697468
Type
issue
State
open
Author
~msweet
Labels
Created
Updated
Closed

Current evaluation

Request to add whitespace validation for plugs values in snapcraft.yaml (e.g. 'home x11' instead of 'home, x11'). Filed ~2015 during the build.snapcraft.io era, zero comments, no labels, no maintainer interaction in 9+ years.

Suggested action: close stale

Reason: The issue is 3367 days old with zero comments, no labels, and no maintainer interaction. It references build.snapcraft.io, which no longer exists, and the snapcraft codebase has been completely rewritten multiple times since then (now using craft-cli and pydantic-based models in snapcraft/models/). The original problem context is no longer applicable, though the underlying validation concern could theoretically still be relevant to the current validation framework.

Impact: 20 Quick Win: 16.0 Staleness: 95 Complexity: 20 Confidence: 40 Support Request: 10

Issue body

I'm in the process of creating a snap for HTMLDOC via build.snapcraft.io. However, after successfully building the snap the bot was unable to publish it due to an error in my plugs: definition, which read: plugs: [home x11] Now, this was a simple typo (missing comma), but since snapcraft didn't catch it and the build bot was unable to report the cause of the publishing error, it took me a while to determine what was wrong and correct the situation. A simple fix here might be to check that the strings do not contain whitespace, and if so log that as an error with a recommendation to add commas to delimit the interfaces.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 20
Quick Win: 16.0
Staleness: 95
Complexity: 20
Confidence: 40
Support Request: 10
close stale Request to add whitespace validation for plugs values in snapcraft.yaml (e.g. 'home x11' instead of 'home, x11'). Filed ~2015 during the build.snapcraft.io era, zero comments, no labels, no maintainer interaction in 9+ years.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 20
Confidence: 95
Support Request: 10
close stale Snapcraft fails to validate plugs list syntax, allowing typos like missing commas to pass parsing but fail at publishing. Unaddressed for over 9 years.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 15
Confidence: 90
Support Request: 10
close stale Feature request to validate snapcraft plugs definitions and catch missing commas. Currently inactive for over 9 years with no maintainer response or labels.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 10
Confidence: 85
Support Request: 10
needs triage Request to add validation for snapcraft plugs definitions to catch typos like missing commas. Issue is over 9 years old with no maintainer response or labels.
qwen3.6-35b-moe-q4
Staleness: 98
Complexity: 20
Confidence: 92
Support Request: 10
close stale Report that snapcraft fails to validate whitespace in plugs definitions, causing cryptic publishing errors. Suggests adding validation to catch missing commas. Issue is inactive for ~9 years with no maintainer response.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1617302 Specifying a nonexistent plug does cause any errors snapcraft (launchpad) open Feature request from 2016: snapcraft should error or warn when a nonexistent plug name is specified in snapcraft.yaml (e.g. misspelling network-bind). No labels, no comments, no maintainer interaction in 10 years.
72%
#1640897 snapcraft doesn't validate gadget.yaml snapcraft (launchpad) open Feature request from 2015 asking snapcraft to validate gadget.yaml metadata for gadget snaps instead of just copying it. Open for nearly 10 years with no labels, comments, or maintainer activity.
72%