So far so good. I think the most curtin-like answer is that if a path is provided, it should be correct. So we could have code verifying that. We would then mark such path values as optional and most people can be blissfully unaware of the capability. Or we could log a warning that the values are ignored.
A solution I considered in other areas is that by definition any config output by curtin is valid curtin config, so we could decide to not include it in the schema. However, this is not an answer I love because you wouldn't be able to just feed a config output to curtin back to curtin. In summary, I recommend we include path in the schema as 'path', and either verify it or something lesser (like the warning that the value is ignored in some cases). -- https://code.launchpad.net/~mwhudson/curtin/+git/curtin/+merge/429401 Your team curtin developers is requested to review the proposed merge of ~mwhudson/curtin:FR-2656-attach-device-to-action into curtin:master. -- Mailing list: https://launchpad.net/~curtin-dev Post to : curtin-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~curtin-dev More help : https://help.launchpad.net/ListHelp
