← Back to issue list

Automatically update template operator based on latest charmcraft init

View original Github issue

Metadata

Project
charmcraft
Number
#828
Type
issue
State
closed
Author
jdkandersson
Labels
—
Created
Updated
Closed

Current evaluation

Declined and closed. Maintainer facundobatista rejected the request to auto-sync template-operator with `charmcraft init`, saying the templates are intentionally independent and init profiles may replace the need.

Resolution: closed not a bug

Reason: No code change was made: facundobatista explicitly rejected the proposal on 2022-08-22, citing template-operator's independent evolution, upcoming `charmcraft init` profiles (added in PR #854, commit 21b83fb0), and unwillingness to add cross-repo automation in charmcraft. He noted the idea may be revisited once profiles are widely used.

Evaluated by: mr-cal-bot

No scores available.

Issue body

There is a GitHub repo (https://github.com/canonical/template-operator) used as a template for many teams when starting new charms. For any changes to the default/ recommended starting point of charms, both the `charmcraft init` command and the template-operator repo have to be updated. This could potentially be improved by unifying the two, for example by include a GitHub action on this repository to automatically send a commit to the template-operator based on the latest output of `charmcraft init`.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed not a bug Declined and closed. Maintainer facundobatista rejected the request to auto-sync template-operator with `charmcraft init`, saying the templates are intentionally independent and init profiles may replace the need.
stealth/space-bunny-alpha — closed not a bug Rejected and closed without implementation. facundobatista declined syncing template-operator automatically with charmcraft init, citing independent templates, planned init profiles, and reluctance to add cross-repository automation.
qwen3.6-35b-a3b-mtp-q6 — — Rejected and closed. Maintainer declined automatic template updates due to upcoming charmcraft init profiles, potential divergence, and policy against cross-repo automation. May revisit once profiles are widely adopted.
qwen/qwen3.6-35b-a3b — — Rejected. Maintainers declined automating updates between charmcraft init and template-operator due to upcoming init profiles, architectural divergence, and cross-repo automation policies. The idea may be revisited later.
qwen3.6-35b-a3b-mtp-q6 — — Rejected and closed. Maintainer declined automating sync between charmcraft init and template-operator due to upcoming charmcraft profiles, architectural divergence, and cross-repo automation policy. May revisit later.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/charmcraft#854 (confidence 80%)

    Merged PR adding the `charmcraft init` profile option (commit 21b83fb0), the feature the maintainer cited as a reason to defer the request.

  • Related To: canonical/charmcraft#2295 (confidence 40%)

    Later replacement of the `simple` profile with `kubernetes`, showing the init template set changed independently of template-operator.

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.
71%