The HashiCorp Packer Plugin Repository, What’s init?
summary
Packer 1.7 ships a GitHub-backed Packer Plugin Repository and the packer init command that automatically downloads plugin binaries defined in an ACL-only required_plugins block; the release includes an SDK (v0.1) and an SDK migrator tool because the plugin protocol moves from API v4 to v5.0, a breaking change. Multicomponent plugins (example: docker combining builder, import/push/save/tag post-processors) install and run during demo builds, and bundled plugins (≈92) are slated to split into separate repos by 1.8.
AI-written summary · about
chapters (11)
- 0:00Introduction to Packer
- 1:49Evolution of Packer
- 8:54Plugin bundling challenges
- 10:42Packer plugin repository vision
- 13:11Maintainer tools and SDK
- 18:55Practitioner workflow with Packer
- 24:38Demo of Packer init
- 25:40Demo of plugin aliasing
- 28:35Demo of plugin upgrades
- 30:01Future of Packer plugins
- 31:43Call to action and Q&A
related talks
31mForget Rebuilding, Install Plugins at Runtime
32mAccelerating Collaborative Plugin Development
26mBackstage Plugin Development: Tales from the Trenches
18mThe Path to Modern Infrastructure Automation [Abridged]
23mBuild plugins using Pluggy
27mBuilding an Internal Developer Platform with Backstage Plugins
33mBuilding Automated Pipelines for Infrastructure Code with Terraform and Packer
34mPanel: Building a Healthy Backstage Plugins Ecosystem
