32c8d43a20
Since the attribute access on a ManagedObjectReference can differ depending on the SOAP library used in the backend, we and especially depending projects should not rely on it, because that breaks the abstraction layer oslo.vmware is supposed to provide. To help transitioning to a newer backend library, we introduce two methods for retrieving a ManagedObjectReference's value and type: get_moref_value() and get_moref_type(). We cannot handle this by just returning our own ManagedObjectReference object with uniform access, because it's hard to get control of all morefs returned by the API. In that spirit, we also change all references inside of oslo_vmware to using `get_moref_value()` and `get_moref_type()` instead of directly accessing the attributes. This is part of phase 1 of https://specs.openstack.org/openstack/oslo-specs/specs/victoria/oslo-vmware-soap-library-switch.html Change-Id: I0b0a3d37f6c7d0c750b48596bc3d79b8b2cb0cee
10 lines
486 B
YAML
10 lines
486 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
``ManagedObjectReference``'s ``value`` and ``_type`` attributes must not be
|
|
used anymore in depending projects. Instead, ``vim_util.get_moref_value()``
|
|
and ``vim_util.get_moref_type()`` have to be used, because with
|
|
`this spec <https://specs.openstack.org/openstack/oslo-specs/specs/victoria/oslo-vmware-soap-library-switch.html>`_
|
|
we switch the backing SOAP library and different libraries have different
|
|
representations of those attributes.
|