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

you can set it as a secret if you want to protect that information

looks like you can also use env vars
<https://www.pulumi.com/registry/packages/gcp/installation-configuration/#credentials>

I typically have a separate Pulumi stack for each environment that I deploy to.  Of course, I use a separate GCP project for each environment, and set the `gcp:project` in the stack configuration.

As <@U01AWJN4N1K> mentioned, use Secrets to protect configuration values as you see fit.
<https://www.pulumi.com/docs/intro/concepts/secrets/>