openwhisk-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <boa...@gmail.com>
Subject Re: exporting activation arguments to the environment
Date Thu, 27 Jun 2019 16:59:58 GMT
Based on the giant mess in Jenkins where parameters and environment
variables sometimes get conflated, I'd definitely recommend making
them separate, especially for inevitable security issues found related
to them. ;)

On Thu, 27 Jun 2019 at 07:00, Rodric Rabbah <rodric@gmail.com> wrote:
>
> Thanks for the added feedback - keep it coming!
>
> Tyson is right in that we shouldn't let implementation concerns affect a
> proper design and sacrifcie the experience.
>
> So in line with his concerns, is there a desire to facilitate environment
> variables at all (user specified values, not system/context ones)?
>
> If so, then having thought about it some more, annotating every parameter
> could be done as suggested say with a -e vs a -p.
>
> -r



-- 
Matt Sicker <boards@gmail.com>

Mime
View raw message