iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

plugins.html.md: Update docs example to match code example. 

`plugin.RegisterBuilder` doesn't seem to exist. Instead the [example](https://github.com/hashicorp/packer/blob/master/plugin/example/main.go) and the tests use `plugin.Server`.
This commit is contained in:
Graham King 2019-07-24 20:46:37 -07:00 committed by GitHub
parent c4806e2fe4
commit 5d470ae731
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/source/docs/extending/plugins.html.md
View File

@ -130,8 +130,7 @@ There are two steps involved in creating a plugin:
plugin, implement the `packer.Builder` interface. plugin, implement the `packer.Builder` interface.
2. Serve the interface by calling the appropriate plugin serving method in 2. Serve the interface by calling the appropriate plugin serving method in
your main method. In the case of a builder, this is your main method.
`plugin.RegisterBuilder`.
A basic example is shown below. In this example, assume the `Builder` struct A basic example is shown below. In this example, assume the `Builder` struct
implements the `packer.Builder` interface: implements the `packer.Builder` interface:
@ -145,11 +144,16 @@ import (
type Builder struct{} type Builder struct{}
func main() { func main() {
plugin.RegisterBuilder(new(Builder)) server, err := plugin.Server()
if err != nil {
panic(err)
}
server.RegisterBuilder(new(Builder))
server.Serve()
} }
``` ```
**That's it!** `plugin.RegisterBuilder` handles all the nitty gritty of **That's it!** `plugin.Server` handles all the nitty gritty of
communicating with Packer core and serving your builder over RPC. It can't get communicating with Packer core and serving your builder over RPC. It can't get
much easier than that. much easier than that.