Updates for CLI which uses stack.yaml by default

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <alexellis2@gmail.com>

Author: alexellis

_includes/landing-page/code-examples/javascript.html

@@ -1,5 +1,5 @@
 <div id="Javascript" class="tabcontent">
-<pre><code class="language-shell">$ faas-cli new --lang node18 javascript-fn 
+<pre><code class="language-shell">$ faas-cli new --lang node20 javascript-fn 
 </code></pre>
 <div class="has-text-grey-darker has-text-weight-light">
     handler.js

_includes/products-page/products-cards.html

@@ -86,7 +86,7 @@ <h3 class="title is-size-12 is-size-8-desktop has-text-grey-darker">
                             <subtitle class="is-size-5 mb-3">
                                 Expose services to the Internet from localhost or Kubernetes
                             </subtitle>
-                            <p style="padding-bottom: 20px" class="has-text-weight-light">Expose TCP & HTTP endpoints without rate-limits and complete privacy.</p>
+                            <p style="padding-bottom: 20px" class="has-text-weight-light">Expose TCP & HTTP endpoints through cloud VMs for complete privacy.</p>
                         </div>
                         <div>
                            <a class="button is-primary is-medium" href="https://inlets.dev">inlets.dev</a>

_posts/2018-08-02-read-only-functions.md

