Log message:
packer: update to 1.9.2
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 init
for HCL2 templates or packer plugins install with legacy JSON templates
for installing external plugins.
* 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 help users update their
templates.
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, or packer plugins install, or as defined in
PACKER_PLUGIN_PATH. Refer to Packer's plugin directory documentation
for details on how loading works.
* The packer init subcommand now bundles all the missing installed plugins
into one condensed warning, as opposed to one warning per missing
plugin.
PLUGINS:
* packer-plugin-parallels: The Parallels plugin has been handed over to the
Parallels team. New releases for this plugin are available at
https://github.com/parallels/packer-plugin-parallels. This plugin 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_plugins block to use the new plugin source address.
required_plugins {
parallels = {
source = "github.com/parallels/parallels"
version = "~> 1"
}
}
IMPROVEMENTS:
* The hcl2_upgrade sub-command will now add required_plugins to the
template generated from JSON for official plugins.
|
Log message:
packer: update to 1.9.1
1.9.1 (June 1, 2023)
BUG FIXES:
* On May 16th 2023, HCP introduced multi-project support to the
platform. 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_ID
environment 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
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_FINGERPRINT
environment variable, and these 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 plugins sub-command and, if using HCL2, a
required_plugins block to define a list 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 init or with the Packer plugins sub-command packer plugins
install github.com/hashicorp/chef. GH-12374
* The following community plugins won't be bundled with Packer anymore:
- Alicloud
- CloudStack
- HCloud
- HyperOne
- Hyper-V
- JDCloud
- LXC
- LXD
- NCloud
- OpenStack
- Proxmox
- TencentCloud
- Triton
- Yandex
GH-12436
Users: relying on these external plugin components should refer to the
packer plugins sub-command and, if using HCL2, a required_plugins block to
define a list of plugins to use for building a template.
IMPROVEMENTS:
* core/hcp: Now, fingerprints used by HCP Packer are randomly generated
ULIDs 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
|
Log message:
packer: update to 1.8.7
Pkgsrc changes:
* Update MAINTAINER mail address.
* Specify correct version number using ldflags.
Upstream changes:
PLUGINS
* core: Migrate external Linode plugin to linode/packer-plugin-linode.
* core: Migrate external UCloud plugin to ucloud/packer-plugin-ucloud.
* core: Remove external plugin for Digital Ocean as a vendored plugin.
* core: Remove external plugins for Profitbricks and 1&1 as vendored
plugins.
* docs: Add HCP Ready label to Oracle builder components.
IMPROVEMENTS
* cmd/console: Add config-type flag to command help.
* core: Add enhanced support to Packer telemetry for HCL2.
* Enhance zsh completion for the Packer command.
BUG FIXES
* cmd/hcl2_upgrade: Fix a crash when running the hcl2_upgrade command
against a legacy JSON template containing user variables with an undefined
variables block.
* core: Bump github.com/hashicorp/hcp-sdk-go to 0.36.0.
* core: Bump github.com/hashicorp/packer-plugin-sdk to 0.4.0 to address
CVE-2023-0475, CVE-2022-41723.
* core: Bump Go module version to 1.20
* core: Fix regression introduced in 1.8.6, where legacy JSON templates
with custom builder names are outputted to STDOUT as uninterpolated user
variables.
|
Log message:
packer: Import version 1.8.6.
Originally packaged in wip by Iku Iwasa, updated and some minor fixes by
myself.
Packer is an open source tool for creating identical machine images for
multiple platforms from a single source configuration. Packer is
lightweight, runs on every major operating system, and is highly
performant, creating machine images for multiple platforms in
parallel. Packer does not replace configuration management like Chef or
Puppet. In fact, when building images, Packer is able to use tools like
Chef or Puppet to install software onto the image.
A machine image is a single static unit that contains a pre-configured
operating system and installed software which is used to quickly create new
running machines. Machine image formats change for each platform. Some
examples include AMIs for EC2, VMDK/VMX files for VMware, OVF exports for
VirtualBox, etc.
|