Hello Packer Community,
The Packer team is excited to announce the release of Packer 1.11.0-alpha for testing.
This release changes how Packer plugins are installed and loaded by recognizing development binaries as supported plugin installations. Please note that these are breaking changes, which may impact your workflows, as we’ve adopted a stricter approach to plugin installation/loading and removed some of the flexibility around plugins.
Please refer to our Blog post for more information on that subject. As always, the CHANGELOG is also a reference for what’s included in this release.
Notable Changes:
- Support for loading legacy single-component plugins, such as packer-builder-happycloud or packer-provsioner-happycloud, has been removed from Packer.
- Support for loading plugin binaries following the naming convention of packer-plugin-name has been dropped. Packer will now only load plugins stored under PACKER_PLUGIN_PATH using the expected namespaced directory and CHECKSUM files. This change drops support for loading plugin binaries in Packer’s executable directory or a template’s current working directory.
- Packer now considers development binaries when evaluating plugin version constraints. This work allows users to use binaries with versions reported as “x.y.z-dev” with the Packer required_plugins block.
As always, thank you for your continued support and contributions.
The Packer Team.