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

I believe it's wait for it to complete. We have Deployment updates block on database migration Jobs in our Pulumi program, and it works great.

Yes, the default behavior is to wait for readiness. You can see details of any readiness checks for a resource in the API docs: <https://www.pulumi.com/registry/packages/kubernetes/api-docs/batch/v1/job/#job>

You can disable the wait behavior by setting the `<http://pulumi.com/skipAwait|pulumi.com/skipAwait>` annotation on the resource.

I have a question, how do you block the deployment? Do I have to keep the job at the start of `index` file and then keep everything else in an `if` condition like this
```if (dbMigrationJob.status.conditions[0].type.apply(t =&gt; t === 'Complete')) {
    // run everything else like creating new image, pushing to ecr, creating deployment,etc
}```

&gt; how do you block the deployment?
If I understand your question correctly, you need to specify the Job as a resource dependency. <https://www.pulumi.com/docs/intro/concepts/resources/options/dependson/> has more information on this.