DelineaXPM / terraform-provider-dsv

A Terraform Provider for Delinea DevOps Secrets Vault
https://delinea.com/products/devops-secrets-management-vault
MIT License
6 stars 3 forks source link

chore(deps): update ⬆️ golang module github.com/hashicorp/terraform to v0.12.17 #14

Closed mend-for-github-com[bot] closed 2 years ago

mend-for-github-com[bot] commented 2 years ago

This PR contains the following updates:

Package Type Update Change
github.com/hashicorp/terraform require patch v0.12.14 -> v0.12.17

By merging this PR, the below vulnerabilities will be automatically resolved:

Severity CVSS Score CVE
High High 7.5 CVE-2019-19316

Release Notes

hashicorp/terraform ### [`v0.12.17`](https://togithub.com/hashicorp/terraform/releases/tag/v0.12.17) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v0.12.16...v0.12.17) 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](https://togithub.com/hashicorp/terraform/security/advisories/GHSA-4rvg-555h-r626). 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](https://togithub.com/hashicorp/terraform/issues/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](https://togithub.com/hashicorp/terraform/issues/23443)) ### [`v0.12.16`](https://togithub.com/hashicorp/terraform/releases/tag/v0.12.16) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v0.12.15...v0.12.16) #### 0.12.16 (November 18, 2019) BUG FIXES: - command/0.12upgrade: fix panic when int value is out of range ([#​23394](https://togithub.com/hashicorp/terraform/issues/23394)) - core: fix cycle between dependencies with create_before_destroy ([#​23399](https://togithub.com/hashicorp/terraform/issues/23399)) - backend/remote: default .terraformignore paths will now work on Windows ([#​23311](https://togithub.com/hashicorp/terraform/issues/23311)) ### [`v0.12.15`](https://togithub.com/hashicorp/terraform/releases/tag/v0.12.15) [Compare Source](https://togithub.com/hashicorp/terraform/compare/v0.12.14...v0.12.15) BUG FIXES: - various commands: Fixed errant error "Initialization required. Please see the error message above." ([#​23383](https://togithub.com/hashicorp/terraform/issues/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.