JSON vs Config vs GUI Settings?

[fattipants2016]

I'm curious about the precedence / interaction between the JSON settings in ProgramData, the config file in Program Files and the configuration in the GUI.

Do JSON settings take precedence over a config file that might still reside in my application directory?

And adjusting settings (turning NTFS filter bypass, for instance) doesn't turn on the corresponding setting in the GUI.

If I've turned on filter bypass in the JSON and the GUI still says it's off, which is correct!?

I don't mind changing the option in multiple places, it's just a lot of bases to cover when troubleshooting / tweaking.

 

 

[Christopher (Drashna)]

The config files are being depreciated in favor of the JSON files.  The json files are more flexible, and list both the default and override values.

 

So use the JSON files, whenever possible. 

[Christopher (Drashna)]

20 minutes ago, fattipants2016 said:

If I've turned on filter bypass in the JSON and the GUI still says it's off, which is correct!?

This is one of the more tricky options.

IIRC, the config/json file essentially sets the default for this. But we allow it to be configured per pool, as well. 

[fattipants2016]

Thanks for the help. Everything seems happy right now, so I'll stop tinkering with it.

[Christopher (Drashna)]

Glad to hear it! 
But feel free to keep tinkering!