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

This is reworked/refactored code, copied from existing projects which work. Undoubtedly an error in the reworking.. but a failing internal Pulumi assertion isn't something I've seen before, maybe someone else has seen this one and has a lead for me to follow?

:neutral_face: That is odd. I've never seen an empty URN before, ID I suppose could end up nil and we fail to check it. Do you have any Resource.get calls in your code?

Yes, though not sure which one is relevant. Is there a way to figure out what sort of resource might be involved?

Unfortunately it's difficult to determine any sort of flow here, because all the Pulumi code is invoked via nest.js, which is a dependency injection manager. There's no way (as far as I can tell) to figure out the order things happen in.

`-v9 --logtostderr` and open an issue with the logs from that. Engineering can probably work out the problematic resource from log ordering then.

Figured it out. The id was coming from a stack reference using `get` instead of `require`, and the source stack didn't exist.

The log hint sorted it for me. Raising an issue with the framework to prevent this happening again (we should use require if there's no error handling).

We really shouldn't have an internal error for that though. I'll see if we can validate IDs passed to get in the engine and give a proper diagnostic instead.

<https://github.com/pulumi/pulumi/pull/9243>