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

<@U02R46KJVK9> could you file an issue in pulumi/pulumi with a repro, sorry about this

<@U02R46KJVK9> what version where you on before updating to 3.32? I don't think the .31 to .32 change broke this

I was previously on `3.31.1`  (I’m fairly certain)

I use pulumi daily for work and always update when there’s a an update available.

huh that's very surprising. can you try going back to 3.31.1 with
```curl -fsSL <https://get.pulumi.com> | sh -s -- --version 3.31.1```
and confirm that?

When I submitted the message above, I then downgraded by downloading `3.31.1` manually and the deploy worked.

Confirmed that was the version I used, as this is what I saw at the end of the successful up:
```warning: A new version of Pulumi is available. To upgrade from version '3.31.1' to '3.32.0', visit <https://pulumi.com/docs/reference/install/> for manual instructions and release notes.```

Thanks! That narrows the search down a bit.

Let me know if you need any other assistance with troubleshooting!

If you could run with `-v11 --logtostderr` and send me those logs (<mailto:fraser@pulumi.com|fraser@pulumi.com>) they nearly always help

Also, would there need to be active changes to make? If I re-ran it now, it would likely have no updates to make.

yes with 3.32 and any run of `preview` or `up` that triggers the panic

I’m not able to reproduce the error. I’ll do some more troubleshooting. It may have been stack-related, but I may not be able to touch that stack for a while as it’s actively in use. (I’m testing on another stack)

Understood, complicates things that maybe this isn't deterministic but I'll check through the display code to see if I can find anything

Thank you! I’ll try a few more variations. Perhaps it was a one-off related to some broken state in AWS. (missing property value, etc)

I had this happen the other day, since we were playing around with Pulumi I assumed it was something we were doing and did a destroy and up again. Everything worked after that.