From 468feee607050cd356215aaafeb87a22ce624af9 Mon Sep 17 00:00:00 2001 From: Megan Marsh Date: Thu, 12 Oct 2017 14:14:07 -0700 Subject: [PATCH] fix docs for 5205 --- website/source/docs/extending/plugins.html.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/source/docs/extending/plugins.html.md b/website/source/docs/extending/plugins.html.md index ad0b4a44c..180a6e8ea 100644 --- a/website/source/docs/extending/plugins.html.md +++ b/website/source/docs/extending/plugins.html.md @@ -124,7 +124,7 @@ There are two steps involved in creating a plugin: plugin, implement the `packer.Builder` interface. 2. Serve the interface by calling the appropriate plugin serving method in your - main method. In the case of a builder, this is `plugin.ServeBuilder`. + main method. In the case of a builder, this is `plugin.RegisterBuilder`. A basic example is shown below. In this example, assume the `Builder` struct implements the `packer.Builder` interface: @@ -138,11 +138,11 @@ import ( type Builder struct{} func main() { - plugin.ServeBuilder(new(Builder)) + plugin.RegisterBuilder(new(Builder)) } ``` -**That's it!** `plugin.ServeBuilder` handles all the nitty gritty of +**That's it!** `plugin.RegisterBuilder` handles all the nitty gritty of communicating with Packer core and serving your builder over RPC. It can't get much easier than that.