feat: support "--platform" for "clean"
Metadata
Current evaluation
Merged PR #483 via commit 07e89deb, adding --platform to clean so one managed instance can be removed, and fixing craft-application#425.
Resolution: closed resolved
Reason: PR #483 was approved and merged into the main branch. Commit 07e89deb implements platform-selective cleanup and explicitly fixes craft-application#425.
Evaluated by: mr-cal-bot
No scores available.
Issue body
This brings 'clean' closer to parity with the other lifecycle commands, and is useful for cases where we want to wipe one of the managed instances, but not all of them.
Fixes #425
- [ ] Have you followed the guidelines for contributing?
- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [ ] Have you successfully run `tox`?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #483 via commit 07e89deb, adding --platform to clean so one managed instance can be removed, and fixing craft-application#425. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged support for clean --platform, enabling cleanup of one managed instance without removing all instances; fixes #425. | |
| qwen/qwen3.6-35b-a3b | — | — | Added --platform flag to the clean command for targeted instance cleanup. Merged after three approvals and passing CI, resolving issue #425. Changes modify three files with 52 additions. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
craft-application#425
(confidence 100%)
The original clean command issue is explicitly referenced by the merged PR.
-
Related To:
canonical/charmcraft#2078
(confidence 85%)
The follow-up reported remaining gaps in clean platform coverage.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #83 Support "platforms" for the build plans | craft-application | closed | Platform support for build plans was merged in craft-application#86 (commit e494797a), adding platform-name selection/filtering and closing #83. | |
| #601 feat: use platform name in build instance name | craft-application | merged | Merged in canonical/craft-application#601 as 5ae7f878: build instance names now use the platform, preventing environment reuse across platforms and fixing #600. | |
| #365 feat: accept build-for: [all] in platforms | craft-application | merged | Merged PR canonical/craft-application#365 (CRAFT-3016): accepts 'build-for: [all]' in platform definitions, disallowing other platforms when set; closes craft-application#360, related to snapcraft#4854. | |
| #947 feat!(platforms): prevent use of '/' in platform names | craft-application | merged | Merged PR #947 as commit f7f3b1ff, adding validation that rejects platform names containing "/" and fixing #941 (CRAFT-4876). | |
| #84 fix: do not strip base from platform names | craft-platforms | merged | Merged PR #84 via commit 7680af2: shorthand platform names now retain their base, preventing duplicate BuildInfo names required by craft-application. | |
| #2054 feat: support multi-base recipes | charmcraft | merged | PR #2054 by mr-cal merged (commit 1ad02d82), adding multi-base recipe support via the `platforms` keyword, dropping base/build-base from project data and passing it unmodified to craft-platforms (CRAFT-3718). |