12 Commits (ccf19fbf5e2b61ba62efd1ac47a3a3fd3917d494)

Author	SHA1	Message	Date
Martin Atkins	88551181d5	plugin: Fix tests ... An earlier change made the tests not compile here. We now need to use the legacyPluginMap function, since pluginMap has now been replaced with helpers to produce new-style plugin _sets_.	8 years ago
James Bardin	ff7d51a9b4	update tests to match new test func signature	8 years ago
Mitchell Hashimoto	045ddf3695	plugin: implement ResourceProvider.Stop	10 years ago
Mitchell Hashimoto	60140b28f4	Revert "Merge pull request #9536 from hashicorp/f-provider-stop" ... This reverts commit c3a4cff133, reversing changes made to 791a02e6e4. This change requires plugin recompilation and we should hold off until a minor release for that.	10 years ago
Mitchell Hashimoto	43b5818b55	plugin: implement ResourceProvider.Stop	10 years ago
Clint	a9aaf44a87	fix make issues (supersedes #7868) (#7876) ... * Fixing the make error or invalid data type for errorf and printf * fix make errors	10 years ago
Martin Atkins	0e0e3d73af	core: New ResourceProvider methods for data resources ... This is a breaking change to the ResourceProvider interface that adds the new operations relating to data sources. DataSources, ValidateDataSource, ReadDataDiff and ReadDataApply are the data source equivalents of Resources, Validate, Diff and Apply (respectively) for managed resources. The diff/apply model seems at first glance a rather strange workflow for read-only resources, but implementing data resources in this way allows them to fit cleanly into the standard plan/apply lifecycle in cases where the configuration contains computed arguments and thus the read must be deferred until apply time. Along with breaking the interface, we also fix up the plugin client/server and helper/schema implementations of it, which are all of the callers used when provider plugins use helper/schema. This would be a breaking change for any provider plugin that directly implements the provider interface, but no known plugins do this and it is not recommended. At the helper/schema layer the implementer sees ReadDataApply as a "Read", as opposed to "Create" or "Update" as in the managed resource Apply implementation. The planning mechanics are handled entirely within helper/schema, so that complexity is hidden from the provider implementation itself.	10 years ago
Mitchell Hashimoto	ba84485c87	plugin: tests for ImportState	10 years ago
Mitchell Hashimoto	498e23162d	plugin: implement new interface methods	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
Mitchell Hashimoto	04858e1a15	plugin: Client/Server uses new RPC client/server	12 years ago
Mitchell Hashimoto	951b7b18eb	plugin: can execute plugins and communicate that way	12 years ago