[Bug 1824172] Re: Do not force value of user properties to on/off

2019-04-11 Thread Jean-Baptiste Lallement
Setting to won't fix, overriding add_bool from the Contrustor class would affect *all* YAML loading and would have effect on configurations that expect boolean values to be converted to boolean types. We'll document the ZFS yaml instead. ** Changed in: curtin (Ubuntu) Status: Triaged =>

[Bug 1824172] Re: Do not force value of user properties to on/off

2019-04-11 Thread Jean-Baptiste Lallement
Hmm, actually since it's cast by the yaml engine, not sure it's fixable at curtin's level. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824172 Title: Do not force value of user properties to

[Bug 1824172] Re: Do not force value of user properties to on/off

2019-04-11 Thread Jean-Baptiste Lallement
A solution would be to override the function that converts values to boolean in the Constructor class of the YAML module. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824172 Title: Do not force

[Bug 1824172] Re: Do not force value of user properties to on/off

2019-04-11 Thread Jean-Baptiste Lallement
I'm talking about user properties not native properties. User properties are arbitrary properties which name contains a ':' and values are arbitrary strings which are never validated. It can be used to annotate datasets. (See user properties in zfs man for more details) Current behavior of

[Bug 1824172] Re: Do not force value of user properties to on/off

2019-04-10 Thread Ryan Harper
What zfs property are you aware of that takes yes/no or maybe? ** Changed in: curtin (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824172 Title: Do not