Update module github.com/hashicorp/terraform to v0.15.5 #1208
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.15.3
->v0.15.5
Release Notes
hashicorp/terraform (github.com/hashicorp/terraform)
v0.15.5
Compare Source
0.15.5 (June 02, 2021)
BUG FIXES:
terraform plan
andterraform apply
: Don't show "Objects have changed" notification when the detected changes are only internal details related to legacy SDK quirks. (#28796)v0.15.4
Compare Source
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 forterraform refresh
. We don't have any plans to remove the long-standingterraform refresh
command, but we do recommend usingterraform 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:
resource.
,template.
,arg.
, andlazy.
. 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 aresource.
prefix; for example, if you have aresource "template" "foo"
then you can change references to it fromtemplate.foo
toresource.template.foo
in order to escape the new meaning.ENHANCEMENTS:
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 thefile
function. (#28681)terraform init
: add a new-migrate-state
flag instead of automatic state migration, to prevent failing when old backend config is not usable (#28718)terraform plan
andterraform 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)terraform plan
andterraform 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 latestterraform apply
. (#28634)GOOGLE_APPLICATION_CREDENTIALS
environment variable. This is also available in the Google Provider in versions newer than v3.61. (#28296)-refresh=false
,-replace
, and-refresh-only
. (#28746)BUG FIXES:
bastion_port
in a resourceconnection
block (#28665)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)lookup
andlength
functions, which were accidentally omitted from the larger update in 0.15.1 (#28509)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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 was generated by Mend Renovate. View the repository job log.