maxmustermann/pulumi
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
pulumi/CHANGELOG.md

89 lines
5.2 KiB
Markdown
Raw Normal View History

Add a --config-file option for stack ops (#2258) This option allows the user to override the file used to fetch and store configuration information for a stack. It is available for the config, destroy, logs, preview, refresh, and up commands. Note that this option is not persistent: if it is not specified, the stack's default configuration will be used. If an alternate config file is used exclusively for a stack, it must be specified to all commands that interact with that stack. This option can be used to share plaintext configuration across multiple stacks. It cannot be used to share secret configuration, as secrets are associated with a particular stack and cannot be decryptex by other stacks.
2018-12-01 00:11:05 +01:00
## 0.16.7 (not yet released)
### 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.
Add CHANGELOG.md
2018-11-12 23:50:55 +01:00
Update changelog (#2250) Stamp in release info for 0.16.6.
2018-11-28 19:02:13 +01:00
## 0.16.6 (Released November 28th, 2018)
Add CHANGELOG.md
2018-11-12 23:50:55 +01:00
Update CHANGELOG.md We are still building the muscle to do this per commit, so some things had fallen through the cracks. I walked the output of `git log v0.16.5...master` and added some small notes for improvements that we had not documented.
2018-11-26 07:56:50 +01:00
### Major Changes
Minor wordsmithing in CHANGELOG.md
2018-11-26 19:37:00 +01:00
- 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.
Update CHANGELOG.md We are still building the muscle to do this per commit, so some things had fallen through the cracks. I walked the output of `git log v0.16.5...master` and added some small notes for improvements that we had not documented.
2018-11-26 07:56:50 +01:00
Fix a race when `pulumi plugin install` ran concurrently
2018-11-15 20:54:45 +01:00
### Improvements
Update CHANGELOG.md We are still building the muscle to do this per commit, so some things had fallen through the cracks. I walked the output of `git log v0.16.5...master` and added some small notes for improvements that we had not documented.
2018-11-26 07:56:50 +01:00
- 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))
Minor wordsmithing in CHANGELOG.md
2018-11-26 19:37:00 +01:00
- 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))
Update CHANGELOG.md We are still building the muscle to do this per commit, so some things had fallen through the cracks. I walked the output of `git log v0.16.5...master` and added some small notes for improvements that we had not documented.
2018-11-26 07:56:50 +01:00
- 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))
Minor wordsmithing in CHANGELOG.md
2018-11-26 19:37:00 +01:00
- Fix an issue where `pulumi` would fail to load resource plugins for newer dev builds.
Update CHANGELOG.md We are still building the muscle to do this per commit, so some things had fallen through the cracks. I walked the output of `git log v0.16.5...master` and added some small notes for improvements that we had not documented.
2018-11-26 07:56:50 +01:00
Fix a race when `pulumi plugin install` ran concurrently
2018-11-15 20:54:45 +01:00
- 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.
Look for language plugins next to `pulumi` when probing When launching plugins today, `pulumi` looks in two places: 1. It looks to see if the plugin in on the $PATH and if so, uses it. This makes it easy to force a specific version of a resource provider to be used and is what happens at development time (since resource providers make their way onto $PATH via GOBIN). 2. If the above fails, it looks in the "plugin cache" in `~/.pulumi/plugins`. This is the location that `pulumi plugin install` places plugins. Unlike resource provider plugins, we don't yet deliver language plugins via `pulumi plugin install` so the language provider plugins must be on the `$PATH` to be found. This is okay, because when we ship the SDK, we include the executables next to `pulumi` itself. However, if a user chooses to not put `pulumi` on their $PATH, or they do but it is a symlink to the real `pulumi` binary installed somewhere, we'd fail to find the language plugins, since they would not be on the `$PATH` To address this, when probing for language plugins, also consider binaries next to the currently running `pulumi` process. Fixes #1956
2018-11-20 00:07:01 +01:00
- 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))
Don't fail on configuration keys like `a:config:b:c` Configuration keys are simple namespace/name pairs, delimited by ":". For compatability, we also allow "<namespace>:config:<name>", but we always record the "nice" name in `Pulumi.<stack-name>.yaml`. While `pulumi config` and friends would block setting a key like `a:b:c` (where the "name" has a colon in it), it would allow `a:config:b:c`. However, this would be recorded as `a:b:c` in `Pulumi.<stack-name>.yaml`, which meant we'd error when parsing the configuration file later. To work around this, disallow ":" in the "name" part of a configuration key. With this change the following all work: ``` keyName my-project:keyName my-project:config:keyName ``` However, both `my-project:keyName:subKey` `my-project:config:keyName:subKey` are now disallowed. I considered allowing colons in subkeys, but I think it adds more confusion (due to the interaction with how we allow you elide the project name in the default case) than is worthwhile at this point. Fixes #2171
2018-11-19 23:14:42 +01:00
- 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))
Fix typo in CHANGELOG.md (#2249)
2018-11-28 17:27:28 +01:00
## 0.16.5 (Released November 16th, 2018)
Fix an issue where plugin install would fail on windows The issue is related to this code: https://github.com/pulumi/pulumi/blob/v0.16.4/pkg/workspace/plugins.go#L155-L195 Note that we use `defer` to ensure we close our handle to the file we are unpacking when we encounter a file in the tarball. However, the defers don't run until the containing function ends, so when we go to do the rename, or process still has a bunch of open file handles, which prevents the directory from being renamed because it is "in use". By doing all of the work in an anonymous function, we ensure that the defer statements run before we go to rename the directory Fixes #2217
2018-11-17 02:53:57 +01:00
Merge branch 'release/0.16' into ellismg/merge-release
2018-11-17 05:22:13 +01:00
### Improvements
Fix an issue where plugin install would fail on windows The issue is related to this code: https://github.com/pulumi/pulumi/blob/v0.16.4/pkg/workspace/plugins.go#L155-L195 Note that we use `defer` to ensure we close our handle to the file we are unpacking when we encounter a file in the tarball. However, the defers don't run until the containing function ends, so when we go to do the rename, or process still has a bunch of open file handles, which prevents the directory from being renamed because it is "in use". By doing all of the work in an anonymous function, we ensure that the defer statements run before we go to rename the directory Fixes #2217
2018-11-17 02:53:57 +01:00
- Fix an issue where `pulumi plugin install` would fail on Windows with an access deined message.
Add CHANGELOG.md
2018-11-12 23:50:55 +01:00
Fix typo in CHANGELOG.md (#2249)
2018-11-28 17:27:28 +01:00
## 0.16.4 (Released November 12th, 2018)
Add CHANGELOG.md
2018-11-12 23:50:55 +01:00
### 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.
Reference in a new issue Copy permalink