Commitment

I confirm that I have read the following resources:

• How to contribute to Qusal
• How Qusal is designed
• How to ask questions The Smart Way
• Writing the perfect question
• Question checklist
• Could you please make my preference the default?

Current problem (if any)

For some scenarios, we might end up with a bunch of mostly duplicated disposable templates only differing by some name/tag/resource reference. For example:

• disp-mail-sender for each outgoing mail account
• disp-sys-net for each network interface
• disp-fetcher for each remote configuration

If there was a channel to dynamically provide the differing configuration at qube start, it would remove the need to also create new vms/templates for each permutation.

Proposed solution

The vm-config looks like a great way to inject the necessary dynamic configuration a la cloud-init.

The value to a user, and who that user might be

User: Easier to spin up and tear down stuff with scoped access with less ceremony.

Developer: Looks like it can be used for some neat patterns and simplify provisioning.