openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominic Kim <>
Subject [Discussion] Use TransactionID as ActivationID
Date Thu, 23 Aug 2018 03:39:35 GMT
Dear whiskers.

This is to discuss to whether we will allow using TransactionID as
Some of discussion history is here:

As that PR is merged, now ActivationID is included in response headers.

Currently, TransactionID is being generated in Nginx with this change:

Then, one question that Rabbah raised comes up.
Why do we have similar two IDs in headers? (x-request-id,
Couldn't it be possible to use just one ID for both the cases?

Basic idea is just to use TransactionID(x-request-id) as a ActivationID.
But there are still few concerns that Christian described here:

And the main issue is the uniqueness of ActivationID.
If we allow using TransactionID as ActivationID, ActivationID could be
generated in two different places(Nginx, controller) as a controller also
needs to generate activation id in case of triggers and sequence actions

I want to kick off the discussion and listen to a good idea from many


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message