TriggerMesh functions are used to perform transformations on events using code written in Python, NodeJS, or Ruby. These are not a replacement for full blown FaaS services, but provide a lot of flexibility when transforming events, particularly to those familiar with one of the support languages.
For low-code style transformations in JSON, refer to JSON Transformation.
TriggerMesh functions with
tmctl is a work in progress and not currently supported.
Furthermore, note that TriggerMesh Functions are opinionated and simple. They are aimed to be used for event transformation and do not support external dependencies. Functions that may need external dependencies are best served with something like AWS Lambda or Knative Functions.
See the Kubernetes object reference for the Function reference docs.
Common function configuration options
Below are some parameters you can configure in the function CRD, that apply to all function runtimes.
||Boolean. If true, function will be allocated a public URL so that it can be accessed from outside the cluster. Default is false.|
||Can be used to modify the values of CloudEvents attributes in the event return by the function back to the caller.|
||Boolean. If false, the function will wrap what is returned by the function into the
||Name of the function to be used as an entry point in the code.|
||Currently supported runtime values are