Commit 9538870
committed
fix: boolean values and null values are not allowed
Cause: The user could specify a value like `value: on` or `value: yes` thinking that these would
be converted to the string `"on"` or `"yes"`. But instead, YAML treats these
as [YAML bool type](https://yaml.org/type/bool.html) and writes them as the string `"True"`.
Consequence: The user who is unaware of YAML boolean handling is not able to set
values to `"on"`, `"off"`, or the like.
Fix: The role will reject any value of boolean or `null` type.
Result: Users must quote such YAML boolean type values as strings in order to write
them to the bootloader configuration.
Signed-off-by: Rich Megginson <rmeggins@redhat.com>1 parent c672ee7 commit 9538870
2 files changed
+24
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
77 | 77 | | |
78 | 78 | | |
79 | 79 | | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
80 | 86 | | |
81 | 87 | | |
82 | 88 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
10 | 10 | | |
11 | 11 | | |
12 | 12 | | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
13 | 31 | | |
14 | 32 | | |
15 | 33 | | |
| |||
0 commit comments