Dexter John Genterone

I don't think it's enabled in our latest installation.

A few things I think we need to improve on the API. 1. Create separate models for the API and the controllers. Right now the API, controller, and the datastore....

> 1. breakdown the models from one big structure (pipeline contains builds contains stages) into several entries in etcd. This would pattern TPR well. Idea is when TPR is available,...

Still thinking about the users. should pipelines be linked to users? eg. 2 users accessing the same repo can have separate pipelines? which means a repo can have several hooks...

> I'm wondering if builds are something that lives as a resource. Its something thats generated as part of a running a pipeline but its never edited after its finished....

The idea of having the builds as a resource is that the API can just edit the build's definition marking a stage as `READY` for the controller to pick up...

A general idea of how the new spec will look like as well as updates for the way the pipeline resources are stored in etcd (making it closer to K8S...

the new pipeline format will have something similar too (after the api refactor).