Profile `simple` in `charmcraft init` has an unclear name
Metadata
Current evaluation
Charmcraft 4 removed the unclear simple init profile and made kubernetes the default in PR #2295 (commit fc17daa7).
Resolution: closed resolved
Reason: PR canonical/charmcraft#2295 merged as commit fc17daa7, removing the simple profile and making kubernetes the default for charmcraft init. The closing maintainer comment identifies this PR as the fix.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
`simple` profile could be renamed to point that by default we're creating a Kubernetes charm. Example name I could think of: `basic-kubernetes`.
### Why it needs to get done
Although we know from the `charmcraft --help init` that `simple` is the default profile, we don't know what it creates. The `simple` profile contains almost the same things as `kubernetes` profile (with differences in `simple` having a `config.yaml` and `httpbin` image defined), but it's unclear it is a Kubernetes charm.
cc @tmihoc
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Charmcraft 4 removed the unclear simple init profile and made kubernetes the default in PR #2295 (commit fc17daa7). | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed in Charmcraft 4 by PR #2295 (fc17daa7): the `simple` init profile was removed and `kubernetes` became the default, so no rename is needed. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | The unclear simple profile name in charmcraft init was resolved by removing the profile entirely in Charmcraft 4 via PR 2295. | |
| qwen/qwen3.6-35b-a3b | — | — | The unclear simple profile name in charmcraft init was resolved by removing the profile entirely in Charmcraft 4. The change was merged in PR #2295. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed by removing the unclear simple profile from charmcraft init in Charmcraft 4, implemented in pull request #2295. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | The unclear simple profile naming was resolved by removing the profile entirely in Charmcraft 4. This change was implemented via pull request 2295, eliminating the need for a rename. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#2295
(confidence 100%)
Merged breaking change that replaced the simple init profile with kubernetes.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2295 feat(templates)!: replace simple profile by kubernetes | charmcraft | merged | Merged as fc17daa7: for Charmcraft 4.0 the `simple` init profile was removed and `kubernetes` made the default; httpbin charm moved to the Ops repo examples. | |
| #1128 `charmcraft init`: issues with --profile docs, default profile, and default charm.py links | charmcraft | closed | PR #1158 (commit 5b50d9e6) documented init profiles and replaced the outdated charm.py link; the default Kubernetes profile was left unchanged. | |
| #966 `charmcraft init --help` doesn't list the available profiles | charmcraft | closed | Fixed by merged PR #2311 (commit c24c0f47): charmcraft init help now lists Kubernetes, machine, and supported 12-factor profiles. | |
| #854 Created the profile option for the init command (CRAFT-1317). | charmcraft | merged | Merged PR #854 as commit 21b83fb0, adding an optional charmcraft init profile that defaults to simple and updating its scaffold template for CRAFT-1317. | |
| #859 Added a kubernetes profile to init command (CRAFT-1318). | charmcraft | merged | Merged in canonical/charmcraft#859 (451c399a), adding the Kubernetes init profile and fixing the simple template for CRAFT-1318. | |
| #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). |