Bump github.com/hashicorp/terraform from 0.12.5 to 0.12.17 in /src

[dependabot]

Bumps github.com/hashicorp/terraform from 0.12.5 to 0.12.17.

Changelog

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

0.12.17 (December 02, 2019)

SECURITY NOTES:

• If you are using the Azure remote state backend and you are using a SAS Token for authentication, please refer to the Azure remote state backend security advisory.

  Prior versions of the backend may have transmitted your state to the storage service using cleartext HTTP unless you specifically requested HTTPS when generating your SAS Token. This does not affect any other backends, and does not affect the Azure backend when using other authentication mechanisms.

NEW FEATURES:

• lang/funcs: Add trim* functions

ENHANCEMENTS:

• cli: Terraform will now consolidate many warnings with the same summary text into fewer warning items, in order to avoid excessive amounts of warnings making it hard to read other output from Terraform commands. (#23425)
• core: The upgrade logic for moving from the Terraform 0.11 to the Terraform 0.12 state snapshot format (internally, format version 3 to version 4) will now tolerate and ignore dependencies with invalid addresses, which tend to be left behind when following the terraform 0.11checklist directive to rename resources whose names start with digits prior to upgrading to Terraform 0.12. This should allow upgrading the state for a configuration that in the past had digit-prefixed resource names, once those names have been fixed in the configuration and state using the instructions given by terraform 0.11checklist in Terraform 0.11.14. (#23443)

BUG FIXES:

• command/jsonplan, command/jsonstate: fix panic with null values (#23492)
• backend/azure: Use HTTPS to talk to the storage API, even if using a SAS token that does not require it. (#23496)

0.12.16 (November 18, 2019)

BUG FIXES:

• command/0.12upgrade: fix panic when int value is out of range (#23394)
• core: fix cycle between dependencies with create_before_destroy (#23399)
• backend/remote: default .terraformignore paths will now work on Windows (#23311)

0.12.15 (November 14, 2019)

BUG FIXES:

• various commands: Fixed errant error "Initialization required. Please see the error message above." (#23383)

  The error was produced on some of Terraform's subcommands (in particular terraform show and terraform output, but possibly others) if a warning was emitted during configuration loading and if a backend block was present. This issue has been present since v0.12.0 for any configuration that produces configuration-related deprecation warnings, but it became more visible in v0.12.14 due to the addition of several more situations that could produce warnings.

0.12.14 (November 13, 2019)

UPGRADE NOTES:

• Terraform v0.12.0 included several changes to the Terraform language involving making expressions, type constraints, keywords, and references first-class in the language syntax, removing the need for placing thee items either in quoted strings or in interpolation syntax. Terraform v0.11 required these items to be quoted because the underlying language could not represent them any other way, while Terraform v0.12 expects them to be unquoted in order to improve readability.

  We have been accepting both forms for backward-compatibility with existing configurations and examples since the inititial v0.12.0 release. Having maintained compatibility for both forms for several versions we are now beginning the deprecation cycle for the old usage by having Terraform emit deprecation warnings.

  Terraform will still accept the older forms in spite of these warnings, so no immediate action is required. If your modules are targeting Terraform v0.12.0 and later exclusively, you can silence the warnings by removing the quotes, as directed in the warning message. In a future major version of Terraform, some of these warnings will be elevated to be errors.

  The summary of the warning for these situations will be one of the following:

  • Interpolation-only expressions are deprecated: an expression like "${foo}" should be rewritten as just foo.

... (truncated)

Commits

• f0ae01e v0.12.17
• 180e233 Update CHANGELOG.md
• 6db3cf8 vendor: upgrade Azure SDK and Azure/go-autorest
• e32641c website/docs: Corrects function name in cidrsubnets function documentation ...
• 4409cc0 Update CHANGELOG.md
• 99225b8 command/jsonstate,plan: fix panic with null values (#23492)
• 211cf08 Update config.yml
• 3db7ea2 Merge pull request #23225 from hashicorp/add-issue-template-cfg
• 438279c github: Add issue templates config
• 88a806c Merge pull request #23450 from hashicorp/jbarin/err-diags
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.