16 Commits (cef46ef953face71f52f4e900a0ea2132ebfae88)

Author	SHA1	Message	Date
James Bardin	6f54bfaa7c	send config during apply	7 years ago
Martin Atkins	53926ea581	plugin: Fix incorrect trace log message in provider Close ... Was incorrectly printing out "PlanResourceChange" instead of "Close".	7 years ago
James Bardin	924b97238f	Handle StateFuncs in provider shim ... Any state modifying functions can only be run once during the plan-apply cycle. When regenerating the Diff during ApplyResourceChange, strip out all StateFunc and CustomizeDiff functions from the schema. Thew NewExtra diff field was where config data that was modified by a StateFunc was stored, and needs to be maintained between plan and apply. During PlanResourceChange, store any NewExtra data from the Diff in the PlannedPrivate data, and re-insert the NewExtra data into the Diff generated during ApplyResourceChange.	8 years ago
Martin Atkins	4fe9632f09	plugin: Establish our current plugin protocol as version 5 ... The main significant change here is that the package name for the proto definition is "tfplugin5", which is important because this name is part of the wire protocol for references to types defined in our package. Along with that, we also move the generated package into "internal" to make it explicit that importing the generated Go package from elsewhere is not the right approach for externally-implemented SDKs, which should instead vendor the proto definition they are using and generate their own stubs to ensure that the wire protocol is the only hard dependency between Terraform Core and plugins. After this is merged, any provider binaries built against our helper/schema package will need to be rebuilt so that they use the new "tfplugin5" package name instead of "proto". In a future commit we will include more elaborate and organized documentation on how an external codebase might make use of our RPC interface definition to implement an SDK, but the primary concern here is to ensure we have the right wire package name before release.	8 years ago
James Bardin	3bdd3b2a6e	update plugin client with PrepareProviderConfig	8 years ago
James Bardin	3a0c2f1b67	close grpc TestListener	8 years ago
James Bardin	0d4d572c39	start work on helper/resource test fixtures ... The helper resource tests won't pass for now, as they use a terraform.MockProvider which can't be used in the schema.Provider shims.	8 years ago
James Bardin	a14fe7ae0c	missing diagnostics in pugin protocol ... Some call diagnostics were being missed	8 years ago
James Bardin	795161f615	update to start a new process for each plugin ... Modify the plugin factories to create a new plugin process for each individual plugin.	8 years ago
James Bardin	35b375d3ee	check responses for nil values ... While providers shouldn't return nil values, we need to protect against them. Always assign valid null cty values when the response contains a nil.	8 years ago
Martin Atkins	a7342de274	core: Properly handle no-op changes in plan ... Previously we just left these out of the plan altogether, but in the new plan types we intentionally include change information for every resource instance, even if no changes are actually planned, to allow alternative plan file viewers to show what isn't changing as well as what is.	8 years ago
Martin Atkins	5d744e6824	plugin: TRACE log for each GRPC-remoted plugin call	8 years ago
Martin Atkins	4bf19797f3	plugin: Fix deadlock in getSchema where mutex is never unlocked ... On the second call here this would fail to release the lock.	8 years ago
James Bardin	c07ce1cd4b	move conversion functions into separate package ... Managing which function need to be shared between the terraform plugin and the helper plugin without creating cycles was becoming difficult. Move all functions related to converting between terraform and proto type into plugin/convert.	8 years ago
James Bardin	b403023841	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
James Bardin	c1d4a63fae	GRPCProvider and GRPCProvisioner clients ... Here we add the GRPCProvisioner and GRPCProvider which implement the core provisioners.Interface and providers.Interface, and translate betweeen the core types and the grpc protocol.	8 years ago