Skip to content

Document cloud-init is applied only to newly created VM #347

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
justinc1 merged 1 commit into from
Jan 8, 2025
Merged

Document cloud-init is applied only to newly created VM #347

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion plugins/doc_fragments/cloud_init.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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: {}
Expand Down
Loading