Plugin: best practice for configuration validation

Hi, I am currently working on developing a mattermost plugin with a few commands and some http serving (the functionality of the plugin should not be important for my question).

I followed the developer documentation and also looked at already implemented plugins like the jira plugin to get an understanding about recommended code structure etc.

I have a few arguments in my configuration struct and the plugin depends on the validity of those arguments.
Is there a good way to reject configuration changes and keep the “old” configuration whenever the “new” value is not valid? Hooks like “OnConfigurationChange” only log errors but still perform the configuration change. What would be the best way to reject new configuration while still working in the bounds of the framework?
Thanks in advance.