Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
m
most-lighter-95902
02/22/2022, 6:00 AMAnyone who can shed some light on this would be greatly appreciated
f
fast-florist-41572
02/22/2022, 7:03 PM@most-lighter-95902 you can add an annotation to the job to make sure pulumi doesn't wait for it
You can read more about it herehttps://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/
m
most-lighter-95902
02/22/2022, 7:54 PMAh nice - thank you!
Oh @fast-florist-41572 - 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?
f
fast-florist-41572
02/23/2022, 7:03 AMYes 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?
m
most-lighter-95902
02/26/2022, 5:36 AMHi @fast-florist-41572 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.
Thanks!