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

When I run:
```pulumi preview '--config=gcp:accessToken=INVALID'```
Pulumi places the config value in my config file. Why is this? I just want to override it for this run, not always.

And is there another way to just override it for this run?

<@U066S14FJEB> preferrably remove the access token from the stack config file. If you ran `gcloud auth login` on your system ahead of `pulumi preview/up`, our GCP provider should pick up the credentials from your local system.

Ringo I don't want it in the stack config file, but I want to set it from the CLI, I would actually prefer to set it from the environment, but setting it from the CLI will be better than nothing

but I don't get why preview will update my config file

This seems to me like undesired behaviour

The docs certainly does not suggest this is what will happen

Pulumi infrastructure code should never update the stack config file (`Pulumi.&lt;stackname&gt;.yaml`).

Okay, but then why does the command I share update the stack config file?

If it is not intended I will file a bug report

Checking with our engineers on expected behavior.

<@U066S14FJEB> for the moment, I would like to ask you to file a bug report. Preferably add a sequence of steps to reproduce this.
<https://github.com/pulumi/pulumi/issues>