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

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

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

Moshe Elisha edited comment on TOSCA-207 at 11/13/14 11:24 AM:
---------------------------------------------------------------

I fully agree. This will also reduce confusion with the "post_configure_xxx" operations of the Configure interface.
Also name it "post_start" (with underscore)


was (Author: mosheelisha):
I fully agree. This will also reduce confusion with the "post_configure_xxx" operations of the Configure interface.

> 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
>            Reporter: Luc Boutier
>
>   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)