I've noticed before that pulumi automatically installs things as they're needed. Now though, I've both added a new library to my requirements.txt, and changed the version requirements on another, and neither is getting picked up after doing

pulumi up

.

┌─[jamesph@Jamess-MBP] - [~/Documents/winfrastructure/aws] - [Fri Mar 17, 12:42]
└─[$]> venv/bin/pip freeze
Arpeggio==1.10.2
attrs==22.1.0
dill==0.3.5.1
grpcio==1.47.0
parver==0.3.1
protobuf==4.21.5
pulumi==3.39.3
pulumi-aws==5.17.0
pulumi-aws-native==0.29.0
PyYAML==6.0
semver==2.13.0
six==1.16.0
┌─[jamesph@Jamess-MBP] - [~/Documents/winfrastructure/aws] - [Fri Mar 17, 12:44]
└─[$]> cat requirements.txt
pulumi>=3.0.0,<4.0.0
pulumi-aws-native==0.52.0
pulumi-aws>=5.17.0,<6.0.0
pulumi-twingate>=0.0.43
┌─[jamesph@Jamess-MBP] - [~/Documents/winfrastructure/aws] - [Fri Mar 17, 12:44]
└─[$]> cat Pulumi.yaml
name: aws
description: AWS
runtime:
    name: python
    options:
        virtualenv: venv

(Observe the much earlier version of pulumi-aws-native, and the missing pulumi-twingate.) I could manually call pip install, but I'd like to know why this isn't working

After

pulumi new

, you do need to

pip install

any new requirements.

I was reading https://www.pulumi.com/docs/intro/languages/python/ before and not getting that from it, but it does seem to say that fairly clearly today. I'll chalk it up to being a Friday 😅

It's consistent across other languages FWIW: if you do

pulumi new aws-typescript

, you'll get a free

npm i @pulumi/aws

, but if you add other providers, you have to

npm i

it yourself.