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-220

get_artifact function

    XMLWordPrintable

    Details

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

      get_artifact:

      The get_artifact function is used to retrieve the location of named artifact declared by the referenced node or relationship template name.

      • Grammar
      get_attribute: <modelable_entity_name>, [<req_or_cap_name>], <artifact_name> ]

      Show
      get_artifact: The get_artifact function is used to retrieve the location of named artifact declared by the referenced node or relationship template name. • Grammar get_attribute: <modelable_entity_name>, [<req_or_cap_name>] , <artifact_name> ]

      Description

      Currently the specification allows to define functions like get_attribute or get_input to be used as input parameters of an operation.

      Actually we may have scenarios where we want also to provide an artifact as an input:

      Let's consider that I want to host 2 database on a single RDBMS or 2 war on a container.
      I want to define a script that is generic so it can handle an artifact based on any location (let's consider the type is file). In order to do so I expect the orchestrator to provide me the actual location of the artifact "db_content" for example. Just like attribute of a node I should be able to access it through an environment variable set by the orchestrator.

      syntax is the same as get_attribute but the value set to the environment variable is the actual artifact location.

        Attachments

          Activity

            People

            • Assignee:
              luc.boutier Luc Boutier (Inactive)
              Reporter:
              luc.boutier Luc Boutier (Inactive)
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: