← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] (TOSCA-207) CLOSE - postconfigure operation on Standard operation should be renamed in poststart

From
OASIS Issues Tracker <>
Date
2014-12-09T20:37:39+00:00
ID
Thread
[OASIS Issue Tracker] (TOSCA-207) CLOSE - postconfigure operation on Standard operation should be renamed in poststart
[ https://issues.oasis-open.org/browse/TOSCA-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew Rutkowski  updated TOSCA-207:
-------------------------------------

    Summary: CLOSE - postconfigure operation on Standard operation should be renamed in poststart  (was: postconfigure operation on Standard operation should be renamed in poststart)

The post_configure / post_start operations has been removed by consensus of the YAML WG as the use case can be solved by using existing operations on nodes and relationships.

> CLOSE - postconfigure operation on Standard operation should be renamed in poststart
> ------------------------------------------------------------------------------------
>
>                 Key: TOSCA-207
>                 URL: https://issues.oasis-open.org/browse/TOSCA-207
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Bug
>          Components: Profile-YAML
>            Reporter: Luc Boutier
>            Assignee: Moshe Elisha
>
>   postconfigure:
>     description: Standard lifecycle post-configure operation (post-start)
> That will be much more clear (simple if it was called poststart as this is actually a poststart operation).



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
← Prev in month ← Prev in thread
Next in thread → Next in month →