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

Anyone have insights into why pulumi may insist on trying to update a resource that hasn't changed?
```  ~ ebsBlockDevices: [
          ~ [0]: {
                  ~ deleteOnTermination: true =&gt; true
                  ~ deviceName         : "/dev/sda1" =&gt; "/dev/sda1"
                }
        ]```
This leads to us having to manually go in and set up the instance each time.

Give me a sec... there's an issue around this...

So check in the console to see what the root volume path is. It's set in the Ami, so you can't change it, but you can change the ebsblockdevice input path

Take a look at this commit <https://github.com/pierskarsenbarg/pulumi-scratchpad/commit/8ac57fd8adede0d68524fdce69bc638974e22142|https://github.com/pierskarsenbarg/pulumi-scratchpad/commit/8ac57fd8adede0d68524fdce69bc638974e22142>

This isn't the first time I've had this question