is there any way to have

pulumi new aws-python

not force the creation of a virtualenv? i.e. “don’t create a venv, don’t install anything for me because I have one already, or I will take care of it myself”. I don’t see any options in

pulumi new --help

. I’ve also tried

pulumi new aws-native-python

in case that is it. Nope. Don’t know how the 2 are different (

aws-native-python

vs

aws-python

), but it creates a venv for me too

I reached out to the engineering team regarding the virtualenv. I don’t use Python myself that often, so I don’t know how to suppress this myself. Regarding the difference on

aws-python

and

aws-native-python

. We have 2 AWS providers: •

aws

- this one is a bridged terraform provider •

aws-native

- this one is a native Pulumi provider, talking to the new AWS Cloud Control API So these templates only differ in which AWS provider is used by default.

thank you Ringo. I appreciate it. If the team has any recommendations on which to use, I’d appreciate it. And if it is

aws-native

, would appreciate any info if anything needs to change in terms of docs (I currently look at https://www.pulumi.com/registry/packages/aws/api-docs/)

aws-native

doesn’t provide full support yet for all AWS services, because that Cloud Control (CC) API doesn’t provide full support for all of their own services yet. So supporting more of AWS in the native provider goes at the same pace as AWS provides support for that in the CC API. But we can deliver a new version of

aws-native

same day as Amazon announces new features to that API. Still, I would suggest to go for

aws-native

when it is possible, and add the classic

aws

provider to the same program. You can use both in the same project (program).

got it. Thank you!

There is

pulumi new -g

which will only generate the code - it won't do any of the other initialization. That is probably the best bet if you want to have full control over dependency management. https://www.pulumi.com/docs/reference/cli/pulumi_new/

great! thank you!