Unable to set boolean config value via command line

Bug #979859 reported by Robert Ayres on 2012-04-12
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Thomas Herve

Bug Description

Attempting to set a boolean config value via the command line, like:

juju set -e local service boolean=False

Results in:

Invalid value for boolean: 'False'

Setting it using a config file '--config' works fine.


Related branches

Changed in juju:
milestone: none → galapagos
status: New → Triaged
importance: Undecided → High
Changed in juju:
status: Triaged → In Progress
assignee: nobody → Thomas Herve (therve)
Gustavo Niemeyer (niemeyer) wrote :

Please consider the conversation around "format: 2" when sorting out this issue. It'd be good to have William as one of the reviewers for the branch too.

William Reade (fwereade) wrote :

Sure, I'll gladly take a look when there's a proposal.

Changed in juju:
milestone: galapagos → honolulu
Jim Baker (jimbaker) wrote :

This was fixed for charms using format: 2 in r544 with merge of charm-format-2 branch. However, this still could be useful for older charms too, since the behavior is clearly buggy as it is now (no backwards compatibility issues),

Changed in juju:
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers