Hi!
Please take a look at the JQ-JSON logfilter filter plugin here, it’s designed for this use case. Let me share an job example with this plugin:
- defaultTab: nodes description: '' executionEnabled: true id: 7c996dc1-47f7-4095-987c-65c5e649432c loglevel: INFO name: newtest nodeFilterEditable: false plugins: ExecutionLifecycle: {} scheduleEnabled: true sequence: commands: - plugins: LogFilter: - config: extraQuotes: 'false' filter: . logData: 'true' prefix: result type: json-mapper script: |- echo "{ \"a1\": { \"project\": \"2020\", \"instance\": \"spanner\" }, \"a2\": { \"project\": \"2021\", \"instance\": \"driver\" }, \"a3\": \"test\" }" - exec: echo ${data.a3} - exec: echo ${data.a1.project} keepgoing: false strategy: node-first uuid: 7c996dc1-47f7-4095-987c-65c5e649432cCheck the result here (tested on Rundeck 5.5.0)
Please look at this doc entry to learn how to install no-bundled plugins (basically, download the jar file located here and save it on the $RDECK_BASE/libext directory, you don’t need to restart the Rundeck instance).
Hope it helps!