ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
terraform/vendor/modules.txt

783 lines
28 KiB
Plaintext
Raw Normal View History

vendor: Bump go-getter to 1.4.0
2019-09-09 14:04:58 +02:00
# cloud.google.com/go v0.45.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
update cty
2020-02-21 20:24:44 +01:00
cloud.google.com/go/compute/metadata
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
cloud.google.com/go/iam
cloud.google.com/go/internal
cloud.google.com/go/internal/optional
vendor: google.golang.org/grpc@v1.18.0 go get google.golang.org/grpc@v1.18.0 go mod tidy go mod vendor
2019-02-20 19:51:33 +01:00
cloud.google.com/go/internal/trace
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
cloud.google.com/go/internal/version
update cty
2020-02-21 20:24:44 +01:00
cloud.google.com/go/storage
vendor: upgrade Azure SDK and Azure/go-autorest This involves some minor changes to the "azure" backend code to account for upstream breaking changes.
2019-11-26 01:03:57 +01:00
# github.com/Azure/azure-sdk-for-go v36.2.0+incompatible
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
backend/azurerm: upgrading the SDK / support for proxies (#19414) * vendor updates - updating to v21.3.0 of github.com/Azure/azure-sdk-for-go - updating to v10.15.4 of github.com/Azure/go-autorest - vendoring github.com/hashicorp/go-azure-helpers @ 0.1.1 * backend/azurerm: refactoring to use the new auth package - refactoring the backend to use a shared client via the new auth package - adding tests covering both Service Principal and Access Key auth - support for authenticating using a proxy - rewriting the backend documentation to include examples of both authentication types * switching to use the build-in logging function * documenting it's also possible to retrieve the access key from an env var
2018-11-21 22:06:03 +01:00
github.com/Azure/azure-sdk-for-go/profiles/2017-03-09/resources/mgmt/resources
github.com/Azure/azure-sdk-for-go/profiles/2017-03-09/storage/mgmt/storage
update cty
2020-02-21 20:24:44 +01:00
github.com/Azure/azure-sdk-for-go/services/graphrbac/1.6/graphrbac
backend/azurerm: upgrading the SDK / support for proxies (#19414) * vendor updates - updating to v21.3.0 of github.com/Azure/azure-sdk-for-go - updating to v10.15.4 of github.com/Azure/go-autorest - vendoring github.com/hashicorp/go-azure-helpers @ 0.1.1 * backend/azurerm: refactoring to use the new auth package - refactoring the backend to use a shared client via the new auth package - adding tests covering both Service Principal and Access Key auth - support for authenticating using a proxy - rewriting the backend documentation to include examples of both authentication types * switching to use the build-in logging function * documenting it's also possible to retrieve the access key from an env var
2018-11-21 22:06:03 +01:00
github.com/Azure/azure-sdk-for-go/services/resources/mgmt/2016-02-01/resources
github.com/Azure/azure-sdk-for-go/services/storage/mgmt/2016-01-01/storage
update cty
2020-02-21 20:24:44 +01:00
github.com/Azure/azure-sdk-for-go/storage
backend/azurerm: upgrading the SDK / support for proxies (#19414) * vendor updates - updating to v21.3.0 of github.com/Azure/azure-sdk-for-go - updating to v10.15.4 of github.com/Azure/go-autorest - vendoring github.com/hashicorp/go-azure-helpers @ 0.1.1 * backend/azurerm: refactoring to use the new auth package - refactoring the backend to use a shared client via the new auth package - adding tests covering both Service Principal and Access Key auth - support for authenticating using a proxy - rewriting the backend documentation to include examples of both authentication types * switching to use the build-in logging function * documenting it's also possible to retrieve the access key from an env var
2018-11-21 22:06:03 +01:00
github.com/Azure/azure-sdk-for-go/version
vendor: upgrade Azure SDK and Azure/go-autorest This involves some minor changes to the "azure" backend code to account for upstream breaking changes.
2019-11-26 01:03:57 +01:00
# github.com/Azure/go-autorest/autorest v0.9.2
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/Azure/go-autorest/autorest
vendor: Downgrade Azure dependencies This is to allow Terraform providers to upgrade to at least one more minor version of the plugin SDK without major UX hiccups. This concludes (unsuccessful) experiments involving upgrades to SDK with https://github.com/Azure/go-autorest/pull/455 Even with that patch all providers still experience broken UX as described in https://github.com/hashicorp/terraform/pull/22490 This downgrade reduces the uncomfort to only a handful of providers from >100s. The affected providers more or less directly depend on Azure SDK(s), which is ~8. Affected providers practically cannot consume Terraform Plugin SDK with this patch (downgraded Azure SDKs) and can just wait for extracted Terraform Plugin SDK which is planned to be released soon. This reverts the following PRs: - https://github.com/hashicorp/terraform/pull/22247 - https://github.com/hashicorp/terraform/pull/22248 - https://github.com/hashicorp/terraform/pull/22524 - https://github.com/hashicorp/terraform/pull/22525 and it is otherwise result of the following commands ``` go get github.com/Azure/azure-sdk-for-go@v21.3.0 go get github.com/hashicorp/go-azure-helpers@166dfd221bb2 go mod tidy ```
2019-08-20 16:50:20 +02:00
github.com/Azure/go-autorest/autorest/azure
vendor: upgrade Azure SDK and Azure/go-autorest This involves some minor changes to the "azure" backend code to account for upstream breaking changes.
2019-11-26 01:03:57 +01:00
# github.com/Azure/go-autorest/autorest/adal v0.8.1-0.20191028180845-3492b2aff503
github.com/Azure/go-autorest/autorest/adal
# github.com/Azure/go-autorest/autorest/azure/cli v0.2.0
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
github.com/Azure/go-autorest/autorest/azure/cli
vendor: upgrade Azure SDK and Azure/go-autorest This involves some minor changes to the "azure" backend code to account for upstream breaking changes.
2019-11-26 01:03:57 +01:00
# github.com/Azure/go-autorest/autorest/date v0.2.0
github.com/Azure/go-autorest/autorest/date
# github.com/Azure/go-autorest/autorest/to v0.3.0
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/Azure/go-autorest/autorest/to
vendor: upgrade Azure SDK and Azure/go-autorest This involves some minor changes to the "azure" backend code to account for upstream breaking changes.
2019-11-26 01:03:57 +01:00
# github.com/Azure/go-autorest/autorest/validation v0.2.0
backend/azurerm: upgrading the SDK / support for proxies (#19414) * vendor updates - updating to v21.3.0 of github.com/Azure/azure-sdk-for-go - updating to v10.15.4 of github.com/Azure/go-autorest - vendoring github.com/hashicorp/go-azure-helpers @ 0.1.1 * backend/azurerm: refactoring to use the new auth package - refactoring the backend to use a shared client via the new auth package - adding tests covering both Service Principal and Access Key auth - support for authenticating using a proxy - rewriting the backend documentation to include examples of both authentication types * switching to use the build-in logging function * documenting it's also possible to retrieve the access key from an env var
2018-11-21 22:06:03 +01:00
github.com/Azure/go-autorest/autorest/validation
vendor: upgrade Azure SDK and Azure/go-autorest This involves some minor changes to the "azure" backend code to account for upstream breaking changes.
2019-11-26 01:03:57 +01:00
# github.com/Azure/go-autorest/logger v0.1.0
github.com/Azure/go-autorest/logger
# github.com/Azure/go-autorest/tracing v0.5.0
github.com/Azure/go-autorest/tracing
vendor: github.com/masterzen/winrm@5e5c9a7fe54b
2019-02-25 09:45:01 +01:00
# github.com/Azure/go-ntlmssp v0.0.0-20180810175552-4a21cbd618b4
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/Azure/go-ntlmssp
vendor: github.com/masterzen/winrm@5e5c9a7fe54b
2019-02-25 09:45:01 +01:00
# github.com/ChrisTrenkamp/goxpath v0.0.0-20170922090931-c385f95c6022
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/ChrisTrenkamp/goxpath
github.com/ChrisTrenkamp/goxpath/internal/execxp
vendor: github.com/masterzen/winrm@5e5c9a7fe54b
2019-02-25 09:45:01 +01:00
github.com/ChrisTrenkamp/goxpath/internal/execxp/findutil
github.com/ChrisTrenkamp/goxpath/internal/execxp/intfns
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/ChrisTrenkamp/goxpath/internal/xsort
vendor: github.com/masterzen/winrm@5e5c9a7fe54b
2019-02-25 09:45:01 +01:00
github.com/ChrisTrenkamp/goxpath/lexer
update cty
2020-02-21 20:24:44 +01:00
github.com/ChrisTrenkamp/goxpath/parser
vendor: github.com/masterzen/winrm@5e5c9a7fe54b
2019-02-25 09:45:01 +01:00
github.com/ChrisTrenkamp/goxpath/parser/pathexpr
update cty
2020-02-21 20:24:44 +01:00
github.com/ChrisTrenkamp/goxpath/tree
github.com/ChrisTrenkamp/goxpath/tree/xmltree
github.com/ChrisTrenkamp/goxpath/tree/xmltree/xmlbuilder
github.com/ChrisTrenkamp/goxpath/tree/xmltree/xmlele
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
github.com/ChrisTrenkamp/goxpath/tree/xmltree/xmlnode
update cty
2020-02-21 20:24:44 +01:00
github.com/ChrisTrenkamp/goxpath/xconst
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/abdullin/seq v0.0.0-20160510034733-d5467c17e7af
## explicit
vendor: github.com/agext/levenshtein@v1.2.2
2019-02-22 23:15:02 +01:00
# github.com/agext/levenshtein v1.2.2
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/agext/levenshtein
# github.com/agl/ed25519 v0.0.0-20150830182803-278e1ec8e8a6
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/agl/ed25519
github.com/agl/ed25519/edwards25519
Add tablestore config to store state lock
2019-04-11 01:11:10 +02:00
# github.com/aliyun/alibaba-cloud-sdk-go v0.0.0-20190329064014-6e358769c32a
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
Add Alibaba Cloud backend OSS with lock
2019-03-07 11:31:36 +01:00
github.com/aliyun/alibaba-cloud-sdk-go/sdk
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
github.com/aliyun/alibaba-cloud-sdk-go/sdk/auth
update cty
2020-02-21 20:24:44 +01:00
github.com/aliyun/alibaba-cloud-sdk-go/sdk/auth/credentials
Add tablestore config to store state lock
2019-04-11 01:11:10 +02:00
github.com/aliyun/alibaba-cloud-sdk-go/sdk/auth/credentials/provider
update cty
2020-02-21 20:24:44 +01:00
github.com/aliyun/alibaba-cloud-sdk-go/sdk/auth/signers
Add Alibaba Cloud backend OSS with lock
2019-03-07 11:31:36 +01:00
github.com/aliyun/alibaba-cloud-sdk-go/sdk/endpoints
github.com/aliyun/alibaba-cloud-sdk-go/sdk/errors
update cty
2020-02-21 20:24:44 +01:00
github.com/aliyun/alibaba-cloud-sdk-go/sdk/requests
github.com/aliyun/alibaba-cloud-sdk-go/sdk/responses
Add tablestore config to store state lock
2019-04-11 01:11:10 +02:00
github.com/aliyun/alibaba-cloud-sdk-go/sdk/utils
update cty
2020-02-21 20:24:44 +01:00
github.com/aliyun/alibaba-cloud-sdk-go/services/location
github.com/aliyun/alibaba-cloud-sdk-go/services/sts
Add Alibaba Cloud backend OSS with lock
2019-03-07 11:31:36 +01:00
# github.com/aliyun/aliyun-oss-go-sdk v0.0.0-20190103054945-8205d1f41e70
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
Add Alibaba Cloud backend OSS with lock
2019-03-07 11:31:36 +01:00
github.com/aliyun/aliyun-oss-go-sdk/oss
Add tablestore config to store state lock
2019-04-11 01:11:10 +02:00
# github.com/aliyun/aliyun-tablestore-go-sdk v4.1.2+incompatible
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
Add tablestore config to store state lock
2019-04-11 01:11:10 +02:00
github.com/aliyun/aliyun-tablestore-go-sdk/tablestore
github.com/aliyun/aliyun-tablestore-go-sdk/tablestore/otsprotocol
github.com/aliyun/aliyun-tablestore-go-sdk/tablestore/search
vendor: github.com/dylanmei/winrmtest@99b7fe2fddf1
2019-02-26 19:22:15 +01:00
# github.com/antchfx/xpath v0.0.0-20190129040759-c8489ed3251e
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/antchfx/xpath
vendor: github.com/dylanmei/winrmtest@99b7fe2fddf1
2019-02-26 19:22:15 +01:00
# github.com/antchfx/xquery v0.0.0-20180515051857-ad5b8c7a47b0
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/antchfx/xquery/xml
go get github.com/apparentlymart/go-cidr@v1.0.1 This includes fixes in the handling of IPv6 prefixes that leave a host portion longer than the size of int on the target platform.
2019-09-09 23:04:56 +02:00
# github.com/apparentlymart/go-cidr v1.0.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/apparentlymart/go-cidr/cidr
vendor: github.com/apparentlymart/go-dump@042adf3cf4a0 go get github.com/apparentlymart/go-dump@042adf3cf4a0 go mod tidy go mod vendor
2019-02-21 09:45:27 +01:00
# github.com/apparentlymart/go-dump v0.0.0-20190214190832-042adf3cf4a0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/apparentlymart/go-dump/dump
vendor: go get github.com/zclconf/go-cty@v1.4.0 This fixes several bugs: - `substr("abc", 0, 0)` would previously return `"abc"`, despite the length argument being `0`. This has been changed to return an empty string when length is zero. - `ceil(1/0)` and `floor(1/0)` would previously return a large integer value, rather than infinity. This has been fixed.
2020-04-09 20:18:55 +02:00
# github.com/apparentlymart/go-textseg/v12 v12.0.0
github.com/apparentlymart/go-textseg/v12/textseg
vendor: go get github.com/apparentlymart/go-userdirs This library implements the user-specific directory layout specifications for various platforms (XDG on Unix, "Known Folders" on Windows, etc). We'll use this in a subsequent commit to add additional system-specific search directories for provider plugins, and perhaps later on also CLI configuration directories.
2020-04-03 02:55:25 +02:00
# github.com/apparentlymart/go-userdirs v0.0.0-20190512014041-4a23807e62b9
## explicit
github.com/apparentlymart/go-userdirs/internal/unix
github.com/apparentlymart/go-userdirs/macosbase
github.com/apparentlymart/go-userdirs/userdirs
github.com/apparentlymart/go-userdirs/windowsbase
github.com/apparentlymart/go-userdirs/xdgbase
go get github.com/apparentlymart/go-versions@master
2019-12-19 23:57:33 +01:00
# github.com/apparentlymart/go-versions v0.0.2-0.20180815153302-64b99f7cb171
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
go get github.com/apparentlymart/go-versions@master
2019-12-19 23:57:33 +01:00
github.com/apparentlymart/go-versions/versions
github.com/apparentlymart/go-versions/versions/constraints
vendor: github.com/armon/circbuf@5111143e8da2 go get github.com/armon/circbuf@5111143e8da2 go mod tidy go mod vendor
2019-02-21 09:48:13 +01:00
# github.com/armon/circbuf v0.0.0-20190214190532-5111143e8da2
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/armon/circbuf
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/armon/go-metrics v0.0.0-20180917152333-f0300d1749da
## explicit
vendor: github.com/terraform-providers/terraform-provider-aws@v1.58.0
2019-02-12 13:23:47 +01:00
# github.com/armon/go-radix v1.0.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/armon/go-radix
deps: github.com/aws/aws-sdk-go@v1.30.12 [master] (#24745) * update github.com/aws/aws-sdk-go to v1.30.9 * deps: github.com/aws/aws-sdk-go@v1.30.12 Reference: https://github.com/hashicorp/terraform/issues/24710 Reference: https://github.com/hashicorp/terraform/issues/24741 Changes: ``` NOTES: * backend/s3: Region validation now automatically supports the new `af-south-1` (Africa (Cape Town)) region. For AWS operations to work in the new region, the region must be explicitly enabled as outlined in the [AWS Documentation](https://docs.aws.amazon.com/general/latest/gr/rande-manage.html#rande-manage-enable). When the region is not enabled, the Terraform S3 Backend will return errors during credential validation (e.g. `error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid`). ENHANCEMENTS: * backend/s3: Support automatic region validation for `af-south-1` ``` Updated via: ```console $ go get github.com/aws/aws-sdk-go@v1.30.12 $ go mod tidy $ go mod vendor ``` Output from acceptance testing: ```console $ TF_ACC=1 go test -v ./backend/remote-state/s3 | grep '^--- ' --- PASS: TestBackend_impl (0.00s) --- PASS: TestBackendConfig (1.68s) --- PASS: TestBackendConfig_invalidKey (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyLength (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyEncoding (0.00s) --- PASS: TestBackendConfig_conflictingEncryptionSchema (0.00s) --- PASS: TestBackend (15.07s) --- PASS: TestBackendLocked (26.40s) --- PASS: TestBackendSSECustomerKey (16.99s) --- PASS: TestBackendExtraPaths (12.05s) --- PASS: TestBackendPrefixInWorkspace (5.55s) --- PASS: TestKeyEnv (45.07s) --- PASS: TestRemoteClient_impl (0.00s) --- PASS: TestRemoteClient (5.39s) --- PASS: TestRemoteClientLocks (14.30s) --- PASS: TestForceUnlock (20.08s) --- PASS: TestRemoteClient_clientMD5 (16.43s) --- PASS: TestRemoteClient_stateChecksum (24.58s) ``` Co-authored-by: Nicola Senno <nicola.senno@workday.com>
2020-04-24 18:20:04 +02:00
# github.com/aws/aws-sdk-go v1.30.12
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/aws/aws-sdk-go/aws
update cty
2020-02-21 20:24:44 +01:00
github.com/aws/aws-sdk-go/aws/arn
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/aws/aws-sdk-go/aws/awserr
github.com/aws/aws-sdk-go/aws/awsutil
github.com/aws/aws-sdk-go/aws/client
github.com/aws/aws-sdk-go/aws/client/metadata
update cty
2020-02-21 20:24:44 +01:00
github.com/aws/aws-sdk-go/aws/corehandlers
github.com/aws/aws-sdk-go/aws/credentials
github.com/aws/aws-sdk-go/aws/credentials/ec2rolecreds
github.com/aws/aws-sdk-go/aws/credentials/endpointcreds
github.com/aws/aws-sdk-go/aws/credentials/processcreds
github.com/aws/aws-sdk-go/aws/credentials/stscreds
deps: github.com/aws/aws-sdk-go@v1.16.4 and github.com/terraform-providers/terraform-provider-aws@v1.52.0 Notable changes: * backend/s3: Automatic validation of `eu-north-1` region * backend/s3: Support for `credential_process` handling in AWS configuration file Updated via: ``` go get github.com/aws/aws-sdk-go@v1.16.4 go get github.com/terraform-providers/terraform-provider-aws@v1.52.0 go mod tidy go mod vendor ```
2018-12-14 02:30:43 +01:00
github.com/aws/aws-sdk-go/aws/crr
update cty
2020-02-21 20:24:44 +01:00
github.com/aws/aws-sdk-go/aws/csm
github.com/aws/aws-sdk-go/aws/defaults
github.com/aws/aws-sdk-go/aws/ec2metadata
github.com/aws/aws-sdk-go/aws/endpoints
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/aws/aws-sdk-go/aws/request
update cty
2020-02-21 20:24:44 +01:00
github.com/aws/aws-sdk-go/aws/session
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/aws/aws-sdk-go/aws/signer/v4
deps: github.com/aws/aws-sdk-go@v1.30.12 [master] (#24745) * update github.com/aws/aws-sdk-go to v1.30.9 * deps: github.com/aws/aws-sdk-go@v1.30.12 Reference: https://github.com/hashicorp/terraform/issues/24710 Reference: https://github.com/hashicorp/terraform/issues/24741 Changes: ``` NOTES: * backend/s3: Region validation now automatically supports the new `af-south-1` (Africa (Cape Town)) region. For AWS operations to work in the new region, the region must be explicitly enabled as outlined in the [AWS Documentation](https://docs.aws.amazon.com/general/latest/gr/rande-manage.html#rande-manage-enable). When the region is not enabled, the Terraform S3 Backend will return errors during credential validation (e.g. `error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid`). ENHANCEMENTS: * backend/s3: Support automatic region validation for `af-south-1` ``` Updated via: ```console $ go get github.com/aws/aws-sdk-go@v1.30.12 $ go mod tidy $ go mod vendor ``` Output from acceptance testing: ```console $ TF_ACC=1 go test -v ./backend/remote-state/s3 | grep '^--- ' --- PASS: TestBackend_impl (0.00s) --- PASS: TestBackendConfig (1.68s) --- PASS: TestBackendConfig_invalidKey (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyLength (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyEncoding (0.00s) --- PASS: TestBackendConfig_conflictingEncryptionSchema (0.00s) --- PASS: TestBackend (15.07s) --- PASS: TestBackendLocked (26.40s) --- PASS: TestBackendSSECustomerKey (16.99s) --- PASS: TestBackendExtraPaths (12.05s) --- PASS: TestBackendPrefixInWorkspace (5.55s) --- PASS: TestKeyEnv (45.07s) --- PASS: TestRemoteClient_impl (0.00s) --- PASS: TestRemoteClient (5.39s) --- PASS: TestRemoteClientLocks (14.30s) --- PASS: TestForceUnlock (20.08s) --- PASS: TestRemoteClient_clientMD5 (16.43s) --- PASS: TestRemoteClient_stateChecksum (24.58s) ``` Co-authored-by: Nicola Senno <nicola.senno@workday.com>
2020-04-24 18:20:04 +02:00
github.com/aws/aws-sdk-go/internal/context
update cty
2020-02-21 20:24:44 +01:00
github.com/aws/aws-sdk-go/internal/ini
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
github.com/aws/aws-sdk-go/internal/s3err
update cty
2020-02-21 20:24:44 +01:00
github.com/aws/aws-sdk-go/internal/sdkio
github.com/aws/aws-sdk-go/internal/sdkmath
github.com/aws/aws-sdk-go/internal/sdkrand
github.com/aws/aws-sdk-go/internal/sdkuri
github.com/aws/aws-sdk-go/internal/shareddefaults
deps: github.com/aws/aws-sdk-go@v1.30.12 [master] (#24745) * update github.com/aws/aws-sdk-go to v1.30.9 * deps: github.com/aws/aws-sdk-go@v1.30.12 Reference: https://github.com/hashicorp/terraform/issues/24710 Reference: https://github.com/hashicorp/terraform/issues/24741 Changes: ``` NOTES: * backend/s3: Region validation now automatically supports the new `af-south-1` (Africa (Cape Town)) region. For AWS operations to work in the new region, the region must be explicitly enabled as outlined in the [AWS Documentation](https://docs.aws.amazon.com/general/latest/gr/rande-manage.html#rande-manage-enable). When the region is not enabled, the Terraform S3 Backend will return errors during credential validation (e.g. `error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid`). ENHANCEMENTS: * backend/s3: Support automatic region validation for `af-south-1` ``` Updated via: ```console $ go get github.com/aws/aws-sdk-go@v1.30.12 $ go mod tidy $ go mod vendor ``` Output from acceptance testing: ```console $ TF_ACC=1 go test -v ./backend/remote-state/s3 | grep '^--- ' --- PASS: TestBackend_impl (0.00s) --- PASS: TestBackendConfig (1.68s) --- PASS: TestBackendConfig_invalidKey (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyLength (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyEncoding (0.00s) --- PASS: TestBackendConfig_conflictingEncryptionSchema (0.00s) --- PASS: TestBackend (15.07s) --- PASS: TestBackendLocked (26.40s) --- PASS: TestBackendSSECustomerKey (16.99s) --- PASS: TestBackendExtraPaths (12.05s) --- PASS: TestBackendPrefixInWorkspace (5.55s) --- PASS: TestKeyEnv (45.07s) --- PASS: TestRemoteClient_impl (0.00s) --- PASS: TestRemoteClient (5.39s) --- PASS: TestRemoteClientLocks (14.30s) --- PASS: TestForceUnlock (20.08s) --- PASS: TestRemoteClient_clientMD5 (16.43s) --- PASS: TestRemoteClient_stateChecksum (24.58s) ``` Co-authored-by: Nicola Senno <nicola.senno@workday.com>
2020-04-24 18:20:04 +02:00
github.com/aws/aws-sdk-go/internal/strings
github.com/aws/aws-sdk-go/internal/sync/singleflight
update cty
2020-02-21 20:24:44 +01:00
github.com/aws/aws-sdk-go/private/protocol
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/aws/aws-sdk-go/private/protocol/eventstream
github.com/aws/aws-sdk-go/private/protocol/eventstream/eventstreamapi
update cty
2020-02-21 20:24:44 +01:00
github.com/aws/aws-sdk-go/private/protocol/json/jsonutil
github.com/aws/aws-sdk-go/private/protocol/jsonrpc
github.com/aws/aws-sdk-go/private/protocol/query
github.com/aws/aws-sdk-go/private/protocol/query/queryutil
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/aws/aws-sdk-go/private/protocol/rest
github.com/aws/aws-sdk-go/private/protocol/restxml
deps: github.com/aws/aws-sdk-go@v1.20.4 Relevant changes: * backend/s3: Support for chaining assume IAM role from AWS shared configuration files * backend/s3: Fix AWS shared configuration file credential source not assuming a role with environment and ECS credentials References: * https://github.com/aws/aws-sdk-go/releases/tag/v1.20.0 * https://github.com/aws/aws-sdk-go/pull/2579 * https://github.com/aws/aws-sdk-go/issues/2385 Updated via: ```console $ go get github.com/aws/aws-sdk-go@v1.20.4 $ go mod tidy $ go mod vendor ```
2019-06-20 06:04:44 +02:00
github.com/aws/aws-sdk-go/private/protocol/xml/xmlutil
update cty
2020-02-21 20:24:44 +01:00
github.com/aws/aws-sdk-go/service/dynamodb
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/aws/aws-sdk-go/service/iam
update cty
2020-02-21 20:24:44 +01:00
github.com/aws/aws-sdk-go/service/s3
deps: github.com/aws/aws-sdk-go@v1.30.12 [master] (#24745) * update github.com/aws/aws-sdk-go to v1.30.9 * deps: github.com/aws/aws-sdk-go@v1.30.12 Reference: https://github.com/hashicorp/terraform/issues/24710 Reference: https://github.com/hashicorp/terraform/issues/24741 Changes: ``` NOTES: * backend/s3: Region validation now automatically supports the new `af-south-1` (Africa (Cape Town)) region. For AWS operations to work in the new region, the region must be explicitly enabled as outlined in the [AWS Documentation](https://docs.aws.amazon.com/general/latest/gr/rande-manage.html#rande-manage-enable). When the region is not enabled, the Terraform S3 Backend will return errors during credential validation (e.g. `error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid`). ENHANCEMENTS: * backend/s3: Support automatic region validation for `af-south-1` ``` Updated via: ```console $ go get github.com/aws/aws-sdk-go@v1.30.12 $ go mod tidy $ go mod vendor ``` Output from acceptance testing: ```console $ TF_ACC=1 go test -v ./backend/remote-state/s3 | grep '^--- ' --- PASS: TestBackend_impl (0.00s) --- PASS: TestBackendConfig (1.68s) --- PASS: TestBackendConfig_invalidKey (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyLength (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyEncoding (0.00s) --- PASS: TestBackendConfig_conflictingEncryptionSchema (0.00s) --- PASS: TestBackend (15.07s) --- PASS: TestBackendLocked (26.40s) --- PASS: TestBackendSSECustomerKey (16.99s) --- PASS: TestBackendExtraPaths (12.05s) --- PASS: TestBackendPrefixInWorkspace (5.55s) --- PASS: TestKeyEnv (45.07s) --- PASS: TestRemoteClient_impl (0.00s) --- PASS: TestRemoteClient (5.39s) --- PASS: TestRemoteClientLocks (14.30s) --- PASS: TestForceUnlock (20.08s) --- PASS: TestRemoteClient_clientMD5 (16.43s) --- PASS: TestRemoteClient_stateChecksum (24.58s) ``` Co-authored-by: Nicola Senno <nicola.senno@workday.com>
2020-04-24 18:20:04 +02:00
github.com/aws/aws-sdk-go/service/s3/internal/arn
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/aws/aws-sdk-go/service/sts
deps: github.com/aws/aws-sdk-go@v1.21.7 Notable changes (from Terraform AWS Provider CHANGELOG): ``` NOTES: * backend/s3: Region validation now automatically supports the new `me-south-1` Middle East (Bahrain) region. For AWS operations to work in the new region, the region must be explicitly enabled as outlined in the [previous new region announcement blog post](https://aws.amazon.com/blogs/aws/now-open-aws-asia-pacific-hong-kong-region/). When the region is not enabled, the Terraform S3 Backend will return errors during credential validation (e.g. `error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid`). * backend/s3: After this update, the AWS Go SDK will prefer credentials found via the `AWS_PROFILE` environment variable when both the `AWS_PROFILE` environment variable and the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables are statically defined. Previously the SDK would ignore the `AWS_PROFILE` environment variable, if static environment credentials were also specified. This is listed as a bug fix in the AWS Go SDK release notes. ENHANCEMENTS: * backend/s3: Add support for assuming role via web identity token via the `AWS_WEB_IDENTITY_TOKEN_FILE` and `AWS_ROLE_ARN` environment variables * backend/s3: Support automatic region validation for `me-south-1` BUG FIXES: * backend/s3: Load credentials via the `AWS_PROFILE` environment variable (if available) when `AWS_PROFILE` is defined along with `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` ``` Updated via: ``` go get github.com/aws/aws-sdk-go@v1.21.7 go mod tidy go mod vendor ``` Verification with this update: ```hcl terraform { backend "s3" { bucket = "me-south-1-testing" key = "test" region = "me-south-1" } } output "test" { value = timestamp() } ``` Outputs: ``` $ terraform apply Apply complete! Resources: 0 added, 0 changed, 0 destroyed. Outputs: test = 2019-07-30T12:49:19Z ``` If the new region is not properly enabled for the account, errors like the below will be received: ``` $ terraform init Initializing the backend... Error: error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid. ``` To use this region before this update: ```hcl terraform { # ... potentially other configuration ... backend "s3" { # ... other configuration ... region = "me-south-1" skip_region_validation = true } } ```
2019-07-30 14:51:39 +02:00
github.com/aws/aws-sdk-go/service/sts/stsiface
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/baiyubin/aliyun-sts-go-sdk v0.0.0-20180326062324-cfa1a18b161f
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
# github.com/bgentry/go-netrc v0.0.0-20140422174119-9fd32a8b3d3d
github.com/bgentry/go-netrc/netrc
vendor: github.com/terraform-providers/terraform-provider-aws@v1.58.0
2019-02-12 13:23:47 +01:00
# github.com/bgentry/speakeasy v0.1.0
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/bgentry/speakeasy
vendor: github.com/blang/semver@v3.5.1
2019-02-12 11:22:28 +01:00
# github.com/blang/semver v3.5.1+incompatible
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/blang/semver
lang/funcs: Switch fileset() function glob implementation to github.com/bmatcuk/doublestar to support additional glob patterns This allows the usage of the glob patterns `**` and `{alternative1,...}` to simplify Terraform configuration logic for more complex file matching.
2019-08-31 02:14:38 +02:00
# github.com/bmatcuk/doublestar v1.1.5
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
lang/funcs: Switch fileset() function glob implementation to github.com/bmatcuk/doublestar to support additional glob patterns This allows the usage of the glob patterns `**` and `{alternative1,...}` to simplify Terraform configuration logic for more complex file matching.
2019-08-31 02:14:38 +02:00
github.com/bmatcuk/doublestar
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/boltdb/bolt v1.3.1
## explicit
# github.com/chzyer/logex v1.1.10
## explicit
vendor: go get github.com/chzyer/readline@master This new version includes Solaris support, the lack of which previously caused us to disable readline-using features ("terraform console") on Solaris builds.
2019-08-10 00:49:03 +02:00
# github.com/chzyer/readline v0.0.0-20180603132655-2972be24d48e
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/chzyer/readline
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/chzyer/test v0.0.0-20180213035817-a1ea475d72b1
## explicit
# github.com/coreos/bbolt v1.3.0
## explicit
vendor: make some transitive dependencies line up better After a bunch of recent changes/rebasing our vendored dependencies got a little out of sync w.r.t transitive dependencies through codebases that are not themselves Go Modules yet.
2018-10-17 02:12:35 +02:00
# github.com/coreos/etcd v3.3.10+incompatible
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
update cty
2020-02-21 20:24:44 +01:00
github.com/coreos/etcd/auth/authpb
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/coreos/etcd/client
github.com/coreos/etcd/clientv3
github.com/coreos/etcd/clientv3/concurrency
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
github.com/coreos/etcd/etcdserver/api/v3rpc/rpctypes
github.com/coreos/etcd/etcdserver/etcdserverpb
github.com/coreos/etcd/mvcc/mvccpb
update cty
2020-02-21 20:24:44 +01:00
github.com/coreos/etcd/pkg/pathutil
github.com/coreos/etcd/pkg/srv
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
github.com/coreos/etcd/pkg/tlsutil
update cty
2020-02-21 20:24:44 +01:00
github.com/coreos/etcd/pkg/transport
github.com/coreos/etcd/pkg/types
github.com/coreos/etcd/version
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
# github.com/coreos/go-semver v0.2.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/coreos/go-semver/semver
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/coreos/go-systemd v0.0.0-20181012123002-c6f51f82210d
## explicit
# github.com/coreos/pkg v0.0.0-20180928190104-399ea9e2e55f
## explicit
vendor: Update HCL2 and cty, and other related packages This brings in a bugfix for analyzing variables inside relative traversal expressions in HCL, and a cosmetic bugfix in cty for GoString of cty.NullVal(cty.DynamicPseudoType). This also updates some other packages, as a result of running "go get -u".
2018-09-25 20:19:23 +02:00
# github.com/davecgh/go-spew v1.1.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/davecgh/go-spew/spew
backend/azurerm: Support for authenticating using the Azure CLI (#19465) * Upgrading to 2.0.0 of github.com/hashicorp/go-azure-helpers * Support for authenticating using Azure CLI * backend/azurerm: support for authenticating using the Azure CLI
2018-12-10 22:23:30 +01:00
# github.com/dgrijalva/jwt-go v3.2.0+incompatible
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/dgrijalva/jwt-go
vendor: upgrade Azure SDK and Azure/go-autorest This involves some minor changes to the "azure" backend code to account for upstream breaking changes.
2019-11-26 01:03:57 +01:00
# github.com/dimchansky/utfbom v1.1.0
backend/azurerm: upgrading the SDK / support for proxies (#19414) * vendor updates - updating to v21.3.0 of github.com/Azure/azure-sdk-for-go - updating to v10.15.4 of github.com/Azure/go-autorest - vendoring github.com/hashicorp/go-azure-helpers @ 0.1.1 * backend/azurerm: refactoring to use the new auth package - refactoring the backend to use a shared client via the new auth package - adding tests covering both Service Principal and Access Key auth - support for authenticating using a proxy - rewriting the backend documentation to include examples of both authentication types * switching to use the build-in logging function * documenting it's also possible to retrieve the access key from an env var
2018-11-21 22:06:03 +01:00
github.com/dimchansky/utfbom
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/dnaeon/go-vcr v0.0.0-20180920040454-5637cf3d8a31
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
# github.com/dylanmei/iso8601 v0.1.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/dylanmei/iso8601
vendor: github.com/dylanmei/winrmtest@99b7fe2fddf1
2019-02-26 19:22:15 +01:00
# github.com/dylanmei/winrmtest v0.0.0-20190225150635-99b7fe2fddf1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/dylanmei/winrmtest
vendor: github.com/mitchellh/cli@v1.0.0 go get github.com/mitchellh/cli@v1.0.0 go mod tidy go mod vendor
2019-02-21 09:56:05 +01:00
# github.com/fatih/color v1.7.0
github.com/fatih/color
deps: Bump github.com/go-test/deep to 1.0.3
2019-08-21 12:32:13 +02:00
# github.com/go-test/deep v1.0.3
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/go-test/deep
vendor: github.com/terraform-providers/terraform-provider-aws@v1.58.0
2019-02-12 13:23:47 +01:00
# github.com/gogo/protobuf v1.2.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: make some transitive dependencies line up better After a bunch of recent changes/rebasing our vendored dependencies got a little out of sync w.r.t transitive dependencies through codebases that are not themselves Go Modules yet.
2018-10-17 02:12:35 +02:00
github.com/gogo/protobuf/gogoproto
github.com/gogo/protobuf/proto
github.com/gogo/protobuf/protoc-gen-gogo/descriptor
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/golang/groupcache v0.0.0-20180513044358-24b0969c4cb7
## explicit
vendor: github.com/golang/mock@v1.3.1
2019-05-27 13:22:03 +02:00
# github.com/golang/mock v1.3.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/golang/mock/gomock
Version tools per Go convention under tools.go
2019-10-17 22:17:23 +02:00
github.com/golang/mock/mockgen
github.com/golang/mock/mockgen/model
vendor: Bump github.com/golang/protobuf to 1.3.2
2019-09-05 14:47:27 +02:00
# github.com/golang/protobuf v1.3.2
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/golang/protobuf/proto
update cty
2020-02-21 20:24:44 +01:00
github.com/golang/protobuf/protoc-gen-go/descriptor
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/golang/protobuf/ptypes
github.com/golang/protobuf/ptypes/any
github.com/golang/protobuf/ptypes/duration
vendor: Bump go-azure-helpers to 0.7.0
2019-08-20 10:32:02 +02:00
github.com/golang/protobuf/ptypes/timestamp
vendor: github.com/terraform-providers/terraform-provider-aws@v1.58.0
2019-02-12 13:23:47 +01:00
# github.com/golang/snappy v0.0.0-20180518054509-2e65f85255db
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: github.com/terraform-providers/terraform-provider-aws@v1.58.0
2019-02-12 13:23:47 +01:00
github.com/golang/snappy
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
# github.com/google/go-cmp v0.3.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/google/go-cmp/cmp
github.com/google/go-cmp/cmp/cmpopts
github.com/google/go-cmp/cmp/internal/diff
vendor: github.com/google/go-cmp@v0.3.0
2019-05-28 03:35:42 +02:00
github.com/google/go-cmp/cmp/internal/flags
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/google/go-cmp/cmp/internal/function
github.com/google/go-cmp/cmp/internal/value
vendor: catch up vendoring We've missed a few recent additions to go.mod in the vendor directory. We need to keep this updated for the moment until all of the surrounding tooling is ready to go all-in with Go 1.11 modules.
2018-11-08 22:13:13 +01:00
# github.com/google/go-querystring v1.0.0
github.com/google/go-querystring/query
remove satori/go.uuid in favor of google/uuid
2019-08-09 21:09:41 +02:00
# github.com/google/uuid v1.1.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
remove satori/go.uuid in favor of google/uuid
2019-08-09 21:09:41 +02:00
github.com/google/uuid
vendor: Bump go-getter to 1.4.0
2019-09-09 14:04:58 +02:00
# github.com/googleapis/gax-go/v2 v2.0.5
vendor: cloud.google.com/go@v0.36.0 go get cloud.google.com/go@v0.36.0 go mod tidy go mod vendor
2019-02-20 19:57:56 +01:00
github.com/googleapis/gax-go/v2
Update dependencies
2020-04-25 08:41:54 +02:00
# github.com/gophercloud/gophercloud v0.10.1-0.20200424014253-c3bfe50899e5
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/gophercloud/gophercloud
github.com/gophercloud/gophercloud/openstack
update cty
2020-02-21 20:24:44 +01:00
github.com/gophercloud/gophercloud/openstack/identity/v2/tenants
github.com/gophercloud/gophercloud/openstack/identity/v2/tokens
Update dependencies
2020-04-25 08:41:54 +02:00
github.com/gophercloud/gophercloud/openstack/identity/v3/extensions/ec2tokens
github.com/gophercloud/gophercloud/openstack/identity/v3/extensions/oauth1
update cty
2020-02-21 20:24:44 +01:00
github.com/gophercloud/gophercloud/openstack/identity/v3/tokens
github.com/gophercloud/gophercloud/openstack/objectstorage/v1/accounts
github.com/gophercloud/gophercloud/openstack/objectstorage/v1/containers
github.com/gophercloud/gophercloud/openstack/objectstorage/v1/objects
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/gophercloud/gophercloud/openstack/objectstorage/v1/swauth
update cty
2020-02-21 20:24:44 +01:00
github.com/gophercloud/gophercloud/openstack/utils
github.com/gophercloud/gophercloud/pagination
Update dependencies
2020-04-25 08:41:54 +02:00
# github.com/gophercloud/utils v0.0.0-20200423144003-7c72efc7435d
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
Update dependencies
2020-04-25 08:41:54 +02:00
github.com/gophercloud/utils/client
github.com/gophercloud/utils/env
vendor: github.com/terraform-providers/terraform-provider-openstack@v1.15.0
2019-02-08 11:59:06 +01:00
github.com/gophercloud/utils/openstack/clientconfig
Update dependencies
2020-04-25 08:41:54 +02:00
github.com/gophercloud/utils/terraform/auth
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/gopherjs/gopherjs v0.0.0-20181017120253-0766667cb4d1
## explicit
# github.com/gorilla/websocket v1.4.0
## explicit
# github.com/grpc-ecosystem/go-grpc-middleware v1.0.0
## explicit
# github.com/grpc-ecosystem/go-grpc-prometheus v1.2.0
## explicit
# github.com/grpc-ecosystem/grpc-gateway v1.8.5
## explicit
deps: github.com/hashicorp/aws-sdk-go-base@v0.4.0 (#22994)
2019-10-11 18:50:12 +02:00
# github.com/hashicorp/aws-sdk-go-base v0.4.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
backend/s3: Switch from github.com/terraform-providers/terraform-provider-aws to github.com/hashicorp/aws-sdk-go-base Output from acceptance testing (no new failures): ``` --- PASS: TestBackend_impl (0.00s) --- PASS: TestBackendConfig (0.37s) --- PASS: TestBackendConfig_invalidKey (0.00s) --- PASS: TestBackend (3.26s) --- PASS: TestBackendLocked (6.80s) --- FAIL: TestBackendExtraPaths (2.32s) --- PASS: TestBackendPrefixInWorkspace (2.06s) --- PASS: TestKeyEnv (8.20s) --- PASS: TestRemoteClient_impl (0.00s) --- PASS: TestRemoteClient (2.42s) --- PASS: TestRemoteClientLocks (6.33s) --- PASS: TestForceUnlock (13.31s) --- PASS: TestRemoteClient_clientMD5 (11.75s) --- PASS: TestRemoteClient_stateChecksum (10.07s) ```
2019-02-18 08:15:26 +01:00
github.com/hashicorp/aws-sdk-go-base
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
# github.com/hashicorp/consul v0.0.0-20171026175957-610f3c86a089
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/consul/api
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
github.com/hashicorp/consul/lib/freeport
update cty
2020-02-21 20:24:44 +01:00
github.com/hashicorp/consul/testutil
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/consul/testutil/retry
vendor: Update HCL2 and cty, and other related packages This brings in a bugfix for analyzing variables inside relative traversal expressions in HCL, and a cosmetic bugfix in cty for GoString of cty.NullVal(cty.DynamicPseudoType). This also updates some other packages, as a result of running "go get -u".
2018-09-25 20:19:23 +02:00
# github.com/hashicorp/errwrap v1.0.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/errwrap
vendor: upgrade Azure SDK and Azure/go-autorest This involves some minor changes to the "azure" backend code to account for upstream breaking changes.
2019-11-26 01:03:57 +01:00
# github.com/hashicorp/go-azure-helpers v0.10.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
backend/azurerm: upgrading the SDK / support for proxies (#19414) * vendor updates - updating to v21.3.0 of github.com/Azure/azure-sdk-for-go - updating to v10.15.4 of github.com/Azure/go-autorest - vendoring github.com/hashicorp/go-azure-helpers @ 0.1.1 * backend/azurerm: refactoring to use the new auth package - refactoring the backend to use a shared client via the new auth package - adding tests covering both Service Principal and Access Key auth - support for authenticating using a proxy - rewriting the backend documentation to include examples of both authentication types * switching to use the build-in logging function * documenting it's also possible to retrieve the access key from an env var
2018-11-21 22:06:03 +01:00
github.com/hashicorp/go-azure-helpers/authentication
vendor: upgrade Azure SDK and Azure/go-autorest This involves some minor changes to the "azure" backend code to account for upstream breaking changes.
2019-11-26 01:03:57 +01:00
github.com/hashicorp/go-azure-helpers/sender
backend/azurerm: support for authenticating via SAS Tokens (#19440) * adding acceptance tests for msi auth * including the resource group name in the tests * backend/azurerm: support for authenticating using a SAS Token * resolving merge conflicts * moving the defer to prior to the error
2018-11-22 18:02:33 +01:00
github.com/hashicorp/go-azure-helpers/storage
vendor: github.com/hashicorp/go-checkpoint@v0.5.0 go get github.com/hashicorp/go-checkpoint@v0.5.0 go mod tidy go mod vendor
2019-02-21 09:50:02 +01:00
# github.com/hashicorp/go-checkpoint v0.5.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/go-checkpoint
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
# github.com/hashicorp/go-cleanhttp v0.5.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/go-cleanhttp
update go-getter Update to a go1.12 compatible branch of v1.4.1, which removes the Header.Clone methods which were added in go1.13.
2020-01-06 20:02:54 +01:00
# github.com/hashicorp/go-getter v1.4.2-0.20200106182914-9813cbd4eb02
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/go-getter
github.com/hashicorp/go-getter/helper/url
update go-plugin and hclog
2018-10-02 22:03:07 +02:00
# github.com/hashicorp/go-hclog v0.0.0-20181001195459-61d530d6c27f
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/go-hclog
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/hashicorp/go-immutable-radix v0.0.0-20180129170900-7f3cd4390caa
## explicit
# github.com/hashicorp/go-msgpack v0.5.4
## explicit
vendor: Update HCL2 and cty, and other related packages This brings in a bugfix for analyzing variables inside relative traversal expressions in HCL, and a cosmetic bugfix in cty for GoString of cty.NullVal(cty.DynamicPseudoType). This also updates some other packages, as a result of running "go get -u".
2018-09-25 20:19:23 +02:00
# github.com/hashicorp/go-multierror v1.0.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/go-multierror
update go-plugin package Fixes a minor issue where the plugin may be closed before the stderr reader completes, resulting in a warning in the logs.
2019-06-10 21:43:36 +02:00
# github.com/hashicorp/go-plugin v1.0.1-0.20190610192547-a1bc61569a26
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/go-plugin
update go-plugin This unfortunately breaks alpha comaptibility at this point, due to changes in the grpc paths.
2019-02-13 00:27:56 +01:00
github.com/hashicorp/go-plugin/internal/plugin
gomod: update `go-tfe`
2019-04-08 11:13:14 +02:00
# github.com/hashicorp/go-retryablehttp v0.5.2
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/go-retryablehttp
vendor: github.com/hashicorp/go-rootcerts@v1.0.0 go get github.com/hashicorp/go-rootcerts@v1.0.0 go mod tidy go mod vendor
2019-02-21 09:54:14 +01:00
# github.com/hashicorp/go-rootcerts v1.0.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/go-rootcerts
vendor: github.com/terraform-providers/terraform-provider-aws@v1.58.0
2019-02-12 13:23:47 +01:00
# github.com/hashicorp/go-safetemp v1.0.0
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/go-safetemp
Point to updated go-tfe
2019-11-14 22:21:18 +01:00
# github.com/hashicorp/go-slug v0.4.1
vendor: catch up vendoring We've missed a few recent additions to go.mod in the vendor directory. We need to keep this updated for the moment until all of the surrounding tooling is ready to go all-in with Go 1.11 modules.
2018-11-08 22:13:13 +01:00
github.com/hashicorp/go-slug
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/hashicorp/go-sockaddr v0.0.0-20180320115054-6d291a969b86
## explicit
Point to updated go-tfe
2019-11-14 22:21:18 +01:00
# github.com/hashicorp/go-tfe v0.3.27
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: catch up vendoring We've missed a few recent additions to go.mod in the vendor directory. We need to keep this updated for the moment until all of the surrounding tooling is ready to go all-in with Go 1.11 modules.
2018-11-08 22:13:13 +01:00
github.com/hashicorp/go-tfe
gomod: update `go-tfe`
2019-04-08 11:13:14 +02:00
# github.com/hashicorp/go-uuid v1.0.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/go-uuid
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
# github.com/hashicorp/go-version v1.2.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/go-version
vendor: Bump go-getter to 1.4.0
2019-09-09 14:04:58 +02:00
# github.com/hashicorp/golang-lru v0.5.1
modules: update Azure deps to latest The dependencies here are dated and are causing conflicts with the ACME provider, namely the version of the top-level autorest package. This explicitly updates the Azure SDK and autorest packages, with the separately versioned sub-packages being added automatically.
2019-07-30 00:19:40 +02:00
github.com/hashicorp/golang-lru/simplelru
configs/configupgrade: do not panic on HEREDOCs. (#20281) Previously, configupgrade would panic if it encountered a HEREDOC. For the time being, we will simply print out the HEREDOC as-is. Unfortunately, we discovered that terraform 0.11's version of HCL allowed for HEREDOCs with the termination delimiter inline (instead of on a newline, which is technically correct). Since 0.12configupgrade needs to be bug-compatible with terraform 0.11, we must roll back to the same version of HCL used in terraform 0.11.
2019-02-09 00:51:53 +01:00
# github.com/hashicorp/hcl v0.0.0-20170504190234-a4b07c25de5f
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/hcl
github.com/hashicorp/hcl/hcl/ast
github.com/hashicorp/hcl/hcl/parser
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
github.com/hashicorp/hcl/hcl/scanner
github.com/hashicorp/hcl/hcl/strconv
update cty
2020-02-21 20:24:44 +01:00
github.com/hashicorp/hcl/hcl/token
github.com/hashicorp/hcl/json/parser
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/hcl/json/scanner
github.com/hashicorp/hcl/json/token
vendor: go get github.com/hashicorp/hcl/v2@v2.5.0
2020-05-06 19:34:17 +02:00
# github.com/hashicorp/hcl/v2 v2.5.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: switch to HCL 2.0 in the HCL repository Previously we were using the experimental HCL 2 repository, but now we'll shift over to the v2 import path within the main HCL repository as part of actually releasing HCL 2.0 as stable. This is a mechanical search/replace to the new import paths. It also switches to the v2.0.0 release of HCL, which includes some new code that Terraform didn't previously have but should not change any behavior that matters for Terraform's purposes. For the moment the experimental HCL2 repository is still an indirect dependency via terraform-config-inspect, so it remains in our go.sum and vendor directories for the moment. Because terraform-config-inspect uses a much smaller subset of the HCL2 functionality, this does still manage to prune the vendor directory a little. A subsequent release of terraform-config-inspect should allow us to completely remove that old repository in a future commit.
2019-09-10 00:58:44 +02:00
github.com/hashicorp/hcl/v2
update cty
2020-02-21 20:24:44 +01:00
github.com/hashicorp/hcl/v2/ext/customdecode
github.com/hashicorp/hcl/v2/ext/dynblock
github.com/hashicorp/hcl/v2/ext/tryfunc
github.com/hashicorp/hcl/v2/ext/typeexpr
github.com/hashicorp/hcl/v2/gohcl
vendor: switch to HCL 2.0 in the HCL repository Previously we were using the experimental HCL 2 repository, but now we'll shift over to the v2 import path within the main HCL repository as part of actually releasing HCL 2.0 as stable. This is a mechanical search/replace to the new import paths. It also switches to the v2.0.0 release of HCL, which includes some new code that Terraform didn't previously have but should not change any behavior that matters for Terraform's purposes. For the moment the experimental HCL2 repository is still an indirect dependency via terraform-config-inspect, so it remains in our go.sum and vendor directories for the moment. Because terraform-config-inspect uses a much smaller subset of the HCL2 functionality, this does still manage to prune the vendor directory a little. A subsequent release of terraform-config-inspect should allow us to completely remove that old repository in a future commit.
2019-09-10 00:58:44 +02:00
github.com/hashicorp/hcl/v2/hcldec
github.com/hashicorp/hcl/v2/hcled
github.com/hashicorp/hcl/v2/hclparse
update cty
2020-02-21 20:24:44 +01:00
github.com/hashicorp/hcl/v2/hclsyntax
vendor: switch to HCL 2.0 in the HCL repository Previously we were using the experimental HCL 2 repository, but now we'll shift over to the v2 import path within the main HCL repository as part of actually releasing HCL 2.0 as stable. This is a mechanical search/replace to the new import paths. It also switches to the v2.0.0 release of HCL, which includes some new code that Terraform didn't previously have but should not change any behavior that matters for Terraform's purposes. For the moment the experimental HCL2 repository is still an indirect dependency via terraform-config-inspect, so it remains in our go.sum and vendor directories for the moment. Because terraform-config-inspect uses a much smaller subset of the HCL2 functionality, this does still manage to prune the vendor directory a little. A subsequent release of terraform-config-inspect should allow us to completely remove that old repository in a future commit.
2019-09-10 00:58:44 +02:00
github.com/hashicorp/hcl/v2/hcltest
update cty
2020-02-21 20:24:44 +01:00
github.com/hashicorp/hcl/v2/hclwrite
github.com/hashicorp/hcl/v2/json
vendor: github.com/hashicorp/hil@latest
2019-02-12 13:09:17 +01:00
# github.com/hashicorp/hil v0.0.0-20190212112733-ab17b08d6590
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/hil
github.com/hashicorp/hil/ast
github.com/hashicorp/hil/parser
github.com/hashicorp/hil/scanner
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/hashicorp/memberlist v0.1.0
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
# github.com/hashicorp/serf v0.0.0-20160124182025-e4ec8cc423bb
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/serf/coordinate
Mildwonkey/tfconfig upgrade (#23670) * deps: bump terraform-config-inspect library * configs: parse `version` in new required_providers block With the latest version of `terraform-config-inspect`, the required_providers attribute can now be a string or an object with attributes "source" and "version". This change allows parsing the version constraint from the new object while ignoring any given source attribute.
2020-01-10 17:54:53 +01:00
# github.com/hashicorp/terraform-config-inspect v0.0.0-20191212124732-c6ae6269b9d7
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: Add github.com/hashicorp/terraform-config-inspect
2019-01-09 02:42:48 +01:00
github.com/hashicorp/terraform-config-inspect/tfconfig
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
# github.com/hashicorp/terraform-svchost v0.0.0-20191011084731-65d371908596
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
github.com/hashicorp/terraform-svchost
github.com/hashicorp/terraform-svchost/auth
github.com/hashicorp/terraform-svchost/disco
vendor: github.com/terraform-providers/terraform-provider-aws@v1.58.0
2019-02-12 13:23:47 +01:00
# github.com/hashicorp/vault v0.10.4
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
github.com/hashicorp/vault/helper/compressutil
update cty
2020-02-21 20:24:44 +01:00
github.com/hashicorp/vault/helper/jsonutil
github.com/hashicorp/vault/helper/pgpkeys
update vendor from go.mod
2018-12-05 20:27:05 +01:00
# github.com/hashicorp/yamux v0.0.0-20180604194846-3520598351bb
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/hashicorp/yamux
deps: github.com/aws/aws-sdk-go@v1.30.12 [master] (#24745) * update github.com/aws/aws-sdk-go to v1.30.9 * deps: github.com/aws/aws-sdk-go@v1.30.12 Reference: https://github.com/hashicorp/terraform/issues/24710 Reference: https://github.com/hashicorp/terraform/issues/24741 Changes: ``` NOTES: * backend/s3: Region validation now automatically supports the new `af-south-1` (Africa (Cape Town)) region. For AWS operations to work in the new region, the region must be explicitly enabled as outlined in the [AWS Documentation](https://docs.aws.amazon.com/general/latest/gr/rande-manage.html#rande-manage-enable). When the region is not enabled, the Terraform S3 Backend will return errors during credential validation (e.g. `error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid`). ENHANCEMENTS: * backend/s3: Support automatic region validation for `af-south-1` ``` Updated via: ```console $ go get github.com/aws/aws-sdk-go@v1.30.12 $ go mod tidy $ go mod vendor ``` Output from acceptance testing: ```console $ TF_ACC=1 go test -v ./backend/remote-state/s3 | grep '^--- ' --- PASS: TestBackend_impl (0.00s) --- PASS: TestBackendConfig (1.68s) --- PASS: TestBackendConfig_invalidKey (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyLength (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyEncoding (0.00s) --- PASS: TestBackendConfig_conflictingEncryptionSchema (0.00s) --- PASS: TestBackend (15.07s) --- PASS: TestBackendLocked (26.40s) --- PASS: TestBackendSSECustomerKey (16.99s) --- PASS: TestBackendExtraPaths (12.05s) --- PASS: TestBackendPrefixInWorkspace (5.55s) --- PASS: TestKeyEnv (45.07s) --- PASS: TestRemoteClient_impl (0.00s) --- PASS: TestRemoteClient (5.39s) --- PASS: TestRemoteClientLocks (14.30s) --- PASS: TestForceUnlock (20.08s) --- PASS: TestRemoteClient_clientMD5 (16.43s) --- PASS: TestRemoteClient_stateChecksum (24.58s) ``` Co-authored-by: Nicola Senno <nicola.senno@workday.com>
2020-04-24 18:20:04 +02:00
# github.com/jmespath/go-jmespath v0.3.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/jmespath/go-jmespath
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/jonboulle/clockwork v0.1.0
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
# github.com/joyent/triton-go v0.0.0-20180313100802-d8f9c0314926
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/joyent/triton-go
github.com/joyent/triton-go/authentication
update cty
2020-02-21 20:24:44 +01:00
github.com/joyent/triton-go/client
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/joyent/triton-go/errors
github.com/joyent/triton-go/storage
Add Alibaba Cloud backend OSS with lock
2019-03-07 11:31:36 +01:00
# github.com/json-iterator/go v1.1.5
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
Add Alibaba Cloud backend OSS with lock
2019-03-07 11:31:36 +01:00
github.com/json-iterator/go
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/jtolds/gls v4.2.1+incompatible
## explicit
vendor: github.com/kardianos/osext@2bc1f35cddc0
2019-02-22 23:16:33 +01:00
# github.com/kardianos/osext v0.0.0-20190222173326-2bc1f35cddc0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/kardianos/osext
# github.com/keybase/go-crypto v0.0.0-20161004153544-93f5b35093ba
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
update cty
2020-02-21 20:24:44 +01:00
github.com/keybase/go-crypto/brainpool
github.com/keybase/go-crypto/cast5
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/keybase/go-crypto/openpgp
github.com/keybase/go-crypto/openpgp/armor
update cty
2020-02-21 20:24:44 +01:00
github.com/keybase/go-crypto/openpgp/elgamal
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/keybase/go-crypto/openpgp/errors
update cty
2020-02-21 20:24:44 +01:00
github.com/keybase/go-crypto/openpgp/packet
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/keybase/go-crypto/openpgp/s2k
github.com/keybase/go-crypto/rsa
Update github.com/lib/pq module
2018-11-14 21:49:15 +01:00
# github.com/lib/pq v1.0.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
Update github.com/lib/pq module
2018-11-14 21:49:15 +01:00
github.com/lib/pq
github.com/lib/pq/oid
update cty
2020-02-21 20:24:44 +01:00
# github.com/likexian/gokit v0.20.15
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
update cty
2020-02-21 20:24:44 +01:00
github.com/likexian/gokit/assert
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
# github.com/lusis/go-artifactory v0.0.0-20160115162124-7e4ce345df82
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/lusis/go-artifactory/src/artifactory.v401
# github.com/masterzen/simplexml v0.0.0-20160608183007-4572e39b1ab9
github.com/masterzen/simplexml/dom
vendor: github.com/masterzen/winrm@5e5c9a7fe54b
2019-02-25 09:45:01 +01:00
# github.com/masterzen/winrm v0.0.0-20190223112901-5e5c9a7fe54b
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/masterzen/winrm
github.com/masterzen/winrm/soap
vendor: github.com/mattn/go-colorable@v0.1.1
2019-02-22 17:51:56 +01:00
# github.com/mattn/go-colorable v0.1.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mattn/go-colorable
vendor: github.com/mattn/go-colorable@v0.1.1
2019-02-22 17:51:56 +01:00
# github.com/mattn/go-isatty v0.0.5
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mattn/go-isatty
vendor: github.com/mattn/go-shellwords@v1.0.4
2019-02-22 17:54:29 +01:00
# github.com/mattn/go-shellwords v1.0.4
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mattn/go-shellwords
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/miekg/dns v1.0.8
## explicit
vendor: github.com/mitchellh/cli@v1.0.0 go get github.com/mitchellh/cli@v1.0.0 go mod tidy go mod vendor
2019-02-21 09:56:05 +01:00
# github.com/mitchellh/cli v1.0.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mitchellh/cli
vendor: github.com/mitchellh/colorstring@d06e56a500db go get github.com/mitchellh/colorstring@d06e56a500db go mod tidy go mod vendor
2019-02-21 09:57:51 +01:00
# github.com/mitchellh/colorstring v0.0.0-20190213212951-d06e56a500db
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mitchellh/colorstring
vendor: go get github.com/mitchellh/copystructure@v1.0.0
2019-02-12 13:06:10 +01:00
# github.com/mitchellh/copystructure v1.0.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mitchellh/copystructure
modules: update Azure deps to latest The dependencies here are dated and are causing conflicts with the ACME provider, namely the version of the top-level autorest package. This explicitly updates the Azure SDK and autorest packages, with the separately versioned sub-packages being added automatically.
2019-07-30 00:19:40 +02:00
# github.com/mitchellh/go-homedir v1.1.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mitchellh/go-homedir
vendor: github.com/mitchellh/go-linereader@1b945b3263eb go get github.com/mitchellh/go-linereader@1b945b3263eb go mod tidy go mod vendor
2019-02-21 09:59:37 +01:00
# github.com/mitchellh/go-linereader v0.0.0-20190213213312-1b945b3263eb
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mitchellh/go-linereader
vendor: github.com/hashicorp/go-getter@v1.1.0 go get github.com/hashicorp/go-getter@v1.1.0 go mod tidy go mod vendor
2019-02-21 09:52:47 +01:00
# github.com/mitchellh/go-testing-interface v1.0.0
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mitchellh/go-testing-interface
vendor: Update HCL2 and cty, and other related packages This brings in a bugfix for analyzing variables inside relative traversal expressions in HCL, and a cosmetic bugfix in cty for GoString of cty.NullVal(cty.DynamicPseudoType). This also updates some other packages, as a result of running "go get -u".
2018-09-25 20:19:23 +02:00
# github.com/mitchellh/go-wordwrap v1.0.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mitchellh/go-wordwrap
vendor: github.com/mitchellh/hashstructure v1.0.0
2019-02-12 12:44:28 +01:00
# github.com/mitchellh/hashstructure v1.0.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mitchellh/hashstructure
vendor: github.com/hashicorp/hil@latest
2019-02-12 13:09:17 +01:00
# github.com/mitchellh/mapstructure v1.1.2
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mitchellh/mapstructure
vendor: go get github.com/mitchellh/panicwrap@v1.0.0
2019-11-05 10:22:11 +01:00
# github.com/mitchellh/panicwrap v1.0.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mitchellh/panicwrap
vendor: github.com/mitchellh/prefixedio@5733675afd51 go get github.com/mitchellh/prefixedio@5733675afd51 go mod tidy go mod vendor
2019-02-21 10:02:56 +01:00
# github.com/mitchellh/prefixedio v0.0.0-20190213213902-5733675afd51
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mitchellh/prefixedio
vendor: go get github.com/mitchellh/copystructure@v1.0.0
2019-02-12 13:06:10 +01:00
# github.com/mitchellh/reflectwalk v1.0.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/mitchellh/reflectwalk
Add Alibaba Cloud backend OSS with lock
2019-03-07 11:31:36 +01:00
# github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
Add Alibaba Cloud backend OSS with lock
2019-03-07 11:31:36 +01:00
github.com/modern-go/concurrent
# github.com/modern-go/reflect2 v1.0.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
Add Alibaba Cloud backend OSS with lock
2019-03-07 11:31:36 +01:00
github.com/modern-go/reflect2
update cty
2020-02-21 20:24:44 +01:00
# github.com/mozillazg/go-httpheader v0.2.1
github.com/mozillazg/go-httpheader
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
# github.com/nu7hatch/gouuid v0.0.0-20131221200532-179d4d0c4d8d
github.com/nu7hatch/gouuid
# github.com/oklog/run v1.0.0
github.com/oklog/run
# github.com/packer-community/winrmcp v0.0.0-20180102160824-81144009af58
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/packer-community/winrmcp/winrmcp
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/pascaldekloe/goe v0.0.0-20180627143212-57f6aae5913c
## explicit
command: "terraform login" command
2019-07-09 21:06:20 +02:00
# github.com/pkg/browser v0.0.0-20180916011732-0a3d74bf9ce4
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
command: "terraform login" command
2019-07-09 21:06:20 +02:00
github.com/pkg/browser
deps: github.com/aws/aws-sdk-go@v1.30.12 [master] (#24745) * update github.com/aws/aws-sdk-go to v1.30.9 * deps: github.com/aws/aws-sdk-go@v1.30.12 Reference: https://github.com/hashicorp/terraform/issues/24710 Reference: https://github.com/hashicorp/terraform/issues/24741 Changes: ``` NOTES: * backend/s3: Region validation now automatically supports the new `af-south-1` (Africa (Cape Town)) region. For AWS operations to work in the new region, the region must be explicitly enabled as outlined in the [AWS Documentation](https://docs.aws.amazon.com/general/latest/gr/rande-manage.html#rande-manage-enable). When the region is not enabled, the Terraform S3 Backend will return errors during credential validation (e.g. `error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid`). ENHANCEMENTS: * backend/s3: Support automatic region validation for `af-south-1` ``` Updated via: ```console $ go get github.com/aws/aws-sdk-go@v1.30.12 $ go mod tidy $ go mod vendor ``` Output from acceptance testing: ```console $ TF_ACC=1 go test -v ./backend/remote-state/s3 | grep '^--- ' --- PASS: TestBackend_impl (0.00s) --- PASS: TestBackendConfig (1.68s) --- PASS: TestBackendConfig_invalidKey (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyLength (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyEncoding (0.00s) --- PASS: TestBackendConfig_conflictingEncryptionSchema (0.00s) --- PASS: TestBackend (15.07s) --- PASS: TestBackendLocked (26.40s) --- PASS: TestBackendSSECustomerKey (16.99s) --- PASS: TestBackendExtraPaths (12.05s) --- PASS: TestBackendPrefixInWorkspace (5.55s) --- PASS: TestKeyEnv (45.07s) --- PASS: TestRemoteClient_impl (0.00s) --- PASS: TestRemoteClient (5.39s) --- PASS: TestRemoteClientLocks (14.30s) --- PASS: TestForceUnlock (20.08s) --- PASS: TestRemoteClient_clientMD5 (16.43s) --- PASS: TestRemoteClient_stateChecksum (24.58s) ``` Co-authored-by: Nicola Senno <nicola.senno@workday.com>
2020-04-24 18:20:04 +02:00
# github.com/pkg/errors v0.9.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/pkg/errors
vendor: github.com/posener/complete@v1.2.1 go get github.com/posener/complete@v1.2.1 go mod tidy go mod vendor
2019-02-21 10:07:42 +01:00
# github.com/posener/complete v1.2.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/posener/complete
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
github.com/posener/complete/cmd
update cty
2020-02-21 20:24:44 +01:00
github.com/posener/complete/cmd/install
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/posener/complete/match
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/prometheus/client_golang v0.9.3-0.20190127221311-3c4408c8b829
## explicit
vendor: github.com/dylanmei/winrmtest@99b7fe2fddf1
2019-02-26 19:22:15 +01:00
# github.com/satori/go.uuid v1.2.0
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/satori/go.uuid
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/sean-/seed v0.0.0-20170313163322-e2103e2c3529
## explicit
# github.com/smartystreets/assertions v0.0.0-20180927180507-b2de0cb4f26d
## explicit
# github.com/smartystreets/goconvey v0.0.0-20180222194500-ef6db91d284a
## explicit
# github.com/soheilhy/cmux v0.1.4
## explicit
vendor: github.com/spf13/afero@v1.2.1 go get github.com/spf13/afero@v1.2.1 go mod tidy go mod vendor
2019-02-21 10:09:22 +01:00
# github.com/spf13/afero v1.2.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/spf13/afero
github.com/spf13/afero/mem
vendor: catch up vendoring We've missed a few recent additions to go.mod in the vendor directory. We need to keep this updated for the moment until all of the surrounding tooling is ready to go all-in with Go 1.11 modules.
2018-11-08 22:13:13 +01:00
# github.com/svanharmelen/jsonapi v0.0.0-20180618144545-0c0828c3f16d
github.com/svanharmelen/jsonapi
update cty
2020-02-21 20:24:44 +01:00
# github.com/tencentcloud/tencentcloud-sdk-go v3.0.82+incompatible
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
update cty
2020-02-21 20:24:44 +01:00
github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common
github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common/errors
github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common/http
github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common/profile
github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/tag/v20180813
# github.com/tencentyun/cos-go-sdk-v5 v0.0.0-20190808065407-f07404cefc8c
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
update cty
2020-02-21 20:24:44 +01:00
github.com/tencentyun/cos-go-sdk-v5
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/tmc/grpc-websocket-proxy v0.0.0-20171017195756-830351dc03c6
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
# github.com/ugorji/go v0.0.0-20180813092308-00b869d2f4a5
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/ugorji/go/codec
vendor: github.com/hashicorp/go-getter@v1.1.0 go get github.com/hashicorp/go-getter@v1.1.0 go mod tidy go mod vendor
2019-02-21 09:52:47 +01:00
# github.com/ulikunitz/xz v0.5.5
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/ulikunitz/xz
update cty
2020-02-21 20:24:44 +01:00
github.com/ulikunitz/xz/internal/hash
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/ulikunitz/xz/internal/xlog
github.com/ulikunitz/xz/lzma
udpate go.mod and vendor
2018-11-29 21:01:47 +01:00
# github.com/vmihailenco/msgpack v4.0.1+incompatible
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/vmihailenco/msgpack
github.com/vmihailenco/msgpack/codes
vendor: github.com/xanzy/ssh-agent@v0.2.1
2019-02-22 15:22:13 +01:00
# github.com/xanzy/ssh-agent v0.2.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/xanzy/ssh-agent
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# github.com/xiang90/probing v0.0.0-20160813154853-07dd2e8dfe18
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
# github.com/xlab/treeprint v0.0.0-20161029104018-1d6e34225557
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/xlab/treeprint
vendor: go get github.com/zclconf/go-cty@v1.4.0 This fixes several bugs: - `substr("abc", 0, 0)` would previously return `"abc"`, despite the length argument being `0`. This has been changed to return an empty string when length is zero. - `ceil(1/0)` and `floor(1/0)` would previously return a large integer value, rather than infinity. This has been fixed.
2020-04-09 20:18:55 +02:00
# github.com/zclconf/go-cty v1.4.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/zclconf/go-cty/cty
github.com/zclconf/go-cty/cty/convert
github.com/zclconf/go-cty/cty/function
github.com/zclconf/go-cty/cty/function/stdlib
update cty
2020-02-21 20:24:44 +01:00
github.com/zclconf/go-cty/cty/gocty
github.com/zclconf/go-cty/cty/json
github.com/zclconf/go-cty/cty/msgpack
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
github.com/zclconf/go-cty/cty/set
vendor: upgrade go-cty-yaml dependency Fixes #22223
2019-07-30 18:27:49 +02:00
# github.com/zclconf/go-cty-yaml v1.0.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: go get github.com/zclconf/go-cty-yaml@v0.1.0 This module contains a YAML parser and encoder tailored to cty, though we are mostly interested in it for its YAMLEncode and YAMLDecode cty functions, which we can make available in Terraform.
2019-05-26 18:30:39 +02:00
github.com/zclconf/go-cty-yaml
vendor: Bump go-getter to 1.4.0
2019-09-09 14:04:58 +02:00
# go.opencensus.io v0.22.0
update cty
2020-02-21 20:24:44 +01:00
go.opencensus.io
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
go.opencensus.io/internal
update cty
2020-02-21 20:24:44 +01:00
go.opencensus.io/internal/tagencoding
go.opencensus.io/metric/metricdata
go.opencensus.io/metric/metricproducer
go.opencensus.io/plugin/ochttp
modules: update Azure deps to latest The dependencies here are dated and are causing conflicts with the ACME provider, namely the version of the top-level autorest package. This explicitly updates the Azure SDK and autorest packages, with the separately versioned sub-packages being added automatically.
2019-07-30 00:19:40 +02:00
go.opencensus.io/plugin/ochttp/propagation/b3
update cty
2020-02-21 20:24:44 +01:00
go.opencensus.io/resource
vendor: Bump go-azure-helpers to 0.7.0
2019-08-20 10:32:02 +02:00
go.opencensus.io/stats
update cty
2020-02-21 20:24:44 +01:00
go.opencensus.io/stats/internal
vendor: Bump go-azure-helpers to 0.7.0
2019-08-20 10:32:02 +02:00
go.opencensus.io/stats/view
go.opencensus.io/tag
update cty
2020-02-21 20:24:44 +01:00
go.opencensus.io/trace
go.opencensus.io/trace/internal
command/format: fix indentation also run go mod tidy
2018-10-10 18:56:21 +02:00
go.opencensus.io/trace/propagation
update cty
2020-02-21 20:24:44 +01:00
go.opencensus.io/trace/tracestate
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
# go.uber.org/atomic v1.3.2
## explicit
# go.uber.org/multierr v1.1.0
## explicit
# go.uber.org/zap v1.9.1
## explicit
Update dependencies
2020-04-25 08:41:54 +02:00
# golang.org/x/crypto v0.0.0-20191202143827-86a70503ff7e
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
golang.org/x/crypto/bcrypt
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/crypto/blowfish
golang.org/x/crypto/cast5
Update dependencies
2020-04-25 08:41:54 +02:00
golang.org/x/crypto/chacha20
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
golang.org/x/crypto/curve25519
golang.org/x/crypto/ed25519
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/crypto/ed25519/internal/edwards25519
golang.org/x/crypto/internal/subtle
golang.org/x/crypto/md4
golang.org/x/crypto/openpgp
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
golang.org/x/crypto/openpgp/armor
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/crypto/openpgp/elgamal
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
golang.org/x/crypto/openpgp/errors
golang.org/x/crypto/openpgp/packet
golang.org/x/crypto/openpgp/s2k
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/crypto/pkcs12
backend/azurerm: upgrading the SDK / support for proxies (#19414) * vendor updates - updating to v21.3.0 of github.com/Azure/azure-sdk-for-go - updating to v10.15.4 of github.com/Azure/go-autorest - vendoring github.com/hashicorp/go-azure-helpers @ 0.1.1 * backend/azurerm: refactoring to use the new auth package - refactoring the backend to use a shared client via the new auth package - adding tests covering both Service Principal and Access Key auth - support for authenticating using a proxy - rewriting the backend documentation to include examples of both authentication types * switching to use the build-in logging function * documenting it's also possible to retrieve the access key from an env var
2018-11-21 22:06:03 +01:00
golang.org/x/crypto/pkcs12/internal/rc2
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/crypto/poly1305
golang.org/x/crypto/ssh
golang.org/x/crypto/ssh/agent
golang.org/x/crypto/ssh/knownhosts
vendor: go get golang.org/x/mod We'll be using this for its directory hashing algorithm, as used in go.sum in Go modules, and applying it also to Terraform provider packages.
2020-03-27 23:32:01 +01:00
# golang.org/x/mod v0.2.0
## explicit
golang.org/x/mod/sumdb/dirhash
deps: github.com/aws/aws-sdk-go@v1.30.12 [master] (#24745) * update github.com/aws/aws-sdk-go to v1.30.9 * deps: github.com/aws/aws-sdk-go@v1.30.12 Reference: https://github.com/hashicorp/terraform/issues/24710 Reference: https://github.com/hashicorp/terraform/issues/24741 Changes: ``` NOTES: * backend/s3: Region validation now automatically supports the new `af-south-1` (Africa (Cape Town)) region. For AWS operations to work in the new region, the region must be explicitly enabled as outlined in the [AWS Documentation](https://docs.aws.amazon.com/general/latest/gr/rande-manage.html#rande-manage-enable). When the region is not enabled, the Terraform S3 Backend will return errors during credential validation (e.g. `error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid`). ENHANCEMENTS: * backend/s3: Support automatic region validation for `af-south-1` ``` Updated via: ```console $ go get github.com/aws/aws-sdk-go@v1.30.12 $ go mod tidy $ go mod vendor ``` Output from acceptance testing: ```console $ TF_ACC=1 go test -v ./backend/remote-state/s3 | grep '^--- ' --- PASS: TestBackend_impl (0.00s) --- PASS: TestBackendConfig (1.68s) --- PASS: TestBackendConfig_invalidKey (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyLength (0.00s) --- PASS: TestBackendConfig_invalidSSECustomerKeyEncoding (0.00s) --- PASS: TestBackendConfig_conflictingEncryptionSchema (0.00s) --- PASS: TestBackend (15.07s) --- PASS: TestBackendLocked (26.40s) --- PASS: TestBackendSSECustomerKey (16.99s) --- PASS: TestBackendExtraPaths (12.05s) --- PASS: TestBackendPrefixInWorkspace (5.55s) --- PASS: TestKeyEnv (45.07s) --- PASS: TestRemoteClient_impl (0.00s) --- PASS: TestRemoteClient (5.39s) --- PASS: TestRemoteClientLocks (14.30s) --- PASS: TestForceUnlock (20.08s) --- PASS: TestRemoteClient_clientMD5 (16.43s) --- PASS: TestRemoteClient_stateChecksum (24.58s) ``` Co-authored-by: Nicola Senno <nicola.senno@workday.com>
2020-04-24 18:20:04 +02:00
# golang.org/x/net v0.0.0-20200202094626-16171245cfb2
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
golang.org/x/net/context
golang.org/x/net/context/ctxhttp
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/net/html
golang.org/x/net/html/atom
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
golang.org/x/net/html/charset
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/net/http/httpguts
vendor: google.golang.org/grpc@v1.18.0 go get google.golang.org/grpc@v1.18.0 go mod tidy go mod vendor
2019-02-20 19:51:33 +01:00
golang.org/x/net/http2
golang.org/x/net/http2/hpack
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/net/idna
golang.org/x/net/internal/timeseries
golang.org/x/net/trace
vendor: Bump go-getter to 1.4.0
2019-09-09 14:04:58 +02:00
# golang.org/x/oauth2 v0.0.0-20190604053449-0f29369cfe45
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
golang.org/x/oauth2
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/oauth2/google
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
golang.org/x/oauth2/internal
golang.org/x/oauth2/jws
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/oauth2/jwt
Update dependencies
2020-04-25 08:41:54 +02:00
# golang.org/x/sys v0.0.0-20191128015809-6d18c012aee9
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
golang.org/x/sys/cpu
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/sys/unix
golang.org/x/sys/windows
go get github.com/hashicorp/hcl2@master This corrects a bug in the HCL 2 scanner where a $ or % symbol would cause incorrect tokenization if appearing immediately before a " . This also includes some updates to Go extension libraries that the HCL update brings in. Some of these changes update to support Unicode 11, but only when compiling with Go 1.13, so we won't see the effect of these changes until we start building Terraform with Go 1.13.
2019-05-03 23:09:08 +02:00
# golang.org/x/text v0.3.2
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
golang.org/x/text/encoding
golang.org/x/text/encoding/charmap
golang.org/x/text/encoding/htmlindex
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
golang.org/x/text/encoding/internal
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/text/encoding/internal/identifier
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
golang.org/x/text/encoding/japanese
golang.org/x/text/encoding/korean
golang.org/x/text/encoding/simplifiedchinese
golang.org/x/text/encoding/traditionalchinese
golang.org/x/text/encoding/unicode
vendor: cloud.google.com/go@v0.36.0 go get cloud.google.com/go@v0.36.0 go mod tidy go mod vendor
2019-02-20 19:57:56 +01:00
golang.org/x/text/internal/language
golang.org/x/text/internal/language/compact
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/text/internal/tag
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
golang.org/x/text/internal/utf8internal
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/text/language
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
golang.org/x/text/runes
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/text/secure/bidirule
golang.org/x/text/transform
golang.org/x/text/unicode/bidi
golang.org/x/text/unicode/norm
gomod: update `go-tfe`
2019-04-08 11:13:14 +02:00
# golang.org/x/time v0.0.0-20190308202827-9d24e82272b4
depencies: update `go-tfe`
2018-11-13 11:17:39 +01:00
golang.org/x/time/rate
Update dependencies
2020-04-25 08:41:54 +02:00
# golang.org/x/tools v0.0.0-20191203134012-c197fd4bf371
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
Version tools per Go convention under tools.go
2019-10-17 22:17:23 +02:00
golang.org/x/tools/cmd/cover
golang.org/x/tools/cmd/stringer
golang.org/x/tools/cover
golang.org/x/tools/go/gcexportdata
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/tools/go/internal/gcimporter
Version tools per Go convention under tools.go
2019-10-17 22:17:23 +02:00
golang.org/x/tools/go/internal/packagesdriver
update cty
2020-02-21 20:24:44 +01:00
golang.org/x/tools/go/packages
golang.org/x/tools/internal/fastwalk
Version tools per Go convention under tools.go
2019-10-17 22:17:23 +02:00
golang.org/x/tools/internal/gopathwalk
golang.org/x/tools/internal/semver
vendor: go get golang.org/x/mod We'll be using this for its directory hashing algorithm, as used in go.sum in Go modules, and applying it also to Terraform provider packages.
2020-03-27 23:32:01 +01:00
golang.org/x/tools/internal/span
vendor: Bump go-getter to 1.4.0
2019-09-09 14:04:58 +02:00
# google.golang.org/api v0.9.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/api/gensupport
google.golang.org/api/googleapi
google.golang.org/api/googleapi/internal/uritemplates
google.golang.org/api/googleapi/transport
google.golang.org/api/internal
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
google.golang.org/api/iterator
google.golang.org/api/option
google.golang.org/api/storage/v1
google.golang.org/api/transport/http
command/format: fix indentation also run go mod tidy
2018-10-10 18:56:21 +02:00
google.golang.org/api/transport/http/internal/propagation
vendor: Bump go-getter to 1.4.0
2019-09-09 14:04:58 +02:00
# google.golang.org/appengine v1.6.1
command/format: fix indentation also run go mod tidy
2018-10-10 18:56:21 +02:00
google.golang.org/appengine
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
google.golang.org/appengine/datastore
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/appengine/datastore/internal/cloudkey
google.golang.org/appengine/datastore/internal/cloudpb
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
google.golang.org/appengine/internal
command/format: fix indentation also run go mod tidy
2018-10-10 18:56:21 +02:00
google.golang.org/appengine/internal/app_identity
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
google.golang.org/appengine/internal/base
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/appengine/internal/datastore
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
google.golang.org/appengine/internal/log
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/appengine/internal/modules
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
google.golang.org/appengine/internal/remote_api
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/appengine/internal/urlfetch
google.golang.org/appengine/urlfetch
vendor: Bump go-getter to 1.4.0
2019-09-09 14:04:58 +02:00
# google.golang.org/genproto v0.0.0-20190819201941-24fa4b261c55
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/genproto/googleapis/api/annotations
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
google.golang.org/genproto/googleapis/iam/v1
go mod tidy & go mod vendor
2019-10-11 23:41:27 +02:00
google.golang.org/genproto/googleapis/rpc/code
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/genproto/googleapis/rpc/status
vendor: Bump go-getter to 1.4.0
2019-09-09 14:04:58 +02:00
google.golang.org/genproto/googleapis/type/expr
# google.golang.org/grpc v1.21.1
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
google.golang.org/grpc
cli: format/state refactor for new state format format/state now requires provider schemas to properly format output state. command/show has been modified to pass a context to format.State.
2018-09-24 18:30:39 +02:00
google.golang.org/grpc/balancer
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/grpc/balancer/base
cli: format/state refactor for new state format format/state now requires provider schemas to properly format output state. command/show has been modified to pass a context to format.State.
2018-09-24 18:30:39 +02:00
google.golang.org/grpc/balancer/roundrobin
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/grpc/binarylog/grpc_binarylog_v1
google.golang.org/grpc/codes
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
google.golang.org/grpc/connectivity
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/grpc/credentials
google.golang.org/grpc/credentials/internal
cli: format/state refactor for new state format format/state now requires provider schemas to properly format output state. command/show has been modified to pass a context to format.State.
2018-09-24 18:30:39 +02:00
google.golang.org/grpc/encoding
google.golang.org/grpc/encoding/proto
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/grpc/grpclog
google.golang.org/grpc/health
google.golang.org/grpc/health/grpc_health_v1
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
google.golang.org/grpc/internal
cli: format/state refactor for new state format format/state now requires provider schemas to properly format output state. command/show has been modified to pass a context to format.State.
2018-09-24 18:30:39 +02:00
google.golang.org/grpc/internal/backoff
vendor: Bump go-getter to 1.4.0
2019-09-09 14:04:58 +02:00
google.golang.org/grpc/internal/balancerload
vendor: google.golang.org/grpc@v1.18.0 go get google.golang.org/grpc@v1.18.0 go mod tidy go mod vendor
2019-02-20 19:51:33 +01:00
google.golang.org/grpc/internal/binarylog
cli: format/state refactor for new state format format/state now requires provider schemas to properly format output state. command/show has been modified to pass a context to format.State.
2018-09-24 18:30:39 +02:00
google.golang.org/grpc/internal/channelz
google.golang.org/grpc/internal/envconfig
google.golang.org/grpc/internal/grpcrand
vendor: google.golang.org/grpc@v1.18.0 go get google.golang.org/grpc@v1.18.0 go mod tidy go mod vendor
2019-02-20 19:51:33 +01:00
google.golang.org/grpc/internal/grpcsync
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/grpc/internal/syscall
cli: format/state refactor for new state format format/state now requires provider schemas to properly format output state. command/show has been modified to pass a context to format.State.
2018-09-24 18:30:39 +02:00
google.golang.org/grpc/internal/transport
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/grpc/keepalive
google.golang.org/grpc/metadata
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
google.golang.org/grpc/naming
google.golang.org/grpc/peer
cli: format/state refactor for new state format format/state now requires provider schemas to properly format output state. command/show has been modified to pass a context to format.State.
2018-09-24 18:30:39 +02:00
google.golang.org/grpc/resolver
google.golang.org/grpc/resolver/dns
google.golang.org/grpc/resolver/passthrough
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
google.golang.org/grpc/stats
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/grpc/status
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
google.golang.org/grpc/tap
update cty
2020-02-21 20:24:44 +01:00
google.golang.org/grpc/test/bufconn
Add tablestore config to store state lock
2019-04-11 01:11:10 +02:00
# gopkg.in/ini.v1 v1.42.0
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
Add tablestore config to store state lock
2019-04-11 01:11:10 +02:00
gopkg.in/ini.v1
Update dependencies
2020-04-25 08:41:54 +02:00
# gopkg.in/yaml.v2 v2.2.7
build: Use Go 1.14 This implies some notable changes that will have a visible impact to end-users of official Terraform releases: - Terraform is no longer compatible with MacOS 10.10 Yosemite, and requires at least 10.11 El Capitan. (Relatedly, Go 1.14 is planned to be the last release to support El Capitan, so while that remains supported for now, it's notable that Terraform 0.13 is likely to be the last major release of Terraform supporting it, with 0.14 likely to further require MacOS 10.12 Sierra.) - Terraform is no longer compatible with FreeBSD 10.x, which has reached end-of-life. Terraform now requires FreeBSD 11.2 or later. - Terraform now supports TLS 1.3 when it makes connections to remote services such as backends and module registries. Although TLS 1.3 is backward-compatible in principle, some legacy systems reportedly work incorrectly when attempting to negotiate it. (This change does not affect outgoing requests made by provider plugins, though they will see a similar change in behavior once built with Go 1.13 or later.) - Ed25519 certificates are now supported for TLS 1.2 and 1.3 connections. - On UNIX systems where "use-vc" is set in resolv.conf, TCP will now be used for DNS resolution. This is unlikely to cause issues in practice because a system set up in this way can presumably already reach its nameservers over TCP (or else other applications would misbehave), but could potentially lead to lookup failures in unusual situations where a system only runs Terraform, has historically had "use-vc" in its configuration, but yet is blocked from reaching its configured nameservers over TCP. - Some parts of Terraform now support Unicode 12.0 when working with strings. However, notably the Terraform Language itself continues to use the text segmentation tables from Unicode 9.0, which means it lacks up-to-date support for recognizing modern emoji combining forms as single characters. (We may wish to upgrade the text segmentation tables to Unicode 12.0 tables in a later commit, to restore consistency.) This also includes some changes to the contents of "vendor", and particularly to the format of vendor/modules.txt, per the changes to vendoring in the Go 1.14 toolchain. This new syntax is activated by the specification of "go 1.14" in the go.mod file. Finally, the exact format of error messages from the net/http library has changed since Go 1.12, and so a couple of our tests needed updates to their expected error messages to match that.
2020-03-04 03:49:56 +01:00
## explicit
vendor: update to latest github.com/zclconf/go-cty This includes a bugfix to the cty/msgpack package to ensure correct decoding of unknown and null values. This also includes updates to cty's dependencies.
2018-08-27 20:26:52 +02:00
gopkg.in/yaml.v2