Add a `charmcraft init` template for machine charms
Metadata
Current evaluation
The machine-charm init-template request was closed without a linked fix after the March 2022 discussion; later profile work is not tied to its closure.
Resolution: closed stale
Reason: No closing maintainer comment, resolving PR, or commit is linked. The sole 2022 comment noted community interest but no implementation, supporting closure through inactivity.
Evaluated by: mr-cal-bot
No scores available.
Issue body
Currently, `charmcraft init` creates a k8s template for the charms. Pretty much all of our systems run machine charms, and we have to always start from scratch.
What about having also a machine charm template? And a toggle switch: `charmcraft init --vm` or `charmcraft init --k8s`?
(There was a related discussion in https://github.com/canonical/charmcraft/issues/328)
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed stale | The machine-charm init-template request was closed without a linked fix after the March 2022 discussion; later profile work is not tied to its closure. | |
| stealth/space-bunny-alpha | — | closed stale | Closed without an identified resolving change. Later template and profile work added machine support, but no evidence links that work to this request’s closure. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The request to add a machine charm template to charmcraft init was acknowledged as valuable but remains unaddressed and effectively abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation. The request for a machine charm template in charmcraft init received community interest but no pull request or fix was submitted, leaving the feature abandoned. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The request for a machine charm template in charmcraft init received community interest but saw no development progress and was ultimately abandoned. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/charmcraft#328
(confidence 100%)
The issue explicitly identifies #328 as the related earlier discussion about machine charm support.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #762 Dynamically import charmcraft init template | charmcraft | closed | Closed in favor of broader charmcraft init profile work, notably #568; live template-repository fetching was left for future discussion. Profile support later landed through PRs #854, #859 and #868. | |
| #328 charmcraft init produces error charm for machine charms | charmcraft | closed | Machine charms gained a dedicated charmcraft init profile, resolving Kubernetes-only initialization; the change was merged in PR #868 (commit 2ed9033c). | |
| #2167 charmcraft init --profile machine does not produce a valid charmcraft.yaml | charmcraft | closed | Fixed by #2200 (commit c4d43add), which migrated the machine init template from legacy bases syntax to platforms. | |
| #238 `charmcraft init` creates broken charm | charmcraft | closed | Superseded by charmcraft#247, a planned overhaul of init templates and generated tests; #247 later closed without implementing its proposed guard against building incomplete templates. |