v2.3.1
What's Changed
This release contains two small changes to log more accurately what happens when the Azure plugin fails to fetch a SIG source name.
For HCP Packer Ancestry this plugin will try and fetch the source image name of the SIG, this is done because it can not be inferred since the SIG image may originally come from either a Virtual Machine, or a managed image, and we have to check the storage ID to figure out what type of image it is. When we fail the API check to get the gallery image version, the plugin continues since this was additional logic added for HCP Packer, and was added to not be a breaking change, but the error message was squashed before this release
- Clearly log result of failing to get the source name for SIG-sourced builds. by @JenGoldstrich in #476
- Clearly log result of unexpected Azure payloads when fetching a source image name on SIG-sourced builds by @JenGoldstrich in #477
Full Changelog: v2.3.0...v2.3.1
Contributors
JenGoldstrich