Hi Espen,
I'm currently working on a solution for this, this falls under the "Data-capture plugin" feature on our Trello board:
https://trello.com/c/oU8OjZoH
For the benefit of everyone not interested in reading through commit logs, here's the TL;DR progress update:
* new Plugins can be used to filter log lines coming from steps, called LogFilterPlugins
* a new shared "data context" can be used to save data values grepped/parsed from those logs
* steps in a workflow can use those data values in the same way as current "context" variables.
For example, I've added a basic "key value capture" filter plugin, so this script
#!/bin/bash
echo RUNDECK:DATA:mydata=somevalue
will capture a variable ${data.mydata}, which can be used in subsequent steps. If you are executing steps on the same node, the `${data.mydata}` comes
from the node same node that echoed it previously. If you want data from a different node, currently you can do `${data.mydata@nodename}` to
read the value from a separate node.
There's a lot more that these filter plugins can do, for example modifying, adding, or removing log events.
Another example plugin I've created is a "Mask Passwords Filter" plugin. This uses the known "private"/password data in the execution
context and replaces any values seen in emitted logs with a "*****".
When will this be ready, you ask? It will be part of the 2.9.0 release, but at this time the ETA is not set.
Any feedback is appreciated.
cheers,
Greg