thousands-hairdresser-72380
04/22/2022, 2:06 PMaws.sqs.QueuePolicy
.
When it was updated, it created a replacement
and deleted the old one.
Turns out that they’re not distinct entities, they’re just a property of the aws.sqs.Queue
.
That means creating a replacement then deleting the prior essential just deleted the property all together, thus breaking our workflow and losing a few hours of messages for the Queue.
This seems to be a bug in the update strategy.
Should I create an issue on pulumi/pulumi-aws
or am I missing something?billowy-army-68599
thousands-hairdresser-72380
04/22/2022, 2:34 PMQueue
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.billowy-army-68599
thousands-hairdresser-72380
04/25/2022, 3:06 PM