• HashiCorp Developer

  • HashiCorp Cloud Platform
  • Terraform
  • Packer
  • Consul
  • Vault
  • Boundary
  • Nomad
  • Waypoint
  • Vagrant
Vagrant
  • Install
  • Intro
  • Tutorials
  • Documentation
  • Vagrant Cloud
  • Try Cloud(opens in new tab)
  • Sign up
Vagrant Home

Vagrant Cloud

Skip to main content
  • Vagrant Cloud
    • Overview
    • Catalog
    • Creating a New Box
    • Creating a New Version
    • Distributing
    • Lifecycle
    • Private Boxes
    • Release Workflow
    • Finding & Using Boxes
  • Request Limits
  • Support
  • API

  • Resources

  • Tutorial Library
  • Community Forum
    (opens in new tab)
  • Support
    (opens in new tab)
  • GitHub
    (opens in new tab)
  1. Developer
  2. Vagrant
  3. Vagrant Cloud
  4. Boxes
  5. Release Workflow
  • Vagrant
  • v2.3.3
  • v2.3.2
  • v2.3.1
  • v2.3.0
  • v2.2.19
  • v2.2.18
  • v2.2.17
  • v2.2.16
  • v2.2.15
  • v2.2.14
  • v2.2.13
  • v2.2.12
  • v2.2.11
  • v2.2.10

ยปAPI Release Workflow

Creating new boxes through their release lifecycle is possible through the Vagrant Cloud website, but you can also automate the task via the Vagrant Cloud API.

  1. Create box, or locate a boxes tag, like hashicorp/bionic64
  2. After some event, like the end of a CI build, you may want to release a new version of the box. To do this, first use the API to create a new version with a version number and a short description of the changes
  3. Then, create any providers associated with the version, like virtualbox
  4. Once your system has made the necessary requests to the API and the version is ready, make a request to the release endpoint on the version
  5. The version should now be available to users of the box via the command vagrant box outdated or via the automated checks on vagrant up
Edit this page on GitHub
Give Feedback(opens in new tab)
  • Certifications
  • System Status
  • Terms of Use
  • Security
  • Privacy
  • Trademark Policy
  • Trade Controls
  • Give Feedback(opens in new tab)