[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-181) Dependency requirement type should match any target node.
[ https://issues.oasis-open.org/browse/TOSCA-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew Rutkowski updated TOSCA-181:
-------------------------------------
Fix Version/s: CSD03
> Dependency requirement type should match any target node.
> ---------------------------------------------------------
>
> Key: TOSCA-181
> URL: https://issues.oasis-open.org/browse/TOSCA-181
> Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
> Issue Type: Sub-task
> Components: Profile-YAML
> Reporter: Luc Boutier
> Assignee: Luc Boutier
> Fix For: CSD03
>
>
> I think the definition of the Root node has something wrong: right now we have removed the Feature capability/dependency to replace it with a single dependency requirement of type tosca.capabilities.Root.
> But actually no nodes defines the tosca.capabilities.Root capability. I think it's not very correct to satisfy a requirement by something that doesn't match the type of the requirement (and we don't have node directly defining the tosca.capabilities.Root capability).
> To make it simpler and, I think, more correct, we should change the dependency definition so the requirement type is directly tosca.nodes.Root as I think any node can depends from another one.
> Woud be:
> tosca.nodes.Root:
> description: The TOSCA Node Type all other TOSCA base Node Types derive from
> attributes:
> tosca_id:
> type: string
> tosca_name:
> type: string
> requirements:
> - dependency:
> type: tosca.nodes.Root
> lower_bound: 0
> upper_bound: unbounded
> interfaces: [tosca.interfaces.node.lifecycle.Standard | tosca.interfaces.node.lifecycle.Simple ]
--
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]