Update node version and syntax for faas-cli new

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>

Author: alexellis

docs/architecture/invocations.md

@@ -22,11 +22,11 @@ Whenever you run `faas-cli build` or `faas-cli publish` using one of the OpenFaa
 Templates tend to abstract away the Dockerfile and entry-point HTTP server from you, so that you can focus on writing a HTTP or function handler, they are still there however and you can look into the "template" folder to find them after running `faas-cli template store pull`
 
 ```bash
-$ faas-cli template store pull node14
-$ ls template/node14
+$ faas-cli template store pull node20
+$ ls template/node20
 Dockerfile      function        index.js        package.json    template.yml
 
-$ ls template/node14/
+$ ls template/node20/
 handler.js      package.json
 ```
 

docs/cli/build.md

@@ -65,7 +65,6 @@ export OPENFAAS_PREFIX=docker.io/alexellis2
 
 faas-cli new --lang [email protected] \
   withprivate
-mv withprivate.yml stack.yml
 ```
 
 Next, set up a build secret, for instance to fetch Pip modules from a private PyPi repository:
@@ -153,9 +152,8 @@ Create a function:
 
 ```bash
 export OPENFAAS_PREFIX=openfaasltd
-faas-cli template store pull node17
-faas-cli new --lang node17 withprivatenpm
-mv withprivatenpm.yml stack.yml
+faas-cli template store pull node20
+faas-cli new --lang node20 withprivatenpm
 ```
 
 You will need to create an authentication token to install private npm modules. These instructions will differ depending on the registry you want to use:
@@ -188,7 +186,7 @@ provider:
   gateway: http://127.0.0.1:8080
 functions:
   withprivatenpm:
-    lang: node17
+    lang: node20
     handler: ./withprivatenpm
     image: openfaasltd/withprivatenpm:latest
     build_secrets:
@@ -201,7 +199,7 @@ Run a build with:
 faas-cli pro build -f stack.yml
 ```
 
-You'll also need an updated version of the node template to mount the secret passed in from the OpenFaaS Pro plugin. Update `template/node17/Dockerfile` and replace the second `npm i` command with:
+You'll also need an updated version of the node template to mount the secret passed in from the OpenFaaS Pro plugin. Update `template/node20/Dockerfile` and replace the second `npm i` command with:
 
 ```Dockerfile
 RUN --mount=type=secret,id=npmrc,mode=0666,dst=/home/app/.npmrc npm i

docs/cli/templates.md

@@ -56,7 +56,7 @@ dockerfile               [x]         openfaas           Classic Dockerfile templ
 dotnet8-csharp           [x]         openfaas           C# template using WebApplication
 golang-middleware        [x]         openfaas           HTTP middleware interface in Go
 java11-vert-x            [x]         openfaas           Java 11 Vert.x template
-node18                   [x]         openfaas           HTTP-based Node 18 template
+node20                   [x]         openfaas           HTTP-based Node 18 template
 php8                     [x]         openfaas           Classic PHP 8 template
 python3-http             [x]         openfaas           Python 3 with Flask and HTTP
 python3-http-debian      [x]         openfaas           Python 3 with Flask and HTTP based on Debian

docs/languages/custom.md

@@ -30,7 +30,7 @@ This will include code submitted by a third party. It may or may not be kept up
 
 ### Make your own template
 
-The easiest way to write a template for OpenFaaS it to copy an official template, and to modify it. This example creates a template using Bun and Express.js which is based upon the official node18 template.
+The easiest way to write a template for OpenFaaS it to copy an official template, and to modify it. This example creates a template using Bun and Express.js which is based upon the official node20 template.
 
 Create a new folder called my-templates, it should have a sub-directory within it called `template`.
 
@@ -57,7 +57,7 @@ Next, create a Dockerfile which should download and make available the OpenFaaS
 
 There are two watchdogs available, the [Classic Watchdog](https://github.com/openfaas/classic-watchdog), meant for processes which do not have their own HTTP server, the process will be forked for each request, and the [of-watchdog](https://github.com/openfaas/of-watchdog) for when a HTTP server is available. Since Bun used with Express.js provides a HTTP server, we'll be using the of-watchdog. 
 
-The following Dockerfile is based upon the node18 template, adapted for Bun.
+The following Dockerfile is based upon the node20 template, adapted for Bun.
 
 The `--platform=${TARGETPLATFORM:-linux/amd64}` directive is required for multi-arch support, to make the template work for 64-bit Arm as well as regular *x86_64* machines. Most images that you find on the Docker Hub will already have multi-arch support, and it's strongly recommended to keep it in place.
 

docs/languages/node.md

@@ -16,7 +16,7 @@ Create a new function using the template:
 
 ```bash
 faas-cli template pull
