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'm not entirely sure what the question is. Are you wanting to set config values via <http://app.pulumi.com|app.pulumi.com> for a particular project as opposed to setting them via the Pulumi CLI?

Is this in the context of Pulumi Deployments?

Screenshot 2023-08-18 at 23.35.36.png

In stack deployment settings I can only set env vars

Ahhh gotcha. This isn't for a stack's config directly. This is for setting environment variables available during a Pulumi Deployments execution.

So no, there is no way to set a stack config value, in this manner.

So how can I set stack config value for Pulumi cloud, like in Terraform Cloud

Just curious, what is the use case? Is this a one-time thing or is setting configuration value outside the CLI part of your workflow?

I don't want to push Pulumi.yaml to github, cuz it have some sensitive config values, so I want set them in Pulumi Cloud like Terraform Cloud sensitive vars.

Terraform have sensitive input vars in their cloud

Pulumi's concept of secrets is quite a bit different than TFs. For one, Pulumi secrets are encrypted by default on a per stack basis. <https://www.pulumi.com/docs/concepts/secrets/>

So the chance of leaking plain-text sensitive values from stack state (or config) is basically nil unless specifically done so by the user.

Also question: Is pulumi gcp package production ready?

<https://www.pulumi.com/registry/packages/gcp/>