This is all an

Question

This is all an <https meta stackexchange com questions 66377 what is the xy problem|XY Problem> though the root problem is I have a helm chart ugh that sometimes hangs double ugh when I try to Pulumi deploy it and when it hangs it doesn t serialize the state and checkpoints back This then puts me in a really bad state because I have a bunch of dangling resources that I can t import correctly How do I handle this

red-match-15116 · Answer

I think the Recovering from an Interrupted Update + Manually Editing Your Deployment sections might be helpful here <https www pulumi com docs troubleshooting interrupted update recovery>

orange-policeman-59119 · Answer

I think that ends up being a huge amount of work when what I really want is behavior like Oh this resource is already deployed with the right namespace and name Okay I ll import it automatically

orange-policeman-59119 · Answer

I can t stress this enough when the helm chart hangs in our CI system the state is completely absent

orange-policeman-59119 · Answer

I cannot edit my deployment because the CI system kills the process and no checkpointed state is persisted anywhere

orange-policeman-59119 · Answer

we have a 1 hour timeout on our CI jobs

red-match-15116 · Answer

I hear ya I think folks have hit this same issue but perhaps want a different outcome behavior Feel free to upvote if that s in line with what you d like to see or open up an issue if it s not

white-balloon-205 · Answer

< orange policeman 59119> just to check are you using the Pulumi service backend of a cloud storage blob backend gt it hangs and doesn t serialized the checkpoint gt This should never happen I d love to understand exactly what is causing this for you

orange-policeman-59119 · Answer

Cloud storage blob backend

orange-policeman-59119 · Answer

I switched to basically doing rsync $bucket $localdir pulumi login local $localdir do operation pulumi logout rsync $localdir $bucket

orange-policeman-59119 · Answer

I was deploying the `prometheus operator` Helm chart to a cluster and a CRD was already defined throwing errors which would then hang

orange-policeman-59119 · Answer

I also think there was some Google Cloud Storage rate limiting happening which caused a hang when I tried running directly against the GCS bucket backend I observed a lot of 429 rateLimitExceeded errors in my console

white-balloon-205 · Answer

Yeah there have been many reports on this recently Appears something changed in the GCS side recently Discussing how to address that for Pulumi at <https github com pulumi pulumi issues 4258|https github com pulumi pulumi issues 4258> I would guess that is the root of the problems here