config: support use actions in charmcraft.yaml
Metadata
Current evaluation
Merged #1114 as commit 201b40f6, enabling actions in charmcraft.yaml and refactoring configuration models to avoid circular imports.
Resolution: closed resolved
Reason: PR #1114 was approved and merged, with resolving commit 201b40f6. The change added inline action definitions to charmcraft.yaml and the related import refactor.
Evaluated by: mr-cal-bot
No scores available.
Issue body
This allow we define actions in the same file rather than separated actions.yaml.
This also included some refactor to avoid circular imports.
CRAFT-1746
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #1114 as commit 201b40f6, enabling actions in charmcraft.yaml and refactoring configuration models to avoid circular imports. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged in canonical/charmcraft#1114 (201b40f6), enabling actions in charmcraft.yaml and refactoring to avoid circular imports. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged update allowing actions in charmcraft.yaml instead of separate actions.yaml. Includes refactoring to fix circular imports. Approved by one reviewer across 10 files with 345 additions and 3 deletions. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged, allowing actions to be defined directly in charmcraft.yaml instead of a separate actions.yaml file. Includes refactoring to eliminate circular imports. Resolves CRAFT-1746. |
Update history
No update history recorded yet.
Related work
-
Related To:
charmcraft#1126
(confidence 90%)
Follow-up #1126, merged as 044b94f8, broadened inline support to actions, config, and metadata when standalone YAML files are absent.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #36 'charmcraft build' should pull in actions.yaml and config.yaml | charmcraft | merged | Merged PR #36 as commit a8cdb744, making charmcraft build automatically include actions.yaml and config.yaml in charm builds. | |
| #1126 Allow use actions/config/metadata in charmcraft.yaml | charmcraft | merged | Merged in canonical/charmcraft#1126 (044b94f8), adding inline actions, config, and ST087-compliant metadata support when standalone YAML files are absent. | |
| #35 charmcraft doesn't support actions | charmcraft | closed | Reported that charmcraft builds omitted actions.yaml, so charms with actions failed on install with 'CharmEvents' has no attribute. Fixed by merged PR #36 (commit a8cdb744), which makes 'charmcraft build' copy actions.yaml and config.yaml into the charm. | |
| #763 charmcraft V1.5.0 and V1.6.0 not bundling up bash actions | charmcraft | closed | Reported that charmcraft 1.5.0/1.6.0 omitted the charm's `actions` directory from built charms. Maintainer facundobatista closed it as a duplicate of #764, which was fixed by merged PR #768 (commit 5ada563c). | |
| #31 feat: charmcraft actions | craft-actions | merged | Merged in commit 91513c1, adding charmcraft/setup to install Charmcraft and LXD and charmcraft/pack to run setup and package charms. | |
| #1122 config: make metadata.yaml file optional | charmcraft | closed | Closed unmerged and superseded by #1126, merged as 044b94f8 to support actions, config, and metadata directly in charmcraft.yaml when separate YAML files are absent. | |
| #768 Include an 'actions' dir if present. | charmcraft | merged | Merged PR #768 (commit 5ada563c) to include an existing actions directory in packaged charms by default, fixing #764. | |
| #1829 fix(reactive): don't overwrite actions.yaml for reactive charms | charmcraft | merged | Merged #1829 as commit 4a3cbacb, fixing #1816 by preserving reactive charms' existing actions.yaml instead of overwriting it. | |
| #1149 command: charmcraft init to use charmcraft.yaml only | charmcraft | merged | Merged in ca4df024: charmcraft init now generates a unified charmcraft.yaml containing metadata, actions, and config, with profile descriptions and an updated URL. |