-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
[Epic]: fix: boolean values and null values are not allowed [rhel-9]
-
Low
-
Red Hat Enterprise Linux
-
0% To Do, 0% In Progress, 100% Done
-
rhel-system-roles
-
False
-
-
No
-
Dev ack
-
Release Note Not Required
This is a clone of issue RHEL-107013 to use for version rhel-9.7
–
Original description:
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>
-
- Summary by Sourcery
Prevent unquoted boolean and null values in bootloader settings by adding validation and updating documentation
Bug Fixes:
- Add a task to fail when boolean or null YAML values are specified for bootloader settings
Enhancements:
- Reject null values regardless of state presence to enforce explicit string values
Documentation:
- Document in README that boolean and null values must be quoted as strings for bootloader configuration
- links to