I don't think that this is a good idea when considering switch to GRPC in the future. Creating another wrapper class will give flexibility of implementing GRPC in separate class and not mixing (probably different) logic for two APIs. Also when needed it is easier drop support for contrail-go-api wi/o modifying code.
Please note that to satisfy requirements of contrail-go-api it is needed to store pointer to contrail.ObjectInterface type.
I don't think that this is a good idea when considering switch to GRPC in the future. Creating another wrapper class will give flexibility of implementing GRPC in separate class and not mixing (probably different) logic for two APIs. Also when needed it is easier drop support for contrail-go-api wi/o modifying code. Please note that to satisfy requirements of contrail-go-api it is needed to store pointer to contrail.ObjectInterface type.