Help improve the Packer plugin experience

Hello Packer Community,

The Packer team is working to improve the external plugin management experience for Packer and would like to get your feedback.

If you are a user working with packer init, packer plugins install, or some other process for downloading and installing external plugins from a remote location (e.g GitHub, company repository) we want to hear from you.

The proliferation of external plugins has introduced confusion around the loading of plugins and we want to fix that in our next Packer release.

To help share with you what we are thinking, we’ve created Issue #12668 on the Packer GitHub issue tracker with a few proposals for solving some of the installation issues reported to us by practitioners. The proposal aims to solve the issue around discovering plugins installed by Packer or, installed manually, outside of Packer for practitioner usage.

If you have thought to yourself “this plugin stuff needs some work”, “how do I run this plugin?” or “the packer commands work but it would be great if…” please drop your comments on the thread or send us an email to to schedule a one-on-one session with us.

We thank you in advance for your support and continued use of Packer. We look forward to working with you in improving the Packer plugin experience.

1 Like