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

Anyone who can shed some light on this would be greatly appreciated

<@U02GCR8KHL4> you can add an annotation to the job to make sure pulumi doesn't wait for it

image.png

You can read more about it here<https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/>

Oh <@U02AB9VLGJH> - one more quick question. Does the Job resource remain in Pulumi state after the stack create/update is complete? Or do I need to delete it afterwards?

Yes it does remain in Pulumi state. That is by design. Pulumi is declarative state management of resources.

Is there a reason you want to remove it?

Hi <@U02AB9VLGJH> sorry I missed this somehow - thanks for getting back to me. Normally not, but I just figured since it’s a Job, which as a finite life, that Pulumi might be replicating the behavior. But no, I can simply remove it when I’m done with it, so it’s fine.