Open stefanprodan opened 1 year ago
how to create a Timoni module from scratch with
timoni mod init
I find that the full-blown podinfo piece this command currently generates is a bit too complex for getting started, ideally, I think it should write out a bare minimum, perhaps just a skeleton. Of course, you need to strike a balance here, but perhaps we could try to use a deployment with a few basic parameters, e.g. namespace, labels, image & replicas?
Hey @stefanprodan this looks great, how have I only just discovered this project! It aligns really closely with some discussions I've been having about Helm improvements such as using CUE to create the values YAML & schema, Cosign signing, and separating chart developer and chart consumer responsibilities.
I have a couple of questions, apologies if I've missed them as a latecomer.
v1.0.01
-> v1.0.1
)I used the documentation to do this and found it pretty complete so I would say this can be closed.
Only thing was this:
explain how the user-defined values.cue files are merged and why Timoni had to break CUE immutability
It might be in there in some way, but it didn't come across to me when going through things.
The guide can be based on
examples/podinfo
and should include:timoni mod init
templates/config.cue
and how it relates tovalues.cue
timoni.cue
and how it relates totimoni build
values.cue
files are merged and why Timoni had to break CUE immutability