fast-river-57630
05/05/2022, 5:36 PMgetting secrets manager: passphrase must be set with PULUMI_CONFIG_PASSPHRASE or PULUMI_CONFIG_PASSPHRASE_FILE environment variables
echoing-dinner-19531
05/05/2022, 6:02 PMfast-river-57630
05/05/2022, 7:17 PMpulumi/setup-pulumi@v2
and just run: pulumi up --stack ...
. Otherwise I'm stuck with whatever version pulumi/actions@v3
gives meechoing-dinner-19531
05/05/2022, 7:56 PMfast-river-57630
05/05/2022, 8:18 PMechoing-dinner-19531
05/05/2022, 9:02 PMPULUMI_CONFIG_PASSPHRASE: ""If your using the service why are you also using the passphrase secret manager? Just let the service do it
fast-river-57630
05/05/2022, 10:39 PMechoing-dinner-19531
05/06/2022, 8:15 AMdont you have to set PULUMI_CONFIG_PASSPHRASE to an empty string when using the service secret manager?Nope, you just want to leave it unset if using the other secret managers. What broke you is we changed 3.32 to treat unset and "" as the same. People kept trying to 'unset' it by doing PASSPHRASE="" in their shell. Plus who wants an empty string as a passphrase. Glad the pointers got you sorted out 🙂