This is an automated email from the ASF dual-hosted git repository.
lukeroy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openwhisk-runtime-go.git
The following commit(s) were added to refs/heads/master by this push:
new 12c5e49 missed doc update for array results (#203)
12c5e49 is described below
commit 12c5e49b4300ecafb9a09c1f5587c39f6586bd56
Author: David Grove <[email protected]>
AuthorDate: Fri Aug 23 14:12:08 2024 -0400
missed doc update for array results (#203)
Fixes #178.
---
docs/ACTION.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/ACTION.md b/docs/ACTION.md
index 0701473..a81bedf 100644
--- a/docs/ACTION.md
+++ b/docs/ACTION.md
@@ -22,7 +22,7 @@
## How to write Go Actions
-The `action-golang-v1.14` runtime can execute actions written in the Go
programming language in OpenWhisk, either precompiled binary or compiling
sources on the fly.
+The `action-golang` runtimes can execute actions written in the Go programming
language in OpenWhisk, either precompiled binary or compiling sources on the
fly.
### Entry Point
@@ -123,7 +123,7 @@ The protocol can be specified informally as follows.
Note however that more values could be provided in future.
Usually this JSON is read and the values are stored in environment variables,
converted to upper case the key and and adding the prefix `__OW_`.
-- The payload of the request is stored in the key `value`. The action should
read the field `value` assuming it is a JSON object (note, not an array, nor a
string or number) and parse it.
+- The payload of the request is stored in the key `value`. The action should
read the field `value` assuming it is either a JSON object or array and parse
it.
- The action can now perform its tasks as appropriate. The action can produce
log writing in standard output (file descriptor 1) and standard error (file
descriptor 3) . Note that those corresponds to file descriptors 1 and 2.
- The action will receive also file descriptor 3 for returning results. The
result of the action must be a single line (without embedding newlines -
newlines in strings must be quoted) written in file descriptor 3.
- The action should not exit now, but continue the loop, reading the next line
and processing as described before, continuing forever.