ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
terraform/go.mod

145 lines
8.9 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-25 01:13:05 +02:00
module github.com/hashicorp/terraform
require (
cloud.google.com/go v0.15.0
github.com/Azure/azure-sdk-for-go v10.3.0-beta+incompatible
github.com/Azure/go-autorest v8.3.1+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/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-25 01:13:05 +02: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 20:26:52 +02: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: 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-25 01:13:05 +02:00
github.com/apparentlymart/go-cidr v0.0.0-20170616213631-2bd8b58cf427
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 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-25 01:13:05 +02: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 20:26:52 +02:00
github.com/armon/go-metrics v0.0.0-20180917152333-f0300d1749da // indirect
github.com/armon/go-radix v0.0.0-20160115234725-4239b77079c7 // 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-25 01:13:05 +02:00
github.com/aws/aws-sdk-go v1.14.31
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/beevik/etree v0.0.0-20171015221209-af219c0c7ea1 // indirect
github.com/beorn7/perks v0.0.0-20180321164747-3a771d992973 // 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-25 01:13:05 +02: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 20:26:52 +02:00
github.com/boltdb/bolt v1.3.1 // indirect
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-25 01:13:05 +02: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 20:26:52 +02:00
github.com/chzyer/test v0.0.0-20180213035817-a1ea475d72b1 // indirect
github.com/cockroachdb/cmux v0.0.0-20170110192607-30d10be49292 // 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-25 01:13:05 +02:00
github.com/coreos/etcd v3.2.7+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/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: 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-25 01:13:05 +02:00
github.com/davecgh/go-spew v1.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/dgrijalva/jwt-go v0.0.0-20160617170158-f0777076321a // indirect
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-25 01:13:05 +02: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 20:26:52 +02: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-25 01:13:05 +02: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 20:26:52 +02:00
github.com/gogo/protobuf v0.0.0-20180821102207-98f6aa8b3bcf // indirect
github.com/golang/groupcache v0.0.0-20180513044358-24b0969c4cb7 // indirect
github.com/golang/mock v0.0.0-20180503014854-22bbf0ddf081
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: 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-25 01:13:05 +02:00
github.com/gophercloud/gophercloud v0.0.0-20170524130959-3027adb1ce72
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/gopherjs/gopherjs v0.0.0-20181004151105-1babbf986f6f // indirect
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-25 01:13:05 +02:00
github.com/hashicorp/consul v0.0.0-20171026175957-610f3c86a089
github.com/hashicorp/errwrap v0.0.0-20141028054710-7554cd9344ce
github.com/hashicorp/go-checkpoint v0.0.0-20171009173528-1545e56e46de
github.com/hashicorp/go-cleanhttp v0.0.0-20171130225243-06c9ea3a335b
github.com/hashicorp/go-getter v0.0.0-20180327010114-90bb99a48d86
github.com/hashicorp/go-hclog v0.0.0-20170716174523-b4e5765d1e5f
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-immutable-radix v1.0.0 // indirect
github.com/hashicorp/go-msgpack v0.0.0-20150518234257-fa3f63826f7c // 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-25 01:13:05 +02:00
github.com/hashicorp/go-multierror v0.0.0-20150916205742-d30f09973e19
github.com/hashicorp/go-plugin v0.0.0-20180125190438-e53f54cbf51e
github.com/hashicorp/go-retryablehttp v0.0.0-20160930035102-6e85be8fee1d
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 20:26:52 +02:00
github.com/hashicorp/go-safetemp v0.0.0-20180326211150-b1a1dbde6fdc // indirect
github.com/hashicorp/go-sockaddr v0.0.0-20180320115054-6d291a969b86 // indirect
github.com/hashicorp/go-uuid 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-25 01:13:05 +02:00
github.com/hashicorp/go-version v0.0.0-20180322230233-23480c066577
github.com/hashicorp/hcl v0.0.0-20170504190234-a4b07c25de5f
github.com/hashicorp/hcl2 v0.0.0-20180308163058-5f8ed954abd8
github.com/hashicorp/hil v0.0.0-20170627220502-fa9f258a9250
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 20:26:52 +02:00
github.com/hashicorp/memberlist v0.1.0 // indirect
github.com/hashicorp/serf v0.0.0-20160124182025-e4ec8cc423bb // 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-25 01:13:05 +02: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 20:26:52 +02:00
github.com/hashicorp/yamux v0.0.0-20160720233140-d1caa6c97c9f // indirect
github.com/jen20/awspolicyequivalence v0.0.0-20170831201602-3d48364a137a // indirect
github.com/jmespath/go-jmespath v0.0.0-20160803190731-bd40a432e4c7 // 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-25 01:13:05 +02: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 20:26:52 +02:00
github.com/jtolds/gls v4.2.1+incompatible // 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-25 01:13:05 +02:00
github.com/kardianos/osext v0.0.0-20160811001526-c2c54e542fb7
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 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-25 01:13:05 +02:00
github.com/lusis/go-artifactory v0.0.0-20160115162124-7e4ce345df82
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/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-25 01:13:05 +02: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 20:26:52 +02: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-25 01:13:05 +02:00
github.com/mattn/go-shellwords 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 20:26:52 +02:00
github.com/matttproud/golang_protobuf_extensions v1.0.1 // indirect
github.com/miekg/dns v1.0.13 // 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-25 01:13:05 +02: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
github.com/mitchellh/go-homedir v0.0.0-20161203194507-b8bc1bf76747
github.com/mitchellh/go-linereader v0.0.0-20141013185533-07bab5fdd958
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 v0.0.0-20170730050907-9a441910b168 // 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-25 01:13:05 +02:00
github.com/mitchellh/go-wordwrap v0.0.0-20150314170334-ad45545899c7
github.com/mitchellh/hashstructure v0.0.0-20160209213820-6b17d669fac5
github.com/mitchellh/mapstructure v0.0.0-20170307201123-53818660ed49
github.com/mitchellh/panicwrap v0.0.0-20161208170302-ba9e1a65e0f7
github.com/mitchellh/prefixedio v0.0.0-20151214002211-6e6954073784
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 20:26:52 +02:00
github.com/nu7hatch/gouuid v0.0.0-20131221200532-179d4d0c4d8d // indirect
github.com/oklog/run 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-25 01:13:05 +02: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 20:26:52 +02:00
github.com/pascaldekloe/goe v0.0.0-20180627143212-57f6aae5913c // indirect
github.com/pkg/errors v0.0.0-20170505043639-c605e284fe17 // indirect
github.com/pmezard/go-difflib 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-25 01:13:05 +02:00
github.com/posener/complete v0.0.0-20171219111128-6bee943216c8
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/prometheus/client_golang v0.9.0 // indirect
github.com/prometheus/client_model v0.0.0-20180712105110-5c3871d89910 // indirect
github.com/prometheus/common v0.0.0-20181015124227-bcb74de08d37 // indirect
github.com/prometheus/procfs v0.0.0-20181005140218-185b4288413d // indirect
github.com/satori/go.uuid v0.0.0-20160927100844-b061729afc07 // indirect
github.com/satori/uuid v0.0.0-20160927100844-b061729afc07 // indirect
github.com/sean-/seed v0.0.0-20170313163322-e2103e2c3529 // indirect
github.com/smartystreets/assertions v0.0.0-20180927180507-b2de0cb4f26d // indirect
github.com/smartystreets/goconvey v0.0.0-20180222194500-ef6db91d284a // 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-25 01:13:05 +02:00
github.com/spf13/afero v1.0.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
github.com/stretchr/testify v1.2.2 // indirect
github.com/terraform-providers/terraform-provider-aws v1.40.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-25 01:13:05 +02:00
github.com/terraform-providers/terraform-provider-openstack v0.0.0-20170616075611-4080a521c6ea
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/terraform-providers/terraform-provider-template v1.0.0 // indirect
github.com/terraform-providers/terraform-provider-tls v1.2.0 // indirect
github.com/ugorji/go v0.0.0-20180813092308-00b869d2f4a5 // indirect
github.com/ulikunitz/xz v0.5.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-25 01:13:05 +02:00
github.com/vmihailenco/msgpack v4.0.0+incompatible // indirect
github.com/xanzy/ssh-agent 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/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-25 01:13:05 +02:00
github.com/xlab/treeprint v0.0.0-20161029104018-1d6e34225557
vendor: upgrade go-cty to latest This includes the new PathSet type, which we'll use to represent the "requires replacement" set of attribute paths coming back from providers during planning.
2018-08-29 20:13:35 +02:00
github.com/zclconf/go-cty v0.0.0-20180829180805-c2393a5d54f2
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 v0.0.0-20180816225734-aabede6cba87
golang.org/x/net v0.0.0-20180826012351-8a410e7b638d
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-25 01:13:05 +02:00
golang.org/x/oauth2 v0.0.0-20170928010508-bb50c06baba3
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/sys v0.0.0-20170608164803-0b25a408a500 // indirect
golang.org/x/time v0.0.0-20180412165947-fbb02b2291d2 // 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-25 01:13:05 +02:00
google.golang.org/api v0.0.0-20171005000305-7a7376eff6a5
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 v0.0.0-20171002232614-f676e0f3ac63 // 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-25 01:13:05 +02:00
google.golang.org/grpc v0.0.0-20170809211603-7657092a1303
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/vmihailenco/msgpack.v2 v2.9.1 // indirect
gopkg.in/yaml.v2 v2.0.0-20170407172122-cd8b52f8269e // 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-25 01:13:05 +02:00
)