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

389 lines
22 KiB
Markdown
Raw Normal View History

Update CHANGELOG for 0.17.9 (#2687)
2019-04-30 20:01:58 +02:00
## 0.17.10 (Unreleased)
### Improvements
`pulumi new`: Suppress npm warnings (#2685) Right now, when we run `npm install` as part of `pulumi new`, the following warnings are emitted: ``` node-pre-gyp WARN Using needle for node-pre-gyp https download ... npm WARN aws-typescript@ No description npm WARN aws-typescript@ No repository field. npm WARN aws-typescript@ No license field. ``` We can suppress these warnings by specifying `--loglevel=error` to the `npm install` command.
2019-05-01 18:17:53 +02:00
- Warnings from `npm` about missing description, repository, and license fields in package.json are
now suppressed when `npm install` is run from `pulumi new` (via `npm install --loglevel=error`).
Update CHANGELOG for 0.17.9 (#2687)
2019-04-30 20:01:58 +02:00
## 0.17.9 (Released April 30, 2019)
### Improvements
Update CHANGELOG for 0.17.8
2019-04-23 20:32:31 +02:00
Add support for state in cloud object storage (S3, GCS, Azure) (#2455)
2019-04-25 05:55:39 +02:00
- `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.
Update CHANGELOG.md
2019-04-27 22:47:49 +02:00
- The pulumi version update check can be skipped by setting the environment variable
`PULUMI_SKIP_UPDATE_CHECK` to `1` or `true`.
`pulumi new`: Ensure the stack is selected (#2683) Ensure the stack is selected when using `pulumi new` with an existing stack (e.g. a stack created on app.pulumi.com).
2019-04-29 22:32:15 +02:00
- 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 support for state in cloud object storage (S3, GCS, Azure) (#2455)
2019-04-25 05:55:39 +02:00
Update CHANGELOG for 0.17.8
2019-04-23 20:32:31 +02:00
## 0.17.8 (Released April 23, 2019)
Update changelog for 0.17.6 release (#2639)
2019-04-11 19:53:17 +02:00
Update CHANGELOG.md for release
2019-04-17 17:19:06 +02:00
### Improvements
Add an ignoreChanges resource option (#2657) Fixes #2277. Adds a new ignoreChanges resource option that allows specifying a list of property names whose values will be ignored during updates. The property values will be used for Create, but will be ignored for purposes of updates, and as a result also cannot trigger replacements. This is a feature of the Pulumi engine, not of the resource providers, so no new logic is needed in providers to support this feature. Instead, the engine simply replaces the values of input properties in the goal state with old inputs for properties marked as ignoreChanges. Currently, only top level properties may be specified in ignoreChanges. In the future, this could be extended to support paths to nested properties (including into array elements) with a JSONPath/JMESPath syntax.
2019-04-22 22:54:48 +02:00
- 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)
Add support for state in cloud object storage (S3, GCS, Azure) (#2455)
2019-04-25 05:55:39 +02:00
- Fix an engine bug that could lead to incorrect interpretation of the previous state of a resource leading to
Use Outputs instead of merged Inputs+Outputs (#2659) Fixes #2650. We have historically relied on merging inputs and outputs in several places in the engine. This used to be necessary, as discussed in #2650 (comment), but our core engine model has moved away from depending on this. However, we still have a couple places we do this merge, and those places have triggered several severe issues recently in subtle cases. We believe that this merging should no longer be needed for a correct interpretation of the current engine model, and indeed that doing the merge actively violates the contract with providers. In this PR we remove the remaining places where this input + output merge was being done. In all three cases, we use just the Outputs, which for most providers will already include the same values as the inputs - but correctly as determined by the provider itself.
2019-04-22 22:52:36 +02:00
unexpected Update, Replace or Delete operations being scheduled. [#2650]https://github.com/pulumi/pulumi/issues/2650)
Update CHANGELOG for 0.17.8
2019-04-23 20:32:31 +02:00
- 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)
Add a --json flag to the preview command This change adds a --json flag to the preview command, enabling basic JSON serialization of preview plans. This effectively flattens the engine event stream into a preview structure that contains a list of steps, diagnostics, and summary information. Each step contains the deep serialization of resource state, in addition to metadata about the step, such as what kind of operation it entails. This is a partial implementation of pulumi/pulumi#2390. In particular, we only support --json on the `preview` command itself, and not `up`, meaning that it isn't possible to serialize the result of an actual deployment yet (thereby limiting what you can do with outputs, etc).
2019-04-20 22:34:58 +02:00
- 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/pulumi#2390](https://github.com/pulumi/pulumi/issues/2390).
Use Outputs instead of merged Inputs+Outputs (#2659) Fixes #2650. We have historically relied on merging inputs and outputs in several places in the engine. This used to be necessary, as discussed in #2650 (comment), but our core engine model has moved away from depending on this. However, we still have a couple places we do this merge, and those places have triggered several severe issues recently in subtle cases. We believe that this merging should no longer be needed for a correct interpretation of the current engine model, and indeed that doing the merge actively violates the contract with providers. In this PR we remove the remaining places where this input + output merge was being done. In all three cases, we use just the Outputs, which for most providers will already include the same values as the inputs - but correctly as determined by the provider itself.
2019-04-22 22:52:36 +02:00
Update CHANGELOG.md for release
2019-04-17 17:19:06 +02:00
## 0.17.7 (Released April 17, 2019)
Collect logs from Google Cloud Functions This change adds an operations provider for GCP. Right now, it can just collect logs from google cloud functions, similar to `gcloud functions logs read`
2019-04-05 00:56:44 +02:00
### Improvements
Enable unit testing for Pulumi programs (#2638) * Enable unit testing for Pulumi programs This change enables rudimentary unit testing of your Pulumi programs, by introducing a `PULUMI_TEST_MODE` envvar that, when set, allows programs to run without a CLI. That includes * Just being able to import your Pulumi modules, and test ordinary functions -- which otherwise would have often accidentally triggered the "Not Running in a CLI" error message * Being able to verify a subset of resource properties and shapes, with the caveat that outputs are not included, due to the fact that this is a perpetual "dry run" without any engine operations occurring In principle, this also means you can attach a debugger and step through your code. * Finish the unit testing features This change 1) Incorporates CR feedback, namely requiring that test mode be explicitly enabled for any of this to work. 2) Implements Python support for the same capabilities. 3) Includes tests for both JavaScript and Python SDKs. * Add a note on unit testing to the CHANGELOG * Use Node 8 friendly assert API * Embellish the CHANGELOG entry a bit
2019-04-17 07:20:01 +02:00
- 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.
Warn instead of error when `refresh`'d resource is unhealthy Fixes #2633. Currently when a user runs `refresh` and a resource is in a state of error, the `refresh` will fail and the resource state will not be persisted. This can make it vastly harder to incrementally fix infrastructure. The issue mentioned above explains more of the historical context, as well as some specific failure modes. This commit resolves this issue by causing refresh to *not* report an error in this case, and instead to simply log a warning that the `refresh` has recognized that the resource is in an unhealthy state during state sync.
2019-04-10 22:47:54 +02:00
Update CHANGELOG.md for release
2019-04-17 17:19:06 +02:00
## 0.17.6 (Released April 11, 2019)
### 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.
Collect logs from Google Cloud Functions This change adds an operations provider for GCP. Right now, it can just collect logs from google cloud functions, similar to `gcloud functions logs read`
2019-04-05 00:56:44 +02:00
## 0.17.5 (Released April 8, 2019)
Update changelog (#2594)
2019-03-27 00:53:37 +01:00
Correctly handle FileArchives when the filename contains a dot Our logic for how we handled `.tar.gz` archives meant that any other type of file that had a dot in the filename would not be detected correctly. Fixes #2589
2019-03-26 22:47:29 +01:00
### Improvements
Revert 'Simplify API for passing providers to a ComponentResource (#2602)' (#2606)
2019-03-29 02:31:03 +01:00
Correctly handle FileArchives when the filename contains a dot Our logic for how we handled `.tar.gz` archives meant that any other type of file that had a dot in the filename would not be detected correctly. Fixes #2589
2019-03-26 22:47:29 +01:00
- Correctly handle the case where we would fail to detect an archive type if the filename included a dot in it. (fixes [pulumi/pulumi#2589](https://github.com/pulumi/pulumi/issues/2589))
Make the Python SDK's Config.name argument optional (#2624) This makes the Python SDK's Config constructor name argument optional, similar to what we do in the Node.js SDK. If not supplied, the current project name is used as the default.
2019-04-05 01:55:01 +02:00
- 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.
Collect logs from Google Cloud Functions This change adds an operations provider for GCP. Right now, it can just collect logs from google cloud functions, similar to `gcloud functions logs read`
2019-04-05 00:56:44 +02:00
- `pulumi logs` will now display log messages from Google Cloud Functions.
Update changelog (#2594)
2019-03-27 00:53:37 +01:00
## 0.17.4 (Released March 26, 2019)
Prepare CHANGELOG.md for release (#2591)
2019-03-26 22:45:09 +01:00
Correctly handle FileArchives when the filename contains a dot Our logic for how we handled `.tar.gz` archives meant that any other type of file that had a dot in the filename would not be detected correctly. Fixes #2589
2019-03-26 22:47:29 +01:00
### Improvements
Prepare CHANGELOG.md for release
2019-03-15 23:21:34 +01:00
Don't print `error` prefix when a confirmation prompt is declined Use `result.Result` in more places, so when a confirmation prompt is declined, we just return `result.Bail()` after printing a message without the `error: ` prefix. Fixes #2070
2019-03-25 21:45:12 +01:00
- Don't print the `error:` prefix when Pulumi exists because of a declined confirmation prompt (fixes [pulumi/pulumi#458](https://github.com/pulumi/pulumi/issues/2070))
Revert "Better present interpolated strings during preview. (#2564)" (#2593)
2019-03-27 00:36:43 +01:00
- 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.
Don't print `error` prefix when a confirmation prompt is declined Use `result.Result` in more places, so when a confirmation prompt is declined, we just return `result.Bail()` after printing a message without the `error: ` prefix. Fixes #2070
2019-03-25 21:45:12 +01:00
## 0.17.3 (Released March 26, 2019)
Add support for serializing bigints (#2581)
2019-03-22 23:33:37 +01:00
Prepare CHANGELOG.md for release
2019-03-15 23:21:34 +01:00
### Improvements
Add `pulumi stack rename` `pulumi stack rename` allows you to change the name of an existing stack. This operation is non-distructive, however it is possible that the next update will show additional changes to resources, if the pulumi program uses the value of `getStack()` as part of a resource name.
2019-03-14 23:32:10 +01:00
- A new command, `pulumi stack rename` was added. This allows you to change the name of an existing stack in a project. Note: When a stack is renamed, the `pulumi.getStack` function in the SDK will now return a new value. If a stack name is used as part of a resource name, the next `pulumi update` will not understand that the old and new resources are logically the same. We plan to support adding aliases to individual resources so you can handle these cases. See [pulumi/pulumi#458](https://github.com/pulumi/pulumi/issues/458) for discussion on this new feature. For now, if you are unwilling to have `pulumi update` create and destroy these resources, you can rename your stack back to the old name. (fixes [pulumi/pulumi#2402](https://github.com/pulumi/pulumi/issues/2402))
Fix spurious warnings when using dynamic provider When using a dynamic provider, the following messages are printed, because we did not update the dynamic provider when we added these new RPCs: ``` Method handler checkConfig for /pulumirpc.ResourceProvider/CheckConfig expected but not provided Method handler diffConfig for /pulumirpc.ResourceProvider/DiffConfig expected but not provided ``` Given that we don't do anything for the `configure` RPC today, we can also just no-op these RPCs as well.
2019-03-26 02:22:18 +01:00
- Fix two warnings that were printed when using a dynamic provider about missing method handlers.
Load default providers deterministically (#2590) * Load default providers deterministically This commit adds a new algorithm for deriving a list of default providers from the set of plugins reported from the language host and from the snapshot. If the language host reports a set of plugins, default providers are sourced directly from that set, otherwise default providers are sourced from the full set of plugins, including ones from the snapshot. When multiple versions of the same provider are requested, the newest version of that provider is always select as the default provider. * Add CHANGELOG.md entry * Skip the language host's plugins if it reports no resource plugins * CR feedback * CR: Log when skipping non resource plugin
2019-03-26 21:29:34 +01:00
- A bug in the previous version of the Pulumi CLI occasionally caused the Pulumi Engine to load the incorrect resource
plugin when processing an update. This bug has been fixed in 0.17.3 by performing a deterministic selection of the
best set of plugins available to the engine before starting up. See
Don't print `error` prefix when a confirmation prompt is declined Use `result.Result` in more places, so when a confirmation prompt is declined, we just return `result.Bail()` after printing a message without the `error: ` prefix. Fixes #2070
2019-03-25 21:45:12 +01:00
- Add support for serializing JavaScript function that capture [BigInts](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt).
- Support serializing arrow-functions with deconstructed parameters.
Add `pulumi stack rename` `pulumi stack rename` allows you to change the name of an existing stack. This operation is non-distructive, however it is possible that the next update will show additional changes to resources, if the pulumi program uses the value of `getStack()` as part of a resource name.
2019-03-14 23:32:10 +01:00
Prepare CHANGELOG.md for release
2019-03-15 23:21:34 +01:00
## 0.17.2 (Released March 15, 2019)
Update changelog. (#2504)
2019-03-02 03:56:12 +01:00
### Improvements
Show `brew upgrade` when installed with Homebrew (#2519) Show `brew upgrade pulumi` as the upgrade message when the currently running pulumi executable is on macOS and running from the brew install directory.
2019-03-06 19:56:44 +01:00
- Show `brew upgrade pulumi` as the upgrade message when the currently running `pulumi` executable
is running on macOS from the brew install directory.
Filter diff keys based on provider info (#2526) If a provider returns information about the top-level properties that differ, use those keys to filter the diffs that are rendered to the user. Fixes #2453.
2019-03-07 01:41:19 +01:00
- Resource diffs that are rendered to the console are now filtered to properties that have semantically-meaningful
changes where possible.
Stop running `up` as part of `pulumi new` (#2539) Originally, `pulumi new` did not run `up` after generating a project. To help users get a deployed stack as quickly as possible, we changed `pulumi new` to run an initial deployment at the end of its operation. Users would first see a preview and get to decide whether to proceed with an initial deployment, and then continue to iterate from there. Note that this would only happen for nodejs projects (TypeScript/JavaScript). We would not run `up` for Python projects as we require the user to run `pip install` in a virtualenv, so we'd print instructions with the necessary commands the user must run instead. Running `up` as part of `pulumi new` for nodejs projects has ended up being more confusing than helpful for new users, and annoying for experienced users. New users aren't expecting `pulumi new` to run an initial deployment after generating the project (they haven't even looked at the project source yet). Experienced users find it frustrating as you typically want to just generate the project, and don't want to have to wait for the preview just to decline running the update. This change reverts `pulumi new` back to not running `up` automatically for nodejs projects. Instead, like with Python projects, at the end of the operation, we print instructions to the user to run `pulumi up` to deploy the project.
2019-03-11 20:32:40 +01:00
- `pulumi new` no longer runs an initial deployment after a project is generated for nodejs projects.
Instead, instructions are printed indicating that `pulumi up` can be used to deploy the project.
Refresh inputs (#2531) These changes take advantage of the newly-added support for returning inputs from Read to update a resource's inputs as part of a refresh. As a consequence, the Pulumi engine will now properly detect drift between the actual state of a resource and the desired state described by the program and generate appropriate update or replace steps. As part of these changes, a resource's old inputs are now passed to the provider when performing a refresh. The provider can take advantage of this to maintain the accuracy of any additional data or metadata in the resource's inputs that may need to be updated during the refresh. This is required for the complete implementation of https://github.com/pulumi/pulumi-terraform/pull/349. Without access to the old inputs for a resource, TF-based providers would lose all information about default population during a refresh.
2019-03-11 21:50:00 +01:00
- Differences between the state of a refreshed resource and the state described in a Pulumi program are now properly
detected when using newer providers.
Elide diffs in internal properties (#2543) Various providers use properties that begin with "__" to represent internal metadata that should not be presented to the user. These changes look for such properties and elide them when displaying diffs.
2019-03-12 02:01:48 +01:00
- Differences between a resource's provider-internal properties are no longer displayed in the CLI.
Install missing plugins on startup (#2560) * Install missing plugins on startup This commit addresses the problem of missing plugins by scanning the snapshot and language host on startup for the list of required plugins and, if there are any plugins that are required but not installed, installs them. The mechanism by which plugins are installed is exactly the same as 'pulumi plugin install'. The installation of missing plugins is best-effort and, if it fails, will not fail the update. This commit addresses pulumi/pulumi-azure#200, where users using Pulumi in CI often found themselves missing plugins. * Add CHANGELOG * Skip downloading plugins if no client provided * Reduce excessive test output * Update Gopkg.lock * Update pkg/engine/destroy.go Co-Authored-By: swgillespie <sean@pulumi.com> * CR: make pluginSet a newtype * CR: Assign loop induction var to local var
2019-03-15 23:01:37 +01:00
- Pulumi will now install missing plugins on startup. Previously, Pulumi would error if a required plugin was not
present and a bug in the Pulumi CLI made it common for users using Pulumi in their continuous integration setup to have problems with missing plugins. Starting with 0.17.2, if Pulumi detects that required plugins are missing, it will make an attempt to install the missing plugins before proceeding with the update.
Show `brew upgrade` when installed with Homebrew (#2519) Show `brew upgrade pulumi` as the upgrade message when the currently running pulumi executable is on macOS and running from the brew install directory.
2019-03-06 19:56:44 +01:00
Tweak signature of .apply to help TS infer things better. (#2520)
2019-03-06 10:53:58 +01:00
## 0.17.1 (Released March 6, 2019)
### Improvements
- Slight tweak to `Output.apply` signature to help TypeScript infer types better.
Update `@pulumi/pulumi` to version 0.17.0 (#2510) This update includes several changes to core `@pulumi/pulumi` constructs that will not play nicely in side-by-side applications that pull in prior versions of this package. As such, we are rev'ing the minor version of the package from 0.16 to 0.17. Recent version of `pulumi` will now detect, and warn, if different versions of `@pulumi/pulumi` are loaded into the same application. If you encounter this warning, it is recommended you move to versions of the `@pulumi/...` packages that are compatible. i.e. keep everything on 0.16.x until you are ready to move everything to 0.17.x. ### Improvements - `Output<T>` now 'lifts' property members from the value it wraps, simplifying common coding patterns. Note: this wrapping only happens for POJO values, not `Output<Resource>`s. - Depending on a **Component** Resource will now depend on all other Resources parented by that Resource. This will help out the programming model for Component Resources as your consumers can just depend on a Component and have that automatically depend on all the child Resources created by that Component. Note: this does not apply to a **Custom** resource. Depending on a CustomResource will still only wait on that single resource being created, not any other Resources that consider that CustomResource to be a parent.
2019-03-06 02:06:57 +01:00
## 0.17.0 (Released March 5, 2019)
This update includes several changes to core `@pulumi/pulumi` constructs that will not play nicely
in side-by-side applications that pull in prior versions of this package. As such, we are rev'ing
the minor version of the package from 0.16 to 0.17. Recent version of `pulumi` will now detect,
and warn, if different versions of `@pulumi/pulumi` are loaded into the same application. If you
encounter this warning, it is recommended you move to versions of the `@pulumi/...` packages that
are compatible. i.e. keep everything on 0.16.x until you are ready to move everything to 0.17.x.
### Improvements
- `Output<T>` now 'lifts' property members from the value it wraps, simplifying common coding patterns.
Update changelog (#2516)
2019-03-06 02:29:53 +01:00
For example:
```ts
interface Widget { text: string, x: number, y: number };
var v: Output<Widget>;
var widgetX = v.x;
// `widgetX` has the type Output<number>.
// This is equivalent to writing `v.apply(w => w.x)`
```
Note: this 'lifting' only occurs for POJO values. It does not happen for `Output<Resource>`s.
Similarly, this only happens for properties. Functions are not lifted.
Update `@pulumi/pulumi` to version 0.17.0 (#2510) This update includes several changes to core `@pulumi/pulumi` constructs that will not play nicely in side-by-side applications that pull in prior versions of this package. As such, we are rev'ing the minor version of the package from 0.16 to 0.17. Recent version of `pulumi` will now detect, and warn, if different versions of `@pulumi/pulumi` are loaded into the same application. If you encounter this warning, it is recommended you move to versions of the `@pulumi/...` packages that are compatible. i.e. keep everything on 0.16.x until you are ready to move everything to 0.17.x. ### Improvements - `Output<T>` now 'lifts' property members from the value it wraps, simplifying common coding patterns. Note: this wrapping only happens for POJO values, not `Output<Resource>`s. - Depending on a **Component** Resource will now depend on all other Resources parented by that Resource. This will help out the programming model for Component Resources as your consumers can just depend on a Component and have that automatically depend on all the child Resources created by that Component. Note: this does not apply to a **Custom** resource. Depending on a CustomResource will still only wait on that single resource being created, not any other Resources that consider that CustomResource to be a parent.
2019-03-06 02:06:57 +01:00
- Depending on a **Component** Resource will now depend on all other Resources parented by that
Resource. This will help out the programming model for Component Resources as your consumers can
just depend on a Component and have that automatically depend on all the child Resources created
by that Component. Note: this does not apply to a **Custom** resource. Depending on a
CustomResource will still only wait on that single resource being created, not any other Resources
that consider that CustomResource to be a parent.
Update changelog (#2532)
2019-03-07 21:47:23 +01:00
## 0.16.19 (Released March 4, 2019)
- Rolled back change where calling toString/toJSON on an Output would cause a message
to be logged to the `pulumi` diagnostics stream.
Update changelog. (#2504)
2019-03-02 03:56:12 +01:00
## 0.16.18 (Released March 1, 2019)
Rollback waiting on children of a component when waiting on the component. (cherry picked from commit d1ecc5a25066e931c5ec51f75a9a33d684216809)
2019-02-27 21:12:23 +01:00
Look for exact match when loading plugins (#2483) * Look for exact match when loading plugins Pulumi's current behavior when loading plugins is surprising in that it will attempt to load the "latest" provider binary instead of exactly the version that was requested. Since provider binaries and provider packages are tied together and versioned together, this is going to be problematic if a provider makes a breaking change. Although there are other issues in this area, this commit fixes the arguably bug-like behavior of loading the latest plugin and instead opts to load the plugin that exactly the requested semver range. Today, the engine will never ask for anything other than an exact version match. Since this is a breaking change, this commit also includes an environment variable that allows users to return back to the "old" plugin loading behavior if they are broken. The intention is that this escape hatch can be removed in a future release once we are confident that this change does not break people. * CR feedback * Use SelectCompatiblePlugin for HasPluginGTE check
2019-03-02 00:42:38 +01:00
- Fix an issue where the Pulumi CLI would load the newest plugin for a resource provider instead of the version that was
requested, which could result in the Pulumi CLI loading a resource provider plugin that is incompatible with the
program. This has the potential to disrupt users that previously had working configurations; if you are experiencing
problems after upgrading to 0.16.17, you can opt-in to the legacy plugin load behavior by setting the environnment
variable `PULUMI_ENABLE_LEGACY_PLUGIN_SEARCH=1`. You can also install plugins that are missing with the command
`pulumi plugin install resource <name> <version> --exact`.
Rollback waiting on children of a component when waiting on the component. (cherry picked from commit d1ecc5a25066e931c5ec51f75a9a33d684216809)
2019-02-27 21:12:23 +01:00
### Improvements
Converting an Output to a string or JSON now produces a warning . (#2496)
2019-02-28 01:00:54 +01:00
- Attempting to convert an [Output<T>] to a string or to JSON will now result in a warning
message being printed, as well as information on how to rectify the situation. This is
to help with diagnosing cryptic problems that can occur when Outputs are accidentally
concatenated into a string in some part of the program.
Incorrect closure serialization when object referenced through different functions. (#2497)
2019-02-28 20:11:43 +01:00
- Fixes incorrect closure serialization issue (https://github.com/pulumi/pulumi/pull/2497)
Do a version check and emit a warning if major/minor versions of @pulumi/pulumi do not match. (#2503)
2019-03-02 02:43:26 +01:00
- `pulumi` will now check that all versions of `@pulumi/pulumi` are compatible in your node_modules
folder, and will issue a warning message if not. To be compatible, the versions of
`@pulumi/pulumi` must agree on their major and minor versions. Running incompatible versions is
not something that will be blocked, but it is discouraged as it may lead to subtle problems if one
version of `@pulumi/pulumi` is loaded and passes objects to/from an incompatible version.
Rollback waiting on children of a component when waiting on the component. (cherry picked from commit d1ecc5a25066e931c5ec51f75a9a33d684216809)
2019-02-27 21:12:23 +01:00
## 0.16.17 (Released February 27th, 2019)
### Improvements
- Rolling back the change:
"Depending on a Resource will now depend on all other Resource's parented by that Resource."
Unforseen problems cropped up that caused deadlocks. Removing this change until we can
have a high quality solution without these issues.
## 0.16.16 (Released February 24th, 2019)
Update changelog (#2466)
2019-02-22 10:00:00 +01:00
### Improvements
Fix deadlock when waiting for transitive dependencies (#2471)
2019-02-24 21:14:16 +01:00
- Fix deadlock with resource dependencies (https://github.com/pulumi/pulumi/issues/2470)
Update changelog (#2466)
2019-02-22 10:00:00 +01:00
## 0.16.15 (Released February 22nd, 2019)
Ensure InvokeRequest is defined InvokeRequest is defined in provider_pb.js not resource_pb.js. Require that module instead.
2019-01-31 20:19:36 +01:00
### Improvements
Show a better error when `--force` needs to be passed to `stack rm` When `pulumi stack rm` is run against a stack with resources, the service will respond with an error if `--force` is not passed. Previously we would just dump the contents of this error and it looked something like: `error: [400] Bad Request: Stack still has resources.` We now handle this case more gracefully, showing our usual "this stack still has resources" error like we would for the local backend. Fixes #2431
2019-02-07 04:07:31 +01:00
- When trying to `stack rm` a stack managed by pulumi.com that has resources, the error message now informs you to pass `--force` if you really want to remove a stack that still has resources under management, as this would orphan these resources (fixes [pulumi/pulumi#2431](https://github.com/pulumi/pulumi/issues/2431)).
Enable delete parallelism for Python (#2443) * Enable delete parallelism for Python * Add CHANGELOG.md entry * Expand changelog message - upgrade to Python 3 * Rework stack rm test The service now allows removing a stack if it just contains the top level `pulumi:pulumi:Stack` resource, so we need to actually create another resource before `stack rm` fails telling you to pass `--force`. Fixes #2444
2019-02-12 23:49:43 +01:00
- Enabled Python programs to delete resources in parallel (fixes [pulumi/pulumi#2382](https://github.com/pulumi/pulumi/issues/2382)). If you are using Python 2, you should upgrade to Python 3 or else you may experience problems when deleting resources.
Fix an issue with empty ID for CustomResource (#2449) * Fix an issue with empty ID for CustomResource The Python runtime was checking the ID field it receives from the engine against None, assuming that the engine would not set the ID field if one was not present. However, it does set the ID field; it is set to the empty string when an ID is not known. This commit fixes an issue that can cause certain IDs to be erroneously considered to be known during previews, which can cause problems during the Check phase of resources that directly reference IDs of other resources. * Add CHANGELOG
2019-02-15 18:55:19 +01:00
- Fixed an issue where Python programs would occasionally fail during preview with errors about empty IDs being passed
to resources. ([pulumi/pulumi#2450](https://github.com/pulumi/pulumi/issues/2450))
Return error from stack tag commands in local mode (#2457) Instead of operating as no-ops, return an error to make it more clear that these commands are not currently implemented when using --local mode.
2019-02-20 01:07:57 +01:00
- Return an error from `pulumi stack tag` commands when using the `--local` mode.
Have child resources update their parent urn to include themselves in its dependencies. (#2299)
2019-02-22 05:18:29 +01:00
- Depending on a Resource will now depend on all other Resource's parented by that Resource.
This will help out the programming model for Component Resources as your consumers can just
depend on a Component and have that automatically depend on all the child Resources created
by that Component.
Show a better error when `--force` needs to be passed to `stack rm` When `pulumi stack rm` is run against a stack with resources, the service will respond with an error if `--force` is not passed. Previously we would just dump the contents of this error and it looked something like: `error: [400] Bad Request: Stack still has resources.` We now handle this case more gracefully, showing our usual "this stack still has resources" error like we would for the local backend. Fixes #2431
2019-02-07 04:07:31 +01:00
Fix date text
2019-02-12 00:28:17 +01:00
## 0.16.14 (Released January 31st, 2019)
Ensure InvokeRequest is defined InvokeRequest is defined in provider_pb.js not resource_pb.js. Require that module instead.
2019-01-31 20:19:36 +01:00
### Improvements
- Fix a regression in `@pulumi/pulumi` introduced by 0.16.13 where an update could fail with an error like:
```
Diagnostics:
pulumi:pulumi:Stack (my-great-stack):
TypeError: resproto.InvokeRequest is not a constructor
at Object.<anonymous> (.../node_modules/@pulumi/pulumi/runtime/invoke.js:58:25)
at Generator.next (<anonymous>)
at fulfilled (.../node_modules/@pulumi/pulumi/runtime/invoke.js:17:58)
at <anonymous>
```
We appologize for the regression. (fixes [pulumi/pulumi#2414](https://github.com/pulumi/pulumi/issues/2414))
Prepare for v0.16.13
2019-01-31 06:17:34 +01:00
Add support for explicit delete-before-replace (#2415) These changes add a new flag to the various `ResourceOptions` types that indicates that a resource should be deleted before it is replaced, even if the provider does not require this behavior. The usual delete-before-replace cascade semantics apply. Fixes #1620.
2019-01-31 23:27:53 +01:00
### Improvements
- Individual resources may now be explicitly marked as requiring delete-before-replace behavior. This can be used e.g. to handle explicitly-named resources that may not be able to be replaced in the usual manner.
Fix date text
2019-02-12 00:28:17 +01:00
## 0.16.13 (Released January 31st, 2019)
Prepare for v0.16.13
2019-01-31 06:17:34 +01:00
### Major Changes
- When used in conjuction with the latest versions of the various language SDKs, the Pulumi CLI is now more precise about the dependent resources that must be deleted when a given resource must be deleted before it can be replaced (fixes [pulumi/pulumi#2167](https://github.com/pulumi/pulumi/issues/2167)).
**NOTE**: As part of the above change, once a stack is updated with v0.16.13, previous versions of `pulumi` will be unable to manage it.
Update CHANGELOG.md for 0.16.12
2019-01-26 00:26:01 +01:00
### Improvements
Spelling (#2521)
2019-03-06 11:58:08 +01:00
- Issue a more prescriptive error when using StackReference and the name of the stack to reference is not of the form `<organization>/<project>/<stack>`.
Improve StackReference error message Because of the change to include a stack's project as part of its identity in the service, the names passed to StackReference now require the project name as well. Improve the error message when they do not include them.
2019-01-31 00:57:44 +01:00
Update CHANGELOG.md for 0.16.12
2019-01-26 00:26:01 +01:00
## 0.16.12 (Released January 25th, 2019)
Update CHANGELOG.md for 0.16.11
2019-01-17 01:54:30 +01:00
Update CHANGELOG.md
2019-01-25 21:52:33 +01:00
### Major Changes
- When using the cloud backend, stack names now must only be unique within a project, instead of across your entire account. Starting with version of 0.16.12 the CLI, you can create stacks with duplicate names. If an account has multiple stacks with the same name across different projects, you must use 0.16.12 or later of the CLI to manage them.
Use project name as part of stack identity with cloud backend This change starts to use a stack's project name as part of it's identity when talking to the cloud backend, which the Pulumi Service now supports. When displaying or parsing stack names for the cloud backend, we now support the following schemes: `<stack-name>` `<owner-name>/<stack-name>` `<owner-name>/<project-name>/<stack-name>` When the owner is not specificed, we assume the currently logged in user (as we did before). When the project name is not specificed, we use the current project (and fail if we can't find a `Pulumi.yaml`) Fixes #2039
2019-01-18 23:37:05 +01:00
Improve StackReference error message Because of the change to include a stack's project as part of its identity in the service, the names passed to StackReference now require the project name as well. Improve the error message when they do not include them.
2019-01-31 00:57:44 +01:00
**BREAKING CHANGE NOTICE**: As part of the above change, when using the 0.16.12 CLI (or a later version) the names passed to `StackReference` must be updated to be of the form (`<organization>/<project>/<stack>`) e.g. `acmecorp/infra/dev` to refer to the `dev` stack of the `infra` project in the `acmecorp` organization.
Update CHANGELOG.md for 0.16.11
2019-01-17 01:54:30 +01:00
### Improvements
Add `--json` to `pulumi history`
2019-01-22 23:28:02 +01:00
- Add `--json` to `pulumi config`, `pulumi config get`, `pulumi history` and `pulumi plugin ls` to request the output be in JSON.
Add `--json` to `pulumi config get` and `pulumi config` This supports using `--json` to get configuration information in a structured way. The objects we return have the following schema: ``` { name: string; value: string?; secret: bool; } ``` In the case of `pulumi config` when --show-secrets is not passed, and there are secret values, the `value` property of the object for that configuration value will not be set. This differs from the normal rendering where we show `[secret]`. Contributes To #496
2019-01-18 22:54:56 +01:00
`pulumi new` improvements (#2379) Some changes to `pulumi new` to improve the experience: - Color the default values for config differently to make them stand out better - Mention that `new` will also perform an initial deployment - Add more vertical whitespace between steps in the process - Print message indicating the "Installing dependencies" step is complete - After "project is ready to go", add a note about doing an initial deployment - Output follow-up command to run when an update fails - Go back to showing the `npm install` output as `npm` doesn't always return an error code when it runs into problems
2019-01-23 17:57:48 +01:00
- Changes to `pulumi new`'s output to improve the experience.
Update CHANGELOG.md for 0.16.11
2019-01-17 01:54:30 +01:00
## 0.16.11 (Released January 16th, 2019)
Update CHANGELOG for 0.16.10 release
2019-01-12 00:18:34 +01:00
Update CHANGELOG.md The previous commit added a note in the wrong section. Simply move the note and add some context that these new features only work in nodejs.
2019-01-16 20:58:15 +01:00
### Improvements
- In the nodejs SDK, `pulumi.interpolate` and `pulumi.concat` have been added as convenient ways to combine Output values into strings.
Update CHANGELOG.md for 0.16.11
2019-01-17 01:54:30 +01:00
- Added `pulumi history` to show information about the history of updates to a stack.
- When creating a project with `pulumi new` the generated `Pulumi.yaml` file no longer contains the template section, which was unused after creating a project
- In the Python SDK, the `is_dry_run` function just always returned `true`, even when an update (and not a preview) was being preformed. This has been fixed.
- Python programs will no longer deadlock due to exceptions in functions run during applies.
Update CHANGELOG for 0.16.10 release
2019-01-12 00:18:34 +01:00
## 0.16.10 (Released January 11th, 2019)
Update CHANGELOG.md for 0.16.9 release
2018-12-25 05:41:44 +01:00
Link directly to /account/tokens (#2328) We're changing /account to redirect to /account/profile instead of /account/tokens as the user profile settings are a more natural place to land when going into account settings. This commit changes the CLI to link directly to /account/tokens, avoiding having to click on "Access Tokens" to go to the tokens page to get an access token when coming from the URL outputted by the CLI.
2018-12-29 00:06:03 +01:00
### Improvements
Update CHANGELOG for 0.16.10 release
2019-01-12 00:18:34 +01:00
- Support for first-class providers in Python.
- Fix a bug where `StackReference` outputs were not updated when changes occured in the referenced stack.
Add commands for managing stack tags (#2333) Adds `pulumi stack tag` commands for managing stack tags.
2019-01-04 22:23:47 +01:00
- Added `pulumi stack tag` commands for managing stack tags stored in the cloud backend.
Link directly to /account/tokens (#2328) We're changing /account to redirect to /account/profile instead of /account/tokens as the user profile settings are a more natural place to land when going into account settings. This commit changes the CLI to link directly to /account/tokens, avoiding having to click on "Access Tokens" to go to the tokens page to get an access token when coming from the URL outputted by the CLI.
2018-12-29 00:06:03 +01:00
- Link directly to /account/tokens when prompting for an access token.
Convert resource to pojo objects when used as stack outputs. (#2311)
2019-01-03 19:03:11 +01:00
- Exporting a Resource from an application Stack now exports it as a rich recursive pojo instead of just being an opaque URN (fixes https://github.com/pulumi/pulumi/issues/1858).
Update CHANGELOG for 0.16.10 release
2019-01-12 00:18:34 +01:00
## 0.16.9 (Released December 24th, 2018)
Improve error message when `Pulumi.yaml` can't be found Fixes #2234
2018-12-05 23:00:14 +01:00
### 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))
Add `--stack` argument to a few missing commands (#2278) As of this change, all of the stack specific commands for `pulumi` now allow passing `--stack` to operate on a different stack from the default one. Fixes #1648
2018-12-10 19:10:43 +01:00
- 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))
Update CHANGELOG.md Add in some fixes and features that were missing from `CHANGELOG.md`
2018-12-24 17:44:59 +01:00
- Added `Output.all` and `Output.from_input` to the Python SDK.
- During previews and updates, read operations (i.e. calls to `.get` methods) are no longer shown in the output unless they cause any changes.
- Fix a performance regression where `pulumi preview` and `pulumi update` would hang for a few moments at the end of a preview or update, in additon to the overall operation being slower.
Link directly to /account/tokens (#2328) We're changing /account to redirect to /account/profile instead of /account/tokens as the user profile settings are a more natural place to land when going into account settings. This commit changes the CLI to link directly to /account/tokens, avoiding having to click on "Access Tokens" to go to the tokens page to get an access token when coming from the URL outputted by the CLI.
2018-12-29 00:06:03 +01:00
Fix synchronization with the event renderer (#2290) The event rendering goroutine in the remote backend was not properly synchronizing with the goroutine that created it, and could continue executing after its creator finished. I believe that this is the root cause of #1850. (cherry picked from commit ded3882afdaf9bbc76c324b9feac46aea6fd97cb)
2018-12-14 23:19:01 +01:00
## 0.16.8 (Released December 14th, 2018)
Update CHANGELOG.md for v0.16.7
2018-12-05 23:32:32 +01:00
Merge v0.16.8 into master
2018-12-15 00:32:48 +01:00
### Improvements
Fix synchronization with the event renderer (#2290) The event rendering goroutine in the remote backend was not properly synchronizing with the goroutine that created it, and could continue executing after its creator finished. I believe that this is the root cause of #1850.
2018-12-14 04:58:26 +01:00
- Fix an issue that caused panics due to shutting the Jaeger tracing infrastructure down before all traces had finished ([pulumi/pulumi#1850](https://github.com/pulumi/pulumi/issues/1850))
Fix synchronization with the event renderer (#2290) The event rendering goroutine in the remote backend was not properly synchronizing with the goroutine that created it, and could continue executing after its creator finished. I believe that this is the root cause of #1850. (cherry picked from commit ded3882afdaf9bbc76c324b9feac46aea6fd97cb)
2018-12-14 23:19:01 +01:00
## 0.16.7 (Released December 5th, 2018)
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
### 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.
Enable ANSI colorization in Windows terminal (#2269) Before the windows console will understand ANSI colorization codes the terminal must be put in a special mode by passing ENABLE_VIRTUAL_TERMINAL_PROCESSING to SetConsoleMode. This was happening as a side effect of term.StdStreams() from a docker package, which we did before displaying the update data. However, any colorization done before that call would just show the raw ANSI escape codes. Call this helper much earlier (i.e. as soon as the CLI starts up) so any messages that we print will have the correct colorization applied to them. Fixes #2214
2018-12-05 01:58:32 +01:00
- Fix an issue where ANSI escape codes would appear in messages printed from the CLI when running on Windows.
Update CHANGELOG.md for v0.16.7
2018-12-05 23:32:32 +01:00
Do not disable echo when stdin is not a terminal When reading values like access keys or secrets from the terminal, we would use the `terminal.ReadPassword` function to ensure characters the user typed were not echo'd back to the console, as a convience. When standard input was not connected to a tty (which would happen in some cases like in docker when -t was not passed or in CI), this would fail with an error about an bad ioctl. Update our logic such that when standard in is not connected to a terminal, we just read input normally. While I was in the area, I unified the code for Windows and *NIX for these functions. Fixes #2017
2018-12-01 14:05:24 +01:00
- 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.
Add CHANGELOG.md
2018-11-12 23:50:55 +01:00
Do not use relative path when launching dynamic provider Previously, we assumed that the dynamic provider was located in `./node_modules/@pulumi/pulumi/../` which is correct in the majority of cases. However, tools like lerna or yarn workspaces (or custom workflows) allow the node_modules folder to be located elsewhere on disk, and node will still find it because of its algorithm for module resolution. So, do what we do in the language host itself, first launch node and ask it to tell us where it resolves a require statement to on disk and then launch node against that script. Fixes #2261
2018-12-05 20:30:00 +01:00
- 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))
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