Merge pull request #38798 from rh-max/srvls-func-yaml-updates

SRVOCF-361: Updates to the func.yaml reference documentation

Author: abrennan89

modules/serverless-functions-func-yaml-fields.adoc

@@ -5,11 +5,33 @@ Many of the fields in `func.yaml` are generated automatically when you create, b
 
 == builder
 
-The `builder` field specifies the Buildpack builder image to use when building the function. In most cases, this value should not be changed. When you do change it, use a value that is listed in the `builderMap` field.
+The `builder` field specifies the Buildpack builder image to use when building the function. In most cases, this value should not be changed. When you do change it, use a value that is listed in the `builders` field.
 
-== builderMap
+== builders
 
-Some function runtimes can be built in multiple ways. For example, a Quarkus function can be built for the JVM or as a native binary. The `builderMap` field contains all of the builders available for a given runtime.
+Some function runtimes can be built in multiple ways. For example, a Quarkus function can be built for the JVM or as a native binary. The `builders` field contains all of the builders available for a given runtime.
+
+== buildEnvs
+
+The `buildEnvs` field enables you to set environment variables to be available to the environment that builds your function. Unlike variables set using `envs`, a variable set using `buildEnv` is not available during function runtime.
+
+You can set a `buildEnv` variable directly from a value. In the following example, the `buildEnv` variable named `EXAMPLE1` is directly assigned the `one` value:
+
+[source,yaml]
+----
+buildEnvs:
+- name: EXAMPLE1
+  value: one
+----
+
+You can also set a `buildEnv` variable from a local environment variable. In the following example, the `buildEnv` variable named `EXAMPLE2` is assigned the value of the `LOCAL_ENV_VAR` local environment variable:
+
+[source,yaml]
+----
+buildEnvs:
+- name: EXAMPLE1
+  value: '{{ env:LOCAL_ENV_VAR }}'
+----
 
 == envs
 
@@ -120,6 +142,28 @@ The `image` field sets the image name for your function after it has been built.
 
 The `imageDigest` field contains the SHA256 hash of the image manifest when the function is deployed. Do not modify this value.
 
+== labels
+
+The `labels` field enables you to set labels on a deployed function.
+
+You can set a label directly from a value. In the following example, the label with the `role` key is directly assigned the value of `backend`:
+
+[source,yaml]
+----
+labels:
+- key: role
+  value: backend
+----
+
+You can also set a label from a local environment variable. In the following example, the label with the `author` key is assigned the value of the `USER` local environment variable:
+
+[source,yaml]
+----
+labels:
+- key: author
+  value: '{{ env:USER }}'
+----
+
 == name
 
 The `name` field defines the name of your function. This value is used as the name of your Knative service when it is deployed. You can change this field to rename the function on subsequent deployments.
@@ -131,7 +175,3 @@ The `namespace` field specifies the namespace in which your function is deployed
 == runtime
 
 The `runtime` field specifies the language runtime for your function, for example, `python`.
-
-== template
-
-The `template` field specifies the type of the invocation event that triggers your function. You can set it to `http` for triggering with plain HTTP requests or to `events` for triggering with cloud events.