I'm looking for a way to run a single job when I do

pulumi up

. I read somewhere that I should do a CronJob without a schedule but the typescript didn't like that. Any other suggestions?

You mean you want to run a Kubernetes Job each time you run

pulumi up

?

@limited-rainbow-51650 yes, exactly! It doesn't have to be a cronjob per se but I want to run something on each

pulumi up

. I tried working with

initContainers

but that runs every time a new pod is created.

At the moment, I lack a suggestion. Can you elaborate on your use case? Maybe it is possible to find a non-Pulumi alternative.

Of course! I'm in the process of moving our Magento2 server to Kubernetes and on deploys I need to run a few commands, for example

bin/magento setup:db-schema:upgrade

which is basically a db-migration. I only want to run this once per deploy. When I say "deploy" I mean

pulumi up

@dazzling-sundown-39670 I usually keep the db migrations out of a declarative Pulumi stack. Such an action is more imperative. When you build your infrastructure over multiple Pulumi projects/stack, the orchestrations happens more on a “workflow” level. Have a look at the recently announced alpha of the

Automation API

. See the #announcements channel for more info.

Okay thanks, that looks like a bit more work than I was hoping for but I'll look into it!

@dazzling-sundown-39670 try ArgoCD first. Spinnaker is a beast… 😉

Cheers!

@dazzling-sundown-39670 db migrations as a part of updates was definitely something we had in mind when designing automation api. Feel free to join us in #automation-api or reach out to me directly if you want some pointers.

@dazzling-sundown-39670 have you tried using a standard job, not a cronjob?

@lemon-agent-27707 cheers, I'll check it out! @billowy-army-68599 I haven't, but now I will! Thank you!

a job is one solution, also take a look at schemahero for a more robust solution: https://github.com/schemahero/schemahero