File: OvfSectionInfo.rst

package info (click to toggle)
python-pyvmomi 5.5.0-2014.1.1-3
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 14,348 kB
  • ctags: 497
  • sloc: python: 6,594; makefile: 12
file content (33 lines) | stat: -rw-r--r-- 1,232 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
.. _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.