|
1 | | -## 1.9.0 (Unreleased) |
| 1 | +## 1.8.1 (Unreleased) |
2 | 2 |
|
3 | | -ENHANCEMENTS: |
| 3 | +BUG FIXES: |
4 | 4 |
|
5 | | -* `terraform console`: Now has basic support for multi-line input in interactive mode. ([#34822](https://github.com/hashicorp/terraform/pull/34822)) |
| 5 | +* Plan renderer: Correctly render strings that begin with JSON compatible text but don't end with it. ([#34959](https://github.com/hashicorp/terraform/pull/34959)) |
6 | 6 |
|
7 | | - If an entered line contains opening paretheses/etc that are not closed, Terraform will await another line of input to complete the expression. This initial implementation is primarily intended to support pasting in multi-line expressions from elsewhere, rather than for manual multi-line editing, so the interactive editing support is currently limited. |
8 | | -* `cli`: Updates the Terraform CLI output to show logical separation between OPA and Sentinel policy evaluations |
| 7 | +## 1.8.0 (April 10, 2024) |
9 | 8 |
|
10 | | -BUG FIXES: |
| 9 | +If you are upgrading from Terraform v1.7 or earlier, please refer to |
| 10 | +[the Terraform v1.8 Upgrade Guide](https://developer.hashicorp.com/terraform/language/v1.8.x/upgrade-guides). |
11 | 11 |
|
12 | | -* `remote-exec`: Each remote connection will be closed immediately after use ([#34137](https://github.com/hashicorp/terraform/issues/34137)) |
13 | | -* `backend/s3`: Fixed the digest value displayed for DynamoDB/S3 state checksum mismatches ([#34387](https://github.com/hashicorp/terraform/issues/34387)) |
| 12 | +NEW FEATURES: |
14 | 13 |
|
15 | | -EXPERIMENTS: |
| 14 | +* Providers can now offer functions which can be used from within the Terraform configuration language. |
16 | 15 |
|
17 | | -Experiments are only enabled in alpha releases of Terraform CLI. The following features are not yet available in stable releases. |
| 16 | + The syntax for calling a provider-contributed function is `provider::provider_name::function_name()`. ([#34394](https://github.com/hashicorp/terraform/issues/34394)) |
| 17 | +* Providers can now transfer the ownership of a remote object between resources of different types, for situations where there are two different resource types that represent the same remote object type. |
| 18 | + |
| 19 | + This extends the `moved` block behavior to support moving between two resources of different types only if the provider for the target resource type declares that it can convert from the source resource type. Refer to provider documentation for details on which pairs of resource types are supported. |
| 20 | +* New `issensitive` function returns true if the given value is marked as sensitive. |
| 21 | + |
| 22 | +ENHANCEMENTS: |
| 23 | + |
| 24 | +* `terraform test`: File-level variables can now refer to global variables. ([#34699](https://github.com/hashicorp/terraform/issues/34699)) |
| 25 | +* When generating configuration based on `import` blocks, Terraform will detect strings that contain valid JSON syntax and generate them as calls to the `jsonencode` function, rather than generating a single string. This is primarily motivated by readability, but might also be useful if you need to replace part of the literal value with an expression as you generalize your module beyond the one example used for importing. |
| 26 | +* `terraform plan` now uses a different presentation for describing changes to lists where the old and new lists have the same length. It now compares the elements with correlated indices and shows a separate diff for each one, rather than trying to show a diff for the list as a whole. The behavior is unchanged for lists of different lengths. |
| 27 | +* `terraform providers lock` accepts a new boolean option `-enable-plugin-cache`. If specified, and if a [global plugin cache](https://developer.hashicorp.com/terraform/cli/config/config-file#provider-plugin-cache) is configured, Terraform will use the cache in the provider lock process. ([#34632](https://github.com/hashicorp/terraform/issues/34632)) |
| 28 | +* built-in "terraform" provider: new `decode_tfvars`, `encode_tfvars`, and `encode_expr` functions, for unusual situations where it's helpful to manually generate or read from Terraform's "tfvars" format. ([#34718](https://github.com/hashicorp/terraform/issues/34718)) |
| 29 | +* `terraform show`'s JSON rendering of a plan now includes two explicit flags `"applyable"` and `"complete"`, which both summarize characteristics of a plan that were previously only inferrable by consumers replicating some of Terraform Core's own logic. ([#34642](https://github.com/hashicorp/terraform/issues/34642)) |
| 30 | + |
| 31 | + `"applyable"` means that it makes sense for a wrapping automation to offer to apply this plan. |
| 32 | + |
| 33 | + `"complete"` means that applying this plan is expected to achieve convergence between desired and actual state. If this flag is present and set to `false` then wrapping automations should ideally encourage an operator to run another plan/apply round to continue making progress toward convergence. |
| 34 | + |
| 35 | +BUG FIXES: |
18 | 36 |
|
19 | | -* `variable_validation_crossref`: This [language experiment](https://developer.hashicorp.com/terraform/language/settings#experimental-language-features) allows `validation` blocks inside input variable declarations to refer to other objects inside the module where the variable is declared, including to the values of other input variables in the same module. |
20 | | -* `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)) |
21 | | -* 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. |
22 | | -* 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. |
| 37 | +* core: Sensitive values will now be tracked more accurately in state and plans, preventing unexpected updates with no apparent changes. ([#34567](https://github.com/hashicorp/terraform/issues/34567)) |
| 38 | +* core: Fix incorrect error message when using in invalid `iterator` argument within a dynamic block. ([#34751](https://github.com/hashicorp/terraform/issues/34751)) |
| 39 | +* core: Fixed edge-case bug that could cause loss of floating point precision when round-tripping due to incorrectly using a MessagePack integer to represent a large non-integral number. ([#24576](https://github.com/hashicorp/terraform/issues/24576)) |
| 40 | +* config: Converting from an unknown map value to an object type now correctly handles the situation where the map element type disagrees with an optional attribute of the target type, since when a map value is unknown we don't yet know which keys it has and thus cannot predict what subset of the elements will get converted as attributes in the resulting object. ([#34756](https://github.com/hashicorp/terraform/issues/34756)) |
| 41 | +* cloud: Fixed unparsed color codes in policy failure error messages. ([#34473](https://github.com/hashicorp/terraform/issues/34473)) |
23 | 42 |
|
24 | 43 | ## Previous Releases |
25 | 44 |
|
26 | 45 | For information on prior major and minor releases, see their changelogs: |
27 | 46 |
|
28 | | -* [v1.8](https://github.com/hashicorp/terraform/blob/v1.8/CHANGELOG.md) |
29 | 47 | * [v1.7](https://github.com/hashicorp/terraform/blob/v1.7/CHANGELOG.md) |
30 | 48 | * [v1.6](https://github.com/hashicorp/terraform/blob/v1.6/CHANGELOG.md) |
31 | 49 | * [v1.5](https://github.com/hashicorp/terraform/blob/v1.5/CHANGELOG.md) |
|
0 commit comments