Add a `charmcraft init` template for machine charms
Metadata
Current evaluation
Closed without implementation. The request to add a machine charm template to charmcraft init was acknowledged as valuable but remains unaddressed and effectively abandoned.
Suggested action: —
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 |
|---|---|---|---|---|
| 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. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without implementation. The request for a machine charm template in charmcraft init was acknowledged as low-hanging fruit but never addressed. The issue remains abandoned after over four years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #328 charmcraft init produces error charm for machine charms | charmcraft | closed | Closed without resolution. Maintainers acknowledged the core issue persists: charmcraft init still lacks a machine charm template or flag, leaving machine charm workflows unsupported despite claims that metadata changes fixed it. | |
| #2365 Add test configuration templates for charmcraft | charmcraft | closed | Closed without implementation. The request to add test configuration templates for charmcraft via charmcraft --init --profile=test was abandoned, with only an automated Jira sync comment recorded. | |
| #267 init doesn't set a charm status | charmcraft | closed | Init template lacks charm status reporting. Closed with zero comments after over five years, indicating the feature request was abandoned or superseded by newer template versions without implementation. |