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

Hi, I'd like to ask if it's safe to edit stack config file directly, without using `pulumi config set`. The reason is that one of the keys I'd like to set is a deeply nested object and I'd like to avoid many `pulumi config set --path` commands to actually set the value. What I'm asking is basically if editing the config file directly and then using `pulumi up` leads to the same result as using `pulumi config set`. Or is setting the config values a local operation anyway? Thanks

As far as I know it's safe -- we do it all the time :joy: Of course with secrets you will want to use `set --secret --path` etc.

When you use `config set` Pulumi will for instance reorder object keys alpahbetically, so you might find that you get diffs even though none of the values have changed, is the only gotcha that springs to mind. Pulumi won't run spurious actions, but Git will say the files are different, for instance.

Cool, thanks for assurance :slightly_smiling_face:

The file is designed to be safe to manually edit. Secrets are the only thing you need to use `config set` for.

Perfect, thanks for information guys :slightly_smiling_face: