IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2024-12-26 17:01:04 -06:00
Code Issues Packages Projects Releases Wiki Activity
8e2f2d0b0f
opentofu/go.mod

147 lines
8.5 KiB
Modula-2
Raw Normal View History

vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
module github.com/hashicorp/terraform
require (
cloud.google.com/go v0.15.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 15:06:03 -06:00
github.com/Azure/azure-sdk-for-go v21.3.0+incompatible
github.com/Azure/go-autorest v10.15.4+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 13:26:52 -05:00
github.com/Azure/go-ntlmssp v0.0.0-20170803034930-c92175d54006 // indirect
github.com/ChrisTrenkamp/goxpath v0.0.0-20170625215350-4fe035839290 // indirect
github.com/Unknwon/com v0.0.0-20151008135407-28b053d5a292 // indirect
github.com/abdullin/seq v0.0.0-20160510034733-d5467c17e7af // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/agext/levenshtein v1.2.1
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 13:26:52 -05:00
github.com/agl/ed25519 v0.0.0-20150830182803-278e1ec8e8a6 // indirect
github.com/antchfx/xpath v0.0.0-20170728053731-b5c552e1acbd // indirect
github.com/antchfx/xquery v0.0.0-20170730121040-eb8c3c172607 // indirect
vendor: github.com/apparentlymart/go-cidr@v1.0.0
2019-02-12 03:32:10 -06:00
github.com/apparentlymart/go-cidr 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 13:26:52 -05:00
github.com/apparentlymart/go-dump v0.0.0-20180507223929-23540a00eaa3
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/armon/circbuf v0.0.0-20150827004946-bbbad097214e
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 13:26:52 -05:00
github.com/armon/go-metrics v0.0.0-20180917152333-f0300d1749da // indirect
github.com/armon/go-radix v0.0.0-20160115234725-4239b77079c7 // indirect
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-13 19:30:43 -06:00
github.com/aws/aws-sdk-go v1.16.4
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 13:26:52 -05:00
github.com/beevik/etree v0.0.0-20171015221209-af219c0c7ea1 // indirect
github.com/bgentry/go-netrc v0.0.0-20140422174119-9fd32a8b3d3d // indirect
github.com/bgentry/speakeasy v0.0.0-20161015143505-675b82c74c0e // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/blang/semver v0.0.0-20170202183821-4a1e882c79dc
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 13:26:52 -05:00
github.com/boltdb/bolt v1.3.1 // indirect
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-13 19:30:43 -06:00
github.com/boombuler/barcode v1.0.0 // indirect
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 13:26:52 -05:00
github.com/chzyer/logex v1.1.10 // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/chzyer/readline v0.0.0-20161106042343-c914be64f07d
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 13:26:52 -05:00
github.com/chzyer/test v0.0.0-20180213035817-a1ea475d72b1 // indirect
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-16 19:12:35 -05:00
github.com/coreos/bbolt v1.3.0 // indirect
github.com/coreos/etcd v3.3.10+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 13:26:52 -05:00
github.com/coreos/go-semver v0.2.0 // indirect
github.com/coreos/go-systemd v0.0.0-20181012123002-c6f51f82210d // indirect
github.com/coreos/pkg v0.0.0-20180928190104-399ea9e2e55f // indirect
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 13:19:23 -05:00
github.com/davecgh/go-spew v1.1.1
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 13:26:52 -05:00
github.com/dnaeon/go-vcr v0.0.0-20180920040454-5637cf3d8a31 // indirect
github.com/dylanmei/iso8601 v0.1.0 // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/dylanmei/winrmtest v0.0.0-20170819153634-c2fbb09e6c08
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 13:26:52 -05:00
github.com/ghodss/yaml v1.0.0 // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/go-test/deep v1.0.1
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 13:26:52 -05:00
github.com/gogo/protobuf v0.0.0-20180821102207-98f6aa8b3bcf // indirect
github.com/golang/groupcache v0.0.0-20180513044358-24b0969c4cb7 // indirect
update go mock
2018-12-10 16:15:53 -06:00
github.com/golang/mock 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 13:26:52 -05:00
github.com/golang/protobuf v1.2.0
github.com/google/btree v0.0.0-20180813153112-4030bb1f1f0c // indirect
github.com/google/go-cmp v0.2.0
github.com/googleapis/gax-go v0.0.0-20161107002406-da06d194a00e // indirect
vendor: github.com/terraform-providers/terraform-provider-openstack@v1.15.0
2019-02-08 04:59:06 -06:00
github.com/gophercloud/gophercloud v0.0.0-20190208042652-bc37892e1968
github.com/gophercloud/utils v0.0.0-20190128072930-fbb6ab446f01 // indirect
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 13:26:52 -05:00
github.com/gopherjs/gopherjs v0.0.0-20181004151105-1babbf986f6f // indirect
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-16 19:12:35 -05:00
github.com/gorilla/websocket v1.4.0 // indirect
github.com/grpc-ecosystem/go-grpc-middleware v1.0.0 // indirect
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 13:26:52 -05:00
github.com/grpc-ecosystem/go-grpc-prometheus v1.2.0 // indirect
github.com/grpc-ecosystem/grpc-gateway v1.5.1 // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/hashicorp/consul v0.0.0-20171026175957-610f3c86a089
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 13:19:23 -05:00
github.com/hashicorp/errwrap v1.0.0
vendor: github.com/hashicorp/go-azure-helpers@0.3.2
2019-02-01 02:40:50 -06:00
github.com/hashicorp/go-azure-helpers v0.0.0-20190129193224-166dfd221bb2
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/hashicorp/go-checkpoint v0.0.0-20171009173528-1545e56e46de
depencies: update `go-tfe`
2018-11-13 04:17:39 -06:00
github.com/hashicorp/go-cleanhttp v0.5.0
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/hashicorp/go-getter v0.0.0-20180327010114-90bb99a48d86
update go-plugin and hclog
2018-10-02 15:03:07 -05:00
github.com/hashicorp/go-hclog v0.0.0-20181001195459-61d530d6c27f
github.com/hashicorp/go-immutable-radix v0.0.0-20180129170900-7f3cd4390caa // indirect
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 13:26:52 -05:00
github.com/hashicorp/go-msgpack v0.0.0-20150518234257-fa3f63826f7c // indirect
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 13:19:23 -05:00
github.com/hashicorp/go-multierror v1.0.0
vendor: github.com/hashicorp/go-plugin@latest
2019-01-29 12:41:20 -06:00
github.com/hashicorp/go-plugin v0.0.0-20190129155509-362c99b11937
go-mod: update dependencies
2019-01-15 08:52:37 -06:00
github.com/hashicorp/go-retryablehttp v0.5.1
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/hashicorp/go-rootcerts v0.0.0-20160503143440-6bb64b370b90
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 13:26:52 -05:00
github.com/hashicorp/go-safetemp v0.0.0-20180326211150-b1a1dbde6fdc // indirect
github.com/hashicorp/go-sockaddr v0.0.0-20180320115054-6d291a969b86 // indirect
go-mod: update dependencies
2019-01-15 08:52:37 -06:00
github.com/hashicorp/go-tfe v0.3.7
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 13:26:52 -05:00
github.com/hashicorp/go-uuid v1.0.0
go-mod: update go-version
2018-12-13 11:35:23 -06:00
github.com/hashicorp/go-version v1.0.0
update go-plugin and hclog
2018-10-02 15:03:07 -05:00
github.com/hashicorp/golang-lru v0.5.0 // indirect
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-08 17:51:53 -06:00
github.com/hashicorp/hcl v0.0.0-20170504190234-a4b07c25de5f
vendor: Upgrade both HCL2 and cty The cty change here fixes a panic situation when cty.Path.Apply is given a null value, making it now correctly return an error. However, the HCL2 change includes an alternative to cty.Path.Apply that uses HCL-level rules rather than cty-level rules, so the result behaves like an HCL expression would. Most uses of cty.Path.Apply ought to use hcl.ApplyPath instead, to ensure that the behavior is consistent with what users expect in the main language.
2019-01-30 19:34:10 -06:00
github.com/hashicorp/hcl2 v0.0.0-20190130225218-89dbc5eb3d9e
Switch to Go 1.11.5 An earlier commit incorrectly updated some versions in go.mod without also updating the vendor tree, so this also rolls those back to where they used to be so that we can roll them forward carefully and make sure the tests actually pass. (If we just accept these new versions as specified the tests do not pass, so some work is required to fix those regressions.)
2019-01-30 18:59:34 -06:00
github.com/hashicorp/hil v0.0.0-20170627220502-fa9f258a9250
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/hashicorp/logutils v0.0.0-20150609070431-0dc08b1671f3
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 13:26:52 -05:00
github.com/hashicorp/memberlist v0.1.0 // indirect
github.com/hashicorp/serf v0.0.0-20160124182025-e4ec8cc423bb // indirect
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-08 17:51:53 -06:00
github.com/hashicorp/terraform-config-inspect v0.0.0-20190208230122-b0707673339c
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/hashicorp/vault v0.0.0-20161029210149-9a60bf2a50e4
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 13:26:52 -05:00
github.com/jen20/awspolicyequivalence v0.0.0-20170831201602-3d48364a137a // indirect
github.com/jonboulle/clockwork v0.1.0 // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/joyent/triton-go v0.0.0-20180313100802-d8f9c0314926
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 13:26:52 -05:00
github.com/jtolds/gls v4.2.1+incompatible // indirect
vendor: Fix dependency on github.com/kardianos/osext In 98c8ac0862e3 I merged a change to the vendored code for this module but didn't spot that it didn't also update the dependency metadata to match. Here we just catch up the metadata to match the vendored version, with no change to the vendored code itself.
2018-12-05 19:07:46 -06:00
github.com/kardianos/osext v0.0.0-20170510131534-ae77be60afb1
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 13:26:52 -05:00
github.com/keybase/go-crypto v0.0.0-20161004153544-93f5b35093ba // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/lusis/go-artifactory v0.0.0-20160115162124-7e4ce345df82
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 15:06:03 -06:00
github.com/marstr/guid v1.1.0 // indirect
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 13:26:52 -05:00
github.com/masterzen/azure-sdk-for-go v0.0.0-20161014135628-ee4f0065d00c // indirect
github.com/masterzen/simplexml v0.0.0-20160608183007-4572e39b1ab9 // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/masterzen/winrm v0.0.0-20180224160350-7e40f93ae939
github.com/mattn/go-colorable v0.0.0-20160220075935-9cbef7c35391
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 13:26:52 -05:00
github.com/mattn/go-isatty v0.0.0-20161123143637-30a891c33c7c // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/mattn/go-shellwords v1.0.1
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 11:30:39 -05:00
github.com/miekg/dns v1.0.8 // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/mitchellh/cli v0.0.0-20171129193617-33edc47170b5
github.com/mitchellh/colorstring v0.0.0-20150917214807-8631ce90f286
github.com/mitchellh/copystructure v0.0.0-20170525013902-d23ffcb85de3
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 15:23:30 -06:00
github.com/mitchellh/go-homedir v1.0.0
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/mitchellh/go-linereader v0.0.0-20141013185533-07bab5fdd958
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 13:19:23 -05:00
github.com/mitchellh/go-wordwrap v1.0.0
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/mitchellh/hashstructure v0.0.0-20160209213820-6b17d669fac5
Switch to Go 1.11.5 An earlier commit incorrectly updated some versions in go.mod without also updating the vendor tree, so this also rolls those back to where they used to be so that we can roll them forward carefully and make sure the tests actually pass. (If we just accept these new versions as specified the tests do not pass, so some work is required to fix those regressions.)
2019-01-30 18:59:34 -06:00
github.com/mitchellh/mapstructure v0.0.0-20170307201123-53818660ed49
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/mitchellh/panicwrap v0.0.0-20161208170302-ba9e1a65e0f7
github.com/mitchellh/prefixedio v0.0.0-20151214002211-6e6954073784
Switch to Go 1.11.5 An earlier commit incorrectly updated some versions in go.mod without also updating the vendor tree, so this also rolls those back to where they used to be so that we can roll them forward carefully and make sure the tests actually pass. (If we just accept these new versions as specified the tests do not pass, so some work is required to fix those regressions.)
2019-01-30 18:59:34 -06:00
github.com/mitchellh/reflectwalk v0.0.0-20170726202117-63d60e9d0dbc
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 13:26:52 -05:00
github.com/nu7hatch/gouuid v0.0.0-20131221200532-179d4d0c4d8d // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/packer-community/winrmcp v0.0.0-20180102160824-81144009af58
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 13:26:52 -05:00
github.com/pascaldekloe/goe v0.0.0-20180627143212-57f6aae5913c // indirect
github.com/pkg/errors v0.0.0-20170505043639-c605e284fe17 // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/posener/complete v0.0.0-20171219111128-6bee943216c8
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-13 19:30:43 -06:00
github.com/pquerna/otp v1.0.0 // indirect
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 13:26:52 -05:00
github.com/satori/go.uuid v0.0.0-20160927100844-b061729afc07 // indirect
github.com/sean-/seed v0.0.0-20170313163322-e2103e2c3529 // indirect
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-16 19:12:35 -05:00
github.com/sirupsen/logrus v1.1.1 // indirect
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 13:26:52 -05:00
github.com/smartystreets/assertions v0.0.0-20180927180507-b2de0cb4f26d // indirect
github.com/smartystreets/goconvey v0.0.0-20180222194500-ef6db91d284a // indirect
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-16 19:12:35 -05:00
github.com/soheilhy/cmux v0.1.4 // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/spf13/afero v1.0.2
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-13 19:30:43 -06:00
github.com/terraform-providers/terraform-provider-aws v1.52.0
vendor: github.com/terraform-providers/terraform-provider-openstack@v1.15.0
2019-02-08 04:59:06 -06:00
github.com/terraform-providers/terraform-provider-openstack v1.15.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 13:26:52 -05:00
github.com/terraform-providers/terraform-provider-template v1.0.0 // indirect
github.com/terraform-providers/terraform-provider-tls v1.2.0 // indirect
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-16 19:12:35 -05:00
github.com/tmc/grpc-websocket-proxy v0.0.0-20171017195756-830351dc03c6 // indirect
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 13:26:52 -05:00
github.com/ugorji/go v0.0.0-20180813092308-00b869d2f4a5 // indirect
github.com/ulikunitz/xz v0.5.4 // indirect
udpate go.mod and vendor
2018-11-29 14:01:47 -06:00
github.com/vmihailenco/msgpack v4.0.1+incompatible // indirect
vendor: upgrade ssh-agent dependency
2018-10-18 17:38:22 -05:00
github.com/xanzy/ssh-agent v0.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 13:26:52 -05:00
github.com/xiang90/probing v0.0.0-20160813154853-07dd2e8dfe18 // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
github.com/xlab/treeprint v0.0.0-20161029104018-1d6e34225557
vendor: go get github.com/zclconf/go-cty@master This fixes a bug in the TestConformance function that was generating false positives when given two object types with the same number of attributes but not identical attribute names.
2019-02-01 16:15:04 -06:00
github.com/zclconf/go-cty v0.0.0-20190201220620-4ca19710f056
command/format: fix indentation also run go mod tidy
2018-10-10 11:56:21 -05:00
go.opencensus.io v0.17.0 // indirect
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-16 19:12:35 -05:00
go.uber.org/atomic v1.3.2 // indirect
go.uber.org/multierr v1.1.0 // indirect
go.uber.org/zap v1.9.1 // indirect
udpate go.mod and vendor
2018-11-29 14:01:47 -06:00
golang.org/x/crypto v0.0.0-20181127143415-eb0de9b17e85
golang.org/x/net v0.0.0-20181129055619-fae4c4e3ad76
command/format: fix indentation also run go mod tidy
2018-10-10 11:56:21 -05:00
golang.org/x/oauth2 v0.0.0-20181003184128-c57b0facaced
vendor: update google.golang.org/api
2018-10-15 12:01:09 -05:00
google.golang.org/api v0.0.0-20181015145326-625cd1887957
udpate go.mod and vendor
2018-11-29 14:01:47 -06:00
google.golang.org/appengine v1.3.0 // indirect
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 11:30:39 -05:00
google.golang.org/grpc v1.14.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 13:26:52 -05:00
gopkg.in/vmihailenco/msgpack.v2 v2.9.1 // indirect
vendor: Fix incorrect checksums
2019-01-29 08:36:35 -06:00
labix.org/v2/mgo v0.0.0-20140701140051-000000000287 // indirect
launchpad.net/gocheck v0.0.0-20140225173054-000000000087 // indirect
vendor: switch to Go modules govendor's lack of understanding of transitive versions was making it hell to figure out some dependency hell between etcd, grpc, and protobuf. After fighting with it for a few hours, I decided to give Go 1.11rc2 a try since previous experiments had been promising on the 1.11 tree in master. The dependencies all worked out first time when managed using the Go Modules code, and so we'll run with this now to continue to make progress though we may wish to back out of this nearer to release and return to govendor for a while until other projects have caught up. However, since this commit includes a vendor directory produced using Go Modules it doesn't actually _require_ Go 1.11 to build, and instead requires it only to make further changes to the selected versions in the vendor dir. Go 1.10's vendoring support will still find the modules in their expected locations within the vendor dir.
2018-08-24 18:13:05 -05:00
)
Reference in New Issue Copy Permalink