https://pulumi.com logo
Join Slack
Powered by
This message was deleted.
# general
s
This message was deleted.
q
Those YAML files needs to exist on the 
git push
, so you'd use Pulumi to generate them and auto commit? I generally think auto-commits are an anti-pattern
g
Well, maybe this wasn’t clear: I would not use pulumi for this at all. Pulumi’s purpose is different, but the switch from k8s yamls to using TypeScript made me just thinking how I can get rid of those CI yaml mess.
I think I would generate them in a commit post-hook or simply run the generation manually via 
npm run
, some shell script or some CLI ….. Yeah it’s nasty having to run some “generate” step after every change, but I think I prefer this tradeoff over yaml-try-and-error and not having the ability to reuse things easily.
Running the “generate” step serves basically as a more powerful replacement for some ci yaml validator.
q
I use GitLab includes
g
I’m currently enabling pulumi deployment via gitlab in some of our repos, but I’m just repeating myself too much / copy and paste a lot, even if making using of yaml anchors etc. a lot.
q
but there's also some nice systems that use Kubernetes CRDs for build pipelines
Such as InfraBox, Knative, and Avro
Oh, and I shouldn't forget Brigade, which lets you code build pipelines in JS
g
yeah i’m aware of gitlab includes, but they don’t support yaml anchors in the include file, so I don’t think this will help me to the extent I want it to.
infrabox uses JSON config, how’s that better?
I used to work for SAP btw ^^
yeah brigade is a nice “idea” but I don’t think it’s nicely executed unfortunately… I tried it a couple of months ago but was very confused by how it works
The CI / Automation systems I know of which support some higher level language are: Jenkins (Groovy DSL), Teamcity (Kotlin Script), buildbot (python), Jenkins X, Brigade. Unfortunately each of them is fully self-hosted. It’d rather use one of those mature managed, docker oriented services like circle and gitlab 😕
ok for gitlab there’s an open issue to allow dynamic config file generation and a few folks in that issue have apparently implemented some config file generation already: https://gitlab.com/gitlab-org/gitlab-ce/issues/45828
just not in typescript yet
q
Oh, I thought InfraBox was CRDs now. I was incorrect 🙂
g
Argo is CRDs
q
Oh
That 
seed
option would be awesome
Argo, that's it's name! I think I called it Avro 😂
I keep looking at it and watching YouTube demonstrations, but I haven't moved away from GitLab CI yet
I very keen to separate CI from CD
CI - Build OCI Image CD - Deploy with Pulumi
That's what I want
g
Avro is a file format 😛
By chance we actually use both Argo and Avro in my company
Argo is actually pretty nice, I think eventually I might just replace gitlab ci with it haha. It’s just that it doesn’t really have good UI integration to gitlab or github…
Currently we use argo for some machine learning pipelines which is slightly different use case to CI / CD, but there are intersections.
oh I forgot, Airflow (python) technically also could be used for CI/CD, but just like argo its more build for data pipelines than CI/CD.
Anyways, I gotta go. I think I might build some MVC for generating gitlab-ci yamls with typescript in the coming days.
can’t be that hard.
q
Best of luck 👍
b
I have an example of this for circle ci. Nothing that sources it though so our devs are forced to setup pre-commit hooks
3 Views
Open in Slack
PreviousNext
Powered by