Skip to content

Releases: hashicorp/packer-plugin-vagrant

v1.1.5

12 Sep 15:21
Compare
Choose a tag to compare

What's Changed

Bug fixes🧑‍🔧 🐞

  • Update box create step to wait for a successful create operation before allowing the HCP Vagrant post-processor to continue by @chrisroberts in #129

Doc improvements 📚

  • Add vagrant-registry component to integration docs by @nywilken in #125

Other Changes

  • [COMPLIANCE] Add Copyright and License Headers by @hashicorp-copywrite in #123

Full Changelog: v1.1.4...v1.1.5

v1.1.4

18 Jun 17:34
Compare
Choose a tag to compare

What's Changed

Exciting New Features 🎉

Bug fixes🧑‍🔧 🐞

Doc improvements 📚

  • fix broken link in template section of vagrant builder doc by @VishnuJin in #111

Other Changes

New Contributors

Full Changelog: v1.1.2...v1.1.4

v1.1.2

17 Jan 19:17
Compare
Choose a tag to compare

What's Changed

Exciting New Features 🎉

  • Treat 201 Created response codes as successful requests by @jerrykan in #99

Bug fixes🧑‍🔧 🐞

Other Changes

New Contributors

Full Changelog: v1.1.1...v1.1.2

v1.1.1

18 Oct 15:43
Compare
Choose a tag to compare

Notes:

When using the template attribute the template variables available to you are {{ .BoxName }}, {{ .SyncedFolder }}, and {{.InsertKey}}, which correspond to the Packer options box_name, synced_folder, and insert_key. Alternatively, the template variable {{.DefaultTemplate}} is now available for use if you wish to extend the default generated template.

# Vagrantfile.tpl
{{ .DefaultTemplate }}

Vagrant.configure("2") do |config|
  config.vm.provider "virtualbox" do |vb|
    vb.customize ['modifyvm', :id, '--nested-hw-virt', 'on']
  end
end

What's Changed

Exciting New Features 🎉

  • Expose default vagrantfile template as a template variable {{.DefaultTemplate}} by @dangra in #59

New Contributors

Full Changelog: v1.1.0...v1.1.1

v1.1.0

10 Oct 19:05
Compare
Choose a tag to compare

Notes

Adds architecture support to the vagrant and the vagrant-cloud post-processors.

Vagrant post-processor

Introduces a new configuration option to the vagrant post-processor:

  • architecture - string

This is an optional value that will automatically default to the host platform's architecture. The architecture value will be included within the metadata.json file of the generated box.

Vagrant Cloud post-processor

Updates the API calls to use Vagrant Cloud's v2 API. The v2 API supports architecture metadata for providers and the post-processor has been updated to include architecture information. New configurations options added:

  • architecture - string
  • default_architecture - string

By default, the post-processor will read the architecture information from the metadata.json within the box. If the box metadata does not include architecture information, or the architecture needs to be overridden for some reason, it can be defined using the architecture configuration option.

The default_architecture option is used for backwards compatibility support (more information available in the Vagrant Cloud docs). If the architecture value set in default_architecture matches the architecture of the box then it will be marked as the default architecture on Vagrant Cloud.

What's Changed

Exciting New Features 🎉

  • Support many files in Vagrant box for libvirt by @LeConTesteur in #48
  • Add Architecture attributed support to post-processors by @chrisroberts in #101
  • Add support for the file builder. This was just done to make it easier for testing generated boxes by @chrisroberts in #101

Doc improvements 📚

Other Changes

New Contributors

Full Changelog: v1.0.3...v1.1.0

v1.0.3

10 Jun 13:39
Compare
Choose a tag to compare

Note

The v0.3.0 release of the Packer plugin SDK contains the following changes which will may affect the downloading of external files such as ISOs used by this plugin.

  • Default timeouts have been added to the GitGetter, HgGetter, S3Getter, and GcsGetter getters to mitigate against resource exhaustion when calling out to external command line applications.
  • Support for the X-Terraform-Get header has been disabled to mitigate against protocol switching, endless redirect, and configuration bypass abuse of custom HTTP response header processing.
  • The default go-getter client has been updated to prevent arbitrary host access via go-getter's path traversal, symlink processing, and command injection flaws.

See Security Options for more details.

What's Changed

Bug fixes🧑‍🔧 🐞

  • Bump packer-plugin-sdk to v0.3.0 to address vulnerabilities in go-getter, as described in
    HCSEC-2022-13.

Other Changes

  • Update action to support transferred issues by @nywilken in #53

Full Changelog: v1.0.2...v1.0.3

v1.0.2

19 May 19:15
Compare
Choose a tag to compare

Note

This release contains the latest golang.org/x/crypto/ssh module which implements client authentication support for signature algorithms based on SHA-2 for use with existing RSA keys. Previously, a client would fail to authenticate with RSA keys to servers that reject signature algorithms based on SHA-1.

What's Changed

Bug fixes🧑‍🔧 🐞

  • Bump packer-plugin-sdk to address legacy SSH key algorithms in SSH communicator

Other Changes

  • goreleaser: auto-generate changelog file by @azr in #47
  • Update release signing configuration by @nywilken in #49

New Contributors

Full Changelog: v1.0.1...v1.0.2

v1.0.1

22 Dec 12:58
@azr azr
2b22e86
Compare
Choose a tag to compare

What's Changed

Exciting New Features 🎉

  • [vagrant-cloud post-processor] box checksums by @dweomer in #32

Doc improvements 📚

Other Changes

  • Validate plugin from the packer-sdc plugin-validate command by @azr in #37

New Contributors

Full Changelog: v1.0.0...v1.0.1

v1.0.0

15 Jun 04:00
Compare
Choose a tag to compare
cut v1.0.0 release

v0.0.3

21 Apr 19:18
Compare
Choose a tag to compare
refactor docs