terraform/plugin/mock_proto/generate.go

//go:generate bash ./generate.sh

package mock_tfplugin5
build: Run "go generate" in modules mode It seems that all of the tools we run here are now sufficiently modules-aware to run without problems in modules mode, and indeed running _not_ in modules mode was causing problems with locating packages in mockgen. 2019-02-06 19:51:39 +01:00			`//go:generate bash ./generate.sh`
generate mocks for some of the grpc interfaces These will allow easier testing of the grpc endpoints in isolation. Mocks are generated for ProviderClient, ProvisionerClient, Provisioner_ProvisionResourceClient, and Provisioner_ProvisionResourceServer using `go generate` 2018-08-08 22:54:40 +02:00
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. 2018-11-19 18:39:16 +01:00			`package mock_tfplugin5`