← Back to issue list

Allow use actions/config/metadata in charmcraft.yaml

View original Github issue

Metadata

Project
charmcraft
Number
#1126
Type
pull request
State
merged
Author
syu-w
Labels
—
Created
Updated
Closed

Current evaluation

Merged in canonical/charmcraft#1126 (044b94f8), adding inline actions, config, and ST087-compliant metadata support when standalone YAML files are absent.

Resolution: closed resolved

Reason: The approved PR was merged as commit 044b94f8, implementing the requested inline charmcraft.yaml support.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Allow use actions/config/metadata in `charmcraft.yaml` when corresponding yaml file does not exist. Metadata in `charmcraft.yaml` also must be new keys defined in spec ST087. CRAFT-1747 CRAFT-1788 CRAFT-1789

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Merged in canonical/charmcraft#1126 (044b94f8), adding inline actions, config, and ST087-compliant metadata support when standalone YAML files are absent.
stealth/space-bunny-alpha — closed resolved Merged PR #1126 (commit 044b94f8) added support for actions, config, and ST087-compliant metadata directly in charmcraft.yaml when separate files are absent.
stealth/space-bunny-alpha — closed resolved Merged in canonical/charmcraft#1126 (044b94f8), adding support for actions, config, and ST087-compliant metadata in charmcraft.yaml when separate YAML files are absent.
qwen/qwen3.6-35b-a3b — — Merged. Allows defining actions, config, and metadata directly in charmcraft.yaml when corresponding files are absent. Addresses CRAFT-1747, CRAFT-1788, and CRAFT-1789. Approved with passing CI checks.
qwen3.6-35b-a3b-mtp-q6 — — Merged. Enables defining actions, config, and metadata directly in charmcraft.yaml when corresponding files are absent, per spec ST087. Resolves CRAFT-1747, CRAFT-1788, and CRAFT-1789.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/charmcraft#1114 (confidence 90%)

    Earlier merged PR added initial actions support in charmcraft.yaml.

  • Related To: canonical/charmcraft#1149 (confidence 85%)

    Follow-up PR updated charmcraft init to generate a unified charmcraft.yaml.

Related issues

Issue Project State Summary Similarity
#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.
80%
#1114 config: support use actions in charmcraft.yaml charmcraft merged Merged #1114 as commit 201b40f6, enabling actions in charmcraft.yaml and refactoring configuration models to avoid circular imports.
79%
#2874 feat: mediate creation of metadata.yaml charmcraft merged PR #2874 merged to charmcraft main (2 approvals): implements craft-application's package service API so metadata.yaml creation is mediated in Charm/rock layers, tracking CHARMCRAFT-723.
72%
#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.
72%
#2856 Implement metadata mediation for metadata.yaml charmcraft closed Fixed by merged charmcraft PR #2874, which added a craft-application package service to mediate metadata.yaml creation.
72%
#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.
71%
#644 Request: be able to specify the location of metadata.yaml (and the rest of the charm code) charmcraft closed Resolved in Charmcraft 3.0 by merged PR canonical/charmcraft#1524 (commit 9988b7db), preserving metadata.yaml generated by the charm tool for reactive charms.
70%