Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-107013

fix: boolean values and null values are not allowed

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • rhel-system-roles
    • 0
    • Dev ack
    • False
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • None
    • Bug Fix
    • Hide
      .`bootloader` role rejects boolean or `null` type values

      Before this update, the user could specify values such as `value: on` or `value: yes` expecting that these would be converted to strings `"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"`. Consequently, users who were unaware of YAML boolean handling could not set values such as `"on"` or `"off"`. With this update, the `bootloader` RHEL system role rejects any value of boolean or `null` type. As a result, users must enter such YAML boolean type values as quoted strings to write them to the bootloader configuration. The readme is updated with this information.
      Show
      .`bootloader` role rejects boolean or `null` type values Before this update, the user could specify values such as `value: on` or `value: yes` expecting that these would be converted to strings `"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"`. Consequently, users who were unaware of YAML boolean handling could not set values such as `"on"` or `"off"`. With this update, the `bootloader` RHEL system role rejects any value of boolean or `null` type. As a result, users must enter such YAML boolean type values as quoted strings to write them to the bootloader configuration. The readme is updated with this information.
    • Done
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      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. 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

              rmeggins@redhat.com Richard Megginson
              rmeggins@redhat.com Richard Megginson
              Richard Megginson Richard Megginson
              David Jez David Jez
              Jan Fiala Jan Fiala
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: