init parameters

Is anyone up for reviewing this PR https://github.com/apache/openwhisk/pull/4559 which adds the ability to separate parameters into init time vs run time? It’s been open for a while with no feedback. Previously discussed here [1] and implemented accordingly. -r [1] https://lists.apache.org/

Re: Passing TransactionId as part of action invocation

Of course if the transaction id is the same as the activation id (of the composite action) the solutions are comparable. The downside of using transaction id is that we have no APIs to query by it today, and it’s not recorded in the activation metadata. So while it’s useful for external tracin

Re: Passing TransactionId as part of action invocation

> I think if OW SDK, and sequences/compositions, propagate X-Request-Id > header (using the existing transaction id/X-Request-Id), the parent is not > needed? Thats what I counting on as we just need to correlate calls made for a given flow corelated with time to get a sequence of flow. > - expos

Re: Passing TransactionId as part of action invocation

I think if OW SDK, and sequences/compositions, propagate X-Request-Id header (using the existing transaction id/X-Request-Id), the parent is not needed? i.e. there may be 2 parts to this effort: - expose the transaction id to runtime container - propagate the transaction id in requests initiated fr

[slack-digest] [2019-08-15] #general

2019-08-15 01:56:11 UTC - Paul Yu: Hello, all ! Glad to join the slack. I have some trouble: After I set up OpenWhisk environment with , I verify the function of `wsk`. I ran, # wsk action create fib fib.py --web true # wsk