This message was deleted.

sparse-intern-71089

12/09/2023, 9:14 AM

This message was deleted.

adorable-house-61348

12/12/2023, 11:06 AM

I believe the docs here might be what you are looking for

wonderful-motherboard-40477

12/12/2023, 12:32 PM

Thanks for the doc, but it's not good, the doc describes exactly what I encountered,

pulumi new python

creates automatically

venv

and install all the dependencies, and we can only alter it after all the installation which is too late. I created this issue on their repo.

adorable-house-61348

12/12/2023, 3:54 PM

I believe you can disable the behaviour or change the directory in the pulumi config:

Copy code

This behavior is controlled by the following virtualenv runtime option in Pulumi.yaml:

runtime:
  name: python
  options:
    virtualenv: venv
virtualenv is the path to a virtual environment to use.

Is this not what you want? I might have misunderstood your problem

adorable-house-61348

12/12/2023, 3:55 PM

oh, I see what you mean - you want the different behaviour for

pulumi new

. I'm afraid that's not possible right now. Thanks for raising the issue!

wonderful-motherboard-40477

12/12/2023, 3:57 PM

yes, not possible for the moment, as the config file

Pulumi.yaml

is generated by

pulumi new

too. I got an update from a pulumi maintainer in above issue, maybe it will be possible soon.

16 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.