-faas-cli new --lang node18 echo
+faas-cli new --lang node20 echo
 ```
 
 You'll find a new folder called `echo` with a `handler.js` and `package.json` file inside.
@@ -64,7 +64,7 @@ Or to combine the `context.status()` method with the `context.succeed()` method
 To install packages, `cd` into the function folder and run `npm install --save`:
 
 ```bash
-faas-cli new --lang node18 http-req
+faas-cli new --lang node20 http-req
 cd http-req
 
 npm install --save axios
@@ -128,12 +128,12 @@ Then create a new secret in OpenFaaS:
 faas-cli secret create node-fn-token --from-file node-fn-token.txt
 ```
 
-Create a new function using the *node18* template:
+Create a new function using the *node20* template:
 
 ```bash
 export OPENFAAS_PREFIX=ttl.sh/fns
 
-faas-cli new --lang node18 node-fn
+faas-cli new --lang node20 node-fn
 ```
 
 Then edit the `node-fn/handler.js`:
@@ -172,7 +172,7 @@ Edit `node-fn.yml` and add the `secrets` section:
 ```diff
 functions:
   node-fn:
-    lang: node18
+    lang: node20
     handler: ./node-fn
     image: ttl.sh/fns/node-fn:latest
 +    secrets:
@@ -206,7 +206,7 @@ When you test the function with `faas-cli up`, make sure you use the function's
 
 Unit tests provide a quick and efficient way to exercise your code on your local computer, without needing to run `faas-cli build` or to deploy the function to a remote cluster.
 
-With the node18 template, any unit tests that you provide will be run automatically upon each invocation of `faas-cli build`.
+With the node20 template, any unit tests that you provide will be run automatically upon each invocation of `faas-cli build`.
 
 
 By default, an empty test step is written to package.json inside your function's handler folder, you can override this with your own command or test runner.

docs/openfaas-pro/builder.md

@@ -74,7 +74,6 @@ Create a test function using the `python3` template, and set it to publish to `t
 ```bash
 faas-cli new --prefix ttl.sh/test-images \
     --lang python3 py-fn
-mv py-fn.yml stack.yml
 ```
 
 Now, publish an image using the remote builder:
@@ -270,7 +269,7 @@ You may need to enable build arguments for the Dockerfile, these can be passed t
 {
   "image": "ttl.sh/alexellis/test-image:0.1.0",
   "buildArgs": {
-    "BASE_IMAGE": "gcr.io/quiet-mechanic-140114/openfaas-base/node16"
+    "BASE_IMAGE": "gcr.io/quiet-mechanic-140114/openfaas-base/node20"
   }
 }
 ```

docs/openfaas-pro/kafka-events.md

@@ -77,7 +77,7 @@ Most templates make these variables available through their request or context o
 
 * [golang-middleware](/languages/go/)
 * [python3-http](/languages/python/)
-* [node17](/languages/node/)
+* [node20](/languages/node/)
 
 For detailed examples with Node.js, see: [Serverless For Everyone Else](http://store.openfaas.com/l/serverless-for-everyone-else)
 

docs/reference/private-registries.md

@@ -116,7 +116,6 @@ Create a sample function with a `--prefix` variable:
 
 ```sh
 faas-cli new --lang go private-fn --prefix=registry:port/repo
-mv private-fn.yml stack.yml
 ```
 
 Update the `stack.yml` file and add a reference to the new secret:

docs/reference/secrets.md

@@ -83,7 +83,6 @@ faas-cli template store pull python3-http
 export OPENFAAS_PREFIX=ttl.sh/alexellis
 
 faas-cli new --lang python3-http protected-api
-mv protected-api.yml stack.yml
 ```
 
 Create a secret called `protected-api-token`, it will be used to authenticate all requests made to the new `protected-api` function.

docs/reference/yaml.md

@@ -43,12 +43,6 @@ functions:
     image: fn2:latest
 ```
 
-Then rename your file to stack.yml, so you don't need to specify the `-f` flag when using the CLI.
-
-```bash
-mv fn1.yml stack.yml
-```
-
 ## Provider
 
 The only valid value for provider `name` is `openfaas`.