
This external documentation for pyVmomi was generated using Googly Docs (aka Google Standard Documentation) which renders very cleanly in GitHub. Internal documentation for a class should be done in Sphinx format because tools like pyCharm and Eclipse can use that documentation as a hint for code completion. Note: External docs as Googly Docs, internal docs as Sphinx. Closes bug#15
33 lines
1.1 KiB
ReStructuredText
33 lines
1.1 KiB
ReStructuredText
.. _objectSet: ../../../vmodl/query/PropertyCollector/FilterSpec.rst#objectSet
|
|
|
|
.. _SystemError: ../../../vmodl/fault/SystemError.rst
|
|
|
|
.. _vmodl.DynamicData: ../../../vmodl/DynamicData.rst
|
|
|
|
.. _vmodl.ManagedObject: ../../../vim.ExtensibleManagedObject.rst
|
|
|
|
.. _ManagedObjectNotFound: ../../../vmodl/fault/ManagedObjectNotFound.rst
|
|
|
|
.. _vmodl.LocalizedMethodFault: ../../../vmodl/LocalizedMethodFault.rst
|
|
|
|
|
|
vmodl.query.PropertyCollector.MissingObject
|
|
===========================================
|
|
Used for reporting missing objects that were explicitly referenced by a filter spec. In other words, any of the objects referenced in `objectSet`_
|
|
:extends: vmodl.DynamicData_
|
|
|
|
Attributes:
|
|
obj (`vmodl.ManagedObject`_):
|
|
|
|
The object that is being reported missing
|
|
fault (`vmodl.LocalizedMethodFault`_):
|
|
|
|
Fault describing the failure to lookup this objectThe possible faults for missing objects are:
|
|
*
|
|
* `SystemError`_
|
|
* if there was some unknown problem looking up the object
|
|
*
|
|
* `ManagedObjectNotFound`_
|
|
* if the object is no longer available
|
|
*
|