Following on this thread after a quick chat with Rodric to discuss the fine
grained approach in more details ( credits go to Rodric ).
For the fine grained permissions OpenWhisk could support unix style
permissions: "rwx" when defining actions and packages. For example:
wsk package create
I spent some time thinking about my proposal to support Go Actions, and I tried
to address some weaknesses that emerged in the discussion (again, thank to
James Thomas for pointing them out).
First, the most relevant, my approach requires you implement a supporting
library able to run an http s
Hi,
sounds very well thought out. The raised concerns all make sense to me and the
proposal (without thinking too deeply into it) seems to fit the "binary
executable" world quite nice (logs to stderr, payload to stdout).
One comment: You said: "Go of course". Why's that so set in stone? Could w
No, absolutely not. It is not set in stone.
It is just I know go, I already wrote the implementation with my first proposal
(replacement with an exec) and this proposal is just a natural enhancements of
the current codebase.
So if I have to implement it (and I will do, if the community agrees) I
+1 for pipes. Go is fine I’d say especially at this point. We’ve been using
python :)
-r
Go is fine of course, was just wondering about the "of course" in the initial
mail. As Rodric mentioned, a huge step forward anyway! Very much looking
forward to the outcome! :)
Cheers,
Markus
