nice-butcher-6430208/09/2023, 10:43 AM
command unfortunately first create the new policy, then delete the old one but since the bucket can have only one policy attached to it, what really happens is that at the end the bucket policy is actually removed. The temporary solution I've found to this problem is to perform the pulumi up, then perform a pulumi refresh and after that another pulumi up. What istead I think could be useful at least in this case is to have a
flag for the cli to perform the delete operation before the create operation. A note on this, I tried with the flag
on the resource, but since I'm actually creating a new resource with a different ID, this is not solving the issue.
nice-butcher-6430208/09/2023, 1:15 PM
command, first pulumi create the new BucketPolicy (and I suppose attach it to the bucket) and then remove the old one. But working this way, the bucket results with no policy at all.
- Pulumi recognize this way the new policy I wanted to apply has been actually deleted in the
operation - and then re-do the
nice-butcher-6430208/09/2023, 1:43 PM
nice-butcher-6430208/10/2023, 9:56 AM