15f7be9a52
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
34 lines
1.2 KiB
ReStructuredText
34 lines
1.2 KiB
ReStructuredText
.. _int: https://docs.python.org/2/library/stdtypes.html
|
|
|
|
.. _str: https://docs.python.org/2/library/stdtypes.html
|
|
|
|
.. _bool: https://docs.python.org/2/library/stdtypes.html
|
|
|
|
.. _vSphere API 4.0: ../../vim/version.rst#vimversionversion5
|
|
|
|
.. _vmodl.DynamicData: ../../vmodl/DynamicData.rst
|
|
|
|
|
|
vim.vApp.OvfSectionInfo
|
|
=======================
|
|
The OvfSection encapsulates uninterpreted meta-data sections in an OVF descriptor. When an OVF package is imported, non-required / non-interpreted sections will be stored as OvfSection object. During the creation of an OVF package, these sections will be placed in the OVF descriptor.
|
|
:extends: vmodl.DynamicData_
|
|
:since: `vSphere API 4.0`_
|
|
|
|
Attributes:
|
|
key (`int`_, optional):
|
|
|
|
A unique key to identify a section.
|
|
namespace (`str`_, optional):
|
|
|
|
The namespace for the value in xsi:type attribute.
|
|
type (`str`_, optional):
|
|
|
|
The value of the xsi:type attribute not including the namespace prefix.
|
|
atEnvelopeLevel (`bool`_, optional):
|
|
|
|
Whether this is a global envelope section
|
|
contents (`str`_, optional):
|
|
|
|
The XML fragment including the top-levelSection...element. The fragment is self-contained will all required namespace definitions.
|