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

not at this time:
<https://github.com/pulumi/pulumi/issues/6753>

If you look at the issue, you can change the physical name of the resource, if that helps somehow

yeah somehow keying the resource name off the bucket config was the only thing i could think of. thanks for clarifying.

is there anything else I can do to help that issue along other than +1ing that github issue? would outlining my specific use case be useful at all?

added a comment. thanks for your time :ok_hand:

In the meantime, if you know the Pulumi URN of the resource when you run `pulumi up` then you could manually replace it with `pulumi up --replace &lt;urn&gt;` .

When you run `pulumi up` normally the preview will tell you that this resource will be updated, so you can spot it at that point and re-run with the `--replace`.