[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-220) get_artifact function
Luc Boutier created TOSCA-220: --------------------------------- Summary: get_artifact function Key: TOSCA-220 URL: https://issues.oasis-open.org/browse/TOSCA-220 Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC Issue Type: New Feature Components: Profile-YAML Reporter: Luc Boutier 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. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]