(1) Generic validator's place doesn't suit __init__.py... I don't see this as a big deal, but if warranted I'd think we could just propose a move via patch.
(2) Some extension specific validators is still in __init__.py... Same as above.
(3) API validator is used directly... I'm not following why this is such a problem. If we decided to version the API at some point, addition changes will likely be needed including updates to the api-defs in neutron-lib. I'd think we could address such issues at that point. In addition the current validator API provides the get_validator() method thereby directly exposing the validator functions to consumers.... Is API versioning coming down the pipeline (maybe I missed it) that's prompting this concern?
Regarding the 3 points in this RFE:
(1) Generic validator's place doesn't suit __init__.py... I don't see this as a big deal, but if warranted I'd think we could just propose a move via patch.
(2) Some extension specific validators is still in __init__.py... Same as above.
(3) API validator is used directly... I'm not following why this is such a problem. If we decided to version the API at some point, addition changes will likely be needed including updates to the api-defs in neutron-lib. I'd think we could address such issues at that point. In addition the current validator API provides the get_validator() method thereby directly exposing the validator functions to consumers.... Is API versioning coming down the pipeline (maybe I missed it) that's prompting this concern?