Skip to content

Releases: hashicorp/packer-plugin-sdk

v0.5.4

18 Jun 16:32
Compare
Choose a tag to compare

Upgrade notes

Upgrading to this release may fail until you've applied one of the fixes documented in #187 (comment). Consumers of the Packer plugin SDK require a replace directive within their plugin's go module file to point to a compatible version of go-cty.

The replace directive subject to change in future releases can be applied by running the packer-sdc fix sub-command to apply the replace directive to your plugin with a recommended version of the go-cty fork.

Plugins already working with Packer Plugin SDK v0.5.2 are advised to apply the updated SDK fixes by re-running packer-sdc fix against the plugin's root directory.

What's Changed

Doc improvements 📚

Other Changes

New Contributors

Full Changelog: v0.5.3...v0.5.4

v0.5.3

16 Apr 14:28
Compare
Choose a tag to compare

Upgrade notes

Upgrading to this release may fail until you've applied one of the fixes documented in #187 (comment). Consumers of the Packer plugin SDK require a replace directive within their plugin's go module file to point to a compatible version of go-cty.

The replace directive subject to change in future releases can be applied by running the packer-sdc fix sub-command to apply the replace directive to your plugin with a recommended version of the go-cty fork.

Plugins already working with Packer Plugin SDK v0.5.2 are advised to apply the updated SDK fixes by re-running packer-sdc fix against the plugin's root directory.

What's Changed

Exciting New Features 🎉

Other Changes

Full Changelog: v0.5.2...v0.5.3

v0.5.2

28 Nov 11:15
Compare
Choose a tag to compare

Upgrade Notes

Upgrading to this release may fail until you've applied one of the fixes documented in packer-plugin-sdk#187. Consumers of the Packer plugin SDK require a replace directive within their plugin's go module file to point to a compatible version of go-cty. The replace directive subject to change in future releases can be applied by running the packer-sdc fix sub-command to apply the replace directive to your plugin with a recommended version of the go-cty fork.

Plugins already working with Packer Plugin SDK v0.5.1 are advised to apply the updated SDK fixes by re-running packer-sdc fix against the plugin's root directory. The updated SDK fixes will bump the supported version of the go-cty fork to v1.13.3, which is required for working with hcl/v2 version 2.17.0 and above.

  • Bumped github.com/zclconf/go-cty to v1.13.1: to bring in the latest supported changes of zclconf/go-cty and hashicorp/hcl/v2 to the SDK.
  • Bumped github.com/hashicorp/hcl/v2 to v2.19.1: to bring in support for the latest HCL/v2 refinements builder and enhancements. Refinements are non-breaking changes but you may see some changed results in your unit test of operations involving unknown values.
  • Updated packer-sdc fix: to upgrade the replace version for github.com/nywilken/go-cty from v1.12.1 to v1.13.3.

What's Changed

Exciting New Features 🎉

  • Add capability to specify additional build args to be executed when running acceptance tests against builders by @lbajolet-hashicorp in #202
  • Bump supported version of go-cty to v1.13.3 by @nywilken in #215

Security Changes

Bug Fixes🧑‍🔧 🐞

  • Fix issue where packer-sdc mapstructure-to-hcl was incorrectly mixing underlying structs for types with similar mapstructure tags by @nywilken in #212
  • hcl2helper: preemptively panic on nil hcl spec by @lbajolet-hashicorp in #204

Other Changes

  • packer-sdc/struct-markdown: Allow packer-internal as project directory for testing purposes by @nywilken in #218

New Contributors

Full Changelog: v0.5.1...v0.5.2

v0.5.1

01 Aug 19:40
Compare
Choose a tag to compare

Upgrade Notes

This release is a fast follow to v0.5.0, which broke the installation of the packer-sdc command due to an invalid go.mod file. The v0.5.0 release has been retracted and should not be used. Consumers of the Packer Plugin SDK should update to v0.5.1. Upgrading to this release will fail until you've applied one of the fixes documented in packer-plugin-sdk#187. We ask that you carefully review this section for details on the released changes.

  • Retracted v0.5.0: the v0.5.0 SDK release was broken because of the replace statement for go-cty. #199
  • Gob supported compile time check: we added a Go compile time check to the SDK for validating that a plugins' version of github.com/zclconf/go-cty contains encoding/gob support for cty.Type and cty.Value. #189
  • Bumped the github.com/zclconf/go-cty to v1.12.1: to bring in the latest supported changes of zclconf/go-cty and hashicorp/hcl/v2 to the SDK. Consumers of the Packer plugin SDK now require a replace directive within their plugin's go module file to point to a compatible version of go-cty. The packer-sdc command has been updated to help apply these types of fixes. #197
  • Added a fix command to packer-sdc: to help with the manual intervention and future changes to the SDK, we've introduced a fix sub-command to apply the replace directive to your plugin with a recommended version of the go-cty fork. #190, #198

What's Changed

Bug fixes🧑‍🔧 🐞

Other Changes

Full Changelog: v0.5.0...v0.5.1

v0.5.0

