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

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

<@UQ8K13T7X> 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?

I ask because I think my eks cluster _state_ was deleted while I was playing around with this stuff

(My stack failed for an unrelated reason before eks cluster finished in aws - takes 10-15m)
So I was mucking about with stack repair in the meantime and at some point the state got deleted

I just want to make sure I fully understand how an interactive repair might work
... e.g. if I don't make any changes then I should _not_ call import afterwards, otherwise pending resources will be stripped.

And if that's the case it kinda feels like it would be safer to not strip pending resources by default

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