From 9c20085ca9b4dafd048770cbd84c3c3662be367f Mon Sep 17 00:00:00 2001 From: Jeff Regan Date: Mon, 24 Jun 2019 15:27:14 -0700 Subject: [PATCH] Update goPluginGuidedExample.md --- docs/plugins/goPluginGuidedExample.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/plugins/goPluginGuidedExample.md b/docs/plugins/goPluginGuidedExample.md index 20a05ecdc..88ffefb95 100644 --- a/docs/plugins/goPluginGuidedExample.md +++ b/docs/plugins/goPluginGuidedExample.md @@ -160,13 +160,13 @@ dependency [skew]. On load failure * be sure to build the plugin with the same - version of Go (`go1.12`) on the same `$GOOS` - (`linux`) and `$GOARCH` (`amd64`) used to build + version of Go (_go1.12_) on the same `$GOOS` + (_linux_) and `$GOARCH` (_amd64_) used to build the kustomize being [used in this demo]. - * change the plugin's dependencies in `go.mod` to - match those used to build kustomize (check the - `go.mod` used in the tagged commit). + * change the plugin's dependencies in its `go.mod` + to match the versions used by kustomize (check + kustomize's `go.mod` used in its tagged commit). Lacking tools and metadata to allow this to be automated, there won't be a Go plugin ecosystem.