mirror of
https://github.com/hashicorp/packer.git
synced 2026-06-09 00:32:09 -04:00
266c4d99d2
With the changes coming up for 1.11.0, we update the Packer configuration docs so they describe the one way to load plugins, and the two environment variables which can be set to change this behaviour.
11 lines
764 B
Text
11 lines
764 B
Text
Upon initialization of Packer, all the installed plugins will be automatically discovered.
|
|
|
|
Packer plugins must be located under the `plugins` sub-directory under Packer's main config directory
|
|
[PACKER_CONFIG_DIR](/packer/docs/configure#packer-s-config-directory).
|
|
If `PACKER_CONFIG_DIR` is either unset or empty, a default value of `$HOME/.config/packer/plugins` on UNIX,
|
|
or `%APPDATA%\packer.d\plugins` for Windows, will be used.
|
|
|
|
If the `PACKER_PLUGIN_PATH` environment variable is set, it will be used instead of `PACKER_CONFIG_DIR/plugins`.
|
|
|
|
-> **Note:** Prior to Packer 1.11 the `PACKER_PLUGIN_PATH` environment variable supported values containing
|
|
multiple directories. Starting with Packer 1.11 and later this variable only supports a single directory.
|