Disregard. Turns out I was misunderstanding an `es...
# general
e
Disregard. Turns out I was misunderstanding an
esc
error message telling me that I was using an environment that references the stage I just removed. If you have this issue, check your
esc
environment to make sure you aren't using an environment with an
app:
reference to the very environment you are trying to
pulumi up
--- Howdy. We have a bug of some sort after performing
pulumi stack rm --force
Now when we're doing a
pulumi up
to recreate the stack, we're getting:
Copy code
error: getting stack configuration: opening environment: [0] 
Diags: missing Stack resource
We've attempted
pulumi refresh
and
pulumi destroy
to try and completely remove the stack, but there's something preventing us from creating a new Stack resource
We performed the
pulumi stack rm --force
because we got a snapshot integrity failure and thought we could manually delete a vpc from amazon and then call
pulumi stack rm
We attempted the same deploy on a second machine, and it appears this is a server-side error from pulumi
Copy code
pulumi stack export
{
    "version": 1,
    "deployment": {
        "manifest": {
            "time": "0001-01-01T00:00:00Z",
            "magic": "",
            "version": ""
        }
    }
}