upstream/vagrant
1
0
Fork 0
mirror of https://github.com/hashicorp/vagrant.git synced 2026-06-10 17:20:16 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Add entry for vagrant-registry packer post-processor

Browse source
This commit is contained in:
Chris Roberts 2024-06-24 09:52:27 -07:00
parent 54a1999546
commit f562149e8b
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
website/content/vagrant-cloud/hcp-vagrant/post-migration-guide.mdx
View file

@ -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.