@@ -54,7 +54,6 @@ The example code will be available [on GitHub here](https://github.com/alexellis
 
 ```bash
 faas-cli new --lang node access-control --prefix=alexellis2
-mv access-control.yml stack.yml
 echo "alexellis" > ./access-control/valid_user.txt
 ```
 

_posts/2018-08-22-five-cli-tips.md

@@ -41,7 +41,7 @@ Now if you were to run a `build`, `push` or `deploy` you'd carry that step out f
 
 You can simply type in `faas-cli build --filter=filter2` for instance.
 
-Now if you do happen to edit most of your functions most of the time such as with [OpenFaaS Cloud](https://github.com/openfaas/openfaas-cloud/blob/master/stack.yml), then you can use the `--parallel` flag and your images will be built concurrently. If you have 16 functions in one YAML file and use `--parallel=4` they will build in batches of 4 saving time overall. This speed-boosting feature isn't available when working with Docker outside of OpenFaaS.
+Now if you do happen to edit most of your functions most of the time such as with [OpenFaaS Cloud](https://github.com/openfaas/openfaas-cloud/blob/master/stack.yaml), then you can use the `--parallel` flag and your images will be built concurrently. If you have 16 functions in one YAML file and use `--parallel=4` they will build in batches of 4 saving time overall. This speed-boosting feature isn't available when working with Docker outside of OpenFaaS.
 
 You can also split your functions into separate folders, repos or YAML files.
 
@@ -111,7 +111,7 @@ Successfully tagged alexellis2/test1:latest-b6d5661
 
 If we change the tag in the YAML file from `latest` to `0.1` then the image tag would have been: `test1:0.1-b6d5661`. This is useful for CI/CD jobs and is supported by the verbs: `build`, `push`, `deploy` and `up`.
 
-You can also omit the `--yaml/-f` flag if you rename your YAML file to `stack.yml`
+You can also omit the `--yaml/-f` flag if you rename your YAML file to `stack.yaml`
 
 ## Tip 5: Use `faas-cli up` and save on typing
 

_posts/2018-09-06-stateless-microservices.md

@@ -294,7 +294,7 @@ The guestbook code stores its state in a MySQL table which means that it can be
 
 To enable [scaling to zero](https://www.openfaas.com/blog/zero-scale/) simply [follow the documentation](https://docs.openfaas.com/architecture/autoscaling/#zero-scale) to enable the `faas-idler`.
 
-Then add a label to your `stack.yml` file to tell OpenFaaS that your function is eligible for zero-scaling:
+Then add a label to your `stack.yaml` file to tell OpenFaaS that your function is eligible for zero-scaling:
 
 ```yaml
     labels:

_posts/2019-01-24-unified-secrets.md

@@ -34,7 +34,7 @@ environment variables can be used to configure non-confidential data such as fea
 
 * Do manage config with environment variables
 
-You can manage configuration with environment variables by declaring an `environment:` section in your function's `stack.yml` file. Or you can create an external file for your environmental configuration with `environment_file:`.
+You can manage configuration with environment variables by declaring an `environment:` section in your function's `stack.yaml` file. Or you can create an external file for your environmental configuration with `environment_file:`.
 
 Read more about using environment variables for config in the [YAML reference](https://docs.openfaas.com/reference/yaml/#function-environmental-variables).
 

_posts/2019-01-29-multifile-python-functions.md

@@ -49,7 +49,7 @@ The project should now look like
 
 ```txt
 .
-├── stack.yml
+├── stack.yaml
 ├── template
 │   ├── python27-flask
 │   │   ├ ...
@@ -78,7 +78,7 @@ The project should now look like this
 
 ```txt
 .
-├── stack.yml
+├── stack.yaml
 ├── template
 │   ├── ...
 └── wordcount

_posts/2019-02-04-digitalocean-one-click.md

@@ -118,12 +118,6 @@ Function created in folder: hello-digitalocean
 Stack file written: hello-digitalocean.yml
 ```
 
-* Rename `hello-digitalocean.yml` to `stack.yml`:
-
-```sh
-$ mv hello-digitalocean.yml stack.yml
-```
-
 * Edit `hello-digitalocean/handler.py` to add our function's code:
 
 ```python

_posts/2019-02-12-openfaas-on-fargate.md

@@ -59,7 +59,7 @@ scheduled in a `private subnet` that has no access to the Internet
 to manage service registration / de-registration
 * **\[logging\]** we configure each container workload to log to [AWS cloudwatch](https://aws.amazon.com/cloudwatch).
 * **\[secrets\]** managed using [AWS Secrets Manager](https://aws.amazon.com/secrets-manager/) and assigned access to functions
-in the `stack.yml`
+in the `stack.yaml`
 * **\[tls\]** ingress TLS is automatically provisioned using [Certbot](https://certbot.eff.org/) and the
 [Let's Encrypt](https://letsencrypt.org/) certificate authority.
 

_posts/2019-02-14-serverless-single-page-app.md

@@ -231,7 +231,7 @@ Functions:
 
 Other files:
 
-* `stack.yml` - defines the functions and is generated by the `faas-cli`
+* `stack.yaml` - defines the functions and is generated by the `faas-cli`
 * `secrets.yaml` - defines encrypted or "sealed" secrets generated by `faas-cli cloud seal`
 
 The database schema is written in the README.md file at the root.

_posts/2019-03-06-google-form-response.md

@@ -119,10 +119,6 @@ In your terminal of choice, create the new function from the `csharp` template:
 
 ```sh
 $ faas-cli new signup-form --lang csharp
-
-# Rename signup-form.yml to the default "stack.yml", to reduce on typing.
-
-$ mv signup-form.yml stack.yml
 ```
 
 We're going to need to add a dependency to `Newtonsoft.Json` to parse the JSON request from the form. We'll also add the C# Slack SDK to make it easy to post a message to the appropriate channel. The dependencies will be added from Nuget via `dotnet add`:

_posts/2019-03-30-openfaas-cloud-gitlab.md

@@ -324,7 +324,7 @@ Now add a tag to the repo so that OpenFaaS Cloud knows that it can manage this r
 
 * Create a new function:
 
-```
+```bash
 faas-cli template store pull node10-express
 faas-cli new --lang node10-express timezone-shift --prefix=dockerhub_username
 ```
@@ -333,14 +333,14 @@ Now let's create a quick function to shift timezones for meetings.
 
 We'll install an `npm` module so you'll need to have Node.js installed on your local machine, or run this command in a container and grab the resulting `package.json` file.
 
-```
+```bash
 cd timezone-shift
 npm install --save moment
 ```
 
 Enter into `handler.js`:
 
-```
+```js
 "use strict"
 const moment = require('moment');
 module.exports = (event, context) => {
@@ -352,15 +352,11 @@ module.exports = (event, context) => {
 }
 ```
 
-We need to rename our function’s YAML file to `stack.yml`, so that it can be picked up by the OpenFaaS Cloud CI/CD pipeline.
-
-```
-mv timezone-shift.yml stack.yml
-```
+We need to rename our function’s YAML file to `stack.yaml`, so that it can be picked up by the OpenFaaS Cloud CI/CD pipeline.
 
 Push the code:
 
-```
+```bash
 git add .
 git commit
 git push origin master

_posts/2019-04-09-openfaas-cloudrun.md

@@ -198,7 +198,7 @@ Now go over to your fork of my GitHub repo and edit your `cloudbuild.yaml` file.
 
 When complete it will deploy a second revision to the Cloud Run Service and we'll get a URL on the Cloud Run dashboard.
 
-> Don't like managing a `cloudbuild.yaml` file for every one of your GitHub repositories? No problem - checkout [OpenFaaS Cloud](https://docs.openfaas.com/openfaas-cloud/intro/) which uses your existing stack.yml file to automate CI/CD for any linked repository on GitHub or self-hosted GitLab.
+> Don't like managing a `cloudbuild.yaml` file for every one of your GitHub repositories? No problem - checkout [OpenFaaS Cloud](https://docs.openfaas.com/openfaas-cloud/intro/) which uses your existing stack.yaml file to automate CI/CD for any linked repository on GitHub or self-hosted GitLab.
 
 ### Monitor the function
 

_posts/2019-04-10-golang-serverless.md

@@ -341,7 +341,7 @@ OK
 
 As part of a blog post on how to build a full Single Page App with OpenFaaS I used the golang-middleware template to build a function to consume events from GitHub and to store them in a Postgres database.
 
-You can read the code here for [handler.go](https://github.com/alexellis/leaderboard-app/blob/master/github-sub/handler.go). Confidential data is configured through the use of secrets and non-confidential configuration us set through environment variables in [stack.yml](https://github.com/alexellis/leaderboard-app/blob/master/stack.yml#L18).
+You can read the code here for [handler.go](https://github.com/alexellis/leaderboard-app/blob/master/github-sub/handler.go). Confidential data is configured through the use of secrets and non-confidential configuration us set through environment variables in [stack.yaml](https://github.com/alexellis/leaderboard-app/blob/master/stack.yaml#L18).
 
 ## Custom templates
 

_posts/2019-04-17-kafka-connector.md

@@ -35,7 +35,7 @@ See also: [Apache Kafka Documentation](https://kafka.apache.org/documentation/).
 
 ## Kafka Connector
 
-The [kafka-connector](https://github.com/openfaas-incubator/kafka-connector) is designed to connect Kafka topics to OpenFaaS Functions. After deploying the kafka-connector and pointing it at your broker, you can connect functions to topics by adding a simple annotation via your functions' stack.yml file.
+The [kafka-connector](https://github.com/openfaas-incubator/kafka-connector) is designed to connect Kafka topics to OpenFaaS Functions. After deploying the kafka-connector and pointing it at your broker, you can connect functions to topics by adding a simple annotation via your functions' stack.yaml file.
 
 Conceptual architecture diagram:
 
@@ -123,14 +123,14 @@ $ export OPENFAAS_PREFIX=docker.io/alexellis2
 # Create a function in Go
 $ faas-cli new email-receipt \
   --lang=go
-$ mv email-receipt.yml stack.yml
+$ mv email-receipt.yml stack.yaml
 ```
 
-> We also renamed the function's YAML file to  `stack.yml` (the default)
+> We also renamed the function's YAML file to  `stack.yaml` (the default)
 
 The function is a simple `Hello World` written in Go, you can edit it if you want, but for simplicity in our example we will keep the default message.
 
-Edit the `stack.yml` file by adding `topic` annotation with the value which which we pointed in the Kafka Connector `payment-received`. The file should look like this:
+Edit the `stack.yaml` file by adding `topic` annotation with the value which which we pointed in the Kafka Connector `payment-received`. The file should look like this:
 
 ```yaml
 provider:

_posts/2019-08-29-five-security-tips.md

@@ -131,7 +131,7 @@ spec:
   image: functions/nodeinfo:latest
 ```
 
-* How to generate a CRD entry from a `stack.yml` file:
+* How to generate a CRD entry from a `stack.yaml` file:
 
 ```bash
 # create a go function for Docker Hub user `alexellis2`
@@ -141,7 +141,7 @@ faas-cli new --lang go --prefix alexellis2 crd-example
 faas-cli build -f crd-example.yaml
 faas-cli push -f crd-example.yaml
 
-# generate the CRD entry from the "stack.yml" file and apply in the cluster
+# generate the CRD entry from the "stack.yaml" file and apply in the cluster
 faas-cli generate -f crd-example.yaml | kubectl apply -f -
 ```
 
@@ -183,7 +183,7 @@ Any containers deployed with "privileged mode" on Kubernetes, if compromised cou
 
 The OpenFaaS core components run as non-root users to reduce attack surface.
 
-Templates contain a Dockerfile and an entrypoint, which is usually a HTTP server. These allow developers to avoid repeating themselves with hundreds of lines of Kubernetes YAML, instead they get 3-4 lines in a CRD or OpenFaaS `stack.yml` file. The official OpenFaaS templates use a non-root user so that functions are running as normal users. 
+Templates contain a Dockerfile and an entrypoint, which is usually a HTTP server. These allow developers to avoid repeating themselves with hundreds of lines of Kubernetes YAML, instead they get 3-4 lines in a CRD or OpenFaaS `stack.yaml` file. The official OpenFaaS templates use a non-root user so that functions are running as normal users. 
 
 See an example: [openfaas-incubator/node10-express-service](https://github.com/openfaas-incubator/node10-express-service/blob/master/template/node10-express-service/Dockerfile)
 
@@ -199,7 +199,7 @@ OpenFaaS Pods can make use of Kubernetes secrets. To create a secret use `faas-c
 echo SECRET | faas-cli secret create api-key
 ```
 
-You can then attach the secret to a function by editing its stack.yml file, or by using the `--secret` flag with `faas-cli up`.
+You can then attach the secret to a function by editing its stack.yaml file, or by using the `--secret` flag with `faas-cli up`.
 
 See also: [OpenFaaS workshop: Lab 10 - Secrets](https://github.com/openfaas/workshop/blob/master/lab10.md)
 

_posts/2019-10-08-lambda-to-openfaas.md

@@ -60,7 +60,7 @@ exports.handler = async (event) => {
 };
 ```
 
-Let's examine the example for OpenFaaS. When you create a new function with the OpenFaaS CLI and the `node18` template, sample code is provided as shown here:
+Let's examine the example for OpenFaaS. When you create a new function with the OpenFaaS CLI and the `node20` template, sample code is provided as shown here:
 
 ```js
 'use strict'
@@ -176,39 +176,35 @@ Now, create the new "shortener" function:
 
 ```sh
 $ faas-cli new shortener \
-    --lang node18
+    --lang node20
 ```
 
 This will create a `shortener.yml` file, and a directory with the same name containing the sample function code to work from. By setting the `OPENFAAS_PREFIX` environment variable your registry name is added to the image so that the image can be pushed.
 
-OpenFaaS uses the convention of having a `stack.yml` file that contains all of the function definitions to operate on. You can use the `--yaml` or `-f` flags to provide a differently named file, but for this post, we'll rename the generated yml file making the remainder of the commands simpler.
-
-```bash
-mv shortener.yml stack.yml
-```
+OpenFaaS uses the convention of having a `stack.yaml` file that contains all of the function definitions to operate on. You can use the `--yaml` or `-f` flags to provide a differently named file, but for this post, we'll rename the generated yml file making the remainder of the commands simpler.
 
 When we create the "redirector" function, we can pass the `--append` flag to automatically add the new function's definition to the existing file.
 
 ```sh
 $ faas-cli new redirector \
-    --lang node18 \
-    --append stack.yml
+    --lang node20 \
+    --append stack.yaml
 ```
 
-The resulting `stack.yml` file will look something like this:
+The resulting `stack.yaml` file will look something like this:
 
 ```yaml
 functions:
   shortener:
-    lang: node18
+    lang: node20
     handler: ./shortener
     image: burtonr/shortener:latest
   redirector:
-    lang: node18
+    lang: node20
     handler: ./redirector
     image: burtonr/redirector:latest
 ```
-_file source: [openfaas/stack.yml](https://github.com/welteki/lambda-openfaas-blog/blob/master/openfaas/stack.yml)_
+_file source: [openfaas/stack.yaml](https://github.com/welteki/lambda-openfaas-blog/blob/master/openfaas/stack.yaml)_
 
 ### Migrate the Function Code
 
@@ -286,13 +282,13 @@ Finally, we'll add the secrets to the function's `yml` file so that the function
 ```yaml
 functions:
   shortener:
-    lang: node18
+    lang: node20
     ...
     secrets:
       - shorturl-dynamo-key
       - shorturl-dynamo-secret
 ```
-_file source: [openfaas/stack.yml](https://github.com/welteki/lambda-openfaas-blog/blob/master/openfaas/stack.yml)_
+_file source: [openfaas/stack.yaml](https://github.com/welteki/lambda-openfaas-blog/blob/master/openfaas/stack.yaml)_
 
 > Read more about [Unifying Secrets with OpenFaaS](/blog/unified-secrets)
 
@@ -306,12 +302,12 @@ Below is the additions that would need to be added to the function's yaml file:
 ```yaml
 functions:
   shortener:
-    lang: node18
+    lang: node20
     ...
     annotations:
       com.openfaas.serviceaccount: "iamserviceaccount"
 ```
-_file source: [openfaas/stack.yml](https://github.com/welteki/lambda-openfaas-blog/blob/master/openfaas/stack.yml)_
+_file source: [openfaas/stack.yaml](https://github.com/welteki/lambda-openfaas-blog/blob/master/openfaas/stack.yaml)_
 
 
 ### Code differences

_posts/2019-11-04-github-badges.md

@@ -118,9 +118,6 @@ I started off by building my function for OpenFaaS Cloud on [The Community Clust
 
     # This generated my badge/handler.js and badge/handler.json files
     faas-cli new --lang node10-express badge
-
-    # The YAML file must be called stack.yml
-    mv badge.yml stack.yml
     ```
 
 * Add the dependencies
@@ -308,7 +305,7 @@ OpenFaaS Official functions:
 
 * [Bot to thank new Patreon backers](https://github.com/openfaas/backer-thankyou/)
 
-* [HTTPS short-URLs](https://github.com/openfaas/cloud-functions/blob/master/stack.yml) - we built a number of short/pretty-URLs for the community to use for joining Slack, Zoom calls and for [becoming an OpenFaaS Insider](https://insiders.openfaas.io/)
+* [HTTPS short-URLs](https://github.com/openfaas/cloud-functions/blob/master/stack.yaml) - we built a number of short/pretty-URLs for the community to use for joining Slack, Zoom calls and for [becoming an OpenFaaS Insider](https://insiders.openfaas.io/)
 
 The UK-based cloud company [Civo.com](https://civo.com/) has an OpenFaaS function on The Community Cluster which filters Twitter mentions and then forwards them onto their Slack community so that the team can engage better with their own community:
 

_posts/2019-12-03-asp-net-core.md

@@ -191,7 +191,7 @@ We should also create a `openfaas-api/.gitignore` file to prevent us committing
 
 Run: `cp .dockerignore .gitignore`
 
-* Create an OpenFaaS stack.yml file
+* Create an OpenFaaS stack.yaml file
 
 Let's use the OpenFaaS template called `dockerfile` to define a new template for the project and call it `api`.
 
@@ -201,7 +201,7 @@ faas-cli new --lang dockerfile api
 
 Now you'll see a folder generated called `api` containing a `Dockerfile` and `api.yml`
 
-Let's edit stack.yml and have it point at our `Dockerfile` we created earlier:
+Let's edit stack.yaml and have it point at our `Dockerfile` we created earlier:
 
 ```yaml
 version: 1.0
@@ -216,7 +216,7 @@ functions:
     image: api:latest
 ```
 
-* Let's rename the file to the default `stack.yml`
+* Let's rename the file to the default `stack.yaml`
 * And also change the `handler` folder to point at the existing folder
 * Then add our Docker Hub username or private Docker container registry as a prefix to `image:` 
 
@@ -233,7 +233,7 @@ functions:
 You should now have:
 
 ```
-./stack.yml
+./stack.yaml
 ./openfaas-api/
 ./openfaas-api/Dockerfile
 ./openfaas-api/Program.cs
@@ -438,7 +438,7 @@ That's fine, you can create different templates or you can just specify the runt
 
 * 12-factor configuration
 
-You can apply 12-factor configuration through the `environment` section of your OpenFaaS stack.yml file.
+You can apply 12-factor configuration through the `environment` section of your OpenFaaS stack.yaml file.
 
 See also: [Configure your OpenFaaS functions for staging and production](https://www.openfaas.com/blog/custom-environments/)