Hey I don't know if I'm misunderstanding something really obvious but it looks like there may be a pretty nasty bug in the Pulumi ESC UI. I've revoked everyone's access to Pulumi in my org as an emergency measure. In the video, we: • Save config on the "Environments / prod-pseudo-config" page. • 1st click on "prod-pseudo-config" from "Environments" Screen - you see the preview load appropriately and quickly disappear. ◦ At this point, via CLI, "esc open pmb/prod-pseudo-config" returns what disappeared on the web UI (config is intact) • 2nd click on "prod-pseudo-config" from "Environments" Screen - you see the preview load appropriately and quickly disappear. ◦ At this point, via CLI, "esc open pmb/prod-pseudo-config" returns what disappeared on the web UI (config is intact) • 3rd click on "prod-pseudo-config" from "Environments" Screen - you see the preview load appropriately and quickly disappear. ◦ At this point, via CLI, "esc open pmb/prod-pseudo-config" returns what disappeared on the web UI (config is intact) ◦ With the "Environments / prod-pseudo-config" page still open, I click the "Open" button on the bottom, to the right of Save. ▪︎ A config updated toast appears in the bottom right. ▪︎ At this point, via CLI, "esc open pmb/prod-pseudo-config" returns nothing. Opening the config via the web UI appears to have wiped it out. • 4th click on "prod-pseudo-config" from "Environments" Screen - the preview no longer loads and quickly disappears. or rather, it does, but config has been wiped ◦ At this point, via CLI, "esc open pmb/prod-pseudo-config" returns nothing (config has been wiped) • 5th click on "prod-pseudo-config" from "Environments" Screen - the preview no longer loads and quickly disappears. or rather, it does, but config has been wiped ◦ At this point, via CLI, "esc open pmb/prod-pseudo-config" returns nothing (config has been wiped) I'm observing this behavior not just on our individual accounts, but also our organization. If someone clicks the "Open" button in our pulumi org via the UI, the underlying config is immediately wiped out.

Thank you for reporting this! We're on it.

@magnificent-soccer-44287 We are reverting a new feature that is causing this, to get back to a good known state. Is there an environment(s) you need restored?

@miniature-musician-31262 @enough-architect-32336 thank you for the prompt support; luckily our configs were partially pass-through to stack outputs from which I was able to reverse engineer most of them. I'm sure a config revision history is in the works so just patiently waiting for that 🙂

Thanks @magnificent-soccer-44287 for raising this. We’ve rolled out a fix to production, and have identified and resolved the small number of environments that were impacted. We are indeed working on a feature to be able to explicitly manage versions of an environment. https://github.com/pulumi/esc/issues/59 and https://github.com/pulumi/esc/issues/190 are tracking two aspects of this feature. Expecting to have updates on those soon.