No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<@UGA2L4GNB> no, but <@UE1LN7A22> might be working on something like this

Yeah, we don’t have await logic implemented yet for `Job`s. It’s on my TODO list

<@UE1LN7A22> That's great! Is there an ETA when it can be released? I'll need this to finish the POC

Hmm, it shouldn’t be that hard to implement, but I’ve got a few other things on my plate right now. How urgent is it for you? Current plan would be sometime in the next month most likely.

<@UGA2L4GNB> Would you mind opening an issue with your use case and how you’d like it to work? <https://github.com/pulumi/pulumi-kubernetes/issues/new>

Specifically, is this a one-time Job, or would it need to run on every update, etc. I haven’t thought through the details yet, but Job is a bit of an odd resource.

When I was at Heptio this was something joe and I argued about a lot. Joe’s position was that `Job` semantics can’t be known _a priori_ and therefore should never be awaited.

That’s likely true in general, but I bet it’s something we could make configurable to accommodate use cases like this.

Yeah... db migrations are generally a weird case, but having it nicely wrapped in pulumi will help a lot.
Actually, it can be done just by running a pod to completion but jobs are more convenient here

Here's the ticket: <https://github.com/pulumi/pulumi-kubernetes/issues/449>.

Thanks guys for the rapid responses!