Thanks Mark for picking this up. For the interested and future reference, this is a sketch of the implementation that aligns with the proposal https://github.com/apache/incubator-openwhisk/compare/master...rabbah:trigger-activations?expand=1
-r On Tue, Dec 5, 2017 at 10:17 AM, Mark Deuser <[email protected]> wrote: > As part of the implementation of Rodric's proposal, a PR [1] has been > submitted to the change the trigger fire API as follows: > - The trigger activation record will now be persisted asynchronously > - A 202 is returned instead of 200. The activation id ("activationId") > continues to be returned in the body as before. > > This means that immediately after firing a trigger, the corresponding > trigger activation may not yet be accessible - similar to today's > asynchronous action invocation behavior. > > [1] https://github.com/apache/incubator-openwhisk/pull/3031 > > Thanks, > Mark Deuser > > On 2017-11-14 14:47, Rodric Rabbah <[email protected]> wrote: > > > > This will require an API change: when a trigger is fired (assuming it> > > exists, and the subject is authorized to fire it), today the controller> > > > will return 200 OK and an activation id. I propose instead to change > the> > > status code should to 202 Accepted if and only if the trigger has a> > > corresponding active rule, an 204 No Content otherwise.> > > > > >
