mirror of
https://github.com/hashicorp/packer.git
synced 2026-09-21 15:31:41 -04:00
b3341164cf
* feat: extract `/plugins` Co-authored-by: Zachary Shilton <[email protected]> Co-authored-by: Adrien Delorme <[email protected]>
14 lines
713 B
Plaintext
14 lines
713 B
Plaintext
## How Plugins Work
|
|
|
|
Packer plugins are completely separate, standalone applications that the core
|
|
of Packer starts and communicates with. Even the components that ship with the
|
|
Packer core (core builders, provisioners, and post-processors) are implemented
|
|
in a similar way and run as though they are standalone plugins.
|
|
|
|
These plugin applications aren't meant to be run manually. Instead, Packer core
|
|
launches and communicates with them. The next time you run a Packer build,
|
|
look at your process list and you should see a handful of `packer-` prefixed
|
|
applications running. One of those applications is the core; the rest are
|
|
plugins -- one plugin process is launched for each component used in a Packer
|
|
build.
|