Enable/disable confd validation at runtime

Core Engine and APIs
1

We have many configuration validation points (both as must statements and tailf:validate statements) in our schemas. But they really come in way of scalability testing (when a huge load of configuration is done via scripting, where we do not want to test input sanctity but input volume).

Of course, the best solution would be to profile and optimize validation codes. But instead can we instruct confd to disable validation checks all together? Bonus would be to have the knob on run time.

2

There is no nob for that.
If you have written clear and concise validation code that rejects an invalid configuration regardless of which commands or other operations that were used to (attempt to) create it, the time it takes to validate should be insignificant.
If it is not insignificant, profiling where the time is consumed should be the next step