What should be the order of calls for the automation api equivalent of repairing stack state? I think that config should still be set before doing the export / import, or does it not matter? (I did a repair at one point before doing this and config was wiped from the ui) So looks like the following makes sense and is consistent with the above: • var stack = LocalWorkspace.CreateOrSelectStackAsync • stack.Workspace.InstallPluginAsync • stack.SetAllConfigAsync • stack.ExportStackAsync • // repair stack • stack.ImportStackAsync

It should not matter. But remember that config is only persisted in backends on update, not on each intermediate

config set

command. I would expect you to need to do something along the following: 1. export 2. // fix 3. import 4. (setup commands, install plugins, config, etc) 5. refresh/update

@lemon-agent-27707 Follow up question... if I import the stack unchanged, i.e. not edited so still with pending resources, should they be preserved or would you expect pending resources to be stripped by the import?

running an export/import does indeed strip pending deletes

Pending deletes or pending resources in general?

all pending operations, see the docs here: https://www.pulumi.com/docs/troubleshooting/#interrupted-update-recovery