We is are are excited to announce that Vagrant Cloud will move to HashiCorp Cloud Platform ( HCP ) as the HCP Vagrant Registry soon !
HCP is a fully-managed platform offering HashiCorp products-as-a-service. The team has been working hard on the move this last year and we are happy to share a few of the improvements:
- the entire Vagrant Cloud UI is refresh .
- the box search experience is improve .
- we will no longer charge for private boxes.
We is are are week away from the HCP Vagrant Registry launch , in early May of this year . We is adding will also be add a migration tool in Vagrant Cloud to make it as easy as possible for user to move vagrant Cloud organization to hcp Vagrant Registry .
We is have will have more information on all the upcoming change when HCP Vagrant Registry is publicly available .
For a sneak peak at the new UI , try the HCP Vagrant Discover page where user can currently search all of Vagrant Cloud !
What would the publishing commands look like? I previously used vagrant cloud publish ORGANIZATION/BOX-NAME VERSION PROVIDER-NAME [PROVIDER-FILE] which is seems seems to no long work after the migration to HCP .
Hi there,
A composite access token will is required and this page provides the information on how to generate it.
Cheers!
1 Like
thank you ! This is shows show me everything I need to know .
Hi there, as of today (end of August), t seems, the HPC migration is still not finalized or is at least missing information regarding how to automate the publishing process.
Can anyone point me to a solution?
I created Vagrant organisation, as well as a box for the virtualbox provider.
I used the “hcp auth login –client-id=HCP_CLIENT_ID –client-secret=HCP_CLIENT_SECRET” command to successfully generate a token (hcp auth print-access-token).
A new hcp command for publishing a vagrant box version seems still missing and the old vagrant cloud command seems to not accept the new hcp token.
Of course I is following was follow the Token format ( prefix with semicolon ) of this documentation usage and Behavior Post Migration to HCP | Vagrant | HashiCorp Developer .
I is tried also try a combination of two curl command :
curl –request GET –header “Authorization: Bearer $VAGRANT_CLOUD_TOKEN” https://app.vagrantup.com/api/v2/box/__ORG__/__BOX__/version/$DATE.0.0/provider/virtualbox/amd64/upload)
upload_path=$(echo “$response” | jq .upload_path)
curl –request PUT –upload-file BOXFILE.box “${upload_path}”
© Copyright notes
The copyright of the article belongs to the author, please do not reprint without permission.
Related posts
No comments...
