While performing a non-interactive configuration of LXD via preseed YAML,
if the yaml contains unknown keys, then LXD is correctly configured and
the user is not notified about those unknown/ignored keys.
I would expect LXD issuing some kind of warning/message better informing
the user about ignored preseed keys.
I am worried about users passing not yet supported keys in older LXD
versions. As for example, in LXD < 4.12, projects is not yet supported
to be preseed-configured, and as far as I can tell, the only way for the
user to realize this is explicitly checking the LXD project configuration.
Some examples of not universally supported preseed keys:
projects introduced in LXD 4.12
projects.config.features.network introduced in LXD 4.6
projects.config.features.storage.buckets introduced in LXD 5.5
Required information
Issue description
While performing a non-interactive configuration of LXD via preseed YAML, if the yaml contains unknown keys, then LXD is correctly configured and the user is not notified about those unknown/ignored keys.
I would expect LXD issuing some kind of warning/message better informing the user about ignored preseed keys.
I am worried about users passing not yet supported keys in older LXD versions. As for example, in LXD < 4.12,
projects
is not yet supported to be preseed-configured, and as far as I can tell, the only way for the user to realize this is explicitly checking the LXD project configuration.Some examples of not universally supported preseed keys:
projects
introduced in LXD 4.12projects.config.features.network
introduced in LXD 4.6projects.config.features.storage.buckets
introduced in LXD 5.5Steps to reproduce
echo "foo: 3.14" | lxd init --preseed --debug 2> lxd.log
.Information to attach
Output of
echo "foo: 3.14" | lxd init --preseed --debug
: