yahoo-eng-team team mailing list archive

[James Falcon <1839659@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3425

** Bug watch added: github.com/canonical/cloud-init/issues #3425
   https://github.com/canonical/cloud-init/issues/3425

** Changed in: cloud-init
       Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1839659

Title:
  cloud-init should stop accepting a plethora of values for true/false
  configuration

Status in cloud-init:
  Expired

Bug description:
  YAML has native support for boolean values, and YAML has been around
  long enough that it's reasonable to expect people to know how to write
  it.

  We should phase out accepting multiple string values ("yes", "1",
  "true", "on" for True; "no", "0", "false", "off" for False) in places
  where we do in favour of YAML boolean values.

  A proposed implementation plan:

  * Start emitting a warning about such values in the string-handling paths of util.{is_true,is_false} ASAP
  * Some time in the future (perhaps in the lead-up to Ubuntu's 22.04 LTS?), after we have been emitting these warnings for a good long while, switch the behaviour of new versions of cloud-init[0] to only accept bools

  What do we think?

  
  [0] For Ubuntu, specifically, we should also _not_ change the behaviour of existing releases when we backport these new versions of cloud-init.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1839659/+subscriptions