Piping conversion extensions


Is it possible to pipe / daisychain conversion extensions?

Something like:

  • Starlark Language Extension produces a data structure containing paths stanzas, understood by the Paths Changed Extension
  • Paths Changed Extension processes the output of the Starlark Language Extension and produces a data structure understood by the Drone server

The use case is being able to deal with mono-repos with something like the Paths Changed Extension (or another extension) but have it all managed in Starlark to keep the pipeline code DRY.

My current understanding is that only one conversion extension is supported by the Drone server and therefore what I would like to achieve might not be possible at this stage. If that’s the case, would you consider putting on the product roadmap?