This is quite intentional. What exactly would printing the result yaml to stdout be good for? Not that I disagree, necessarily, but it sounds like an emerging hack :)

That's just a debug output. You already have the full resultyaml structure, because you need to feed it to resultsdb directive. So why don't just simply save it to a file if you need it? Our existing shell directive doesn't support feeding something to stdin at the moment, so the safest way right now (to avoid shell escaping issues) is to create save_results.sh that will safe the first argument received into a file of your choosing, and then call something like:

shell:
    - [ save_results.sh, '${resultsyaml}' ]

Of course you can also print it to stdout (just use cat or echo in the shell directive), but that doesn't sound like something that would help with reliable data processing (stdout can contain lots of other stuff).

Thank you for your hints, I misunderstood how the directives worked exactly! I now added a new directive that does what I need.