mirror of
https://github.com/ansible-collections/community.general.git
synced 2025-07-26 14:41:23 -07:00
More validate module fixes (#39097)
* Fix type bool DOCUMENTATION issues
This commit is contained in:
parent
b533ebe20d
commit
7c4b91844d
118 changed files with 187 additions and 398 deletions
|
@ -52,7 +52,7 @@ options:
|
|||
- Whether to avoid synchronization prior to role reversal
|
||||
required: no
|
||||
default: no
|
||||
choices: [yes, no]
|
||||
type: bool
|
||||
force:
|
||||
description:
|
||||
- Whether to force the role reversal regardless of the online-state of the primary
|
||||
|
|
|
@ -63,9 +63,7 @@ options:
|
|||
- If false, the synchronization will be suspended if the amount of unsynchronized data exceeds the CoW Repository capacity on the secondary
|
||||
and the failures point will be preserved.
|
||||
- "NOTE: This only has impact for newly launched syncs."
|
||||
choices:
|
||||
- yes
|
||||
- no
|
||||
type: bool
|
||||
default: no
|
||||
"""
|
||||
EXAMPLES = """
|
||||
|
|
|
@ -64,12 +64,12 @@ options:
|
|||
- "Only required when the requested state is 'present'. The RAID level of the storage pool to be created."
|
||||
erase_secured_drives:
|
||||
required: false
|
||||
choices: ['true', 'false']
|
||||
type: bool
|
||||
description:
|
||||
- Whether to erase secured disks before adding to storage pool
|
||||
secure_pool:
|
||||
required: false
|
||||
choices: ['true', 'false']
|
||||
type: bool
|
||||
description:
|
||||
- Whether to convert to a secure storage pool. Will only work if all drives in the pool are security capable.
|
||||
reserve_drive_count:
|
||||
|
|
|
@ -65,7 +65,7 @@ options:
|
|||
description:
|
||||
- Defines if a copy pair will be created if it does not exist.
|
||||
- If set to True destination_volume_id and source_volume_id are required.
|
||||
choices: [True, False]
|
||||
type: bool
|
||||
default: True
|
||||
start_stop_copy:
|
||||
description:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue