I implemented both, the "convention" and the parameters designated as init through the API. The latter wasn't much more over the former and is backward compatible. This can be introduced incrementally into the main repo/REST API, then the runtimes (I added it to Node but not the others), and eventually the CLI and other tooling to introduce a "-e".
> - this is also a bigger convention change for action developers (read from env or context instead of the single args object given to main) We have no mechanism today for developers to use env vars with their actions. This new capability actually leads to nicer code -- one prime example is the use of 'npm openwhisk' which can now be lifted to a top level constant that's automatically initialized, or using libraries such as sequelize in a similar way. So while it would require developers to take advantage of this, it doesn't break any existing code. On Thu, Jun 27, 2019 at 1:25 PM Tyson Norris <tnor...@adobe.com.invalid> wrote: > BTW, circling back on "can it be done just using -p in current form": I > still like the idea that: > - action configured params are different the user specified params (and we > should only pass them on init, not run) > - this is also a bigger convention change for action developers (read from > env or context instead of the single args object given to main) > > But - *adding* the -e, instead of revising the meaning of -p does makes > this a backwards compatible change, so that's a good thing. > > Thanks > Tyson > > >
