| commit | a74b45bb990786da4d4a4dd75f20eb985b901a15 | [log] [tgz] |
|---|---|---|
| author | Francesco Timperi Tiberi <francesco.timperi@gmail.com> | Sat Sep 14 11:43:37 2024 +0200 |
| committer | GitHub <noreply@github.com> | Sat Sep 14 11:43:37 2024 +0200 |
| tree | fff74f49ddd146bf9aeca7fb5e31568a30f070a4 | |
| parent | 31842f63435b31ef7abba602184f248d9998528e [diff] | |
| parent | 1e9a9cbd2723ab4d70147a20a99e964cb0bf0632 [diff] |
Merge pull request #23 from francescotimperi/main chore: added a task to generate runtimes.json according to current tag
All the Apache Openserverless OpenWhisk runtimes in a single place using the Go proxy and ActionLoop.
runtimes are docker images, and they all use a proxy in go and some scripts for execution.
Go Proxy code is in folder openwhisk and the main is proxy.go in top level.
You can compile it with go build -o proxy.
Tests are in openwhisk folder, test it with cd opewhisk ; go test
Runtime sources are under runtimes/<plang>/<version> (<plang> is programming languate)
Special case is runtime/common/<version> that contains the proxy itseself, it is used as base image for the others and must be build first.
Build and push the common runtime with task build-common. Also ensure the image is public.
Then you can build a single runtime specifingh the dir:
Build a single runtime: task build-runtime RT=nodejs VER=v18
The project contains a runtimes.json.tpl with specific placeholder for managed Apache OpenServerless runtimes. To regenerate a newer runtimes.json from the current TAG and assuming that the images have been effectively pushed to the Official DockerHub repositories under the apache account use the command:
task render-runtimes
This will create a new runtimes.json that can be pushed to the official Apache OpenServerless task repo.