Weird... I've got a stack output that is supposedl...
# general
Weird... I've got a stack output that is supposedly being deleted when the corresponding resource gets deleted, but running
pulumi stack
immediately afterward shows the output is still present, and it persists across multiple `pulumi up`s, despite the fact that the underlying resource is long gone. I think I'm going to do some manual surgery on the stack state (using
pulumi stack export
pulumi stack import
), but I'm curious if anybody else has come across this before.
Are you still exporting the value and you're expecting the value to go to
? 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<type> = value;
in node. Are you doing it like that, or some other export mechanism?
it's in Python, so something like
pretty standard, as far as I know
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
@red-match-15116 I couldn't find anything that seemed relevant (using various searches on "output"), so I created
👍🏽 1
Yes I've had this problem if the Output was the last output remaining in the stack!