The desire for the support of TOSCA Trigger definitions has grown
stronger with opening the #32 issue. At this point we are therefore
introducing the support for parsing TOSCA Policy type triggers which
can be used to define the event, condition and action that is used to
invoke(trigger) a policy it is associated with. These changes also
include unit tests and the runnable TOSCA template example in
examples/policy_triggers that contains policies with TOSCA triggers.
In the implementation part we first targeted to support the standard
trigger definition keynames, but then continued adding the support for
the additional keynames that are used in extended trigger notation.
With these changes we also refactor parsing policy type targets and add
new TOSCA entities like activity, condition clause and event filter, time
interval etc. along with all the tests and examples.
The desire for the support of TOSCA Trigger definitions has grown stronger with opening the #32 issue. At this point we are therefore introducing the support for parsing TOSCA Policy type triggers which can be used to define the event, condition and action that is used to invoke(trigger) a policy it is associated with. These changes also include unit tests and the runnable TOSCA template example in
examples/policy_triggersthat contains policies with TOSCA triggers. In the implementation part we first targeted to support the standard trigger definition keynames, but then continued adding the support for the additional keynames that are used in extended trigger notation.With these changes we also refactor parsing policy type targets and add new TOSCA entities like activity, condition clause and event filter, time interval etc. along with all the tests and examples.