https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
p
ultimately the real question is if those strings for the 
secure
value are actually secure enough to be committed or if this file should just be in a .gitignore
oh I just found this in the examples repo and it looks like Pulumi does recommend to ignore those config files https://github.com/pulumi/examples/blob/master/.gitignore#L14
c
Pulumi docs actually say they are intended to be safe to commit to VC. Let me see if I can find the source.
b
yes they are secure
c
b
dependending on your secrets provider - they are either, AWS kms / Azure keyvault / GCP Kms or hashivault
p
Thanks Paul and Dean, that is helpful 🙂
a
In practice with multiple developers and CI/CD pipelines using pulumi, you absolutely need to have those stack config files in git.
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by