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

Apply suggestions from code review 

Co-authored-by: Sylvia Moss <moss@hashicorp.com>
This commit is contained in:
Megan Marsh 2020-12-15 09:34:04 -08:00
parent 8650f7990c
commit 3fd8066a95
5 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
packer-plugin-sdk/communicator/config.go
View File

@ -24,7 +24,7 @@ import (
"golang.org/x/crypto/ssh/agent" "golang.org/x/crypto/ssh/agent"
) )
// Config is the common a builder uses to define and configure a Packer // Config is the common configuration a builder uses to define and configure a Packer
// communicator. Embed this struct in your builder config to implement // communicator. Embed this struct in your builder config to implement
// communicator support. // communicator support.
type Config struct { type Config struct {

2
packer-plugin-sdk/communicator/doc.go
View File

@ -5,6 +5,6 @@ Normally, a builder will want to implement StepConnect, which is smart enough
to then determine which kind of communicator, and therefore which kind of to then determine which kind of communicator, and therefore which kind of
substep, it should implement. substep, it should implement.
Various helper functions are also supplied. CommHost Various helper functions are also supplied.
*/ */
package communicator package communicator

2
packer-plugin-sdk/net/configure_port.go
View File

@ -1,4 +1,4 @@
// package net contains some helper wrapping functions for the http and net // Package net contains some helper wrapping functions for the http and net
// golang libraries that meet Packer-specific needs. // golang libraries that meet Packer-specific needs.
package net package net

2
packer-plugin-sdk/packer/doc.go
View File

@ -11,7 +11,7 @@ absolutely necessary.
Plugins will need to implement either the Builder, Provisioner, Plugins will need to implement either the Builder, Provisioner,
or Post-Processor interfaces, and will likely create an Artifact. The or Post-Processor interfaces, and will likely create an Artifact. The
Communicator must be implemented in the Builder and is then passed into the Communicator must be implemented in the Builder and then passed into the
Provisioners so they can use it communicate with the instance without needing Provisioners so they can use it communicate with the instance without needing
to know the connection details. to know the connection details.

2
packer-plugin-sdk/rpc/init.go
View File

@ -1,7 +1,7 @@
/* /*
Package rpc contains the implementation of the remote procedure call code that Package rpc contains the implementation of the remote procedure call code that
the Packer core uses to communicate with packer plugins. As a plugin maintainer, the Packer core uses to communicate with packer plugins. As a plugin maintainer,
You are unlikely to need to directly import or use this package, but it you are unlikely to need to directly import or use this package, but it
underpins the packer server that all plugins must implement. underpins the packer server that all plugins must implement.
*/ */
package rpc package rpc