pulumi/pkg/backend
Justin Van Patten b77ec919d4
Install and use dependencies automatically for new Python projects (#4775)
Automatically create a virtual environment and install dependencies in it with `pulumi new` and `pulumi policy new` for Python templates.

This will save a new `virtualenv` runtime option in `Pulumi.yaml` (`PulumiPolicy.yaml` for policy packs):

```yaml
runtime:
  name: python
  options:
    virtualenv: venv
```

`virtualenv` is the path to a virtual environment that Pulumi will use when running `python` commands.

Existing projects are unaffected and can opt-in to using this by setting `virtualenv`, otherwise, they'll continue to work as-is.
2020-06-09 16:42:53 -07:00
..
display Allow pulumi stack export to decrypt secrets (#4046) 2020-05-11 19:16:30 +01:00
filestate Allow pulumi stack export to decrypt secrets (#4046) 2020-05-11 19:16:30 +01:00
httpstate Install and use dependencies automatically for new Python projects (#4775) 2020-06-09 16:42:53 -07:00
state Breaking changes due to Feature 2.0 work 2020-04-14 09:30:25 +01:00
apply.go Breaking changes due to Feature 2.0 work 2020-04-14 09:30:25 +01:00
backend.go Breaking changes due to Feature 2.0 work 2020-04-14 09:30:25 +01:00
backend_test.go Breaking changes due to Feature 2.0 work 2020-04-14 09:30:25 +01:00
errors.go Add a link to docs for the 409 Conflict error message (#3207) 2019-09-10 13:25:08 -07:00
mock.go Breaking changes due to Feature 2.0 work 2020-04-14 09:30:25 +01:00
policypack.go Breaking changes due to Feature 2.0 work 2020-04-14 09:30:25 +01:00
query.go Breaking changes due to Feature 2.0 work 2020-04-14 09:30:25 +01:00
snapshot.go Breaking changes due to Feature 2.0 work 2020-04-14 09:30:25 +01:00
snapshot_test.go Breaking changes due to Feature 2.0 work 2020-04-14 09:30:25 +01:00
stack.go Breaking changes due to Feature 2.0 work 2020-04-14 09:30:25 +01:00
updates.go Breaking changes due to Feature 2.0 work 2020-04-14 09:30:25 +01:00
watch.go Breaking changes due to Feature 2.0 work 2020-04-14 09:30:25 +01:00