Hi,
How does the node state updation during the execution of the custom workflows is handled? I have defined a new interface type with its own set of lifecycle operations. It does not involve the TOSCA defined lifecycle operations like create, configure, start etc. So when I execute my service using the custom workflow, the node state is in 'initial' state. I arrived at the following observations after looking through the source code, 1. Only the 'standard' interface type is checked and the node states are updated based on the lifecycle operation associated with that interface type. 2. Node states are not updated when the interface type is not 'standard' and it remains with the default value 'initial' 3. In the model class of the node, only the set of node states defined by TOSCA and the 'deleted' state is hardcoded and set as enum to the status column Do we have any plans to support the updation of the node states during the custom workflow execution? If we have, will the user be allowed to pass the node states in the custom workflows module with the transitional and the finished states? Thanks, /Vaish
