Skip to content
This repository has been archived by the owner on Nov 8, 2022. It is now read-only.

Add validation of keys in config #898

Closed
jcooklin opened this issue May 3, 2016 · 1 comment
Closed

Add validation of keys in config #898

jcooklin opened this issue May 3, 2016 · 1 comment

Comments

@jcooklin
Copy link
Collaborator

jcooklin commented May 3, 2016

When snapd is started with a global config file the user should receive an
error if invalid keys are present. Snapd should not start if an invalid
config is provided.

@IRCody
Copy link
Contributor

IRCody commented May 3, 2016

I think we need a more specific definition for what makes a config invalid. Are all the sections required? If not what is the minimum set of options we are going to require? Or is it just as simple as requiring that any keys present in the config be both valid keys and in a valid position?

Some things that definitely make a config invalid:

  • Invalid/unknown keys
  • Valid keys in invalid positions

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants