ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-10-04 15:34:01 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Adjust booleans in system modules (#5153)

Browse source 
* Adjust booleans in system modules.

* Fix some IP addresses

Co-authored-by: Sandra McCann <samccann@redhat.com>

Co-authored-by: Sandra McCann <samccann@redhat.com>
This commit is contained in:
Felix Fontein 2022-08-24 19:59:01 +02:00 • committed by GitHub
commit be2de15c66
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
39 changed files with 162 additions and 146 deletions
Download patch file Download diff file Expand all files Collapse all files

6
plugins/modules/system/vdo.py
View file

@ -48,7 +48,7 @@ options:
activated:
description:
- The "activate" status for a VDO volume. If this is set
to "no", the VDO volume cannot be started, and it will
to C(false), the VDO volume cannot be started, and it will
not start on system startup. However, on initial
creation, a VDO volume with "activated" set to "off"
will be running, until stopped. This is the default
@ -270,7 +270,7 @@ options:
checks it is important to make sure that all parameters
provided are accurate and intentional."
type: bool
default: no
default: false
version_added: 2.4.0
notes:
- In general, the default thread configuration should be used.
@ -725,7 +725,7 @@ def run_module():
# Note that a disabled VDO volume cannot be started by the
# 'vdo start' command, by design. To accurately track changed
# status, don't try to start a disabled VDO volume.
# If the playbook contains 'activated: yes', assume that
# If the playbook contains 'activated: true', assume that
# the activate_vdo() operation succeeded, as 'vdoactivatestatus'
# will have the activated status prior to the activate_vdo()
# call.