You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwhisk.apache.org by Rodric Rabbah <ro...@gmail.com> on 2019/12/21 11:40:27 UTC
disallow init parameters at invoke time?
This PR https://github.com/apache/openwhisk/pull/4559 added init-time
parameters. It allows those parameters to be specified on action
creation/updates as well as at invoke time.
This note is to solicit feedback on whether the controller should disallow
init-parameters at invoke time. The reason is that unless the activation is
a fresh (cold) activation, the init-parameters will not be observable by
the action (init-paramters are only sent at /init time and not /run time).
So it can be confusing although it is also convenient for rapid iterations
in the cloud (update/invoke pattern where the invoke is always cold after
an update).
Opinions and feedback?
-r
Re: disallow init parameters at invoke time?
Posted by Dominic Kim <st...@gmail.com>.
+1 to disallow it as init-parameters are not used at invoke time.
The clearer the better.
Best regards
Dominic
2019년 12월 21일 (토) 오후 8:41, Rodric Rabbah <ro...@gmail.com>님이 작성:
> This PR https://github.com/apache/openwhisk/pull/4559 added init-time
> parameters. It allows those parameters to be specified on action
> creation/updates as well as at invoke time.
>
> This note is to solicit feedback on whether the controller should disallow
> init-parameters at invoke time. The reason is that unless the activation is
> a fresh (cold) activation, the init-parameters will not be observable by
> the action (init-paramters are only sent at /init time and not /run time).
>
> So it can be confusing although it is also convenient for rapid iterations
> in the cloud (update/invoke pattern where the invoke is always cold after
> an update).
>
> Opinions and feedback?
>
> -r
>
Re:disallow init parameters at invoke time?
Posted by Bill Zong <bi...@163.com>.
+1 to disallow it as init-parameters are not used at invoke time.
The init function invokes once and only once in users’ mind, they wouldn't aware of reuse of the container.
| |
Bill Zong
|
|
billzong@163.com
ShenZhen, China
|
签名由网易邮箱大师定制
On 12/21/2019 19:40，Rodric Rabbah<ro...@gmail.com> wrote：
This PR https://github.com/apache/openwhisk/pull/4559 added init-time
parameters. It allows those parameters to be specified on action
creation/updates as well as at invoke time.
This note is to solicit feedback on whether the controller should disallow
init-parameters at invoke time. The reason is that unless the activation is
a fresh (cold) activation, the init-parameters will not be observable by
the action (init-paramters are only sent at /init time and not /run time).
So it can be confusing although it is also convenient for rapid iterations
in the cloud (update/invoke pattern where the invoke is always cold after
an update).
Opinions and feedback?
-r
Re: disallow init parameters at invoke time?
Posted by Seong Hyun Oh <se...@gmail.com>.
+1 To disallow init-parameters at invoke time.
But I'd like to keep the OW environment variables that are sent at /init
time.
Best regards
Seonghyun (@upgle)
2019년 12월 21일 (토) 오후 8:41, Rodric Rabbah <ro...@gmail.com>님이 작성:
> This PR https://github.com/apache/openwhisk/pull/4559 added init-time
> parameters. It allows those parameters to be specified on action
> creation/updates as well as at invoke time.
>
> This note is to solicit feedback on whether the controller should disallow
> init-parameters at invoke time. The reason is that unless the activation is
> a fresh (cold) activation, the init-parameters will not be observable by
> the action (init-paramters are only sent at /init time and not /run time).
>
> So it can be confusing although it is also convenient for rapid iterations
> in the cloud (update/invoke pattern where the invoke is always cold after
> an update).
>
> Opinions and feedback?
>
> -r
>