Bump github.com/hashicorp/terraform from 0.14.4 to 0.15.3

[dependabot]

Bumps github.com/hashicorp/terraform from 0.14.4 to 0.15.3.

Release notes

Sourced from github.com/hashicorp/terraform's releases.

v0.15.3

0.15.3 (May 06, 2021)

ENHANCEMENTS:

• terraform show: Add data to the JSON plan output describing which changes caused a resource to be replaced (#28608)

BUG FIXES:

• terraform show: Fix crash for JSON plan output of new resources with sensitive attributes in nested blocks (#28624)

v0.15.2

0.15.2 (May 05, 2021)

ENHANCEMENTS:

• terraform plan and terraform apply: Both now support a new planning option -replace=... which takes the address of a resource instance already tracked in the state and forces Terraform to upgrade either an update or no-op plan for that instance into a "replace" (either destroy-then-create or create-then-destroy depending on configuration), to allow replacing a degraded object with a new object of the same configuration in a single action and preview the effect of that before applying it.
• terraform apply: Now has a -destroy option for symmetry with terraform plan -destroy, which makes terraform destroy effectively an alias for terraform apply -destroy. This change is only for consistency between terraform plan and terraform apply; there are no current plans to deprecate terraform destroy. (#28489)
• core: Update HCL to allow better planning of dynamic blocks (#28424)
• core: Unmark values when planning data sources (#28539)

BUG FIXES:

• command/format: Fix various issues with nested-type attribute formatting (#28600)
• core: Fix JSON plan output to add sensitivity data for provider-specified sensitive attribute values (#28523)
• cli: Fix missing "forces replacement" UI for attribute changes which are marked as sensitive by the provider (#28583)
• cli: Fix crash when rendering diagnostic caused by missing trailing quote (#28598)
• functions: Fix crash when calling setproduct with one or more empty collections (#28607)

v0.15.1

0.15.1 (April 26, 2021)

ENHANCEMENTS:

• config: Various Terraform language functions now have more precise inference rules for propagating the "sensitive" characteristic values.

  The affected functions are chunklist, concat, flatten, keys, length, lookup, merge, setproduct, tolist, tomap, values, and zipmap. The details are a little different for each of these but the general idea is to, as far as possible, preserve the sensitive characteristic on individual element or attribute values in result structures rather than always conservatively applying sensitivity to the whole result.

  The primary benefit of these improvements is that you can now use these functions as part of constructing maps for for_each in situations where the input collection is never sensitive but some of the elements/attributes inside might be. (#28446] [#28460)

• cli: Update the HashiCorp public key (#28505)

• cli: Diagnostic messages can now be annotated with resource and provider addresses. (#28275)

• cli: terraform login now has a new user experience for successful log-ins to Terraform Cloud and Terraform Enterprise. (#28487)

• core: Minor graph performance optimizations. (#28329)

BUG FIXES:

• config: Fix validation error when passing providers from a non-default namespace into modules. (#28414)
• cli: Fix missing colors and extraneous resource summary for plan/apply with the remote backend. (#28409)
• cli: Diagnostics messages will only indicate that a referenced value is sensitive if that value is directly sensitive, as opposed to being a complex-typed value that contains a sensitive value. (#28442)

... (truncated)

Changelog

Sourced from github.com/hashicorp/terraform's changelog.

0.15.3 (May 06, 2021)

ENHANCEMENTS:

• terraform show: Add data to the JSON plan output describing which changes caused a resource to be replaced (#28608)

BUG FIXES:

• terraform show: Fix crash for JSON plan output of new resources with sensitive attributes in nested blocks (#28624)

0.15.2 (May 05, 2021)

ENHANCEMENTS:

• terraform plan and terraform apply: Both now support a new planning option -replace=... which takes the address of a resource instance already tracked in the state and forces Terraform to upgrade either an update or no-op plan for that instance into a "replace" (either destroy-then-create or create-then-destroy depending on configuration), to allow replacing a degraded object with a new object of the same configuration in a single action and preview the effect of that before applying it.
• terraform apply: Now has a -destroy option for symmetry with terraform plan -destroy, which makes terraform destroy effectively an alias for terraform apply -destroy. This change is only for consistency between terraform plan and terraform apply; there are no current plans to deprecate terraform destroy. (#28489)
• core: Update HCL to allow better planning of dynamic blocks (#28424)
• core: Unmark values when planning data sources (#28539)

BUG FIXES:

• command/format: Fix various issues with nested-type attribute formatting (#28600)
• core: Fix JSON plan output to add sensitivity data for provider-specified sensitive attribute values (#28523)
• cli: Fix missing "forces replacement" UI for attribute changes which are marked as sensitive by the provider (#28583)
• cli: Fix crash when rendering diagnostic caused by missing trailing quote (#28598)
• functions: Fix crash when calling setproduct with one or more empty collections (#28607)

0.15.1 (April 26, 2021)

ENHANCEMENTS:

• config: Various Terraform language functions now have more precise inference rules for propagating the "sensitive" characteristic values.

  The affected functions are chunklist, concat, flatten, keys, length, lookup, merge, setproduct, tolist, tomap, values, and zipmap. The details are a little different for each of these but the general idea is to, as far as possible, preserve the sensitive characteristic on individual element or attribute values in result structures rather than always conservatively applying sensitivity to the whole result.

  The primary benefit of these improvements is that you can now use these functions as part of constructing maps for for_each in situations where the input collection is never sensitive but some of the elements/attributes inside might be. (#28446] [#28460)

• cli: Update the HashiCorp public key (#28505)

• cli: Diagnostic messages can now be annotated with resource and provider addresses. (#28275)

• cli: terraform login now has a new user experience for successful log-ins to Terraform Cloud and Terraform Enterprise. (#28487)

• core: Minor graph performance optimizations. (#28329)

BUG FIXES:

• config: Fix validation error when passing providers from a non-default namespace into modules. (#28414)
• cli: Fix missing colors and extraneous resource summary for plan/apply with the remote backend. (#28409)
• cli: Diagnostics messages will only indicate that a referenced value is sensitive if that value is directly sensitive, as opposed to being a complex-typed value that contains a sensitive value. (#28442)
• core: Don't trigger data source reads from changes in sibling module instances. (#28267)
• core: Restore saved dependencies when a resource destroy operation fails. (#28317)
• core: Fix crash when setting sensitive attributes to a sensitive value. (#28383)
• core: Loosen output value sensitivity requirement for non-root modules. This means that modules which may receive sensitive values as input variables no longer need to mark all related outputs as sensitive. The requirement for root modules to specify the sensitive attribute for sensitive values remains, with an extended diagnostic message to explain why. (#28472)

... (truncated)

Commits

• 69f9f12 Release v0.15.3
• 7d580fc Update CHANGELOG.md
• 3c31aad Merge pull request #28625 from hashicorp/backport/jbardin/schema-value-marks/...
• ab3b94b backport of commit d76a8fcf6cc2d280ca41686780e5144451e35327
• 56b8352 Update CHANGELOG.md
• 0c379e2 Merge pull request #28622 from hashicorp/backport/alisdair/json-plan-replace-...
• 8e3bab7 core: Track both previous run state and refresh state during planning
• dc454e7 plans: Track both the previous run and prior states in the plan
• 49fecbd Cleanup after v0.15.2 release
• 33b654c Release v0.15.2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)