Re: Allow decision about action result inclusion in logs on a per call basis

Thanks for the info. It makes sense. I think it is slightly confusing that this field is not invoked anywhere in the code, because you only invoke from another class managed externally. Thanks Tyson On 9/10/19, 2:45 AM, "Ruediger Maass" wrote: Hi Tyson, please find my answers below.

RE: Using private registry with KubernetesContainerFactory

Chetan Mehrotra wrote on 09/10/2019 01:23:51 AM: > > May be we can change the current approach of building the whole Pod > spec prgramatically to more of a template based. Use a base yaml/json > template [1] (exposed as config) to the podSpec and then update it for > the dynamic part before sendin

Re: Allow decision about action result inclusion in logs on a per call basis

Hi Tyson, please find my answers below. A couple questions: * " Action results may contain sensible data that should not be logged." - I don't think this solves that problem, correct? E.g. the result or error could have sensitive data still, right? Since this is generated based on the user code

[slack-digest] [2019-09-09] #general

2019-09-09 01:23:59 UTC - Dominic Kim: Please participate in this survey to figure out the best time for our community call.. https://openwhisk-team.slack.com/archives/C3T