openwhisk
Here are 270 public repositories matching this topic...
-
Updated
Jul 24, 2019 - JavaScript
-
Updated
Mar 8, 2022 - Shell
-
Updated
Oct 5, 2021 - JavaScript
-
Updated
Aug 22, 2021 - JavaScript
-
Updated
Mar 24, 2021 - JavaScript
Currently building all the cli takes a good amount of time because there are many libraries in components.
We should speed up build using smart building and build tags so task build-fast will build the core binary without the embedded binaries like task, kops, wsk and kind.
-
Updated
Mar 25, 2020 - JavaScript
-
Updated
May 5, 2020
Just spent an embarrassing amount of time trying to determine why the wsk CLI was working on one machine and not on another. The ultimate issue was that I ended up specifying the APIHOST variable as https://localhost:8443/ in the config file, with the trailing slash, which causes 404s since the CLI was sending requests to https://localhost:8443//api/v1/namespaces/_/triggers?limit=0&skip=0 (n
-
Updated
Jul 5, 2018 - Go
-
Updated
Jan 4, 2022 - JavaScript
-
Updated
Oct 20, 2021 - Python
In this PR: apache/openwhisk-wskdeploy#1124
I updated all the dependencies to their latest versions, but go-18n has a new v2 interface which can be explored for adoption and hopefully in the process improve the methods by which we generate the i18n_resources.go file and language resources.
Loop detection
Add logic to detect when an API might be calling itself (directly or via another API) in a loop, and terminate the loop.
This can be done through injection of unique headers for every hop through the gateway.
For example:
Client request -> GW: GET /api1
GW inject header: X-ApiGw-Loop: get_api1
GW request -> GW: GET /api2
GW inject header: X-ApiGw-Loop: get_api1 get_api2
GW req
-
Updated
Dec 14, 2019 - JavaScript
currently you have to run composer twice, once to generate the function code and again to generate the ast (needed for k/o-ui visualization).
it would be convenient to run compose once and specify two different files for output.
-
Updated
Apr 9, 2022 - JavaScript
If the npm package that is defined by https://github.com/apache/incubator-openwhisk-runtime-nodejs/blob/master/core/nodejs8Action/package.json was published to npm then projects would be able to depend on it and get the current set of js dependencies present in OW. Those projects building with webpack would also be able to exclude those packages from their builds, making their images smaller.
-
Updated
Dec 21, 2018 - JavaScript
-
Updated
Jul 25, 2018 - Swift
-
Updated
Aug 6, 2020 - JavaScript
-
Updated
May 26, 2019 - JavaScript
-
Updated
Apr 5, 2022 - Scala
-
Updated
Mar 28, 2022 - Jupyter Notebook
-
Updated
Jan 24, 2019 - JavaScript
-
Updated
Oct 7, 2021 - Go
-
Updated
Feb 14, 2022 - Shell
Improve this page
Add a description, image, and links to the openwhisk topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the openwhisk topic, visit your repo's landing page and select "manage topics."
The typescript runtime was recently added to openwhisk but we do not yet have docs for the runtime and it is missing from runtimes.json.
We need a doc like https://github.com/apache/incubator-openwhisk/blob/master/docs/actions-nodejs.md for typescript functions.
Adding the runtime to the runtime manifest can be done per https://github.com/apache/openwhisk/blob/master/docs/actions-new.md#the-