diff --git a/docs/cli/build.md b/docs/cli/build.md index b416d2d..36194db 100644 --- a/docs/cli/build.md +++ b/docs/cli/build.md @@ -219,7 +219,7 @@ The OpenFaaS CLI provides a `--build-option` flag which enables named sets of na There are two ways to achieve this: ```bash -faas-cli build --lang python3 --build-option dev [--build-option debug] +faas-cli build --lang python3-http --build-option dev [--build-option debug] ``` or in YAML: @@ -272,13 +272,13 @@ RUN apk --no-cache add curl ${ADDITIONAL_PACKAGE} \ There may be scenarios where a single native module needs to be added to a build. A single-package build option could be added as described above. Alternatively a package could be specified through a `--build-arg`. ```bash -faas-cli build --lang python3 --build-arg ADDITIONAL_PACKAGE=jq +faas-cli build --lang python3-http --build-arg ADDITIONAL_PACKAGE=jq ``` In the event a `build-option` is set the effect will be cumulative: ```bash -faas-cli build --lang python3 --build-option dev --build-arg ADDITIONAL_PACKAGE=jq +faas-cli build --lang python3-http --build-option dev --build-arg ADDITIONAL_PACKAGE=jq ``` The entries in the template's Dockerfile described in 1.0 above need to be present for this mode of operation. diff --git a/docs/openfaas-pro/builder.md b/docs/openfaas-pro/builder.md index c93dd59..f28d4a7 100644 --- a/docs/openfaas-pro/builder.md +++ b/docs/openfaas-pro/builder.md @@ -69,11 +69,11 @@ export PAYLOAD=$(kubectl get secret -n openfaas payload-secret -o jsonpath='{.da echo $PAYLOAD > $HOME/.openfaas/payload.txt ``` -Create a test function using the `python3` template, and set it to publish to `ttl.sh`, an ephemeral registry that doesn't require authentication: +Create a test function using the `python3-http` template, and set it to publish to `ttl.sh`, an ephemeral registry that doesn't require authentication: ```bash faas-cli new --prefix ttl.sh/test-images \ - --lang python3 py-fn + --lang python3-http py-fn ``` Now, publish an image using the remote builder: