config.yaml should have enum type
Bug #918386 reported by
Gustavo Niemeyer
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Medium
|
Unassigned | ||
pyjuju |
Triaged
|
Low
|
Unassigned |
Bug Description
Currently only string is an acceptable type for data in the config.yaml file. Other types should be added, primarily: enum, integer, and boolean to help maintain some sanity in configuration options.
This bug covers enum only. For boolean, see bug #885551.
Changed in juju: | |
importance: | Undecided → Wishlist |
description: | updated |
Changed in juju: | |
status: | New → Triaged |
Changed in juju: | |
importance: | Wishlist → Low |
tags: | added: improvement |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.26-alpha1 |
tags: | added: config |
Changed in juju-core: | |
milestone: | 1.26-alpha1 → 1.26-alpha2 |
Changed in juju-core: | |
milestone: | 1.26-alpha2 → 1.26.0 |
Changed in juju-core: | |
milestone: | 1.26.0 → 2.0-alpha1 |
Changed in juju-core: | |
milestone: | 2.0-alpha1 → 2.0-alpha2 |
Changed in juju-core: | |
milestone: | 2.0-alpha2 → 2.0-alpha3 |
Changed in juju-core: | |
milestone: | 2.0-alpha3 → 2.0-beta4 |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.1.0 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.1.0 → none |
milestone: | none → 2.1.0 |
Changed in juju: | |
status: | Triaged → New |
Changed in juju: | |
status: | New → Triaged |
importance: | Low → Medium |
To post a comment you must log in.
Adding this to juju-core, as enums are still being requested for juju configuration