diff --git a/command/init.go b/command/init.go index 2b8cdd7595a..9e5b82f04ba 100644 --- a/command/init.go +++ b/command/init.go @@ -169,7 +169,7 @@ Options: version, if there is a new higher one. Note that this still takes into consideration the version constraint of the config. - -force Forces installation of plugins, even if already + -force Forces reinstallation of plugins, even if already installed. ` diff --git a/command/plugins_install.go b/command/plugins_install.go index b467eee5f4d..4d8434a2780 100644 --- a/command/plugins_install.go +++ b/command/plugins_install.go @@ -54,7 +54,7 @@ Options: not try to download it from a remote location, and instead install the binary in the Packer plugins path. This option cannot be specified with a version constraint. - - force: forces installation of a plugin, even if it is already there. + - force: forces reinstallation of plugins, even if already installed. ` return strings.TrimSpace(helpText) diff --git a/website/content/docs/plugins/install-plugins.mdx b/website/content/docs/plugins/install-plugins.mdx index 1c2b602823f..b2d97975216 100644 --- a/website/content/docs/plugins/install-plugins.mdx +++ b/website/content/docs/plugins/install-plugins.mdx @@ -227,5 +227,15 @@ If you have a `required_plugins` for the plugin you're manually installing, make it respects the constraints described in the [Plugin loading workflow](#plugin-loading-workflow) section, otherwise Packer will not be able to load it. +Starting with v1.10.0 of Packer, you can also use `packer plugins install` with the +`--path` flag to install a plugin from a binary, following the layout that is required to +work with `required_plugins` block. + +```shell +packer plugins install --path github.com/hashicorp/vagrant +``` + +-> packer plugins install --path only works with release versions of plugins. +