The charm tool should offer an initial skeleton
Metadata
Current evaluation
Implemented `charmcraft init` to generate an initial charm skeleton via merged PR canonical/charmcraft#91.
Resolution: closed resolved
Reason: The initial charm scaffolder was completed as `charmcraft init` and merged in canonical/charmcraft#91. A maintainer confirmed on 2020-07-28 that the work had landed.
Evaluated by: mr-cal-bot
No scores available.
Issue body
As with many (new) frameworks that expose a lot of functionality, it's is easy to shoot oneself in the foot.
This is something that cannot be prevented, but I think that many 'beginners' mistakes could be prevented by providing some templates on how to realize certain functionality.
E.g. some helping code to create an operator framework 'project' with all links in place, using some templates for e.g. installing a snap, or a deb, or creating an interface to be reused.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Implemented `charmcraft init` to generate an initial charm skeleton via merged PR canonical/charmcraft#91. | |
| stealth/space-bunny-alpha | — | closed resolved | Resolved by merged PR canonical/charmcraft#91 (commit 0ebd9f87, merge 12ceda1e) adding `charmcraft init`, which scaffolds the charm skeleton (config.yaml, metadata.yaml, src/charm.py). Closed 2020-07-28 by facundobatista. | |
| stealth/space-bunny-alpha | — | closed resolved | Resolved by merged PR canonical/charmcraft#91 (commit 0ebd9f87, merge 12ceda1e) adding `charmcraft init`, which scaffolds the charm skeleton (config.yaml, metadata.yaml, src/charm.py). Closed 2020-07-28 by facundobatista. | |
| stealth/space-bunny-alpha | — | closed resolved | Implemented Charmcraft’s initial charm scaffolder, `charmcraft init`, through merged PR canonical/charmcraft#91; further improvements were deferred to new issues. | |
| qwen/qwen3.6-35b-a3b | — | — | Requested skeleton generator for charm projects was implemented and landed in the charm tool. Closed as completed, with future enhancements tracked separately. | |
| qwen/qwen3.6-35b-a3b | — | — | Implemented. The charm tool now provides skeleton templates and initialization commands for new projects. Work has already landed, and users should file new issues for further enhancements. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed. The requested skeleton generator and project templates were implemented in the charm tool, specifically charmcraft. Users can now initialize new charm projects with standard files and configurations. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Implemented. The requested skeleton generation feature has landed via charmcraft, enabling project initialization with templates. The issue is closed. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#91
(confidence 100%)
Merged PR that implemented the initial charm scaffolder requested here.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1 Charmcraft tool base skeleton | charmcraft | merged | Merged PR #1 as commit 1acba721, introducing Charmcraft’s initial CLI skeleton with extensible commands, routing, logging, and error/exit-code handling. | |
| #91 First pass at 'charmcraft init' | charmcraft | merged | Merged PR #91 delivered the first non-interactive charmcraft init scaffolding implementation; README improvements, extra options, and prompts were deferred (commit 0ebd9f87). | |
| #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. |