-
Notifications
You must be signed in to change notification settings - Fork 596
Fix config-schema.json #696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
wking
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The other changes (requiring type/soft/hard and not requiring mounts) look good to me.
schema/config-schema.json
Outdated
| "type": "object", | ||
| "required": [ | ||
| "uid", | ||
| "gid" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can't add this to the JSON Schema, because they're only required on Linux. Windows entries will not have them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That being the case, should the user field should be removed from the config-schema, into different types(config-linux.json/config-windows.json etc).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should the user field should be removed from the
config-schema, into different types (config-linux.json/config-windows.jsonetc).
You could do that if you like, but I don't think it's worth the trouble. I'd rather leave the user fields optional in the JSON Schema and check for any platform-specific requirements in runtime-tools' Go validation.
Signed-off-by: zhouhao <[email protected]>
Signed-off-by: zhouhao <[email protected]>
Signed-off-by: zhouhao [email protected]