cold-analyst-29667
07/31/2024, 9:42 AMlittle-library-54601
07/31/2024, 1:22 PMaz login --tenant "{tenant guid}"
az account set --subscription "{subscription guid}"
$Env:PULUMI_CONFIG_PASSPHRASE="{stack-passphrase}"
$Env:AZURE_STORAGE_ACCOUNT="{storage-account-name}"
$Env:AZURE_STORAGE_KEY="{storage-account-key}"
pulumi login azblob://{state-blob-name}
pulumi whoami -v
pulumi stack ls
pulumi stack select {target-stack-name}
cold-analyst-29667
07/31/2024, 1:50 PM.pulumi/.history
folder that is located on the Blob. In fact it succeeds into writing inside the Blob, but the error still appears in the end (and maybe that's ok if a user runs it, but that's not good in a pipeline)
Here are the steps to reproduce what I'm doing:
- az login
# (select correct subscription)
- export all environment variables (as per your example)
- pulumi login --cloud-url <azblob://myStorage>
- (pulumi stack ls
, pulumi stack init asd
etc. works fine.)
- In my example I'm using python, create a project with the following 3 lines inside `___main___.py`:
import pulumi
from pulumi_azure_native import resources
resource_group = resources.ResourceGroup('rg-test', location='francecentral', resource_group_name='rg-test'
- I then create a python virtual env (python -m venv venv
).
- Inside the virtual env, I install with pip the following packages: pulumi>=3.0.0,<4.0.0
and pulumi-azure-native>=2.0.0,<3.0.0
- I then run the code with pulumi up
The infrastructure on Azure gets created fine, the state even gets updated inside my Blob Storage.. but still the error appears in the end (even though it managed to edit the Blob Storage).
Notes: Using Python 3.10 and a virtual environment, inside WSL2little-library-54601
07/31/2024, 3:46 PM