ioana-blue opened a new issue #995: Redo action sequence implementation URL: https://github.com/apache/incubator-openwhisk/issues/995 @perryibm @rabbah and I discussed sequences. I'm summarizing the conclusions of the discussion. User-visible aspects: - A sequence will have an activation id - The logs of a sequence are constructed by the OW runtime as follows: each line contains an activation id and the result (success, failure) for the activation id - Entitlement check is performed at the moment of invocation for all actions (i.e., to invoke a sequence, the user has to have the rights to invoke each action in the sequence). There won't be any partial execution of sequences (e.g., first 2 actions in the sequence are executed as the user has rights, while the remaining ones are not if the user doesn't have the right to invoke the third action in the sequence). Implementation internals: - The current implementation with `pipe.js` in the invoker will stay in place but guarded by a flag for experimental/comparison reasons - The logic of executing a sequence are moved to the controller. The controller starts an actor each time it needs to execute a sequence. The actor executes in blocking fashion each action by posting directly to Kafka. - The logs for the sequence are constructed as explained above and stored in the activation record for the sequence. - The annotation for the activation will contain a field kind that indicates this activation was a sequence More comments from @rabbah - entitlement check for the sequence component should be done both at create/update and invoke time. - note: the actor doesn't perform an entitlement check before invoking - it's the route handler that does; the actor simply executes the invokes, waits for responses, and then writes the activation record. - the result of the sequence should be the result of the last action in the sequence. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
With regards, Apache Git Services
