Pulumi

Improvements

- `pulumi login` now supports `s3://`, `azblob://` and `gs://` paths (on top of `file://`) for
storing stack information. These are passed the location of a desired bucket for each respective
cloud provider (i.e. `pulumi login s3://mybucket`). Pulumi artifacts (like the
`xxx.checkpoint.json` file) will then be stored in that bucket. Credentials for accessing the
bucket operate in the normal manner for each cloud provider. i.e. for AWS this can come from the
environment, or your `.aws/credentials` file, etc.
- The pulumi version update check can be skipped by setting the environment variable
`PULUMI_SKIP_UPDATE_CHECK` to `1` or `true`.
- Fix an issue where the stack would not be selected when an existing stack is specified when running
`pulumi new <template> -s <existing-stack>`.
- Add a `--json` flag (`-j` for short) to the `preview` command. This allows basic serialization of a plan,
including the anticipated set of deployment steps, list of diagnostics messages, and summary information.
Each step includes deeply serialized information about the resource state and step metadata itself. This
is part of ongoing work tracked in [pulumi/pulumi2390](https://github.com/pulumi/pulumi/issues/2390).

Improvements

- Add a new `ignoreChanges` option to resource options to allow specifying a list of properties to
ignore for purposes of updates or replacements. [2657](https://github.com/pulumi/pulumi/pull/2657)
- Fix an engine bug that could lead to incorrect interpretation of the previous state of a resource leading to
unexpected Update, Replace or Delete operations being scheduled. [2650]https://github.com/pulumi/pulumi/issues/2650)
- Build/push `pulumi/actions` container to [DockerHub](https://hub.docker.com/r/pulumi/actions) with new SDK releases [#2646](https://github.com/pulumi/pulumi/pull/2646)

Improvements

- A new "test mode" can be enabled by setting the `PULUMI_TEST_MODE` environment variable to
`true` in either the Node.js or Python SDK. This new mode allows you to unit test your Pulumi programs
using standard test harnesses, without needing to run the program using the Pulumi CLI. In this mode, limited
functionality is available, however basic resource object allocation with input properties will work.
Note that no actual engine operations will occur in this mode, and that you'll need to use the
`PULUMI_CONFIG`, `PULUMI_NODEJS_PROJECT`, and `PULUMI_NODEJS_STACK` environment variables to control settings
the CLI would have otherwise managed for you.

Improvements

- `refresh` will now warn instead of returning an error when it notices a resource is in an
unhealthy state. This is in service of https://github.com/pulumi/pulumi/issues/2633.

Improvements
- Correctly handle the case where we would fail to detect an archive type if the filename included a dot in it. (fixes [pulumi/pulumi2589](https://github.com/pulumi/pulumi/issues/2589))
- Make `Config`'s constructor's `name` argument optional in Python, for consistency with our Node.js SDK. If it isn't
supplied, the current project name is used as the default.
- `pulumi logs` will now display log messages from Google Cloud Functions.

Improvements

- Don't print the `error:` prefix when Pulumi exists because of a declined confirmation prompt (fixes [pulumi/pulumi458](https://github.com/pulumi/pulumi/issues/2070))
- Fix issue where `Outputs` produced by `pulumi.interpolate` might have values which could
cause validation errors due to them containing the text `<computed>` during previews.