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

Are you still exporting the value and you're expecting the value to go to `undefined`? Or you've deleted the exported constant, and it's still appearing in the outputs?

I have a function I'm calling that creates a resource and exports a value from that resource. I removed the place where I call that function, and Pulumi deletes the resource (as expected), and the diff indicates that the corresponding output is also deleted, but the output remains.

with the removal of this function's call-site, I should have no more outputs from the stack.

While I've since fixed it manually, I wonder if there is some kind of weird boundary condition going from 1 output to 0 outputs.

I haven't encountered that, but I only ever create outputs via something like `export const x: pulumi.Output&lt;type&gt; = value;` in node. Are you doing it like that, or some other export mechanism?

it's in Python, so something like `pulumi.export("foo", my_resource.foo)`

Yep, looks normal. And you're deleted that code but it remains in the state? That must be a bug.

I feel like I’ve heard this before but I can’t remember the context

Might be worth doing a quick search in the issues to see if anything pops up but if not definitely open an issue

<@U01038HJ93R> I couldn't find anything that seemed relevant (using various searches on "output"), so I created <https://github.com/pulumi/pulumi/issues/8273>

Yes I've had this problem if the Output was the last output remaining in the stack!