KubeVirt Collection for Ansible Release Notes
+KubeVirt Collection for Ansible Release Notes
This changelog describes changes after version 1.0.0.
v1.3.2
+v1.3.2
Release Summary
+Release Summary
No functional changes, hotfix release to retrigger the downstream build and to keep in sync with Ansible Automation Hub.
Minor Changes
+Minor Changes
Bugfixes
+Bugfixes
fix(kubevirt_vm): Set wait_condition based on running #89
v1.3.1
-Release Summary
+v1.3.1
+Release Summary
No functional changes, only updates to the shipped documentation.
v1.3.0
-Minor Changes
+v1.3.0
+Minor Changes
Bugfixes
+Bugfixes
v1.2.3
-Release Summary
+v1.2.3
+Release Summary
No functional changes, hotfix release to retrigger the downstream build and to keep in sync with Ansible Automation Hub.
v1.2.2
-Release Summary
+v1.2.2
+Release Summary
No functional changes, only cleanup of files included in the release tarball and vendoring of documentation fragments.
v1.2.1
-Release Summary
+v1.2.1
+Release Summary
Mostly code cleanups and dependency updates to ensure compatibility with KubeVirt >= 1.1.0
v1.2.0
-Release Summary
+v1.2.0
+Release Summary
Not released due to issues in the release process
v1.1.0
-Minor Changes
+v1.1.0
+Minor Changes
Add kubevirt_vm_info module to describe existing VirtualMachines
inventory: Allow to control creation of additional groups
@@ -273,9 +274,9 @@
v1.0.0
-Release Summary
+v1.0.0
+Release Summary
Initial release
Specify whether the VirtualMachine should be running.
+This affects the ready condition to wait for.
+This requires wait and is only used when wait=yes.
Choices:
+-
+
false
+ true
+
username
@@ -430,7 +452,7 @@ ParametersPlease note that this only works with clusters configured to use HTTP Basic Auth. If your cluster has a different form of authentication (e.g. OAuth2 in OpenShift), this option will not work as expected and you should look into the community.okd.k8s_auth module, as that might do what you need.
wait
@@ -462,15 +484,17 @@ ParametersWhether to wait for the VirtualMachine to end up in the ready state.
+By default this is waiting for the VirtualMachine to be up and running.
+Modify this behavior by setting running.
Choices:
-
-
false← (default)
+ falsetrue
wait_sleep
@@ -485,7 +509,7 @@ ParametersDefault: 5
wait_timeout
@@ -547,12 +571,19 @@ Examples label_selectors: - app=test - - name: Wait until the VirtualMachine is Ready + - name: Wait until the VirtualMachine is running kubevirt.core.kubevirt_vm_info: name: testvm namespace: default wait: true + - name: Wait until the VirtualMachine is stopped + kubevirt.core.kubevirt_vm_info: + name: testvm + namespace: default + running: false + wait: true + @@ -599,7 +630,7 @@ Common return values are documented :ref:`hereThe VirtualMachine(s) that exists
+The VirtualMachine(s) that exist(s)
Returned: success
Specify whether the VirtualMachine should be running.
+This affects the ready condition to wait for.
+This requires wait and is only used when wait=yes.
Choices:
+-
+
false
+ true
+
username
@@ -496,7 +518,7 @@ see +wait_sleep
@@ -551,7 +575,7 @@ see Default:5
The VirtualMachine(s) that exists
+The VirtualMachine(s) that exist(s)
Returned: success