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

196 lines
11 KiB
Markdown
Raw Normal View History

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
## 0.16.15 (Unreleased)
### 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)).
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
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
- Issue a more perscriptive error when using StackReference and the name of the stack to reference is not of the form `<organization>/<project>/<stack>`.
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