Ionut, of course. This is how can it be done. If you can recall we've discussed this case long time ago. And i suggest to add specific validation rule to validation_rules.json
After that there were no activity around this question.
@Amrith. This is not a bug because Trove was made in that way in which you could use custom validation_rules.json without touching codebase, same for config templates, heat templates, etc.
Just as an example. Amrith, if you still think that this is a bug then we should enter certain set of bugs for each missing configuration option for MySQL datastore.
Ionut, of course. This is how can it be done. If you can recall we've discussed this case long time ago. And i suggest to add specific validation rule to validation_ rules.json
After that there were no activity around this question.
@Amrith. This is not a bug because Trove was made in that way in which you could use custom validation_ rules.json without touching codebase, same for config templates, heat templates, etc.
Just as an example. Amrith, if you still think that this is a bug then we should enter certain set of bugs for each missing configuration option for MySQL datastore.