Do not include dynamically loaded values into OVO testing
Those OVO values loaded dynamically (for example [1]) should not be
added to the tested object. A dynamic column in a DB register is a
``sqlalchemy.orm.AppenderQuery`` object that represents the needed
query to retrieve this value.
These OVO fields, mapped from the DB object, should be considered as
synthetic fields and not be included in
``_BaseObjectTestCase.obj_fields``.
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/788463 /opendev. org/openstack/ neutron/ commit/ de295f036df2ced ec9de4c25f344eb b770f66e0a
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit de295f036df2ced ec9de4c25f344eb b770f66e0a
Author: Rodolfo Alonso Hernandez <email address hidden>
Date: Wed Apr 28 09:36:07 2021 +0000
Do not include dynamically loaded values into OVO testing
Those OVO values loaded dynamically (for example [1]) should not be y.orm.AppenderQ uery`` object that represents the needed
added to the tested object. A dynamic column in a DB register is a
``sqlalchem
query to retrieve this value.
These OVO fields, mapped from the DB object, should be considered as BaseObjectTestC ase.obj_ fields` `.
synthetic fields and not be included in
``_
[1]https:/ /github. com/openstack/ neutron/ blob/ff2464bf33 f1c84bd8525eca6 8c5774f5e14f1f1 /neutron/ db/models/ securitygroup. py#L103- L106
Closes-Bug: #1926399
Change-Id: I4b59dbc71316ee de52b22c0788de5 fd682fbff30