5 Commits (d1e606eac8eb17fcb2d9d7b7efd7b40f2e2b6d01)

Author	SHA1	Message	Date
Martin Atkins	d1e606eac8	vendor: update go-cty, and some other dependencies ... The primary reason for this update is to get cty.PathSet.Equal, for more convenient deep comparisons using "cmp" in tests.	8 years ago
Martin Atkins	bed2566c76	vendor: update cty to v0.0.0-20180831220647-752f6a689f5e ... This includes a fix to UnknownAsNull to make it not crash when given a value that is _already_ null.	8 years ago
Martin Atkins	cc3c3863fb	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.	8 years ago
Martin Atkins	71865be05c	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.	8 years ago
Martin Atkins	ecca5f291e	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.	8 years ago