← Back to issue list

Support for manifest generation

View original Github issue

Metadata

Project
imagecraft
Number
#279
Type
issue
State
open
Author
rthill91
Labels
Status: Triaged
Created
Updated
Closed
—

Current evaluation

Feature request to generate a .manifest (and related zsync/signed checksum) artifact from imagecraft builds via a create_manifest option; triaged as IMAGECRAFT-116, no implementation yet.

Suggested action: keep open

Reason: The issue carries the `Status: Triaged` label and an internal ticket IMAGECRAFT-116 was created, so it has been assessed and accepted as a real gap. Searches for `create_manifest` and for manifest-related commits return no matches, confirming the feature is still unimplemented; the only manifest code in the tree is unrelated `seed.manifest` snap revision output in imagecraft/plugins/uc_prepare_plugin.py and snap_preseed_plugin.py. Impact is moderate since CPC builds need it but overlay scripts provide a current workaround, and actionability is capped because the second comment expands scope to zsync metafiles and signed checksums without a design for output path or format.

Evaluated by: mr-cal-bot

Impact: 45 Quick Win: 13 Complexity: 50 Confidence: 78 Actionability: 58

Issue body

### Check existing issues - [x] I've verified that this request isn't described by any existing issues. ### Request I would like to be able to define something like `create_manifest: true` in the imagecraft.yaml and have a manifest generated as a build artifact ### The problem it solves Existing livecd-rootfs builds have support for manifest generation (see [here](https://git.launchpad.net/livecd-rootfs/tree/live-build/functions#n49)). This is a requirement for cpc builds, and being able to do it without the use of overlay scripts would be much clearer.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 45
Quick Win: 13
Complexity: 50
Confidence: 78
Actionability: 58
keep open Feature request to generate a .manifest (and related zsync/signed checksum) artifact from imagecraft builds via a create_manifest option; triaged as IMAGECRAFT-116, no implementation yet.
qwen/qwen3.6-35b-a3b
Impact: 60
Quick Win: 25
Complexity: 40
Confidence: 80
Actionability: 70
keep open Feature request to add manifest generation support (create_manifest config option) for imagecraft builds, needed for CPC builds. Triaged with internal Jira ticket IMAGECRAFT-116.
qwen/qwen3.6-35b-a3b
Impact: 50
Quick Win: 22
Staleness: 45
Complexity: 55
Confidence: 70
Support Request: 10
keep open Feature request to add manifest generation support via create_manifest option in imagecraft.yaml for Ubuntu image builds. Triaged but no implementation started.
qwen/qwen3.8-27b
Impact: 40
Quick Win: 22
Staleness: 58
Complexity: 45
Confidence: 72
Support Request: 5
keep open Feature request to add create_manifest option to imagecraft.yaml for generating a manifest build artifact, required for cpc builds. Triaged (label applied) but no implementation or maintainer discussion since the Jira ticket was created ~5 months ago.
qwen/qwen3.6-35b-a3b
Staleness: 50
Complexity: 45
Confidence: 85
Support Request: 10
keep open Feature request to add manifest generation via create_manifest option in imagecraft.yaml. Triaged and synced to Jira, awaiting implementation.
qwen3.6-35b-a3b-mtp-q6
Staleness: 45
Complexity: 50
Confidence: 85
Support Request: 10
keep open Feature request to add manifest generation via a create_manifest flag in imagecraft.yaml, replacing overlay scripts. Currently triaged and linked to an internal Jira ticket.
qwen3.6-35b-a3b-mtp-q6
Staleness: 60
Complexity: 40
Confidence: 80
Support Request: 5
keep open Feature request to add manifest generation via a create_manifest config option in imagecraft.yaml, required for cpc builds. Currently triaged and linked to an internal Jira ticket.

Update history

Date Change
updated

Related work

  • Related To: charmcraft#279 (confidence 65%)

    Flagged as related: 'Produce a manifest when building charms and bundles' — same manifest-generation concept in a sibling Canonical project, but a different codebase and build flow.

Related issues

No related issues found above the similarity threshold.