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.

Pulumi Community

hmm, maybe try running a `pulumi refresh`

can you send the full log trace? where it says its deleting and recreating it? i’ve never experienced anything like this with pulumi before tbh

if its just trying to create, and not delete it, then its indicative that the bucket was created with another pulumi stack or by other means, and its trying to recreate the bucket. if thats the case then i’d recommend importing the resource in to pulumi

It is trying to delete it as well - I’ll send the preview log trace one sec

``` ~  aws:s3:Bucket aaa refreshing 

@ previewing update.....
+  aws:s3:Bucket aaa create  
-  aws:s3:Bucket aaa delete ```

Note that I haven’t included the full log because the stack is quite large

so its trying to create it before it deletes it? thats a bit strange. have you tried removing the resource definition altogether and putting it back in

<@U03FETA0P28> can you show the diff from pulumi preview ?

This usually happens because the resource name is changing on each run, also sharing the code you're using to define the bucket helps 

The name is the same (it doesn’t include a sha)

Unfortunately the repo is internal, so I’ll have to post the details here. Give me a minute

Sorry the bucket is created through another internal repo and is quite complex (it includes various optional settings) so not the easiest to share. Will post this afternoon (along with the diff) :slightly_smiling_face:

if the bucket is created by another repo, then thats why you’re getting the error

you’re trying to create a bucket with the same name twice

S3 buckets’ names are globally defined, therefor each bucket name has to be unique, if you’re trying to reference the same bucket from another stack, I’d recommend using pulumi stack references to achieve this: <https://www.pulumi.com/learn/building-with-pulumi/stack-references/>

Sorry what I meant is that the function for creating the bucket is defined in another repo and packaged as a library

We create the bucket by calling the function in the repo where the rest of the stack is created

if you could send some snippets over that would be really helpful

I’m going to ask my manager why the repo is internal - I can’t see anything sensitive

Reached out to my colleague and turns out the problem is because I reset the  PULUMI_CONFIG_PASSPHRASE. This meant pulumi was trying to recreate the stack, so the solution is to revert the stack from a backup