Template composition

Problem statement

One problem we see with Coral is a potential of template explosion. This will typically happen if there are to many special variations in how software gets delivered.

Also, developers might like to start off with a simple repository and then later evolve it to a fully fledged software delivery pipeline.

Suggested solution

In order to support this we suggest having the ability to compose templates together and be able to apply them when appropriate in the product lifecycle.

Value proposition

The flexibility of composition makes it so that one team can own, say, the build parts of an aligned setup, while another team can maintain the release parts of the pipeline. It would reduce template explosion and still allow manageable variability.