6 Commits (654acb7ddda17f0cd504f2362aaba043cc5c91bc)

Author	SHA1	Message	Date
Martin Atkins	6291c20358	plugin: Register v5 plugins only if present ... Previously we would construct both provisioner and the provider objects if either callback was set, but this is incorrect because a plugin should actually set only one of these at a time, depending on what kind of plugin it is.	8 years ago
James Bardin	de11eed345	serve the new version 5 grpc plugins ... Use the new go-plugin version negotiation to server th appropriate plugin type when the client requests protocol version 5.	8 years ago
Mitchell Hashimoto	700c74bdd0	plugin: bump protocol version ... We changed the type of InstanceState.Meta and this will break pre-existing plugins. They simply have to recompile to work.	9 years ago
Mitchell Hashimoto	96884ec42d	plugin: bump the protocol version due to Provisioner change	9 years ago
Mitchell Hashimoto	b3124e16ca	plugin: bump protocol version ... This is necessary since the TypeUnknown HIL handling in helper/schema makes providers compiled WITHOUT TypeUnknown incompatible with the way core handles unknown values.	10 years ago
Mitchell Hashimoto	84214437b3	Use hashicorp/go-plugin for plugin system ... This replaces this plugin system with the extracted hashicorp/go-plugin library. This doesn't introduce any new features such as binary flattening but opens us up to that a lot more easily and removes a lot of code from TF in favor of the upstream lib. This will introduce a protocol change that will cause all existing plugins to have to be recompiled to work properly. There is no actual API changes so they just have to recompile, but it is technically backwards incompatible.	10 years ago