Martin Atkins a1e29ae290 plugin/discovery: use go-version instead of semver ... The semver library we were using doesn't have support for a "pessimistic constraint" where e.g. the user wants to accept only minor or patch version upgrades. This is important for providers since users will generally want to pin their dependencies to not inadvertantly accept breaking changes. So here we switch to hashicorp's home-grown go-version library, which has the ~> constraint operator for this sort of constraint. Given how much the old version object was already intruding into the interface and creating dependency noise in callers, this also now wraps the "raw" go-version objects in package-local structs, thus keeping the details encapsulated and allowing callers to deal just with this package's own types.		2017-06-09 14:03:59 -07:00
..
test-fixtures	plugin/discovery: find plugins in a given set of directories	2017-06-09 14:03:59 -07:00
find_test.go	plugin/discovery: find plugins in a given set of directories	2017-06-09 14:03:59 -07:00
find.go	plugin/discovery: use go-version instead of semver	2017-06-09 14:03:59 -07:00
meta_set_test.go	plugin/discovery: use go-version instead of semver	2017-06-09 14:03:59 -07:00
meta_set.go	plugin/discovery: use go-version instead of semver	2017-06-09 14:03:59 -07:00
meta_test.go	plugin/discovery: SHA256() method to get the hash of each plugin	2017-06-09 14:03:59 -07:00
meta.go	plugin/discovery: use go-version instead of semver	2017-06-09 14:03:59 -07:00
requirements.go	plugin/discovery: use go-version instead of semver	2017-06-09 14:03:59 -07:00
version_set_test.go	plugin/discovery: use go-version instead of semver	2017-06-09 14:03:59 -07:00
version_set.go	plugin/discovery: use go-version instead of semver	2017-06-09 14:03:59 -07:00
version.go	plugin/discovery: use go-version instead of semver	2017-06-09 14:03:59 -07:00