← Back to issue list

Please support custom cloud-init config for Multipass VMs

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1818017
Type
issue
State
open
Author
~brlin
Labels
—
Created
Updated
Closed
—

Current evaluation

Request to merge user cloud-init settings into new Multipass build VMs; remains open, unlabelled, and untriaged, with implementation now likely owned by craft-providers.

Suggested action: needs triage

Reason: The body provides a concrete apt mirror/proposed-suite example and explicitly requests merging configuration before Multipass initialization, making this a valid capability request. It has no labels, assignee, or maintainer comments, and current code delegates Multipass handling to craft-providers without a cloud-init configuration path, leaving ownership, user interface, and merge semantics unresolved.

Evaluated by: mr-cal-bot

Impact: 48 Quick Win: 8 Complexity: 70 Confidence: 82 Actionability: 54

Issue body

This feature request is a possible solution to Bug #1818016, as user can, for example, set: ```yaml #cloud-config apt:     disable_suites: $RELEASE-proposed     primary:     - arches: [default]         uri: http://my.favorite.ubuntu.mirror/ubuntu/ ``` It would be great if Snapcraft is able to merge the custom config before initializing the multipass VM.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 48
Quick Win: 8
Complexity: 70
Confidence: 82
Actionability: 54
needs triage Request to merge user cloud-init settings into new Multipass build VMs; remains open, unlabelled, and untriaged, with implementation now likely owned by craft-providers.
stealth/space-bunny-alpha
Impact: 38
Quick Win: 10
Complexity: 62
Confidence: 87
Actionability: 66
needs triage Custom cloud-init configuration for Multipass remains unlabelled and untriaged; provider ownership and YAML merge semantics need clarification after the craft-providers migration.
qwen/qwen3.8-27b
Impact: 30
Quick Win: 14
Staleness: 95
Complexity: 55
Confidence: 55
Support Request: 15
needs triage Feature request to let snapcraft merge a user-supplied cloud-init config (e.g. custom apt mirror / disable-proposed) before initializing its Multipass VM. Open ~7.5 years with no labels, comments, or maintainer engagement; proposed as a workaround for Launchpad bug 1818016.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 40
Confidence: 90
Support Request: 5
close stale Feature request to allow custom cloud-init configuration for Snapcraft's Multipass VMs. The issue has been open for over 7 years with no maintainer comments, labels, or activity, and remains unaddressed.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 30
Confidence: 90
Support Request: 10
close stale Feature request to pass custom cloud-init configuration to Multipass VMs in Snapcraft. Open for over seven years with no maintainer comments, labels, or activity.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 20
Confidence: 85
Support Request: 0
close stale Feature request to allow custom cloud-init configuration for Multipass VMs in Snapcraft. Unlabelled, zero comments, and inactive for over 7 years.

Update history

Date Change
created

Related work

  • Related To: snapcraft (launchpad)#1818016 (confidence 95%)

    The issue body explicitly identifies Bug #1818016 as the motivating problem, although the tracker lookup found no record for further verification.

  • Related To: snapcraft#2940 (confidence 88%)

    Snapcraft PR #2940 removed build-provider use of cloud-init, so the intended integration point must be reassessed.

Related issues

No related issues found above the similarity threshold.