https://pulumi.com logo
#general
Title
# general
f

flat-guitar-86436

09/12/2019, 3:59 PM
alright so after working with Pulumi programs for a while on my local, it’s time to put everything in my CI.. oh wait, yaml files.. I got so spoiled by not working with disgusting yaml files that writting my CI sequence in it feels weird and unefficient… any thoughts? I’d love to have CI/CD as code
maybe this is an area where pulumi would want to go? I could see another type of program that would represent the buids, triggers, etc 🙂
b

bitter-dentist-28132

09/12/2019, 4:03 PM
CI sequence?
g

gorgeous-egg-16927

09/12/2019, 4:11 PM
Not sure what CI system you’re using, but https://www.pulumi.com/docs/guides/continuous-delivery/ might have some useful info for you
f

flat-guitar-86436

09/12/2019, 4:14 PM
I use CircleCI now yes
I would see a pulumi program that represent a build sequence
b

best-xylophone-83824

09/12/2019, 4:15 PM
there is THE program for this already: https://buildbot.net/
f

flat-guitar-86436

09/12/2019, 4:16 PM
@best-xylophone-83824 that’s in python language right? it looks nice
b

best-xylophone-83824

09/12/2019, 4:17 PM
yes it is in python and is oldest player in this market
👍 1
g

gorgeous-egg-16927

09/12/2019, 4:17 PM
Another possibility is implementing a pulumi provider for whatever CI backend so that you could manage it with pulumi. If there’s an existing terraform provider, it’s fairly easy to generate a pulumi one from that
f

flat-guitar-86436

09/12/2019, 4:17 PM
I just think that Pulumi covering CI/CD is the next logical step, I have my stacks ready to be automated.. why not have a pulumi program that takes trigger A, update pulumi stack etc
basically I want to avoid writting yaml files, I would want to write my CI/CD sequence with TypeScript 😂
I’m curious, what CI/CD does the pulumi team use internally? @gorgeous-egg-16927
g

gorgeous-egg-16927

09/12/2019, 4:22 PM
Currently a combination of TravisCI and GitHub actions. But I agree with your points 😄
👍 1
f

flat-guitar-86436

09/12/2019, 4:24 PM
I have the following pulumi “programs” right now: - identity (AWS Org, Accounts, Users, base IAM) - infra (EKS cluster, ECR, etc) - auth (authentication + permissioning layer) - apps (service and application to be run on the cluster)
a “ci” pulumi program would be awesome sauce, since I could reference the other stacks and trigger updates “pulumi up” based on conditions (like what trigger do I have)
this would be soooo awesome to write in a normal language
in over 7 years of workin in IT, my most miserable moments have been “configuring the goddamn CI”
b

bitter-dentist-28132

09/12/2019, 4:36 PM
by CI sequence, i guess you mean running all the stacks one after the other?
f

flat-guitar-86436

09/12/2019, 4:59 PM
I mean, like the CI we know 1. trigger happens (git or manual) 2. depending on condition (what branch, what trigger) run whatever you need, including “pulumi up” on pulumi programs that needs to be updated
Joe Duffy pointed me to: https://atomist.com
but the paradigm they use.. is very very different from what we are used to.. anyway, it’s worth having a look