JSON-e

[djmitche]

JSON-e is a language for parameterizing data structures. It should be the standard way that TaskCluster tasks are generated from templates (replacing rudimentary text substitution in YAML or JSON files).

https://github.com/taskcluster/json-e

This involves both implementing JSON-e itself, and deploying it for use in a bunch of contexts:

• JS implementation
  • TC-Github's .taskcluster.yml
  • Mozilla-taskcluster's .taskcluster.yml
  • TC-Hooks
    • Schedule in response to pulse messages, parameterized on their content (could replace mozilla-taskcluster!!)
    • Allow triggerTask calls to include a payload which is used to parameterize the task
• Python Implementation
  • Parameterizing Decision, Action, and Cron Tasks (in-tree)
  • Re-parameterizing decision tasks in Chain-of-trust validation (scriptworker)

Implementation Tracking: bug 1372600

[djmitche]

Per discussion at the SF all-hands, we're temporarily scaling this back to just the decision/action bits. The rest is still planned and certainly open for implementation by someone who is interested, but at the moment nobody is working on it.

[gregarndt]

Closing out issue, this I believe has been completed now.

[djmitche]

Not really - the decision/action task bits are done, but the hooks, tc-github, and scriptworker bits are not.

[gregarndt]

ah sorry, I meant to close a different one.

[djmitche]

Remaining:

• hooks -- that's Allow hooks to be triggered by pulse messages #66
• scriptworker -- not a TC thing (and underway AIUI)
• tc-github bug 1335915. I don't think that needs an RFC to track it.

Aside from that, JSON-e itself is pretty much stable.

[djmitche]

This RFC is stored as rfcs/0008-JSON-e.md