mirror of https://github.com/pulumi/pulumi.git
106 lines
7.8 KiB
Markdown
106 lines
7.8 KiB
Markdown
## 0.16.8 (Unreleased)
|
|
|
|
### Improvements
|
|
|
|
- Update the error message when When `pulumi` commands fail to detect your project to mention that `pulumi new` can be used to create a new project (fixes [pulumi/pulumi#2234](https://github.com/pulumi/pulumi/issues/2234))
|
|
|
|
- Added a `--stack` argument (short form `-s`) to `pulumi stack`, `pulumi stack init`, `pulumi state delete` and `pulumi state unprotect` to allow operating on a different stack than the currently selected stack. This brings these commands in line with the other commands that operate on stacks and already provided a `--stack` option (fixes [pulumi/pulumi#1648](https://github.com/pulumi/pulumi/issues/1648))
|
|
|
|
- Stack specific configuration settings are now stored in yaml files under the `.pulumi` folder, next to `Pulumi.yaml` instead of being in the same directory as `Pulumi.yaml`. However, if a configuration file is in the old location, it is used instead. The `config` property of the project's `Pulumi.yaml` can pick a different directory. To go back to the old behavior, add `config: .` to `Pulumi.yaml` (fixes [pulumi/pulumi#2005](https://github.com/pulumi/pulumi/issues/2005))
|
|
|
|
- When using the Pulumi Service, stack configuration files are now segmented by owner. Previously, we share the same on disk location for a stack if its name was shared across organizations. This would lead to issues when encrypted configuration (which was encrypted with a per stack key) was not usable, except for the organization that the stack was created in. If an existing configuration file exists at the old location, it is prefered, to match behavior with older CLIs (fixes), so when you want to take advantage of this new feature, we recommend that you either manually move the old `Pulumi.<stack-name>.yaml` into its new prefered location (by default: `.pulumi/<organization-name>/Pulumi.<stack-name>.yaml`) or remove it from disk and run `pulumi config refresh` to sync the configuration from the last deployment into a new file in the correct location. (fixes [pulumi/pulumi#1859](https://github.com/pulumi/pulumi/issues/1859))
|
|
|
|
## 0.16.7 (Release December 5th, 2018)
|
|
|
|
### Improvements
|
|
|
|
- Configuration and stack commands now take a `--config-file` options. This option allows the user to override the file used to fetch and store config information for a stack during the execution of a command.
|
|
|
|
- Fix an issue where ANSI escape codes would appear in messages printed from the CLI when running on Windows.
|
|
|
|
- Fix an error about a bad icotl when trying to read sensitive input from the console and standard in was not connected to a terminal.
|
|
|
|
- The dynamic provider would fail to launch if your `node_modules` folder was non in the default location or had a non standard layout. This has been fixed so we correctly find your `node_modules` folder in the same way node does. (fixes [pulumi/pulumi#2261](https://github.com/pulumi/pulumi/issues/2261))
|
|
|
|
## 0.16.6 (Released November 28th, 2018)
|
|
|
|
### Major Changes
|
|
|
|
- When running a Python program, pulumi will now run `python3` instead of `python`, since `python` often points at Python 2.7 binary, and Pulumi requires Python 3.6 or later. The environment variable `PULUMI_PYTHON_CMD` can be used to provide a different binary to run.
|
|
|
|
### Improvements
|
|
|
|
- Allow `Output`s in the dependsOn property of `ResourceOptions` (fixes [pulumi/pulumi#991](https://github.com/pulumi/pulumi/issues/991))
|
|
|
|
- Add a new `StackReference` type to the node SDK which allows referencing an output of another stack (fixes [pulumi/pulumi#109](https://github.com/pulumi/pulumi/issues/109))
|
|
|
|
- Fix an issue where `pulumi` would not respect common `NO_PROXY` settings (fixes [pulumi/pulumi#2134](https://github.com/pulumi/pulumi/issues/2134))
|
|
|
|
- The CLI wil now correctly report any output from a Python program which writes to `sys.stderr` (fixes [pulumi/pulumi#1542](https://github.com/pulumi/pulumi/issues/1542))
|
|
|
|
- Don't install packages by default for Python projects when creating a new project from a template using `pulumi new`. Previously, `pulumi` would install these packages using `pip install` and they would be installed globally when `pulumi` was run outside a virtualenv.
|
|
|
|
- Fix an issue where `pulumi` could panic during a peview when using a first class provider which was constructed using an output property of another resource (fixes [pulumi/pulumi#2223](https://github.com/pulumi/pulumi/issues/2223))
|
|
|
|
- Fix an issue where `pulumi` would fail to load resource plugins for newer dev builds.
|
|
|
|
- Fix an issue where running two copies of `pulumi plugin install` in parallel for the same plugin version could cause one to fail with an error about renaming a directory.
|
|
|
|
- Fix an issue where if the directory containing the `pulumi` executable was not on the `$PATH` we would fail to load language plugins. We now will also search next to the current running copy of Pulumi (fixes [pulumi/pulumi#1956](https://github.com/pulumi/pulumi/issues/1956))
|
|
|
|
- Fix an issue where passing a key of the form `foo:config:bar:baz` to `pulumi config set` would succeed but cause errors later when trying to interact with the stack. Setting this value is now blocked eagerly (fixes [pulumi/pulumi#2171](https://github.com/pulumi/pulumi/issues/2171))
|
|
|
|
## 0.16.5 (Released November 16th, 2018)
|
|
|
|
### Improvements
|
|
|
|
- Fix an issue where `pulumi plugin install` would fail on Windows with an access deined message.
|
|
|
|
## 0.16.4 (Released November 12th, 2018)
|
|
|
|
### Major Changes
|
|
|
|
- If you're using Pulumi with Python, this release removes Python 2.7 support in favor of Python 3.6 and greater. In addition, some members have been renamed. For example the `stack_output` function has been renamed to `export`. All major features of Pulumi work with this release, including parallelism!
|
|
|
|
### Improvements
|
|
|
|
- Download plugins to a temporary folder during `pulumi plugin install` to ensure if the operation is canceled, the have downloaded plugin is not used.
|
|
|
|
- If an update is in progress when `pulumi stack ls` is run, don't show its last update time as "a long time ago".
|
|
|
|
- Add `--preserve-config` to `pulumi stack rm` which causes Pulumi to keep the `Pulumi.<stack-name>.yaml` when removing a stack.
|
|
|
|
- Support passing template names to `pulumi up` the same as `pulumi new` does.
|
|
|
|
- When `-g` or `--generate-only` is passed to `pulumi new`, don't show a confusing message that says it will update a stack.
|
|
|
|
- Fix an issue where an output property of a resource would change its type during an update in some cases.
|
|
|
|
- Provide richer detail on the properties during a multi-stage replace.
|
|
|
|
- Fix `pulumi logs` so it can collect log messages from Lambdas on AWS.
|
|
|
|
- Pulumi now reports metadata during CI runs on CircleCI, for later display on app.pulumi.com.
|
|
|
|
- Fix an assert that could fire if a checkpoint had multiple resources with the same URN (which could happen in cases where a delete operation was pending on an old copy of a resource).
|
|
|
|
- When `$TERM` is set to `dumb`, Pulumi should no longer try to use interactive reading from the terminal, which would fail.
|
|
|
|
- When displaying elapsed time for an update, round to the nearest second.
|
|
|
|
- Add the `--json` flag to the `pulumi logs` command.
|
|
|
|
- Add an `iterable` module to `@pulumi/pulumi` with two helpful combinators `toObject` and `groupBy` to help combine multiple `Output<T>`'s into a single object.
|
|
|
|
- Pulumi no longer prompts you for confirmation when `--skip-preview` is passed to `pulumi update`. Instead, it just preforms the update as requested.
|
|
|
|
- Add the `--json` flag to the `pulumi stack ls` command.
|
|
|
|
- The `--color=always` flag should now be respected in all cases.
|
|
|
|
- Pulumi now reports metadata about GitLab repositories when doing an update, so they can be shown on app.pulumi.com.
|
|
|
|
- Pulumi now uses compression when uploading your checkpoint file to the Pulumi service, which should speed up updates where your stack has many resources.
|
|
|
|
- "First Class" providers used to be shown as changing during previews. This is no longer the case.
|