From 45d84fd745da4804c2dbd65f6f52f7067559206a Mon Sep 17 00:00:00 2001 From: Justin Cinkelj Date: Mon, 6 Jan 2025 11:12:26 +0100 Subject: [PATCH] Document cloud-init is applied only to newly created VM Fixes #340 Signed-off-by: Justin Cinkelj --- plugins/doc_fragments/cloud_init.py | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/plugins/doc_fragments/cloud_init.py b/plugins/doc_fragments/cloud_init.py index 717ff2c6..23be24aa 100644 --- a/plugins/doc_fragments/cloud_init.py +++ b/plugins/doc_fragments/cloud_init.py @@ -16,8 +16,12 @@ class ModuleDocFragment(object): cloud_init: description: - Configuration to be used by cloud-init (Linux) or cloudbase-init (Windows). - - When non-empty will create an extra ISO device attached to VirDomain as a NoCloud datasource. + - When non-empty will create an extra ISO device attached to VM as a NoCloud datasource. - There has to be cloud-config comment present at the beginning of cloud_init file or raw yaml. + - The cloud-init configuration is applied only during the initial creation of a VM + (whether through provisioning, cloning, or importing). + It is not applied to an existing VM. + This is consistent with the behavior of the HyperCore appliance. required: false type: dict default: {}