some commands, like clean, should not need schema validation

Metadata

Project: rockcraft
Number: #613
Type: issue
State: open
Author: cjdcordeiro
Labels: —
Created: 2024-06-25 10:50 AM UTC
Updated: 2024-06-25 11:38 AM UTC
Closed: —

Current evaluation

Rockcraft clean command requires full rockcraft.yaml schema validation, preventing cleanup when the config contains unsupported fields. Maintainer acknowledged the issue but noted name/platforms/base are needed to identify instances to clean. No fix implemented; issue inactive for ~2 years.

Suggested action: keep open

Reason: The issue was acknowledged by a maintainer (tigarmo) who agreed in principle but clarified that name, platforms, and base fields are required to identify which instances to clean, meaning the original example was flawed. The author agreed and updated the description. However, no fix has been implemented and the issue has been inactive for ~797 days. The clean command is now provided by craft-application upstream, so any fix would need to happen there. The issue remains a valid UX concern (clean should work with minimal valid config) but is low priority given the 2-year inactivity and the complexity of relaxing validation while preserving instance identification.

Impact: 35 Quick Win: 21.0 Staleness: 85 Complexity: 40 Confidence: 70 Support Request: 10

Issue body

### Bug Description Some commands, like clean, should not need such a strict schema validation, if all they gonna do is “clean”. IoW, if I want to `clean` my project, the YAML shouldn't have an impact on the operation. ### To Reproduce Write a bogus rockcraft.yaml and run `rockcraft clean`. ### Environment Any ### rockcraft.yaml ```shell name: my-rock base: ubuntu@22.04 # the base environment for this rock version: '0.1' # just for humans. Semantic versioning is recommended summary: Single-line elevator pitch for your amazing rock # 79 char long summary description: | This is my-rock-name's description. You have a paragraph or two to tell the most important story about it. Keep it under 100 words though, we live in tweetspace and your description wants to look good in the container registries out there. platforms: # the platforms this rock should be built on and run on amd64: some-unsupported-field: foo parts: my-part: plugin: nil ``` ### Relevant log output ```shell Bad rockcraft.yaml content: - extra field 'some-unsupported-field' not permitted in top-level configuration For more information, check out: https://documentation.ubuntu.com/rockcraft/en/stable/reference/rockcraft.yaml ```

Evaluation history

Date	Model	Scores	Action	Summary
2026-09-01 01:52 AM UTC	qwen/qwen3.8-27b	Impact: 35 Quick Win: 21.0 Staleness: 85 Complexity: 40 Confidence: 70 Support Request: 10	keep open	Rockcraft clean command requires full rockcraft.yaml schema validation, preventing cleanup when the config contains unsupported fields. Maintainer acknowledged the issue but noted name/platforms/base are needed to identify instances to clean. No fix implemented; issue inactive for ~2 years.
2026-07-22 12:09 PM UTC	qwen/qwen3.6-35b-a3b	Staleness: 85 Complexity: 20 Confidence: 70 Support Request: 10	close stale	Request to bypass strict schema validation for the clean command when rockcraft.yaml contains unsupported fields. Currently open, last discussed over two years ago with the author acknowledging a counterpoint about required tracking fields.
2026-07-08 06:49 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 85 Complexity: 20 Confidence: 60 Support Request: 10	needs triage	Requests relaxing schema validation for the clean command to bypass strict rockcraft.yaml checks. Open for two years without labels, assignee, or official triage after the author acknowledged a reviewer's feedback.
2026-07-05 09:53 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 90 Complexity: 15 Confidence: 75 Support Request: 5	needs triage	Maintainer requests bypassing strict schema validation for commands like clean. Discussion notes some fields are still needed for instance tracking. Issue remains unlabelled and unassigned after two years.
2026-06-16 11:40 AM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 85 Complexity: 30 Confidence: 70 Support Request: 10	close stale	Bypass strict schema validation for commands like clean that do not rely on config content. Maintainers note name and base fields are required for instance tracking. Author acknowledges and is updating the description. Under discussion.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.