|
1 |
| -## 1.10.0 (Unreleased) |
| 1 | +## 1.10.0-alpha20240814 (August 14, 2024) |
2 | 2 |
|
3 | 3 | BUG FIXES:
|
4 | 4 |
|
5 |
| -- The error message for an invalid default value for an input variable now indicates when the problem is with a nested value in a complex data type. [GH-35465] |
6 |
| -- Sensitive marks could be incorrectly transferred to nested resource values, causing erroneous changes during a plan [GH-35501] |
| 5 | +- The error message for an invalid default value for an input variable now indicates when the problem is with a nested value in a complex data type. ([#35465](https://github.com/hashicorp/terraform/issues/35465)) |
| 6 | +- Sensitive marks could be incorrectly transferred to nested resource values, causing erroneous changes during a plan ([#35501](https://github.com/hashicorp/terraform/issues/35501)) |
7 | 7 | - Allow unknown `error_message` values to pass the core validate step, so variable validation can be completed later during plan
|
8 |
| - [GH-35537] |
9 |
| -- Unencoded slashes within GitHub module source refs were being truncated and incorrectly used as subdirectories in the request path [GH-35552] |
| 8 | + ([#35537](https://github.com/hashicorp/terraform/issues/35537)) |
| 9 | +- Unencoded slashes within GitHub module source refs were being truncated and incorrectly used as subdirectories in the request path ([#35552](https://github.com/hashicorp/terraform/issues/35552)) |
10 | 10 |
|
11 | 11 | ENHANCEMENTS:
|
12 | 12 |
|
13 |
| -- The `element` function now accepts negative indices [GH-35501] |
14 |
| -- Import block validation has been improved to provide more useful errors and catch more invalid cases during `terraform validate` [GH-35543] |
| 13 | +- The `element` function now accepts negative indices ([#35501](https://github.com/hashicorp/terraform/issues/35501)) |
| 14 | +- Import block validation has been improved to provide more useful errors and catch more invalid cases during `terraform validate` ([#35543](https://github.com/hashicorp/terraform/issues/35543)) |
15 | 15 |
|
16 | 16 | EXPERIMENTS:
|
17 | 17 |
|
18 | 18 | Experiments are only enabled in alpha releases of Terraform CLI. The following features are not yet available in stable releases.
|
19 | 19 |
|
20 |
| -* `ephemeral_values`: This [language experiment](https://developer.hashicorp.com/terraform/language/settings#experimental-language-features) introduces a new special kind of value which Terraform allows to change between the plan phase and the apply phase, and between plan/apply rounds. Ephemeral values are never persisted in saved plan files or state snapshots, and so can only be used in parts of the language that don't require values to persist in those artifacts. Ephemeral input values are the main initial example of this concept, allowing the use of input variables to provide dynamic credentials that must change between plan and apply. |
21 |
| -* `terraform test` accepts a new option `-junit-xml=FILENAME`. If specified, and if the test configuration is valid enough to begin executing, then Terraform writes a JUnit XML test result report to the given filename, describing similar information as included in the normal test output. ([#34291](https://github.com/hashicorp/terraform/issues/34291)) |
22 |
| -* The new command `terraform rpcapi` exposes some Terraform Core functionality through an RPC interface compatible with [`go-plugin`](https://github.com/hashicorp/go-plugin). The exact RPC API exposed here is currently subject to change at any time, because it's here primarily as a vehicle to support the [Terraform Stacks](https://www.hashicorp.com/blog/terraform-stacks-explained) private preview and so will be broken if necessary to respond to feedback from private preview participants, or possibly for other reasons. Do not use this mechanism yet outside of Terraform Stacks private preview. |
23 |
| -* The experimental "deferred actions" feature, enabled by passing the `-allow-deferral` option to `terraform plan`, permits `count` and `for_each` arguments in `module`, `resource`, and `data` blocks to have unknown values and allows providers to react more flexibly to unknown values. This experiment is under active development, and so it's not yet useful to participate in this experiment |
| 20 | +- `ephemeral_values`: This [language experiment](https://developer.hashicorp.com/terraform/language/settings#experimental-language-features) introduces a new special kind of value which Terraform allows to change between the plan phase and the apply phase, and between plan/apply rounds. Ephemeral values are never persisted in saved plan files or state snapshots, and so can only be used in parts of the language that don't require values to persist in those artifacts. Ephemeral input values are the main initial example of this concept, allowing the use of input variables to provide dynamic credentials that must change between plan and apply. |
| 21 | +- `terraform test` accepts a new option `-junit-xml=FILENAME`. If specified, and if the test configuration is valid enough to begin executing, then Terraform writes a JUnit XML test result report to the given filename, describing similar information as included in the normal test output. ([#34291](https://github.com/hashicorp/terraform/issues/34291)) |
| 22 | +- The new command `terraform rpcapi` exposes some Terraform Core functionality through an RPC interface compatible with [`go-plugin`](https://github.com/hashicorp/go-plugin). The exact RPC API exposed here is currently subject to change at any time, because it's here primarily as a vehicle to support the [Terraform Stacks](https://www.hashicorp.com/blog/terraform-stacks-explained) private preview and so will be broken if necessary to respond to feedback from private preview participants, or possibly for other reasons. Do not use this mechanism yet outside of Terraform Stacks private preview. |
| 23 | +- The experimental "deferred actions" feature, enabled by passing the `-allow-deferral` option to `terraform plan`, permits `count` and `for_each` arguments in `module`, `resource`, and `data` blocks to have unknown values and allows providers to react more flexibly to unknown values. This experiment is under active development, and so it's not yet useful to participate in this experiment |
24 | 24 |
|
25 | 25 | ## Previous Releases
|
26 | 26 |
|
27 | 27 | For information on prior major and minor releases, refer to their changelogs:
|
28 | 28 |
|
29 |
| -* [v1.9](https://github.com/hashicorp/terraform/blob/v1.9/CHANGELOG.md) |
30 |
| -* [v1.8](https://github.com/hashicorp/terraform/blob/v1.8/CHANGELOG.md) |
31 |
| -* [v1.7](https://github.com/hashicorp/terraform/blob/v1.7/CHANGELOG.md) |
32 |
| -* [v1.6](https://github.com/hashicorp/terraform/blob/v1.6/CHANGELOG.md) |
33 |
| -* [v1.5](https://github.com/hashicorp/terraform/blob/v1.5/CHANGELOG.md) |
34 |
| -* [v1.4](https://github.com/hashicorp/terraform/blob/v1.4/CHANGELOG.md) |
35 |
| -* [v1.3](https://github.com/hashicorp/terraform/blob/v1.3/CHANGELOG.md) |
36 |
| -* [v1.2](https://github.com/hashicorp/terraform/blob/v1.2/CHANGELOG.md) |
37 |
| -* [v1.1](https://github.com/hashicorp/terraform/blob/v1.1/CHANGELOG.md) |
38 |
| -* [v1.0](https://github.com/hashicorp/terraform/blob/v1.0/CHANGELOG.md) |
39 |
| -* [v0.15](https://github.com/hashicorp/terraform/blob/v0.15/CHANGELOG.md) |
40 |
| -* [v0.14](https://github.com/hashicorp/terraform/blob/v0.14/CHANGELOG.md) |
41 |
| -* [v0.13](https://github.com/hashicorp/terraform/blob/v0.13/CHANGELOG.md) |
42 |
| -* [v0.12](https://github.com/hashicorp/terraform/blob/v0.12/CHANGELOG.md) |
43 |
| -* [v0.11 and earlier](https://github.com/hashicorp/terraform/blob/v0.11/CHANGELOG.md) |
| 29 | +- [v1.9](https://github.com/hashicorp/terraform/blob/v1.9/CHANGELOG.md) |
| 30 | +- [v1.8](https://github.com/hashicorp/terraform/blob/v1.8/CHANGELOG.md) |
| 31 | +- [v1.7](https://github.com/hashicorp/terraform/blob/v1.7/CHANGELOG.md) |
| 32 | +- [v1.6](https://github.com/hashicorp/terraform/blob/v1.6/CHANGELOG.md) |
| 33 | +- [v1.5](https://github.com/hashicorp/terraform/blob/v1.5/CHANGELOG.md) |
| 34 | +- [v1.4](https://github.com/hashicorp/terraform/blob/v1.4/CHANGELOG.md) |
| 35 | +- [v1.3](https://github.com/hashicorp/terraform/blob/v1.3/CHANGELOG.md) |
| 36 | +- [v1.2](https://github.com/hashicorp/terraform/blob/v1.2/CHANGELOG.md) |
| 37 | +- [v1.1](https://github.com/hashicorp/terraform/blob/v1.1/CHANGELOG.md) |
| 38 | +- [v1.0](https://github.com/hashicorp/terraform/blob/v1.0/CHANGELOG.md) |
| 39 | +- [v0.15](https://github.com/hashicorp/terraform/blob/v0.15/CHANGELOG.md) |
| 40 | +- [v0.14](https://github.com/hashicorp/terraform/blob/v0.14/CHANGELOG.md) |
| 41 | +- [v0.13](https://github.com/hashicorp/terraform/blob/v0.13/CHANGELOG.md) |
| 42 | +- [v0.12](https://github.com/hashicorp/terraform/blob/v0.12/CHANGELOG.md) |
| 43 | +- [v0.11 and earlier](https://github.com/hashicorp/terraform/blob/v0.11/CHANGELOG.md) |
0 commit comments