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

```
{
    "name": "aws-typescript",
    "devDependencies": {
        "@types/node": "12.7.1"
    },
    "dependencies": {
        "@pulumi/aws": "0.18.27",
        "@pulumi/awsx": "0.18.8",
        "@pulumi/pulumi": "0.17.28"
    }
}
```

`pulumi preview --diff` should show why does it want to recreate cert

Used that flag and all it says is "completing deletion from previous update"

Actual values.
```
subjectAlternativeNames: [
        [0]: "*.<http://eu-central-1.dev.aws.lykkeservices.net|eu-central-1.dev.aws.lykkeservices.net>"
        [1]: "*.<http://dev.aws.lykkeservices.net|dev.aws.lykkeservices.net>"
    ]
```
vs
```
subjectAlternativeNames: [
            [0]: "*.<http://dev.aws.lykkeservices.net|dev.aws.lykkeservices.net>"
            [1]: "*.<http://eu-central-1.dev.aws.lykkeservices.net|eu-central-1.dev.aws.lykkeservices.net>"
        ]
```

luckily you have jsut 2, so you can sort or reverse sort to get desired order and see if diff is still there

The order didn't change in code though :face_with_head_bandage:

image.png

Always been like this since initial deployment

what if you clear pending deletion in state manually ,then run preview --diff again? does it show anything meaningful?

How do I clear the pending deletion? (Thanks for your assistance btw)

Reordering it in code to match the pending deletion had no effect.

&gt; - I've exported, edited and imported the stack to remove the `pendingOperations`  section.

There is no `pendingOperations`. But I see this property on the resource itself:

Removing that and importing the stack removed the "pending deletion from previous operation" :slightly_smiling_face:

Code on left, diff on right.

So something has changed, possibly on the pulumi side, that _originally_ stored these in reverse order.

I think I can patch the stack to fix this.

Seattle is about to wake up, they might help

I patched the stack to re-order the `subjectAlternativeNames` and changed the code to align with it. Pulumi no longer wanted to re-create the cert.

I still don't know why it suddenly thought that the resource had changed, my spidey sense is pointing at a pulumi behaviour update somewhere.

Anyway, thanks for asking the right questions <@UG53R9UJC>! :slightly_smiling_face: