@thousands-hairdresser-72380 when you say you changed the parent child relationship, you mean as a resource option? If so, this is expected behaviour and you can use an alias to prevent a replacement
@billowy-army-68599
Yes as a resource option. Replacing isn’t an issue in itself.
The issue is it didn’t create two entities, it just modified the same property on the
Queue
entity.
So the order of operations was
1. Create the replacement
QueuePolicy
a. This equates to updating the
policy
attribute for the
Queue
b. This is not a separate entity but a property of the
Queue
2. Delete the previous
QueuePolicy
a. Since the
policy
is not a separate entity but a property of the
Queue
, it just deleted the
policy
attribute altogether.
The resolution ended up being running
pulumi refresh
so it detected that the policy had been deleted, then running
pulumi up
again.
b
billowy-army-68599
04/22/2022, 11:25 PM
Again, using an alias would have entirely prevented this
t
thousands-hairdresser-72380
04/25/2022, 3:06 PM
@billowy-army-68599
I’m not sure that an alias is the correct solution here.
To provide more context and evidence of that claim, I’ve created an issue here
Thank you for taking time to help out!
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.