Uploaded image for project: 'OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC'
  1. OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
  2. TOSCA-303

Attribute status pointing to property one

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Profile-YAML
    • Labels:
      None
    • Proposal:
      Hide

      Option1: create an attribute status definition by cut and paste the property one.
      Option2: create a generic status definition and use that one everywhere is needed.

      Show
      Option1: create an attribute status definition by cut and paste the property one. Option2: create a generic status definition and use that one everywhere is needed.

      Description

      It seems really strange that for defining the attribute status we use another definition's keyname description.
      If thoese are really the same than we should have a STATUS definition that is generic and all that need it use it.
      If there is something that is called "something status" should really be used just for "that something" and not for "also something else" somewhere else in the spec.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              luca.gioppo Luca Gioppo (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: