From 58bfbc2f1a01d36807b7b3a784444c9d590c7da7 Mon Sep 17 00:00:00 2001 From: Chris Roberts Date: Mon, 24 Jun 2024 10:18:11 -0700 Subject: [PATCH] Merge pull request #13465 from hashicorp/packer-registry Add entry for vagrant-registry packer post-processor --- .../vagrant-cloud/hcp-vagrant/post-migration-guide.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/website/content/vagrant-cloud/hcp-vagrant/post-migration-guide.mdx b/website/content/vagrant-cloud/hcp-vagrant/post-migration-guide.mdx index 6c3415b1772..fea1484880e 100644 --- a/website/content/vagrant-cloud/hcp-vagrant/post-migration-guide.mdx +++ b/website/content/vagrant-cloud/hcp-vagrant/post-migration-guide.mdx @@ -70,3 +70,9 @@ If all organizations have been migrated to HCP Vagrant Registry, only the HCP ac ``` export VAGRANT_CLOUD_TOKEN=";$(hcp auth print-access-token)" ``` + +# Packer + +After migrating to HCP, box uploads may fail when using the [vagrant-cloud](/packer/integrations/hashicorp/vagrant/latest/components/post-processor/vagrant-cloud) post-processor. This is due to the HCP access token used in the composite token expiring prior to the post-processor being executed. + +To resolve this issue, a new Packer post-processor has been introduced: [vagrant-registry](/packer/integrations/hashicorp/vagrant/latest/components/post-processor/vagrant-registry). This post-processor iteracts directly with the HCP Vagrant Box Registry and removes the requirement of a composite access token. The configuration of the `vagrant-registry` post-processor matches the configuration of the `vagrant-cloud` post-processor with the exception of the [authentication settings](/packer/integrations/hashicorp/vagrant/latest/components/post-processor/vagrant-registry#required) which requires a `client_id` and `client_secret` value instead of the `access_token` used by the `vagrant-cloud` post-processor.