[OASIS Issue Tracker] (TOSCA-239) Close - Feature: Address override comment in Chapter 5

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/TOSCA-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59552#comment-59552 ] 

Sahdev Zala  commented on TOSCA-239:
------------------------------------

Per discussion on 05/07/15 TOSCA TC Special 4 Hour Meeting:

(Matt) New comment added in the C6.1 Additional Requirement section to qualify behavior to address collision, that "the default behavior when providing scripts for operations in a sub-type (sub-class) or a template of an existing type which already has a scripts provided for the operation SHALL be override. Meaning that the subclasses' script is used in place of the parent type's script. 

We are creating a new JIRA issue, and we would like to close this issue. 


> Close - Feature: Address override comment in Chapter 5
> ------------------------------------------------------
>
>                 Key: TOSCA-239
>                 URL: https://issues.oasis-open.org/browse/TOSCA-239
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Profile-YAML
>    Affects Versions: CSD03
>            Reporter: Matthew Rutkowski 
>
> Chapter 5 has the following comment:
> ---
> FEATURE: Simple override of just the named lifecycle operation (i.e. configure).  In this case, an alias for “tosca.interfaces.lifecycle.configure” see section 17.
> Thomas: Simple names (built in) that match the operations already declared in the full lifecycle definition.
> Note: Used to have in TOSCA, was complex and removed.   But, would have been useful in simplifying the design of SAP templates.
> ----
> What feature is needed? For what CSD?  The current spec. draft seems to describe already the ability override TOSCA lifecycle operations.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)