72c1912b60
This add : * discovery of `packer-plugin-*` binaries from the known folders and ask them to describe themselves * tests For testing: in go we create a bash script that in turn calls back to Go. I could not make the tests to work on windows and then would like to postpone testing this for when we know more about the finite layout of this feature. That is mainly: how things are going to work with init, versioning and such. |
||
|---|---|---|
| .. | ||
| acctest | ||
| adapter | ||
| bootcommand | ||
| chroot | ||
| common | ||
| communicator | ||
| filelock | ||
| guestexec | ||
| iochan | ||
| json | ||
| multistep | ||
| net | ||
| packer | ||
| packerbuilderdata | ||
| pathing | ||
| plugin | ||
| random | ||
| retry | ||
| rpc | ||
| sdk-internals/communicator | ||
| shell | ||
| shell-local | ||
| shutdowncommand | ||
| template | ||
| test-fixtures | ||
| tmp | ||
| useragent | ||
| uuid | ||
| version | ||
| Makefile | ||
| README.md | ||
| go.mod.example | ||
README.md
Packer Plugin SDK
This SDK enables building Packer plugins. This allows Packer's users to use both the officially-supported builders, provisioners, and post-processors, and custom in-house solutions.
Packer itself is a tool for building identical machine images for multiple platforms from a single source configuration. You can find more about Packer on its website and its GitHub repository.
Packer CLI Compatibility
Packer v1.7.0 or later is needed for this SDK. Versions of Packer prior to that release are still compatible with third-party plugins, but the plugins should use the plugin tooling from inside earlier versions of Packer to ensure complete API compatibility.
Go Compatibility
The Packer Plugin SDK is built in Go, and uses the support policy of Go as its support policy. The two latest major releases of Go are supported by the SDK.
Currently, that means Go 1.14 or later must be used when building a provider with the SDK.
Getting Started
See the Extending Packer docs for a guided tour of plugin development.
Documentation
See the Extending Packer section on the Packer website.
Packer Scope (Plugins VS Core)
Packer Core
- acts as an RPC client
- interacts with the user
- parses (HCL/JSON) configuration
- manages build as whole, asks plugin(s) to manage the image lifecycle and modify the image being built.
- discovers plugin(s) and their versions per configuration
- manages plugin lifecycles (i.e. spins up & tears down plugin process)
- passes relevant parts of parsed (valid JSON/HCL) and interpolated configuration to plugin(s)
Packer Provider (via this SDK)
- acts as RPC server
- executes any domain-specific logic based on received parsed configuration. For builders this includes managing the vm lifecycle on a give hypervisor or cloud; for provisioners this involves calling the operation on the remote instance.
- tests domain-specific logic via provided acceptance test framework
- provides Core with template validation, artifact information, and information about whether the plugin process succeeded or failed.
Migrating to SDK from built-in SDK
Migrating to the standalone SDK v1 is covered on the Plugin SDK section of the website.
Versioning
The Packer Plugin SDK is a Go module versioned using semantic versioning.