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

just to confirm, you’re running `stack.getAllConfig()` after you’ve run a destroy?

`stack.getAllConfig` will only return a value after a successgul `stack.up` operation

Thanks for your reply <@UCWG26BH7>

I take the following steps:
1. Start server and run the stack init/select, call some endpoints which sets configuration. Then I run a pulumi up which sets configurations and deploys resources.
2. Destroy server
3. Start server again from scratch and run a stack init/select. Then, without doing anything or running a pulumi up, I run `stack.getAllConfig()` which returns an empty object.
If I would run a pulumi up in step 3, after running the stack selection but before anything else, it cleans configurations and deletes all resources

stack init on its own won’t set any config.

you need to run `getAllConfig` after you run `setConfig`

so selecting the existing stack wont give the possibility to get the already existing config from Pulumi (state)? Instead we need to store this configuration yaml somewhere and get it from this location to recover the previous configuration?

sorry, when you say “Destroy server” do you mean run a `pulumi destroy` ?

or destroy the server you’re running automation API on?

yes destroy the server I am running the automation api on

ohhh, in that case, your local copy of the config hasn’t been retrieved, run a `refresh` first after you select the stack

ahh great, that worked. Tried a refresh before but must have made a mistake when using the `pulumi.refresh()` (since that one also cleaned my configuration) instead of the `pulumi.refreshConfig()` :smile: Thanks a lot :slightly_smiling_face: