Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add entry for vagrant-registry packer post-processor #13465

Merged
merged 2 commits into from
Jun 24, 2024
Merged

Add entry for vagrant-registry packer post-processor #13465

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f562149
Add entry for vagrant-registry packer post-processor
chrisroberts Jun 24, 2024
432c861
Update website/content/vagrant-cloud/hcp-vagrant/post-migration-guide…
chrisroberts Jun 24, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions website/content/vagrant-cloud/hcp-vagrant/post-migration-guide.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
chrisroberts marked this conversation as resolved.
Show resolved Hide resolved

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