openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Thömmes <me.markusthoem...@googlemail.com.INVALID>
Subject Re: System env vars in user containers
Date Mon, 06 Aug 2018 09:04:10 GMT
I guess this is the famous "context" object, that some other platforms
use in their function signature? @Chetan is that what you're referring
to in option 2?
Am Mo., 6. Aug. 2018 um 10:58 Uhr schrieb Chetan Mehrotra
<chetan.mehrotra@gmail.com>:
>
> > What are you thinking as an alternarive?
>
> There can be 2 ways
>
> 1. Make them part of request json itself say by placing them under
> `_ow_env` key
> 2. Or introduce a new explicit env param to the run method call
>
> #1 would be compatible. We can also introduce some convention for such
> system generated values like start with '__' or '__ow_<key name>' etc to
> avoid collision in future for such changes
>
> Chetan Mehrotra
>
>
> On Mon, Aug 6, 2018 at 2:14 PM Rodric Rabbah <rodric@gmail.com> wrote:
>
> >
> > > Should we reduce dependency on env variable to communicate such state?
> >
> > Oy. That’s right the activation id and deadline will conflict. What are
> > you thinking as an alternarive?
> >
> > -r

Mime
View raw message