juju-gui exports booleans incorrectly

[Brad Marshall]

When exporting a bundle from Juju Gui, it does something interesting to any boolean values. As per this example extract from a bundle exported from a Juju GUI:

  nagios:
    charm: "local:xenial/nagios-0"
    num_units: 1
    options:
      enable_livestatus: falsetrue
      enable_pagerduty: falsetrue

and an extract from juju config nagios:

  enable_livestatus:
    default: true
    description: |
      Config variable to enable livestatus module or not.
    type: boolean
    value: false
  enable_pagerduty:
    default: true
    description: |
      Config variable to enable pagerduty notifications or not.
    type: boolean
    value: false

I believe what it is doing is taking both the default and the value for any boolean settings, and mushing them together.

I've tested this both with juju-gui from the charm store as of today, and with the built in juju-gui with juju2 with LXD deployed units, and with a deployed juju-gui with juju 1.25.6.

$ dpkg-query -W juju
juju 1:2.0.3-0ubuntu1~16.10.2~juju1

$ dpkg-query -W juju
juju 1.25.6-0ubuntu1.14.04.1

Please let me know if you need any further information.

[Drew Freiberger (afreiberger)]

This also has just happened on juju-gui rev 142 from latest charmstore on a juju 2.2.4.1 model on a different site.