28 Jul 17:13
Compare
Choose a tag to compare

Advisory ⚠️

This release breaks the installation of the packer-sdc command using go install github.com/hashicorp/packer-plugin-sdk/cmd/[email protected]. Please hold-off upgrading for now, as we work on a fix for this issue and re-release the SDK.

Apologies for the inconvenience.

Upgrade Notes

This release contains changes to the API that introduce compatibility constraints for zclconf/go-cty. Namely, the bundled version of go-cty used by the SDK is now provided via a fork to resolve the encoding/gob incompatibility issue introduced by the breaking change in zclconf/go-cty v1.11.0. Before upgrading we ask that you carefully review this section and refer to packer-plugin-sdk#187 for details on upgrading your plugin dependencies.

  • Gob supported compile time check: we added a Go compile time check to the SDK for validating that a plugins' version of github.com/zclconf/go-cty contains encoding/gob support for cty.Type and cty.Value. GH-189
  • Replaced github.com/zclconf/go-cty with a temporary fork: to avoid introducing a major breaking change to the plugin API, we've created a temporary fork of github.com/zclconf/go-cty containing support for gob encoding to use in place of the upstream go-cty package. Consumers of the Packer plugin SDK now require a replace directive within their plugin's go module file to point to a compatible version of go-cty. The packer-sdc command has been updated to help apply these types of fixes. GH-189
  • Added a fix command to packer-sdc: to help with the manual intervention and future changes to the SDK, we've introduced a fix sub-command to apply the replace directive to your plugin with a recommended version of the fork. GH-190

What's Changed

Breaking Changes 🛠

Exciting New Features 🎉

Bug fixes🧑‍🔧 🐞

Doc improvements 📚

  • Remove extra backticks from HTTP server documentation by @edigaryev in #191

Other Changes

  • GHA migration finalisation by @lbajolet-hashicorp in #172
  • SEC-090: Automated trusted workflow pinning (2023-04-21) by @hashicorp-tsccr in #175
  • [COMPLIANCE] Add Copyright and License Headers by @hashicorp-copywrite in #170 #182
  • Update pinned actions to latest trusted versions by @nywilken in #195

New Contributors

  • @hashicorp-tsccr made their first contribution in #175
  • @korli made their first contribution in #184
  • @edigaryev made their first contribution in #191

Full Changelog: v0.4.0...v0.5.0

v0.4.0

08 Mar 16:30
Compare
Choose a tag to compare

Notes

Previously the sub-command packer-sdc mapstructure-to-hcl would ignore duplicate fields in the generated HCL schema file, which sometimes resulted in configuration input attributes being removed from the schema. The command has been updated to error, as opposed to warn, when a duplicate possible conflicting mapstructure field is found to aid plugin developers. We've marked this release a minor release because the new behavior may be breaking to some plugin components. Any new reported conflicting input attributed should be rename or consolidated if possible. GH-164

What's Changed

Bug fixes🧑‍🔧 🐞

Doc improvements 📚

Other Changes

  • Remove ioutil in favour of io and os packages and exclude crypto/dsa … by @rossmaclean in #153
  • Replace circle-ci test with GitHub actions by @nywilken in #167

Full Changelog: v0.3.4...v0.4.0

v0.3.4

27 Jan 17:06
Compare
Choose a tag to compare

What's Changed

Bug fixes🧑‍🔧 🐞

Other Changes

Full Changelog: v0.3.3...v0.3.4

v0.3.3

26 Jan 22:20
Compare
Choose a tag to compare

What's Changed

Bug fixes🧑‍🔧 🐞

Doc improvements 📚

  • Update links used in embedded documentation partials by @nywilken in #151

Other Changes

  • [COMPLIANCE] Update MPL 2.0 LICENSE by @hashicorp-copywrite in #133
  • Update docs links by @sylviamoss in #138
  • [COMPLIANCE] Add Copyright and License Headers by @hashicorp-copywrite in #145
  • communicator: add note to docs on protocol/Windows by @lbajolet-hashicorp in #146
  • Fix some linting warnings. by @rossmaclean in #149

New Contributors

  • @hashicorp-copywrite made their first contribution in #133
  • @rossmaclean made their first contribution in #149

Full Changelog: v0.3.2...v0.3.3

v0.3.2

12 Sep 20:29
7f67d2c
Compare
Choose a tag to compare

What's Changed

Exciting New Features 🎉

Bug fixes🧑‍🔧 🐞

  • Fix support for forward slashes with nested folders in cd_files for Windows by @tempora-mutantur in #115

Doc improvements 📚

Other Changes

New Contributors

Full Changelog: v0.3.1...v0.3.2

v0.3.1

28 Jul 16:20
Compare
Choose a tag to compare

NOTES

There's been a change in the way the ssh_timeout option and the ssh_handshake_attempts work together, the behaviour is unchanged if both or none are specified, however if only one of the two is set, the other won't have a default value anymore and will be ignored.

What's Changed

Other Changes

New Contributors

Full Changelog: v0.3.0...v0.3.1