This message was deleted.
# getting-started
s
This message was deleted.
g
Hi- I'm not entirely sure what the question is. Are you wanting to set config values via app.pulumi.com for a particular project as opposed to setting them via the Pulumi CLI?
f
Yes! Exactly
For particular stack
I only see Environment variables
g
Is this in the context of Pulumi Deployments?
f
In stack deployment settings I can only set env vars
g
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.
f
So how can I set stack config value for Pulumi cloud, like in Terraform Cloud
g
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?
f
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.
Maybe I'm missing something?
Terraform have sensitive input vars in their cloud
How it works in Pulumi Cloud?
g
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.
f
Thanks! I will try it out!
Also question: Is pulumi gcp package production ready?
g
Yep it surely is!
f
Thank you so much for your help!