hashicorp/terraform
### [`v0.15.5`](https://togithub.com/hashicorp/terraform/releases/v0.15.5)
[Compare Source](https://togithub.com/hashicorp/terraform/compare/v0.15.4...v0.15.5)
#### 0.15.5 (June 02, 2021)
BUG FIXES:
- `terraform plan` and `terraform apply`: Don't show "Objects have changed" notification when the detected changes are only internal details related to legacy SDK quirks. ([#28796](https://togithub.com/hashicorp/terraform/issues/28796))
- core: Prevent crash during planning when encountering a deposed instance that has been removed from the configuration. ([#28766](https://togithub.com/hashicorp/terraform/issues/28766))
- core: Fix crash when rendering changes to deposed instances outside of Terraform. ([#28796](https://togithub.com/hashicorp/terraform/issues/28796))
- core: Restore a missing error when attempting to import a non-existent remote object. ([#28808](https://togithub.com/hashicorp/terraform/issues/28808))
- core: Fix bug where Terraform failed to release the state lock when applying a stale saved plan failed. ([#28819](https://togithub.com/hashicorp/terraform/issues/28819))
### [`v0.15.4`](https://togithub.com/hashicorp/terraform/releases/v0.15.4)
[Compare Source](https://togithub.com/hashicorp/terraform/compare/v0.15.3...v0.15.4)
#### 0.15.4 (May 19, 2021)
NEW FEATURES:
- **Noting changes made outside of Terraform:** Terraform has always, by default, made a point during the planning operation of reading the current state of remote objects in order to detect any changes made outside of Terraform, to make sure the plan will take those into account.
Terraform will now report those detected changes as part of the plan result, in order to give additional context about the planned changes. We've often heard that people find it confusing when a plan includes a change that doesn't seem to be prompted by any recent change in the *configuration*, and so this feature is aiming to provide the previously-missing explanation for situations where Terraform is planning to undo a change.
It can also be useful just as general information when the change *won't* be undone by Terraform: if you've intentionally made a change outside of Terraform and mirrored that change in your configuration then Terraform will now confirm that it noticed the change you made and took it into account when planning.
By default this new output is for information only and doesn't change any behavior. If Terraform detects a change you were *expecting* then you don't need to take any additional action to respond to it. However, we've also added a new planning mode `-refresh-only` which allows you to explicitly plan and apply the action of writing those detected changes to the Terraform state, which serves as a plannable replacement for `terraform refresh`. We don't have any plans to remove the long-standing `terraform refresh` command, but we do recommend using `terraform apply -refresh-only` instead in most cases, because it will provide an opportunity to review what Terraform detected before updating the Terraform state.
UPGRADE NOTES:
- This release adds some new reserved reference prefixes to make them available for later work. These are `resource.`, `template.`, `arg.`, and `lazy.`. We don't expect these additions to cause problems for most existing configurations, but could cause a conflict if you are using a custom provider which has a resource type named exactly "resource", "template", "arg", or "lazy". In that unlikely event, you can escape references to resources of those types by adding a `resource.` prefix; for example, if you have a `resource "template" "foo"` then you can change references to it from `template.foo` to `resource.template.foo` in order to escape the new meaning.
ENHANCEMENTS:
- config: The various functions that compute hashs of files on disk, like `filesha256`, will now stream the contents of the given file into the hash function in smaller chunks. Previously they would always read the entire file into memory before hashing it, due to following a similar implementation strategy as the `file` function. ([#28681](https://togithub.com/hashicorp/terraform/issues/28681))
- config: Some new escaping syntax which is not yet useful but will be part of the backward-compatibility story for certain future language editions. ([#28709](https://togithub.com/hashicorp/terraform/issues/28709))
- core: Rsource diagnostics are no longer lost on remote state storage fails ([#28724](https://togithub.com/hashicorp/terraform/issues/28724))
- core: Diagnostics from provisioner failures are now shown in CLI output ([#28753](https://togithub.com/hashicorp/terraform/issues/28753))
- `terraform init`: add a new `-migrate-state` flag instead of automatic state migration, to prevent failing when old backend config is not usable ([#28718](https://togithub.com/hashicorp/terraform/issues/28718))
- `terraform plan` and `terraform apply`: will now report any changes Terraform detects during the "refresh" phase for each managed object, providing confirmation that Terraform has seen those changes and, where appropriate, extra context to help understand the planned change actions that follow. ([#28634](https://togithub.com/hashicorp/terraform/issues/28634))
- `terraform plan` and `terraform apply`: now have a new option `-refresh-only` to activate the "refresh only" planning mode, which causes Terraform to ignore any changes suggested by the configuration but still detect any changes made outside of Terraform since the latest `terraform apply`. ([#28634](https://togithub.com/hashicorp/terraform/issues/28634))
- backend/gcs: Terraform Core now supports [Workload Identity Federation](https://cloud.google.com/iam/docs/workload-identity-federation). The federated JSON credentials must be loaded through the `GOOGLE_APPLICATION_CREDENTIALS` environment variable. This is also available in the Google Provider in versions newer than v3.61. ([#28296](https://togithub.com/hashicorp/terraform/issues/28296))
- backend/remote: supports several new CLI options when running plans and applies with Terraform Cloud: `-refresh=false`, `-replace`, and `-refresh-only`. ([#28746](https://togithub.com/hashicorp/terraform/issues/28746))
BUG FIXES:
- core: Fix sensitivity handling with plan values, which could cause the sensitive marks to be lost during apply leading to a perpetual diff ([#28687](https://togithub.com/hashicorp/terraform/issues/28687))
- core: Fix crash when specifying SSH `bastion_port` in a resource `connection` block ([#28665](https://togithub.com/hashicorp/terraform/issues/28665))
- core: Terraform will now upgrade and refresh (unless disabled) deposed objects during planning, in a similar manner as for objects that have been removed from the configuration. "Deposed" is how Terraform represents the situation where a `create_before_destroy` replacement failed to destroy the old object, in which case Terraform needs to track both the new and old objects until the old object is successfully deleted. Refreshing these during planning means that you can, if you wish, delete a "deposed" object manually outside of Terraform and then have Terraform detect that you've done so. ([#28634](https://togithub.com/hashicorp/terraform/issues/28634))
- config: Improve the sensitivity support for `lookup` and `length` functions, which were accidentally omitted from the larger update in 0.15.1 ([#28509](https://togithub.com/hashicorp/terraform/issues/28509))
- backend/gcs: Fixed a bug where service account impersonation didn't work if the original identity was another service account ([#28139](https://togithub.com/hashicorp/terraform/issues/28139))
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box.
This PR contains the following updates:
0.15.3->0.15.5Release Notes
hashicorp/terraform
### [`v0.15.5`](https://togithub.com/hashicorp/terraform/releases/v0.15.5) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v0.15.4...v0.15.5) #### 0.15.5 (June 02, 2021) BUG FIXES: - `terraform plan` and `terraform apply`: Don't show "Objects have changed" notification when the detected changes are only internal details related to legacy SDK quirks. ([#28796](https://togithub.com/hashicorp/terraform/issues/28796)) - core: Prevent crash during planning when encountering a deposed instance that has been removed from the configuration. ([#28766](https://togithub.com/hashicorp/terraform/issues/28766)) - core: Fix crash when rendering changes to deposed instances outside of Terraform. ([#28796](https://togithub.com/hashicorp/terraform/issues/28796)) - core: Restore a missing error when attempting to import a non-existent remote object. ([#28808](https://togithub.com/hashicorp/terraform/issues/28808)) - core: Fix bug where Terraform failed to release the state lock when applying a stale saved plan failed. ([#28819](https://togithub.com/hashicorp/terraform/issues/28819)) ### [`v0.15.4`](https://togithub.com/hashicorp/terraform/releases/v0.15.4) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v0.15.3...v0.15.4) #### 0.15.4 (May 19, 2021) NEW FEATURES: - **Noting changes made outside of Terraform:** Terraform has always, by default, made a point during the planning operation of reading the current state of remote objects in order to detect any changes made outside of Terraform, to make sure the plan will take those into account. Terraform will now report those detected changes as part of the plan result, in order to give additional context about the planned changes. We've often heard that people find it confusing when a plan includes a change that doesn't seem to be prompted by any recent change in the *configuration*, and so this feature is aiming to provide the previously-missing explanation for situations where Terraform is planning to undo a change. It can also be useful just as general information when the change *won't* be undone by Terraform: if you've intentionally made a change outside of Terraform and mirrored that change in your configuration then Terraform will now confirm that it noticed the change you made and took it into account when planning. By default this new output is for information only and doesn't change any behavior. If Terraform detects a change you were *expecting* then you don't need to take any additional action to respond to it. However, we've also added a new planning mode `-refresh-only` which allows you to explicitly plan and apply the action of writing those detected changes to the Terraform state, which serves as a plannable replacement for `terraform refresh`. We don't have any plans to remove the long-standing `terraform refresh` command, but we do recommend using `terraform apply -refresh-only` instead in most cases, because it will provide an opportunity to review what Terraform detected before updating the Terraform state. UPGRADE NOTES: - This release adds some new reserved reference prefixes to make them available for later work. These are `resource.`, `template.`, `arg.`, and `lazy.`. We don't expect these additions to cause problems for most existing configurations, but could cause a conflict if you are using a custom provider which has a resource type named exactly "resource", "template", "arg", or "lazy". In that unlikely event, you can escape references to resources of those types by adding a `resource.` prefix; for example, if you have a `resource "template" "foo"` then you can change references to it from `template.foo` to `resource.template.foo` in order to escape the new meaning. ENHANCEMENTS: - config: The various functions that compute hashs of files on disk, like `filesha256`, will now stream the contents of the given file into the hash function in smaller chunks. Previously they would always read the entire file into memory before hashing it, due to following a similar implementation strategy as the `file` function. ([#28681](https://togithub.com/hashicorp/terraform/issues/28681)) - config: Some new escaping syntax which is not yet useful but will be part of the backward-compatibility story for certain future language editions. ([#28709](https://togithub.com/hashicorp/terraform/issues/28709)) - core: Rsource diagnostics are no longer lost on remote state storage fails ([#28724](https://togithub.com/hashicorp/terraform/issues/28724)) - core: Diagnostics from provisioner failures are now shown in CLI output ([#28753](https://togithub.com/hashicorp/terraform/issues/28753)) - `terraform init`: add a new `-migrate-state` flag instead of automatic state migration, to prevent failing when old backend config is not usable ([#28718](https://togithub.com/hashicorp/terraform/issues/28718)) - `terraform plan` and `terraform apply`: will now report any changes Terraform detects during the "refresh" phase for each managed object, providing confirmation that Terraform has seen those changes and, where appropriate, extra context to help understand the planned change actions that follow. ([#28634](https://togithub.com/hashicorp/terraform/issues/28634)) - `terraform plan` and `terraform apply`: now have a new option `-refresh-only` to activate the "refresh only" planning mode, which causes Terraform to ignore any changes suggested by the configuration but still detect any changes made outside of Terraform since the latest `terraform apply`. ([#28634](https://togithub.com/hashicorp/terraform/issues/28634)) - backend/gcs: Terraform Core now supports [Workload Identity Federation](https://cloud.google.com/iam/docs/workload-identity-federation). The federated JSON credentials must be loaded through the `GOOGLE_APPLICATION_CREDENTIALS` environment variable. This is also available in the Google Provider in versions newer than v3.61. ([#28296](https://togithub.com/hashicorp/terraform/issues/28296)) - backend/remote: supports several new CLI options when running plans and applies with Terraform Cloud: `-refresh=false`, `-replace`, and `-refresh-only`. ([#28746](https://togithub.com/hashicorp/terraform/issues/28746)) BUG FIXES: - core: Fix sensitivity handling with plan values, which could cause the sensitive marks to be lost during apply leading to a perpetual diff ([#28687](https://togithub.com/hashicorp/terraform/issues/28687)) - core: Fix crash when specifying SSH `bastion_port` in a resource `connection` block ([#28665](https://togithub.com/hashicorp/terraform/issues/28665)) - core: Terraform will now upgrade and refresh (unless disabled) deposed objects during planning, in a similar manner as for objects that have been removed from the configuration. "Deposed" is how Terraform represents the situation where a `create_before_destroy` replacement failed to destroy the old object, in which case Terraform needs to track both the new and old objects until the old object is successfully deleted. Refreshing these during planning means that you can, if you wish, delete a "deposed" object manually outside of Terraform and then have Terraform detect that you've done so. ([#28634](https://togithub.com/hashicorp/terraform/issues/28634)) - config: Improve the sensitivity support for `lookup` and `length` functions, which were accidentally omitted from the larger update in 0.15.1 ([#28509](https://togithub.com/hashicorp/terraform/issues/28509)) - backend/gcs: Fixed a bug where service account impersonation didn't work if the original identity was another service account ([#28139](https://togithub.com/hashicorp/terraform/issues/28139))Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.