The use of env vars wouldn't be an issue with intra-container concurrency if they're immutable, right? The more specific issue that arises today which I think is your primary concern, are the __OW_ system provided environment variables which mutate with each invocation of main. Is that right?
If so, then I think there are only two issues: 1. do we introduce a context object (did you see my other dev list mail?) 2. logging i really think my issue is orthogonal to these concerns - it's a convenience feature for the developer. An action can already export environment variables today from main. -r On Wed, Jun 26, 2019 at 8:44 PM Tyson Norris <tnor...@adobe.com.invalid> wrote: > Sorry, what I meant was: accumulating issues around the "main" function, > which are: > - context > - use of env vars > - your issue: separating user provided params from developer-provided > params > - completely separate, but worth noting: logging (and env vars) in the > face of concurrency > > On 6/26/19, 5:29 PM, "Rodric Rabbah" <rod...@gmail.com> wrote: > > > There are some accumulating issues around init and run. > > Which issues are these? > > -r > > >
