Closed jw3 closed 1 year ago
Might want to add a configuration entry to disable this override by default, allowing it to be optionally enabled.
I am not a big fan of this extra dialog, but the point is to allow user to complete their workflow if the parser is incorrectly rejecting valid rules (which hasnt happened, but could). If user run into this they can change the config toml to allow the override to be displayed.
There will be a follow up issue to add that to the config.
Allow an override option for deployment when the rule parser is saying the rules are invalid.
This would provide a workaround for bugs or missing parse capability that erroneously prevent deployment.