Default to UseAutomaticVirtualEnv in integration tests

[justinvp]

This way, the tests use the built-in virtual environment support by default, which is what most customers will be using. A new UsePipenv option is available to go back to using pipenv for tests.

[justinvp]

I changed this here to match what we do inside the Python SDK, running it as python -m pip install rather than pip install.

pulumi/sdk/python/python.go

Line 231 in 066507c

pipCmd := VirtualEnvCommand(venvDir, "python", append([]string{"-m", "pip", "install"}, arg...)...)

[stack72]

Do we need the Pulumi.yaml file to be updated before the venv will be created or am I conflating 2 separate things here?

[justinvp]

Do we need the Pulumi.yaml file to be updated before the venv will be created or am I conflating 2 separate things here?

No. The integration test code will handle that automatically.

pulumi/pkg/testing/integration/program.go

Lines 1744 to 1748 in 066507c

	projinfo.Proj.Runtime.SetOption("virtualenv", "venv")
	projfile := filepath.Join(projinfo.Root, workspace.ProjectFile+".yaml")
	if err = projinfo.Proj.Save(projfile); err != nil {
	return errors.Wrap(err, "saving project")
	}

It doesn't hurt for the Pulumi.yaml to already have it. And for the examples repo, we will want to go ahead and add it to the Pulumi.yaml for the examples (this PR that I will finish up), just to make it easier for folks who are acquiring the examples (either via cloning the repo, pulumi new <url>, or the Pulumi button). When it is specified in Pulumi.yaml and the dir doesn't exist, the CLI will create it and install deps automatically.

[stack72]

Awesome! The set of PR tests and master should help us get some mileage around this :)