This message was deleted.
# generals
sparse-intern-71089
04/30/2021, 10:22 AMThis message was deleted.
b
broad-dog-22463
04/30/2021, 11:31 AMHi @bumpy-agent-19616
broad-dog-22463
04/30/2021, 11:31 AMThis was fixed in Pulumi v2.25.2 - what version of Pulumi CLI are you using?
b
bumpy-agent-19616
04/30/2021, 11:34 AMI actually use pulumi: pulumi/pulumi@2.0.0 orb which installs v3.1.0 as far as I see from the CircleCI logs.
bumpy-agent-19616
04/30/2021, 11:39 AMI am not sure if the order of adding firewall rules to storage matters. I moved firewall rule addition step a bit up before Pulumi Login step which seems to have worked. However, do you think this would have made any difference?
bumpy-agent-19616
04/30/2021, 12:14 PMOh, sorry! Problem seems to occur again unfortunately!
b
broad-dog-22463
04/30/2021, 12:57 PMWhat are you setting any azure environment variables to allow interaction with azure?
b
bumpy-agent-19616
04/30/2021, 1:14 PMI set up azure credentials for Pulumi stacks using pulumi config set way and am not using environment variables for the interaction.
b
broad-dog-22463
04/30/2021, 1:38 PMSo I think there’s some missing information here
broad-dog-22463
04/30/2021, 1:39 PMAre you trying to store your state in an azure blob or is this an issue when creating a resource in azure?
b
bumpy-agent-19616
04/30/2021, 1:46 PMI am actually trying to update my infrastructure with already creating stacks having cloud storage as backend after logging in via pulumi login --cloud-url. So, it is problem while Pulumi trying to connect state or checkpoint file to know about the current state of infrastructure and then perform create/update operation on it.
b
broad-dog-22463
04/30/2021, 1:53 PMOk, when connecting to an Azure blob self-managed backend, you need to set AZURE_STORAGE_ACCOUNT and AZURE_STORAGE_SAS_TOKEN
broad-dog-22463
04/30/2021, 1:53 PMthose are requirements for interacting with the backend
broad-dog-22463
04/30/2021, 1:54 PMnotice they are different from the Pulumi provider configurations
b
bumpy-agent-19616
04/30/2021, 2:02 PMAZURE_STORAGE_ACCOUNT, AZURE_STORAGE_KEY and AZURE_KEYVAULT_AUTH_VIA_CLI are env variables that we set atm. Maybe, I will try adding AZURE_STORAGE_SAS_TOKEN but AZURE_STORAGE_KEY could be used in place of AZURE_STORAGE_SAS_TOKEN. Is that correct?
b
broad-dog-22463
04/30/2021, 2:24 PMThat is correct
broad-dog-22463
04/30/2021, 2:25 PMIf those env vars are set and you get that error then I suggest checking you can use the same values locally and talk to the storage accounts
b
bumpy-agent-19616
04/30/2021, 2:29 PMI will check that one and see what happens. Thanks, Paul!
b
broad-dog-22463
04/30/2021, 2:36 PMno worries at all!
15 Views