|
|
|
|
@ -68,13 +68,12 @@ Directory](/docs/configure#packer-s-plugin-directory).
|
|
|
|
|
|
|
|
|
|
### Implicit plugin requirements
|
|
|
|
|
|
|
|
|
|
When running `packer init`, if Packer logs a warning that tells you to add a
|
|
|
|
|
`packer.required_plugin` block to your config file, this is because this plugin
|
|
|
|
|
was moved out of the Packer binary and you should consider using that block.
|
|
|
|
|
This is part of a set of breaking changes made to decouple Packer releases from
|
|
|
|
|
a Plugin release. These suggestion are manually added each time we move a plugin
|
|
|
|
|
out of the Packer core. These should happen only starting from version `1.8` of
|
|
|
|
|
Packer.
|
|
|
|
|
Starting from Version `1.8` many plugins will move out from Packer core. To make
|
|
|
|
|
the transition easier we will tag many core plugins as moved out. If one of the
|
|
|
|
|
components of a moved out plugin is used in a config file, then it is implied
|
|
|
|
|
that this plugin is required. This is part of a set of breaking changes made to
|
|
|
|
|
decouple Packer releases from a Plugin release. These suggestion are manually
|
|
|
|
|
added each time we move a plugin out of the Packer core.
|
|
|
|
|
|
|
|
|
|
See [Installing Plugins](/docs/plugins#installing-plugins) for more information on how plugin installation works.
|
|
|
|
|
## Options
|
|
|
|
|
|