able-honey-93860
12/24/2021, 12:29 AM"error: constructing secrets manager of type “passphrase”: unable to find either ‘PULUMI_CONFIG_PASSPHRASE’ or ‘PULUMI_CONFIG_PASSPHRASE_FILE’ when trying to access the Passphrase Secrets Provider; please ensure one of these environments barebones is set to allow the operation to continue”
I have tried a number of ways to “set” the passphrase but no luck. First tried setting it locally in my windows environment variables list and then tried pulumi config set —secret PULUMI_CONFIG_PASSPHRASE “Test”
And yes “Test” is the passphrase I used when running pulumi up, just trying to understand how it's all working then I would use something more secure.
Along with setting it up before running pulumi up by running pulumi stack unit dev —secrets-provider passphrase
It just continuously gives me the error above after I run any subsequent commands after a successful pulumi up. For instance after creating the bucket I run pulumi stack output bucket_name
and then get the same passphrase error above. I have to be missing something super simple lol. I have deleted everything and redid it multiple times but no luck. I just can't find anything on my own so I appreciate any help!billowy-army-68599
12/24/2021, 6:18 AMable-honey-93860
12/24/2021, 8:31 AMPULUMI_CONFIG_PASSPHRASE
with the value “Test”
as an environment variable, but pulumi still wasn't happy. Also felt that this was a bit odd since the password would then be stored as a plain text value in the environment variable. Is that truly expected? Seemed a bit counter intuitive lolbillowy-army-68599
12/24/2021, 9:00 AMsparse-butcher-73713
12/24/2021, 12:05 PMable-honey-93860
12/25/2021, 12:25 AMimport pulumi_okta as okta
just fine. So I think it might be due to pulumi using its own python exe? I installed via chocolatey, but have since uninstalled it and decided to install through the cmd command since I am more familiar with picking apart installs when they're not done via choco. This work however the environment variable set within CMD is being leveraged and I can run pulumi in cmd, but I can't run pulumi in powershell. Superrrr weird since I verified the environment variable is set in the gui, I have reloaded multiple powershell sessions and ran refreshenv
quite a few times, however when I run (Get-ChildItem -path env:PATH).value -split “;”
it doesn't pull in the environment variable. So odd, I am definitely more of a powershell user and never used cmd to set env variables before. I think I can figure out a fix eventually, but just another growing pain hahasteep-beach-52652
12/25/2021, 7:32 PMable-honey-93860
12/26/2021, 3:12 AM