most-state-94104
05/16/2022, 1:15 PM+ aws:s3:Bucket aaa creating
+ aws:s3:Bucket aaa creating error: 1 error occurred:
+ aws:s3:Bucket aaa **creating failed** error: 1 error occurred:
Diagnostics:
aws:s3:Bucket (aaa):
error: 1 error occurred:
* Error creating S3 bucket: BucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it.
status code: 409, request id: Q3A6YB3N22Y5T7WW, host id: huiDWKeYcWdOUbIIjq/h4RlUSNCXA1yQG0l85af5uXLaZpVFsnHXVD5lUkP0QRmGTiPFLajBiwo=
How can I tell pulumi to recognise the existing bucket so that it doesn’t try to delete and recreate it? I get the same error when I run pulumi locally (v3.32.1) and through a github action (v3.31.0)victorious-church-57397
05/16/2022, 1:21 PMmost-state-94104
05/16/2022, 1:22 PMvictorious-church-57397
05/16/2022, 1:22 PMpulumi refresh
most-state-94104
05/16/2022, 1:22 PMvictorious-church-57397
05/16/2022, 1:23 PMmost-state-94104
05/16/2022, 1:27 PM~ aws:s3:Bucket aaa refreshing
@ previewing update.....
+ aws:s3:Bucket aaa create
- aws:s3:Bucket aaa delete
victorious-church-57397
05/16/2022, 1:31 PMmost-state-94104
05/16/2022, 1:33 PMbillowy-army-68599
most-state-94104
05/16/2022, 1:35 PMbillowy-army-68599
most-state-94104
05/16/2022, 2:10 PMvictorious-church-57397
05/16/2022, 2:10 PMmost-state-94104
05/16/2022, 2:14 PMvictorious-church-57397
05/16/2022, 2:15 PMmost-state-94104
05/16/2022, 2:15 PMvictorious-church-57397
05/16/2022, 2:15 PMmost-state-94104
05/16/2022, 2:16 PM