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

btw, it happened with 0.17.28. I then upgraded to 1.1.0 and still the same error

actually after the upgrade all `pulumi up` fail

Could you export your checkpoint and see if there is any resource whose `id` is `””`?

Also, please do open an issue.  This is definitely not expected. 

&gt; actually after the upgrade all `pulumi up` fail

Could you include the error message you see in this case as well in an issue?

<@UB3BGTV63> No resources with empty ids…

Opened <https://github.com/pulumi/pulumi/issues/3231>
Not sure what else to include. I’m checking if that can be due to a custom tfgen built provider we use

If the assert exactly the same on 1.1.0?  (Including line 238 in step.go)

What is the assert on the update operation? 

If you can share your checkpoint in DM - that would help. Else if you can make absolutely sure there are no resources with `id` either missing or `””`?

Seems I found the issue. It was:

```
    const nodeSecurityGroup = aws.ec2.SecurityGroup.get(
      'defaultWorkerNode',
      someStackReference.outputs.workerSecurityGroupId
    )
```

The stack outputs didn’t have `workerSecurityGroupId` set.
I think there should be an easier way to debug these. Panic and crash seems like inadequate here

&gt; Panic and crash seems like inadequate here

Definitely. We made some changes in August that were intended to address missing resources in `.get`: <https://github.com/pulumi/pulumi/pull/3123>

Notably, however, these changes do not look for an empty ID, which is what leads to the assert you're seeing.

I'll have to look into the exact behavior that occurs when attempting to read a security group with an empty ID. Hopefully the fix is straightforward.