Chaps,

we were discussing this many times in the past, and as with the type-restriction, I think this is the right time to get this done, actually.

It sure ties to the fact, that I'm trying to put together Taskotron-continuously-testing-Taskotron together - the idea here being that on each commit to a devel branch on any of the Taskotron components, we will spin-up a testing instance of the whole stack, and run some integration tests.

To do this, I added a new consumer to Trigger (https://phab.qa.fedoraproject.org/D1110) that eats Pagure.io commits, and spins jobs based on that.

This means, that I want to have the repo, branch and commit id as input for the job, thus making yet-another-nasty-hack to pass the combined data into the job (https://phab.qa.fedoraproject.org/D1110#C16697NL18) so I can hack it apart later on either in the formula or in the task itself.

It would be very helpfull to be able to pass some structured data into the task instead.

I kind of remember that we agreed on json/yaml. The possibilities were either reading it from stdin or file. I don't really care that much either way, but would probably feel a bit better about having a cli-param to pass the filename there.

The formulas already provide a way to 'query' structured data via the dot-format, so we could do with as much as passing some variable like 'task_data' that would contain the parsed json/yaml.

What do you think?

Joza