Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add support for per-configuration property default values #33

Open
glennmatthews opened this issue May 4, 2015 · 0 comments
Open

add support for per-configuration property default values #33

glennmatthews opened this issue May 4, 2015 · 0 comments

Comments

@glennmatthews
Copy link
Owner

DSP 0243, 1.1.0, lines 1190-1206:

Configurations can further be used to control default values for properties. For Property elements inside a ProductSection, the following additional semantic is defined:

  • It is possible to use alternative default property values for different configurations in a DeploymentOptionSection. In addition to a Label and Description element, each Property element may optionally contain Value elements. The Value element shall have an ovf:value attribute specifying the alternative default and an ovf:configuration attribute specifying the configuration in which this new default value should be used. Multiple Value elements shall not refer to the same configuration.

EXAMPLE 2: The following shows an example ProductSection:

    <ProductSection>
      <Property ovf:key="app.log" ovf:type="string" ovf:value="low"
ovf:userConfigurable="true">
        <Label>Loglevel</Label>
        <Description>Loglevel for the service</Description>
        <Value ovf:value="none" ovf:configuration="minimal">
      </Property>
    </ProductSection>

COT does not presently support this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant