Update dependency hashicorp/packer to v1.11.0#3
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.7.8->1.11.0Release Notes
hashicorp/packer (hashicorp/packer)
v1.11.0Compare Source
1.11.0 (2024-05-31)
NOTES:
A LICENSE.txt file has been added to the Packer release artifacts.
GH-12931
GH-12940
Breaking Change: Support for loading single-component plugins has been removed from Packer. GH-12785
Breaking Change: Support for loading plugin binaries following
the naming convention of packer-plugin-name has been dropped. Packer will now only load
plugins stored under the Packer plugin directory using the expected namespaced
directory and CHECKSUM files. This change drops support for loading plugin
binaries in Packer's executable directory or a template's current working
directory. GH-12828
/Users/dev/.packer.d/plugins └── github.com └── hashicorp └── happycloud ├── packer-plugin-happycloud_v0.0.1_x5.0_darwin_arm64 └── packer-plugin-happycloud_v0.0.1_x5.0_darwin_arm64_SHA256SUMFEATURES:
-ignore-prerelease-pluginsflag to disable the use of developmentplugin binaries for the
buildandvalidatecommands development pluginbinaries. GH-12828
GH-12882
build artifact in HCP Packer.
GH-12866
For feature parity with Terraform, and since having access to strings
encoded in something that is not UTF-8 is required in some cases, we add
both the textencodebase64 and textdecodebase64 functions to HCL2 templates.
Please note these functions return base64 encoded byte slices because of how
cty/hcl defines strings (NFC normalised, UTF-8 encoded).
GH-12997
SECURITY:
GH-12880
GH-12924
IMPROVEMENTS:
GH-12935
GH-12942
GH-12960
GH-12979
GH-12932
GH-12988
Previous versions of Packer only supported 200 as a success case for the http
datasource. This change makes any status code from 200 to 299 successful.
GH-12989
plugins stored under the Packer plugin directory using the expected namespaced
directory and CHECKSUM files.
GH-12828
GH-12785
packer plugincommand topacker executeto avoid user confusion withthe plugins subcommand.
GH-12865
version constraints. This work allows users to use binaries with versions
reported as "x.y.z-dev" to be used with the Packer
required_pluginsblock. GH-12828
packer plugins removecommand. This addition makes it possible to pipe commands like
packer plugins installedwith it for speedy cleanup of installed plugins.GH-12886
required_pluginsblock tosupport the installation of local plugin binary using a custom or internal
source address (e.g. mycompany.com/plugins/happyorg/happycloud). Remote
installation using
packer initorpacker plugins installdoes notsupport non-GitHub source URIs. Users using alternative hosts must
install plugins manually using
packer plugins install --path.GH-12911, [GH-12962] (https://github.com/hashicorp/packer/pull/12962)
differs from the version number within the binary name can lead to
confusion when tracking Packer plugin version information. To help track
such discrepancies in the plugin version,
packer initandpacker plugin installhave been updated to reject installation of such plugins.1.0.0-dev). Users are encouraged to notify plugin maintainers of any
version mismatches.
GH-12915, GH-12953, GH-12972
To avoid confusion with multiple plugins that report the same effective version,
plugins installed need to have no metadata in their name.
When installed through Packer commands, the metadata is scrubbed from the name of the
installed plugin binary, but manually it may still be possible, so we enforce
that scrubbing at load-time as well.
GH-12980
Since Packer 1.11 removed the capability for PACKER_PLUGIN_PATH to specify
multiple directories separated by
:or;(depending on the platform), weare explicitly erroring when this is discovered, with suggestions as to how
to fix the problem.
GH-12967
in their versions, Packer supports it, and applies the semver recommendations on
them, i.e. they are ignored for comparison/sorting purposes, but allowed for
adding extra information about a plugin.
GH-12888
Given the specified version constraint only versions greater than or equal to 1.1.0 will be considered.
If a development binary is installed, Packer will use it if:
/Users/dev/.packer.d/plugins └─ github.com └─ hashicorp └── amazon ├── packer-plugin-amazon_v1.1.0_x5.0_darwin_arm64 ├── packer-plugin-amazon_v1.1.0_x5.0_darwin_arm64_SHA256SUM ├── packer-plugin-amazon_v1.1.1-dev_x5.0_darwin_arm64 └── packer-plugin-amazon_v1.1.1-dev_x5.0_darwin_arm64_SHA256SUMVersion 1.1.1-dev of the Amazon plugin will match the specified version constraint and be used for executing the Packer build.
If, however, a 1.1.1 release version of the plugin is available, it will have precedence over the development binary.
/Users/dev/.packer.d/plugins └─ github.com └─ hashicorp └── amazon ├── packer-plugin-amazon_v1.1.1-dev_x5.0_darwin_arm64 ├── packer-plugin-amazon_v1.1.1-dev_x5.0_darwin_arm64_SHA256SUM ├── packer-plugin-amazon_v1.1.1_x5.0_darwin_arm64 └── packer-plugin-amazon_v1.1.1_x5.0_darwin_arm64_SHA256SUMBUG FIXES:
with how plugins are discovered by Packer, and ensures proper version ordering.
This means that with this change, versions that are semantically greater,
but lexicographically inferior will be loaded.
Ex: 1.0.9 vs. 1.0.10;
1.0.9 > 1.0.10lexicographically, but semantically1.0.10 > 1.0.9Packer metadata storage map.
GH-12936
This fix addresses bugs present in the alpha releases of 1.11, where
the discovery of Windows binaries were not matching against the
filename extension (.exe).
GH-12981
v1.10.3Compare Source
1.10.3 (April 22, 2024)
NOTES
12981
FEATURES
build artifact in HCP Packer.
GH-12891
GH-12910
GH-12923
GH-12926
SECURITY
GH-12928
GH-12924
BUG FIXES
fmtfails due to HCL2parsing error. GH-12870
v1.10.2Compare Source
1.10.2 (March 6, 2024)
NOTES:
a locally sourced plugin using packer
plugins install --path, thisrelease extends support to development plugin binaries - binaries that
report "dev" as part of their plugin version. Instead of manually placing a
downloaded binary into the executable or current working directory we
encourage you to run the command
packer plugins install –path <path-to- downloaded-extracted-binary> github.com/hashicorp/happycloudto installthe binary into a Packer compatible path.
GH-12855
IMPROVEMENTS:
packer plugins install.GH-12855
hcp_packer_registryblock.GH-12820
GH-12850
GH-12827
BUG FIXES:
plugins and general publishing errors.
GH-12854
GH-12835
v1.10.1Compare Source
1.10.1 (January 30, 2024)
NOTES:
publishing and consuming built artifacts. To best support the new approach, HCP Packer components within Packer have
been updated to use the v2 nomenclature when publishing build metadata to
HCP Packer. These changes include data source components for consuming HCP
Packer stored artifacts. The data source components hcp-packer-version
and hcp-packer-artifact respectively replace, the now deprecated,
hcp-packer-iteration
and hcp-packer-image
component data sources. The added changes are compatible with all existing HCP Packer workflows and do not warrant any
immediate template changes by the user. However, we encourage all HCP Packer users to visit the updated
HCP Packer CHANGELOG to familiarize themselves with the nomenclature changes.
GH-12794 GH-12799
hcp-packer-imagedata source has been deprecated, please use HCP PackerArtifact data source instead.
GH-12794
hcp-packer-iterationdata source has been deprecated, please use HCPPacker Version data source instead.
GH-12794
packer.iterationIDhas been deprecated, please usethe new contextual variable
packer.versionFingerprint. The iterationIDrepresents the HCP Packer iteration that build metadata has been publish
to, with this release an Iteration is now referred to as a Version and the
ID has been replaced by the Version Fingerprint.
GH-12803
FEATURES:
hcp-packer-artifactThe HCP Packer Artifact Data Sourceretrieves information about an artifact from the HCP Packer Registry.
GH-12794
hcp-packer-versionThe HCP Packer Version Data Sourceretrieves information about HCP Packer Version from the HCP Packer.
Registry. GH-12794
SECURITY:
IMPROVEMENTS:
GH-12792
GH-12764
GH-12800
this change HCP Packer iterations are now referred to as Versions, and
Images are now referred to as Artifacts. The data sources for interacting
with HCP Packer have been respectively renamed to align with the terminology
of Version and Artifact.
GH-12794
GH-12799
GH-12742
GH-12743
v1.10.0Compare Source
1.10.0 (December 5, 2023)
NOTES:
This release contains breaking changes for practitioner relying on plugins
previously bundled into Packer. As specified in the Bundled Plugins Removal announcement
HashiCorp maintained plugins will no longer be shipped with Packer.
Users are encouraged to use
packer initorpacker plugins [...]when managing required pluginsneeded for executing their builds.
GH-12660
The affected plugins include:
SECURITY:
no reported issues with Packer but we are bumping given that it is a
secondary
dependency. GH-12723
GH-12661
Packer but we are bumping given its usage of the path/filepath pkg.
GH-12690
GH-12717
PLUGINS:
GH-12660, GH-12720
Hetzner integrations team. New releases for this plugin are available at
https://github.com/hetznercloud/packer-plugin-hcloud. Existing references
to the plugin will continue to work but users are advised to update the
required_pluginsblock to use the new plugin source address.required_plugins {
parallels = {
source = "github.com/hetznercloud/hcloud"
version = "~> 1"
}
}
IMPROVEMENTS:
packer initon configuration templates with amissing
required_pluginsblocks.GH-12638
--pathflag topacker plugins installsubcommand tosupport installation of plugins from a local binary rather than from
GitHub. GH-12643
GH-12665
GH-12666
for removal. GH-12669
GH-12712
source dependencies.
GH-12608
GH-12704
GH-12717
is unknown. GH-12705
packer -vandpacker --versionto matchpacker version.GH-12569
above. GH-12713
BUG FIXES:
packer plugin installedto show all installed pluginbinaries, including any duplicate versions or binaries copied from a
different source URI.
GH-12731
v1.9.5Compare Source
1.9.5 (December 4, 2023)
SECURITY
GH-12723
BUG FIXES:
GH-12719
v1.9.4Compare Source
1.9.4 (August 18, 2023)
BUG FIXES:
reporter is left uninitialized in order to disable telemetry reporting.
Any method calls on the nil reporter is expected to check if the reporter is active or in
NOOP mode. The SetBundledUsage function, introduced in Packer 1.9.2, failed to perform a nil
check before attempting to modify an attribute, causing Packer to fail when telemetry is
disabled. This release fixes this issue by introducing such a check.
v1.9.3Compare Source
1.9.3 (August 17, 2023)
NOTES:
Docker target called
release-fullhas been added to the Packer releaseartifacts. The release-full image includes Packer and all the official
plugins pre-installed in its environment. This image is being offered as an
alternative option for those users who may still be relying on the plugin
versions bundled into the Packer binary.
GH-12532
IMPROVEMENTS:
packer initcommand for HCL2template builds.GH-12535
with a project level service principals must provide a valid HCP_PROJECT_ID
in order to connect.
GH-12520
GH-12576
packer:release-fullhas been added for allsupported architectures. The release-full image includes Packer and all the
official plugins pre-installed in its environment.
GH-12532
GH-12536
BUG FIXES:
itself is not vulnerable to the CVE as we don't render web pages, but
security checks do point it as an issue that needs to be addressed.
GH-12561
GH-12544
v1.9.2Compare Source
1.9.2 (July 19, 2023)
NOTES:
Vendored plugins within Packer have not been updated. Plugin releases occur on
a regular basis to address issues and feature requests.
Please note that in an upcoming version of Packer, we will remove the last
bundled plugins from Packer.
Users are encouraged to use
packer initfor HCL2 templates orpacker plugins installwith legacy JSON templates for installing externalplugins.
Packer will now warn when using bundled plugins. This feature will be removed in
a future version of the tool, so this warning is meant to bring awareness of the
upcoming change, and to help users update their environment/templates to be
ready for this.
GH-12495
BUG FIXES:
Fixed a bug with how Packer was discovering plugins: in order to load
plugins, Packer would recursively scan all the known directories in which
we could have installed plugins. This caused unnecessary directory
walks and slowdowns upon invocation. Packer will now only check
for nested plugins within the directories used by commands such as
packer init, orpacker plugins install, or as defined in PACKER_PLUGIN_PATH.Refer to
Packer's plugin directory documentation
for details on how loading works.
GH-12414
The
packer initsubcommand now bundles all the missing installed plugins into onecondensed warning, as opposed to one warning per missing plugin.
GH-12506
PLUGINS:
team. New releases for this plugin are available at
https://github.com/parallels/packer-plugin-parallels. This plugin is is no longer
being bundled in the Packer binary release. Existing references to the
plugin will continue to work but users are advised to update the
required_pluginsblock to use the new plugin source address.GH-12476
required_plugins {
parallels = {
source = "github.com/parallels/parallels"
version = "~> 1"
}
}
IMPROVEMENTS:
hcl2_upgradesubcommand will now addrequired_pluginsto the templategenerated from JSON for all our officially supported plugins.
GH-12504
v1.9.1Compare Source
1.9.1 (June 1, 2023)
BUG FIXES:
In order to use multiple projects in your organization, you will need to update Packer
to version 1.9.1 or above. Starting with 1.9.1, you may specify a project ID to push
builds to with the
HCP_PROJECT_IDenvironment variable. If no project ID is specified,Packer will pick the project with the oldest creation date. Older versions of Packer are
incompatible with multi-project support on HCP, and builds will fail for HCP
organizations with multiple projects on versions before 1.9.1.
GH-12453
v1.9.0Compare Source
1.9.0 (May 31, 2023)
NOTES:
Breaking Change: Iteration fingerprints used to be computed from the Git SHA of the
repository where the template is located when running packer build. This
changes with this release, and now fingerprints are automatically generated
as a ULID. This implies that continuing an existing iteration will require
users to define the fingerprint in the environment manually in order to
adopt this behaviour, otherwise, by default, a new iteration will be
created. This does not impact workflows where the fingerprint was defined
through the
HCP_PACKER_ITERATION_FINGERPRINTenvironment variable, andthese builds will work exactly as they did before.
GH-12172
Breaking Change: Community-maintained plugins bundled with the Packer binary have been removed.
These external plugin components are released independently of Packer core and can be installed
directly by the user. Users relying on the external plugin components listed below should refer
to the
packer pluginssub-command and, if using HCL2, arequired_pluginsblock to define alist of plugins for building a template.
PLUGINS
Remove provisioner plugins for Chef, Converge, Puppet, Salt, and Inspec as
vendored plugins. These plugins have been previously archived and not
updated in release since being archived. These plugins can be installed
using
packer initor with the Packer plugins sub-commandpacker plugins install github.com/hashicorp/chef.GH-12374
The following community plugins won't be bundled with Packer anymore:
GH-12436
Users relying on these external plugin components should refer to the
packer pluginssub-command and,if using HCL2, a
required_pluginsblock to define a list of plugins to use for building a template.IMPROVEMENTS:
instead of a Git SHA, and a new one is always generated, unless one is
specified in the environment.
GH-12172
BUG FIXES:
Fix LDFLAGS for release pipelines: Between Packer 1.8.5 and Packer 1.8.7, changes
to the LDFLAGS in use for building the binaries for Packer had mistakenly
removed some compilation flags, leading to the final binaries not being stripped.
This change raised the size of the built binaries by as much as 45%.
In this release, we fixed the LDFLAGS during compilation, yielding leaner binaries.
Bumped gopsutil to v3. This fixes a macOS intermittent crash reported by the community
GH-12430
v1.8.7Compare Source
1.8.7 (May 4, 2023)
NOTES:
Vendored plugins within Packer have not been updated. Plugin releases occur on
a regular basis to address issues and feature requests. Users are encouraged
to use
packer initfor HCL2 templates orpacker plugins installwithlegacy JSON templates for installing external plugins.
packer-plugin-digitalocean: The Digital Ocean Packer plugin has been handed
over to the Digital Ocean team. New releases for this plugin are available
at https://github.com/digitalocean/packer-plugin-digitalocean.
required_plugins {
digitalocean = {
source = "github.com/digitalocean/digitalocean"
version = ">=1.1.1"
}
}
packer-plugin-linode: The Linode plugin has been handed over to the Linode
team. New releases for this plugin are available at
https://github.com/linode/packer-plugin-linode. This plugin is is no longer
being bundled in the Packer binary release. Existing references to the
plugin will continue to work but users are advised to update the
required_pluginsblock to use the new plugin source address.GH-12329
required_plugins {
linode = {
source = "github.com/linode/linode"
version = ">=1.0.5"
}
}
packer-plugin-ucloud: The UCloud plugin has been handed over to the UCloud
team. New releases for this plugin are available at
https://github.com/ucloud/packer-plugin-ucloud. This plugin is is no longer
being bundled in the Packer binary release. Existing references to the
plugin will continue to work but users are advised to update the
required_pluginsblock to use the new plugin source address.GH-12335
required_plugins {
ucloud = {
source = "github.com/ucloud/ucloud"
version = ">=1.0.8"
}
}
packer-plugin-profitbricks: The Profitbricks plugin has been removed as a
bundled plugin in Packer. New releases for this plugin are available at
https://github.com/hashicorp/packer-plugin-profitbricks. This plugin is is
no longer being bundled in the Packer binary release. Existing references
to the plugin will continue to work but users are advised to update the
required_pluginsblock to use the new plugin source address.GH-12385
required_plugins {
ucloud = {
source = "github.com/hashicorp/profitbricks"
version = ">=1.0.2"
}
}
PLUGINS
GH-12329
GH-12335
GH-12376
GH-12385
GH-12217
IMPROVEMENTS
GH-12360
GH-12319
GH-12356,
GH-12366
BUG FIXES
legacy JSON template containing user variables with an undefined variables
block. GH-12257
GH-12292
CVE-2023-0475, CVE-2022-41723.
GH-12306
GH-12380
custom builder names are outputted to STDOUT as uninterpolated user
variables. GH-12290
v1.8.6Compare Source
1.8.6 (February 15, 2023)
NOTES:
build for JSON templates. Previously only the builder type or the builder
name, if it was set, would be displayed. Now for named builders
(
"name":"mybuilder") the builder's type and name will be displayed (i.e".mybuilder". This does not impact the behavior of options such as
only or except, they will continue to work as they did before.)
IMPROVEMENTS:
GH-12271
GH-12163
GH-12262
-only/exludefilters for running select builds.GH-12187
BUG FIXES:
GH-12250
would display an empty string for the template filename at line 0, which
made it difficult to identify the broken build block. Packer has been
updated to display the proper filename and line number where the unknown
reference resides.
GH-12167
HashiCorp. This fix is implemented for any future releases, but will not be
updated for historical releases.
v1.8.5Compare Source
1.8.5 (December 12, 2022)
NOTES:
unusable data source that was built for experimentation but not released. It
should not affect users in any way but is being mentioned for visibility
purposes.
GH-12111
FEATURES:
HCP Packer registry metadata. Upon running a
packer buildthe type oftemplate used during execution will be sent along to the registry as
additional build metadata.GH-12132
PLUGINS:
The following external plugins have been updated and pinned to address open
issues. Please see their respective changelogs for details on plugin
specific bug fixes and improvements.
IMPROVEMENTS:
variables. GH-12136
-evaluate-datasourcesflag to evaluatethe data sources from a template during validation time.
GH-12106
GH-12152
an HCL2 template will no longer warn during build execution. Warnings will
be displayed to a user during template validation, which can be disabled by
passing the
-no-warn-undeclared-varflag to the validate command.GH-12104
GH-12109
xorrisopackage forsupporting the creation of ISO files.GH-12081
module. GH-11
GH-12116
BUG FIXES:
for a plugin, if the most recent version is not available or has a missing
checksum file. This should prevent Packer from trying to install versions
that have a GitHub tag but no actual assets.
GH-12103
plugins installsub-command will try to fallback to thenext available version for a plugin, if the most recent version is not
available or has a missing checksum file. This should prevent Packer from
trying to install versions that have a GitHub tag but no actual assets.
GH-12103
concerns the net/http and golang.org/x/net
packages.GH-12153
GH-12158
setting
keep_input_artifactstofalse.GH-11462
image iteration will now trigger a runtime build error due to the
mixing of template types.
GH-12132
v1.8.4Compare Source
1.8.4 (October 28 2022)
NOTES:
Packer user documentation has been moved to the new HashiCorp developer
documentation portal. The main Packer site (https://www.packer.io) will
continue to be the home for Packer but all requests for general
documentation and binary downloads will be redirected to
https://developer.hashicorp.com/packer. Users are encouraged to visit the
developer documentation portal for access to all Packer related
documentation; including integrations with HCP Packer.
The Oracle builder and post-processor are no longer vendored with Packer
core. Users of the Oracle plugin should use
packer initto install thelatest version of the plugin. See the Oracle Plugin
Documentation for more
information. GH-11983
HCP Packer environment variables: The behaviour of some HCP Packer-specific
environment variables has changed slightly. Refer to HCP Packer
in the Packer documentation for a full list of HCP Packer environment variables. GH-12059
HCP_PACKER_REGISTRYenvironment variable waspreviously required to enable the HCP Packer integration. In this release,
the environment variable is now optional, and can be used for disabling the
publishing of metadata for any HCP Packer enabled configuration template.
HCP_PACKER_REGISTRYenvironment variable can be usedto disable publishing to a HCP Packer registry even if the template defines a
hcp_packer_registryblock. This can be useful for testing that a templateworks as intended prior to pushing metadata to HCP Packer.
HCP_PACKER_BUCKET_NAMEenvironment variable is now the onlyrequirement to push metadata to a HCP Packer registry, in both JSON
and HCL2 templates without a
hcp_packer_registryblock.FEATURES:
use_pwshconfiguration argument to support pwshin powershell provisioner. GH-11950
PLUGINS:
plugins. GH-11983
IMPROVEMENTS:
engine options that were supported by the legacy JSON templates. While the
upgrade command copies the template engine options as is support for the
template options may not actually work with HCL2 templates; indicated by an
error similar to
fieldname type <no value> is invalid. Before executing abuild with the upgraded template you are encouraged to run
packer validateagainst the template and fix any invalid
<no value>references.GH-12068
sources selected for execution.
GH-12016
consolidated into a single report to help users address all potential
issues before retrying their build.
GH-12031
HCP Packer registry using its full build name (e.g
happycloud.windows-srv-2019),as opposed to just the build name field (e.g
"name"="windows-srv-2019").Builders with no defined name will continue to publish build
metadate using the builder type as the build name (e.g
happycloud).GH-12059
*.pkrvars.hcl), but isn't defined with the template files (i.e
*.pkr.hcl), the outputted error message will now include an example of
variable block that can be added to the build template to remedy the issue.
GH-12020
GH-11966
GH-11981
GH-11927
BUG FIXES:
shared_image_galleryfix.GH-12087
GH-11953
GH-12047
GH-12009
v1.8.3Compare Source
1.8.3 (August 2, 2022)
NOTES:
There's been a change in the way the
ssh_timeoutand thessh_handshake_attemptsconfiguration arguments work together. Thebehaviour 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. See Packer Plugin SDK change for details
packer-plugin-digitalocean: The Digital Ocean Packer plugin has been handed over
to the Digital Ocean team. New releases for this plugin are available at
https://github.com/digitalocean/packer-plugin-digitalocean. This plugin is
still being bundled in the Packer binary but will be removed in a future
release. Existing references to the plugin will continue to work but
users are advised to update the required_plugins block to use the new
plugin source address.
GH-11912
packer-plugin-outscale: The Outscale Packer plugin managed by the Outscale
team, since Packer 1.7.9, has been removed from the Packer binary. Users are
advised to install the latest version of the plugin by running
packer plugins install github.com/outscale/outscale. GH-11912packer-plugin-outscale: The Scaleway Packer plugin managed by the Scaleway
team, since Packer 1.7.7, has been removed from the Packer binary. Users are
advised to install the latest version of the plugin by running
packer plugins install github.com/scaleway/scaleway. GH-11912FEATURES:
Packer core to validate that a newly built image is a direct child of a HCP
Packer registry source image. This feature is only available for HCP Packer
enabled builds using the
hcp_packer_imageandhcp_packer_iterationdatasource for setting a builder's source image.
GH-11861
PLUGINS:
The following external plugins have been updated and pinned to address open
issues. Please see their respective changelogs for details on plugin
specific bug fixes and improvements.
IMPROVEMENTS:
ssh_timeoutand
ssh_handshake_attemptsconfiguration arguments in the SSHcommunicator. GH-11909
timed out if it has not posted an update after a certain number of minutes. For HCP
Packer enabled builds a status update will now be sent every 2 minutes to
the registry to prevent long builds from being marked as timed
out. GH-11846
component_typeconfiguration argument tosupport specifying an exact build image when multiple images exist in the
same provider and region for a given HCP Packer bucket iteration.
GH-11872
channelas input argument toretrieve an image from the associated iteration. If
using several images from a single iteration, you may prefer sourcing an
iteration first, and referencing it for subsequent uses, as every
hcp_packer_imagewith the channel set will generate a potentiallybillable HCP Packer request, but if several
hcp_packer_images use ashared
hcp_packer_iterationthat will only generate one potentiallybillable request.
GH-11865
BUG FIXES
GH-11881
packer validateon templates containingone or more HCP Packer data sources.
GH-11883
v1.8.2Compare Source
1.8.2 (June 21, 2022)
NOTES:
The Packer plugin SDK includes the latest version of the go-getter library, which has been updated to address the vulnerabilities listed in HCSEC-2022-13.
The updated SDK contains changes that can be breaking for some plugins as the updated go-getter settings in the SDK prevent reading/writing through symlinks and to sub-directories that require upward path traversal (e.g /tmp/.../etc/hosts). The updates also includes a 30 minute maximum timeout for file downloading, which can be an issue for very large or slow downloads if they exceed more than 30 minutes to complete.
SECURITY:
the go-getter library.
GH-11843
reported vulnerabilities within the go-getter library. See HCSEC-2022-13 for details.
GH-11844
FEATURES:
validate that a newly built image is a direct child of a HCP Packer
registry source image. This feature is only available for HCP Packer
enabled builds using the
hcp_packer_imagedata source for setting abuilder's source image.
GH-11832
PLUGINS:
External plugins have been pinned to the following versions. Please see their
respective changelogs for details on plugin specific bug fixes and
improvements.
IMPROVEMENTS:
pause_afterconfiguration argument to Powershell provisioner.GH-11792
GH-11854
BUG FIXES:
envconfiguration argument in remote shellprovisioners. GH-11819
directives, have been removed from the Pa
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.