I ve noticed that sometimes Pulumi will take multiple runs t

Question

I ve noticed that sometimes Pulumi will take multiple runs to complete all of its tasks Is this normal or expected in some situations

steep-toddler-94095 · Answer

It shouldn t normally take more than a single run to complete everything It s likely it s not able to draw the dependency tree correctly Sometimes it s due to an obvious oversight in the user s code and other times it could be due to something trickier for example a Docker image s baseImageName is known before creating the image so Pulumi will attempt to update a Deployment before building the image If you have trouble figuring out what s going on if you give more specifics on the tasks that don t run the first time maybe we can help

strong-helmet-83704 · Answer

Admittedly this only seems to happen with larger more complex dependency structures Is there some way we can explicitly signal to Pulumi resources that it should depend on something else

steep-toddler-94095 · Answer

yeah there s the `dependsOn` property <https www pulumi com docs intro concepts resources options dependson >

strong-helmet-83704 · Answer

e g we have a resource which requires an eip we perform a change which tries to create a new natgw which tries to associate the eip but the eip is still associated until the natgw releases it If we could instruct Pulumi to delete the natgw before it creates a new one that would probably fix this

strong-helmet-83704 · Answer

I think technically in this case i need to specify ```delete before replace=True```

strong-helmet-83704 · Answer

Why is it that when a resource is renamed Pulumi wants to re create the resource

steep-toddler-94095 · Answer

Pulumi needs to keep track of the mapping between its representation in Pulumi statefile with the resource s UID in the cloud and the resources name is part of the identifier If you change the identifier it counts as a removal of the resource associated with the old identifier and the addition of a resource with the new identifier If you try to think about how one might implement it so that it doesn t delete the old resources and simply adopts the old resources state into the new ones you ll find that it s impossible to guarantee the desired result 100 of the time without additional information on how exactly to do this remapping Luckily Pulumi allows you to do this through <https www pulumi com docs intro concepts resources options aliases |aliases>

strong-helmet-83704 · Answer

Great point on the implementation I will check out aliases

strong-helmet-83704 · Answer

I m setting ```opts=pulumi ResourceOptions delete before replace=True provider=provider options ``` on the natgw which binds to an eip but a rename operation still fails It still tries to create the natgw before deleting the old one all creates are listed before the deletes

steep-toddler-94095 · Answer

by rename do you mean renaming the Pulumi resource not the AWS resource just making sure i understand if you do mean renaming the Pulumi resource basically the first parameter in the class instantiation then I dont think the `delete before replace` parameter handles that case It s meant for cases where the Pulumi URN stays the same but you are trying to change an immutable property of the resource which the cloud provider requires that it be recreated If you are trying to rename the Pulumi resource without changing the cloud resource you should use the alias property for this

strong-helmet-83704 · Answer

Yes I mean renaming the pulumi resource This is not a real requirement but something i ran into Perhaps `retain on delete=True` will maintain the natgw with the eip attached

strong-helmet-83704 · Answer

curiously i notice ` retainOnDelete true` specified in the state but delete before replace was not

steep-toddler-94095 · Answer

Renaming it with alias wont even trigger a recreate so these properties dont even come into the picture