packer

HashiCorp Packer 1.2.0

We are proud to announce the release of HashiCorp Packer 1.2.0. This release includes several new features, improvements, bug fixes, and introduces a few backwards incompatibilities.

Download Now

Here are some highlights from Packer 1.2.0:

  • New builder: ncloud for building server images using the NAVER Cloud Platform.
  • New builder: oci-classic for building new custom images for use with Oracle Cloud Infrastructure Classic Compute.
  • New builder: scaleway - The Scaleway Packer builder is able to create new images for use with Scaleway BareMetal and Virtual cloud server.
  • Amazon authentication enhancements - The authentication logic for the Amazon builders has been reworked to be more configurable and return errors faster. See the updated documentation for more information.
  • SSH communicator now detects hanging connections - Dead connections should now be noticed and handled correctly.
  • VMWare builder more configurable - The VMWare builder now has finer-grained settings for virtual ports and hardware.

There are a couple of backwards incompatible changes to be aware of:

  • The amazon ssh_private_ip option has been removed - Instead, please use "ssh_interface": "private". A fixer has been written for this, which can be invoked with packer fix.
  • OpenStack extension support has been removed - To use OpenStack builder with the OpenStack Newton (Oct 2016) or earlier, we recommend you use Packer v1.1.2 or earlier.
  • Plugin API has changed - Existing external plugins will continue to work, but the multistep interface has changed, meaning slight changes must be made before compiling them against this version of Packer will succeed. Please see the multistep documentation for more information.

There are many other changes and improvements in this release. Please review the v1.2.0 changelog for a detailed list of changes.


Sign up for the latest HashiCorp news

By submitting this form, you acknowledge and agree that HashiCorp will process your personal information in accordance with the Privacy Policy.