From 86e70ee7f1c61a0c345cd2c5a004cdd90240c76e Mon Sep 17 00:00:00 2001 From: Lucas Bajolet Date: Wed, 7 Jun 2023 18:47:22 +0000 Subject: [PATCH 1/2] backport of commit 3ca74ccca89c2ead56a8c20b1efc08d224a2d99c --- website/content/docs/hcp/index.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/website/content/docs/hcp/index.mdx b/website/content/docs/hcp/index.mdx index 35f7c2fd4..f00eef4bb 100644 --- a/website/content/docs/hcp/index.mdx +++ b/website/content/docs/hcp/index.mdx @@ -47,6 +47,9 @@ Refer to [`hcp_packer_registry`](/packer/docs/templates/hcl_templates/blocks/bui Packer uses a unique fingerprint for tracking the completion of builds associated to an iteration. By default a fingerprint is automatically generated by Packer during each invocation of `packer build`, unless a fingerprint is manually provided via the `HCP_PACKER_BUILD_FINGERPRINT` environment variable. +In versions before 1.9.0, this fingerprint was computed from the git SHA of the current HEAD in which your template is stored. If you are running builds outside of Git, you would have to set the `HCP_PACKER_BUILD_FINGERPRINT` environment variable prior to invoking `packer build`. +Starting with Packer 1.9.0, the fingerprint generation does not rely on Git at all, and instead Packer will generate a Unique Lexicographically sortable IDentifier (ULID). + #### Fingerprints and Incomplete Iterations When you build a template with Packer, there's always a chance that it does not succeed because of a network issue, a provisioning failure, or some upstream error. When that happens, Packer will output the generated fingerprint associated with the incomplete iteration so that you can resume building that iteration using the `HCP_PACKER_BUILD_FINGERPRINT` environment variable; an iteration can be resumed until it is marked as complete. This environment variable is necessary for resuming an incomplete iteration, otherwise Packer will create a new iteration for the build. From 0053fed6837ca29c15a1b685a388cb44af0b124b Mon Sep 17 00:00:00 2001 From: Wilken Rivera Date: Thu, 15 Jun 2023 18:49:03 +0000 Subject: [PATCH 2/2] backport of commit f568b68b920d92eb76b3e6855d1dde1aee162f6e --- website/content/docs/hcp/index.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/hcp/index.mdx b/website/content/docs/hcp/index.mdx index f00eef4bb..b7af158ee 100644 --- a/website/content/docs/hcp/index.mdx +++ b/website/content/docs/hcp/index.mdx @@ -47,8 +47,8 @@ Refer to [`hcp_packer_registry`](/packer/docs/templates/hcl_templates/blocks/bui Packer uses a unique fingerprint for tracking the completion of builds associated to an iteration. By default a fingerprint is automatically generated by Packer during each invocation of `packer build`, unless a fingerprint is manually provided via the `HCP_PACKER_BUILD_FINGERPRINT` environment variable. -In versions before 1.9.0, this fingerprint was computed from the git SHA of the current HEAD in which your template is stored. If you are running builds outside of Git, you would have to set the `HCP_PACKER_BUILD_FINGERPRINT` environment variable prior to invoking `packer build`. -Starting with Packer 1.9.0, the fingerprint generation does not rely on Git at all, and instead Packer will generate a Unique Lexicographically sortable IDentifier (ULID). +In versions before 1.9.0, this fingerprint was computed from the Git SHA of the current HEAD in which your template is stored. If you were running builds using a non Git managed template, you had to set the `HCP_PACKER_BUILD_FINGERPRINT` environment variable prior to invoking `packer build`. +Starting with Packer 1.9.0, fingerprint generation does not rely on Git at all, and instead Packer now generates a Unique Lexicographically sortable Identifier (ULID) as the fingerprint for every `packer build` invocation. #### Fingerprints and Incomplete Iterations