@@ -23,18 +23,18 @@ include::snippets/technology-preview.adoc[leveloffset=+1]
2323
2424. In each namespace where you want to run {pipelines-shortname} and deploy a function, you must create the following resources:
2525
26- .. Create the functions buildpacks Tekton task to be able to build the function image :
26+ .. Create the `s2i` Tekton task to be able to use Source-to-Image in the pipeline :
2727+
2828[source,terminal]
2929----
30- $ oc apply -f https://raw.githubusercontent.com/openshift-knative/kn-plugin-func/serverless-1.22 .0/pipelines/resources/tekton/task/func-buildpacks /0.1/func-buildpacks .yaml
30+ $ oc apply -f https://raw.githubusercontent.com/openshift-knative/kn-plugin-func/serverless-1.25 .0/pipelines/resources/tekton/task/func-s2i /0.1/func-s2i .yaml
3131----
3232
3333.. Create the `kn func` deploy Tekton task to be able to deploy the function in the pipeline:
3434+
3535[source,terminal]
3636----
37- $ oc apply -f https://raw.githubusercontent.com/openshift-knative/kn-plugin-func/serverless-1.22 .0/pipelines/resources/tekton/task/func-deploy/0.1/func-deploy.yaml
37+ $ oc apply -f https://raw.githubusercontent.com/openshift-knative/kn-plugin-func/serverless-1.25 .0/pipelines/resources/tekton/task/func-deploy/0.1/func-deploy.yaml
3838----
3939
4040. Create a function:
@@ -51,17 +51,15 @@ $ kn func create <function_name> -l <runtime>
5151[source,yaml]
5252----
5353...
54- build: git <1>
5554git:
56- url: <git _repository_url > <2 >
57- revision: main <3 >
58- contextDir: <directory _path > <4 >
55+ url: <git _repository_url > <1 >
56+ revision: main <2 >
57+ contextDir: <directory _path > <3 >
5958...
6059----
61- <1> Required. Specify `git` build type.
62- <2> Required. Specify the Git repository that contains your function's source code.
63- <3> Optional. Specify the Git repository revision to be used. This can be a branch, tag or commit.
64- <4> Optional. Specify the function's directory path if the function is not located in the Git repository root folder.
60+ <1> Required. Specify the Git repository that contains your function's source code.
61+ <2> Optional. Specify the Git repository revision to be used. This can be a branch, tag, or commit.
62+ <3> Optional. Specify the function's directory path if the function is not located in the Git repository root folder.
6563
6664. Implement the business logic of your function. Then, use Git to commit and push the changes.
6765
0 commit comments