openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chetan Mehrotra <chetan.mehro...@gmail.com>
Subject Re: System env vars in user containers
Date Mon, 06 Aug 2018 08:57:56 GMT
> 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
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message