riff is for functions

riff is for functions

  • Docs
  • Blog
  • GitHub
  • Slack

›Functions

Version (v0.3.x)

  • v0.6.x (snapshot)
  • v0.5.x
  • v0.4.x

Getting Started

  • Pick your environment
  • GKE
  • Minikube
  • Docker for Mac
  • Docker for Windows

CLI Reference

  • riff
  • riff version
  • riff completion
  • System

    • riff system
    • riff system install
    • riff system uninstall

    Namespace

    • riff namespace
    • riff namespace cleanup
    • riff namespace init

    Functions

    • riff function
    • riff function build
    • riff function create
    • riff function update

    Services

    • riff service
    • riff service create
    • riff service delete
    • riff service invoke
    • riff service list
    • riff service status
    • riff service update

    Subscriptions

    • riff subscription
    • riff subscription create
    • riff subscription delete
    • riff subscription list

    Channels

    • riff channel
    • riff channel create
    • riff channel delete
    • riff channel list
Edit

riff function create

riff function create

Create a new function resource

Synopsis

Create a new function resource from the content of the provided Git repo/revision or local source.

The --invoker flag can be used to force the language runtime and function invoker that is added to the function code in the build step. The resulting image is then used to create a Knative Service (service.serving.knative.dev) instance of the name specified for the function.

Images will be pushed to the registry specified in the image name. If a default image prefix was specified during namespace init, the image flag is optional. The function name is combined with the default prefix to define the image. Instead of using the function name, a custom repository can be specified with the image set like --image _/custom-name which would resolve to docker.io/example/custom-name.

From then on you can use the sub-commands for the service command to interact with the service created for the function.

If --env-from is specified the source reference can be configMapKeyRef to select a key from a ConfigMap or secretKeyRef to select a key from a Secret. The following formats are supported:

--env-from configMapKeyRef:{config-map-name}:{key-to-select}
--env-from secretKeyRef:{secret-name}:{key-to-select}
riff function create [flags]

Examples

  riff function create square --git-repo https://github.com/acme/square --artifact square.js --image acme/square --invoker node --namespace joseph-ns
  riff function create tweets-logger --git-repo https://github.com/acme/tweets --image acme/tweets-logger:1.0.0

Options

      --artifact path                  path to the function source code or jar file; auto-detected if not specified
      --dry-run                        don't create resources but print yaml representation on stdout
      --env stringArray                environment variable expressed in a 'key=value' format
      --env-from stringArray           environment variable created from a source reference; see command help for supported formats
      --git-repo URL                   the URL for a git repository hosting the function code
      --git-revision ref-spec          the git ref-spec of the function code to use (default "master")
      --handler method or class        the name of the method or class to invoke, depending on the invoker used
  -h, --help                           help for create
      --image repository/image[:tag]   the name of the image to build; must be a writable repository/image[:tag] with credentials configured
      --invoker language               invoker runtime to override language detected by buildpack
  -l, --local-path path                path to local source to build the image from; only build-pack builds are supported at this time
  -n, --namespace namespace            the namespace of the service
      --sub-path string                the directory within the git repo to expose, files outside of this directory will not be available during the build
  -v, --verbose                        print details of command progress
  -w, --wait                           wait until the created resource reaches either a successful or an error state (automatic with --verbose)

Options inherited from parent commands

      --kubeconfig path   the path of a kubeconfig (default "~/.kube/config")
      --master address    the address of the Kubernetes API server; overrides any value in kubeconfig

SEE ALSO

  • riff function - Interact with function related resources
← riff function buildriff function update →
  • riff function create
    • Synopsis
    • Examples
    • Options
    • Options inherited from parent commands
    • SEE ALSO
riff is for functions
Docs
Versions
Community
BlogGitHubSlackKnativeTwitter
More
Privacy PolicyTerms of UseCode of Conduct
Deployed by Netlify
Copyright © 2021 VMware, Inc