capture_name_prefix
and capture_container_name
do not appear as expected in the resulting Packer manifest JSON file
#339
Labels
Overview of the Issue
In our workflow, we build and save off several Packer images over multiple stages. To make sure we're building on top of the previous stage, we always recall the
artifact_id
of the previous build from themanifest.json
file. After the upgrade fromv1.4.5
tov2.0.0
, theartifact_id
entries inmanifest.json
no longer match up with the artifacts that are actually saved to blob storage. We would expect both theartifact_id
and the URL of the blob to look like this as noted in the docs:https://<storage_account>.blob.core.windows.net/system/Microsoft.Compute/Images/<capture_container_name>/<capture_name_prefix>.xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.vhd
But instead, the
artifact_id
inmanifest.json
is always set to the defaults for thecapture
arguments and instead looks like this:https://<storage_account>.blob.core.windows.net/system/Microsoft.Compute/Images/images/packer.xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.vhd
The UUID in the file name is still stored correctly so this can be worked around for now by reconstructing the image path with the correct arguments.
Reproduction Steps
capture_name_prefix
other than the default of "packer".manifest.json
to the name of the image saved in blob storage. Themanifest.json
will have the default "packer" prefix for the image while the image in blob storage will be appropriately named using thecapture_name_prefix
.Plugin and Packer version
Simplified Packer Buildfile
Operating system and Environment details
Images are built on Ubuntu 22.04. Packer is ran from a Jenkins instance.
Log Fragments and crash.log files
Expected (v1.4.5):
Actual (v2.0.0):
The text was updated successfully, but these errors were encountered: