Memory action

The action is used to flush the result into an in-memory topic so that it can be consumed by the memory source. The topic is like pubsub topic such as mqtt, so that there could be multiple memory sinks which publish to the same topic and multiple memory sources which subscribe to the same topic. The typical usage for memory action is to form rule pipelines.

Below is a sample memory action configuration:

{
  "memory": {
    "topic": "devices/result"
  }
}

Below is another sample for dynamic topic action:

{
  "memory": {
    "topic": "{{.topic}}"
  }
}

Data Templates

::: v-pre The data transfer between the memory action and the memory source is in internal format and is not coded or decoded for efficiency. Therefore, the format-related configuration items of the memory action are ignored, except for the data template. The memory action can support data templates to vary the result format, but the result of the data template must be in the object form of a JSON string, e.g. "{\"key\":\"{{.key}}\"}". JSON strings in the form of arrays or non-JSON strings are not supported. :::