[feature] investigating applicability of ytt

[aegershman]

(To be entirely honest, I'm not 100% sure what the workflow for this would look like yet, just putting an issue here as a way to point this out. Feel free to close this whenever you feel fit.)

• https://developer.ibm.com/blogs/yaml-templating-tool-to-simplify-complex-configuration-management/
• https://github.com/k14s/ytt

I'm investigating using ytt as a way to templatize my concourse pipelines. I thought this might be an interesting project to check out and see if/how it could integrate to aviator.

Thanks for your time!

[herrjulz]

Hi @aegershman

very interesting. I talked to @nimakaviani recently about adding ytt support. I'm already investigating if I can integrate it somehow. I'll leave this issue open for ideas.

Thx very much for open this issue.

[herrjulz]

I played a little bit with ytt and I think it can be nicely integrated with Aviator. Still need to take a look at the code. The idea I have so far is to have ytt separated from the spruce config in the aviator.yml with the following concept:

• template (ytt)
• merge (spruce)
• modify (goml)
• squash (aviator)
• execute (fly|kubectl|others)

For executors I think I create a plug-in point and let them be added separately to Aviator. Something like aviator install ansible-executor.

Moreover, I thinking about to change the aviator yaml such that the order of the processes like template, merge, modify, squash can be defined by the user. Today, the order is strict: spruce->squash->execute

[cppforlife]

@aegershman off topic, but you may want to connect with @cdutra since he was playing around with ytt and concourse pipelines as well. yall might have some interesting things to share.

[prein]

@herrjulz Would you mind summarizing your thoughts / findings? Is ytt planned to be supported?