This message was deleted.

hmm is there a reason why you aren't using something like

envFrom

instead?

So I am also using

envFrom

with that

ConfigMap

. 🙂 The use-case here is that this deployment needs to launch new pods that also mount in that

ConfigMap

, so I need to know the name to bind to.

but the code you posted above does not use

envFrom

what's your configmap resource look like? i believe if you do NOT use the

metadata.name

property (so you let Pulumi autoname the resource for you) it will handle it the way you want where it creates the new configmap and auto replace the pods before removing the old configmap

Whether or not there's an

envFrom

shouldn't affect the execution, I don't think. This is letting Pulumi name the resource for me - it's generating

metadata.name

on-the-fly. It's also possible that this only happens when the create operation fails for the deployment, since I noticed this earlier today when an updated failed partway through. Maybe it's not a generic race, but rather a poorly-handled error?

Whether or not there's an 

envFrom

 shouldn't affect the execution, I don't think.

sorry I should have been more clear that my question about this was tangential.

This is letting Pulumi name the resource for me - it's generating 

metadata.name

 on-the-fly.

thanks for confirming! I wasn't sure since the code you posted just has

...

where the configmap specs are

It's also possible that this only happens when the create operation fails for the deployment

huh? i thought your issue was you saw Pulumi would delete the old configmap before making any changes to the deployment.